CM.L2-3.4.7 Nonessential Functionality
Prevent nonessential programs, functions, ports, protocols and services from being used, by restricting or disabling each one identified as unnecessary.
3
artefacts
1
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Configuration and scan evidence showing they are disabled or blocked · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Exception records with justification · Cloud console / configuration management
governing documentDocuments that govern the control
- List of prohibited or restricted programs, ports, protocols and services · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- Ports and services addressed but programs and functions ignored
- Blocking at perimeter only while hosts remain open
- Exceptions granted permanently without review
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.6 Least Functionality · CM.L2-3.4.8 Application Execution Policy