Security
Trust through specifics, not badges. This page describes how replay is isolated, where capture has limits, and what is honestly still in progress.
01 · Replay isolation
Replay serves recorded observations back to your agent. Boundaries are intercepted; a correct replay is designed so it cannot reach the outside world:
Attempted effects during replay are reported as findings — never performed.
02 · Fidelity and eligibility
If an execution touched a boundary Ontral did not instrument, replay reports the exact source, operation, and remediation. Ontral is designed to fail closed: an uncovered execution boundary must produce REPLAY INCOMPLETE rather than a false identical result.
source thread-3 operation socket.connect coverage unsupported boundary remediation install the relevant interceptor or annotate the boundary
designed to fail closed · eligibility reported per capsule
03 · Data capture
A capsule preserves what crossed the boundary — which can include customer data inside prompts, tool responses, and retrieved documents. Deployment, retention, and storage controls are being productized so capture can follow your data boundary.
04 · Redaction limitations
Base64 is encoding, not protection.
Key-name filtering alone does not solve arbitrary-payload redaction.
Generic redaction of arbitrary payloads is not a fully solved problem, and we do not claim it is. Field-level policies, allow/deny rules, PII and secret scanning, and customer-controlled retention and storage are being built in the open with design partners. Payloads that cannot safely be retained have a required behavior: exclude them, report the boundary as uncovered, and prevent the replay from being classified as exact.
05 · Content-derived verification
Every observation is hashed into a capsule root. Any modified byte changes the root; a replay is attested against it; an exported capsule can be re-verified anywhere. This is not blockchain — it is verifiable execution evidence.
06 · Retention and deletion
Configurable retention and deletion are part of the design-partner roadmap, alongside customer-controlled storage. Until those controls are generally available, retention expectations are agreed explicitly with each early-access team.
07 · Security status
Ontral does not currently claim SOC 2, ISO, HIPAA, or other certifications. Security and compliance programs will be published as they become available. Ask us where we are in the process — we will answer specifically.
08 · Responsible disclosure
We ask researchers to report vulnerabilities privately and give us reasonable time to remediate before disclosure. We commit to acknowledging reports quickly and crediting researchers who want credit.