Skip to main content

The complete map · live from the scored dataset

CMMC Level 2 requirements: all 110 NIST SP 800-171 controls

CMMC Level 2 is the full set of 110 security requirements from NIST SP 800-171 Rev 2, grouped into 14 families. In the SPRS score you start at 110 and subtract each unmet requirement's weight: 44 are worth 5 points, 14 worth 3, and 51 worth 1. One — 3.12.4, the System Security Plan — is unscored (it is a gate, not a weighted line). 47 are POA&M-eligible under 32 CFR 170.21. Explore every one below.

Jump to the 110-control explorer ↓

How the 110 requirements are weighted

Every requirement carries a SPRS point value under the DoD NIST SP 800-171 Assessment Methodology. You begin at a perfect 110 and lose a requirement's points whenever it is not fully met (a requirement is met only when every applicable 800-171A assessment objective is satisfied). The weights cluster into three tiers, plus one special case:

  • 44 requirements are worth 5 points — the highest-impact controls. Two of them, MFA (3.5.3) and FIPS-validated cryptography (3.13.11), allow partial credit: a 3-point deduction instead of 5 when partially in place.
  • 14 requirements are worth 3 points.
  • 51 requirements are worth 1 point.
  • One requirement is unscored: 3.12.4, the System Security Plan. Without a current SSP no assessment can be completed at all, so it functions as a gate rather than a weighted deduction.

That makes the maximum possible deduction 313 points, so a SPRS score runs from a high of 110 down to a floor of -203. Of the 110 requirements, 47 are POA&M-eligible (32 CFR 170.21) and 17 also appear in CMMC Level 1.

Sources: NIST SP 800-171 DoD Assessment Methodology v1.2.1 (Annex A); 32 CFR 170.21 (POA&M eligibility) and 170.24 (Level 2 scoring); requirement text from NIST SP 800-171 Rev 2. The full point-by-point math is on the scoring methodology page, and you can run the deductions yourself in the SPRS calculator.

The 110-control explorer, by family

