Webhook alerts

Prisma Cloud offers native integration with a number of services, including email, JIRA, and Slack. When no native integration is available, webhooks provide a mechanism to interface Prisma Cloud’s alert system with virtually any third party service.
A webhook is an HTTP callback. When an event occurs, Prisma Cloud notifies your web service with an HTTP POST request. The request contains an JSON body that you configure when you set up the webhook. A webhook configuration consists of:
  • URL
  • Custom JSON body
  • Credentials
  • CA Certificate

Custom JSON body

You can customize the body of the POST request with values of interest. The content of the JSON object in the request body is defined using predefined macros. For example:
{ "type":#type, "host":#host, "details":#message }
When an event occurs, Prisma Cloud replaces the macros in your custom JSON with real values, and then submits the request.
{ "type":"ContainerRuntime", "host":"host1", "details":"/bin/cp changed binary /bin/busybox MD5:XXXXXXX" }
All supported macros are described in the following table. Not all macros are applicable to all alert types.
Rule
Description
Audit alert type. For example, 'Container Runtime'.
Audit alert time. For example, 'Jan 21, 2018 UTC'.
Impacted container.
Impacted image.
The ID of the impacted image. For example 'sha256:13b66b487594a1f2b75396013bc05d29d9f527852d96c5577cc4f187559875d0'.
The tags of the impacted resource.
Hostname for the host where the audit occurred.
Fully qualified domain name for the host where the audit occurred.
Serverless function where the audit occurred.
Region where the audit occurred. For example 'N. Virginia'.
The cloud provider in which the alert was detected. For example 'aws'.
The OS on which the alert occurred. For example 'stretch'.
The OS distro on which the alert occurred. For example 'Debian GNU/Linux 9'.
Language runtime in which the audit occurred. For example, 'python3.6'.
Serverless or Function name.
Rule which triggered the alert.
Associated alert message.
All fields in the audit message as a single JSON object.
All subsequent alerts that occurred during the aggregation period, in JSON format.