SECOPS
Escalate access-control forced-door and tailgate events
Triages access-system door events from a webhook, distinguishes genuine forced-entry or held-open alarms from routine traffic.
How it runs
The automated pipeline, trigger to output.
- TriggerAccess system posts door eventHTTP webhook
- LogicFilter out routine badge grants
- LogicRate severity by event type and hour
- ActionPage physical-security on-callPagerDuty
- OutputNotify security channel with contextSlack
What it does
Filters the firehose of access-control events down to the ones that matter for security. It inspects each event type, ignores normal badge grants, and treats forced-door, door-held-open, and repeated denied-access events as potential breaches. Genuine alarms page the physical-security on-call and post a rich notification with the door, reader, and credential details to the security channel.
When to use it
Use this when your access-control platform (badge readers, smart locks) emits door events to a webhook and you need forced-entry or propped-door alarms surfaced to security immediately, without humans watching a noisy event stream all night.
How it works
- 1The access system posts a door event with door ID, event type, and credential.
- 2A logic filter drops routine grant events and keeps forced, held-open, and denied bursts.
- 3A second logic step rates severity by event type and time-of-day.
- 4High-severity alarms page the physical-security on-call rotation.
- 5A formatted alert with door, reader, and credential context is sent to the security Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.