Security from infrastructure to application.
ORUNVAULT is designed around layered security controls spanning facilities, infrastructure, networks, data, identities, and monitoring.
Physical
Controls at the facility level that protect the physical infrastructure ORUNVAULT is designed to run on.
- Data-center access controls
- Environmental monitoring
- Power resilience
- Network redundancy
Infrastructure
Controls that isolate workloads and keep the underlying platform patched and hardened.
- Workload isolation
- Network segmentation
- Secure virtualization
- Patch management
- Infrastructure hardening
Data
Controls that protect data at rest, in transit, and across backup and key-management architecture.
- Encryption at rest
- Encryption in transit
- Backup protection
- Key-management architecture
Access
Controls that govern who can reach infrastructure and what they can do once they are in.
- Multi-factor authentication
- Role-based access control
- SSH keys
- Privileged access management
Visibility
Controls that make infrastructure activity observable, so issues can be detected and investigated.
- Audit logs
- Infrastructure monitoring
- Security events
- Administrative activity tracking
Security is a system, not a checkbox.
Defense-in-depth means no single control carries the full weight of protecting a workload. Security is communicated as multiple overlapping controls across every layer of the stack:
A note on claims
ORUNVAULT does not claim to be “100% secure,” unhackable, or protected by “military-grade” or “bank-grade” security. Instead, this page describes the specific technical controls ORUNVAULT is designed around — encryption at rest and in transit, role-based access control, network segmentation, and audit logging — and is explicit about which controls are live versus planned.
Talk to a security engineer
Discuss your security and architecture requirements directly with our team.