Loading…
Open-Policy Exchange
servicenow~5 min to deploy
IT Ops Pack
Access, change, and procurement gates for internal automation — prove every sensitive change followed the approved path.
For: Mid-market IT, security, platform ops
SOC 2 CC6.2ISO 27001 A.5.18Access review evidence
What it enforces
Access Change Gate
Requires a timed, approved dossier for sensitive access and change workflows.
Just-In-Time Access
Adds a timed dossier and revocation trail for temporary admin rights.
Software Procurement Gate
Blocks unapproved OAuth and SaaS procurement events before signup.
it-ops-pack.yaml
# IT Ops Pack
# Fork: the three gates from the it_ops starter pack, with your thresholds.
apiVersion: decionis.dev/v1
kind: PolicyPack
metadata:
name: it-ops-pack
surface: servicenow
policy_pack_id: it_ops
standards: [SOC2-CC6.2, ISO27001-A.5.18]
defaults:
mode: shadow
emit_dossier: true
rules:
- name: access_change_gate
when: "request startswith 'access.'"
decision: |
ESCALATE IF approval_dossier == null
ALLOW OTHERWISE
reason_code: access_change_without_dossier
- name: just_in_time_access
when: "request == 'access.temporary_admin'"
decision: |
BLOCK IF requested_duration_hours > 8
ESCALATE IF revocation_scheduled_at == null
ALLOW OTHERWISE
reason_code: jit_window_or_revocation_missing
- name: software_procurement_gate
when: "action in ['oauth.grant', 'saas.signup']"
decision: |
BLOCK IF vendor.id not in approved_software_catalog
ALLOW OTHERWISE
reason_code: unapproved_software_procurement
Fork it, change the thresholds to match your environment, and deploy in shadow mode first — it defaults to listen-only so nothing in your live pipeline changes.
How to install it
Follow the install path for this surface, then paste the forked YAML as your policy config.
What to do next
This recipe is one step in a path. The same five steps apply to every recipe in the exchange.
- Simulate this recipe
Run the policy against a realistic action in the browser. Push it past what the rules allow and watch the verdict come back. No account.
- View the signed Decision Dossier
See exactly what was decided and why: the rule that fired, the evidence it read, the policy version in force, and an Ed25519 signature you can verify yourself.
- Deploy in shadow mode
Measure what the policy would have caught on your own traffic without touching the live path. Every recipe defaults to shadow, so the first deployment carries no execution risk.
- Connect a real workflow
Point the same policy at the system where the action actually originates — a checkout, an ERP posting, a Zap, an agent's tool call.
- Share the verified result
Publish the proof: a public verification link, an embeddable badge, a PR comment, or an anonymized shadow-mode finding. This is how the next person discovers Decionis.