Zero-trust principles
Authenticate explicitly, minimize implicit trust, and continuously evaluate context.
Security architecture
The security platform must be secure by design.
OZVO is in active development. The principles and requirements below describe the intended production direction—not certifications or claims of completed deployment.
Least privilege
Dedicated service identities and narrowly scoped permissions are production requirements.
Hardened appliance
A hardened Ubuntu foundation with TPM 2.0, Secure Boot, and full-disk encryption as target requirements.
Application isolation
Separate services and responsibilities to reduce the effect of a component failure.
Secure updates
Design for authenticated, integrity-checked updates and controlled recovery.
Protected communication
Encrypt and authenticate communication between the appliance and planned cloud services.
Auditability
Record important administrative and automated actions so activity can be reviewed.
Resilient operation
Keep core local security functions available during temporary cloud interruption.
Selective telemetry
Make cloud telemetry privacy-conscious and customer-selectable where practical.
Bounded autonomy
Apply severity, confidence, impact, and policy before automated action.
Support access
Design customer-authorized support access to be temporary and audited, without a permanent vendor backdoor.
Recovery
Plan for reliable restoration paths without bypassing platform security controls.
Responsible disclosure
Security contact
We value responsible security research and intend to publish a formal disclosure process and monitored security contact before general availability.
No final security mailbox is configured yet. Please do not interpret this page as providing an active reporting channel.