Need to know is a control
Who may see a record is a property of the record and of the person, not a setting in somebody's interface.
Solutions · Defence and public sector
Classified estates, and the ones with no route out.
Public sector and defence estates carry two constraints most products treat as an afterthought: information is classified and compartmented, and the network may have no route to the internet at all.
What is asked of you
What makes this different.
No route out
A tool that has to reach a vendor service to answer a question is a tool that cannot be deployed here.
The evidence outlives the vendor
What an auditor receives has to be verifiable without an account, without us, and years later.
Our answer
What it does inside a classified estate.
Classification and clearances
Classification levels, compartments and per-user clearances with an expiry date are part of the product, and they are enforced on the server rather than drawn in the interface.
It runs with no route out
The self-hosted build runs on your own servers with every detection, and nothing has to call home. Activation uses a signed licence file, the install comes as a bundle you carry in, and evidence is verified offline.
Signed is not the same as genuine
Attackers have shipped tools signed with stolen certificates. Zero Door weighs the signature, the signer and the certificate's state together with the original content, so a valid signature alone does not make a binary legitimate.
Evidence verified without us
Actions land in a hash-chained audit trail, reports can be signed, and the evidence bundle carries its own verifier script.
The agent defends itself
The binary hashes itself at start-up, binary and unit files can be made immutable, remote commands can be required to carry a signature, and updates verify a pinned trust root before they swap anything.
RuleEvidence checks out without us.
An auditor checks it without us.
Every export carries a signature and a verifier that runs on a machine with no network. Years later, with no account and no call to us, it still ends in PASS or FAIL.
[ PASS ] Ed25519 signature is valid for the embedded public keySee the proof: Evidence checks out without us.Control catalogues
Mapped to NIST SP 800-53 and national catalogues.
- NIST SP 800-53 Rev 5
- ISO/IEC 27001:2022
- NATO catalogue (illustrative)
- Information and Communication Security Guide
- Turkish Cyber Security Law 7545
Catalogues ship with control rules that integrity telemetry can answer. Where a catalogue is illustrative rather than authoritative, the product says so.
Evidence
What leaves the room.
- 01The audit trail is HMAC-chained with signed nightly checkpoints and a verifier that names the failure kind.
- 02Assessments export in OSCAL alongside PDF, CSV and JSON.
- 03The evidence bundle lists hashes, freshness and supersession for every artefact rather than quietly dropping the stale ones.
- What is handed overAn assessment export, and a bundle that checks itself.
Boundaries
What it is not.
There is no accreditation to claim. The product maps to control catalogues and produces evidence; the accreditation is the authority's.
Offline, vulnerability and end-of-life data does not refresh by itself, and trusted timestamping needs a route out.
It detects, explains and evidences. It does not respond on your behalf.
Plan a pilot inside your perimeter.
The self-hosted build on your own servers, with no route out, and the scope written down before anything is installed.
Plan a pilot