Quality, Expert-Derived Cybersecurity Documentation To Keep Organizations Secure, Compliant & Resilient  |  Got Questions? +1-307-241-8740
ComplianceForge

NIST 800-171 R2 to R3 Transition Guide

When NIST 800-171 R3 was released, ComplianceForge teamed up with DEFCERT to write the NIST 800-171 R2 to R3 Transition Guide, an Assessment Objective (AO)-level analysis of NIST 800-171A to NIST 800-171A R3.

NIST SP 800-171 Rev 3 was published on May 14, 2024 with significant changes from Rev 2, which NIST withdrew the same day. OMB Circular A-130 expects federal agencies to meet new or updated NIST publications within one year, but contractors must meet the revision named in their contract clauses. DoD contracts (DFARS 252.204-7012) and CMMC Level 2 still reference Rev 2 today (see the current Rev 2 vs Rev 3 status). Planning your documentation around Rev 3 now avoids a second rebuild when the rules change.

CIRCULAR NO. A-130: "For legacy information systems, agencies are expected to meet the requirements of, and be in compliance with, NIST standards and guidelines within one year of their respective publication dates unless otherwise directed by OMB. The one-year compliance date for revisions to NIST publications applies only to new or updated material in the publications. For information systems under development or for legacy systems undergoing significant changes, agencies are expected to meet the requirements of, and be in compliance with, NIST standards and guidelines immediately upon deployment of the systems."

Key Takeaways - NIST 800-171 R2 to R3 Transition Guide
  • NIST SP 800-171 R3 cuts the CUI controls from 110 to 97, but those 97 controls hold 287 discrete requirements, about 2.6 times as many as R2.
  • The 61 Non-Federal Organization (NFO) controls in R2 are gone. Their governance content now sits inside the R3 CUI controls.
  • Assessment Objectives (AOs) grow from 320 in NIST 800-171A to 510 in NIST 800-171A R3, a 59% increase.
  • About one-third of R3 AOs map directly (minimal effort), about one-fifth map indirectly (moderate effort) and nearly half are new or have no clear link (significant effort).
  • 37 NIST 800-171A AOs have no R3 equivalent, which leaves undocumented dependencies in areas like maintenance, roles, inventories and physical security.
  • The DoD CIO set its own values for the R3 Organization-Defined Parameters (ODP) in an April 10, 2025 memorandum.
  • For most organizations, the Supply Chain Risk Management (SCRM) plan is the heaviest lift.
Executive Summary

What Changed From R2 To R3

Looking only at control counts makes the move from NIST 800-171 R2 to NIST 800-171 R3 look smaller than it is. What matters for compliance is how each control is implemented at the Assessment Objective (AO) level. R3 also folds the governance content of the Non-Federal Organization (NFO) controls into the new CUI controls.

Types of ControlsNIST 800-171 R2NIST 800-171 R3
CUI11097 (core controls)
287 (discrete requirements)
NFO610

On paper, the number of CUI controls drops by about 11%. Underneath, the 97 R3 controls contain 287 discrete requirements, 177 more than the 110 controls in R2. NIST 800-171A R3 also has 59% more unique requirements at the AO level.

Assessment ObjectivesNIST 800-171ANIST 800-171A R3
# Unique AO Requirements320510
% Change In AO Requirements-+59%

From a "reasonable person's perspective," about one-third of the R3 AOs map directly to a previous AO and need minimal effort. About one-fifth map indirectly and need some work to remove assumptions. That leaves nearly half of the AOs needing significant effort.

Establishing ContextExpected Level of EffortNIST 800-171A R3 AO Count% of R3 AOs
R3 AOs that directly map to previous version AOsMinimal17134%
R3 AOs that indirectly map to previous AOsModerate11022%
R3 AOs that do not have a clear link to any previous AOSignificant5711%
R3 AOs that are new for NIST 800-171 R3 controlsSignificant17234%
171

Minimal Effort

Direct mapping. The R3 AO traces back to an existing NIST 800-171A AO. See the 171 AOs

110

Moderate Effort

Indirect mapping. Parts of the R3 AO trace back, but you need to confirm what changed. See the 110 AOs

229

Significant Effort

57 AOs with no clear link to a previous AO and 172 AOs that are new in R3. See the 229 AOs

Everything on this page comes from the free NIST 800-171 R2 to R3 Transition Guide that our team wrote with DEFCERT. It walks through every NIST 800-171A R3 AO and how much work it will take to get there from R2.

The companion Excel spreadsheet has the same mapping in a format you can sort and filter, with tabs for the direct, indirect, no mapping, new and orphaned AOs.

Cover NIST 800-171 R2 To R3 Upgrade
Organization-Defined Parameters

DoD-Specified ODP Values

On April 10, 2025, the DoD CIO's office released a memorandum on minimum criteria for NIST SP 800-171 R3 Organization-Defined Parameters (ODP). These are the values DoD expects wherever R3 leaves a time period, frequency or other parameter up to the organization. The table below lists all 80 DoD-specified values.

