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

CM-10 Software Usage Restrictions

a. Use software and associated documentation in accordance with contract agreements and copyright laws; b. Track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and c. Control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work.

Source: NIST SP 800-53 Rev 5, CM-10. 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.

9
artefacts
0
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

none for this control

periodic reviewEvidence produced at each review

  • Software license tracking reports · Cloud console / configuration management
  • Test of Organizational processes for tracking the use of software protected by quantity licenses; organizational processes for controlling/documenting the use of peer-to-peer file sharing technology; mechanisms implementing software license tracking; mechanisms implementing and controlling the use of peer-t · Cloud console / configuration management

governing documentDocuments that govern the control

  • Configuration management policy · Policy repository / GRC workspace
  • Software usage restrictions · Policy repository / GRC workspace
  • Software contract agreements and copyright laws · Vendor register / contract repository
  • Site license documentation · Policy repository / GRC workspace
  • List of software usage restrictions · Policy repository / GRC workspace
  • Configuration management plan · Policy repository / GRC workspace
  • System security plan · Policy repository / GRC workspace

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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-9(1) Configuration Management Plan | Assignment of Responsibility · CM-10(1) Software Usage Restrictions | Open-source Software