3.13.7Block split tunneling in Rev. 3
Withdrawn and incorporated elsewhere: 03.01.12 Remote Access, 03.04.02 Configuration Settings, 03.04.06 Least Functionality.
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.13.7 Split Tunneling
Assessment objectives · 800-171A
- [a] remote devices are prevented from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling)
Rev. 3 · not adopted 03.01.12 Remote Access
a. Establish usage restrictions, configuration requirements, and connection requirements for each type of allowable remote system access.
b. Authorize each type of remote system access prior to establishing such connections.
c. Route remote access to the system through authorized and managed access control points.
d. Authorize the remote execution of privileged commands and remote access to security-relevant information.
Determination statements · 800-171A Rev. 3
- 03.01.12.a[01] types of allowable remote system access are defined.
- 03.01.12.a[02] usage restrictions are established for each type of allowable remote system access.
- 03.01.12.a[03] configuration requirements are established for each type of allowable remote system access.
- 03.01.12.a[04] connection requirements are established for each type of allowable remote system access.
- 03.01.12.b each type of remote system access is authorized prior to establishing such connections.
- 03.01.12.c[01] remote access to the system is routed through authorized access control points.
- 03.01.12.c[02] remote access to the system is routed through managed access control points.
- 03.01.12.d[1] remote execution of privileged commands is authorized.
- 03.01.12.d[2] remote access to security-relevant information is authorized.
Rev. 3 · not adopted 03.04.02 Configuration Settings
a. Establish, document, and implement the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements: [Assignment: organization-defined configuration settings].
b. Identify, document, and approve any deviations from established configuration settings.
Determination statements · 800-171A Rev. 3
- 03.04.02.a[01] the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements are established and documented: <A.03.04.02.ODP[01]: configuration settings>.
- 03.04.02.a[02] the following configuration settings for the system are implemented: <A.03.04.02.ODP[01]: configuration settings>.
- 03.04.02.b[01] any deviations from established configuration settings are identified and documented.
- 03.04.02.b[02] any deviations from established configuration settings are approved.
Organization-defined parameters
- A.03.04.02.ODP[01] configuration settings for the system that reflect the most restrictive mode consistent with operational requirements are defined.
Rev. 3 · not adopted 03.04.06 Least Functionality
a. Configure the system to provide only mission-essential capabilities.
b. Prohibit or restrict use of the following functions, ports, protocols, connections, and services: [Assignment: organization-defined functions, ports, protocols, connections, and services].
c. Review the system [Assignment: organization-defined frequency] to identify unnecessary or nonsecure functions, ports, protocols, connections, and services.
d. Disable or remove functions, ports, protocols, connections, and services that are unnecessary or nonsecure.
Determination statements · 800-171A Rev. 3
- 03.04.06.a the system is configured to provide only mission-essential capabilities.
- 03.04.06.b[01] the use of the following functions is prohibited or restricted: <A.03.04.06.ODP[01]: functions>.
- 03.04.06.b[02] the use of the following ports is prohibited or restricted: <A.03.04.06.ODP[02]: ports>.
- 03.04.06.b[03] the use of the following protocols is prohibited or restricted: <A.03.04.06.ODP[03]: protocols>.
- 03.04.06.b[04] the use of the following connections is prohibited or restricted: <A.03.04.06.ODP[04]: connections>.
- 03.04.06.b[05] the use of the following services is prohibited or restricted: <A.03.04.06.ODP[05]: services>.
- 03.04.06.c the system is reviewed <A.03.04.06.ODP[06]: frequency> to identify unnecessary or nonsecure functions, ports, protocols, connections, and services.
- 03.04.06.d unnecessary or nonsecure functions, ports, protocols, connections, and services are disabled or removed.
Organization-defined parameters
- A.03.04.06.ODP[01] functions to be prohibited or restricted are defined.
- A.03.04.06.ODP[02] ports to be prohibited or restricted are defined.
- A.03.04.06.ODP[03] protocols to be prohibited or restricted are defined.
- A.03.04.06.ODP[04] connections to be prohibited or restricted are defined.
- A.03.04.06.ODP[05] services to be prohibited or restricted are defined.
- A.03.04.06.ODP[06] the frequency at which to review the system to identify unnecessary or nonsecure functions, ports, protocols, connections, or services is defined.
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 each Rev. 3 requirement it feeds into. A mechanical comparison of the two verbatim texts, not an interpretation.
removed in Rev. 3 added in Rev. 3
Rev. 2 3.13.7 → Rev. 3 03.01.12 Remote Access
5 words kept, 20 removed, 49 added. Rev. 3 statement labels omitted for the comparison.
Rev. 2 3.13.7 → Rev. 3 03.04.02 Configuration Settings
2 words kept, 23 removed, 33 added. Rev. 3 statement labels omitted for the comparison.
Rev. 2 3.13.7 → Rev. 3 03.04.06 Least Functionality
3 words kept, 22 removed, 57 added. Rev. 3 statement labels omitted for the comparison.
What NIST says changed
Rev. 3 withdraws this requirement as a separate item and folds it into other requirements. NIST's note: Addressed by 03.01.12, 03.04.02 and 03.04.06.
NIST's Rev. 3 discussion for 03.01.12
Remote access is access to systems (or processes acting on behalf of users) that communicate through external networks, such as the internet. Monitoring and controlling remote access methods allows organizations to detect attacks and ensure compliance with remote access policies. Routing remote access through managed access control points enhances explicit control over such connections and reduces susceptibility to unauthorized access to the system, which could result in the unauthorized disclosure of CUI. Remote access to the system represents a significant potential vulnerability that can be exploited by adversaries. Restricting the execution of privileged commands and access to security-relevant information via remote access reduces the exposure of the organization and its susceptibility to threats by adversaries. A privileged command is a human-initiated command executed on a system that involves the control, monitoring, or administration of the system, including security functions and security-relevant information. Security-relevant information is information that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions.
NIST's Rev. 3 discussion for 03.04.02
Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system and that affect the security posture or functionality of the system. Security-related configuration settings can be defined for systems (e.g., servers, workstations), input and output devices (e.g., scanners, copiers, printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications. Security parameters are those parameters that impact the security state of the system, including the parameters required to satisfy other security requirements. Security parameters include registry settings; account, file, and directory permission settings (i.e., privileges); and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for the system. The established settings become part of the system’s configuration baseline. Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, and security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations, including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors.
NIST's Rev. 3 discussion for 03.04.06
Systems can provide a variety of functions and services. Some functions and services that are routinely provided by default may not be necessary to support essential organizational missions, functions, or operations. It may be convenient to provide multiple services from single system components. However, doing so increases risk over limiting the services provided by any one component. Where feasible, organizations limit functionality to a single function per component. Organizations review the functions and services provided by the system or system components to determine which functions and services are candidates for elimination. Organizations disable unused or unnecessary physical and logical ports and protocols to prevent the unauthorized connection of devices, the transfer of information, and tunneling. Organizations can employ network scanning tools, intrusion detection and prevention systems, and endpoint protection systems (e.g., firewalls and host-based intrusion detection systems) to identify and prevent the use of prohibited functions, ports, protocols, system connections, and services. Bluetooth, File Transfer Protocol (FTP), and peer-to-peer networking are examples of the types of protocols that organizations consider eliminating, restricting, or disabling.
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.13.7 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.
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.01.12
- bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]
- Rev. 3 03.04.02
- bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]
- Rev. 3 03.04.06
- bedrock-cmmc-api@89b8e8e:docs/reference/nist-800-171-rev3/normalized/rev3.json#requirements[]