SECOPS
GitHub OAuth App & Install Reviewer
When a new GitHub OAuth app or installation gains org access, it summarizes the repository and permission scope.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub webhook: app install / OAuth authorizationGitHub
- ActionFetch app permissions and repo accessGitHub
- ActionSummarize reach and riskOpenAI
- LogicBranch: org-wide/secrets access vs. single-repo read
- OutputPost review card to secops SlackSlack
What it does
Focuses specifically on GitHub, where third-party apps and OAuth integrations can request broad repo, org, and Actions permissions. When a new app installation or OAuth authorization touches the org, it pulls the permission set and repo selection, explains what the app can actually reach (code, secrets, workflows), and posts a review card so engineering security can approve or flag it.
When to use it
Use this when your source code lives in GitHub and you want a dedicated gate for app installs and OAuth grants there, separate from your general SaaS OAuth review.
How it works
- 1A GitHub webhook fires on an installation or OAuth authorization event for the org.
- 2The flow fetches the app's granted permissions and the list of repositories it can access via the GitHub integration.
- 3An LLM step turns permissions into a plain-English reach summary and risk note.
- 4A logic branch separates all-repo or secrets/Actions-capable grants from single-repo read grants.
- 5A Slack review card is posted to the secops channel identifying the installer and recommended action.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.