Skip to content

Watch first, then enforce

Purpose: a guardrail that blocks the wrong thing breaks someone's app on a Monday morning. Start every policy Observing: its guardrails record what they find and stop nothing. Then read What enforcing would have done on the last seven days of real calls, and switch it to Enforcing when the answer is right.

In the demo world, "GDPR: personal data stays out (Maison Ardelle)" is observing while the client agrees what may be sent.

Before you start

  • You're an organisation admin or a Compliance officer Enterprise, or a group admin for a policy on your own teams.
  • The policy exists and is Observing (New policy and the built-in recipes start that way).

A policy's states

State What its parts do
Draft Nothing is applied.
Observing Guardrail parts log what they find without acting. Region rules, routes and other parts aren't applied yet.
Enforcing Every part is in force.
Paused Every part is lifted until someone resumes it. It stays on Home while paused.

Steps

  1. Open Policies › Policies and choose the policy.
  2. Read What enforcing would have done: over the last seven days, for the keys it reaches now, findings by category and what would have been done, calls that went outside its region rules' areas, and calls its compliance routes would have sent elsewhere.
  3. In Request logs, its calls show what it found with Logged, so you can open a few and check. Filter Guardrail outcome by Logged.
  4. When you're satisfied, choose Start enforcing…. The confirmation lists the parts and, under What it changes, how many keys it reaches and what its parts would have done.
  5. Choose Start enforcing. "… is now enforcing."

Observing to enforcing: What enforcing would have done over the last seven days, then Start enforcing

Check it worked

The policy reads Enforcing on Policies. Its guardrails in Guardrails › Rules › List every rule no longer say Observing: logs only, and new calls they catch show Blocked, Masked, Pseudonymised or Redirected in Request logs instead of Logged.

Step back, pause or resume

  • Back to observing…: its guardrail parts go back to only logging, and its other parts stop applying, until it enforces again.
  • Pause… lifts every part; it needs a reason, kept in the audit log, and shows the keys it reaches.
  • Resume… asks whether to resume as Observing or Enforcing, with what that changes.

Good to know

  • What enforcing would have done is an estimate from past calls; enforcing acts on future calls only.
  • A single guardrail can also observe on its own: List every rule › open it › Promote to enforce.
  • A guardrail that only logs personal data such as cards, health data or ID numbers says Stores the original text: wherever call bodies are kept, the original is stored. Mask or block to keep it out.