SECOPS
Daily Google Drive Public-Link Exposure Sweep
Scans Google Drive each morning for files shared via "anyone with the link" or public access, flags ones containing sensitive keywords.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the sweep
- ActionList recent Drive files and fetch permissionsGoogle Drive
- LogicKeep only public / anyone-with-link files
- LogicScore files against sensitive-keyword list
- OutputPost ranked exposure digest to SlackSlack
What it does
Runs a scheduled audit of your Google Drive every morning, finding every file whose sharing permission is set to "anyone with the link" or fully public. It filters those down to files whose names or content suggest sensitive material (contracts, payroll, credentials, customer data) and delivers a ranked digest to a Slack security channel so nothing externally exposed goes unnoticed.
When to use it
Use this when your team relies on Google Drive for daily work and link-sharing has crept out of control. It is the lightweight, read-only first line of defense before you wire up automated revocation — perfect for an early security program that needs visibility without blocking anyone's workflow.
How it works
- 1A daily schedule fires the sweep at a fixed hour.
- 2The flow lists recently modified Drive files and pulls each file's permission set.
- 3A filter keeps only files exposed via public or anyone-with-link access.
- 4A second filter scores each exposed file against a sensitive-keyword list to rank true risk.
- 5The ranked findings are formatted into a digest and posted to the security Slack channel with direct file links.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 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.