SECOPS
Stale OAuth App Grant Cleanup Reviewer
An agent reviews your OAuth grant inventory for apps with no recent sign-in activity, drafts a per-app recommendation to keep or revoke.
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly cleanup schedule fires
- ActionPull grants plus last-activity dataOutlook
- LogicFlag stale grants and weigh revoke risk
- LogicDraft keep-or-revoke recommendation per app
- OutputPost cleanup plan to Teams for sign-offMicrosoft Teams
What it does
Finds OAuth applications that still hold active grants but show no recent usage, reasons about whether each is safe to revoke, and presents a consolidated cleanup recommendation for an administrator to approve.
When to use it
Use this for periodic access hygiene — trimming the long tail of abandoned app connections that accumulate as employees trial tools and move on. Best when you want judgment on borderline apps, not just a mechanical list.
How it works
- 1A schedule kicks off the quarterly cleanup review.
- 2The agent pulls the OAuth grant inventory plus each app's last sign-in / token activity from the tenant.
- 3It flags grants idle past the staleness window and weighs scope risk, publisher trust, and user count for each.
- 4For every stale app it drafts a keep-or-revoke recommendation with a short rationale.
- 5The agent compiles the recommendations into a single cleanup plan and posts it to the IT/security Teams channel for one-click sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect Microsoft TeamsChannels, chats, files.
- 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.