SECOPS
AI investigation of audit anomalies into a Confluence report
When an audit anomaly webhook fires, an agent gathers context from Cloudflare and Datadog audit logs, reasons about whether the actor's actions form a coherent attack pattern.
How it runs
The automated pipeline, trigger to output.
- TriggerAnomaly webhook receivedHTTP webhook
- ActionFetch actor's recent Cloudflare audit historyCloudflare
- ActionFetch actor's recent Datadog audit eventsDatadog
- LogicCorrelate timeline and classify intent
- OutputPublish investigation report to ConfluenceConfluence
What it does
Given a single flagged anomaly, this agent pulls the surrounding audit history across Cloudflare and Datadog, correlates the actor's behavior into a timeline, assesses intent (misconfiguration vs. likely malicious), and publishes a written investigation to Confluence — turning a raw alert into a reviewable narrative.
When to use it
Use it when a flagged anomaly needs more than a one-liner: you want the surrounding 24-hour activity, cross-system correlation, and a plain-language verdict documented for the incident record or a later audit.
How it works
- 1A webhook receives an anomaly payload (actor, action, timestamp) from an upstream detector.
- 2The agent fetches that actor's recent Cloudflare audit entries for context.
- 3The agent fetches the same actor's Datadog audit events to correlate cross-platform activity.
- 4It reasons over the combined timeline, classifying the pattern and assigning a confidence level.
- 5It drafts a structured report: summary, timeline, indicators, and recommended next step.
- 6The report is published as a new Confluence page under the security investigations space and linked back in the response.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.