KoraSafe

Policy enforcement
That actually enforces

Powered by the Kora Enforcement agent and its fleet of Guardian agents: Kora PII Sentinel, Kora Bias Watchdog, Kora Hallucination Detector, Kora Cost Monitor, and Kora Autonomy Governor. Every violation tracked, every action timestamped, every resolution auditable.

Policy Engine

Policy engine

From input filtering to emergency circuit breakers, each policy type addresses a distinct enforcement need. Compose them together for defense-in-depth coverage.

  • Input Filter -- scrub sensitive data before it reaches the model
  • Output Filter -- intercept and redact model responses
  • Approval Workflow -- human-in-the-loop for high-impact actions
  • Circuit Breaker -- emergency kill switch on threshold breach
  • LLM-as-Judge -- secondary model evaluates primary outputs
  • Pre-deployment Gate -- block non-compliant agents from production
  • Rate Limiting -- control frequency and volume of interactions
POLICY ENGINE Input Filter Output Filter Approval Flow Circuit Breaker LLM-as-Judge Pre-deploy Gate Rate Limiting
Lifecycle

Policy lifecycle

Every policy follows a strict lifecycle path. Transitions are logged with timestamps and admin identity. Policies cannot skip states, ensuring full auditability.

  • Draft -- under review, not yet enforced
  • Active -- live enforcement in production
  • Paused -- temporarily suspended, reversible
  • Archived -- permanently deactivated, preserved for audit
Draft Active Paused Arch- ived Reactivate Every transition logged: admin@company.com activated policy at 2026-04-07T14:30Z
Violations

Track, triage, and resolve

Every policy violation is captured with full context. Filter by severity and status, then resolve through an admin workflow with a complete audit trail.

  • Three severity levels: High, Medium, Low
  • Status tracking: Open and Resolved
  • Per-asset guardrail coverage indicators
  • Timestamped audit trail for every action
VIOLATION SEVERITY BREAKDOWN 3 High Severity PII exposure, boundary violations, safety failures OPEN 7 Medium Severity Policy threshold near-misses, partial compliance gaps 5 OPEN 12 Low Severity Configuration warnings, documentation gaps RESOLVED 70% resolved -- 22 total violations
How Enforcement Works

When a Guardian agent detects a violation, it triggers the appropriate policy automatically. Every step is logged for regulatory evidence.

Detection
Guardian agent identifies a policy breach or anomaly in real time
Policy Trigger
Matching enforcement policy activates - filter, circuit breaker, or approval gate
Resolution
Admin reviews the violation, confirms severity, and marks it as resolved
Audit Trail
Timestamped record of detection, policy action, and resolution - audit-ready