SECOPS
Agent-triaged incident brief from Cloudflare and GitLab token signals
When a Cloudflare bot spike correlates to GitLab token activity, an agent gathers context from both systems.
How it runs
The automated pipeline, trigger to output.
- TriggerBot-spike to token-activity correlation webhookHTTP webhook
- ActionAgent pulls Cloudflare attack profileCloudflare
- ActionAgent pulls GitLab token scopes and recent actionsGitLab
- LogicAgent reasons over blast radius and sets severity
- OutputFile triage brief as Linear security incidentLinear
What it does
This turns raw cross-system signals into a decision-ready incident brief. An agent pulls the Cloudflare attack details and the matching GitLab token history, reasons over what the token can access and what the actor actually did, and produces a human-readable narrative: what happened, blast radius, severity, and recommended containment steps. The brief is filed as a Linear issue so the security team starts triage with context instead of raw logs.
When to use it
Use this when your responders waste the first 20 minutes of every incident stitching together dashboards. It is best for teams who want judgment and narrative — not just a row of matched IPs — and who track security work in Linear.
How it works
- 1A correlation webhook fires when bot-spike and token activity overlap.
- 2The agent queries Cloudflare for the attack profile (volume, ASN, paths hit).
- 3The agent queries GitLab for the token's scopes, owner, and recent actions.
- 4It reasons over blast radius and assigns a severity with justification.
- 5The finished triage brief is filed as a Linear security incident with severity and next steps.
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 LinearIssues, projects, cycles, triage.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.