CA.L3-3.12.1e
Penetration Testing
Requirement
Assessment objectives
An assessor checks each lettered objective separately. The letters in brackets elsewhere on this page, such as [a] or [b,c], refer to these.
Determine if:
- aAutomated scanning tools are identified;
- bAd hoc tests using subject matter experts are identified; and
- cPenetration testing is conducted at least annually or when significant security changes are made to the system, leveraging automated scanning tools and ad hoc tests using subject matter experts.
From the CMMC Level 3 Assessment Guide v2.13 · publisher approved 2026-11-08.
How to implement
Have your CUI environment penetration tested at least once a year and after significant security changes, using both automated scanning tools and hands-on tests by skilled people. Level 2 vulnerability scanning is not enough on its own; Level 3 expects people trying to break in the way an attacker would, then remediating what they find. Most small contractors hire a qualified outside firm, which is a recurring cost; the guide also allows an internal team with the skills and the objectivity to do it (L3 guide p.72).
The minimum for a small organization · Expert CMMC's reading, not official text
Name the automated scanning tools [a] and the hands-on tests by subject matter experts [b] your penetration testing uses, and run a penetration test that combines them at least annually, and again when significant security changes are made to the system [c]; the guide's "or when" lists both as triggers. Most small Level 3 contractors hire a qualified outside firm, track the findings to closure, and record after each significant change whether a new test is needed.
Required outcome: what the requirement or its objectives call for. Recommended way: one common way to get there. Going further: worth doing, more than this practice asks.
- 1
- 2Required outcomeProcessConduct penetration testing at least annually, and again when significant security changes are made to the system, using the automated scanning tools and ad hoc tests by subject matter experts.[c]
You can tell it worked when a penetration test report from within the last twelve months, and from after the latest significant change, describes both automated and manual testing.
- 3Recommended wayPolicySet the penetration testing policy: at least annually and after significant security changes (new network segment, major cloud migration, new internet-facing service, replacement of a core security tool), with defined scope, rules of engagement, tester qualifications and independence, and how findings are remediated.[c]
- 4Recommended wayProcessScope each test to the CUI environment and its supporting systems: external perimeter and internet-facing services, internal network from an assumed-breach position, identity and cloud tenant (for example the Microsoft 365 or Google Workspace tenant that holds CUI), wireless, custom web applications, and social engineering if the threat profile warrants it. Base scenarios on the threat-informed risk assessment.[c]
- 5Recommended wayProcessEngage qualified testers (an outside firm, or an internal team independent of the system administrators) who combine automated scanning tools with manual, ad hoc testing by subject matter experts. Sign rules of engagement and an authorization letter, and handle the report as sensitive.[a][b][c]
- 6Recommended wayProcessRemediate findings by risk, track them in the plan of action (CA.L2-3.12.2), and retest critical and high findings to confirm closure.[c]
- 7Recommended wayProcessMaintain the change triggers: when a significant security change is approved through change management, decide and record whether an additional test is required.[c]
Evidence to collect
Artifacts that show the practice is implemented and operating. Tags show which assessment objectives each one supports.
A process you started recently is shown honestly by its dated procedure, the first record it produced and the date it began. No evidence row needs more history than the process has existed, and the review periods shown are suggestions unless a guide page or regulation is named beside them.
Penetration testing policy[c]
Rules of engagement and authorization[c]
Remediation and retest evidence[c]
Change-triggered test decisions[c]
The detail for 5 evidence items: how to produce each, how fresh it must be, what it must include and what it does not show.
Free with an account. Create a free account or sign in.
How assessors check
What an assessor examines, asks and tests: 3 notes.
Free with an account. Create a free account or sign in.
Tools and products
Named options a contractor can adopt, with an honest cost tier. The industry standard is listed even when it is expensive, alongside what is free and acceptable for a very small shop.
Notes on 5 products for this practice: why each matters here, what it assumes and what stays yours.
Free with an account. Create a free account or sign in.
Editorial mentions, not endorsements. Pricing and tiers change; confirm with the vendor and check FedRAMP or GCC High availability where CUI is involved.
Common pitfalls
- Presenting an automated vulnerability scan as a penetration test.
- Testing only the external IP addresses and not the internal network or cloud tenant.
- Findings from last year's test still open with no plan of action entry.
- No retest after a major change such as moving to GCC High or replacing the firewall.
- Testers given no authorization letter, creating legal and operational risk.
Platform notes
- Microsoft 365 (GCC / GCC High)
- Google Workspace
- On-premises or MSP-managed
Notes for 3 platforms.
Free with an account. Create a free account or sign in.
Related practices: CA.L2-3.12.1, RA.L2-3.11.2, RA.L3-3.11.5e, CA.L2-3.12.2, CM.L2-3.4.4
Editorial implementation guidance published November 14, 2026. It is not part of the official requirement and does not replace the assessment guide.
Crosswalk
Full crosswalkThe NIST requirements this practice is built on, what NIST made of each in the newer edition, and the SP 800-53 controls behind them, each from an official NIST or DoD table. Open any one to read it and see every CMMC practice it supports.
NIST SP 800-172 (Feb 2021)
3.12.1eSP 800-172 Rev 3
03.12.01E—
SP 800-53 Rev 5
CA-8CSSR-6(1)CHow these were reachedHide how these were reached
- CA-8 · Penetration Testing
- S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL) · via 800-172 Rev 3 03.12.01E → 800-53 Rev 5 CA-8
- C SP 800-172 (Feb 2021) Appendix C
- SR-6(1) · Supplier Assessments and Reviews | Testing and Analysis
- C SP 800-172 (Feb 2021) Appendix C
Rev 5 paths: D SP 800-171 Rev 2 Appendix D → SP 800-53 Rev 4 control → NIST's Rev 4 → Rev 5 comparison; S source control of the SP 800-171 Rev 3 or SP 800-172 Rev 3 requirement (NIST OSCAL); C SP 800-172 (Feb 2021) Appendix C. NIST also names this Rev 3 requirement as the successor of other withdrawn requirements: open “How these were reached” under the Rev 5 controls for which, in NIST's words.
Where each link comes from (5 links from 4 official documents)
32 CFR 170.14 Office of the Federal Register / GPO
- CA.L3-3.12.1e → 3.12.1e“Level 3 security requirement”32 CFR 170.14(c)(4), Table 1, item (xx)
Trace notes
Notes marked NIST state what the owners' own files say. Notes marked Expert CMMC note are our reading of the links, not official guidance. Neither is a crosswalk link.
About this practice
Expert CMMC note
SR-6(1) is in 800-172 Appendix C because it carries forward Rev 4 SA-12(11) (penetration testing/analysis of supply chain elements). It covers supply-chain testing, not penetration testing of the system; 800-172 Rev 3 dropped it.
Relies on: NIST SP 800-172 (Feb 2021); NIST SP 800-172 Rev 3; NIST SP 800-53 Rev 5 (OSCAL, release 5.2.0)
Further discussion
Practice guide notes
Implementation guidance
Editorial examples to help you plan. Adapt them to your environment; the official requirement and objectives remain authoritative.
In plain language
Have penetration tests done at least yearly and after significant security changes, using automated scanning plus manual testing by experts.
Implementation example
Example from the source assessment guide (not a mandatory implementation): You are responsible for information security in your organization. Leveraging a contract managed by the CIO, you hire an external expert penetration team annually to test the security of the organization’s enclave that stores and processes CUI [a,c]. You hire the same firm annually or on an ad hoc basis when significant changes are made to the architecture or components that affect security [b,c].
Evidence examples
Examples suggested by the source guide (not an exhaustive or mandatory checklist): Security assessment policy; procedures addressing penetration testing; security plan; security assessment plan; penetration test report; security assessment report; security assessment evidence; other relevant documents or records
Common mistakes
Treating an automated vulnerability scan as a penetration test.
Track this in a workspace
The compliance workspace tracks each objective, its evidence and the tasks to close gaps. It is open to invited contractors while in pilot: request access below.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Source: DoD CIO · https://dodcio.defense.gov/CMMC/