The CMMC vulnerability scanning requirement is NIST SP 800-171 Rev 2 requirement 3.11.2: scan your systems and applications for vulnerabilities on a schedule you define, and scan again when a new vulnerability that affects them is announced. You need a written frequency, scan results that prove you followed it, and evidence that you rescanned when something new came out.
It does not require an expensive product or a security team. A small shop can meet 3.11.2 with a free open source scanner, the vulnerability reporting already built into some endpoint protection products, or a provider who runs scans for you. What it cannot skip is the record. This post covers the requirement, the five assessment objectives behind it, what it is worth on your SPRS score, and a setup a 10 person company can run.
What 3.11.2 says
The requirement text in NIST SP 800-171 Rev 2 reads: scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
The discussion section that follows adds three useful points. First, scanning covers all system components, and NIST names networked printers, scanners and copiers as sources that get overlooked. Second, scanning includes patch levels, ports and services that should not be reachable, and misconfigured information flow controls. Third, it suggests tools that report findings by Common Vulnerabilities and Exposures (CVE) identifier and score them with the Common Vulnerability Scoring System (CVSS). Those are suggestions, not mandates, but almost every current scanner does both.
It sits in the Risk Assessment family next to two related requirements:
| Requirement | Plain English | SPRS points |
|---|---|---|
| 3.11.1 | Periodically assess risk to operations, assets and people from running your systems and handling CUI | 3 |
| 3.11.2 | Scan systems and applications for vulnerabilities on a schedule and when new ones are announced | 5 |
| 3.11.3 | Fix vulnerabilities in line with your risk assessment | 1 |
Point values come from the NIST SP 800-171 DoD Assessment Methodology, version 1.2.1, which lists 3.11.2 among the requirements worth a full 5 points.
The five assessment objectives
NIST SP 800-171A splits 3.11.2 into five objectives. An assessor, or you during a self-assessment, must be able to answer yes to each one:
- 3.11.2[a] The frequency to scan systems and applications is defined.
- 3.11.2[b] Systems are scanned at that frequency.
- 3.11.2[c] Applications are scanned at that frequency.
- 3.11.2[d] Systems are scanned when new vulnerabilities are identified.
- 3.11.2[e] Applications are scanned when new vulnerabilities are identified.
Two things trip small shops up. The first is [a]: you scan "every so often" but never wrote a number down, so there is nothing to measure against. The second is [c] and [e]: a network scan of open ports shows your devices but says little about the software on them. You need visibility into installed applications and their versions, which usually means a scan that signs in to each machine (often called an authenticated or credentialed scan) or an agent on each device. NIST notes that privileged access makes scanning more thorough.
800-171A lists what an assessor may examine: procedures for vulnerability scanning, the system security plan (SSP), scanner configuration, scan results, and patch and vulnerability management records. They may also interview whoever runs the scans and whoever fixes what they find. Our post on 800-171A assessment objectives explains how objectives are judged.
Why 3.11.2 matters for your SPRS score and Level 2
At 5 points, an unmet 3.11.2 costs as much as missing multifactor authentication. It also matters beyond the number. Under 32 CFR 170.21, a Conditional Level 2 status requires a score of at least 80 percent and no requirement worth more than 1 point on the plan of action and milestones (POA&M), with a narrow exception for 3.13.11. So 3.11.2 has to be met, not planned, if you want CMMC Level 2 (Self). 3.11.3, worth 1 point, is one you could place on a POA&M while you work through a backlog of fixes.
The same scan feeds other requirements. Finding missing patches supports 3.14.1 (identify, report and correct system flaws, also 5 points), and finding unneeded open services supports 3.4.7 (restrict nonessential programs, ports and services). Our list of the 5-point controls shows where scanning fits in the fix order, and the free SPRS calculator shows the effect on your own score.
Free and low-cost ways to meet 3.11.2
No specific product is required. Pick the option that covers both systems and applications, then write down how you use it.
| Option | What it covers | Good fit when |
|---|---|---|
| Open source scanner (for example Greenbone Community Edition, built on OpenVAS) | Internal network and, with credentials, installed software | Someone on staff is comfortable running a server tool |
| Vulnerability reporting in your endpoint protection product | Software versions and missing updates on enrolled devices | You already license a product that includes it |
| NSA DIB Cybersecurity Services | Your internet-facing assets, no cost | You hold a DoD contract or access non-public DoD information |
| CISA Cyber Hygiene vulnerability scanning | Your internet-facing addresses, no cost | You want a second external view on a weekly report |
| Managed service provider scans | Whatever the contract says | You already pay an MSP for IT |
The government options. The NSA DIB Cybersecurity Services program offers no-cost attack surface management to defense industrial base companies, prime or sub, with an active DoD contract or access to non-public DoD information. CISA's Cyber Hygiene Services include free vulnerability scanning for public and private critical infrastructure organizations, and the defense industrial base is one of the critical infrastructure sectors. Both look only at what faces the internet. They are a strong addition, and they will find an exposed remote access port before an attacker does, but on their own they do not reach the laptops and servers inside your network, so they do not satisfy [b] through [e] by themselves.
If you use an MSP. A provider can run the scans, but you still own the requirement. Ask for the schedule in writing, the scope (which devices and applications), and a copy of every report. Our guide on MSPs and CMMC covers how to document who does what.
A frequency you can defend
NIST does not set the frequency. You define it under [a] and then prove you kept to it. Our suggestion, not a rule: scan monthly at a minimum, scan after any significant change such as a new server or firewall rule, and run an extra scan within a few days whenever a widely publicized vulnerability affects software you use. Monthly lines up with the regular patch cycle most vendors follow, so each scan also confirms the last round of updates went in.
For the "when new vulnerabilities are identified" objectives, you need a trigger. Subscribe to vendor security notices for the products you run, or watch the CISA Known Exploited Vulnerabilities catalog. When something relevant appears, scan, save the result, and note the date and the reason. That note is your evidence for [d] and [e].
What to do this week
- List what is in scope: every computer, server, firewall, printer and copier that touches CUI, plus the main applications on them. Your scoping work should already have this.
- Pick a scanner from the table above that can see installed software, not only open ports.
- Write one paragraph in your SSP: the tool, the frequency, the trigger for extra scans, who runs it and where results are kept.
- Run the first scan and save the report with the date in the file name.
- Sort findings by severity and record a target fix date for each. That record covers 3.11.3.
- Put the next scan date on a calendar with a named owner.
- If you hold a DoD contract, email NSA about enrolling in its no-cost external scanning.
Evidence an assessor will ask for
- The written frequency and trigger, in your SSP or a short procedure
- Dated scan reports going back at least a few cycles
- Proof that applications were covered, such as a software inventory section in the report
- At least one out-of-cycle scan tied to a named new vulnerability
- A remediation log showing what you fixed, when, and why you accepted anything you did not fix
CMMC Map, CMMC compliance software for small defense contractors, walks you through 3.11.2 objective by objective in the free assessment and keeps the evidence list with the requirement, so the paragraph for your SSP is written once and stays current.
See what 3.11.2 is costing your score
The free CMMC Map assessment scores 3.11.2 alongside the other 109 requirements and shows which gaps block Level 2 (Self).
Start free in CMMC Map