SECOPS
Auto-revoke GitLab tokens authenticating from active Cloudflare bot IPs
On a confirmed Cloudflare bot attack, this finds GitLab tokens that just authenticated from the attacking IPs and revokes them automatically.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare confirmed-attack webhookCloudflare
- ActionFind GitLab tokens authenticated from attack IPsGitLab
- LogicGate: skip protected/service-account tokens
- ActionRevoke matching GitLab tokensGitLab
- OutputPost containment summary to SlackSlack
What it does
This is a containment automation. When Cloudflare confirms an active bot attack against your origins, it identifies any GitLab personal-access or project-access token that authenticated from the attack IPs and revokes those tokens immediately to cut the attacker off mid-incident. It then posts exactly what it killed to Slack so a human can verify and follow up.
When to use it
Reach for this when minutes matter and you have authorized automated revocation in your incident runbook. It is the right tool once you trust the correlation logic enough to let it act — for example during a confirmed, high-confidence attack — rather than just alerting and waiting for a responder.
How it works
- 1Cloudflare fires a confirmed-attack webhook with the attacking IP set.
- 2The flow queries GitLab for tokens that authenticated from those IPs in the attack window.
- 3A logic gate checks each token against a protected-token allowlist to avoid revoking critical service accounts.
- 4Non-allowlisted matching tokens are revoked via the GitLab API.
- 5A Slack message reports every token revoked, its owner, and the triggering evidence.
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 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
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.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Exposed-Secret Incident Triage and Remediation Agent
An agent-driven workflow that investigates a reported leaked secret end to end, decides revoke-versus-escalate, executes the rotation.
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.
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.