From Self-Reported Controls to Verifiable System State
Continuous attestation for cyber insurance. No plaintext exposure. Underwriting and claims inputs backed by cryptographic proof.
Verifiable inputs for every stage of the policy lifecycle
Underwriting
Replace questionnaires with attested control-state evidence
Claims
Verified system state at time of event — not what was reported after
Broker
Turn constrained accounts into placeable business in under 2 minutes
Four steps. Two minutes. Cryptographic proof.
Broker sends Terminal link
A unique, scoped link is generated for the policyholder.
Policyholder connects systems
OAuth-based, read-only connections. Takes approximately 2 minutes.
HATS produces attested state
Continuous, cryptographically signed control-state evidence.
Insurer receives verifiable inputs
For underwriting and claims — backed by post-quantum proof.
Clear boundaries. Clear outputs.
What HATS produces
- Attested control-state signals across 6 security domains
- Cryptographic proof bundles (ML-DSA-65, FALCON-512, SLH-DSA)
- Time-of-event assertions with deterministic state reconstruction
- Continuous monitoring with fresh attestation at every cycle
- Hash-only evidence — no raw data, no payloads
What HATS does NOT do
- Does not underwrite policies or assess risk levels
- Does not price premiums or determine coverage
- Does not bind coverage or issue policies
- Does not adjudicate, approve, or deny claims
- Does not make any decisions requiring an insurance license
See it in action
Explore how HATS works for underwriters, brokers, and policyholders — or review the trust framework.
HATS produces verifiable control-state evidence. Insurers use it — H33 does not make underwriting or coverage decisions.