PostQS
Request a demo
PostQS/Platform/EnclaveVault
EV

Native identity, authorization, and cryptographic control.

Rather than delegating trust to external identity systems, EnclaveVault enforces identity and access as a native part of platform operation - a single, authoritative trust boundary.

What EnclaveVault is

The identity and key authority for the PostQS stack.

EnclaveVault is the identity, authorization, and cryptographic authority across EDP, EncryptHub, and the rest of the PostQS stack.

  • Defines native user and service identities
  • Enforces authentication and authorization
  • Issues and validates access tokens
  • Manages cryptographic material lifecycles
TRUST BOUNDARY · ENCLAVEVAULT Identities Users · services · roles Authorization Native, evaluated internally Tokens Issuance & validation Cryptographic Material Scoped lifecycles Coordinates with: EDP execution · storage · inter-component No implicit trust inherited from external systems EXTERNAL IDENTITY · NOT TRUSTED BY DEFAULT
Identity as a platform boundary

If an identity does not exist in EnclaveVault, it cannot access the platform.

Identities exist within the platform

Users and services live inside EnclaveVault. Implicit trust from outside systems is never inherited.

Decisions evaluated internally

Access policies are applied inside EDP at execution time.

Authorization at execution time

Authorization is enforced during execution - not as an after-the-fact check.

No inherited trust

External identity systems are not assumed as part of the trust model.

Cryptographic authority

Material is scoped, lifecycle-managed, and not broadly accessible.

Beyond identity, EnclaveVault coordinates cryptographic context for execution, storage, and inter-component communication.

  • Execution-scoped cryptographic context
  • Storage-scoped key lifecycles
  • Inter-component communication keying
  • Backed by TRNG hardware entropy
See how TRNG fits in
Integrated with the platform

Tight coordination with the Enclave Data Platform.

Together they ensure identity, access, execution, and persistence operate under a consistent trust model.

Read about EDP

A single trust boundary for a single platform.

Detailed documentation is available under NDA and appropriate authorization.

Talk to us See the security model