Every requirement, grouped into the 14 families. Each family is anchored (for example, #AC for Access Control) so you can deep-link straight to it. Filter by weight or search by requirement ID, CMMC ID, or keyword.

Showing 110 of 110 requirements.

AC Access Control

22 requirements
  • AC.L2-3.1.1Level 1

    Limit system access to authorized users

    5 ptsMust fix
  • AC.L2-3.1.2Level 1

    Limit users to permitted transactions and functions

    5 ptsMust fix
  • AC.L2-3.1.3

    Control the flow of CUI

    1 ptPOA&M-eligible
  • AC.L2-3.1.4

    Separate duties to reduce malicious risk

    1 ptPOA&M-eligible
  • AC.L2-3.1.5

    Enforce least privilege for privileged accounts

    3 ptsMust fix
  • AC.L2-3.1.6

    Use non-privileged accounts for routine tasks

    1 ptPOA&M-eligible
  • AC.L2-3.1.7

    Prevent and log privileged function execution

    1 ptPOA&M-eligible
  • AC.L2-3.1.8

    Limit repeated unsuccessful logon attempts

    1 ptPOA&M-eligible
  • AC.L2-3.1.9

    Display privacy and security notices

    1 ptPOA&M-eligible
  • AC.L2-3.1.10

    Lock idle sessions with pattern-hiding displays

    1 ptPOA&M-eligible
  • AC.L2-3.1.11

    Terminate user sessions after defined conditions

    1 ptPOA&M-eligible
  • AC.L2-3.1.12

    Monitor and control remote access sessions

    5 ptsMust fix
  • AC.L2-3.1.13

    Encrypt remote access sessions with cryptographic mechanisms

    5 ptsMust fix
  • AC.L2-3.1.14

    Route remote access through managed control points

    1 ptPOA&M-eligible
  • AC.L2-3.1.15

    Authorize remote privileged commands and security access

    1 ptPOA&M-eligible
  • AC.L2-3.1.16

    Authorize wireless access before allowing connections

    5 ptsMust fix
  • AC.L2-3.1.17

    Protect wireless access with authentication and encryption

    5 ptsMust fix
  • AC.L2-3.1.18

    Control connections of mobile computing devices

    5 ptsMust fix
  • AC.L2-3.1.19

    Encrypt CUI on mobile devices and platforms

    3 ptsMust fix
  • AC.L2-3.1.20Level 1

    Verify and limit external system connections

    1 ptMust fix
  • AC.L2-3.1.21

    Limit portable storage on external systems

    1 ptPOA&M-eligible
  • AC.L2-3.1.22Level 1

    Control CUI on publicly accessible systems

    1 ptMust fix

AT Awareness and Training

3 requirements
  • AT.L2-3.2.1

    Make users aware of security risks

    5 ptsMust fix
  • AT.L2-3.2.2

    Train personnel to perform security duties

    5 ptsMust fix
  • AT.L2-3.2.3

    Provide insider threat awareness training

    1 ptPOA&M-eligible

AU Audit and Accountability

9 requirements
  • AU.L2-3.3.1

    Create and retain system audit logs

    5 ptsMust fix
  • AU.L2-3.3.2

    Trace user actions to unique individuals

    3 ptsMust fix
  • AU.L2-3.3.3

    Review and update logged event types

    1 ptPOA&M-eligible
  • AU.L2-3.3.4

    Alert on audit logging process failures

    1 ptPOA&M-eligible
  • AU.L2-3.3.5

    Correlate audit review, analysis, and reporting

    5 ptsMust fix
  • AU.L2-3.3.6

    Provide audit reduction and report generation

    1 ptPOA&M-eligible
  • AU.L2-3.3.7

    Synchronize system clocks with authoritative source

    1 ptPOA&M-eligible
  • AU.L2-3.3.8

    Protect audit information and logging tools

    1 ptPOA&M-eligible
  • AU.L2-3.3.9

    Restrict audit management to privileged users

    1 ptPOA&M-eligible

CM Configuration Management

9 requirements
  • CM.L2-3.4.1

    Establish and maintain baseline system configurations

    5 ptsMust fix
  • CM.L2-3.4.2

    Enforce security configuration settings for products

    5 ptsMust fix
  • CM.L2-3.4.3

    Track, review, approve, and log changes

    1 ptPOA&M-eligible
  • CM.L2-3.4.4

    Analyze security impact before implementing changes

    1 ptPOA&M-eligible
  • CM.L2-3.4.5

    Enforce access restrictions for system changes

    5 ptsMust fix
  • CM.L2-3.4.6

    Configure systems for essential capabilities only

    5 ptsMust fix
  • CM.L2-3.4.7

    Restrict nonessential programs, ports, and services

    5 ptsMust fix
  • CM.L2-3.4.8

    Apply software allowlisting or denylisting policies

    5 ptsMust fix
  • CM.L2-3.4.9

    Control and monitor user-installed software

    1 ptPOA&M-eligible

IA Identification and Authentication

11 requirements
  • IA.L2-3.5.1Level 1

    Identify system users, processes, and devices

    5 ptsMust fix
  • IA.L2-3.5.2Level 1

    Authenticate users, processes, and devices before access

    5 ptsMust fix
  • IA.L2-3.5.3

    Use multifactor authentication for system access

    5 ptsMust fix
  • IA.L2-3.5.4

    Employ replay-resistant authentication for network access

    1 ptPOA&M-eligible
  • IA.L2-3.5.5

    Prevent identifier reuse for defined period

    1 ptPOA&M-eligible
  • IA.L2-3.5.6

    Disable identifiers after defined inactivity period

    1 ptPOA&M-eligible
  • IA.L2-3.5.7

    Enforce minimum password complexity and change

    1 ptPOA&M-eligible
  • IA.L2-3.5.8

    Prohibit password reuse for specified generations

    1 ptPOA&M-eligible
  • IA.L2-3.5.9

    Allow temporary passwords with immediate change

    1 ptPOA&M-eligible
  • IA.L2-3.5.10

    Store and transmit only cryptographically protected passwords

    5 ptsMust fix
  • IA.L2-3.5.11

    Obscure feedback of authentication information

    1 ptPOA&M-eligible

IR Incident Response

3 requirements
  • IR.L2-3.6.1

    Establish an operational incident-handling capability

    5 ptsMust fix
  • IR.L2-3.6.2

    Track, document, and report security incidents

    5 ptsMust fix
  • IR.L2-3.6.3

    Test the organizational incident response capability

    1 ptPOA&M-eligible

MA Maintenance

6 requirements
  • MA.L2-3.7.1

    Perform maintenance on organizational systems

    3 ptsMust fix
  • MA.L2-3.7.2

    Control maintenance tools, techniques, and personnel

    5 ptsMust fix
  • MA.L2-3.7.3

    Sanitize equipment removed for off-site maintenance

    1 ptPOA&M-eligible
  • MA.L2-3.7.4

    Check maintenance media for malicious code

    3 ptsMust fix
  • MA.L2-3.7.5

    Require multifactor authentication for nonlocal maintenance

    5 ptsMust fix
  • MA.L2-3.7.6

    Supervise maintenance personnel lacking access authorization

    1 ptPOA&M-eligible

MP Media Protection

9 requirements
  • MP.L2-3.8.1

    Protect system media containing CUI

    3 ptsMust fix
  • MP.L2-3.8.2

    Limit CUI media access to authorized users

    3 ptsMust fix
  • MP.L2-3.8.3Level 1

    Sanitize or destroy media before disposal

    5 ptsMust fix
  • MP.L2-3.8.4

    Mark media with required CUI markings

    1 ptPOA&M-eligible
  • MP.L2-3.8.5

    Control and account for transported media

    1 ptPOA&M-eligible
  • MP.L2-3.8.6

    Encrypt CUI on media during transport

    1 ptPOA&M-eligible
  • MP.L2-3.8.7

    Control removable media on system components

    5 ptsMust fix
  • MP.L2-3.8.8

    Prohibit portable storage without identifiable owner

    3 ptsMust fix
  • MP.L2-3.8.9

    Protect confidentiality of backup CUI

    1 ptPOA&M-eligible

PS Personnel Security

2 requirements
  • PS.L2-3.9.1

    Screen individuals before authorizing system access

    3 ptsMust fix
  • PS.L2-3.9.2

    Protect CUI during personnel terminations and transfers

    5 ptsMust fix

PE Physical Protection

6 requirements
  • PE.L2-3.10.1Level 1

    Limit physical access to authorized individuals

    5 ptsMust fix
  • PE.L2-3.10.2

    Protect and monitor facility support infrastructure

    5 ptsMust fix
  • PE.L2-3.10.3Level 1

    Escort visitors and monitor visitor activity

    1 ptMust fix
  • PE.L2-3.10.4Level 1

    Maintain audit logs of physical access

    1 ptMust fix
  • PE.L2-3.10.5Level 1

    Control and manage physical access devices

    1 ptMust fix
  • PE.L2-3.10.6

    Enforce CUI safeguards at alternate worksites

    1 ptPOA&M-eligible

RA Risk Assessment

3 requirements
  • RA.L2-3.11.1

    Periodically assess risk to operations and individuals

    3 ptsMust fix
  • RA.L2-3.11.2

    Scan for system and application vulnerabilities

    5 ptsMust fix
  • RA.L2-3.11.3

    Remediate vulnerabilities according to risk assessments

    1 ptPOA&M-eligible

CA Security Assessment

4 requirements
  • CA.L2-3.12.1

    Periodically assess security control effectiveness

    5 ptsMust fix
  • CA.L2-3.12.2

    Develop plans of action for deficiencies

    3 ptsMust fix
  • CA.L2-3.12.3

    Monitor security controls on ongoing basis

    5 ptsMust fix
  • CA.L2-3.12.4

    Develop and update system security plans

    unscoredMust fix

SC System and Communications Protection

16 requirements
  • SC.L2-3.13.1Level 1

    Monitor and protect communications at boundaries

    5 ptsMust fix
  • SC.L2-3.13.2

    Use secure architecture and engineering principles

    5 ptsMust fix
  • SC.L2-3.13.3

    Separate user functionality from system management

    1 ptPOA&M-eligible
  • SC.L2-3.13.4

    Prevent information transfer via shared resources

    1 ptPOA&M-eligible
  • SC.L2-3.13.5Level 1

    Implement subnetworks for publicly accessible components

    5 ptsMust fix
  • SC.L2-3.13.6

    Deny network traffic by default, allow by exception

    5 ptsMust fix
  • SC.L2-3.13.7

    Prevent split tunneling on remote devices

    1 ptPOA&M-eligible
  • SC.L2-3.13.8

    Encrypt CUI in transit unless otherwise protected

    3 ptsMust fix
  • SC.L2-3.13.9

    Terminate network connections when sessions end

    1 ptPOA&M-eligible
  • SC.L2-3.13.10

    Establish and manage cryptographic keys

    1 ptPOA&M-eligible
  • SC.L2-3.13.11

    Employ FIPS-validated cryptography to protect CUI

    5 ptsPOA&M-eligible
  • SC.L2-3.13.12

    Prohibit remote activation of collaborative devices

    1 ptPOA&M-eligible
  • SC.L2-3.13.13

    Control and monitor use of mobile code

    1 ptPOA&M-eligible
  • SC.L2-3.13.14

    Control and monitor VoIP technologies

    1 ptPOA&M-eligible
  • SC.L2-3.13.15

    Protect authenticity of communications sessions

    5 ptsMust fix
  • SC.L2-3.13.16

    Protect confidentiality of CUI at rest

    1 ptPOA&M-eligible

SI System and Information Integrity

7 requirements
  • SI.L2-3.14.1Level 1

    Identify, report, and correct system flaws

    5 ptsMust fix
  • SI.L2-3.14.2Level 1

    Provide malicious code protection at designated locations

    5 ptsMust fix
  • SI.L2-3.14.3

    Monitor security alerts and take action

    5 ptsMust fix
  • SI.L2-3.14.4Level 1

    Update malicious code protection mechanisms promptly

    5 ptsMust fix
  • SI.L2-3.14.5Level 1

    Perform periodic system and real-time file scans

    3 ptsMust fix
  • SI.L2-3.14.6

    Monitor systems and traffic for attacks

    5 ptsMust fix
  • SI.L2-3.14.7

    Identify unauthorized use of organizational systems

    3 ptsMust fix

"Must fix" marks requirements that are not POA&M-eligible — they must be fully implemented before a Level 2 assessment, per 32 CFR 170.21. Titles are plain-English summaries written for this dataset, not the official CMMC practice names; the verbatim requirement text is NIST SP 800-171 Rev 2. See the Level 1 vs Level 2 guide for the L1 subset.

Straight answers

How many requirements are in CMMC Level 2?

CMMC Level 2 covers all 110 security requirements of NIST SP 800-171 Rev 2, organized into 14 families. They are the same requirements DFARS 252.204-7012 has obligated contractors handling covered defense information to implement since 2017; CMMC Level 2 adds verification on top.

How are the 110 requirements weighted in the SPRS score?

Under the DoD Assessment Methodology you start at 110 and subtract a requirement's point value for each one not met: 44 requirements are worth 5 points, 14 are worth 3, and 51 are worth 1. Two of the 5-point items — MFA (3.5.3) and FIPS-validated cryptography (3.13.11) — allow partial credit (a 3-point deduction instead of 5). The maximum total deduction is 313 points, so the score floor is -203.

Which Level 2 requirement is unscored?

Only one: 3.12.4 (CA.L2-3.12.4), the System Security Plan requirement. It carries no point value because without a current SSP an assessment cannot be completed at all — there is nothing to deduct against, so it is a gate rather than a weighted line item. It is also never POA&M-eligible.

Which Level 2 requirements can sit on a POA&M?

47 of the 110 requirements are POA&M-eligible per 32 CFR 170.21 — generally only the 1-point items, with one exception: 3.13.11 (CUI encryption) qualifies in its 3-point partial case when encryption is deployed but not yet FIPS-validated. Conditional Level 2 status also requires a score of at least 88 of 110, and the eligible items must be closed within 180 days.

Are the Level 2 requirements the same as Level 1?

No. CMMC Level 1 is the 17 requirements (implementing the 15 basic safeguarding requirements of FAR 52.204-21) that apply to Federal Contract Information. Level 2 is the full set of 110 NIST SP 800-171 requirements for Controlled Unclassified Information — Level 1 is a subset, marked with an L1 badge in the explorer below.

This is compliance information, not legal advice. The regulation and methodology documents govern; for contract-specific questions, consult qualified counsel.

Reading the list is one thing. Knowing your score is another.

The free assessment walks all 110 requirements in plain English, computes your SPRS score with the exact DoD methodology, and splits your gaps into POA&M-eligible and must-fix — turning this map into a plan.