FASTER DETECTION. FASTER PROOF. ONE LOOP.

Your control fired.
Did it work?

Detection is measured in seconds. Proof is signed in minutes. We send a live adversary agent at each control and sign only the result that matches what was committed before the run.

proof-record.jsonEXAMPLE
targetagent ct-dummy-07 (agent under test)
ttpT1021 remote services
envcustomer-like arena, isolated
PROOF OF CONTROL
control fired / logged
PROOF OF EFFICACY
expected = actual
committedblocked, locked pre-run
expectedblocked
actualblocked
verdictSIGNED
Self-attestation is a claim. A signed outcome is proof.
READOUT / EXAMPLE AGENT CAMPAIGN, 12 TTPS

Every attack, read out.

12/12
PROOF OF CONTROLcontrol fired on every TTP
11/12
PROOF OF EFFICACYattacks that failed
1 held
VERDICTdivergence is never signed
01 / THE GAP

Firing is not working.

THE BASELINE

Proof of Control

The control fired. A SIEM entry, an alert, or an audit record says so. Nothing shows whether the agent got through.

answers: did it run?
THE STANDARD

Proof of Efficacy

The control worked against a real adversary technique, in a customer-like environment, with the expected result committed before the run.

answers: did the attack fail?

Chaotic.core™ produces both, and the signed record only counts when efficacy matches what was committed.

02 / HOW IT WORKS

Commit. Attack. Measure. Sign.

  1. 01

    Commit

    Expected outcomes are locked before anything runs. No moving the goalposts after the agent has fired.

  2. 02

    Attack

    Adversary agents run real techniques with no industry mappings against the controls in an isolated environment.

  3. 03

    Measure

    Actual outcomes are captured as they happen: did the control stop the agent, or did the attack get through?

  4. 04

    Sign or withhold

    Expected matches actual, so the record is signed. Divergence is withheld until the control is fixed and retested.

03 / MODES

In the lab. Or live, alongside real traffic.

Arena

Model the target locally, then spin up a full arena in the cloud. Good for pre-deploy checks and vendor evaluations.

Continuous

A witness runs in production with no start and no finish. Proof updates as the control changes and as new agents appear.

CLOUD EVIDENCE ADAPTERS
AWS GOOGLE CLOUD AZURE DIGITALOCEAN
04 / BUILT ON PROOF PROTOCOL

Open specs.
Controlled code.

The Proof Protocol specs are open on GitHub, so anyone can check a signature, read the declared AI contribution, and see who funded the work. The code that produces the proofs stays controlled.

Read the specs
AI_DISCLOSURE.mdAI vs human, declared
FUNDING.mdwho paid, named
REVIEWERS.mdhuman or AI, marked
schemas/machine-readable
LICENSE.mdopen specs, Proof Protocol License

Stop attesting.
Start proving.

REQUEST ACCESS Request access

Vendors proving a product. Buyers verifying one. Insurers pricing the gap. Send us one control to start.