SECOPS
Sweep public S3 objects for secrets and lock down on detection
On a schedule, scans publicly readable S3 objects for embedded credentials; on a hit it makes the object private, rotates the exposed key, and files a Linear remediation ticket.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled sweep fires
- ActionList and download public S3 objectsAWS S3
- LogicBranch: exposed secret vs clean object
- ActionSet object ACL to privateAWS S3
- ActionRotate the exposed credentialShell
- OutputOpen Linear remediation ticketLinear
What it does
Periodically enumerates publicly accessible objects in your S3 buckets and scans their contents for leaked credentials, config secrets, and private keys. When it finds an exposed secret in a public object, it immediately revokes public access, rotates the leaked credential, and opens a Linear ticket so the root cause gets fixed.
When to use it
Use it when teams ship config files, backups, or build artifacts to S3 and occasionally leave them world-readable with secrets inside. This is for catching the accidental public exposure that perimeter tools miss because the bucket itself is intentionally public.
How it works
- 1A schedule trigger kicks off the sweep.
- 2The flow lists publicly readable objects and downloads candidates for scanning.
- 3It runs credential and entropy detection on each object body.
- 4A logic branch separates exposed-secret hits from clean objects.
- 5For a hit it sets the object ACL to private and rotates the leaked key via a shell step.
- 6It opens a Linear ticket with the bucket, key, and credential type for permanent remediation.
Set it up
What you configure once, before turning it on.
- 1Connect AWS S3Buckets, objects, signed URLs.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.