SECOPS
Phishing Mailbox Triage and Intake
Watches a shared phishing-report mailbox, parses each reported email, scores its risk.
How it runs
The automated pipeline, trigger to output.
- TriggerNew email in phishing-report mailboxGmail
- ActionParse headers, sender, subject, and URLs
- LogicScore risk: low / medium / high
- LogicBranch high+medium to triage, low to digest
- OutputPost triage card to SOC Slack channelSlack
What it does
Turns a noisy `phishing@company` reporting inbox into a clean, scored queue. Every forwarded suspicious email is parsed, classified by initial risk, and posted as a structured triage card to the SOC Slack channel with reporter, subject, sender domain, and any URLs found.
When to use it
Run this when employees forward suspect emails to a shared mailbox and analysts waste time opening each one by hand. Best for teams that want a single front door for phishing reports with consistent, auditable intake.
How it works
- 1A new message arriving in the monitored Gmail label fires the trigger.
- 2The body and headers are parsed to pull the original sender, subject, reporting employee, and embedded links.
- 3A scoring step flags high-risk signals such as lookalike domains, urgent language, and credential-form links, assigning low / medium / high.
- 4A branch routes high and medium reports to immediate triage and low reports to a digest list.
- 5A formatted triage card is posted to the SOC Slack channel with all extracted fields and the assigned score.
Set it up
What you configure once, before turning it on.
- 1Connect GmailRead, draft, send, label.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.