Join our Newsletter — 33% off our NHI Course
Home› Glossary› Architecture & Implementation› Customer-Managed Infrastructure
Architecture & Implementation

Customer-Managed Infrastructure

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Architecture & Implementation

Customer-managed infrastructure is infrastructure that the customer provisions, configures and administers rather than relying on a provider to run it for them. It can include servers, virtual machines, storage, networking and operating systems, with the customer responsible for patching, access control, logging and other operational controls.

What customer-managed infrastructure means in practice

Customer-managed infrastructure is defined by ownership of the operational stack, not by where it runs. The customer provisions the environment, sets the configuration, and carries responsibility for day-to-day administration, which means the security model is driven by what the customer must control directly rather than what a provider abstracts away.

This matters because the boundary of responsibility is clearer than in fully managed services, but it is also narrower. When you choose customer-managed infrastructure, you inherit the work of hardening hosts, maintaining operating systems, defining administrative access, and keeping visibility into what is running and who can change it.

Core components under customer control

Customer-managed infrastructure can include servers, virtual machines, storage, networking, and operating systems. Those layers are the substrate for most higher-level workloads, so the customer must decide how they are segmented, monitored, patched, and administered.

The practical consequence is that the customer owns the control plane of the environment, even if some underlying facilities are hosted elsewhere. That means patch cadence, baseline configuration, firewalling, image management, and administrative boundaries are part of the customer’s security posture, not incidental details.

Security responsibilities and control boundaries

The main security value of customer-managed infrastructure is control, because the organisation can choose its own tooling, logging depth, and access model. The same control also creates obligation: if a configuration is weak, the customer cannot attribute that weakness to a managed-service abstraction.

In cloud environments, this is where service boundaries become especially important. Customer-managed infrastructure often sits alongside provider-managed services, so teams need to know exactly which controls remain theirs and which are handled elsewhere. For key-handling decisions, AWS KMS Security Guide is a useful reference for understanding how key policy, grants, and logging separate customer responsibility from platform defaults.

It is also common for infrastructure choices to intersect with secrets and encryption management. Secrets Manager vs KMS vs HSM helps clarify which layer protects secrets, which layer manages keys, and when a hardware-backed boundary becomes relevant.

Operational trade-offs and governance implications

Customer-managed infrastructure usually delivers more flexibility than a fully managed service, but the trade-off is operational load. The customer must run change management, availability planning, backups, recovery testing, and log review with enough discipline to match the criticality of the workload.

That governance burden becomes more visible as the fleet grows. If the estate contains many hosts, virtual machines, or self-managed operating systems, ownership must be explicit: who patches, who approves changes, who reviews logs, and who can administer privileged access on behalf of the environment.

For cloud-heavy estates, the control conversation maps cleanly to cloud security assessment and shared-responsibility governance. The CSA Cloud Controls Matrix is a strong external reference for organising those control expectations across IAM, infrastructure, audit, and data security domains.

Risk and Threat Considerations

Customer-managed infrastructure concentrates operational responsibility in the customer’s own team, which means misconfiguration, missed patching, weak access control, and poor logging can turn directly into exposure. The threat surface is usually not exotic, it is cumulative: exposed management ports, stale images, overprivileged administrators, and unreviewed system changes create straightforward paths to compromise.

Failure mechanism: Attackers commonly target the layers the customer must maintain, because those layers often carry the widest privilege and the least consistent oversight. A weak operating system baseline, exposed administrative interface, or unmonitored VM can give an intruder a durable foothold.

Impact: Compromise can lead to data theft, service disruption, credential exposure, lateral movement, and persistence across adjacent systems. If infrastructure logging is incomplete, post-incident review may also miss the earliest indicators of compromise.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST CSF 2.0PR.AA-01 — Identity Management, Authentication, and Access ControlCustomer-managed infrastructure depends on controlled administrative access.
Recommendation — Define and enforce access rules for infrastructure administrators and operators.
NIST SP 800-53 Rev 5CM-2 — Baseline ConfigurationCustomer-managed infrastructure requires customer-owned secure baselines.
CM-6 — Configuration SettingsThe term centers on customer-set operating system and infrastructure settings.
AU-2 — Event LoggingLogging is a stated customer responsibility in this infrastructure model.
Recommendation — Establish and maintain secure host and VM configuration baselines. Apply approved configuration settings to customer-managed systems. Log administrative and system events for customer-managed infrastructure.
CIS Controls v8CIS-4 — Secure Configuration of Enterprise Assets and SoftwareCustomer-managed infrastructure hinges on hardened, customer-controlled configuration.
Recommendation — Harden infrastructure assets with secure configuration standards.

Practitioner Guidance

Why practitioners should care: The term is operationally significant because it defines who must own hardening, monitoring, patching, and recovery. A team that treats customer-managed infrastructure like a provider-managed service will usually under-resource the controls that matter most.

Governance implication: Make the responsibility split explicit in architecture diagrams, operating procedures, and vendor contracts. For infrastructure that includes privileged administration or host-level secrets, align the control model with least-privilege and strong auditability, using sources such as NIST Cybersecurity Framework 2.0 and NIST SP 800-53 Rev 5 Security and Privacy Controls as broad control references.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org