About
In response to your valued feedback, we're excited to introduce a highly requested enhancement to the Vulcan Cyber Platform - Ticket Template Customization. We understand that vulnerability remediation is established when efficient communication happens. Through the Ticket Template Customization, you can shape the ticket content to match the organization's needs.
How?
Customizing a ticket is made easy by utilizing an array of available parameters and the flexibility of free-text input.
Support and Limitations
Ticket Customization is only applicable to tickets opened using the Unique Vulnerabilities table through the Take Action for one or multiple vulnerabilities, or generated automatically via Playbooks "Separated by Unique Vulnerabilities" and "Aggregate all Vulnerabilities".
Benefits
Use the organizational terminology
We know that each organization operates with its distinct terminology and processes. With the Ticket Template Customization feature, you're now in complete control. No longer restricted to generic content, you can communicate remediation tasks using your preferred language and terminology. Whether aligning content with your organizational structure, adapting to various asset types, or catering to specific team requirements, this feature places customization in your hands.
Flexibility
The Ticket Template Customization offers a modular ticket template, a canvas to customize to your heart's content. This enables you to create a template that resonates with your team, ensuring every remediation action is clear and actionable.
Better remediation communication
By customizing the ticket template to include selective vulnerability information and actionable content directly aligned with the organizational preferences, you can simplify the remediation process for your team and encourage prompt action.
Creating Ticket Templates
You can customize the default Vulcan template or create new ticket templates:
Go to your Vulcan Platform > Settings > Templates
Click on Create New Template or Duplicate an existing template.
- You can create as many templates as you want.Add/remove parameters. Learn about all the available parameters and their availability across the ticket content blocks.
Modify the default template or start from scratch for tailored communication. In the template editor, you modify the content and apply custom styling, such as:
- Font size and font style (bold, italics, etc.).
- Text alignment (left, center, right).
- Colors for text and backgrounds to match your brand.
- Spacing and layout adjustments to customize how information is displayed.Apply your desired styling by using the available formatting tools. Ensure that the styling aligns with your organizational branding guidelines.
Support Note: Ticket styling options are currently available for Jira, Azure, and Email platforms. Support for ServiceNow is not yet available.
Click Save or Discard Changes.
- For the Vulcan Default template, you can always reset to system defaults by clicking "Reset to system defaults".Once you create a template, you can click the three dots on the template block to Duplicate it, Delete it, or Set it as default.
Use the template across platforms
When you’re ready to use the styled template, you can open tickets on Jira, Azure, or via Email and select the template you wish to use. The styling will be applied consistently across these platforms.
Ticket Parameters Description
Parameter | Return Value Description | Return Value Format and Example |
Business Groups | The names of the business groups impacted by the vulnerability(ies) in the ticket |
|
Count of Assets in Ticket | The number of assets associated with the vulnerabilities in the ticket |
|
Count of Unique Vulnerabilities in Ticket | The number of unique vulnerabilities associated with the ticket |
|
Count of Vulnerability Instances in Ticket | The number of vulnerability instances associated with the ticket |
|
Highest Risk Level | The highest risk level among the vulnerabilities listed in the ticket |
|
One Asset Name | If the ticket has many assets, it displays the first name on the list. |
|
One Vulnerability Name | If the ticket has many vulnerabilities, it displays the first name on the list. |
|
Playbook Name | The playbook name (i.e., automation name) through which the ticket is generated. |
|
Sender Name | The username of the person who opened the ticket or created the playbook |
|
Smart Subject | Option 1: If the ticket contains one vulnerability and multiple assets, the
Option 2: If the ticket contains one asset and multiple vulnerabilities, the
Option 3: If the ticket contains multiple assets and multiple vulnerabilities, the
Option 4: If the ticket contains one vulnerability and one asset, the
| Option 1:
Option 2:
Option 3:
Option 4:
|
Soonest SLA | The date of the soonest SLA associated with the ticket, | |
Ticket Max Score | The highest max score among the vulnerability instances listed in the ticket |
|
Vulnerability Header | Option 1: If the ticket contains one vulnerability, the
Option 2: If the ticket contains two or more vulnerabilities, the |
|
Remediation Work Form Link | A remediation work form URL will be generated for the user to view vulnerability instances and their details through the remediation ticket and submit an exception request for part or all instances. |
|
SLA Policy Configuration | The details of the SLA policies associated with the vulnerabilities in the ticket
|
|
Affected Assets
| A list of the assets affected by the vulnerability
Each asset type has its own type of return value.
|
|
Affected Vendor | The name of the vendor affected by the vulnerability | |
Attack Vectors | A list of the attack vectors threat tags associated with the vulnerability
If there is no attack vector, the following will be displayed: |
|
CVEs | A list of CVEs associated with the vulnerability, including hyperlinks to the CVE details published on the National Vulnerability Database website |
|
Vulnerability CVSS Score | The CVSS score of the vulnerability |
|
CWEs | A list of CWEs associated with the vulnerability |
|
Vulnerability Description | A description of the vulnerability |
|
Exploitability List | A list of exploitability threat tags (Intelligence Threat Tags) associated with the vulnerability
|
|
High Impact Assets Tag | A list of high-impact asset tags associated with the assets in the ticket |
|
Vulnerability Max Risk Level | The highest risk level among the vulnerability instances of the unique vulnerability |
|
Vulnerability Max Score | The highest risk score among the vulnerability instances of the unique vulnerability |
|
Vulnerability Name | The name of the vulnerability |
|
Remedies | A description of the available remedies available for the vulnerability. Note: All the relevant remedies are attached in a CSV file to the ticket.
| If multiple vulnerabilities are in the same ticket, only the number of remedies is mentioned:
If only one vulnerability in the ticket, up to 10 remedies can be included in the body of the ticket:
|
Vulnerability Tags | A list of the tags associated with the vulnerability. |
|
Vulcan Link | A URL to vulnerability details on the Vulcan Platform. |
|
Ticket Parameters Availability
There are various parameters available in the ticket customization template. Some parameters can be used in specific blocks in the ticket template, while others can be used in several blocks. The table below summarizes the entire list of parameters and where they can be used in the ticket template.
Parameter | Ticket summary/ email subject | Description Header | Vulnerability repeatable block | Description Footer |
Business Groups | ✓ | ✓ |
| ✓ |
Count of Assets in Ticket | ✓ | ✓ |
| ✓ |
Count of Unique Vulnerabilities in Ticket | ✓ | ✓ |
| ✓ |
Count of Vulnerability Instances in Ticket | ✓ | ✓ |
| ✓ |
Highest Risk Level | ✓ | ✓ |
| ✓ |
One Asset Name | ✓ | ✓ |
| ✓ |
One Vulnerability Name | ✓ | ✓ |
| ✓ |
Sender Name | ✓ | ✓ |
| ✓ |
Smart Subject | ✓ | ✓ |
| ✓ |
Soonest SLA | ✓ | ✓ |
| ✓ |
Ticket Max Score | ✓ | ✓ |
| ✓ |
Vulnerability Header | ✓ | ✓ |
| ✓ |
Remediation Work Form Link |
| ✓ |
| ✓ |
SLA Policy Configuration |
| ✓ |
| ✓ |
Affected Assets
|
|
| ✓ |
|
Affected Vendor |
|
| ✓ |
|
Attack Vectors |
|
| ✓ |
|
CVEs |
|
| ✓ |
|
Vulnerability CVSS Score |
|
| ✓ |
|
CWEs |
|
| ✓ |
|
Vulnerability Description |
|
| ✓ |
|
Exploitability List |
|
| ✓ |
|
High Impact Assets Tag |
|
| ✓ |
|
Vulnerability Max Risk Level |
|
| ✓ |
|
Vulnerability Max Score |
|
| ✓ |
|
Vulnerability Name |
|
| ✓ |
|
Remedies |
|
| ✓ |
|
Vulnerability Tags |
|
| ✓ |
|
Vulcan Link |
|
| ✓ |
|