CM.L2-3.4.6 Least Functionality
Configure systems to provide only the capabilities that are essential, applying the principle of least functionality.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Cloud console / configuration management
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration evidence showing nonessential capabilities removed · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Periodic review of enabled capabilities · Cloud console / configuration management
governing documentDocuments that govern the control
- Documented determination of essential capabilities per system type · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Cloud console / configuration management); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Default installations left intact
- Essential capability never actually defined
- Review performed without removing anything
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 sheetCM.L2-3.4.5 Access Restrictions for Change · CM.L2-3.4.7 Nonessential Functionality