SECOPS
Daily exposure digest of GitLab tokens seen on Cloudflare bot IPs
Once a day this summarizes which GitLab tokens authenticated from any Cloudflare bot-flagged IP over the prior 24 hours and emails security leadership a prioritized exposure…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionQuery Cloudflare bot-flagged IPs (last 24h)Cloudflare
- ActionCross-reference GitLab token authenticationsGitLab
- LogicDedupe by token/owner and rank by scope
- OutputEmail prioritized exposure digestGmail
What it does
This produces a daily executive-readable digest of credential exposure. It looks back over 24 hours of Cloudflare bot-flagged IPs, finds every GitLab token that authenticated from one of them, deduplicates by token and owner, ranks by token scope and access breadth, and emails a clean summary to security leadership with a recommended rotation list.
When to use it
Use this for routine hygiene and reporting rather than live response. It gives leadership a daily pulse on which credentials brushed against hostile infrastructure and which engineers need to rotate tokens — useful for audit trails and for driving rotation campaigns without paging anyone.
How it works
- 1A daily schedule triggers the digest run.
- 2The flow queries Cloudflare for bot-flagged IPs over the last 24 hours.
- 3It cross-references GitLab token authentications against that IP set.
- 4A logic step deduplicates by token and owner and ranks by scope and exposure.
- 5A formatted exposure digest with recommended rotations is emailed to security leadership via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect GmailRead, draft, send, label.
- 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.