---
title: "NIST 800-171 3.14.6 (SI.L2-3.14.6): Attack Monitoring"
description: "NIST SP 800-171 3.14.6 Attack Monitoring: 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/system-and-information-integrity/3.14.6
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/system-and-information-integrity/3.14.6
records: 7
digest: sha3:bbe029efe0afe51f7eb5f0ec62c44cd2035aee5d470aeceb92e1ed186b634eb4
---

# NIST 800-171 3.14.6 (SI.L2-3.14.6): Attack Monitoring

NIST 800-171 / System and Information Integrity / 3.14.6

"Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks." ([NIST SP 800-171 Rev. 2, requirement 3.14.6](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice SI.L2-3.14.6.

## What 3.14.6 means in practice

Monitor systems and network traffic, inbound and outbound, for attacks and signs of attack, using intrusion detection, endpoint detection and log analysis. Outbound traffic matters because it is how stolen data and an attacker's command traffic leave.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: SI.L2-3.14.6
- **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.14.6

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

- 3.14.6[a] the system is monitored to detect attacks and indicators of potential attacks.
- 3.14.6[b] inbound communications traffic is monitored to detect attacks and indicators of potential attacks.
- 3.14.6[c] outbound communications traffic is monitored to detect attacks and indicators of potential attacks.

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

## Evidence that shows 3.14.6 is met

- The monitoring tools in place, such as intrusion detection, endpoint detection and response, and network monitoring.
- Coverage showing both inbound and outbound traffic are monitored.
- Alerts and the records of how they were handled.

## How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.14.6. Your team provides the evidence listed above.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.14.6 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-SI)
- **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 7 System and Information Integrity requirements (3.14).](https://policycortex.com/nist-800-171/system-and-information-integrity)
- **Previous**: [3.14.5: Malware Scanning](https://policycortex.com/nist-800-171/system-and-information-integrity/3.14.5)
- **Next**: [3.14.7: Unauthorized Use](https://policycortex.com/nist-800-171/system-and-information-integrity/3.14.7)
- **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 | eb8509c922f4 | 7a0a2d170a4c |
| REC 0001 | MEANING | be8fdc416af8 | eb8509c922f4 |
| REC 0002 | POINTS AND POA&M | 1313849c646f | be8fdc416af8 |
| REC 0003 | ASSESSMENT OBJECTIVES | bb4eba75b1e3 | 1313849c646f |
| REC 0004 | EVIDENCE | c3a885ff61e5 | bb4eba75b1e3 |
| REC 0005 | COLLECTORS | fb5c7eaba6a2 | c3a885ff61e5 |
| REC 0006 | RELATED | bbe029efe0af | fb5c7eaba6a2 |

Head sha3:bbe029efe0afe51f7eb5f0ec62c44cd2035aee5d470aeceb92e1ed186b634eb4. 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.