Background

When creating a ticket on Vulcan to ServiceNow, there are three possible options to choose the ticket creation method:

Option number 1 - Separate tickets per unique vulnerability

This is the first option of the three:

For this example, we will use the following Vulnerability:

Unique Vulnerability name - Debian Security Update for e2fsprogs (DLA 1935-1)

Number of vulnerability instances - 4

On this ticket creation option, Vulcan will create a Problem ticket for the unique vulnerability with the name: Debian Security Update for e2fsprogs (DLA 1935-1)

And will create 4 Problem task tickets, for the 4 vulnerability instances, with the name of the affected hosts:

Problem:

Problem Tasks:

Option number 2 - Separate tickets per asset

This is the second option of the three:

For this example, we will use the following Asset:

Asset name: Prod1-AppSrv-51001

Number of related vulnerabilities: 159

On this ticket creation option, Vulcan will create a Problem ticket for the Asset and will create 159 Problem task tickets, for the 159 related vulnerabilities to this asset:

Problem:

Problem Tasks will be a list of 159 related problem tasks.

Option number 3 - Separate tickets per asset

This is the third option of the three:

On this option, all the findings will be aggregated to 1 problem ticket, as attached CSV.

Did this answer your question?