EvidenceSheet
NIST SP 800-53 Rev 5 · CM - Configuration Management

CM-7(2) Least Functionality | Prevent Program Execution

Prevent program execution in accordance with Selection (one or more): [organization-defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions; rules authorizing the terms and conditions of software program usage].

Source: NIST SP 800-53 Rev 5, CM-7(2). 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 NIST SP 800-53 Rev 5 in the compliance library.

Base controls and their enhancements. Which apply follows the baseline you are assessed against (for example FedRAMP Moderate or High, or the low, moderate and high baselines of SP 800-53B). Text in square brackets is a parameter your organisation sets.

10
artefacts
1
held by a system
1
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

  • Change control records · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Test of Organizational processes preventing program execution on the system; organizational processes for software program usage and restrictions; mechanisms preventing program execution on the system; mechanisms supporting and/or implementing software program usage and restrictions · Cloud console / configuration management

governing documentDocuments that govern the control

  • Configuration management policy · Policy repository / GRC workspace
  • Procedures addressing least functionality in the system · Policy repository / GRC workspace
  • Configuration management plan · Policy repository / GRC workspace
  • System design documentation · Policy repository / GRC workspace
  • System configuration settings and associated documentation · Policy repository / GRC workspace
  • System component inventory · Policy repository / GRC workspace
  • Common secure configuration checklists · Policy repository / GRC workspace
  • Specifications for preventing software program execution · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management 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-7(1) Least Functionality | Periodic Review · CM-7(3) Least Functionality | Registration Compliance