Infrastructure 05 of 06
Security, Certification and Licensing
Technical assurance and the machinery of trust: identity, approvals, signed releases, audit evidence and licences that work offline.
In development
What it enables
- Releases that can be verified rather than trusted on a vendor’s word.
- Entitlements that a site can validate without calling home, so an offline customer is a supported customer.
- Audit evidence a customer can hold and show, under their own control.
Who it serves
- Customers answering their own regulators and auditors.
- Publishers who need a predictable, documented review.
- Administrators operating a site day to day.
Scope and boundaries
- Certification applies to what was reviewed, at the version reviewed. It does not bless everything a publisher later says.
- Revocation on an isolated site is limited by what that site has already accepted. The rules for that case are stated, not glossed.
- We describe what the controls do and what they were tested against. No security claim is absolute, and ours are stated with their evidence.
- Compliance with a given regime is the customer’s to establish with their own advisers. A framework can support it; it cannot confer it.
In practice
- A release is signed, its artefact hashes recorded, and a site verifies them before install.
- A licence is issued as a signed file naming the site and its term, and validates with no network call.
- A security review ends in a written outcome with its exceptions listed, not a badge.
Where we are
In development, alongside the operating system it protects. The review tiers and signing practice are settled, and the services that run them are being built.
Questions
- Do you need to see our data to license us?
- No. Issuing and validating a licence needs the site and the entitlement, not the contents of your vault or your ledger.