Platform
Security, certification and licensing
The threat model, administrator and user permissions, audit evidence, offline licensing and update control.
What this component is responsible for
Technical assurance, policy, identity, approvals, signed releases, audit evidence and commercial entitlement enforcement. It is the machinery that lets a customer verify rather than trust.
Offline licensing
A licence is a signed file naming the site, the permitted framework and features, the effective dates and the release signatures. It validates without a network call, so a fully air-gapped customer is a supported customer.
Issuing a licence requires the site identity and the entitlement. It does not require, and does not receive, customer financial data or vault contents.
What the design excludes
- Routine phone-home telemetry.
- Unrestricted remote vendor access to a customer site.
- Any requirement to send operational data to Lanvex for the system to keep working.
Limits worth stating plainly
Revocation on an isolated site is bounded by what that site has already accepted; the operational rules for that case are specified rather than implied.
No security claim here is absolute. Each control is described with what it does and what it was tested against, and is called verified only after independent testing.
Certification applies to the version reviewed, not to everything a publisher later says about it.