SECOPS
Daily Lookalike Domain Sweep into Linear
Runs a scheduled Brave Search sweep for typosquat and lookalike variants of your brand, scores each hit for impersonation risk.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the sweep
- ActionBrave Search for lookalike domain permutationsBrave Search
- LogicScore impersonation risk and drop known/low-risk hits
- ActionCreate a triage ticket per candidate in LinearLinear
- OutputPost run summary to SlackSlack
What it does
Every morning this workflow hunts the open web for domains that imitate your brand — common typos, character swaps, and added keywords like "login" or "support" — then turns the suspicious ones into actionable Linear tickets so your secops team can start takedown prep.
When to use it
Use it when you want continuous, hands-off monitoring for brand-impersonation domains without a paid threat-intel feed. Ideal for security teams that already triage work in Linear and want a steady, deduplicated queue rather than noisy alerts.
How it works
- 1A daily schedule fires the run at a fixed hour.
- 2A Brave Search action queries a generated list of lookalike permutations of your brand name and domain.
- 3A logic step scores each result on signals like edit distance to your real domain, presence of phishing keywords, and recency, then filters out low-risk and already-known hits.
- 4For each surviving candidate, a Linear action creates a ticket pre-filled with the domain, risk score, and evidence snippet.
- 5The output posts a one-line run summary so the team knows the sweep completed and how many tickets were opened.
Set it up
What you configure once, before turning it on.
- 1Connect Brave SearchWeb, news, image, video search.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.
