SECOPS
Weekly Cross-Cloud Exposure Report to Snowflake
Audits both Dropbox and Google Drive weekly for public-link exposures, loads a normalized findings table into Snowflake for trend analysis, and posts an executive summary to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts cross-cloud audit
- ActionPull public files from DropboxDropbox
- ActionPull public files from Google DriveGoogle Drive
- LogicMerge and normalize findings
- ActionUpsert findings into Snowflake history tableSnowflake
- OutputPost executive trend summary to SlackSlack
What it does
Produces a unified weekly view of external file exposure across both Dropbox and Google Drive. It collects every publicly shared file from both clouds, normalizes them into one schema, lands the dataset in Snowflake so you can chart exposure trends over time, and sends leadership a concise Slack summary of the week's risk posture.
When to use it
Use this when you store files in more than one cloud and need a single source of truth for exposure metrics — for board reporting, audit evidence, or tracking whether your remediation efforts are actually reducing public shares quarter over quarter.
How it works
- 1A weekly schedule kicks off the cross-cloud audit.
- 2The flow pulls public/anyone-with-link files from Dropbox and from Google Drive in parallel.
- 3Results are merged and normalized into a common findings shape (source, owner, file, link, risk score).
- 4The normalized rows are upserted into a Snowflake exposure-history table.
- 5A logic step computes week-over-week deltas (new, resolved, still-open).
- 6An executive summary with the key counts and trend is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect Google DriveDocs, sheets, slides, files.
- 3Connect SnowflakeWarehouses, queries, shares.
- 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
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.