NIST SP 800-53 Rev. 5 CM-7(6) — Confined Environments With Limited Privileges

What this control requires

Organizations must identify user-installed software that poses risks due to its origin or potential for containing malicious code. Such software is required to execute only in confined physical or virtual machine environments with limited privileges, such as virtual machines or containers with restricted system access. This isolation minimizes the attack surface and contains potential damage from malicious code, ensuring system security and integrity. This control supports the Virtual Machine capability within the Configuration Management family.

In plain English

Organizations must identify user-installed software that poses risks due to its origin or potential for containing malicious code. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within Configuration Management, the assessor will trace your implementation back to the catalogue reference (Control CM-7(6)) and look for objective evidence on the latest two assessment cycles.

How to implement

Physical Security

Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Configuration. Document the trigger, the owner and the cadence.
• Physical. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• Scope: management, system, only, identity, configuration, software, environments, virtual machines.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Confined Environments With Limited Privileges.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• NIST SP 800-171 Rev. 3 3.4.10 — System Component Inventory
• ISO/IEC 27001:2022 A.8.4 — Access to source code
• SOC 2 (2017 TSC) CC6.8 — Malicious Code Protection

Related controls in NIST SP 800-53 Rev. 5

• Control CM-11(2) — Software Installation With Privileged Status
• Control SI-3(4) — Updates Only By Privileged Users
• Control CM-3(6) — Cryptography Management
• Control CM-5(6) — Limit Library Privileges
• Control CM-5(4) — Dual Authorization
• Control CM-8(5) — No Duplicate Accounting Of Components

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control CM-7(6)

Topics: identity accessidentity managementaccess reviewprivileged accessphysical security