SECOPS
Daily sweep for leaked keys across logs and revoke matches
On a daily schedule, this workflow scans recent log exports for credential patterns, revokes any matched GitHub tokens, and files findings in a Notion incident register.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the sweep
- ActionPull latest log export from S3 and scan for patternsAWS S3
- LogicFilter to high-confidence GitHub token matches
- ActionRevoke each matched token in GitHubGitHub
- ActionAppend findings to Notion incident registerNotion
- OutputSend daily found-and-revoked digest to SlackSlack
What it does
Runs a proactive daily sweep instead of waiting for an alert. It scans recent log exports for credential patterns, and for any confirmed GitHub token match it revokes the credential and records the finding in a Notion register so nothing slips through silently.
When to use it
Use this when secrets leak into application logs, debug output, or exported telemetry that secret scanning never sees. A scheduled sweep catches the exposures that live outside your source control.
How it works
- 1A daily schedule triggers the sweep.
- 2The workflow pulls the latest log export from S3 and scans it for credential patterns.
- 3A filter keeps only high-confidence matches that map to known GitHub token formats.
- 4For each match it revokes the token in GitHub.
- 5It appends a row to a Notion incident register with the source, match, and revocation result.
- 6A Slack digest summarizes how many keys were found and revoked that day.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.