Define, document, approve, enforce physical and logical access restrictions for changes.
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 46 controls across 19 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
1.2.8 Configuration files secured and synchronised
7.2.3 Required privileges are approved by authorized personnel
8.4.1 MFA is implemented for all non-console access into the CDE for personnel with administrative access
6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval
NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties
NIST-CSF-PR.AA-06 Physical access to assets is managed, monitored, and enforced commensurate with risk
NIST-CSF-PR.PS-01 Configuration management practices are established and applied
You are reading one control. How much of FedRAMP High have you already done?
FedRAMP High CM-5 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.