SECOPS
Phishing Case Ticket Builder
Converts an enriched phishing report into a fully populated tracking ticket in Linear, links the original email and evidence, assigns the right responder.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires with scored, enriched reportHTTP webhook
- LogicMap verdict to priority and assignee
- ActionCreate Linear incident ticketLinear
- ActionAttach report and evidence as commentLinear
- OutputSend acknowledgment reply to reporterGmail
What it does
Closes the loop between intake and case management. It takes a triaged phishing report and creates a structured incident ticket with the verdict, indicators, affected users, and evidence links pre-filled, then routes it to the correct analyst and acknowledges the employee who reported it.
When to use it
Use this when your SOC tracks investigations as tickets and you want every phishing report to become a consistent, well-formed case without manual data entry. Removes the gap where reports get triaged but never formally tracked.
How it works
- 1A webhook from the enrichment stage fires with the scored report and verdict.
- 2A logic step maps the verdict and category to a ticket priority and the owning analyst.
- 3A Linear issue is created with title, indicators, affected recipients, and evidence links in the description.
- 4The original report and enrichment summary are attached as a comment for full context.
- 5A confirmation reply is sent to the reporting employee via Gmail, closing the acknowledgment loop.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.