End-of-Life (EoL)

ServiceNow alerts

ServiceNow is a workflow management platform. It offers a number of security operations applications. You can configure Prisma Cloud to route alerts to ServiceNow’s Security Incident Response application.
Prisma Cloud audits are mapped to a ServiceNow security incident as follows:
  • Audits and incidents are mapped to individual ServiceNow security incidents.
  • Vulnerabilities are aggregated by resource (currently image) and mapped to individual ServiceNow security incidents. ServiceNow short description fields list the resource. ServiceNow long description fields list the details of each finding.
ServiceNow security incident
Field description
Prisma Cloud audit data
The current state of the security incident. Upon security incident creation, this field defaults to Draft.
Draft (automatically set by ServiceNow)
Select the order in which to address this security incident, based on the urgency. If this value is changed after the record is saved, it can affect the Business impact calculation.
Vulnerabilities: Max severity from the image’s new vulnerabilities. ServiceNow’s priorities map one-to-one to Prisma Cloud priorities (Critical - Critical, High - High, Medium - Medium, Low - Low).
Incidents and audits: runtime audits priority set in the alert profile.
Business impact
Select the importance of this security incident to your business. The default value is Non-critical. If, after the security incident record has been saved, you change the value in the Priority and/or Risk fields, the Business impact is recalculated.
Automatically calculated by ServiceNow
Assignment group
The group to which this security incident is assigned.
Assignment group set in the alert profile
Assigned to
The individual assigned to analyze this security incident.
Assignee set in the alert profile
Short description
A brief description of the security incident.
Vulnerabilities: Prisma Cloud Compute vulnerabilities for image <image name> Compliance: Prisma Cloud Compute compliance issues for image/container/host <image/container/host name> Incidents and audits: Prisma Cloud Compute audit - <audit type>
Set to "None"
Set to "None"
  • CVEs IDs list (with each CVE’s details)
  • Project
  • Collections
  • Summary of compliance issues count by severity
  • Compliance issues list (with each issue’s details)
  • Project
  • Collections
Incidents and audits:
  • Description: <audit description>
  • Related resource: <resource name>
  • Project: <Project>
  • Time created: <audit creation date>
  • Then add all the other fields this type of Incident/Audit has
Note that the
field will specify
Central Console
even when projects aren’t enabled.

Configuring alert frequency

You can configure the rate at which alerts are emitted. This is a global setting that controls the spamminess of the alert service. Alerts received during the specified period are aggregated into a single alert. For each alert profile, an alert is sent as soon as the first matching event is received. All subsequent alerts are sent once per period.
  1. Open Console, and go to
    Manage > Alerts
  2. In
    Aggregate audits every
    , specify the maximum rate that alerts should be sent.
    You can specify

Sending findings to ServiceNow

Alert profiles specify which events trigger the alert machinery, and to which channel alerts are sent. You can send alerts to any combination of channels by creating multiple alert profiles.
Alert profiles consist of two parts:
(1) Alert settings — Who should get the alerts, and on what channel?
Configure Prisma Cloud to integrate with ServiceNow and specify the people or places where alerts should be sent. You can specify assignees and assignment groups.
(2) Alert triggers — Which events should trigger an alert to be sent?
Specify which of the rules that make up your overall policy should trigger alerts.

Create new alert profile

Create a new alert profile.
  1. In
    Manage > Alerts
    , click
    Add profile
  2. Enter a name for your alert profile.
  3. In
    , select

Configure the channel

Configure Prisma Cloud to send alerts to ServiceNow, then validate the setup by sending a test alert.
You’ve created a service account in ServiceNow with a base role of web_service_admin.
  1. In
    , select
    Security Incident Response
  2. In
    , specify the base URL of your ServiceNow tenant.
  3. In
    , click
    Add New
    1. In
      , select
      Basic authentication
      This is currently the only auth method supported.
    2. Enter a username and password.
  4. (Optional) In
    , enter the name of a user in ServiceNow that will be assigned the security incident.
    This value isn’t case sensitive.
  5. (Mandatory) In
    Assignment Group
    , enter the name of a group in ServiceNow that will be assigned the security incident. The default value is
    Security Incident Assignment
    Assignment Group
    is set without speciying
    , the first user from the group is set on the security incident (ServiceNow’s logic).
    If the
    set in the profile isn’t a part of the
    Assignment Group
    , the security incident won’t be created (ServiceNow’s logic).
  6. (Optional) In
    CA certificate
    , enter a CA certificate in PEM format. Relevant only for on-premises deployments of ServiceNow.
  7. Click
    Send Test Alert
    . If everything looks good, and you get an alert in ServiceNow, save the profile.

Configure the triggers

Configure how the alert is triggered.
  1. Under
    Alert Types
    , check the boxes types of events that should trigger an alert.
  2. For additional configuration options, click
  3. To specify specific rules that should trigger an alert, deselect
    All rules
    , and then select any individual rules.
  4. Click

Recommended For You