IdentifierODP Assignment TextDoD-Specified ODP Value
03.01.01.f.02[Assignment: organization-defined time period]at most 90 days
03.01.01.g.01[Assignment: organization-defined time period]24 hours
03.01.01.g.02[Assignment: organization-defined time period]24 hours
03.01.01.g.03[Assignment: organization-defined time period]24 hours
03.01.01.h.01[Assignment: organization-defined time period]at most 24 hours
03.01.01.h.02[Assignment: organization-defined circumstances]the work period ends, for privileged users at a minimum
03.01.05.b.01[Assignment: organization-defined security functions]at a minimum and if applicable: establishing system accounts and assigning privileges, configuring access authorizations, configuring settings for events to be audited, establishing vulnerability scanning parameters, establishing intrusion detection parameters, and managing audit information
03.01.05.b.02[Assignment: organization-defined security-relevant information]at a minimum and if applicable: threat and vulnerability information, filtering rules for routers or firewalls, configuration parameters for security services, cryptographic key management information, security architecture, access control lists, and audit information
03.01.05.c[Assignment: organization-defined frequency]at least every 12 months
03.01.06.a[Assignment: organization-defined personnel or roles]only defined and authorized personnel or administrative roles
03.01.08.a.01[Assignment: organization-defined number]at most five (5)
03.01.08.a.02[Assignment: organization-defined time period]period of five (5) minutes
03.01.08.b[Assignment: organization-defined time period][Selection (one or more): lock the account or node for an at least 15-minute time period; lock the account or node until released by an administrator and notify a system administrator]
03.01.10.a[Assignment: organization-defined time period]initiating a device lock after “at most 15 minutes” of inactivity and requiring the user to initiate a device lock before leaving the system unattended
03.01.11[Assignment: organization-defined conditions or trigger events requiring session disconnect]a specified duration (maximum of 24 hours) of inactivity, misbehavior (end the session due to an attempted policy violation), and maintenance (terminate sessions to prevent issues with an upgrade or service outage)
03.01.20.b[Assignment: organization-defined security requirements]Guidance: Organizations establish specific terms and conditions for the use of external systems in accordance with organizational security policies and procedures. At a minimum, terms and conditions address the specific types of applications that can be accessed on organizational systems from external systems and the highest security category of information that can be processed, stored, or transmitted on external systems. If the terms and conditions with the owners of the external systems cannot be established, organizations may impose restrictions on organizational personnel using those external systems. If applicable, use NIST SP 800-47 as a guide for establishing information exchanges between organizations.
03.02.01.a.01[Assignment: organization-defined frequency]at least every 12 months
03.02.01.a.02[Assignment: organization-defined events]significant, novel incidents, or significant changes to risks
03.02.01.b.01[Assignment: organization-defined frequency]at least every 12 months
03.02.01.b.02[Assignment: organization-defined events]significant, novel incidents, or significant changes to risks
03.02.02.a.01[Assignment: organization-defined frequency]at least every 12 months
03.02.02.a.02[Assignment: organization-defined events]significant, novel incidents, or significant changes to risks
03.02.02.b.01[Assignment: organization-defined frequency]at least every 12 months
03.02.02.b.02[Assignment: organization-defined events]significant, novel incidents, or significant changes to risks
03.03.01.a[Assignment: organization-defined event types]at a minimum and where applicable:
1) Authentication events:
a) Logons (Success/Failure)
b) Logoffs (Success)
2) Security Relevant File and Objects events:
a) Create (Success/Failure)
b) Access (Success/Failure)
c) Delete (Success/Failure)
d) Modify (Success/Failure)
e) Permission Modification (Success/Failure)
f) Ownership Modification (Success/Failure)
3) Export/Writes/downloads to devices/digital media (e.g., CD/DVD, USB, SD) (Success/Failure)
4) Import/Uploads from devices/digital media (e.g., CD/DVD, USB, SD) (Success/Failure)
5) User and Group Management events:
a) User add, delete, modify, disable, lock (Success/Failure)
b) Group/Role add, delete, modify (Success/Failure)
6) Use of Privileged/Special Rights events:
a) Security or audit policy changes (Success/Failure)
b) Configuration changes (Success/Failure)
7) Admin or root-level access (Success/Failure)
8) Privilege/Role escalation (Success/Failure)
9) Audit and security relevant log data accesses (Success/Failure)
10) System reboot, restart, and shutdown (Success/Failure)
11) Print to a device (Success/Failure)
12) Print to a file (e.g., pdf format) (Success/Failure)
13) Application (e.g., Adobe, Firefox, MS Office Suite) initialization (Success/Failure)
For additional guidance, see: OMB21-31 ML 1
03.03.01.b[Assignment: organization-defined frequency]at least every 12 months and after any significant incidents or significant changes to risks
03.03.04.a[Assignment: organization-defined time period]near real time or as soon as practicable upon discovery
03.03.04.b[Assignment: organization-defined additional actions]document the failure and resolution, troubleshoot, repair/restart the audit logging process, and report as incident if applicable
03.03.05.a[Assignment: organization-defined frequency]at least weekly
03.03.07.b[Assignment: organization-defined granularity of time measurement]a granularity of one (1) second or smaller
03.04.01.b[Assignment: organization-defined frequency]at least every 12 months and after any significant incidents or significant changes occur
03.04.02.a[Assignment: organization-defined configuration settings]Apply the appropriate use of common security configurations available from the National Institute of Standards and Technology’s National Checklist Program (NCP) website (https://ncp.nist.gov/repository) and prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other unauthorized connection to resources in external networks. Document any deviations from the published standard or source document.
03.04.06.b[Assignment: organization-defined functions, ports, protocols, connections, and services]Guidance: Where feasible, organizations should limit component functionality to a single function per component. Organizations should consider removing unused or unnecessary software and disabling unused or unnecessary physical and logical ports and protocols to prevent unauthorized connection of components, transfer of information, and tunneling. Organizations should employ network scanning tools, intrusion detection and prevention systems, and end-point protection technologies, such as firewalls and host-based intrusion detection systems, to identify and prevent the use of prohibited functions, protocols, ports, and services. Least functionality should also be achieved as part of the fundamental design and development of the system.
03.04.06.c[Assignment: organization-defined frequency]at least every 12 months, when any system functions, ports, protocols, or services changes are made, and after any significant incidents or significant changes to risks
03.04.08.c[Assignment: organization-defined frequency]at least quarterly
03.04.10.b[Assignment: organization-defined frequency]at least quarterly
03.04.12.a[Assignment: organization-defined system configurations]a configuration that has no CUI or FCI stored on the system and prevents the processing, storing, and transmission of CUI and FCI, unless a specific exception is granted in writing by the Contracting Officer
03.04.12.b[Assignment: organization-defined security requirements]examine the system for signs of physical tampering and take the appropriate actions, and then either purge and reimage all storage media or destroy the system
03.05.01.b[Assignment: organization-defined circumstances or situations requiring re-authentication]roles, authenticators, or credentials change (including modification of user privilege); when security categories of systems change; when the execution of privileged functions occurs; and after a session termination
03.05.02[Assignment: organization-defined devices or types of devices]all devices for identification, where feasible for authentication, and document when not feasible
03.05.05.c[Assignment: organization-defined time period]at least ten (10) years
03.05.05.d[Assignment: organization-defined characteristic identifying individual status]privileged or non-privileged users; contractors, foreign nationals, and/or non-organizational users
03.05.07.a[Assignment: organization-defined frequency]at least quarterly
03.05.07.f[Assignment: organization-defined composition and complexity rules]1) Must have a minimum length of 16 characters. 2) Contains a string of characters that does not include the user’s account name or full name.
03.05.12.e.01[Assignment: organization-defined frequency]never for passwords where MFA is employed, at least every five (5) years for hard tokens and identification badges, and at least every three (3) years for all other authenticators
03.05.12.e.02[Assignment: organization-defined events]after a relevant security incident or any evidence of compromise or loss
03.06.02.b[Assignment: organization-defined time period]near real time or as soon as practicable upon discovery
03.06.02.c[Assignment: organization-defined authorities]all applicable personnel and entities as specified by the contract, and in accordance with any incident response plan notification procedures
03.06.03[Assignment: organization-defined frequency]at least every 12 months
03.06.04.a.01[Assignment: organization-defined time period]ten (10) days for privileged users, thirty (30) days for all other roles
03.06.04.a.03[Assignment: organization-defined frequency]at least every 12 months
03.06.04.b.01[Assignment: organization-defined frequency]at least every 12 months
03.06.04.b.02[Assignment: organization-defined events]significant, novel incidents, or significant changes to risks
03.08.07.a[Assignment: organization-defined types of system media]any removable media not managed by or on behalf of the organization
03.09.01.b[Assignment: organization-defined conditions requiring rescreening]an organizational policy requiring rescreening when there is a significant incident, or change in status, related to an individual
03.09.02.a.01[Assignment: organization-defined time period]four (4) hours
03.10.01.c[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.10.02.b.01[Assignment: organization-defined frequency]at least every 45 days
03.10.02.b.02[Assignment: organization-defined events or potential indications of events]significant, novel incidents, or significant changes to risks
03.10.06.b[Assignment: organization-defined security requirements]adequate security, comparable to organizational security requirements at the primary work site where practical, documented in policy, and covered by training
03.11.01.b[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.11.02.a[Assignment: organization-defined frequency]at least monthly, or when there are significant incidents or significant changes to risks
03.11.02.b[Assignment: organization-defined response times]thirty (30) days from date of discovery for high-risk vulnerabilities (including both critical and high); 90 days from date of discovery for moderate-risk vulnerabilities; and 180 days from date of discovery for low-risk vulnerabilities
03.11.02.c[Assignment: organization-defined frequency]no more than 24 hours prior to running the scans
03.12.01[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.12.05.a[Selection (one or more): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service-level agreements; user agreements; nondisclosure agreements; other types of agreements]requirements as described in the contract
03.12.05.c[Assignment: organization-defined frequency]at least every 12 months
03.13.09[Assignment: organization-defined time period]no longer than 15 minutes
03.13.10[Assignment: organization-defined requirements for key generation, distribution, storage, access, and destruction]Guidance: At a minimum, establish a policy and procedure in line with the latest Cryptographic key management guidance
03.13.11[Assignment: organization-defined types of cryptography]FIPS Validated Cryptography (https://csrc.nist.gov/Projects/Cryptographic-Module-Validation-Program/Validated-Modules)
03.13.12.a[Assignment: organization-defined exceptions where remote activation is to be allowed]only as enumerated and justified in the System Security Plan before such remote activation occurs, and only when there are no other options, and the remote activation is operationally critical
03.14.01.b[Assignment: organization-defined time period]thirty (30) days for high-risk flaws (including both critical and high), 90 days for moderate-risk flaws, and 180 days for low-risk flaws
03.14.02.c.01[Assignment: organization-defined frequency]at least weekly
03.15.01.b[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.15.02.b[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.15.03.d[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.16.01[Assignment: organization-defined systems security engineering principles]Guidance: At a minimum, documentation that provides user and administrator guidance for the implementation and operation of controls. The level of detail required in such documentation should be based on the degree to which organizations depend on the capabilities, functions, or mechanisms to meet risk response expectations. Requirements can include mandated configuration settings that specify allowed functions, ports, protocols, and services. Acceptance criteria for systems, system components, and system services are defined in the same manner as the criteria for any organizational acquisition or procurement.
03.16.03.a[Assignment: organization-defined security requirements]1. For cloud service providers:
(i) FedRAMP Authorized at the FedRAMP Moderate (or higher) baseline in accordance with the FedRAMP Marketplace; or
(ii) meets security requirements established by the government equivalent to the FedRAMP Moderate (or higher) baseline.
2. All other external service providers must meet NIST SP 800-171 R2.
03.17.01.b[Assignment: organization-defined frequency]at least every 12 months, or when there are significant incidents or significant changes to risks
03.17.03.b[Assignment: organization-defined security requirements]at a minimum, integrate Supply Chain Risk Management (SCRM) into acquisition/procurement policies, provide adequate SCRM resources, define the SCRM control baseline, establish processes to ensure suppliers disclose significant vulnerabilities and significant incidents
NIST SP 800-171 R3

Breaking Down The R3 CUI Controls

NIST SP 800-171 R2 had 110 CUI controls. NIST SP 800-171 R3 organizes its requirements into two levels:

97

Core CUI Controls

The top-level controls listed in NIST SP 800-171 R3.

287

Discrete Requirements

The sub controls inside those 97 core controls. This is where most of the assessment scope lives.

The free Excel spreadsheet breaks down every core control, sub control and AO so you can see exactly where each requirement came from.

End Of Life (EOL) Assessment Objectives

Undocumented Dependencies In NIST 800-171A R3

The central issue with End of Life (EOL) AOs is the undocumented dependencies they leave behind. Assumptions can lead to non-compliance, poor security practices or both. A thorough comparison of NIST 800-171A and NIST 800-171A R3 turns up several AOs that existed before but do not exist in R3:

  • The underlying function still exists in R3 (e.g., maintenance operations), but no AO calls out a unique requirement to perform it (e.g., perform maintenance on assets).
  • Demonstrating compliance with R3 relies on assuming that certain fundamental IT capabilities are mature enough to support the control.

The intent of NIST 800-171 is "reasonable security practices" to protect CUI wherever it is stored, processed or transmitted. Even so, NIST left several evidentiary gaps in NIST 800-171A R3 that could lead to assumptions or compliance failures. Review these areas before you start the move from R2 to R3:

01

Maintenance Operations

Problem: R3 drops 3.7.1, the R2 AO that determined whether system maintenance is performed. No R3 AO specifies maintenance-related operations. The maintenance AOs that remain only cover:

  • Approving and controlling maintenance tools (A.03.07.04.a[01] and A.03.07.04.a[02])
  • Monitoring the use of maintenance tools (A.03.07.04.a[03])
  • Controlling maintenance media (A.03.07.04.b and A.03.07.04.c)
  • The closest analogs assume change control (A.03.04.03.c[01]) or vulnerability remediation (A.03.11.02.b) covers maintenance

Dependency issue: There is a clear assumption that maintenance is performed, but no AO-level requirement in NIST 800-171A R3 to actually perform it.

02

Roles And Responsibilities

Problem: R3 drops the NIST 800-171A AOs that defined and assigned roles and responsibilities:

  • 3.1.22[a]: individuals authorized to post or process information on publicly accessible systems are identified
  • 3.2.2[a]: information security-related duties, roles and responsibilities are defined
  • 3.2.2[b]: those duties, roles and responsibilities are assigned to designated personnel
  • The only R3 requirement is for third parties: A.03.16.03.b covers roles and responsibilities for external system services

Dependency issue: The word "roles" appears throughout NIST 800-171A R3, yet nothing requires you to define cybersecurity roles and responsibilities for internal personnel.

03

Documenting The Flow Of CUI

Problem: R3 drops the NIST 800-171A AOs that set expectations for controlling the flow of CUI:

  • 3.1.2[a]: types of transactions and functions authorized users can execute are defined
  • 3.1.3[a] through 3.1.3[d]: flow control policies, enforcement mechanisms, approved sources and destinations, and authorizations are defined
  • The closest R3 analogs default to organizational policy (A.03.01.02[01] and A.03.01.02[02])

Dependency issue: R3 assumes documentation exists that specifies how CUI is controlled, which leaves the expected level of due diligence and due care unclear. The System Security Plan (SSP) could capture this, but R3 does not require the SSP to document it.

04

Logical Access Control And Account Management

Problem: R3 drops the NIST 800-171A AOs for privileged and non-privileged accounts:

  • 3.1.5[a]: privileged accounts are identified
  • 3.1.6[a] and 3.1.6[b]: nonsecurity functions are identified and require non-privileged accounts
  • 3.1.7[a] and 3.1.7[b]: privileged functions and non-privileged users are defined
  • The closest R3 analog is A.03.01.05.ODP[01] (security functions for authorized access are defined)

Dependency issue: R3 assumes privileged accounts are identified and privileged functions are defined, and the same goes for non-privileged accounts. Training or assigned roles might provide that clarity, but that is an assumption, not a documented requirement.

05

Situational Awareness

Problem: R3 drops 3.3.7[b], which required an authoritative time source to compare and synchronize internal system clocks. R3 only requires:

  • A defined granularity of time measurement (A.03.03.07.ODP[01])
  • Internal system clocks to generate time stamps (A.03.03.07.a)
  • Recorded time stamps (A.03.03.07.b[01] and A.03.03.07.b[02])

Dependency issue: R3 assumes internal clocks sync to an authoritative time source (e.g., the US Naval Observatory (USNO) public time server). Without one, time is subjective, which hurts event log analysis and incident response.

06

Comprehensive Inventories

Problem: R3 drops the NIST 800-171A AOs that called for inventories of assets and personnel that affect the security of CUI:

  • 3.1.18[a] and 3.1.18[c]: mobile devices that handle CUI are identified, and their connections are monitored and logged
  • 3.1.20[a], 3.1.20[b] and 3.1.20[d]: connections to and use of external systems are identified and verified
  • 3.5.3[a]: privileged accounts are identified
  • 3.13.12[a]: collaborative computing devices are identified
  • The only R3 inventory requirement is for system components (A.03.04.10.a)

Dependency issue: R3 assumes you have inventories of systems (hardware, software and services), third parties (e.g., Cloud Service Providers (CSP) and External Service Providers (ESP)), privileged users, non-privileged users and third-party users. You could assume the SCRM requirements cover third parties, but the SCRM plan requirement lacks that level of detail.

07

Incident Response

Problem: R3 drops the NIST 800-171A AOs that defined responsible personnel and required incident response operations:

  • 3.3.4[a] and 3.3.4[b]: who is alerted to audit logging process failures and which failures trigger alerts
  • 3.6.2[d]: organizational officials who receive incident reports are identified
  • 3.14.3[a] and 3.14.3[c]: response actions to security alerts and advisories are identified and taken
  • R3 does not specify who to alert for audit logging failures, which internal officials to alert about incidents or how to respond to physical security incidents

Dependency issue: R3 assumes incident response operations exist and are documented, along with clearly defined roles for incident response personnel.

08

Physical Security

Problem: R3 drops the NIST 800-171A AOs that set the basis for physical security practices:

  • 3.10.2[a]: the physical facility where the system resides is protected
  • 3.10.2[b]: the support infrastructure for the system is protected
  • 3.10.2[d]: the support infrastructure for the system is monitored
  • No R3 AO specifies physical security protections or broader physical infrastructure security

Dependency issue: R3 assumes physical security is performed and that there is enough documentation to prove it.

Orphaned Assessment Objectives

NIST 800-171A AOs That Do Not Exist In NIST 800-171A R3

These 37 NIST 800-171A AOs are End of Life (EOL). They no longer exist, and there is no corresponding AO in NIST 800-171A R3. Several of them create the dependency issues described above.

NIST 800-171ANIST 800-171A Assessment Objective (AO)
3.1.2[a]the types of transactions and functions that authorized users are permitted to execute are defined
3.1.3[a]information flow control policies are defined.
3.1.3[b]methods and enforcement mechanisms for controlling the flow of CUI are defined.
3.1.3[c]designated sources and destinations (e.g., networks, individuals, and devices) for CUI within systems and between interconnected systems are identified.
3.1.3[d]authorizations for controlling the flow of CUI are defined.
3.1.5[a]privileged accounts are identified.
3.1.6[a]nonsecurity functions are identified.
3.1.6[b]users are required to use non-privileged accounts or roles when accessing nonsecurity functions.
3.1.7[a]privileged functions are defined.
3.1.7[b]non-privileged users are defined.
3.1.12[d]remote access sessions are monitored.
3.1.18[a]mobile devices that process, store, or transmit CUI are identified.
3.1.18[c]mobile device connections are monitored and logged.
3.1.20[a]connections to external systems are identified.
3.1.20[b]use of external systems is identified.
3.1.20[d]use of external systems is verified.
3.1.22Determine if CUI posted or processed on publicly accessible systems is controlled.
3.1.22[a]individuals authorized to post or process information on publicly accessible systems are identified.
3.1.22[b]procedures to ensure CUI is not posted or processed on publicly accessible systems are identified.
3.2.2[a]information security-related duties, roles, and responsibilities are defined.
3.2.2[b]information security-related duties, roles, and responsibilities are assigned to designated personnel.
3.3.1[d]audit records, once created, contain the defined content.
3.3.4[a]personnel or roles to be alerted in the event of an audit logging process failure are identified.
3.3.4[b]types of audit logging process failures for which alert will be generated are defined.
3.3.7[b]an authoritative source with which to compare and synchronize internal system clocks is specified.
3.5.3[a]privileged accounts are identified.
3.5.3[b]multifactor authentication is implemented for local access to privileged accounts.
3.6.2[d]organizational officials to whom incidents are to be reported are identified.
3.10.2[a]the physical facility where that system resides is protected.
3.10.2[b]the support infrastructure for that system is protected.
3.10.2[d]the support infrastructure for that system is monitored.
3.13.12[a]collaborative computing devices are identified.
3.14.1[a]the time within which to identify system flaws is specified.
3.14.1[c]the time within which to report system flaws is specified.
3.14.1[e]the time within which to correct system flaws is specified.
3.14.3[a]response actions to system security alerts and advisories are identified.
3.14.3[c]actions in response to system security alerts and advisories are taken.
Minimal Effort

Minimal Effort AO Transition

If you already have controls in place for NIST 800-171 R2 and use NIST 800-171A, about one-third of the AOs in NIST 800-171A R3 should take minimal effort to transition.

NIST 800-171A R3 AOs With Direct Mapping (Existing NIST 800-171 R3 Control)

These 171 AOs have "direct mapping," which means each NIST 800-171A R3 AO clearly maps back to an existing NIST 800-171A AO.

NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.01.01.ODP[01]Account Managementthe time period for account inactivity before disabling is defined.Maps to 3.5.6[a]
A.03.01.01.c.01Account Managementauthorized users of the system are specified.Maps to 3.1.1[a]
A.03.01.01.f.02Account Managementsystem accounts are disabled when the accounts have been inactive for <A.03.01.01.ODP[01]: time period>.Maps to 3.5.6[b]
A.03.01.04.aSeparation of Dutiesduties of individuals requiring separation are identified.Maps to 3.1.4[a]
A.03.01.05.b[01]Least Privilegeaccess to <A.03.01.05.ODP[01]: security functions> is authorized.Maps to 3.1.5[d]
A.03.01.07.aLeast Privilege - Privileged Functionsnon-privileged users are prevented from executing privileged functions.Maps to 3.1.7[c]
A.03.01.07.bLeast Privilege - Privileged Functionsthe execution of privileged functions is logged.Maps to 3.1.7[d]
A.03.01.08.ODP[01]Unsuccessful Logon Attemptsthe number of consecutive invalid logon attempts by a user allowed during a time period is defined.Maps to 3.1.8[a]
A.03.01.09System Use Notificationa system use notification message with privacy and security notices consistent with applicable CUI rules is displayed before granting access to the system.Maps to 3.1.9[a], 3.1.9[b]
A.03.01.10.ODP[01]Device Lockone or more of the following PARAMETER VALUES are selected: {a device lock is initiated after <A.03.01.10.ODP[02]: time period> of inactivity; the user is required to initiate a device lock before leaving the system unattended}.Maps to 3.1.10[b]
A.03.01.10.ODP[02]Device Lockthe time period of inactivity after which a device lock is initiated is defined (if selected).Maps to 3.1.10[a]
A.03.01.10.aDevice Lockaccess to the system is prevented by <A.03.01.10.ODP[01]: SELECTED PARAMETER VALUES>.Maps to 3.1.10[b]
A.03.01.10.cDevice Lockinformation previously visible on the display is concealed via device lock with a publicly viewable image.Maps to 3.1.10[c]
A.03.01.11.ODP[01]Session Terminationconditions or trigger events that require session disconnect are defined.Maps to 3.1.11[a]
A.03.01.11Session Terminationa user session is terminated automatically after <A.03.01.11.ODP[01]: conditions or trigger events>.Maps to 3.1.11[b]
A.03.01.12.a[01]Remote Accesstypes of allowable remote system access are defined.Maps to 3.1.12[b] and elements of 3.1.14[a]
A.03.01.12.c[02]Remote Accessremote access to the system is routed through managed access control points.Maps to 3.1.14[b]
A.03.01.16.bWireless Accesseach type of wireless access to the system is authorized prior to establishing such connections.Maps to 3.1.16[b]
A.03.01.16.d[01]Wireless Accesswireless access to the system is protected using authentication.Maps to 3.1.17[b]
A.03.01.16.d[02]Wireless Accesswireless access to the system is protected using encryption.Maps to 3.1.17[a]
A.03.01.18.bAccess Control for Mobile Devicesthe connection of mobile devices to the system is authorized.Maps to 3.1.19[a]
A.03.01.18.cAccess Control for Mobile Devicesfull-device or container-based encryption is implemented to protect the confidentiality of CUI on mobile devices.Maps to 3.1.19[b]
A.03.01.22.b[01]Publicly Accessible Contentthe content on publicly accessible systems is reviewed for CUI.Maps to 3.1.22[c], 3.1.22[d]
A.03.01.22.b[02]Publicly Accessible ContentCUI is removed from publicly accessible systems, if discovered.Maps to 3.1.22[e]
A.03.02.01.a.03[01]Literacy Training and Awarenesssecurity literacy training is provided to system users on recognizing indicators of insider threat.Maps to 3.2.3[b] and elements of 3.2.1[c], 3.2.1[d], 3.2.3[a]
A.03.02.02.a.01[01]Role-Based Trainingrole-based security training is provided to organizational personnel before authorizing access to the system or CUI.Maps to 3.2.2[c]
A.03.02.02.a.01[02]Role-Based Trainingrole-based security training is provided to organizational personnel before performing assigned duties.Maps to 3.2.2[c]
A.03.02.02.a.01[03]Role-Based Trainingrole-based security training is provided to organizational personnel <A.03.02.02.ODP[01]: frequency> after initial training.Maps to 3.2.2[c]
A.03.02.02.a.02Role-Based Trainingrole-based security training is provided to organizational personnel when required by system changes or following <A.03.02.02.ODP[02]: events>.Maps to 3.2.2[c]
A.03.02.02.b[01]Role-Based Trainingrole-based security training content is updated <A.03.02.02.ODP[03]: frequency>.Maps to 3.2.2[c]
A.03.03.01.ODP[01]Event Loggingevent types selected for logging within the system are defined.Maps to 3.3.1[a], 3.3.1[b]
A.03.03.01.aEvent Loggingthe following event types are specified for logging within the system: <A.03.03.01.ODP[01]: event types>.Maps to 3.3.1[a], 3.3.1[b]
A.03.03.01.b[02]Event Loggingthe event types selected for logging are updated <A.03.03.01.ODP[02]: frequency>.Maps to 3.3.3[c]
A.03.03.03.aAudit Record Generationaudit records for the selected event types and audit record content specified in 03.03.01 and 03.03.02 are generated.Maps to 3.3.1[c] and elements of NFO - SI-4(5)
A.03.03.03.bAudit Record Generationaudit records are retained for a time period consistent with the records retention policy.Maps to 3.3.1[f]
A.03.03.04.aResponse to Audit Logging Process Failuresorganizational personnel or roles are alerted in the event of an audit logging process failure within <A.03.03.04.ODP[01]: time period>.Maps to 3.3.4[c]
A.03.03.05.aAudit Record Review, Analysis, and Reportingsystem audit records are reviewed and analyzed <A.03.03.05.ODP[01]: frequency> for indications and the potential impact of inappropriate or unusual activity.Maps to 3.3.5[a]
A.03.03.05.c[01]Audit Record Review, Analysis, and Reportingaudit records across different repositories are analyzed to gain organization-wide situational awareness.Maps to 3.3.5[b]
A.03.03.05.c[02]Audit Record Review, Analysis, and Reportingaudit records across different repositories are correlated to gain organization-wide situational awareness.Maps to 3.3.5[b]
A.03.03.06.a[01]Audit Record Reduction and Report Generationan audit record reduction and report generation capability that supports audit record review is implemented.Maps to 3.3.6[a]
A.03.03.06.a[02]Audit Record Reduction and Report Generationan audit record reduction and report generation capability that supports audit record analysis is implemented.Maps to 3.3.6[a]
A.03.03.06.a[03]Audit Record Reduction and Report Generationan audit record reduction and report generation capability that supports audit record reporting requirements is implemented.Maps to 3.3.6[b]
A.03.03.07.aTime Stampsinternal system clocks are used to generate time stamps for audit records.Maps to 3.3.7[a]
A.03.03.07.b[01]Time Stampstime stamps are recorded for audit records that meet <A.03.03.07.ODP[01]: granularity of time measurement>.Maps to 3.3.7[c]
A.03.03.08.a[01]Protection of Audit Informationaudit information is protected from unauthorized access, modification, and deletion.Maps to 3.3.8[a], 3.3.8[b], 3.3.8[c]
A.03.03.08.a[02]Protection of Audit Informationaudit logging tools are protected from unauthorized access, modification, and deletion.Maps to 3.3.8[d], 3.3.8[e], 3.3.8[f]
A.03.03.08.bProtection of Audit Informationaccess to management of audit logging functionality is authorized to only a subset of privileged users or roles.Maps to 3.3.9[a], 3.3.9[b]
A.03.04.01.a[01]Baseline Configurationa current baseline configuration of the system is developed.Maps to 3.4.1[a], 3.4.1[b], 3.4.2[a]
A.03.04.01.a[02]Baseline Configurationa current baseline configuration of the system is maintained under configuration control.Maps to 3.4.1[c], 3.4.2[b]
A.03.04.02.ODP[01]Configuration Settingsconfiguration settings for the system that reflect the most restrictive mode consistent with operational requirements are defined.Maps to 3.4.2[a], 3.4.6[a], 3.4.6[b] and elements of 3.13.7
A.03.04.02.a[01]Configuration Settingsthe 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>.Maps to 3.4.2[a], 3.4.6[a], 3.4.6[b] and elements of 3.13.7
A.03.04.03.b[01]Configuration Change Controlproposed configuration-controlled changes to the system are reviewed with explicit consideration for security impacts.Maps to 3.4.3[a], 3.4.3[b]
A.03.04.03.b[02]Configuration Change Controlproposed configuration-controlled changes to the system are approved or disapproved with explicit consideration for security impacts.Maps to 3.4.3[a], 3.4.3[c]
A.03.04.03.c[02]Configuration Change Controlapproved configuration-controlled changes to the system are documented.Maps to 3.4.3[d]
A.03.04.04.aImpact Analyseschanges to the system are analyzed to determine potential security impacts prior to change implementation.Maps to 3.4.4
A.03.04.05[01]Access Restrictions for Changephysical access restrictions associated with changes to the system are defined and documented.Maps to 3.4.5[a], 3.4.5[b]
A.03.04.05[02]Access Restrictions for Changephysical access restrictions associated with changes to the system are approved.Maps to 3.4.5[c]
A.03.04.05[03]Access Restrictions for Changephysical access restrictions associated with changes to the system are enforced.Maps to 3.4.5[d]
A.03.04.05[04]Access Restrictions for Changelogical access restrictions associated with changes to the system are defined and documented.Maps to 3.4.5[e], 3.4.5[f]
A.03.04.05[05]Access Restrictions for Changelogical access restrictions associated with changes to the system are approved.Maps to 3.4.5[g]
A.03.04.05[06]Access Restrictions for Changelogical access restrictions associated with changes to the system are enforced.Maps to 3.4.5[h]
A.03.04.08.aAuthorized Software - Allow by Exceptionsoftware programs authorized to execute on the system are identified.Maps to 3.4.8[a], 3.4.8[b]
A.03.04.08.bAuthorized Software - Allow by Exceptiona deny-all, allow-by-exception policy for the execution of authorized software programs on the system is implemented.Maps to 3.4.8[c] and elements of 3.4.9[a], 3.4.9[b] and NFO CA-3(5) (now SC-7(5))
A.03.04.10.aSystem Component Inventoryan inventory of system components is developed and documented.3.4.1[d] and elements of 3.4.1[e]
A.03.05.01.a[02]User Identification and Authenticationsystem users are authenticated.Maps to 3.5.2[a], 3.5.2[b]
A.03.05.01.a[03]User Identification and Authenticationprocesses acting on behalf of users are associated with uniquely identified and authenticated system users.Maps to 3.1.1[b]
A.03.05.02[02]Device Identification and Authentication<A.03.05.02.ODP[01]: devices or types of devices> are authenticated before establishing a system connection.Maps to 3.5.2[c]
A.03.05.03[01]Multi-Factor Authenticationmulti-factor authentication for access to privileged accounts is implemented.Maps to 3.5.3[c]
A.03.05.03[02]Multi-Factor Authenticationmulti-factor authentication for access to non-privileged accounts is implemented.Maps to 3.5.3[d]
A.03.05.04[01]Replay-Resistant Authenticationreplay-resistant authentication mechanisms for access to privileged accounts are implemented.Maps to 3.5.4
A.03.05.04[02]Replay-Resistant Authenticationreplay-resistant authentication mechanisms for access to non-privileged accounts are implemented.Maps to 3.5.4
A.03.05.07.ODP[01]Password Managementthe frequency at which to update the list of commonly used, expected, or compromised passwords is defined.Maps to 3.5.7[b]
A.03.05.07.ODP[02]Password Managementpassword composition and complexity rules are defined.Maps to 3.5.7[a]
A.03.05.07.cPassword Managementpasswords are only transmitted over cryptographically protected channels.Maps to 3.5.10[b]
A.03.05.07.dPassword Managementpasswords are stored in a cryptographically protected form.Maps to 3.5.10[a]
A.03.05.11Authentication Feedbackfeedback of authentication information during the authentication process is obscured.Maps to 3.5.11
A.03.06.01[01]Incident Handlingan incident-handling capability that is consistent with the incident response plan is implemented.Maps to 3.6.1[a] and elements of NFO - IR-8
A.03.06.01[02]Incident Handlingthe incident handling capability includes preparation.Maps to 3.6.1[b]
A.03.06.01[03]Incident Handlingthe incident handling capability includes detection and analysis.Maps to 3.6.1[c], 3.6.1[d]
A.03.06.01[04]Incident Handlingthe incident handling capability includes containment.Maps to 3.6.1[e]
A.03.06.01[05]Incident Handlingthe incident handling capability includes eradication.Maps to 3.6.1[f]
A.03.06.01[06]Incident Handlingthe incident handling capability includes recovery.Maps to 3.6.1[g]
A.03.06.02.ODP[02]Incident Monitoring, Reporting, and Response Assistanceauthorities to whom incident information is to be reported are defined.Maps to 3.6.2[c]
A.03.06.02.a[01]Incident Monitoring, Reporting, and Response Assistancesystem security incidents are tracked.Maps to 3.6.2[a]
A.03.06.02.a[02]Incident Monitoring, Reporting, and Response Assistancesystem security incidents are documented.Maps to 3.6.2[b]
A.03.06.02.bIncident Monitoring, Reporting, and Response Assistancesuspected incidents are reported to the organizational incident response capability within <A.03.06.02.ODP[01]: time period>.Maps to 3.6.2[f]
A.03.06.02.cIncident Monitoring, Reporting, and Response Assistanceincident information is reported to <A.03.06.02.ODP[02]: authorities>.Maps to 3.6.2[e]
A.03.06.03Incident Response Testingthe effectiveness of the incident response capability is tested <A.03.06.03.ODP[01]: frequency>.Maps to 3.6.3
A.03.07.04.a[02]Maintenance Toolsthe use of system maintenance tools is controlled.Maps to 3.7.2[a]
A.03.07.04.bMaintenance Toolsmedia with diagnostic and test programs are checked for malicious code before the media are used in the system.Maps to 3.7.4
A.03.07.05.b[01]Nonlocal Maintenancemulti-factor authentication is implemented in the establishment of nonlocal maintenance and diagnostic sessions.Maps to 3.7.5[a]
A.03.07.05.c[01]Nonlocal Maintenancesession connections are terminated when nonlocal maintenance is completed.Maps to 3.7.5[b]
A.03.07.05.c[02]Nonlocal Maintenancenetwork connections are terminated when nonlocal maintenance is completed.Maps to 3.7.5[b]
A.03.08.01[01]Media Storagesystem media that contain CUI are physically controlled.Maps to 3.8.1[a], 3.8.1[b]
A.03.08.01[02]Media Storagesystem media that contain CUI are securely stored.Maps to 3.8.1[c], 3.8.1[d]
A.03.08.02Media Accessaccess to CUI on system media is restricted to authorized personnel or roles.Maps to 3.8.2
A.03.08.03Media Sanitizationsystem media that contain CUI are sanitized prior to disposal, release out of organizational control, or release for reuse.Maps to 3.7.3, 3.8.3[a], 3.8.3[b]
A.03.08.04[01]Media Markingsystem media that contain CUI are marked to indicate distribution limitations.Maps to 3.8.4[b]
A.03.08.04[03]Media Markingsystem media that contain CUI are marked to indicate applicable CUI markings.Maps to 3.8.4[a]
A.03.08.05.a[01]Media Transportsystem media that contain CUI are protected during transport outside of controlled areas.Maps to 3.8.5[a]
A.03.08.05.a[02]Media Transportsystem media that contain CUI are controlled during transport outside of controlled areas.Maps to 3.8.5[a]
A.03.08.05.bMedia Transportaccountability for system media that contain CUI is maintained during transport outside of controlled areas.Maps to 3.8.5[b]
A.03.08.07.aMedia Usethe use of the following types of system media is restricted or prohibited: <A.03.08.07.ODP[01]: types of system media>.Maps to 3.8.7
A.03.08.07.bMedia Usethe use of removable system media without an identifiable owner is prohibited.Maps to 3.8.8
A.03.08.09.aSystem Backup - Cryptographic Protectionthe confidentiality of backup information is protected.Maps to 3.8.9
A.03.08.09.bSystem Backup - Cryptographic Protectioncryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI at backup storage locations.Maps to 3.8.9
A.03.09.01.aPersonnel Screeningindividuals are screened prior to authorizing access to the system.Maps to 3.9.1
A.03.10.01.a[01]Physical Access Authorizationsa list of individuals with authorized access to the facility where the system resides is developed.Maps to 3.10.1[a]
A.03.10.01.a[02]Physical Access Authorizationsa list of individuals with authorized access to the facility where the system resides is approved.Maps to 3.10.1[a]
NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.10.01.a[03]Physical Access Authorizationsa list of individuals with authorized access to the facility where the system resides is maintained.Maps to 3.10.1[a]
A.03.10.01.bPhysical Access Authorizationsauthorization credentials for facility access are issued.Maps to 3.10.1[b], 3.10.1[c], 3.10.1[d]
A.03.10.02.a[01]Monitoring Physical Accessphysical access to the facility where the system resides is monitored to detect physical security incidents.Maps to 3.10.2[c] and elements of NFO - PE-6(1)
A.03.10.06.ODP[01]Alternate Work Sitesecurity requirements to be employed at alternate work sites are defined.Maps to 3.10.6[a]
A.03.10.06.bAlternate Work Sitethe following security requirements are employed at alternate work sites: <A.03.10.06.ODP[01]: security requirements>.Maps to 3.10.6[b]
A.03.10.07.bPhysical Access Controlphysical access audit logs for entry or exit points are maintained.Maps to 3.10.4
A.03.10.07.c[01]Physical Access Controlvisitors are escorted.Maps to 3.10.3[a]
A.03.11.01.ODP[01]Risk Assessmentthe frequency at which to update the risk assessment is defined.Maps to 3.11.1[a]
A.03.11.01.aRisk Assessmentthe risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI is assessed.Maps to 3.2.1[a], 3.11.1[b]
A.03.11.01.bRisk Assessmentrisk assessments are updated <A.03.11.01.ODP[01]: frequency>.Maps to 3.11.1[b]
A.03.11.02.ODP[02]Vulnerability Monitoring and Scanningthe frequency at which the system is scanned for vulnerabilities is defined.Maps to 3.11.2[a]
A.03.11.02.a[02]Vulnerability Monitoring and Scanningthe system is scanned for vulnerabilities <A.03.11.02.ODP[02]: frequency>.Maps to 3.11.2[b] and elements of 3.11.2[c], 3.11.3[a]
A.03.11.02.a[04]Vulnerability Monitoring and Scanningthe system is scanned for vulnerabilities when new vulnerabilities that affect the system are identified.Maps to 3.11.2[d] and elements of 3.11.2[c], 3.11.3[a]
A.03.12.01.ODP[01]Security Assessmentthe frequency at which to assess the security requirements for the system and its environment of operation is defined.Maps to 3.12.1[a]
A.03.12.01Security Assessmentthe security requirements for the system and its environment of operation are assessed <A.03.12.01.ODP[01]: frequency> to determine if the requirements have been satisfied.Maps to 3.12.1[b]
A.03.13.01.a[01]Boundary Protectioncommunications at external managed interfaces to the system are monitored.Maps to 3.13.1[c] and elements of 3.13.14[b]
A.03.13.01.a[02]Boundary Protectioncommunications at external managed interfaces to the system are controlled.Maps to 3.13.1[e], 3.13.1[g] and elements of 3.13.5[a]
A.03.13.01.a[03]Boundary Protectioncommunications at key internal managed interfaces within the system are monitored.Maps to 3.13.1[d] and elements of 3.13.14[b]
A.03.13.01.a[04]Boundary Protectioncommunications at key internal managed interfaces within the system are controlled.Maps to 3.13.1[f], 3.13.1[h]
A.03.13.04[01]Information in Shared System Resourcesunauthorized information transfer via shared system resources is prevented.Maps to 3.13.4
A.03.13.04[02]Information in Shared System Resourcesunintended information transfer via shared system resources is prevented.Maps to 3.13.4
A.03.13.06[01]Network Communications - Deny by Default - Allow by Exceptionnetwork communications traffic is denied by default.Maps to 3.13.6[a]
A.03.13.06[02]Network Communications - Deny by Default - Allow by Exceptionnetwork communications traffic is allowed by exception.Maps to 3.13.6[b]
A.03.13.08[01]Transmission and Storage Confidentialitycryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI during transmission.Maps to 3.13.8[c] and elements of 3.13.8[c], 3.8.6
A.03.13.08[02]Transmission and Storage Confidentialitycryptographic mechanisms are implemented to prevent the unauthorized disclosure of CUI while in storage.Maps to 3.13.8[c] and elements of 3.13.8[c], 3.8.6, 3.13.16
A.03.13.09.ODP[01]Network Disconnectthe time period of inactivity after which the system terminates a network connection associated with a communications session is defined.Maps to 3.13.9[a]
A.03.13.09Network Disconnectthe network connection associated with a communications session is terminated at the end of the session or after <A.03.13.09.ODP[01]: time period> of inactivity.Maps to 3.13.9[b], 3.13.9[c]
A.03.13.10[01]Cryptographic Key Establishment and Managementcryptographic keys are established in the system in accordance with the following key management requirements: <A.03.13.10.ODP[01]: requirements>.Maps to 3.13.10[a]
A.03.13.10[02]Cryptographic Key Establishment and Managementcryptographic keys are managed in the system in accordance with the following key management requirements: <A.03.13.10.ODP[01]: requirements>.Maps to 3.13.10[b]
A.03.13.12.aCollaborative Computing Devices and Applicationsthe remote activation of collaborative computing devices and applications is prohibited with the following exceptions: <A.03.13.12.ODP[01]: exceptions>.Maps to 3.13.12[c]
A.03.13.12.bCollaborative Computing Devices and Applicationsan explicit indication of use is provided to users who are physically present at the devices.Maps to 3.13.12[b]
A.03.13.13.b[01]Mobile Codethe use of mobile code is authorized.Maps to 3.13.13[a]
A.03.13.13.b[02]Mobile Codethe use of mobile code is monitored.Maps to 3.13.13[b]
A.03.13.13.b[03]Mobile Codethe use of mobile code is controlled.Maps to 3.13.13[a]
A.03.13.15Session Authenticitythe authenticity of communications sessions is protected.Maps to 3.13.15
A.03.14.01.a[01]Flaw Remediationsystem flaws are identified.Maps to 3.14.1[b]
A.03.14.01.a[02]Flaw Remediationsystem flaws are reported.Maps to 3.14.1[d]
A.03.14.01.a[03]Flaw Remediationsystem flaws are corrected.Maps to 3.14.1[f]
A.03.14.02.ODP[01]Malicious Code Protectionthe frequency at which malicious code protection mechanisms perform scans is defined.Maps to 3.14.5[a]
A.03.14.02.a[01]Malicious Code Protectionmalicious code protection mechanisms are implemented at system entry and exit points to detect malicious code.Maps to 3.14.2[a]
A.03.14.02.a[02]Malicious Code Protectionmalicious code protection mechanisms are implemented at system entry and exit points to eradicate malicious code.Maps to 3.14.2[b]
A.03.14.02.bMalicious Code Protectionmalicious code protection mechanisms are updated as new releases are available in accordance with configuration management policy and procedures.Maps to 3.14.4
A.03.14.02.c.01[01]Malicious Code Protectionmalicious code protection mechanisms are configured to perform scans of the system <A.03.14.02.ODP[01]: frequency>.Maps to 3.14.5[b]
A.03.14.02.c.01[02]Malicious Code Protectionmalicious code protection mechanisms are configured to perform real-time scans of files from external sources at endpoints or system entry and exit points as the files are downloaded, opened, or executed.Maps to 3.14.5[c]
A.03.14.03.aSecurity Alerts, Advisories, and Directivessystem security alerts, advisories, and directives from external organizations are received on an ongoing basis.Maps to 3.14.3[b]
A.03.14.06.a.01[01]System Monitoringthe system is monitored to detect attacks.Maps to 3.14.6[a]
A.03.14.06.a.01[02]System Monitoringthe system is monitored to detect indicators of potential attacks.Maps to 3.14.6[b]
A.03.14.06.a.02System Monitoringthe system is monitored to detect unauthorized connections.Maps to 3.14.6[a], 3.14.6[c]
A.03.14.06.bSystem Monitoringunauthorized use of the system is identified.Maps to 3.14.7[b]
A.03.14.06.c[01]System Monitoringinbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.Maps to 3.14.6[b]
A.03.14.06.c[02]System Monitoringoutbound communications traffic is monitored to detect unusual or unauthorized activities or conditions.Maps to 3.14.6[c]
A.03.15.01.a[01]Policy and Procedurespolicies needed to satisfy the security requirements for the protection of CUI are developed and documented.Maps to 3.2.1[b] and elements of 3.9.2[a]
A.03.15.01.a[02]Policy and Procedurespolicies needed to satisfy the security requirements for the protection of CUI are disseminated to organizational personnel or roles.Maps to 3.2.1[b]
A.03.15.01.a[03]Policy and Proceduresprocedures needed to satisfy the security requirements for the protection of CUI are developed and documented.Maps to 3.2.1[b] and elements of 3.9.2[a]
A.03.15.01.a[04]Policy and Proceduresprocedures needed to satisfy the security requirements for the protection of CUI are disseminated to organizational personnel or roles.Maps to 3.2.1[b]
A.03.15.02.ODP[01]System Security Planthe frequency at which the system security plan is reviewed and updated is defined.Maps to 3.12.4[g]
A.03.15.02.a.01System Security Plana system security plan that defines the constituent system components is developed.Maps to 3.12.4[a]
A.03.15.02.a.04System Security Plana system security plan that describes the operational environment for the system and any dependencies on or connections to other systems or system components is developed.Maps to 3.12.4[b], 3.12.4[c], 3.12.4[f]
A.03.15.02.a.05System Security Plana system security plan that provides an overview of the security requirements for the system is developed.Maps to 3.12.4[d]
A.03.15.02.a.06System Security Plana system security plan that describes the safeguards in place or planned for meeting the security requirements is developed.Maps to 3.12.4[e]
A.03.15.02.b[01]System Security Planthe system security plan is reviewed <A.03.15.02.ODP[01]: frequency>.Maps to 3.12.4.[h]
A.03.15.02.b[02]System Security Planthe system security plan is updated <A.03.15.02.ODP[01]: frequency>.Maps to 3.12.4.[h]
Moderate Effort

Moderate Effort AO Transition

If you already have controls in place for NIST 800-171 R2 and use NIST 800-171A, about one-fifth of the AOs in NIST 800-171A R3 should take moderate effort to transition.

NIST 800-171A R3 AOs With Indirect Mapping (Existing NIST 800-171 R3 Control)

These 110 AOs have "indirect mapping," which means parts of each NIST 800-171A R3 AO map back to an existing NIST 800-171A AO. Because the mapping is indirect, you will need a closer look at what the new AO requires.

NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.01.01.d.01Account Managementaccess to the system is authorized based on a valid access authorization.Elements of 3.1.1[c], 3.1.1[d], 3.1.1[e], 3.1.1[f]
A.03.01.01.d.02Account Managementaccess to the system is authorized based on intended system usage.Elements of 3.1.1[c], 3.1.1[d], 3.1.1[e], 3.1.1[f]
A.03.01.02[01]Access Enforcementapproved authorizations for logical access to CUI are enforced in accordance with applicable access control policies.Elements of 3.1.2[b]
A.03.01.02[02]Access Enforcementapproved authorizations for logical access to system resources are enforced in accordance with applicable access control policies.Elements of 3.1.2[b]
A.03.01.03[01]Information Flow Enforcementapproved authorizations are enforced for controlling the flow of CUI within the system.Elements of 3.1.3[e]
A.03.01.03[02]Information Flow Enforcementapproved authorizations are enforced for controlling the flow of CUI between connected systems.Elements of 3.1.3[e]
A.03.01.04.bSeparation of Dutiessystem access authorizations to support separation of duties are defined.Elements of 3.1.4[b], 3.1.4[c]
A.03.01.05.ODP[01]Least Privilegesecurity functions for authorized access are defined.Elements of 3.1.5[c], 3.13.3[a], 3.13.3[b], 3.13.3[c]
A.03.01.05.aLeast Privilegesystem access for users (or processes acting on behalf of users) is authorized only when necessary to accomplish assigned organizational tasks.Elements of 3.1.5[b]
A.03.01.06.ODP[01]Least Privilege - Privileged Accountspersonnel or roles to which privileged accounts on the system are to be restricted are defined.Elements of 3.13.3[a], 3.13.3[b], 3.13.3[c]
A.03.01.06.aLeast Privilege - Privileged Accountsprivileged accounts on the system are restricted to <A.03.01.06.ODP[01]: personnel or roles>.Elements of 3.13.3[a], 3.13.3[b], 3.13.3[c]
A.03.01.06.bLeast Privilege - Privileged Accountsusers (or roles) with privileged accounts are required to use non-privileged accounts when accessing non-security functions or non-security information.Elements of 3.13.3[a], 3.13.3[b], 3.13.3[c]
A.03.01.08.ODP[02]Unsuccessful Logon Attemptsthe time period to which the number of consecutive invalid logon attempts by a user is limited is defined.Elements of 3.1.8[b]
A.03.01.08.ODP[03]Unsuccessful Logon Attemptsone or more of the following PARAMETER VALUES are selected: {the account or node is locked automatically for <A.03.01.08.ODP[04]: time period>; the account or node is locked automatically until released by an administrator; the next logon prompt is delayed automatically; the system administrator is notified automatically; other action is taken automatically}.Elements of 3.1.8[b]
A.03.01.08.ODP[04]Unsuccessful Logon Attemptsthe time period for an account or node to be locked is defined (if selected).Elements of 3.1.8[b]
A.03.01.08.aUnsuccessful Logon Attemptsa limit of <A.03.01.08.ODP[01]: number> consecutive invalid logon attempts by a user during <A.03.01.08.ODP[02]: time period> is enforced.Elements of 3.1.8[b]
A.03.01.08.bUnsuccessful Logon Attempts<A.03.01.08.ODP[03]: SELECTED PARAMETER VALUES> when the maximum number of unsuccessful attempts is exceeded.Elements of 3.1.8[b]
A.03.01.12.a[02]Remote Accessusage restrictions are established for each type of allowable remote system access.Elements of 3.1.12[a], 3.1.12[c], 3.1.15[a], 3.1.15[b], 3.1.15[c], 3.1.15[d]
A.03.01.12.a[03]Remote Accessconfiguration requirements are established for each type of allowable remote system access.Elements of 3.1.12[c], 3.1.13[a], 3.1.13[b], 3.13.7
A.03.01.16.a[01]Wireless Accesseach type of wireless access to the system is defined.Elements of 3.1.16[a]
A.03.01.18.a[03]Access Control for Mobile Devicesconnection requirements are established for mobile devices.Elements of 3.1.18[b]
A.03.01.20.ODP[01]Use of External Systemssecurity requirements to be satisfied on external systems prior to allowing the use of or access to those systems by authorized individuals are defined.Elements of 3.1.20[e]
A.03.01.20.aUse of External Systemsthe use of external systems is prohibited unless the systems are specifically authorized.Elements of 3.1.21[a], 3.1.21[b], 3.1.21[c]
A.03.01.20.bUse of External Systemsthe following security requirements to be satisfied on external systems prior to allowing the use of or access to those systems by authorized individuals are established: <A.03.01.20.ODP[01]: security requirements>.Elements of 3.1.20[e], 3.1.20[f]
A.03.01.20.c.01Use of External Systemsauthorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after verifying that the security requirements on the external systems as specified in the organization’s system security plans have been satisfied.Elements of 3.1.20[c]
A.03.01.20.c.02Use of External Systemsauthorized individuals are permitted to use external systems to access the organizational system or to process, store, or transmit CUI only after retaining approved system connection or processing agreements with the organizational entity hosting the external systems.Elements of 3.1.20[e], 3.1.20[f]
A.03.01.20.dUse of External Systemsthe use of organization-controlled portable storage devices by authorized individuals on external systems is restricted.Elements of 3.1.20[f]
A.03.02.01.a.01[01]Literacy Training and Awarenesssecurity literacy training is provided to system users as part of initial training for new users.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.01[02]Literacy Training and Awarenesssecurity literacy training is provided to system users <A.03.02.01.ODP[01]: frequency> after initial training.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.02Literacy Training and Awarenesssecurity literacy training is provided to system users when required by system changes or following <A.03.02.01.ODP[02]: events>.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.03[02]Literacy Training and Awarenesssecurity literacy training is provided to system users on reporting indicators of insider threat.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.03[03]Literacy Training and Awarenesssecurity literacy training is provided to system users on recognizing indicators of social engineering.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.03[04]Literacy Training and Awarenesssecurity literacy training is provided to system users on reporting indicators of social engineering.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.03[05]Literacy Training and Awarenesssecurity literacy training is provided to system users on recognizing indicators of social mining.Elements of 3.2.1[c], 3.2.1[d]
A.03.02.01.a.03[06]Literacy Training and Awarenesssecurity literacy training is provided to system users on reporting indicators of social mining.Elements of 3.2.1[c], 3.2.1[d]
A.03.03.01.b[01]Event Loggingthe event types selected for logging are reviewed <A.03.03.01.ODP[02]: frequency>.Elements of 3.3.3[a], 3.3.3[b]
A.03.03.02.a.01Audit Record Contentaudit records contain information that establishes what type of event occurred.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.a.02Audit Record Contentaudit records contain information that establishes when the event occurred.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.a.03Audit Record Contentaudit records contain information that establishes where the event occurred.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.a.04Audit Record Contentaudit records contain information that establishes the source of the event.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.a.05Audit Record Contentaudit records contain information that establishes the outcome of the event.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.a.06Audit Record Contentaudit records contain information that establishes the identity of the individuals, subjects, objects, or entities associated with the event.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.02.bAudit Record Contentadditional information for audit records is provided, as needed.Elements of 3.3.2[a], 3.3.2[b]
A.03.03.06.a[04]Audit Record Reduction and Report Generationan audit record reduction and report generation capability that supports after-the-fact investigations of incidents is implemented.Elements of 3.3.6[a], 3.3.6[b]
A.03.03.06.b[01]Audit Record Reduction and Report Generationthe original content of audit records is preserved.Elements of 3.3.1[e]
A.03.03.06.b[02]Audit Record Reduction and Report Generationthe original time ordering of audit records is preserved.Elements of 3.3.1[e], 3.3.7[a]
A.03.04.01.ODP[01]Baseline Configurationthe frequency of baseline configuration review and update is defined.Elements of 3.4.1[c] and NFO - CM-2(1)
A.03.04.01.b[01]Baseline Configurationthe baseline configuration of the system is reviewed <A.03.04.01.ODP[01]: frequency>.Elements of 3.4.1[c]
A.03.04.01.b[02]Baseline Configurationthe baseline configuration of the system is updated <A.03.04.01.ODP[01]: frequency>.Elements of 3.4.1[c]
A.03.04.01.b[03]Baseline Configurationthe baseline configuration of the system is reviewed when system components are installed or modified.Elements of 3.4.1[c]
A.03.04.01.b[04]Baseline Configurationthe baseline configuration of the system is updated when system components are installed or modified.Elements of 3.4.1[c]
A.03.04.02.a[02]Configuration Settingsthe following configuration settings for the system are implemented: <A.03.04.02.ODP[01]: configuration settings>.Elements of 3.4.2[a]
A.03.04.02.b[01]Configuration Settingsany deviations from established configuration settings are identified and documented.Elements of 3.4.2[b]
A.03.04.02.b[02]Configuration Settingsany deviations from established configuration settings are approved.Elements of 3.4.2[b]
A.03.04.03.c[01]Configuration Change Controlapproved configuration-controlled changes to the system are implemented.Elements of 3.7.1
A.03.04.06.ODP[01]Least Functionalityfunctions to be prohibited or restricted are defined.Elements of multiple 3.4.7 AOs. No clear mapping.
A.03.04.06.ODP[02]Least Functionalityports to be prohibited or restricted are defined.Elements of multiple 3.4.7 AOs and NFO - SA-9(2). No clear mapping.
A.03.04.06.ODP[03]Least Functionalityprotocols to be prohibited or restricted are defined.Elements of multiple 3.4.7 AOs and NFO - SA-9(2). No clear mapping.
A.03.04.06.ODP[04]Least Functionalityconnections to be prohibited or restricted are defined.Elements of multiple 3.4.7 AOs. No clear mapping.
A.03.04.06.ODP[05]Least Functionalityservices to be prohibited or restricted are defined.Elements of multiple 3.4.7 AOs and NFO - SA-9(2). No clear mapping.
A.03.04.06.ODP[06]Least Functionalitythe frequency at which to review the system to identify unnecessary or nonsecure functions, ports, protocols, connections, or services is defined.Elements of multiple 3.4.7 AOs. No clear mapping.
A.03.04.06.aLeast Functionalitythe system is configured to provide only mission-essential capabilities.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.b[01]Least Functionalitythe use of the following functions is prohibited or restricted: <A.03.04.06.ODP[01]: functions>.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.b[02]Least Functionalitythe use of the following ports is prohibited or restricted: <A.03.04.06.ODP[02]: ports>.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.b[03]Least Functionalitythe use of the following protocols is prohibited or restricted: <A.03.04.06.ODP[03]: protocols>.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.b[04]Least Functionalitythe use of the following connections is prohibited or restricted: <A.03.04.06.ODP[04]: connections>.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.b[05]Least Functionalitythe use of the following services is prohibited or restricted: <A.03.04.06.ODP[05]: services>.Elements of multiple 3.4.7 AOs, 3.13.7 and 3.13.14[a]. No clear mapping.
A.03.04.06.cLeast Functionalitythe system is reviewed <A.03.04.06.ODP[06]: frequency> to identify unnecessary or nonsecure functions, ports, protocols, connections, and services.Elements of multiple 3.4.7 AOs. No clear mapping.
A.03.04.06.dLeast Functionalityunnecessary or nonsecure functions, ports, protocols, connections, and services are disabled or removed.Elements of multiple 3.4.7 AOs. No clear mapping.
A.03.04.08.ODP[01]Authorized Software - Allow by Exceptionthe frequency at which to review and update the list of authorized software programs is defined.Elements of 3.4.9[c]
A.03.04.08.cAuthorized Software - Allow by Exceptionthe list of authorized software programs is reviewed and updated <A.03.04.08.ODP[01]: frequency>.Elements of 3.4.9[c]
A.03.04.10.b[01]System Component Inventorythe system component inventory is reviewed <A.03.04.10.ODP[01]: frequency>.Elements exist in NIST 800-171A R3 as 3.4.1[f]
A.03.04.10.b[02]System Component Inventorythe system component inventory is updated <A.03.04.10.ODP[01]: frequency>.Elements exist in NIST 800-171A R3 as 3.4.1[f]
A.03.04.10.c[01]System Component Inventorythe system component inventory is updated as part of component installations.Elements exist in NIST 800-171A R3 as 3.4.1[f]
A.03.04.10.c[02]System Component Inventorythe system component inventory is updated as part of component removals.Elements exist in NIST 800-171A R3 as 3.4.1[f]
A.03.04.10.c[03]System Component Inventorythe system component inventory is updated as part of system updates.Elements exist in NIST 800-171A R3 as 3.4.1[f]
A.03.05.01.a[01]User Identification and Authenticationsystem users are uniquely identified.Elements of 3.5.1[a], 3.5.1[b], 3.5.1[c]
A.03.05.05.ODP[01]Identifier Managementthe time period for preventing the reuse of identifiers is defined.3.5.5[a]
A.03.05.05.cIdentifier Managementthe reuse of identifiers for <A.03.05.05.ODP[01]: time period> is prevented.3.5.5[b]
A.03.05.07.ePassword Managementa new password is selected upon first use after account recovery.elements of 3.5.9
A.03.05.07.fPassword Managementthe following composition and complexity rules for passwords are enforced: <A.03.05.07.ODP[02]: rules>.elements of 3.5.7[c], 3.5.7[d]
A.03.07.04.a[01]Maintenance Toolsthe use of system maintenance tools is approved.Elements of 3.7.2[b], 3.7.2[c]
A.03.07.06.aMaintenance Personnela process for maintenance personnel authorization is established.Elements of 3.7.2[d]
A.03.07.06.bMaintenance Personnela list of authorized maintenance organizations or personnel is maintained.Elements of 3.7.2[d]
A.03.07.06.cMaintenance Personnelnon-escorted personnel who perform maintenance on the system possess the required access authorizations.Elements of 3.7.2[d]
A.03.07.06.d[01]Maintenance Personnelorganizational personnel with required access authorizations are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.Elements of 3.7.6
A.03.07.06.d[02]Maintenance Personnelorganizational personnel with required technical competence are designated to supervise the maintenance activities of personnel who do not possess the required access authorizations.Elements of 3.7.6
A.03.09.02.a.01Personnel Termination and Transferupon termination of individual employment, system access is disabled within <A.03.09.02.ODP[01]: time period>.Elements of 3.9.2[a]
A.03.09.02.a.02[01]Personnel Termination and Transferupon termination of individual employment, authenticators associated with the individual are terminated or revoked.Elements of 3.9.2[b]
A.03.09.02.a.02[02]Personnel Termination and Transferupon termination of individual employment, credentials associated with the individual are terminated or revoked.Elements of 3.9.2[b]
A.03.09.02.b.01[01]Personnel Termination and Transferupon individual reassignment or transfer to other positions in the organization, the ongoing operational need for current logical and physical access authorizations to the system and facility is reviewed.Elements of 3.9.2[b]
A.03.09.02.b.01[02]Personnel Termination and Transferupon individual reassignment or transfer to other positions in the organization, the ongoing operational need for current logical and physical access authorizations to the system and facility is confirmed.Elements of 3.9.2[b]
A.03.09.02.b.02Personnel Termination and Transferupon individual reassignment or transfer to other positions in the organization, access authorization is modified to correspond with any changes in operational need.Elements of 3.9.2[c]
A.03.10.07.c[02]Physical Access Controlvisitor activity is controlled.Elements of 3.10.3[b] and NFO - PE-8
A.03.10.07.dPhysical Access Controlkeys, combinations, and other physical access devices are secured.Elements of 3.10.5[a], 3.10.5[b], 3.10.5[c]
A.03.11.02.a[03]Vulnerability Monitoring and Scanningthe system is monitored for vulnerabilities when new vulnerabilities that affect the system are identified.Elements of 3.11.3[a]
NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.11.02.bVulnerability Monitoring and Scanningsystem vulnerabilities are remediated within <A.03.11.02.ODP[03]: response times>.Elements of 3.11.3[b]
A.03.12.02.a.01Plan of Action and Milestonesa plan of action and milestones for the system is developed to document the planned remediation actions for correcting weaknesses or deficiencies noted during security assessments.Elements of 3.12.2[a], 3.12.2[b], 3.12.2[c]
A.03.12.02.a.02Plan of Action and Milestonesa plan of action and milestones for the system is developed to reduce or eliminate known system vulnerabilities.Elements of 3.12.2[a], 3.12.2[b], 3.12.2[c]
A.03.12.03[01]Continuous Monitoringa system-level continuous monitoring strategy is developed.Elements of 3.12.3
A.03.12.03[02]Continuous Monitoringa system-level continuous monitoring strategy is implemented.Elements of 3.12.3
A.03.12.03[03]Continuous Monitoringongoing monitoring is included in the continuous monitoring strategy.Elements of 3.12.3
A.03.12.03[04]Continuous Monitoringsecurity assessments are included in the continuous monitoring strategy.Elements of 3.12.3
A.03.13.01.bBoundary Protectionsubnetworks are implemented for publicly accessible system components that are physically or logically separated from internal networks.Elements of 3.13.5[b]
A.03.13.11Cryptographic Protectionthe following types of cryptography are implemented to protect the confidentiality of CUI: <A.03.13.11.ODP[01]: types of cryptography>.Elements of 3.13.11
A.03.16.01.ODP[01]Security Engineering Principlessystems security engineering principles to be applied to the development or modification of the system and system components are defined.Elements of 3.13.2[a], 3.13.2[b], 3.13.2[c], 3.13.2[d], 3.13.2[e], 3.13.2[f] and NFO - PL-8
A.03.16.01Security Engineering Principles<A.03.16.01.ODP[01]: systems security engineering principles> are applied to the development or modification of the system and system components.Elements of 3.13.2[a], 3.13.2[b], 3.13.2[c], 3.13.2[d], 3.13.2[e], 3.13.2[f] and NFO - PL-8
A.03.16.03.ODP[01]External System Servicessecurity requirements to be satisfied by external system service providers are defined.Elements of 3.1.20[f]
A.03.16.03.aExternal System Servicesthe providers of external system services used for the processing, storage, or transmission of CUI comply with the following security requirements: <A.03.16.03.ODP[01]: security requirements>.Elements of 3.1.20[f]
A.03.16.03.bExternal System Servicesuser roles and responsibilities with regard to external system services, including shared responsibilities with external service providers, are defined and documented.Elements of 3.2.2[a], 3.2.2[b]
Significant Effort

Significant Effort AO Transition

If you already have controls in place for NIST 800-171 R2 and use NIST 800-171A, about half of the AOs in NIST 800-171A R3 should be treated as significant effort.

NIST 800-171A R3 AOs With No Clear Mapping (Existing NIST 800-171 R3 Control)

These 57 AOs have no clear mapping back to an existing NIST 800-171A AO, so you will need a detailed analysis of what each one requires.

NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.01.01.ODP[02]Account Managementthe time period within which to notify account managers and designated personnel or roles when accounts are no longer required is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.01.ODP[03]Account Managementthe time period within which to notify account managers and designated personnel or roles when users are terminated or transferred is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.01.ODP[04]Account Managementthe time period within which to notify account managers and designated personnel or roles when system usage or the need-to-know changes for an individual is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.01.ODP[05]Account Managementthe time period of expected inactivity requiring users to log out of the system is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.01.ODP[06]Account Managementcircumstances requiring users to log out of the system are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.05.ODP[02]Least Privilegesecurity-relevant information for authorized access is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.05.ODP[03]Least Privilegethe frequency at which to review the privileges assigned to roles or classes of users is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.12.a[04]Remote Accessconnection requirements are established for each type of allowable remote system access.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.16.a[02]Wireless Accessusage restrictions are established for each type of wireless access to the system.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.18.a[01]Access Control for Mobile Devicesusage restrictions are established for mobile devices.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.18.a[02]Access Control for Mobile Devicesconfiguration requirements are established for mobile devices.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.01.22.aPublicly Accessible Contentauthorized individuals are trained to ensure that publicly accessible information does not contain CUI.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.01.ODP[01]Literacy Training and Awarenessthe frequency at which to provide security literacy training to system users after initial training is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.01.ODP[02]Literacy Training and Awarenessevents that require security literacy training for system users are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.01.ODP[03]Literacy Training and Awarenessthe frequency at which to update security literacy training content is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.01.ODP[04]Literacy Training and Awarenessevents that require security literacy training content updates are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.02.ODP[01]Role-Based Trainingthe frequency at which to provide role-based security training to assigned personnel after initial training is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.02.ODP[02]Role-Based Trainingevents that require role-based security training are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.02.02.ODP[03]Role-Based Trainingthe frequency at which to update role-based security training content is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.03.01.ODP[02]Event Loggingthe frequency of event types selected for logging are reviewed and updated.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.03.04.ODP[01]Response to Audit Logging Process Failuresthe time period for organizational personnel or roles receiving audit logging process failure alerts is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.03.04.ODP[02]Response to Audit Logging Process Failuresadditional actions to be taken in the event of an audit logging process failure are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.03.05.ODP[01]Audit Record Review, Analysis, and Reportingthe frequency at which system audit records are reviewed and analyzed is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.03.07.ODP[01]Time Stampsgranularity of time measurement for audit record time stamps is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.04.03.aConfiguration Change Controlthe types of changes to the system that are configuration-controlled are defined.Elements of NFO - CM-9
A.03.04.12.ODP[01]System and Component Configuration for High-Risk Areasconfigurations for systems or system components to be issued to individuals traveling to high-risk locations are defined.Elements of NFO - CM-2(7)
A.03.05.01.ODP[01]User Identification and Authenticationcircumstances or situations that require re-authentication are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.05.02.ODP[01]Device Identification and Authenticationdevices or types of devices to be uniquely identified and authenticated before establishing a connection are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.05.02[01]Device Identification and Authentication<A.03.05.02.ODP[01]: devices or types of devices> are uniquely identified before establishing a system connection.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.05.05.ODP[02]Identifier Managementcharacteristic used to identify individual status are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.05.07.a[01]Password Managementa list of commonly used, expected, or compromised passwords is maintained.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.05.07.a[02]Password Managementa list of commonly used, expected, or compromised passwords is updated <A.03.05.07.ODP[01]: frequency>.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.06.02.ODP[01]Incident Monitoring, Reporting, and Response Assistancethe time period to report suspected incidents to the organizational incident response capability is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.07.05.a[01]Nonlocal Maintenancenonlocal maintenance and diagnostic activities are approved.Elements of NFO - MA-4(2)
A.03.07.05.a[02]Nonlocal Maintenancenonlocal maintenance and diagnostic activities are monitored.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.08.04[02]Media Markingsystem media that contain CUI are marked to indicate handling caveats.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.09.02.ODP[01]Personnel Termination and Transferthe time period within which to disable system access is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.10.01.ODP[01]Physical Access Authorizationsthe frequency at which to review the access list detailing authorized facility access by individuals is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.10.02.ODP[01]Monitoring Physical Accessthe frequency at which to review physical access logs is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.10.02.ODP[02]Monitoring Physical Accessevents or potential indications of events requiring physical access logs to be reviewed are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.10.02.a[02]Monitoring Physical Accessphysical security incidents are responded to.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.10.06.aAlternate Work Sitealternate work sites allowed for use by employees are determined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.11.02.ODP[01]Vulnerability Monitoring and Scanningthe frequency at which the system is monitored for vulnerabilities is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.11.02.ODP[03]Vulnerability Monitoring and Scanningresponse times to remediate system vulnerabilities are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.11.02.ODP[04]Vulnerability Monitoring and Scanningthe frequency at which to update system vulnerabilities to be scanned is defined.Elements of NFO - RA-5(1), RA-5(2)
A.03.11.02.a[01]Vulnerability Monitoring and Scanningthe system is monitored for vulnerabilities <A.03.11.02.ODP[01]: frequency>.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.12.02.b.01Plan of Action and Milestonesthe existing plan of action and milestones is updated based on the findings from security assessments.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.13.01.cBoundary Protectionexternal system connections are only made through managed interfaces that consist of boundary protection devices arranged in accordance with an organizational security architecture.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.13.10.ODP[01]Cryptographic Key Establishment and Managementrequirements for key generation, distribution, storage, access, and destruction are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.13.12.ODP[01]Collaborative Computing Devices and Applicationsexceptions where remote activation is to be allowed are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.13.13.a[01]Mobile Codeacceptable mobile code is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.13.13.a[02]Mobile Codeacceptable mobile code technologies are defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.14.01.ODP[01]Flaw Remediationthe time period within which to install security-relevant software updates after the release of the updates is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.14.01.ODP[02]Flaw Remediationthe time period within which to install security-relevant firmware updates after the release of the updates is defined.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.14.01.b[01]Flaw Remediationsecurity-relevant software updates are installed within <A.03.14.01.ODP[01]: time period> of the release of the updates.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.14.03.b[01]Security Alerts, Advisories, and Directivesinternal security alerts, advisories, and directives are generated, as necessary.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A
A.03.14.03.b[02]Security Alerts, Advisories, and Directivesinternal security alerts, advisories, and directives are disseminated, as necessary.This NIST 800-171A R3 AO does not have a clear link to an AO from the previous version of NIST 800-171A

NIST 800-171A R3 AOs With No Transition Path (Newly Added NIST 800-171 R3 Control)

These 172 AOs belong to new NIST 800-171 R3 controls. They are net new AOs, with no existing AO to transition from.

NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.01.01.a[01]Account Managementsystem account types allowed are defined.AO is new for NIST 800-171A R3
A.03.01.01.a[02]Account Managementsystem account types prohibited are defined.AO is new for NIST 800-171A R3
A.03.01.01.b[01]Account Managementsystem accounts are created in accordance with organizational policy, procedures, prerequisites, and criteria.AO is new for NIST 800-171A R3
A.03.01.01.b[02]Account Managementsystem accounts are enabled in accordance with organizational policy, procedures, prerequisites, and criteria.AO is new for NIST 800-171A R3
A.03.01.01.b[03]Account Managementsystem accounts are modified in accordance with organizational policy, procedures, prerequisites, and criteria.AO is new for NIST 800-171A R3
A.03.01.01.b[04]Account Managementsystem accounts are disabled in accordance with organizational policy, procedures, prerequisites, and criteria.AO is new for NIST 800-171A R3
A.03.01.01.b[05]Account Managementsystem accounts are removed in accordance with organizational policy, procedures, prerequisites, and criteria.AO is new for NIST 800-171A R3
A.03.01.01.c.02Account Managementgroup and role memberships are specified.AO is new for NIST 800-171A R3
A.03.01.01.c.03Account Managementaccess authorizations (i.e., privileges) for each account are specified.AO is new for NIST 800-171A R3
A.03.01.01.eAccount Managementthe use of system accounts is monitored.AO is new for NIST 800-171A R3
A.03.01.01.f.01Account Managementsystem accounts are disabled when the accounts have expired.AO is new for NIST 800-171A R3
A.03.01.01.f.03Account Managementsystem accounts are disabled when the accounts are no longer associated with a user or individual.AO is new for NIST 800-171A R3
A.03.01.01.f.04Account Managementsystem accounts are disabled when the accounts violate organizational policy.AO is new for NIST 800-171A R3
A.03.01.01.f.05Account Managementsystem accounts are disabled when significant risks associated with individuals are discovered.AO is new for NIST 800-171A R3
A.03.01.01.g.01Account Managementaccount managers and designated personnel or roles are notified within <A.03.01.01.ODP[02]: time period> when accounts are no longer required.AO is new for NIST 800-171A R3
A.03.01.01.g.02Account Managementaccount managers and designated personnel or roles are notified within <A.03.01.01.ODP[03]: time period> when users are terminated or transferred.AO is new for NIST 800-171A R3
A.03.01.01.g.03Account Managementaccount managers and designated personnel or roles are notified within <A.03.01.01.ODP[04]: time period> when system usage or the need-to-know changes for an individual.AO is new for NIST 800-171A R3
A.03.01.01.hAccount Managementusers are required to log out of the system after <A.03.01.01.ODP[05]: time period> of expected inactivity or when the following circumstances occur: <A.03.01.01.ODP[06]: circumstances>.AO is new for NIST 800-171A R3
A.03.01.05.b[02]Least Privilegeaccess to <A.03.01.05.ODP[02]: security-relevant information> is authorized.AO is new for NIST 800-171A R3
A.03.01.05.cLeast Privilegethe privileges assigned to roles or classes of users are reviewed <A.03.01.05.ODP[03]: frequency> to validate the need for such privileges.AO is new for NIST 800-171A R3
A.03.01.05.dLeast Privilegeprivileges are reassigned or removed, as necessary.AO is new for NIST 800-171A R3
A.03.01.10.bDevice Lockthe device lock is retained until the user reestablishes access using established identification and authentication procedures.AO is new for NIST 800-171A R3
A.03.01.12.bRemote Accesseach type of remote system access is authorized prior to establishing such connections.AO is new for NIST 800-171A R3
A.03.01.12.c[01]Remote Accessremote access to the system is routed through authorized access control points.AO is new for NIST 800-171A R3. Elements of NFO - SC-7(3)
A.03.01.12.d[1]Remote Accessremote execution of privileged commands is authorized.AO is new for NIST 800-171A R3
A.03.01.12.d[2]Remote Accessremote access to security-relevant information is authorized.AO is new for NIST 800-171A R3
A.03.01.16.a[03]Wireless Accessconfiguration requirements are established for each type of wireless access to the system.AO is new for NIST 800-171A R3
A.03.01.16.a[04]Wireless Accessconnection requirements are established for each type of wireless access to the system.AO is new for NIST 800-171A R3
A.03.01.16.cWireless Accesswireless networking capabilities not intended for use are disabled prior to issuance and deployment.AO is new for NIST 800-171A R3
A.03.02.01.b[01]Literacy Training and Awarenesssecurity literacy training content is updated <A.03.02.01.ODP[03]: frequency>.AO is new for NIST 800-171A R3
A.03.02.01.b[02]Literacy Training and Awarenesssecurity literacy training content is updated following <A.03.02.01.ODP[04]: events>.AO is new for NIST 800-171A R3
A.03.02.02.ODP[04]Role-Based Trainingevents that require role-based security training content updates are defined.AO is new for NIST 800-171A R3
A.03.02.02.b[02]Role-Based Trainingrole-based security training content is updated following <A.03.02.02.ODP[04]: events>.AO is new for NIST 800-171A R3
A.03.03.04.bResponse to Audit Logging Process Failuresthe following additional actions are taken: <A.03.03.04.ODP[02]: additional actions>.AO is new for NIST 800-171A R3
A.03.03.05.bAudit Record Review, Analysis, and Reportingfindings are reported to organizational personnel or roles.AO is new for NIST 800-171A R3
A.03.03.07.b[02]Time Stampstime stamps are recorded for audit records that use Coordinated Universal Time (UTC), have a fixed local time offset from UTC, or include the local time offset as part of the time stamp.AO is new for NIST 800-171A R3
A.03.04.03.d[01]Configuration Change Controlactivities associated with configuration-controlled changes to the system are monitored.AO is new for NIST 800-171A R3
A.03.04.03.d[02]Configuration Change Controlactivities associated with configuration-controlled changes to the system are reviewed.AO is new for NIST 800-171A R3
A.03.04.04.bImpact Analysesthe security requirements for the system continue to be satisfied after the system changes have been implemented.AO is new for NIST 800-171A R3
A.03.04.10.ODP[01]System Component Inventorythe frequency at which to review and update the system component inventory is defined.AO is new for NIST 800-171A R3
A.03.04.11.a[01]Information Locationthe location of CUI is identified and documented.AO is new for NIST 800-171A R3
A.03.04.11.a[02]Information Locationthe system components on which CUI is processed are identified and documented.AO is new for NIST 800-171A R3
A.03.04.11.a[03]Information Locationthe system components on which CUI is stored are identified and documented.AO is new for NIST 800-171A R3
A.03.04.11.b[01]Information Locationchanges to the system or system component location where CUI is processed are documented.AO is new for NIST 800-171A R3
A.03.04.11.b[02]Information Locationchanges to the system or system component location where CUI is stored are documented.AO is new for NIST 800-171A R3
A.03.04.12.ODP[02]System and Component Configuration for High-Risk Areassecurity requirements to be applied to the system or system components when individuals return from travel are defined.AO is new for NIST 800-171A R3
A.03.04.12.aSystem and Component Configuration for High-Risk Areassystems or system components with the following configurations are issued to individuals traveling to high-risk locations: <A.03.04.12.ODP[01]: configurations>.AO is new for NIST 800-171A R3
A.03.04.12.bSystem and Component Configuration for High-Risk Areasthe following security requirements are applied to the system or system components when the individuals return from travel: <A.03.04.12.ODP[02]: security requirements>.AO is new for NIST 800-171A R3
A.03.05.01.bUser Identification and Authenticationusers are reauthenticated when <A.03.05.01.ODP[01]: circumstances or situations>.AO is new for NIST 800-171A R3
A.03.05.05.aIdentifier Managementauthorization is received from organizational personnel or roles to assign an individual, group, role, service, or device identifier.AO is new for NIST 800-171A R3
A.03.05.05.b[01]Identifier Managementan identifier that identifies an individual, group, role, service, or device is selected.AO is new for NIST 800-171A R3
A.03.05.05.b[02]Identifier Managementan identifier that identifies an individual, group, role, service, or device is assigned.AO is new for NIST 800-171A R3
A.03.05.05.dIdentifier Managementindividual identifiers are managed by uniquely identifying each individual as <A.03.05.05.ODP[02]: characteristic>.AO is new for NIST 800-171A R3
A.03.05.07.a[03]Password Managementa list of commonly used, expected, or compromised passwords is updated when organizational passwords are suspected to have been compromised.AO is new for NIST 800-171A R3
A.03.05.07.bPassword Managementpasswords are verified not to be found on the list of commonly used, expected, or compromised passwords when they are created or updated by users.AO is new for NIST 800-171A R3
A.03.05.12.ODP[01]Authenticator Managementthe frequency for changing or refreshing authenticators is defined.AO is new for NIST 800-171A R3
A.03.05.12.ODP[02]Authenticator Managementevents that trigger the change or refreshment of authenticators are defined.AO is new for NIST 800-171A R3
A.03.05.12.aAuthenticator Managementthe identity of the individual, group, role, service, or device receiving the authenticator as part of the initial authenticator distribution is verified.AO is new for NIST 800-171A R3
A.03.05.12.bAuthenticator Managementinitial authenticator content for any authenticators issued by the organization is established.AO is new for NIST 800-171A R3
A.03.05.12.c[01]Authenticator Managementadministrative procedures for initial authenticator distribution are established.AO is new for NIST 800-171A R3
A.03.05.12.c[02]Authenticator Managementadministrative procedures for lost, compromised, or damaged authenticators are established.AO is new for NIST 800-171A R3
A.03.05.12.c[03]Authenticator Managementadministrative procedures for revoking authenticators are established.AO is new for NIST 800-171A R3
A.03.05.12.c[04]Authenticator Managementadministrative procedures for initial authenticator distribution are implemented.AO is new for NIST 800-171A R3
A.03.05.12.c[05]Authenticator Managementadministrative procedures for lost, compromised, or damaged authenticators are implemented.AO is new for NIST 800-171A R3
A.03.05.12.c[06]Authenticator Managementadministrative procedures for revoking authenticators are implemented.AO is new for NIST 800-171A R3
A.03.05.12.dAuthenticator Managementdefault authenticators are changed at first use.AO is new for NIST 800-171A R3
A.03.05.12.eAuthenticator Managementauthenticators are changed or refreshed <A.03.05.12.ODP[01]: frequency> or when the following events occur: <A.03.05.12.ODP[02]: events>.AO is new for NIST 800-171A R3
A.03.05.12.f[01]Authenticator Managementauthenticator content is protected from unauthorized disclosure.AO is new for NIST 800-171A R3
A.03.05.12.f[02]Authenticator Managementauthenticator content is protected from unauthorized modification.AO is new for NIST 800-171A R3
A.03.06.02.dIncident Monitoring, Reporting, and Response Assistancean incident response support resource that offers advice and assistance to system users on handling and reporting incidents is provided.AO is new for NIST 800-171A R3
A.03.06.03.ODP[01]Incident Response Testingthe frequency at which to test the effectiveness of the incident response capability for the system is defined.AO is new for NIST 800-171A R3
A.03.06.04.ODP[01]Incident Response Trainingthe time period within which incident response training is to be provided to system users is defined.AO is new for NIST 800-171A R3
A.03.06.04.ODP[02]Incident Response Trainingthe frequency at which to provide incident response training to users after initial training is defined.AO is new for NIST 800-171A R3
A.03.06.04.ODP[03]Incident Response Trainingthe frequency at which to review and update incident response training content is defined.AO is new for NIST 800-171A R3
A.03.06.04.ODP[04]Incident Response Trainingevents that initiate a review of the incident response training content are defined.AO is new for NIST 800-171A R3
A.03.06.04.a.01Incident Response Trainingincident response training for system users consistent with assigned roles and responsibilities is provided within <A.03.06.04.ODP[01]: time period> of assuming an incident response role or responsibility or acquiring system access.AO is new for NIST 800-171A R3
A.03.06.04.a.02Incident Response Trainingincident response training for system users consistent with assigned roles and responsibilities is provided when required by system changes.AO is new for NIST 800-171A R3
A.03.06.04.a.03Incident Response Trainingincident response training for system users consistent with assigned roles and responsibilities is provided <A.03.06.04.ODP[02]: frequency> thereafter.AO is new for NIST 800-171A R3
A.03.06.04.b[01]Incident Response Trainingincident response training content is reviewed <A.03.06.04.ODP[03]: frequency>.AO is new for NIST 800-171A R3
A.03.06.04.b[02]Incident Response Trainingincident response training content is updated <A.03.06.04.ODP[03]: frequency>.AO is new for NIST 800-171A R3
A.03.06.04.b[03]Incident Response Trainingincident response training content is reviewed following <A.03.06.04.ODP[04]: events>.AO is new for NIST 800-171A R3
A.03.06.04.b[04]Incident Response Trainingincident response training content is updated following <A.03.06.04.ODP[04]: events>.AO is new for NIST 800-171A R3
A.03.06.05.a.01Incident Response Planan incident response plan is developed that provides the organization with a roadmap for implementing its incident response capability.AO is new for NIST 800-171A R3
A.03.06.05.a.02Incident Response Planan incident response plan is developed that describes the structure and organization of the incident response capability.AO is new for NIST 800-171A R3
A.03.06.05.a.03Incident Response Planan incident response plan is developed that provides a high-level approach for how the incident response capability fits into the overall organization.AO is new for NIST 800-171A R3
A.03.06.05.a.04Incident Response Planan incident response plan is developed that defines reportable incidents.AO is new for NIST 800-171A R3
A.03.06.05.a.05Incident Response Planan incident response plan is developed that addresses the sharing of incident information.AO is new for NIST 800-171A R3
A.03.06.05.a.06Incident Response Planan incident response plan is developed that designates responsibilities to organizational entities, personnel, or roles.AO is new for NIST 800-171A R3
A.03.06.05.b[01]Incident Response Plancopies of the incident response plan are distributed to designated incident response personnel (identified by name or by role).AO is new for NIST 800-171A R3
A.03.06.05.b[02]Incident Response Plancopies of the incident response plan are distributed to organizational elements.AO is new for NIST 800-171A R3
A.03.06.05.cIncident Response Planthe incident response plan is updated to address system and organizational changes or problems encountered during plan implementation, execution, or testing.AO is new for NIST 800-171A R3
A.03.06.05.dIncident Response Planthe incident response plan is protected from unauthorized disclosure.AO is new for NIST 800-171A R3
A.03.07.04.a[03]Maintenance Toolsthe use of system maintenance tools is monitored.AO is new for NIST 800-171A R3
A.03.07.04.cMaintenance Toolsthe removal of system maintenance equipment containing CUI is prevented by verifying that there is no CUI on the equipment, sanitizing or destroying the equipment, or retaining the equipment within the facility.AO is new for NIST 800-171A R3
A.03.07.05.b[02]Nonlocal Maintenancereplay resistance is implemented in the establishment of nonlocal maintenance and diagnostic sessions.AO is new for NIST 800-171A R3
A.03.08.05.cMedia Transportactivities associated with the transport of system media that contain CUI are documented.AO is new for NIST 800-171A R3
A.03.08.07.ODP[01]Media Usetypes of system media with usage restrictions or that are prohibited from use are defined.AO is new for NIST 800-171A R3
A.03.09.01.ODP[01]Personnel Screeningconditions that require the rescreening of individuals are defined.AO is new for NIST 800-171A R3
A.03.09.01.bPersonnel Screeningindividuals are rescreened in accordance with the following conditions: <A.03.09.01.ODP[01]: conditions>.AO is new for NIST 800-171A R3
A.03.09.02.a.03Personnel Termination and Transferupon termination of individual employment, security-related system property is retrieved.AO is new for NIST 800-171A R3
NIST 800-171A R3NIST 800-171 R3 Control NameNIST 800-171A R3 Assessment Objective (AO)NIST 800-171 R2 to R3 Upgrade Notes
A.03.10.01.cPhysical Access Authorizationsthe facility access list is reviewed <A.03.10.01.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.10.01.dPhysical Access Authorizationsindividuals from the facility access list are removed when access is no longer required.AO is new for NIST 800-171A R3
A.03.10.02.b[01]Monitoring Physical Accessphysical access logs are reviewed <A.03.10.02.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.10.02.b[02]Monitoring Physical Accessphysical access logs are reviewed upon occurrence of <A.03.10.02.ODP[02]: events or potential indicators of events>.AO is new for NIST 800-171A R3
A.03.10.07.a.01Physical Access Controlphysical access authorizations are enforced at entry and exit points to the facility where the system resides by verifying individual physical access authorizations before granting access.AO is new for NIST 800-171A R3
A.03.10.07.a.02Physical Access Controlphysical access authorizations are enforced at entry and exit points to the facility where the system resides by controlling ingress and egress with physical access control systems, devices, or guards.AO is new for NIST 800-171A R3
A.03.10.07.ePhysical Access Controlphysical access to output devices is controlled to prevent unauthorized individuals from obtaining access to CUI.AO is new for NIST 800-171A R3
A.03.10.08Access Control for Transmissionphysical access to system distribution and transmission lines within organizational facilities is controlled.AO is new for NIST 800-171A R3
A.03.11.02.c[01]Vulnerability Monitoring and Scanningsystem vulnerabilities to be scanned are updated <A.03.11.02.ODP[04]: frequency>.AO is new for NIST 800-171A R3
A.03.11.02.c[02]Vulnerability Monitoring and Scanningsystem vulnerabilities to be scanned are updated when new vulnerabilities are identified and reported.AO is new for NIST 800-171A R3
A.03.11.04[01]Risk Responsefindings from security assessments are responded to.AO is new for NIST 800-171A R3
A.03.11.04[02]Risk Responsefindings from security monitoring are responded to.AO is new for NIST 800-171A R3
A.03.11.04[03]Risk Responsefindings from security audits are responded to.AO is new for NIST 800-171A R3
A.03.12.02.b.02Plan of Action and Milestonesthe existing plan of action and milestones is updated based on the findings from audits or reviews.AO is new for NIST 800-171A R3
A.03.12.02.b.03Plan of Action and Milestonesthe existing plan of action and milestones is updated based on the findings from continuous monitoring activities.AO is new for NIST 800-171A R3
A.03.12.05.ODP[01]Information Exchangeone or more of the following PARAMETER VALUES are selected: {interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service-level agreements; user agreements; non-disclosure agreements; other types of agreements}.AO is new for NIST 800-171A R3
A.03.12.05.ODP[02]Information Exchangethe frequency at which to review and update agreements is defined.AO is new for NIST 800-171A R3
A.03.12.05.a[01]Information Exchangethe exchange of CUI between the system and other systems is approved using <A.03.12.05.ODP[01]: SELECTED PARAMETER VALUES>.AO is new for NIST 800-171A R3
A.03.12.05.a[02]Information Exchangethe exchange of CUI between the system and other systems is managed using <A.03.12.05.ODP[01]: SELECTED PARAMETER VALUES>.AO is new for NIST 800-171A R3
A.03.12.05.b[01]Information Exchangeinterface characteristics for each system are documented as part of the exchange agreements.AO is new for NIST 800-171A R3
A.03.12.05.b[02]Information Exchangesecurity requirements for each system are documented as part of the exchange agreements.AO is new for NIST 800-171A R3
A.03.12.05.b[03]Information Exchangeresponsibilities for each system are documented as part of the exchange agreements.AO is new for NIST 800-171A R3
A.03.12.05.c[01]Information Exchangeexchange agreements are reviewed <A.03.12.05.ODP[02]: frequency>.AO is new for NIST 800-171A R3
A.03.12.05.c[02]Information Exchangeexchange agreements are updated <A.03.12.05.ODP[02]: frequency>.AO is new for NIST 800-171A R3
A.03.13.11.ODP[01]Cryptographic Protectionthe types of cryptography for protecting the confidentiality of CUI are defined.AO is new for NIST 800-171A R3
A.03.14.01.b[02]Flaw Remediationsecurity-relevant firmware updates are installed within <A.03.14.01.ODP[02]: time period> of the release of the updates.AO is new for NIST 800-171A R3
A.03.14.02.c.02Malicious Code Protectionmalicious code protection mechanisms are configured to block malicious code, quarantine malicious code, or take other actions in response to malicious code detection.AO is new for NIST 800-171A R3
A.03.14.08[01]Information Management and RetentionCUI within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.AO is new for NIST 800-171A R3
A.03.14.08[02]Information Management and RetentionCUI within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.AO is new for NIST 800-171A R3
A.03.14.08[03]Information Management and RetentionCUI output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.AO is new for NIST 800-171A R3
A.03.14.08[04]Information Management and RetentionCUI output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.AO is new for NIST 800-171A R3
A.03.15.01.ODP[01]Policy and Proceduresthe frequency at which the policies and procedures for satisfying security requirements are reviewed and updated is defined.AO is new for NIST 800-171A R3
A.03.15.01.b[01]Policy and Procedurespolicies and procedures are reviewed <A.03.15.01.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.15.01.b[02]Policy and Procedurespolicies and procedures are updated <A.03.15.01.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.15.02.a.02System Security Plana system security plan that identifies the information types processed, stored, and transmitted by the system is developed.AO is new for NIST 800-171A R3
A.03.15.02.a.03System Security Plana system security plan that describes specific threats to the system that are of concern to the organization is developed.AO is new for NIST 800-171A R3
A.03.15.02.a.07System Security Plana system security plan that identifies individuals that fulfill system roles and responsibilities is developed.AO is new for NIST 800-171A R3
A.03.15.02.a.08System Security Plana system security plan that includes other relevant information necessary for the protection of CUI is developed.AO is new for NIST 800-171A R3
A.03.15.02.cSystem Security Planthe system security plan is protected from unauthorized disclosure.AO is new for NIST 800-171A R3
A.03.15.03.ODP[01]Rules of Behaviorthe frequency at which the rules of behavior are reviewed and updated is defined.AO is new for NIST 800-171A R3
A.03.15.03.aRules of Behaviorrules that describe responsibilities and expected behavior for system usage and protecting CUI are established.AO is new for NIST 800-171A R3. Elements of NFO - PL-4, PL-4(1)
A.03.15.03.bRules of Behaviorrules are provided to individuals who require access to the system.AO is new for NIST 800-171A R3
A.03.15.03.cRules of Behaviora documented acknowledgement from individuals indicating that they have read, understand, and agree to abide by the rules of behavior is received before authorizing access to CUI and the system.AO is new for NIST 800-171A R3. Elements of NFO - PS-6
A.03.15.03.d[01]Rules of Behaviorthe rules of behavior are reviewed <A.03.15.03.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.15.03.d[02]Rules of Behaviorthe rules of behavior are updated <A.03.15.03.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.16.02.aUnsupported System Componentssystem components are replaced when support for the components is no longer available from the developer, vendor, or manufacturer.AO is new for NIST 800-171A R3
A.03.16.02.bUnsupported System Componentsoptions for risk mitigation or alternative sources for continued support for unsupported components that cannot be replaced are provided.AO is new for NIST 800-171A R3
A.03.16.03.cExternal System Servicesprocesses, methods, and techniques to monitor security requirement compliance by external service providers on an ongoing basis are implemented.AO is new for NIST 800-171A R3
A.03.17.01.ODP[01]Supply Chain Risk Management Planthe frequency at which to review and update the supply chain risk management plan is defined.AO is new for NIST 800-171A R3
A.03.17.01.a[01]Supply Chain Risk Management Plana plan for managing supply chain risks is developed.AO is new for NIST 800-171A R3. Elements of NFO -PS-7
A.03.17.01.a[02]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the research and development of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[03]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the design of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[04]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the manufacturing of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[05]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the acquisition of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[06]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the delivery of the system, system components, or system services.AO is new for NIST 800-171A R3. Elements of NFO - PE-16
A.03.17.01.a[07]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the integration of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[08]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the operation of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[09]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the maintenance of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.a[10]Supply Chain Risk Management Planthe SCRM plan addresses risks associated with the disposal of the system, system components, or system services.AO is new for NIST 800-171A R3
A.03.17.01.b[01]Supply Chain Risk Management Planthe SCRM plan is reviewed <A.03.17.01.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.17.01.b[02]Supply Chain Risk Management Planthe SCRM plan is updated <A.03.17.01.ODP[01]: frequency>.AO is new for NIST 800-171A R3
A.03.17.01.cSupply Chain Risk Management Planthe SCRM plan is protected from unauthorized disclosure.AO is new for NIST 800-171A R3
A.03.17.02[01]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are developed to identify supply chain risks.AO is new for NIST 800-171A R3
A.03.17.02[02]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are developed to protect against supply chain risks.AO is new for NIST 800-171A R3
A.03.17.02[03]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are developed to mitigate supply chain risks.AO is new for NIST 800-171A R3
A.03.17.02[04]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are implemented to identify supply chain risks.AO is new for NIST 800-171A R3
A.03.17.02[05]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are implemented to protect against supply chain risks.AO is new for NIST 800-171A R3
A.03.17.02[06]Acquisition Strategies, Tools, and Methodsacquisition strategies, contract tools, and procurement methods are implemented to mitigate supply chain risks.AO is new for NIST 800-171A R3
A.03.17.03.ODP[01]Supply Chain Requirements and Processessecurity requirements to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences from supply chain-related events are defined.AO is new for NIST 800-171A R3. Elements of NFO - SA-9
A.03.17.03.a[01]Supply Chain Requirements and Processesa process for identifying weaknesses or deficiencies in the supply chain elements and processes is established.AO is new for NIST 800-171A R3
A.03.17.03.a[02]Supply Chain Requirements and Processesa process for addressing weaknesses or deficiencies in the supply chain elements and processes is established.AO is new for NIST 800-171A R3
A.03.17.03.bSupply Chain Requirements and Processesthe following security requirements are enforced to protect against supply chain risks to the system, system components, or system services and to limit the harm or consequences of supply chain-related events: <A.03.17.03.ODP[01]: security requirements>.AO is new for NIST 800-171A R3. Elements of NFO - SA-9
Practical Steps

How To Transition From R2 To R3

Every organization is unique in its business practices, technologies and resource limits, so treat this as a general roadmap for the transition from NIST 800-171 R2 to NIST 800-171 R3.

Assumptions

Since you are transitioning from established NIST 800-171 R2 practices, we assume your organization already has:

  1. Documented evidence of due diligence and due care for NIST 800-171 R2 and CMMC 2.0, including policies, standards and procedures; a System Security Plan (SSP); documented roles and responsibilities for internal and external stakeholders; and a Plan of Action & Milestones (POA&M) for any identified deficiencies.
  2. Executive sponsorship to make changes to technologies, third-party relationships and business practices.
  3. Third parties that are contractually obligated to comply with flow-down requirements (e.g., NIST 800-171 and CMMC).

Key NIST 800-171 R3 Transition Steps

Prioritize these two steps, since they cover the biggest changes between R2 and R3:

01

Governance Oversight

Earlier versions of NIST 800-171 included Non-Federal Organization (NFO) controls in Appendix E. NIST treated them as fundamentals that were reasonably expected (e.g., policies, procedures and training records), so they needed no further clarification. R3 removes the NFO controls entirely, which raises the governance requirements inside the CUI controls. That makes governance oversight the most logical first step:

  • Update policies and standards to cover every NIST 800-171 R3 requirement, down to the AO level.
  • Inventory all External Service Providers (ESP) to determine their access to CUI and in-scope systems, applications and services.
02

Supply Chain Risk Management (SCRM) Plan

Developing a SCRM plan is likely the heaviest lift in the move from R2 to R3. There are several ways to approach it, but most organizations will align with NIST SP 800-161 R1 for SCRM practices.

NIST 800-171 R3 sets basic requirements for what a SCRM plan must contain, but it will still take significant time to develop and implement.

For a phase-by-phase plan, see How To Upgrade To NIST SP 800-171 Rev 3. Our NIST 800-171 & CMMC compliance solutions give you affordable, editable documentation templates to make the move to R3 easier.

Free Resources

Free Resources For Your R3 Transition

01

NIST 800-171 R3 Kill Chain

Our NIST 800-171 R3 Kill Chain complements this guide with a phase-based model to prioritize NIST 800-171 R3 control implementation.

02

CMMC COA NIST 800-171 R3 Awesomeness Spreadsheet

The CMMC Center of Awesomeness (CMMC COA) updated its free "CMMC Awesomeness Spreadsheet" for NIST 800-171 R3 and NIST 800-171A R3. It takes a "paint by numbers" approach and includes:

  • Control to AO visibility
  • Crosswalk mapping to the SCF, NIST 800-53, NIST CSF 2.0, ISO 27002 and more
  • RASCI matrix (shared responsibility matrix)
  • Roles and responsibilities based on the NIST NICE Cybersecurity Workforce Framework
  • Cadence for control execution (e.g., daily, weekly or monthly)
  • Evidence Request List (ERL) with reasonable evidence for each AO

You can also download the existing spreadsheets for NIST 800-171 R2 and CMMC 2.0.

Common Questions

Frequently Asked Questions (FAQs)

Here are answers to common questions about the move to NIST 800-171 Rev 3:

When was NIST SP 800-171 Rev 3 released?
NIST published the final NIST SP 800-171 Rev 3 on May 14, 2024, and withdrew Rev 2 the same day. Its companion assessment publication, NIST SP 800-171A Rev 3, was also finalized in May 2024. Publication by NIST did not by itself change DoD contract requirements, and 32 CFR 170.14 still defines CMMC Level 2 using the requirements of NIST SP 800-171 Rev 2.
What is the difference between NIST 800-171 Rev 2 and Rev 3?
Rev 3 restructures the CUI security requirements to align directly with NIST SP 800-53 Rev 5 and grows from 14 to 17 families by adding Planning, System and Services Acquisition, and Supply Chain Risk Management. It also introduces organization-defined parameters and removes the separate NFO tailoring category used in Rev 2. ComplianceForge's mapping of Rev 3 shows fewer numbered requirements but far more assessment objectives, which rise from 320 to 510.
What is NIST SP 800-171A Rev 3 used for?
NIST SP 800-171A Rev 3 provides the assessment procedures and methodology used to evaluate whether the security requirements in NIST SP 800-171 Rev 3 are met. Each requirement is broken into assessment objectives, which are the specific determination statements an assessor evaluates. Because evidence is judged at the assessment objective level, a transition plan built only on requirement titles will miss work that an assessor expects to see.
What are orphaned assessment objectives in the Rev 3 transition?
Orphaned assessment objectives are Rev 2 assessment objectives that have no direct counterpart in NIST SP 800-171A Rev 3. These items still matter, because you're generally still expected to show evidence of due diligence for topics such as maintenance, roles, inventories and physical security even when Rev 3 no longer phrases them the same way. If you remove them without checking their logical dependencies, you can end up with gaps in your evidence.
Where can I download the NIST 800-171 R2 to R3 Transition Guide?
ComplianceForge offers the NIST 800-171 R2 to R3 Transition Guide as a downloadable PDF, with no purchase required. We developed it with DEFCERT, and it maps every Rev 2 assessment objective to its Rev 3 equivalent, including logical dependencies for orphaned objectives. The work is grouped into minimal, moderate and significant effort, so your team can plan resources before you start rewriting documentation.