SECOPS
Block source IPs in Cloudflare when a GitLab token shows anomalous use
Starting from a suspicious GitLab token event, this verifies the originating IPs are also flagged as bots in Cloudflare and, if so, adds them to a Cloudflare WAF block list…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab token-anomaly eventGitLab
- ActionExtract source IPs from anomalous token activityGitLab
- ActionCheck IP bot reputation in CloudflareCloudflare
- LogicGate: proceed only for confirmed hostile IPs
- ActionAdd IPs to Cloudflare WAF block listCloudflare
- OutputOpen Datadog incident to track containmentDatadog
What it does
This flips the usual direction: the trigger is GitLab, not Cloudflare. When GitLab reports anomalous token use — a new geo, an impossible-travel login, or a sudden burst of API calls — the flow checks whether the source IPs are already bot-flagged in Cloudflare. If they are, it concludes the token is being driven by hostile infrastructure and blocks those IPs at the Cloudflare WAF, then opens a Datadog incident to track the containment.
When to use it
Use this when GitLab anomaly detection is your earliest signal and you want to push enforcement back out to the edge automatically. It closes the loop between identity-layer anomalies and perimeter blocking without a responder copy-pasting IPs between consoles.
How it works
- 1A GitLab token-anomaly event triggers the flow.
- 2The flow extracts the source IPs from the anomalous token activity.
- 3It checks each IP's bot reputation in Cloudflare.
- 4A logic gate proceeds only for IPs confirmed as bot/hostile.
- 5Confirmed IPs are added to a Cloudflare WAF block list and a Datadog incident is opened for tracking.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect DatadogMetrics, traces, log search.
- 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.