Need the ability to run vulnerability assignment rules on Closed or Inactive vulnerabilities

D_SantiagoHQY
Tera Contributor

Context:
In the Application Vulnerability Response plugin, we are working with a vendor that doesn't have an integration, so we've built import sets to import the data. 

Issue:

We aren't able to run the Assignment rules on Closed or Active = false vulnerabilities, or on Vulnerabilities that have a specific Assignment Group already assigned. 

Why is this important:

When importing already closed vulnerabilities, we need to be able to show what group fixed them (this is based on the assigned vulnerability remediation group, it's an attribute on the CI). 

My thoughts on this:

It baffles me that SNVR allows for manual import but doesn't allow us to choose to run rules on "closed" vulns. I love the idea of a single pain of glass that SNVR allows for, but having a bunch of unassigned vulns that were "fixed" doesn't allow us to showcase the remediation teams accomplished work. It make reporting much harder then it should be, meaning in order to get around this I'll have to report on the CI's rather then the Vits and that doesn't work considering the limitation of avits, cvits and vits only being created on CI's that ServiceNow see's as "active" when in truth they should be created regardless and depend on the scanner to say when they are remediated or they haven't been seen in so many days (controlled by the Autoclose rules).

Can anyone help me figure out how to get around this limitation?


2 REPLIES 2

Shivam Sarawagi
ServiceNow Employee
ServiceNow Employee

You may have to use the code of the BR "Run assignment rules" on these VITs via a scheduled job or customize the AssignmentUtils to not ignore the closed items.

joe_harvey
ServiceNow Employee
ServiceNow Employee

I like Shivam's idea. If you go with it, you will want to ensure that the Assignment Group is not populated because no rules will run for a VI that is already assigned. Maybe not populate Assignment Group when you import closed VIs? 

 

A different option might be to run a two phased import where the first wave creates & assigns the VI and the second closes it and sets the close values. Not sure of the time required between the two phases. You might need to play with that a bit to get it figured out.

--Joe