At Scale Computing, security is a core design principle. It is built into every layer of the SC//HyperCore™ HyperVisor. It reaches from the storage layer and hypervisor up to the web interface and the update pipeline. The software was designed to provide highly available, scalable compute and storage services. Smart automation and a lean design keep it simple to run. The same simplicity that makes the system easy to run also cuts the number of moving parts an attacker can target.
Core principles
The SC//HyperCore security approach is deliberate and works on many fronts. It rests on three core principles:
Zero Trust, simplicity, and automation. The SC//HyperCore software is built around a “trust nothing, verify everything” philosophy. Complexity is kept low, and routine processes are automated. This shrinks the attack surface and the chance of human error. With no extra clients, protocols, or management tools, there are fewer sources of misconfiguration. There is also less licensing and lifecycle overhead.
Full ownership. Scale Computing keeps full ownership and control of the design, source code, and software updates of the SC//HyperCore platform. Trusted Scale Computing engineers manage all software in-house, without third-party or outsourced engineering teams. The platform removes third-party dependencies wherever it can. That way it avoids hidden exposure points. It gives you a unified environment with no parts in the critical path that others control.
Proactive security posture. Scale Computing engineering and product teams actively monitor new threats, common vulnerabilities and exposures (CVEs), and industry trends. So they can build and ship security updates before risks reach customer sites, rather than reacting after the fact.
Inherent security by design
The SC//HyperCore software is purpose-built for hyperconverged infrastructure, and that focus shapes its security model. Scale Computing tightly controls, reviews, and maintains all third-party and open-source software used in the platform. Scale Computing employees monitor known vulnerabilities and patch them at the source-code level. They don’t depend on outside third parties to gate or test fixes.
The platform shows this discipline in several concrete ways:
- No root or privileged shell access is granted to end users, admins, or outside representatives. There is no general-purpose operating system underneath for an attacker to pivot into.
- No unneeded ports or protocols are open on cluster nodes. The only inbound access path is the SC//HyperCore web interface over HTTPS.
- No separate controller VM, virtual storage appliance (VSA), or external “brain” is required to manage the cluster. So there is no extra system to compromise.
- The hypervisor, storage layer, and management plane are all included in the SC//HyperCore software, reachable only through the web interface and REST API, and protected by a built-in firewall.
Scale Computing calls this mix of Zero Trust thinking, full-stack ownership, and simple design secure by design. It also reflects the broader RFC 1925 principle that guides the product. In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away.
The other pages in this section show how these principles work in practice:
- in the supply chain that produces the SC//HyperCore software
- in the platform-level security features of the runtime
- in the way SC//Fleet™ Manager extends management to the cloud
- in the processes around vulnerability response and customer support