SECOPS
Datadog audit-event spike to PagerDuty escalation
Watches the Datadog audit trail for bursts of sensitive admin events (user role grants, API key creation, monitor deletions) and, when a burst crosses threshold, opens…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 minutes (scheduled)
- ActionQuery Datadog audit events for recent windowDatadog
- LogicGroup by actor and count sensitive actions
- LogicBranch: any actor over burst threshold?
- OutputOpen PagerDuty incident with burst summaryPagerDuty
What it does
It continuously evaluates the Datadog audit event stream, detects when a single actor performs an unusual burst of privileged actions in a short window, and escalates that burst as a PagerDuty incident so on-call can intervene before damage spreads.
When to use it
Reach for this when a compromised or rogue Datadog admin is your concern — for example mass role grants, bulk monitor deletions, or rapid API key minting. It turns 'noticed it next morning' into 'paged within minutes.'
How it works
- 1A scheduled trigger runs every 5 minutes.
- 2The flow queries the Datadog audit events API for the recent window.
- 3Events are grouped by actor and counted against per-action thresholds (e.g. 3+ role grants or any monitor deletion).
- 4A decision step checks whether any actor's burst crosses the threshold.
- 5If clear, the run ends quietly; if a spike is found, it builds an incident summary with actor, action counts, and timestamps.
- 6A PagerDuty incident is created at the matching severity and assigned to the security on-call schedule.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.