Skip to main content
Routing is Panaptico’s action layer. When verified state drifts from intent, Routing directs the response: a risky login triggers a harder authentication path, a non-compliant device is moved to quarantine, a failing deployment is blocked from production. Routing is bidirectional with your existing tools (Okta, Cloudflare, ServiceNow, LaunchDarkly, and others) so Panaptico decides when to act, and the tools you already use enforce the action. Because Panaptico’s Test mode exists, the routing itself can be verified.

​
How Routing works

Routing rules connect verification results to actions. A rule has three parts:
  1. Condition — a Signal, Initiative score, or Probe result that must be true or false
  2. Action — the change to make in a connected system
  3. Scope — the entities or populations the rule applies to
When the condition is met, Panaptico sends the action to the target system via API. The action is not a suggestion: it is a directed change that the target system applies. Panaptico then verifies the result, either through a subsequent sensor read or an active Probe.

​
Routing examples

  • Identity and access — a user with a high-risk Signal from an unmanaged device is routed to a step-up MFA flow in Okta
  • Network placement — a device that drops out of MDM compliance is moved to an isolation segment in Cloudflare
  • Deployment gates — a deployment pipeline stage where the Initiative score for “Production Readiness” is off target is blocked in LaunchDarkly
  • Work creation — a gap that cannot be auto-remediated creates a ticket in ServiceNow with the full verification context attached

​
Verified routing

Because Panaptico supports Test mode (active Probes), you can verify that a routing action actually produced the intended effect. If a rule quarantines a device, a subsequent Probe can attempt access from that device and confirm the isolation is effective. If the Probe succeeds, the routing is off target and Panaptico surfaces the gap. Routing is not fire-and-forget: it is part of the continuous verification loop.

​
When to use Routing

Use Routing when you need automated, verified responses to state changes. It is the final step in the Panaptico loop: Acquire, Understand, Verify, Run, and Act. Routing makes the operational ledger operational.

Signals

The scored telemetry that triggers Routing conditions.

Initiatives

The programs whose scores and gaps drive Routing decisions.

Probes

Actively verify that Routing actions produced the intended effect.