EvidenceSheet
CMMC 2.0 · Personnel Security

PS.L2-3.9.2 Personnel Actions

Protect systems containing CUI during and after personnel actions such as termination or transfer, including timely revocation of access.

Source: CMMC 2.0, PS.L2-3.9.2. 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
0
held by a system
2
at each review
hard
to go live
HR system / LMS
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

  • Records showing revocation timing against departure date · Document repository
  • Evidence credentials and property are recovered · Identity provider / directory

governing documentDocuments that govern the control

  • Termination and transfer procedure covering access revocation and asset return · HR system / LMS

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

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

PS.L2-3.9.1 Screen Individuals · RA.L2-3.11.1 Risk Assessments