Alert Features

Alert Popup

The popup that appears on clicking the alert gives a detailed summary of the security issue.

  • Rule Description: This gives a detailed description of the identified alert.

  • Violation: This explains the impact of the alert on the repo.

On clicking Impacted Components, the complete details of the components that are impacted by the security issue are displayed.

It displays the following details related to the components:

  • Application - Displays the application name in which the alert was identified.

  • Service - Displays the service name of the application.

  • Artifact - Displays the artifact name in which the application was deployed.

  • Life Cycle Stage - Displays in which stage the alert was deducted.

  • Deployed To - Displayed the cluster name in which the application is deployed.

  • First Seen - Displays the timestamp on when the alert was found initially.

  • View Jira Ticket - Displays the JIRA ticket that was created to resolve the alert.

  • Exception - Displays the exceptions that were created for the alert.

Actions on Alerts

Various actions can be performed on the displayed alerts. The options are displayed at the bottom of the alert popup page. The different actions that can be performed on the displayed alerts are as follows:

JIRA Automation

JIRA tickets are automatically created and also can be manually created for the Security Issues. If the security issue is of Critical or High severity, the Jira is automatically created and for other severities you can create manually by using the Create Jira Ticket option in the Security Issue details popup.

Creating JIRA Ticket

The JIRA tickets can be created at the alert level and component level.

At Alert Level:

To create JIRA tickets at Alert level; follow the steps given below:

  • Click on the Alert for which you want to create a JIRA ticket. The Alert details popup is displayed as shown below:

  • Click Create JIRA Ticket. A popup is displayed.

  • Click Create.

  • A JIRA is created and displayed as shown below:

At Impacted Component Level:

To create JIRA tickets at Impacted component level; follow the steps given below:

  • Expand the Show impacted components drop down. The list of all the components impacted by the selected alert are displayed.

  • Click the additional options menu (three dots).

  • Click the Create Jira Ticket option.

  • A Jira ticket is created and listed in the View Jira Ticket column as shown below:

When a ticket is created for an alert using the Create JIRA Ticket option, a corresponding ticket is created in the JIRA application.

If the ticket is resolved in the JIRA application, the corresponding ticket in the alert popup is resolved by default and likewise.

If the vulnerability is of Critical or High severity, the Jira is automatically created by default and the ticket number is displayed as a tab as shown below:

You can click the View SSD-2880 tab to view the ticket details.

If the JIRA ticket created at the Alert level is resolved, all the JIRA tickets create at the component level are also resolved by default.

Resolve Alert

The alerts displayed in the supply chain details page can be resolved. You can resolve the alert by following the steps provided below:

  • Click Resolve Alert from the options displayed in the popup on clicking the alert.

  • Another pop up is displayed.

  • Enter the comments for resolving the alert and click Resolve.

  • The alert is resolved. It becomes inactive and is removed from the active alert lists.

Send to Slack

The alerts that are notified in the application can be shared through slack. The slack channel to which you want to send the alert can be configured and thus the alert is shared to the respective channel.

  • Click Send to Slack from the options displayed in the popup on clicking the alert.

  • An alert is sent to the configured slack channel and a success message is displayed.

PreviousView Open Security IssuesNextManage Policies

Last updated

Was this helpful?