EvidenceSheet

CM-5(5) Access Restrictions for Change | Privilege Limitation for Production and Operation (CM-5(5))

Access Restrictions for Change | Privilege Limitation for Production and Operation. (a) Limit privileges to change system components and system-related information within a production or operational environment; and (b) Review and reevaluate privileges [

Source: FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline), CM-5(5). The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open FedRAMP Moderate (NIST SP 800-53 Rev 5 baseline) in the compliance library.

A FedRAMP baseline is a subset of NIST SP 800-53 Rev 5, enhancements included.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Configuration evidence that developers and other non-operational roles cannot change production components · Identity provider / directory

periodic reviewEvidence produced at each review

  • User privilege review records at the defined frequency, showing privileges reviewed and reevaluated · Cloud console / configuration management
  • Records of privileges removed or reduced as a result of a review · Cloud console / configuration management

governing documentDocuments that govern the control

  • Documented list of privileges that permit change to system components and system related information in the production or operational environment · Policy repository / GRC workspace
  • Identification of the accounts and roles holding those privileges, extracted from the production environment itself · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Identity provider / directory on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CM-5(1) Access Restrictions for Change | Automated Access Enforcement and Audit Records (CM-5(1)) · CM-6 Configuration Settings