Rosetta: Cybersecurity

Rosetta / Cybersecurity

Rosetta Cybersecurity Adapter

Compiled Physics for Defended Zones

The Cybersecurity adapter translates the Substrate's structural-margin reading into the forces governing AI-assisted attack pressure. Noisy telemetry becomes a deterministic stability score per defended zone, per tick.

SOC analysts see structural drift in the lookahead window where intervention is still cheap, before the engine returns an active intrusion verdict. The score is hash-bound, replay-deterministic, and reproducible across processes.

Two structural variables compute the score:

Λ Lambda: Attack Surface Pressure

The live load an attacker imposes on a defended zone.
The cyber adapter aggregates this across the kill chain so that one severe indicator drives the zone score.

Γ Gamma: Defense Posture

The structural buffer that segmentation, monitoring coverage, and detection latency produce. One collapsed defensive control drives the buffer for the entire defended zone.

The Latency of Signature Detection

Time is the fundamental constraint of pattern-matching defense. Current intrusion detection methodologies rely on prior observation to categorize malicious behavior. These classifiers require a known signature to trigger an alert, evaluating the network telemetry only after the perimeter has absorbed the attack.

Frontier models shrink the interval between novel vulnerability discovery and reproduction at scale. When an adversary deploys an undocumented exploit, the execution sequence bypasses historical threat feeds. The defender must absorb the initial breach to extract the signature required to halt subsequent intrusions.

This architecture creates a permanent structural deficit. Relying on historical patterns leaves the infrastructure exposed during the window between a zero-day event and a deployed classifier update. The security apparatus remains permanently synchronized to yesterday's attack surface.

Structural Zero-Day Early Warning

The KAIROS Substrate reads a signal that exists before a signature does. Per defended zone, per tick: the engine measures how much structural pressure the zone can still absorb before its weakest control collapses. The reading is computed from the telemetry's own geometry, available from the first tick of the first attack.

The cyber adapter treats the defended zone as a load-bearing structure: segmentation, monitoring coverage, and detection latency are the columns. The column carrying the highest live load against its rated capacity is the column that fails first, and the zone score collapses with it. The reading behaves like a stress meter on the weakest column, surfacing the moment the load exceeds what the column can hold.

The score lands in the SOC operator's queue before the intrusion verdict commits. Identical telemetry produces identical scores, hash-bound and reproducible across processes, so the same incident replayed six months later returns the same warning at the same tick. The deterministic envelope holds against zero-day events because the reading is computed on the defender's own structural posture.

Evaluation Point: Live telemetry, per defended zone, per tick
Output: Deterministic stability score per zone
Warning Window: Pre-breach structural drift
Replay Guarantee: Identical telemetry produces hash-identical scores

Deterministic

Identical telemetry produces identical envelopes (ϵ = 10^-6).

Zone-scoped

Each defended zone gets its own stability score. A breach in one zone does not blind the engine to others.

Zero-dependency

The Rust adapter requires no API calls or network access at evaluation time.

Memory-safe

The core engine contains zero unsafe blocks.

Four Zone Archetypes

Every defended surface reduces to a zone with a finite capacity to absorb structural pressure. The cyber adapter assigns each zone a Gamma margin and reads how fast attacker agency erodes it. Four archetypes cover the surfaces most intrusions cross.

Identity Plane

The control surface for authentication, authorization, and credential stores. Attacker agency registers as privilege escalation, lifting Lambda before any payload moves. The adapter measures how much escalation pressure the plane holds before its credential control gives way.

Edge Device

The perimeter surface where external traffic first reaches infrastructure. Attacker agency registers as initial-access attempts, lifting Lambda against an exposed boundary. The adapter measures how much exploitation pressure the device holds before its patch margin gives way.

Internal Segment

The east-west surface carrying traffic between trusted interior systems. Attacker agency registers as lateral movement, lifting Lambda once a foothold lands. The adapter measures how much propagation pressure the segment holds before its segmentation control gives way.

Data Plane

The storage surface holding the records and secrets attackers move toward. Attacker agency registers as bulk egress, lifting Lambda in the final jump. The adapter measures how much exfiltration pressure the plane holds before its access boundary gives way.

Each archetype is one calibration of a single engine. The Gamma margins, Lambda mappings, and weak-link aggregation differ per surface; the physics stays identical.

Tested Against the Mythos Shape

The fixture corpus includes a Mythos-shaped sandbox-escape scenario. The sequence reflects the structural pattern of AI-assisted attacker behavior: privilege pressure rises first, segmentation collapses next, exfiltration arrives after.

Mythos Smoke Results

Zones: agent-sandbox, identity-plane, data-layer
Active intrusion reached: Tick 3 (before exfiltration jump)
Gamma weak link: networkSegmentation
Exfiltration jump: Tick 4 drives Lambda ≥ 0.90
Detection latency clamp: 7,200,000 ms (no reject)

The Read

Aggregating Gamma with critical_min traces the collapse to networkSegmentation, not to the top-level defensePosture rollup. Aggregating Lambda with critical_max ensures the exfiltration jump dominates the zone score even when other indicators stay moderate.

Read the cyber calibration debrief

Three Gates. Cyber Read.

Every proposed action passes through a layered gate chain. Any gate will reject an action that violates structural integrity.

State Gate

Evaluates structural health before considering any action. If gamma (Γ) falls below the zone's deployment floor, the engine refuses further action and emits the warning envelope.

Action Gate

Previews proposed SOC responses against zone reachability. Host isolation, broad containment, credential reset. Reversible actions map to stabilizing moves; blast-radius actions trigger escalation.

