Collect Palo Alto Prisma Cloud alert logs

Overview

This parser extracts alert logs from Palo Alto Prisma Cloud in JSON format, transforming them into the UDM. The parser performs data normalization, type conversions, and conditional logic to populate the appropriate UDM fields. It also handles nested JSON structures and arrays within the log data to extract relevant information.

Before you begin

• Ensure that you have a Google SecOps instance.
• Ensure that you have privileged access to Palo Alto Prisma Cloud.

Configure a feed in Google SecOps to ingest Palo Alto Prisma Cloud Alerts

1. Go to SIEM Settings > Feeds.
2. Click Add new.
3. In the Feed name field, enter a name for the feed (for example, PAN Prisma Cloud Alerts).
4. Select Webhook as the Source type.
5. Select Palo Alto Prisma Cloud Alerts payload as the Log type.
6. Click Next.
7. Optional: Specify values for the following input parameters:
   • Split delimiter: the delimiter that is used to separate log lines, such as \n.
   • Asset namespace: the asset namespace.
   • Ingestion labels: the label applied to the events from this feed.
8. Click Next.
9. Review the feed configuration in the Finalize screen, and then click Submit.
10. Click Generate Secret Key to generate a secret key to authenticate this feed.
11. Copy and store the secret key. You cannot view this secret key again. If needed, you can regenerate a new secret key, but this action makes the previous secret key obsolete.
12. From the Details tab, copy the feed endpoint URL from the Endpoint Information field. You need to specify this endpoint URL in your client application.
13. Click Done.

Create an API key for the webhook feed

1. Go to Google Cloud console > Credentials.

   Go to Credentials

2. Click Create credentials, and then select API key.

3. Restrict the API key access to the Google Security Operations API.

Specify the endpoint URL

1. In your client application, specify the HTTPS endpoint URL provided in the webhook feed.

2. Enable authentication by specifying the API key and secret key as part of the custom header in the following format:

   X-goog-api-key = API_KEY
   X-Webhook-Access-Key = SECRET
   

   Recommendation: Specify the API key as a header instead of specifying it in the URL.

3. If your webhook client doesn't support custom headers, you can specify the API key and secret key using query parameters in the following format:

   ENDPOINT_URL?key=API_KEY&secret=SECRET
   

   Replace the following:

   • ENDPOINT_URL: the feed endpoint URL.
   • API_KEY: the API key to authenticate to Google Security Operations.
   • SECRET: the secret key that you generated to authenticate the feed.

Configure Palo Alto Prisma Cloud webhook to Google SecOps

1. Sign in to Palo Alto Prisma Cloud.
2. Select Settings > Integrations & Notification ((and_then)) Integrations.
3. Click Add Integration.
4. Select Webhook.
5. Specify values for the following input parameters:
   • Integration Name: Provide a unique and descriptive name (for example, Google SecOps)
   • Webhook URL: Enter the ENDPOINT_URL.
   • Optional: Provide a Description of the integration.
   • Optional: Enable Custom Payload > click Next to review or revise the custom payload.
6. Click Next.
7. Test and Save Integration.

Configure Palo Alto Prisma Cloud Alerts

1. In the Palo Alto Prisma Cloud console, go to Alerts > View Alert Rules.
2. Select an existing alert rule to edit.
3. Optional: Create new Alert for Cloud Infrastructure.
4. Optional: Create new Alert for Cloud Workload.
5. Go to Configure Notifications.
6. Select Webhook.
7. Optional: Select the Channels that you want to send notifications of alerts triggered by the alert rule.
8. Click Next.
9. Click Save.

UDM Mapping Table

Changes

2023-12-10

• Added a Grok pattern to extract JSON part.
• Mapped "resourceId" to "principal.resource.product_object_id".
• Mapped "accountId" to "target.resource.product_object_id".
• Mapped "alertRuleName" to "security_result.rule_name".
• Mapped "accountName" to "target.resource.name".
• Mapped "hasFinding" to "security_result.detection_fields".
• Mapped "resourceRegionId" to "principal.cloud.availability_zone".
• Mapped "source" to "principal.application".
• Mapped "callbackUrl" to "metadata.url_back_to_product".
• Mapped "alertRuleId" to "security_result.rule_id".
• Mapped "alertId" to "security_result.detection_fields".
• Mapped "policyLabels" to "additional.fields".
• Mapped "policyName" to "security_result.description".
• Mapped "resourceName" to "principal.resource.name".
• Mapped "resourceRegion" to "principal.location.country_or_region".
• Mapped "policyDescription" to "security_result.detection_fields".
• Mapped "policyRecommendation" to "security_result.detection_fields".
• Mapped "resourceCloudService" to "principal.resource.attribute.labels".
• Mapped "resource.url" to "principal.url".
• Mapped "alertTs" to "security_result.detection_fields".
• Mapped "firstSeen" to "principal.asset.first_seen_time".
• Mapped "lastSeen" to "principal.asset.last_discover_time".
• Mapped "reason" to "security_result.summary".
• Mapped "alertStatus" to "security_result.detection_fields".
• If "severity" value is "HIGH", set "security_result.severity" to "HIGH".
• If "cloudType" value is "gcp", set "principal.cloud.environment" to "GOOGLE_CLOUD_PLATFORM".

2023-08-17

• Newly created parser.