What you can inspect. What you can attest to. What stays out of the wire.
One principle: no consumer health data should cross a third-party perimeter the operator cannot inspect. The architecture, cryptography, validation cycle, and corporate risk coverage all serve it.
Zero-trust framework throughout — every component mutually authenticated, every traffic flow logged inside the operator's perimeter, no third party receiving matchable identifiers. Risk analysis cycles run under 45 CFR § 164.308(a)(8). What follows is the reference posture.
Cloud architecture & data isolation
Isolated boundary under direct engineering control. Enterprise deployments run dedicated single-tenant infrastructure — no shared compute or storage across clients. Independent Practice multi-tenant deployments use logically-isolated environments with cryptographic separation.
Validation Standard — dedicated infrastructure hardening
Every MSO Platform and Enterprise deployment ends with an independent Letter of Attestation before live production data routes through the perimeter.
Isolated Provisioning
Dedicated single-tenant environment on enterprise-grade cloud infrastructure carrying provider-level SOC 2 Type II and ISO 27001 attestations, operated under Apex Vault's direct engineering control.
Dedicated Penetration Testing
Independent third-party security firm conducts a targeted manual pen test against the client's specific infrastructure pre-go-live. Findings remediated to zero un-remediated Critical or High under CVSS v3.1.
Attestation at Go-Live
Independent Letter of Attestation issued. Traffic routing activates only after manual hardening, validation, and the clean attestation. Annual re-validation pen test runs for the life of the engagement.
Cryptography & transmission security
Industry-standard primitives in transit and at rest. Automated key rotation. Hardware-backed identity for privileged access.
Continuous monitoring & threat detection
Automated monitoring and incident response wrap every deployment. Detection runs at the infrastructure, network, and application layers.
Compliance & attestation posture
Posture is deliberately calibrated to what is currently substantiated. Self-attestation language is not upgraded beyond what an independent audit confirms.
Apex Vault's own posture
Self-attested against the Cloud Security Alliance Cloud Controls Matrix (CCM) via the Consensus Assessments Initiative Questionnaire (CAIQ). SOC 2 Type 1 attestation is the next compliance milestone.
Infrastructure provider posture
Underlying cloud infrastructure carries provider-level SOC 2 Type II and ISO 27001 attestations, independently issued and operated under Apex Vault's direct engineering control. Provider-level attestation reports made available under MNDA.
Applicable regulatory frameworks
Corporate risk & insurance
Multi-million-dollar Excess Liability towers covering Tech E&O and Cyber Liability. Coverage scales to deployment shape; specific limits made available under MNDA.
Request the full trust package under MNDA. Detailed architecture schematics, cloud-provider identity, complete attestation mapping, named subcontractors, specific control evidence, and full insurance tower documentation. Email compliance@apexvaultcompliance.com.