Hazard Gate

Detects basin collapse and dual-administrator paradoxes: defensive automation and human operator commands diverging inside the same zone under exogenous attacker pressure.

Intervention That Escalates

The adapter produces operator-facing recommendations from the engine's structural verdict. Recommendations reflect the stability margin, never bypass it.

Investigate Anomaly

Warning active at low to moderate level. The recommendation prompts analyst review while the zone retains structural headroom.

Escalate Incident

Active intrusion: warning level reaches 0.50, kill-chain indicators reach the imminent stage, or steps-to-impact drops below three.

Containment Review

Critical compromise risk. The engine returns RejectState, RejectBasinCollapse, or RejectParadox. Human review is required before any further action.

Cryptographic Operator Authority

A SOC operator authorizing a non-standard containment carries the same cryptographic burden as a frontier model operator authorizing an out-of-policy action.

Substrate signals HUMAN_ESCALATION and halts.
The operator reviews the rejection context, zone telemetry, and stability state.
Authorization requires an RSA-PSS signed override token.
The token binds to the specific evaluation request via SHA-256 digest.
The HITL coordinator records the decision in a durable audit trail.

The system fails closed. If the coordinator is unreachable, the engine blocks the action.

Two-Layer Policy Architecture

A dual-layer system separates platform authority from operator customization, identical to the AI Safety policy contract.

Base Policy

The platform provider sets the structural floor. This policy defines minimum gamma thresholds, enforcement modes, and HITL authorities. It is signed with RSA-PSS and remains immutable for downstream operators.

Operator Overrides

Operators tighten policy within base layer bounds. They will raise the gamma floor or restrict enforcement modes. They cannot lower safety thresholds.

Enforcement Modes

Observe: Evaluates telemetry without rejection for baselining.
State Gate: Refuses when zone Γ falls below the floor.
State + Action Gate: Full preview of SOC actions against zone reachability.

One Engine. Four Surfaces.

The Rust codebase compiles to four specific deployment targets.

Native Library

Embeds into hypervisors, brokers, and on-prem SOC infrastructure via C FFI.

CLI Binary

kairos cyber provides replay, evaluation, action preview, and policy-check.

Python SDK

PyO3 bindings for SOC analytics pipelines and pilot integrations.

WASM Module

Browser-based advisory evaluation and dashboard visualization.

Use Cases for Security Organizations

The adapter delivers structural guarantees across diverse deployment shapes.

Frontier-vendor SOC action gating: previews host isolation, broad containment, and credential reset against zone reachability before execution.
Multi-zone governance: separate stability tracking for DMZ, identity plane, prod-API, data layer, and control plane.
Incident reconstruction: replay-deterministic envelopes pinned to artifact and policy version. Two operators reach the same answer.
Pre-deployment CI gate: kairos cyber policy-check enforces safe defaults before a pilot policy ships.
Escalation discipline: the engine emits recommendation tiers, not severity scores. Recommendations track structural margin.

Compared to Existing Tooling

Substrate provides a structural guarantee where existing tools produce statistical guesses or pattern matches.

Approach	Mechanism	Deterministic?	Aggregation
SIEM correlation	Pattern matching	Implementation-defined	Logical OR
EDR / XDR scoring	Statistical classifier	No	Weighted sum
Substrate cyber adapter	Stability physics	Yes	`critical_max` / `critical_min`

Pattern matchers describe what an analyst would have written into a rule. Substrate computes the structural margin the system actually has.

Technical Specifications

Engine

Language: Rust (Stable)
Latency: Sub-millisecond per evaluation
Determinism: ϵ = 10^-6
Default topology: Per-zone actor

Artifact & Policy

Artifact schema: v1, domain cybersecurity
Lambda aggregation: critical_max
Gamma aggregation: critical_min
License + HMAC: RSA-PSS signed, secret via file or env

Where to Dig Deeper

The body of this page is the translator. Each item below names a load-bearing feature or piece of supporting research and points at the depth artifact where the full treatment lives.

Calibrated Benign Baseline

A 144-cell synthetic grid calibrated against DBIR, NIST, CIS, OCSF, LANL, and DARPA references. 5.2M-snapshot reference run with byte-identical replay. The internal-segment 98.08% finding and what it means.

Methodology debrief →

Kairos Margin (kMargin)

The signed buffer-unit form of structural margin. SOC-facing alternative to raw gamma, with companion fields gateBreached and displayRegime.

Margin blog post →

Distributed Retry Ledger

Multi-node-safe retry budget and escalation state via the HITL coordinator's authenticated adaptive-ledger endpoints. Fail-closed on unreachable coordinators.

Dist. Retry Ledger blog post →

OCSF-Lite Ingest

The adapter consumes a documented subset of OCSF 1.x. A field-level translator ships with the partner tooling; native OCSF 1.x ingest is the planned follow-on.

Cyber CLI Reference

kairos cyber surface: replay, evaluate, action-preview, policy-check, and explain for incident replay and pre-deployment validation.

CLI documentation →

Become a Design Partner

Telemetry contribution shape, redaction rules, labelling discipline, and what partners get back. Mutual NDA, redacted exports preferred, aggregate-only publication.

Partner invitation →

Become a Design Partner

KAIROS Substrate is shipping to design partners ahead of general availability. Active pilots: the cybersecurity adapter (redacted telemetry) and the AI safety adapter (agent trajectories) — see the partner briefs for what a contribution looks like and what comes back.

Compliance and regulatory teams, agent-eval researchers, and investors are also welcome to reach out. Submit your details or use the Contact tab.

Request received. We'll be in touch.