The pages in this section explain how the SC//HyperCore™ HyperVisor is designed, built, and run to keep your workloads safe. They also show how to apply the shared responsibility model when you run SC//Platform™ in your environment.
Security is a core design principle for the SC//HyperCore software, not an add-on. Every layer of the stack is purpose-built, owned, and maintained by Scale Computing engineers. That covers the custom-built SCRIBE storage layer and the embedded KVM-based hypervisor. It also covers cryptographically signed updates and customer-controlled support access. The result is a hyperconverged platform with a small attack surface by design, open operations, and the controls you need to meet regulatory obligations.
Use these pages to learn how each layer of the platform adds to your overall security posture. They also show how SC//Fleet™ Manager extends that posture into the cloud, and where your responsibilities begin as an operator of the platform.
- Security Philosophy — the principles behind the SC//HyperCore security model: Zero Trust, full ownership of the stack, and a proactive security posture.
- Trusted Software Development — how SC//HyperCore software is built, tested, and signed before it ever reaches a cluster.
- Platform Security Features — the embedded hypervisor, SCRIBE storage layer, AIME automation, and isolated networking that secure the runtime.
- Access Control and Authentication — how authentication, role-based access, and audit logging control administrative access to a cluster.
- Encryption and Boot Integrity — Secure Boot, vTPM, encryption at rest, and encryption in flight for replication traffic.
- SC//Fleet Manager Cloud Security — the outbound-only connection model and access controls behind cloud fleet management.
- Customer-Controlled Support Access — how customer-initiated support tunnels keep remote support access on your terms.
- Incident Response and Patching — how vulnerabilities are monitored, patched, and communicated, and how to report one.
- Compliance and Shared Responsibility — the frameworks SC//Platform aligns with and where platform responsibility ends and yours begins.
For day-to-day setup and administration tasks referenced throughout this section — configuring SSO, managing user roles, remote support tunnels, and SC//Fleet Manager — see the SC//HyperCore User Guide.