Copyright © 2022-2026 basebox GmbH, all rights reserved.
Licensed to be used in conjunction with basebox, only.
Licensed to be used in conjunction with basebox, only.
// security
Dedicated hardware
Applies to
Product: Server · Audience: Security / Compliance reviewer
One customer per physical server; no shared use at the hardware level. That is the property distinguishing basebox Server from the Cloud – and it applies regardless of where the hardware comes from, where it stands and who operates it.
What "dedicated" means
- One organization, one machine. On a basebox Server run exclusively the platform, service models and inference of one customer. No other customer shares CPU, GPU, storage or network interfaces.
- Tenants within the customer are possible: several organizations (for example departments) per installation, logically separated (Infrastructure policy). That is separation within the customer, not between customers.
- GPU sharing is customer-internal. MIG instances or a dedicated service GPU share the hardware between your workloads – inference and service models – never with third parties (Dedicated service GPU).
- No third-party hypervisor. Whether you run Kubernetes on bare metal or on your own VMs is your decision; a basebox Server is not a slice of a shared virtual environment.
Where the hardware comes from
| Source | What changes | What stays the same |
|---|---|---|
| FAST LTA / supplied by basebox | Reference configuration with status Validated or Supported; hardware support via the partner; supply chain documented | Software, data storage, access model |
| Customer-owned / procured by the customer | You are responsible for procurement, firmware, hardware support; status Supported, Experimental or Custom depending on the configuration (Reference configurations) | Software, data storage, access model |
Relevant for the security assessment: firmware level (BIOS, BMC, GPU), supply chain and who provides hardware support – for customer hardware you, for FAST LTA the partner.
What dedicated hardware achieves security-wise
- No side channels to other customers – there are none.
- Physical control sits with the customer or with basebox as housing partner (Customer data center · Hosting at basebox).
- Disks belong to the machine. At the end of the lifecycle you wipe or destroy them according to your concept – nothing sits on a third party's shared storage (Deletion).
- The network boundary is your boundary. The server stands in the customer network; what may go in and out is set by your firewall (Networking); air-gapped operation is possible (Air-gapped environments).
What dedicated hardware does not achieve
- It replaces no encryption at rest – that comes from your storage layer (Encryption).
- It replaces no access control – whoever may read Kubernetes Secrets reads everything.
- It replaces no backup. A server is a single point of failure as long as you do not back up and, if needed, build multi-node.
- It does not automatically activate hardware security features (Secure Boot, TPM, BMC hardening) – that is part of the server preparation by the Platform Operator.
For the review
- Document the server as one asset with serial numbers, GPU UUIDs, firmware levels and location (the manifest from Validate the installation).
- Record who has physical access – depending on location you or basebox.
- Define the sanitization concept for the disks before commissioning.
Next step: Customer data center