3.7.5Require MFA for remote maintenance, and hang up after in Rev. 3

Reworded: 03.07.05 Nonlocal Maintenance.

Status as of 2026-09-08

Rev. 2 is what a contract requires today. DFARS 252.204-7012 and the CMMC rule at 32 CFR 170 point at NIST SP 800-171 Rev. 2, and a standing DoD class deviation keeps it there. NIST has published Rev. 3, but publishing a revision does not change an obligation. A move to Rev. 3 would arrive through the Department's reform process and formal rulemaking, a change to that deviation or an amendment to the rule, not through publication. The Department has published its organization-defined parameter values for Rev. 3 in preparation; that is groundwork, not adoption.

Side by side

Rev. 2 · in force 3.7.5 Nonlocal Maintenance

Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.

Assessment objectives · 800-171A

[a] nonlocal maintenance sessions are established via secure connections
[b] multifactor authentication is used to establish nonlocal maintenance sessions via external network connections
[c] nonlocal maintenance sessions are terminated when nonlocal maintenance is complete

Rev. 3 · not adopted 03.07.05 Nonlocal Maintenance

a. Approve and monitor nonlocal maintenance and diagnostic activities.

b. Implement multi-factor authentication and replay resistance in the establishment of nonlocal maintenance and diagnostic sessions.

c. Terminate session and network connections when nonlocal maintenance is completed.

Determination statements · 800-171A Rev. 3

03.07.05.a[01] nonlocal maintenance and diagnostic activities are approved.
03.07.05.a[02] nonlocal maintenance and diagnostic activities are monitored.
03.07.05.b[01] multi-factor authentication is implemented in the establishment of nonlocal maintenance and diagnostic sessions.
03.07.05.b[02] replay resistance is implemented in the establishment of nonlocal maintenance and diagnostic sessions.
03.07.05.c[01] session connections are terminated when nonlocal maintenance is completed.
03.07.05.c[02] network connections are terminated when nonlocal maintenance is completed.

Draws on Rev. 2 3.7.5.

Left: NIST SP 800-171 Rev. 2 and 800-171A, verbatim. Right: NIST SP 800-171 Rev. 3 and 800-171A Rev. 3, verbatim, with organization-defined blanks highlighted.

Word by word

The Rev. 2 requirement compared with its Rev. 3 successor. A mechanical comparison of the two verbatim texts, not an interpretation.

~~removed in Rev. 3~~ added in Rev. 3

Rev. 2 3.7.5 → Rev. 3 03.07.05 Nonlocal Maintenance

~~Require multifactor~~ Approve and monitor nonlocal maintenance and diagnostic activities. Implement multi-factor authentication ~~to establish~~ and replay resistance in the establishment of nonlocal maintenance ~~sessions via external network connections~~ and diagnostic sessions. Terminate ~~such~~ session and network connections when nonlocal maintenance is ~~complete.~~ completed.

10 words kept, 11 removed, 23 added. Rev. 3 statement labels omitted for the comparison.

What NIST says changed

New security requirement title
Aligned with SP 800-53, Rev 5 to provide more comprehensive detail on and foundational tasks for nonlocal maintenance

NIST, SP 800-171 Rev. 2 to Rev. 3 change analysis, class “Minor change”. At adoption, Bedrock files this under “Review”.

NIST's Rev. 3 discussion for 03.07.05

Nonlocal maintenance and diagnostic activities are conducted by individuals who communicate through an external or internal network. Local maintenance and diagnostic activities are carried out by individuals who are physically present at the location of the system and not communicating across a network connection. Authentication techniques used to establish nonlocal maintenance and diagnostic sessions reflect the requirements in <a href="#/cprt/framework/version/SP_800_171_3_0_0/home?element=03.05.01">03.05.01</a>.

What this means for you now

Nothing changes in what you are assessed against until a class deviation or a published rule adopts Rev. 3. Keep meeting 3.7.5 as written in Rev. 2.

Bedrock CMMC shows this same comparison against your own package, with your current status on the Rev. 2 side, so the day adoption lands the migration is a review, not a rewrite.

Back to the Rev. 2 vs Rev. 3 overview

Where this page's facts come from

Rev. 2 text and objectives: bedrock-cmmc-api@89b8e8e:migrations/004_reference_requirements.sql#Requirement.basicRequirement@rev2; bedrock-cmmc-api@89b8e8e:migrations/005_reference_objectives.sql#AssessmentObjective.description@rev2
Mapping and change class: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/r2_r3_transition_map.json#r2_to_r3
Rev. 3 03.07.05: bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]