What evidence do auditors commonly ask for on CM.L2-3.4.9 User-Installed Software?

Policy governing user installed software; Technical control restricting installation rights; Monitoring output identifying user installed software.

What is the most common gap auditors find on CM.L2-3.4.9?

Users hold local administrator rights so installation is unrestricted

CMMC 2.0 · Configuration Management

`CM.L2-3.4.9` User-Installed Software

Control which software users are able to install, and monitor what has in fact been installed on organizational systems.

Source: CMMC 2.0, CM.L2-3.4.9. 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 CMMC 2.0 in the compliance library.

artefacts

held by a system

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

none for this control

governing documentDocuments that govern the control

Policy governing user installed software · Policy repository / GRC workspace
Technical control restricting installation rights · Policy repository / GRC workspace
Monitoring output identifying user installed software · 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

Users hold local administrator rights so installation is unrestricted
Control present but no monitoring of what was installed
Browser extensions and portable applications out of scope

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.L2-3.4.8 Application Execution Policy · IA.L2-3.5.1 Identification