---
title: "NIST 800-171 3.11.2 (RA.L2-3.11.2): Vulnerability Scanning"
description: "NIST SP 800-171 3.11.2 Vulnerability Scanning: 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/risk-assessment/3.11.2
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/risk-assessment/3.11.2
records: 7
digest: sha3:0f05ffbb5ac8e4b6ea9251168ba209a64327db0ce4a6e2b6ff5c55b2d63c56ee
---

# NIST 800-171 3.11.2 (RA.L2-3.11.2): Vulnerability Scanning

NIST 800-171 / Risk Assessment / 3.11.2

"Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified." ([NIST SP 800-171 Rev. 2, requirement 3.11.2](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice RA.L2-3.11.2.

## What 3.11.2 means in practice

Scan systems and applications for vulnerabilities on a schedule and whenever a relevant new vulnerability is announced. The scans cover everything inside the boundary, including network devices, printers and cloud resources, and use current vulnerability definitions.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: RA.L2-3.11.2
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.11.2

NIST SP 800-171A gives 5 determination statements for 3.11.2, each found satisfied or other than satisfied. Determine if:

- 3.11.2[a] the frequency to scan for vulnerabilities in organizational systems and applications is defined.
- 3.11.2[b] vulnerability scans are performed on organizational systems with the defined frequency.
- 3.11.2[c] vulnerability scans are performed on applications with the defined frequency.
- 3.11.2[d] vulnerability scans are performed on organizational systems when new vulnerabilities are identified.
- 3.11.2[e] vulnerability scans are performed on applications when new vulnerabilities are identified.

[NIST SP 800-171A (June 2018), assessment objectives for 3.11.2](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.11.2 is met

- The defined scanning frequency.
- Scan reports covering systems and applications over a recent period.
- A scan run after a significant new vulnerability was announced.

## How PolicyCortex gathers the evidence

PolicyCortex reads this evidence with the collectors below, read only, and grades 3.11.2 from it. Each line says what the product checks.

- **Microsoft Defender for Cloud: Recommendations and assessments.** Reads Microsoft Defender for Cloud assessments and checks that vulnerability scanning is on and that its findings are tracked by severity.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.11.2 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-RA)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 3 Risk Assessment requirements (3.11).](https://policycortex.com/nist-800-171/risk-assessment)
- **Previous**: [3.11.1: Risk Assessment](https://policycortex.com/nist-800-171/risk-assessment/3.11.1)
- **Next**: [3.11.3: Fixing Vulnerabilities](https://policycortex.com/nist-800-171/risk-assessment/3.11.3)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | d59e14086ace | 35377eaae093 |
| REC 0001 | MEANING | 5d1d52880368 | d59e14086ace |
| REC 0002 | POINTS AND POA&M | 5050809103d3 | 5d1d52880368 |
| REC 0003 | ASSESSMENT OBJECTIVES | 7e89bf350cf5 | 5050809103d3 |
| REC 0004 | EVIDENCE | bc9e955eff83 | 7e89bf350cf5 |
| REC 0005 | COLLECTORS | 5eae1dafeaba | bc9e955eff83 |
| REC 0006 | RELATED | 0f05ffbb5ac8 | 5eae1dafeaba |

Head sha3:0f05ffbb5ac8e4b6ea9251168ba209a64327db0ce4a6e2b6ff5c55b2d63c56ee. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.