SECOPS
Credential-in-Logs Detection to Service Correlation
When Datadog detects a secret pattern in application logs, this workflow correlates the leaking log source to its service and team.
How it runs
The automated pipeline, trigger to output.
- TriggerDatadog sensitive-data scanner alertDatadog
- ActionExtract service, env, and host tagsDatadog
- LogicSet priority by environment
- ActionFile remediation ticketLinear
- OutputAlert owning team channelSlack
What it does
Catches secrets that slip into application logs and routes them to whoever owns the noisy service. It uses the log's service and host tags to identify the responsible team, files a remediation ticket, and surfaces it in the right channel so the leak is scrubbed and the secret rotated.
When to use it
Use it when you ship a Datadog Sensitive Data Scanner rule for credential patterns and want each hit to become an owned engineering task instead of an alert nobody actions. Good for catching accidental `print(token)` style leaks.
How it works
- 1A Datadog monitor alert fires when the sensitive-data scanner matches a credential pattern in logs.
- 2The flow extracts the service, environment, and host tags from the alert payload.
- 3It branches: production-tagged leaks are marked urgent, while staging hits are filed as normal priority.
- 4It creates a Linear issue describing the leaking log line, service, and rotation requirement.
- 5It posts to the owning team's Slack channel with the ticket link and a redaction reminder.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.