03.01.02E — Non-Organizationally Owned Systems - Restricted Use

Official NIST requirement content

Security requirement

Restrict the use of non-organizationally owned systems or system components to process, store, or transmit CUI using [Organization-defined: restrictions].

Official NIST discussion

Discussion

Non-organizationally owned systems or system components include systems or system components owned by other organizations as well as personally owned devices. These also include systems and system components that are leased, part of subscription services, government-furnished equipment, or "bring your own" devices. There are risks to using non-organizationally owned systems or components. In some cases, the risk is sufficiently high as to prohibit such use. In other cases, the use of such systems or system components may be allowed but restricted in some way. Restrictions include requiring the implementation of approved safeguards prior to authorizing connections to non-organizationally owned systems and components; limiting access to types of information, services, or applications; using virtualization techniques to limit processing and storage activities to system components that are provisioned by the organization; and agreeing to the terms and conditions for usage. This requirement enhances SP 800-171 requirement 03.01.20

Official organization-defined parameters

Tailoring decisions required

Resolve these values through the governing organization’s approved tailoring and risk-management process before declaring the requirement implemented.

restrictionsorganization-defined restrictionsrestrictions on the use of non-organizationally owned systems or system components to process, store, or transmit CUI are defined.

Official protection strategy classifications

Protection strategies supported

These classifications are carried from the official SP 800-172 OSCAL record and help explain the enhanced requirement’s defensive purpose.

PS-DLODamage-Limiting Operations

PS-PRAPenetration-Resistant Architecture

Bare Metal Cyber interpretation

Implementation perspective

Treat Non-Organizationally Owned Systems - Restricted Use as an enhanced CUI protection outcome for elevated threat conditions that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to approved identities, least privilege, remote access, information flow, and the full account lifecycle.

Confirm the federal agency selected this enhanced requirement for the critical program or high-value asset and identify the CUI system components, services, users, and external connections in scope.
Resolve every organization-defined parameter through an approved governance and tailoring process.
Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

Which critical-program or high-value-asset CUI, data flows, users, and services are protected by this enhanced requirement?
Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
What change, incident, or threshold should trigger reassessment?

Evidence and validation

access authorization and approval records
account inventories and entitlement exports
access review results
authentication and authorization logs

Common failure patterns

CUI access that exceeds mission need
shared or orphaned accounts
remote access paths outside the approved boundary
access reviews that cannot be reconciled to deployed permissions

Official NIST SP 800-172A content

Assessment objectives and methods

Assessment objectives (1)

the use of non-organizationally owned systems or system components to process, store, or transmit CUI is restricted using [Organization-defined: restrictions].

Examine

Access control policy
procedures addressing the use of external systems
system design documentation
system configuration settings and associated documentation
system connection or processing agreements
account management documents
system audit records
other relevant documents or records

Interview

Personnel with responsibilities for restricting or prohibiting the use of non-organizationally owned systems, system components, or devices
system/network administrators
personnel with information security responsibilities

Test

Mechanisms implementing restrictions on the use of non-organizationally owned systems, components, or devices

Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-172 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlAC-20(3)Open SP 800-53 control →

Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.