SECOPS
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
How it runs
The automated pipeline, trigger to output.
- TriggerRotation-completed eventHTTP webhook
- ActionAttempt auth with old key (expect rejection)HTTP webhook
- LogicBranch on whether old key still works
- ActionAppend verified result to audit tablePostgres
- OutputReport success or raise failed-revocation alertSlack
What it does
Closes the loop on revocation by proving it worked. Triggered after a rotation event, it actively tests that the old key is now rejected and the new key authenticates, then records the verified outcome to a durable audit log for compliance evidence.
When to use it
Use it whenever a regulator or auditor needs proof that a leaked credential was truly killed, not just marked rotated. It catches the dangerous failure mode where a revocation API returns success but the old key still works.
How it works
- 1A rotation-completed event from an upstream revocation workflow triggers the check.
- 2An action makes a live authentication attempt with the old credential against the provider, expecting rejection.
- 3A logic step branches: if the old key still authenticates, it flags a failed revocation; otherwise it confirms closure.
- 4An action records the verification result, key fingerprints, and timestamps to a Postgres audit table.
- 5A Slack message reports verified success, or raises a loud failure alert if the old key is still live.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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).
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.