EvidenceSheet

CM-7 Least Functionality

Removes supplier-included functionality that the organization does not need and that widens the attack surface.

3
artefacts
0
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Review of delivered functionality against need · Document repository
  • Records of functions and services disabled · Document repository

governing documentDocuments that govern the control

  • Acquisition requirements limiting bundled functionality · Document repository

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

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-6 Configuration Settings · CM-8 System Component Inventory