SECOPS
OAuth Consent Inventory Snapshot to Postgres
Takes a full point-in-time snapshot of every OAuth app grant, scope, and consenting user.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled snapshot run
- ActionEnumerate all OAuth grants and scopesOutlook
- LogicNormalize into per-app-scope-user rows
- ActionUpsert snapshot rows into PostgresPostgres
- OutputWrite run summary for trend queriesPostgres
What it does
Captures a complete, timestamped inventory of all third-party OAuth grants in your tenant and persists it to a Postgres table, building the historical record needed for drift analysis, audits, and compliance evidence.
When to use it
Use this when point-in-time alerts aren't enough and you need queryable history — to answer "which apps gained scopes since last quarter" or to produce evidence for SOC 2 / ISO access reviews. Run it on a fixed cadence so each snapshot is comparable.
How it works
- 1A schedule triggers the snapshot on a fixed interval.
- 2The flow enumerates every OAuth app grant with its scopes, consent type, and consenting users.
- 3A normalization step flattens the nested grant data into one row per app-scope-user with a run timestamp.
- 4The rows are upserted into a Postgres consent-inventory table keyed by snapshot date.
- 5The run finishes by writing a summary record (total apps, new since last run, scopes added) for quick trend queries.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.