SECOPS
Public Paste Credential Sweep and Owner Hunt
On a schedule, an agent searches the public web for leaked credentials tied to your domains, identifies the owning service from the secret's prefix.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily sweep schedule
- ActionSearch public web for leaked secretsExa
- LogicDiscard false positives and expired tokens
- ActionOpen issue per confirmed leakGitHub
- ActionPage owning service on-callPagerDuty
- OutputPost leak roll-up to security channelSlack
What it does
Proactively hunts for your organization's secrets exposed in public pastes, gists, and code. An agent reasons over each hit to figure out which internal service the credential belongs to, confirms it's genuinely yours, and orchestrates rotation end to end rather than just reporting a URL.
When to use it
Use it as a daily perimeter sweep alongside reactive GitHub scanning, to catch secrets leaked outside repos you control. Best when secrets carry identifiable prefixes (for example `sk_live_`, internal token namespaces) the agent can attribute to a service.
How it works
- 1A daily schedule triggers the sweep.
- 2The agent runs targeted web searches for your domains, token prefixes, and service identifiers.
- 3It fetches and inspects candidate pages, discarding false positives and already-expired tokens.
- 4For each confirmed leak, it attributes the secret to its owning service using prefix and naming conventions.
- 5It opens a GitHub issue per confirmed leak with the source URL and the attributed service.
- 6It pages the owning service's on-call so rotation starts immediately.
- 7It posts a roll-up of all confirmed leaks and their owners to the security Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ExaNeural search across the web.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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
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.