SECOPS
Agent-triage GitLab MRs by sensitivity and log the rationale to Confluence
An agent reviews each GitLab MR's changed files, decides a sensitivity tier with a written rationale, applies the matching label.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updatedGitLab
- ActionFetch changed files + diff contextGitLab
- LogicAgent reasons risk and picks tier + rationale
- ActionApply chosen sec:: label to MRGitLab
- OutputAppend triage entry to Confluence security logConfluence
What it does
This workflow uses an agent to make a judgment call that simple path rules miss. For each new or updated MR it reads the changed files plus the diff context, reasons about the actual risk (for example, a config-only change to an auth module may be low risk while a logic change is high), assigns a `sec::*` tier with a short rationale, and records the decision in a Confluence audit log so the reasoning is reviewable later.
When to use it
Use it when rigid path matching produces too many false alarms and you want explainable, context-aware triage with a durable paper trail for compliance reviews.
How it works
- 1A GitLab MR webhook fires on open or update.
- 2The agent fetches the changed files and surrounding diff context.
- 3It reasons about real risk and selects a sensitivity tier plus a one-paragraph rationale.
- 4It applies the chosen `sec::*` label to the MR.
- 5It appends a timestamped triage entry — MR, tier, rationale — to the Confluence security log page.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.