EvidenceSheet
CMMC 2.0 · Maintenance

MA.L2-3.7.4 Media Inspection

Scan media holding diagnostic and test programs for malicious code before that media is connected to organizational systems.

Source: CMMC 2.0, MA.L2-3.7.4. 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.

3
artefacts
1
held by a system
0
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. 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

  • Scan records for media used during maintenance · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Procedure requiring scanning of diagnostic media · Policy repository / GRC workspace
  • Control preventing unscanned media from being connected · 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

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

MA.L2-3.7.3 Equipment Sanitization · MA.L2-3.7.5 Nonlocal Maintenance