CMMC Personnel Screening: A 3.9.1 and 3.9.2 Checklist
Hire veterans who are ready for the job
We turn real military records into clear, civilian resumes so your hiring team can see what each veteran actually did.
CMMC Level 2 requirement 3.9.1 says to "screen individuals prior to authorizing access to organizational systems containing CUI." Requirement 3.9.2 says those systems must be protected "during and after personnel actions such as terminations and transfers."
Both lines come word for word from NIST SP 800-171 Rev 2. The reason is 32 CFR 170.14(c)(3). It says the Level 2 requirements "are identical to the requirements in NIST SP 800-171 R2."
By the end you'll have a day-one CMMC personnel screening checklist. Each step lists the evidence to keep in the file. You'll also get the offboarding and transfer steps, and where a veteran hire's records fit.
What goes on the day-one screening checklist?
These six steps are our checklist for each person who gets a CUI system account. The middle column shows the rule or official guidance each step rests on. The right column is what to keep in the file.
| Step | Requirement | Evidence to keep |
|---|---|---|
| 1. Write the screening standard for each role. | The DoD Level 2 guide calls for "organization-defined screening." It says to "base the types of screening on the requirements for a given position and role." | Personnel security policy. Screening procedure. The section of your system security plan that points to both. |
| 2. Get written consent before you order a background report. | The Fair Credit Reporting Act requires written notice and written consent before you order a job background report. | The signed disclosure and authorization, dated before the report was ordered. |
| 3. Run the checks your standard names for the role. | NIST says screening looks at a person's "conduct, integrity, judgment, loyalty, reliability, and stability." | The completed check results, with the date each one came back. |
| 4. Approve the person in writing. | The one 3.9.1 assessment objective asks if people "are screened prior to authorizing access." | A signed approval with the approver's name and the date. |
| 5. Create the account only after the approval. | Access comes after screening, so the dates have to line up. | The account creation date, which should fall after the approval date. Your list of system accounts. |
| 6. Tie it to your system security plan. | The system security plan is on the 800-171A list of things an assessor can examine for 3.9.1. | The plan section that names the policy, the owner and where records live. |
Step 5 is the one to test yourself. Pull five recent hires. Put each approval date next to the account creation date. If any account came first, you have found a gap before an assessor does. That spot check is our advice. No rule requires it.
Which contracts make this a requirement?
The contract clause is DFARS 252.204-7021. The current version is dated November 2025. It tells you to hold a current CMMC status at the level the contracting officer fills in. That status has to cover every system that handles federal contract information or CUI for the contract.
Under 32 CFR 170.3, CMMC rolls into contracts in four phases. Each phase starts one year after the last one. So check the clause in each new solicitation. The level it names decides if 3.9.1 and 3.9.2 apply to you.
The screening rule lives at Level 2 and up. Level 1 uses the 15 basic items in FAR 52.204-21. None of them is a personnel screening step.
What does an assessor check for 3.9.1 and 3.9.2?
NIST SP 800-171A sets the test. The DoD CMMC Level 2 Assessment Guide repeats the same objectives.
3.9.1 has one objective
- [a]: Individuals are screened before they get access to systems that hold CUI.
To check it, an assessor can examine four things. They're your personnel security policy, screening procedures, screening records and system security plan. They can interview the people who run personnel security and information security. They can also test the screening process itself.
3.9.2 has three objectives
- [a]: A policy or process ends access and credentials when a personnel action happens.
- [b]: Access and credentials actually end in line with the action, such as a termination or a transfer.
- [c]: The system stays protected during and after a transfer.
For 3.9.2, the examine list adds records of transfers and terminations. It also adds your list of system accounts, records of revoked credentials and records of exit interviews. The interview list adds system admins and the people who manage accounts.
So a policy alone will not carry you. The records have to show the policy ran, with dates.
How deep should the screening go for each role?
The rule does not name a check. NIST says screening follows the laws and rules that apply. It also follows "specific criteria established for the level of access required for assigned positions." You set the depth, role by role.
The DoD guide gives one example. A company runs "standard criminal background and credit checks" on everyone it hires before they can touch CUI. The guide shows it as an example. It does not set it as a minimum.
One tiering you could adapt is below. It's our suggestion and does not come from DoD.
- Standard user with CUI access: Identity check, past job check and a criminal history check.
- Admin or privileged user: Everything above, plus any added check your policy ties to privileged access.
- Finance or contracts staff with CUI access: Everything above, plus a credit check where your state allows it.
Two legal limits apply to any tier. Under 15 U.S.C. 1681b(b), you need written disclosure and written approval before you order the report. The notice has to sit in a document by itself. Before you turn someone down based on the report, give them a copy. Include a written summary of their rights.
State and city laws can add more limits on criminal and credit checks. Have counsel review your standard before you roll it out. For credit-check roles, see our guide on screening veterans for roles with a credit check.
One more fence. The Form I-9 under 8 CFR 274a.2 checks identity and work authorization. It does not look at trustworthiness. So a finished I-9 does not meet 3.9.1 by itself.
Does a veteran's security clearance count as CMMC screening?
The rule does not say. Look at the personnel security parts of NIST SP 800-171, 800-171A and the DoD guide. None of them mentions security clearances. They ask you to screen the person and decide before you grant access.
Our reading: A clearance is a separate federal decision about a person. It's strong evidence about the same traits NIST lists. But the rule still asks for your own screening record and your own approval.
So write it into your policy. Say what a verified, current clearance counts for. Then say what you still check on top of it. Then record the verification and your approval in the hire's file, the same as any other step.
Verify the clearance through the proper channel. Do not take a resume line as proof. Our guide on how to verify a veteran's security clearance as an employer covers that part. Classified work brings its own rules under your contract's DD Form 254. See onboarding a cleared veteran under a DD-254.
Where the rest of a veteran's record fits
- Military service: Treat it as past employment in step 3. Check the dates and role the same way your policy checks any job.
- Training on handling sensitive data: It belongs in your security training records. It does not count as screening.
- A pending clearance: It's not a finished decision, so run your full standard. See when a new hire with an interim clearance can start.
Apply the same standard to veterans and non-veterans in the same role. One standard per role is easier to defend and easier to show an assessor.
What are the offboarding steps when someone leaves?
The DoD guide lists three things that "may occur within the defined time frame" when someone leaves. Gear comes back, badges come back and an exit interview happens. It then lists three more steps to "perform": remove CUI access, disable accounts and limit physical access. Run all six as one checklist.
- Disable or close the person's accounts.
- Remove access to every account that reaches CUI.
- Collect company IT gear, such as laptops, phones and storage devices.
- Collect ID badges, access cards and keys.
- Limit their access to physical spaces that hold CUI.
- Hold an exit interview that reminds them not to discuss CUI after they leave.
Keep a dated record for each step.
How fast does access have to come off?
The rule sets no fixed number of hours. NIST says "timely execution is essential for individuals terminated for cause." It adds that some companies disable accounts before telling the person they are being let go.
The DoD guide ties the gear, badges and exit interview to "the defined time frame." Its assessment questions ask if credentials are revoked "within a certain time frame." That's your time frame. The assessor checks your records against the window your own policy sets.
Our suggestion is to disable accounts by the end of the person's last day. For a for-cause exit, disable them before the meeting. Then make sure the timestamps prove you did it.
NIST also notes exit interviews are not always possible. A person may walk off the job or be too ill. Record why it did not happen.
What changes when someone transfers to a new role?
Objective 3.9.2[c] covers transfers. NIST applies it when the move is permanent or long enough to need protection.
The DoD guide's example runs like this. HR tells IT the transfer date. The new manager files a ticket for the access the new role needs. IT adds the new rights and removes the old ones on the official transfer date.
NIST lists what a transfer can involve:
- Keys and badges: Return the old ones and issue new ones.
- Privileges: Change what the person's account can do.
- Accounts: Close old accounts and set up new ones.
- Records: Give access to the official records the person used in the old role.
The trap is the person who moves off a CUI contract and keeps the old access. Keep the transfer ticket with both dates, old access removed and new access added.
Who else falls under your screening: temps, admins and subs?
The rule says "individuals," not "employees." Our reading is that anyone who gets an account on your CUI systems goes through your standard. That includes temps, contractors you bring in and outside IT admins.
Subcontractors that keep CUI on their own systems are a separate case. DFARS 252.204-7021 tells you to flow the right CMMC level down to them. They must also affirm compliance before the subcontract is awarded and every year after. Their screening lives in their program, so ask for proof of their status.
For more, see how subcontractors hire cleared veterans for GovCon.
Rule text comes from NIST SP 800-171 Rev 2 and NIST SP 800-171A. The DoD guide is the CMMC Assessment Guide Level 2, version 2.13 (September 2024). The clause is DFARS 252.204-7021 (November 2025), and the rule is 32 CFR Part 170. Checked November 2026.
What to Do Next
Copy the six-step table into your personnel security procedure. Then run the step 5 date check on your last five hires.
Veterans who held a clearance or handled controlled data in uniform have worked under rules like these. You still run your own screen.
For the billing side of those hires, see mapping veteran experience to LCATs. For cleared staffing in general, see how government contractors hire cleared veterans.
79,061 resumes have been built on Best Military Resume. Reach out to access BMR's veteran talent pool and find veterans for your CUI roles.
Frequently Asked Questions
Does CMMC 3.9.1 require re-screening current employees?
Do we have to screen employees who never touch CUI systems?
Is CMMC Level 2 based on NIST SP 800-171 Rev 3?
Does a Level 2 self-assessment have different screening rules than a C3PAO assessment?
Who confirms each year that we still meet these requirements?
About the author
Brad Tachi is the CEO and founder of Best Military Resume and a 2025 Military Friendly Vetrepreneur of the Year award recipient for overseas excellence. A former U.S. Navy Diver with over 20 years of combined military, private sector, and federal government experience, Brad brings unparalleled expertise to help veterans and military service members successfully transition to rewarding civilian careers. Having personally navigated the military-to-civilian transition, Brad deeply understands the challenges veterans face and specializes in translating military experience into compelling resumes that capture the attention of civilian employers. Through Best Military Resume, Brad has helped thousands of service members land their dream jobs by providing expert resume writing, career coaching, and job search strategies tailored specifically for the veteran community.