SECOPS
Dropbox Exposure Metrics to Datadog
Counts external Dropbox shares by team, sensitivity tier, and age on a schedule and emits the totals as Datadog metrics so exposure trends and SLA breaches are graphable…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly metrics schedule
- ActionPull Dropbox shared links and membersDropbox
- LogicAggregate by team, tier, and link age
- OutputEmit tagged exposure metrics to DatadogDatadog
What it does
This turns Dropbox sharing posture into observable telemetry. On a recurring schedule it tallies how many external links exist, breaks them down by owning team, sensitivity tier, and how long they have been open, and ships those counts to Datadog as custom metrics you can chart, threshold, and monitor like any other production signal.
When to use it
Use this when leadership or compliance wants trend lines instead of one-off reports, and when you want Datadog monitors to fire if external exposure crosses a budget or a stale link ages past its remediation SLA.
How it works
- 1An hourly schedule starts the metric collection.
- 2Dropbox returns current shared links and member lists for the team.
- 3A logic step aggregates counts by team, sensitivity tier, and link age buckets.
- 4Datadog ingests each aggregate as a tagged custom metric.
- 5The same step emits an SLA-breach gauge for links older than the remediation window, ready for Datadog monitors.
Set it up
What you configure once, before turning it on.
- 1Connect DropboxFiles and folders.
- 2Connect DatadogMetrics, traces, log search.
- 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.