Ingest detection and compliance findings and audit logs from Palo Alto Prisma Cloud into Dynatrace. Dynatrace enriches the findings with the cloud entities it monitors, so you can prioritize risks that affect your production workloads.
The Dynatrace integration with Palo Alto Prisma Cloud lets you unify and contextualize cloud security findings and audit activity across your DevSecOps tools and products. The integration provides central prioritization, visualization, and automation of security findings.
The integration ingests incident and risk alerts from Prisma Cloud as detection and compliance finding events. Dynatrace enriches them with the cloud entities it monitors and makes them available in dashboards, apps, and workflows.
The integration helps security teams investigate detections faster and review security posture and compliance more efficiently. The integration also helps security teams connect security findings with monitored environments and prioritize and assess risk.
With the ingested data, you can address use cases such as
To use this integration, make sure you have:
https://api.prismacloud.io or https://api2.eu.prismacloud.io)ActiveGate that must:
Recommended Use the Dedicated limits option for the performance profile. For details, see ActiveGate performance profile configuration.
For required permissions, open Hub, select
Extensions, then go to the Technical information tab.
Generate an access token with the openpipeline.events_security scope and save it for later. For details, see Dynatrace API - Tokens and authentication.
In Dynatrace, open Hub.
Look for Palo Alto Prisma Cloud and select Install.
Follow the instructions to configure the extension.
To verify the configuration, run the following queries in
Notebooks:
For detection finding events:
fetch security.events| filter event.provider == "Palo Alto Prisma Cloud"AND event.type == "DETECTION_FINDING"
For compliance finding events:
fetch security.events| filter event.provider == "Palo Alto Prisma Cloud"AND event.type == "COMPLIANCE_FINDING"
For audit logs:
fetch logs| filter log.type == "pan-prisma-cloud-audit-logs"
After installation, you can access and manage the extension in
Extensions. For details, see About Extensions.

The integration runs as an extension on Dynatrace ActiveGate. After you install and configure the Prisma Cloud extension:
default_securityevents bucket (for details, see Built-in Grail buckets).For billing information, see Events powered by Grail.
The integration ingests security events from Prisma Cloud Enterprise Edition.
The integration ingests alerts from Prisma Cloud based on the configured ingestion options:
m days, where m is set by the Security events initial fetch time window option in the monitoring configuration.n minutes, where n is set by the Security events ingest frequency option in the monitoring configuration.p minutes, where p is set by the Audit logs ingest frequency option. The first run starts from the current time.The prisma namespace is added for Prisma Cloud-specific attributes on top of the core security event schema. The full upstream payload is stored in event.original_content.
Fields added to findings include:
prisma.policy.id: Prisma Cloud policy identifierprisma.policy.category: Policy category (for example, incident or risk)prisma.policy.type: Policy type (for example, anomaly, config, or audit_event)prisma.policy.class: Policy classprisma.policy.mode: Policy modeprisma.rule.type: Rule type from the policyprisma.alert.reason: Alert reason (for example, NEW_ALERT)prisma.finding.types: Finding types reported by the policyDynatrace normalizes severity and risk scores for all findings ingested through this integration. Normalization helps you prioritize findings consistently, regardless of their source. For details, see Severity and score normalization.
dt.security.risk.level is mapped from the Prisma Cloud policy severity returned by the Alerts and Policy APIs. finding.severity keeps that Prisma severity string.
dt.security.risk.score is derived from that severity using the standard Dynatrace static severity-to-score mapping.
dt.security.risk.level (mapped from finding.severity) | dt.security.risk.score (mapped from finding.score) |
|---|---|
critical → CRITICAL | 10.0 |
high → HIGH | 8.9 |
medium → MEDIUM | 6.9 |
low → LOW | 3.9 |
other → NONE | 0.0 |