SECOPS
Daily Loom library secret audit with findings tracker
Each morning, sweeps Loom recordings published in the last 24 hours for exposed secrets and logs every finding to a Linear-tracked queue with severity and owner.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionList Loom recordings from last 24hLoom
- ActionScan transcript and frames for secretsOpenAI
- LogicAssign severity by secret type
- ActionCreate Linear finding per leakLinear
- OutputPost daily findings digest to SlackSlack
What it does
This scheduled audit catches anything the real-time webhook missed (older videos re-shared, backfilled libraries, recordings published while a webhook was down). It lists the last day's Loom recordings, scans each for credentials, and files structured findings so security can work a queue rather than chase pings.
When to use it
Use this as the safety net beneath a real-time scanner, or as a standalone control if you'd rather batch-review once a day. Ideal for teams that need an auditable paper trail of who leaked what and whether it was triaged.
How it works
- 1A daily schedule triggers the audit.
- 2The flow lists all Loom recordings published in the last 24 hours.
- 3Each recording's transcript and frame text is fetched and scanned for secret patterns.
- 4A logic step assigns severity by secret type (live API key = high, internal URL = low).
- 5For each finding, a Linear issue is created with the recording link, secret type, severity, and the recording's owner pre-assigned.
- 6A summary digest of all findings is posted to Slack so the team sees the day's volume at a glance.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
Scheduled AWS Access-Key Age Sweep and Forced Rotation
Runs daily to find IAM access keys older than your policy threshold, deactivates the stale key, issues a fresh pair, and notifies the key owner with their replacement instructions.
Correlate Datadog WAF anomaly alert with Cloudflare evidence
When Datadog fires a WAF block-rate anomaly monitor, it pulls the matching Cloudflare firewall events, builds an evidence pack of top rules and ASNs.
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.
Non-Rotatable Leaked Secret to PagerDuty Escalation
Catches secret-scan hits for credentials that cannot be auto-rotated, gathers blast-radius context, and pages the on-call engineer with a step-by-step manual rotation runbook.
GitHub Secret-Scan Hit to Auto-Revoke and Rotate
When GitHub secret scanning flags a leaked credential in a repo, it auto-classifies the secret type, revokes the live key at the provider, mints a replacement.
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
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.