home/arrivals

Arrivals from document review

Terms a reviewer proposed and accepted while tagging a document in the CKI mapping queue. Each one is a Candidate carrying its provenance and waiting on classification.

200 terms · 200 still unclassified
open-source softwarecandidateneeds classifying

No definition recorded.

re components or obtain the services of external service providers who provide ongoing support for unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated by prohibiting the connection of such components to public or uncontrolled networks or implementing other forms of isolation.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
system-level softwarecandidateneeds classifying

No definition recorded.

k administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and personnel with access to system-level software with securityrelated technical training specifically tailored for their assigned duties.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
solid-state devicecandidateneeds classifying

No definition recorded.

inserted into and removed from a system and that is used to store information or data (e.g., text, video, audio, and/or image data). Such components are typically implemented on magnetic, optical, or solid-state devices (e.g., compact/digital video disks, flash/thumb drives, external solid-state drives, external hard disk drives, flash memory cards/drives that contain nonvolatile memory).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
external solid-statecandidateneeds classifying

No definition recorded.

n or data (e.g., text, video, audio, and/or image data). Such components are typically implemented on magnetic, optical, or solid-state devices (e.g., compact/digital video disks, flash/thumb drives, external solid-state drives, external hard disk drives, flash memory cards/drives that contain nonvolatile memory).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
third-party credential usagecandidateneeds classifying

No definition recorded.

specific and ongoing auditing needs. Event types can include password changes, the execution of privileged functions, failed logons or accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the system monitoring and auditing that are appropriate for each of the security requirements. When defining event types, organizations consider the logging necessary to cover related events, such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
open-source software valuecandidateneeds classifying

No definition recorded.

re components or obtain the services of external service providers who provide ongoing support for unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated by prohibiting the connection of such components to public or uncontrolled networks or implementing other forms of isolation.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
external solid-state drivecandidateneeds classifying

No definition recorded.

n or data (e.g., text, video, audio, and/or image data). Such components are typically implemented on magnetic, optical, or solid-state devices (e.g., compact/digital video disks, flash/thumb drives, external solid-state drives, external hard disk drives, flash memory cards/drives that contain nonvolatile memory).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
solid-statecandidateneeds classifying

No definition recorded.

inserted into and removed from a system and that is used to store information or data (e.g., text, video, audio, and/or image data). Such components are typically implemented on magnetic, optical, or solid-state devices (e.g., compact/digital video disks, flash/thumb drives, external solid-state drives, external hard disk drives, flash memory cards/drives that contain nonvolatile memory).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
non-signaturecandidateneeds classifying

No definition recorded.

Malicious code protection mechanisms include signatureand non-signature-based technologies. Non-signature-based detection mechanisms include artificial intelligence techniques that use heuristics to detect, analyze, and describe the characteristics or behavior of malicious code and to provide controls against such code for which signatures do not yet exist or for which existing signatures may not be effective. Malicious code for which active signatures d
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
system-levelcandidateneeds classifying

No definition recorded.

k administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and personnel with access to system-level software with securityrelated technical training specifically tailored for their assigned duties.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
open-sourcecandidateneeds classifying

No definition recorded.

re components or obtain the services of external service providers who provide ongoing support for unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated by prohibiting the connection of such components to public or uncontrolled networks or implementing other forms of isolation.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
violation of lawcandidateneeds classifying

No definition recorded.

actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. [79]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
third-partycandidateneeds classifying

No definition recorded.

specific and ongoing auditing needs. Event types can include password changes, the execution of privileged functions, failed logons or accesses related to systems, administrative privilege usage, or third-party credential usage. In determining event types that require logging, organizations consider the system monitoring and auditing that are appropriate for each of the security requirements. When defining event types, organizations consider the logging necessary to cover related events, such as the steps in distributed, transaction-based processes (e.g., processes that are distributed across
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
user trainingcandidateneeds classifying

No definition recorded.

ndle incidents; and incident responders may receive specific training on data collection techniques, forensics, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of 03.02.02. Events that may cause an update to incident response training content include incident response plan testing, response to an actual incident, audit or assessment findings, or changes in applicable laws, Executive Orders, poli
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
user identitycandidateneeds classifying

No definition recorded.

vity. The unique identification and authentication of users apply to all system accesses. Organizations use passwords, physical authenticators, biometrics, or some combination thereof to authenticate user identities. Organizations may reauthenticate individuals in certain situations, including when roles, authenticators, or credentials change; when the execution of privileged functions occurs; after a fixed time period; or periodically.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 29, 2026open in CKI ↗
unauthorized processcandidateneeds classifying

No definition recorded.

Software or firmware intended to perform an unauthorized process that will have an adverse impact on the confidentiality, integrity, or availability of a system. Examples of malicious code include viruses, worms, Trojan horses, spyware, some forms of adware, or other code-based entities that infect a host.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
trusted sourcecandidateneeds classifying

No definition recorded.

es and procedures address the actions taken to prevent the development, acquisition, and use of unacceptable mobile code within the system, including requiring mobile code to be digitally signed by a trusted source.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
telecommunications controllercandidateneeds classifying

No definition recorded.

A system implemented with a collection of interconnected components. Such components may include routers, hubs, cabling, telecommunications controllers, key distribution centers, and technical control devices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
technology productcandidateneeds classifying

No definition recorded.

licies, standards, and guidelines. Incident information informs risk assessments, the effectiveness of security assessments, the security requirements for acquisitions, and the selection criteria for technology products. Incident response support resources provided by organizations include help desks, assistance groups, automated ticketing systems to open and track incident response tickets, and access to forensic services or consumer redress services, when required.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
federal lawcandidateneeds classifying

No definition recorded.

bility of an individual (i.e., the individual's trustworthiness) prior to authorizing access to the system or when elevating system access. The screening and rescreening activities reflect applicable federal laws, Executive Orders, directives, policies, regulations, and criteria established for the level of access required for the assigned position.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
defined eventcandidateneeds classifying

No definition recorded.

When required by system changes or following [ Assignment: organizationdefined events ], and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
types of external systemcandidateneeds classifying

No definition recorded.

facilities; systems owned or controlled by nonfederal organizations; and systems managed by contractors. Organizations have the option to prohibit the use of any type of external system or specified types of external systems (e.g., prohibit the use of external systems that are not organizationally owned). Terms and conditions are consistent with the trust relationships established with the entities that own, operate, or maintain external systems and include descriptions of shared responsibilities.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
system security plans referencecandidateneeds classifying

No definition recorded.

f the plans and the subsequent determinations of risk if the plan is implemented as intended. System security plans can be a collection of documents, including documents that already exist. Effective system security plans reference policies, procedures, and documents (e.g., design specifications) that provide additional detailed information. This reduces the documentation requirements associated with security programs and maintains security information in other established management or operational areas related to enterprise architecture, the system development life cycle, systems engineering
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
part of collaborative computing devicecandidateneeds classifying

No definition recorded.

Collaborative computing devices include white boards, microphones, and cameras. Notebook computers, smartphones, display monitors, and tablets containing cameras and microphones are considered part of collaborative computing devices when conferencing software is in use. Indication of use includes notifying users (e.g., a pop-up menu stating that recording is in progress or that the microphone has been turned on) when collaborative computing devices are activated. Dedicated video conferencing systems, which typically rely on one of the participants calling or connecting to the other part
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
execution of termination actioncandidateneeds classifying

No definition recorded.

The timely execution of termination actions is essential for individuals who have been terminated for cause. Organizations may consider disabling the accounts of individuals who are being terminated prior to the individuals being notified. This requirement applies to the reassignment or transfer of individuals when the personnel action is permanent or of such extended duration as to require protection. Prote
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
development systemcandidateneeds classifying

No definition recorded.

Organizations apply systems security engineering principles to new development systems. For legacy systems, organizations apply systems security engineering principles to system modifications to the extent feasible, given the current state of hardware, software, and firmware components. The application of systems security engineering principles helps to develop trustworthy, secure, and resilient systems and reduce the susceptibility of organizations to disruption
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
unauthorized individualcandidateneeds classifying

No definition recorded.

Authentication feedback does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For example, for desktop or notebook systems with relatively large monitors, the threat may be significant (commonly referred to as shoulder surfing). For mobile devices with small displays, this threat may be less significant and is balanced against the increased likelihood of input errors due to small keyboards. Therefore, the mea
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
identifiable ownercandidateneeds classifying

No definition recorded.

Prohibit the use of removable system media without an identifiable owner.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
current usercandidateneeds classifying

No definition recorded.

ation transfer via shared system resources stops information produced by the actions of prior users or roles (or actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations of information. In other contexts, the control of information in shared system resources is referred to as object reuse and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
single authoritycandidateneeds classifying

No definition recorded.

A domain that implements a security policy and is administered by a single authority. [78, adapted]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
related resourcecandidateneeds classifying

No definition recorded.

Information and related resources, such as personnel, equipment, funds, and information technology. [81]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
potential circumstancecandidateneeds classifying

No definition recorded.

A measure of the extent to which an entity is threatened by a potential circumstance or event, and typically is a function of: (i) the adverse impact, or magnitude of harm, that would arise if the circumstance or event occurs; and (ii) the likelihood of occurrence. [13]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
lawful authoritycandidateneeds classifying

No definition recorded.

An occurrence that actually or imminently jeopardizes, without lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. [79]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
human componentcandidateneeds classifying

No definition recorded.

Interacting digital, analog, physical, and human components engineered for function through integrated physics and logic.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
automatic acquisitioncandidateneeds classifying

No definition recorded.

Any services, equipment, or interconnected system(s) or subsystem(s) of equipment, that are used in the automatic acquisition, storage, analysis, evaluation, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the agency. For purposes of this definition, such services or equipment if used by the agency directly or is used by a contractor under a contract with the agency that requires its use; or to a significant extent, i
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
authorized restrictioncandidateneeds classifying

No definition recorded.

Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. [79]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
audiovisual formcandidateneeds classifying

No definition recorded.

Any communication or representation of knowledge such as facts, data, or opinions in any medium or form, including textual, numerical, graphic, cartographic, narrative, electronic, or audiovisual forms. [13]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
transmitted informationcandidateneeds classifying

No definition recorded.

ssion level, not at the packet level. Such protection establishes grounds for confidence at both ends of the communications sessions in the ongoing identities of other parties and the validity of the transmitted information. Authenticity protection includes protecting against adversary-in-the-middle attacks, session hijacking, and the insertion of false information into sessions.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
system usecandidateneeds classifying

No definition recorded.

System Use Notification
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
security technologycandidateneeds classifying

No definition recorded.

ch the establishment, maintenance, and provisioning of security controls are under the direct control of organizational employees or contractors or in which the cryptographic encapsulation or similar security technology implemented between organization-controlled endpoints provides the same effect (with regard to confidentiality and integrity). An internal network is typically organization-owned yet may be organizationcontrolled while not being organization-owned.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
security constraintcandidateneeds classifying

No definition recorded.

ty includes hardware authentication tokens, system administration technical manuals, keys, identification cards, and building passes. Exit interviews ensure that terminated individuals understand the security constraints imposed by being former employees and that accountability is achieved for the organizational property. Security topics at exit interviews include reminding individuals of potential limitations on future employment and non-disclosure agreements. Exit interviews may not always be possible for some individuals, including in cases related to the unavailability of supervisors, illn
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
accessible systemcandidateneeds classifying

No definition recorded.

Review the content on publicly accessible systems for CUI and remove such information, if discovered.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
accessible informationcandidateneeds classifying

No definition recorded.

Train authorized individuals to ensure that publicly accessible information does not contain CUI.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
level of interactioncandidateneeds classifying

No definition recorded.

these objectives in the future. The advanced persistent threat pursues its objectives repeatedly over an extended period; adapts to defenders' efforts to resist it; and is determined to maintain the level of interaction needed to execute its objectives. [60]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
types of cryptographycandidateneeds classifying

No definition recorded.

Implement the following types of cryptography when used to protect the confidentiality of CUI: [ Assignment: organization-defined types of cryptography ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
observation of eventcandidateneeds classifying

No definition recorded.

System monitoring involves external and internal monitoring. Internal monitoring includes the observation of events that occur within the system. External monitoring includes the observation of events that occur at the system boundary. Organizations can monitor the system by observing audit record activities in real time or by observing other system aspects, such as access patterns, characteristics of access, and other actions. The monitoring objectives may guide determination of the event
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
handling of CUIcandidateneeds classifying

No definition recorded.

includes an understanding of the need for security and the actions required of users to maintain security and respond to incidents. The content also addresses the need for operations security and the handling of CUI. Security awareness techniques include displaying posters, offering supplies inscribed with security reminders, generating email advisories or notices from organizational officials, displaying logon screen messages, and conducting awareness events using podcasts, videos, and webinars. Security literacy training is conducted at a frequency consistent with applicable laws, directives
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
disclosure of CUIcandidateneeds classifying

No definition recorded.

te access through managed access control points enhances explicit control over such connections and reduces susceptibility to unauthorized access to the system, which could result in the unauthorized disclosure of CUI.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
set of informationcandidateneeds classifying

No definition recorded.

A discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. [81]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
required security controlcandidateneeds classifying

No definition recorded.

A system or component of a system that is outside of the authorization boundary established by the organization and for which the organization typically has no direct control over the application of required security controls or the assessment of security control effectiveness.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
unsatisfied security requirementcandidateneeds classifying

No definition recorded.

Plans of action and milestones (POAMs) are important documents in organizational security programs. Organizations use POAMs to describe how unsatisfied security requirements will be met and how planned mitigations will be implemented. Organizations can document system security plans and POAMs as separate or combined documents in any format. Federal agencies may consider system security plans and POAMs as inputs to risk-based decisions on whether to process, store, or transmit CUI on a system hosted by a nonfederal organization.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
single network connectioncandidateneeds classifying

No definition recorded.

essions includes deallocating TCP/IP addresses or port pairs at the operating system level or deallocating networking assignments at the application level if multiple application sessions are using a single network connection. Time periods of inactivity may be established by organizations and include time periods by type of network access or for specific network accesses.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
proposed configuration-controlled changecandidateneeds classifying

No definition recorded.

Review proposed configuration-controlled changes to the system, and approve or disapprove such changes with explicit consideration for security impacts.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
possession of authenticatorcandidateneeds classifying

No definition recorded.

ashed or encrypted formats or files that contain hashed or encrypted passwords that are accessible with administrator privileges. Actions can be taken to protect authenticators, including maintaining possession of authenticators, not sharing authenticators with others, and immediately reporting lost, stolen, or compromised authenticators.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
new identification cardcandidateneeds classifying

No definition recorded.

manent or of such extended duration as to require protection. Protections that may be required for transfers or reassignments to other positions within organizations include returning old and issuing new identification cards, keys, and building passes; changing system access authorizations (i.e., privileges); closing system accounts and establishing new accounts; and providing access to official records to which individuals had access at previous work locations in previous system accounts.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
information security responsibilitycandidateneeds classifying

No definition recorded.

identify systems that are affected by announced software and firmware flaws, including potential vulnerabilities that result from those flaws, and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address the flaws discovered during security assessments, continuous monitoring, incident response activities, and system error handling. Organizations can take advantage of available resources (e.g., CWE or CVE databases) when remediating system flaw
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
current enterprise architecturecandidateneeds classifying

No definition recorded.

cement of components in the system architecture. Maintaining baseline configurations requires creating new baselines as the system changes over time. Baseline configurations of the system reflect the current enterprise architecture.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
contractors operating systemcandidateneeds classifying

No definition recorded.

impacts to organizational operations and assets based on the operation and use of the system and the unauthorized disclosure of CUI. Risk assessments also consider risks from external parties (e.g., contractors operating systems on behalf of the organization, service providers, individuals accessing systems, and outsourcing entities). Risk assessments can be conducted at the organization level, the mission or business process level, or the system level and at any phase in the system development life cycle. Risk assessments include supply chain-related risks associated with suppliers or contra
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
compromised system accountcandidateneeds classifying

No definition recorded.

The misuse of privileged functions - whether intentionally or unintentionally by authorized users or by unauthorized external entities that have compromised system accounts - is a serious and ongoing concern that can have significant adverse impacts on organizations. Logging the use of privileged functions is one way to detect such misuse and mitigate risks from advanced persistent threats and insider threats.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
collected audit informationcandidateneeds classifying

No definition recorded.

Audit records are generated in 03.03.03. Audit record reduction and report generation occur after audit record generation. Audit record reduction is a process that manipulates collected audit information and organizes it in a summary format that is more meaningful to analysts. Audit record reduction and report generation capabilities do not always come from the same system or organizational entities that conduct auditing activities. An audit record reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalo
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
violation of organizational policycandidateneeds classifying

No definition recorded.

The accounts are in violation of organizational policy, or
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
use of security attributecandidateneeds classifying

No definition recorded.

System media include digital and non-digital media. Marking refers to the use or application of human-readable security attributes. Labeling refers to the use of security attributes for internal system data structures. Digital media include diskettes, magnetic tapes, external or removable solid state or magnetic drives, flash drives, compact discs, and digital versatile discs. Non-digital media include paper and microfilm. CUI is defined by NARA along with marking, safeguarding, and dissemination requirements for such information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
use of non-privileged accountcandidateneeds classifying

No definition recorded.

r. Restricting privileged accounts to specific personnel or roles ensures that only those authorized users can access and manipulate security functions or security-relevant information. Requiring the use of non-privileged accounts when such access is not needed can limit unauthorized access to and manipulation of security functions or security-relevant information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
use of maintenance toolcandidateneeds classifying

No definition recorded.

er information security logging performed by organizations and can include logging that results from the monitoring of account usage, remote access, wireless connectivity, configuration settings, the use of maintenance tools and nonlocal maintenance, system component inventory, mobile device connection, equipment delivery and removal, physical access, temperature and humidity, communications at system interfaces, and the use of mobile code. Findings can be reported to organizational entities, such as the incident response team, help desk, and security or privacy offices. If organizations are p
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
types of system monitoringcandidateneeds classifying

No definition recorded.

orized export of information, or signaling to external systems. Evidence of malicious code is used to identify a potentially compromised system. System monitoring requirements, including the need for types of system monitoring, may be referenced in other requirements.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
types of audit logcandidateneeds classifying

No definition recorded.

s, and card readers. Physical access control systems comply with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidelines. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural, automated, or some combination thereof. Physical access points can include exterior access points, interior access points to systems that require supplemental access controls, or both. Physical access control applies to employees and visitors. Individuals with permanent physical access authorizations are not considered visitors.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
type of access agreementcandidateneeds classifying

No definition recorded.

Rules of behavior represent a type of access agreement for system users. Organizations consider rules of behavior for the handling of CUI based on individual user roles and responsibilities and differentiate between rules that apply to privileged users and rules that apply to general users.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
thefact investigations of incidentcandidateneeds classifying

No definition recorded.

Implement an audit record reduction and report generation capability that supports audit record review, analysis, reporting requirements, and after-thefact investigations of incidents.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
selection of cryptographic mechanismcandidateneeds classifying

No definition recorded.

The selection of cryptographic mechanisms is based on the need to protect the confidentiality of backup information. Hardware security module (HSM) devices safeguard and manage cryptographic keys and provide cryptographic processing. Cryptographic operations (e.g., encryption, decryption, and signature generation and verification) are typically hosted on the HSM device, and many implementations provid
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
risk of malevolent activitycandidateneeds classifying

No definition recorded.

Separation of duties addresses the potential for abuse of authorized privileges and reduces the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and support functions among different individuals or roles, conducting system support functions with different individuals or roles (e.g., quality assurance, configuration management, network security, system management, assessments, and programming), and ensuring that personnel who administer a
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
protection of classified informationcandidateneeds classifying

No definition recorded.

Cryptography that consists of an approved algorithm, an implementation that has been approved for the protection of classified information and/or controlled unclassified information in a specific environment, and a supporting key management infrastructure. [8]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
part of device authenticationcandidateneeds classifying

No definition recorded.

, Kerberos) to identify and authenticate devices on local and wide area networks. Public Key Infrastructure (PKI) and certificate revocation checking for the certificates exchanged can be included as part of device authentication.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
operation of security functioncandidateneeds classifying

No definition recorded.

the control, monitoring, or administration of the system, including security functions and security-relevant information. Security-relevant information is information that can potentially impact the operation of security functions or the provision of security services in a manner that could result in failure to enforce the system security policy or maintain isolation of code and data. Privileged commands give individuals the ability to execute sensitive, security-critical, or security-relevant system functions.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
notification of organizational personnelcandidateneeds classifying

No definition recorded.

dination among mission and business owners, system administrators, human resource managers, and legal staff is essential when disabling system accounts for high-risk individuals. Time periods for the notification of organizational personnel or roles may vary.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
insider threat awareness topiccandidateneeds classifying

No definition recorded.

t or bullying of fellow employees; workplace violence; and other serious violations of the policies, procedures, rules, directives, or practices of organizations. Organizations may consider tailoring insider threat awareness topics to roles (e.g., training for managers may be focused on specific changes in the behavior of team members, while training for employees may be focused on more general observations).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
examples of media inspectioncandidateneeds classifying

No definition recorded.

nnel on media, cloud-based, or downloaded from a website. Diagnostic and test programs are potential vehicles for transporting malicious code into the system, either intentionally or unintentionally. Examples of media inspection include checking the cryptographic hash or digital signatures of diagnostic and test programs and media.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
descriptions of shared responsibilitycandidateneeds classifying

No definition recorded.

ystems that are not organizationally owned). Terms and conditions are consistent with the trust relationships established with the entities that own, operate, or maintain external systems and include descriptions of shared responsibilities.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
applicable access control policycandidateneeds classifying

No definition recorded.

Enforce approved authorizations for logical access to CUI and system resources in accordance with applicable access control policies.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
actions of prior usercandidateneeds classifying

No definition recorded.

Preventing unauthorized and unintended information transfer via shared system resources stops information produced by the actions of prior users or roles (or actions of processes acting on behalf of prior users or roles) from being available to current users or roles (or current processes acting on behalf of current users or roles) that obtain access to shared system resources after those resources have been released back to the system. Information in shared system resources also applies to encrypted representations
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
abuse of authorized privilegecandidateneeds classifying

No definition recorded.

Separation of duties addresses the potential for abuse of authorized privileges and reduces the risk of malevolent activity without collusion. Separation of duties includes dividing mission functions and support functions among different individuals or roles, conducting system support functions with different individuals or roles (e.g., quality assurance, configuration management, network security, system management, assessments, and programming
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
transmission capabilities of mobile devicecandidateneeds classifying

No definition recorded.

nchronizing local data with remote locations. Examples include smart phones, smart watches, and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capabilities of mobile devices may be comparable to or a subset of notebook or desktop systems, depending on the nature and intended purpose of the device. Some organizations may consider notebook computers to be mobile devices. The protection and control of mobile devices are behavioror policy-based and require users to take physical action to protect and control such devices when ou
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
potential indicators of insider threatcandidateneeds classifying

No definition recorded.

s an attempt to gather information about the organization that may be used to support future attacks. Security literacy training includes how to communicate employee and management concerns regarding potential indicators of insider threat and potential and actual instances of social engineering and data mining through appropriate organizational channels in accordance with established policies and procedures.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
examples of physical access monitoringcandidateneeds classifying

No definition recorded.

r more physical locations containing systems or system components that process, store, or transmit CUI. Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
effectiveness of incident response processcandidateneeds classifying

No definition recorded.

testing can include a determination of the effects of incident response on organizational operations, organizational assets, and individuals. Qualitative and quantitative data can help determine the effectiveness of incident response processes.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
effective accountability of system componentcandidateneeds classifying

No definition recorded.

components from all systems. In such situations, organizations ensure that the inventories include the system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
system-specific informationcandidateneeds classifying

No definition recorded.

centralized system component inventories that include components from all systems. In such situations, organizations ensure that the inventories include the system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
resilient systemcandidateneeds classifying

No definition recorded.

ns to the extent feasible, given the current state of hardware, software, and firmware components. The application of systems security engineering principles helps to develop trustworthy, secure, and resilient systems and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples include developing layered protections; establishing security policies, architectures, and controls as the foundation for system design; incorporating security requirements into the system development life cycle; delineating physical and logical security boundaries; ensuring that develop
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
owned systemcandidateneeds classifying

No definition recorded.

External systems are systems that are used by but are not part of the organization. These systems include personally owned systems, system components, or devices; privately owned computing and communication devices in commercial or public facilities; systems owned or controlled by nonfederal organizations; and systems managed by contractors. Organizations have the option to prohibit the use of any type of external system or specified types of external systems (e.g., prohibit the use of external systems that are
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
federal informationcandidateneeds classifying

No definition recorded.

Federal Information Processing Standards
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
modification of informationcandidateneeds classifying

No definition recorded.

the potential to adversely impact organizational operations, organizational assets, individuals, other organizations, or the Nation through a system via unauthorized access, destruction, disclosure, modification of information, and/or denial of service. [55]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
groups of data fieldcandidateneeds classifying

No definition recorded.

ved (e.g., forms, reports, test results) that serve as a basis for verifying that the organization and the system are performing as intended. Also used to refer to units of related data fields (i.e., groups of data fields that can be accessed by a program and that contain a complete set of information on particular items).
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
system levelcandidateneeds classifying

No definition recorded.

ss to the system when users depart from the immediate vicinity of the system but do not want to log out due to the temporary nature of their absences. Device locks can be implemented at the operating system level or application level. User-initiated device locking is behavioror policy-based and requires users to take physical action to initiate the device lock. Device locks are not an acceptable substitute for logging out of the system (e.g., when organizations require users to log out at the end of workdays). Publicly viewable images can include static or dynamic images, such as patterns used
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
types of agreementcandidateneeds classifying

No definition recorded.

e): interconnection security agreements; information exchange security agreements; memoranda of understanding or agreement; service-level agreements; user agreements; non-disclosure agreements; other types of agreements ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
organization-defined eventcandidateneeds classifying

No definition recorded.

Update security literacy training content [ Assignment: organization-defined frequency ] and following [ Assignment: organization-defined events ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
removable solid statecandidateneeds classifying

No definition recorded.

System media include digital and non-digital media. Digital media include diskettes, flash drives, magnetic tapes, external or removable solid state or magnetic drives, compact discs, and digital versatile discs. Non-digital media include paper and microfilm. Physically controlling stored media includes conducting inventories, establishing procedures to allow individuals to check out and return media to libraries, and maintaining accountability for stored media. Secure storage includes a locked drawer, desk, or cabinet or
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
use of mobile codecandidateneeds classifying

No definition recorded.

and nonlocal maintenance, system component inventory, mobile device connection, equipment delivery and removal, physical access, temperature and humidity, communications at system interfaces, and the use of mobile code. Findings can be reported to organizational entities, such as the incident response team, help desk, and security or privacy offices. If organizations are prohibited from reviewing and analyzing audit records or unable to conduct such activities, the review or analysis may be carried out by other organizations granted such authority. The scope, frequency, and/or depth of the aud
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
removable data storagecandidateneeds classifying

No definition recorded.

bile device is a computing device with a small form factor such that it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable, or removable data storage; and includes a selfcontained power source. Mobile device functionality may include on-board sensors that allow the device to capture information, voice communication capabilities, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, smart watches, and tablets. Mobile devices are typically associated with a single indivi
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
protection of CUIcandidateneeds classifying

No definition recorded.

Cryptography is implemented in accordance with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidelines. FIPS-validated cryptography is recommended for the protection of CUI.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
policy enforcement methodcandidateneeds classifying

No definition recorded.

e and downloading new applications from organization-approved 'app stores.' The policies selected for governing user-installed software are organization-developed or provided by some external entity. Policy enforcement methods can include procedural methods and automated methods.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
video surveillance equipmentcandidateneeds classifying

No definition recorded.

components that process, store, or transmit CUI. Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of physical security incidents and responses to those inci
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
planned remediation actioncandidateneeds classifying

No definition recorded.

To document the planned remediation actions to correct weaknesses or deficiencies noted during security assessments and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
subscription servicecandidateneeds classifying

No definition recorded.

nd the Federal Bureau of Investigation (FBI) generate security alerts and advisories to maintain situational awareness across the Federal Government and in nonfederal organizations. Software vendors, subscription services, and industry Information Sharing and Analysis Centers (ISACs) may also provide security alerts and advisories. Compliance with security directives is essential due to the critical nature of many of these directives and the potential immediate adverse effects on organizational operations and assets, individuals, other organizations, and the Nation should the directives not be
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
sensor devicecandidateneeds classifying

No definition recorded.

hysical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of physical security incidents and responses to those incidents. Incidents include security violations or su
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
professional servicecandidateneeds classifying

No definition recorded.

pheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including cloud computing and help-desk services or other professional services which support any point of the life cycle of the equipment or service), and related resources. Information technology does not include any equipment that is acquired by a contractor incidental to a contract which does not require its use. [13]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
policy enforcementcandidateneeds classifying

No definition recorded.

ith different security policies introduces the risk that such transfers violate one or more domain security policies. In such situations, information owners or stewards provide guidance at designated policy enforcement points between interconnected systems. Organizations consider mandating specific architectural solutions when required to enforce specific security policies. Enforcement includes prohibiting CUI transfers between interconnected systems (i.e., allowing information access only), employing hardware mechanisms to enforce one-way information flows, and implementing trustworthy regrad
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
stability of individualcandidateneeds classifying

No definition recorded.

The discipline of assessing the conduct, integrity, judgment, loyalty, reliability, and stability of individuals for duties and responsibilities requiring trustworthiness. [8]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
critical software patchcandidateneeds classifying

No definition recorded.

Support for system components includes software patches, firmware updates, replacement parts, and maintenance contracts. An example of unsupported components includes when vendors no longer provide critical software patches or product updates, which can result in opportunities for adversaries to exploit weaknesses or deficiencies in the installed components. Exceptions to replacing unsupported system components include systems that provide critical mission or business capabilities when newer technologies are unavailable or when the systems are so isolated that installing replacement componen
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
software version numbercandidateneeds classifying

No definition recorded.

s include the system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, model, serial number, and supplier information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
unsuccessful logon attemptcandidateneeds classifying

No definition recorded.

Unsuccessful Logon Attempts
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
software versioncandidateneeds classifying

No definition recorded.

s include the system-specific information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, model, serial number, and supplier information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
readonly memorycandidateneeds classifying

No definition recorded.

Computer programs and data stored in hardware - typically in read-only memory (ROM) or programmable readonly memory (PROM) - such that the programs and data cannot be dynamically written or modified during execution of the programs. See hardware and software . [78]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
surveillance equipmentcandidateneeds classifying

No definition recorded.

ents that process, store, or transmit CUI. Physical access monitoring includes publicly accessible areas within organizational facilities. Examples of physical access monitoring include guards, video surveillance equipment (i.e., cameras), and sensor devices. Reviewing physical access logs can help to identify suspicious activities, anomalous events, or potential threats. The reviews can be supported by audit logging controls if the access logs are part of an automated system. Incident response capabilities include investigations of physical security incidents and responses to those incidents.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
serial numbercandidateneeds classifying

No definition recorded.

e machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, model, serial number, and supplier information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
remediation actioncandidateneeds classifying

No definition recorded.

To document the planned remediation actions to correct weaknesses or deficiencies noted during security assessments and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
personal privacycandidateneeds classifying

No definition recorded.

Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. [79]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
peripheral equipmentcandidateneeds classifying

No definition recorded.

he furnishing of a product. Information technology includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including cloud computing and help-desk services or other professional services which support any point of the life cycle of the equipment or service), and related resources. Information technology does not include any equipment that is acquired by a con
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
patch levelcandidateneeds classifying

No definition recorded.

. Organizations can use these approaches in source code reviews and tools (e.g., static analysis tools, web-based application scanners, binary analyzers). Vulnerability scanning includes scanning for patch levels; scanning for functions, ports, protocols, and services that should not be accessible to users or devices; and scanning for improperly configured or incorrectly operating flow control mechanisms.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
organizational structurecandidateneeds classifying

No definition recorded.

An entity of any size, complexity, or positioning within an organizational structure. [7, adapted]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
protection mechanismcandidateneeds classifying

No definition recorded.

ptographic key management activities. Non-privileged users do not possess the authorizations to execute privileged functions. Bypassing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from nonprivileged users. This requirement represents a condition achieved by the definition of authorized privileges in 03.01.01 and privilege enforcement in 03.01.02.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
technical control devicecandidateneeds classifying

No definition recorded.

A system implemented with a collection of interconnected components. Such components may include routers, hubs, cabling, telecommunications controllers, key distribution centers, and technical control devices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
programmable readonly memorycandidateneeds classifying

No definition recorded.

Computer programs and data stored in hardware - typically in read-only memory (ROM) or programmable readonly memory (PROM) - such that the programs and data cannot be dynamically written or modified during execution of the programs. See hardware and software . [78]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
selfcontained power sourcecandidateneeds classifying

No definition recorded.

a small form factor such that it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable, or removable data storage; and includes a selfcontained power source. Mobile device functionality may include on-board sensors that allow the device to capture information, voice communication capabilities, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, smart watches, and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and tran
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
serious adverse effectcandidateneeds classifying

No definition recorded.

The loss of confidentiality, integrity, or availability could be expected to have: (i) a limited adverse effect (FIPS Publication 199 low); (ii) a serious adverse effect (FIPS Publication 199 moderate); or (iii) a severe or catastrophic adverse effect (FIPS Publication 199 high) on organizational operations, organizational assets, or individuals. [6]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
physical devicecandidateneeds classifying

No definition recorded.

Physical devices or writing surfaces including, but not limited to, magnetic tapes, optical disks, magnetic disks, Large-Scale Integration (LSI) memory chips, and printouts (but not including display media) onto which information is recorded, stored, or printed within a system. [7]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 23, 2026open in CKI ↗
interconnected componentcandidateneeds classifying

No definition recorded.

A system implemented with a collection of interconnected components. Such components may include routers, hubs, cabling, telecommunications controllers, key distribution centers, and technical control devices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
handling capabilitycandidateneeds classifying

No definition recorded.

Implement an incident-handling capability that is consistent with the incident response plan and includes preparation, detection and analysis, containment, eradication, and recovery.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
wide situational awarenesscandidateneeds classifying

No definition recorded.

Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
transmitted authenticationcandidateneeds classifying

No definition recorded.

Protection against the capture of transmitted authentication or access control information and its subsequent retransmission with the intent of producing an unauthorized effect or gaining unauthorized access.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
suspected incidentcandidateneeds classifying

No definition recorded.

Report suspected incidents to the organizational incident response capability within [ Assignment: organization-defined time period ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
sources of system security alertcandidateneeds classifying

No definition recorded.

There are many publicly available sources of system security alerts and advisories. The Department of Homeland Security's Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), and the Federal Bureau of Investigation (FBI) generate security alerts and advisories to maintain situational awareness across the Federal Government and in nonfederal organizations. Software vendors, subscription servi
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
sanitization extraordinary meancandidateneeds classifying

No definition recorded.

Actions taken to render data written on media unrecoverable by ordinary and - for some forms of sanitization extraordinary means. A process to remove information from media such that data recovery is not possible, including the removal of all classified labels, markings, and activity logs.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
investigations of incidentcandidateneeds classifying

No definition recorded.

Implement an audit record reduction and report generation capability that supports audit record review, analysis, reporting requirements, and after-thefact investigations of incidents.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
determinations of riskcandidateneeds classifying

No definition recorded.

information are protected. System security plans contain sufficient information to enable a design and implementation that are unambiguously compliant with the intent of the plans and the subsequent determinations of risk if the plan is implemented as intended. System security plans can be a collection of documents, including documents that already exist. Effective system security plans reference policies, procedures, and documents (e.g., design specifications) that provide additional detailed information. This reduces the documentation requirements associated with security programs and maint
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
software patchcandidateneeds classifying

No definition recorded.

Support for system components includes software patches, firmware updates, replacement parts, and maintenance contracts. An example of unsupported components includes when vendors no longer provide critical software patches or product updates, which can result in opportunities for adversaries to exploit weaknesses or deficiencies in the installed components. Exceptions to replacing unsupported system components include systems that pro
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
shared responsibilitycandidateneeds classifying

No definition recorded.

not organizationally owned). Terms and conditions are consistent with the trust relationships established with the entities that own, operate, or maintain external systems and include descriptions of shared responsibilities.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
remote connectioncandidateneeds classifying

No definition recorded.

isfy other security requirements. Security parameters include registry settings; account, file, and directory permission settings (i.e., privileges); and settings for functions, ports, protocols, and remote connections. Organizations establish organization-wide configuration settings and subsequently derive specific configuration settings for the system. The established settings become part of the system's configuration baseline.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
power sourcecandidateneeds classifying

No definition recorded.

actor such that it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable, or removable data storage; and includes a selfcontained power source. Mobile device functionality may include on-board sensors that allow the device to capture information, voice communication capabilities, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, smart watches, and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capab
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organizationdefined eventcandidateneeds classifying

No definition recorded.

When required by system changes or following [ Assignment: organizationdefined events ], and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
information technology platformcandidateneeds classifying

No definition recorded.

guides, security reference guides, and security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those system components to meet operational requirements. Common secure configurations can be developed by a variety of organizations, including information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
identities of group account usercandidateneeds classifying

No definition recorded.

he security state of the system after the event occurred). Detailed information that organizations consider in audit records may include a full text recording of privileged commands or the individual identities of group account users.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
contractual relationshipcandidateneeds classifying

No definition recorded.

in-house support by developing customized patches for critical software components or obtain the services of external service providers who provide ongoing support for unsupported components through contractual relationships. Such contractual relationships can include open-source software value-added vendors. The increased risk of using unsupported system components can be mitigated by prohibiting the connection of such components to public or uncontrolled networks or implementing other forms of isolation.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
considered visitorcandidateneeds classifying

No definition recorded.

or system components that process, store, or transmit CUI. Physical access authorizations apply to employees and visitors. Individuals with permanent physical access authorization credentials are not considered visitors. Authorization credentials include identification badges, identification cards, and smart cards. Organizations determine the strength of the authorization credentials consistent with applicable laws, Executive Orders, directives, regulations, policies, standards, and guidelines. Physical access authorizations may not be necessary to access certain areas within facilities that a
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
audit monitoringcandidateneeds classifying

No definition recorded.

Incident-related information can be obtained from a variety of sources, including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. An effective incident handling capability involves coordination among many organizational entities, including mission and business owners, system owners, human resources offices, physical and personnel security offices, legal departments, operations personnel, and pro
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
operations personnelcandidateneeds classifying

No definition recorded.

ty involves coordination among many organizational entities, including mission and business owners, system owners, human resources offices, physical and personnel security offices, legal departments, operations personnel, and procurement offices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
integrated physiccandidateneeds classifying

No definition recorded.

Interacting digital, analog, physical, and human components engineered for function through integrated physics and logic.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
independent verificationcandidateneeds classifying

No definition recorded.

ware developers, systems integrators, acquisition/procurement officials, system and network administrators, personnel conducting configuration management and auditing activities, personnel performing independent verification and validation, security assessors, and personnel with access to system-level software with securityrelated technical training specifically tailored for their assigned duties.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
high-risk locationcandidateneeds classifying

No definition recorded.

Issue systems or system components with the following configurations to individuals traveling to high-risk locations: [ Assignment: organization-defined system configurations ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
anomalous behaviorcandidateneeds classifying

No definition recorded.

system or organizational entities that conduct auditing activities. An audit record reduction capability can include, for example, modern data mining techniques with advanced data filters to identify anomalous behavior in audit records. The report generation capability provided by the system can help generate customizable reports. The time ordering of audit records can be a significant issue if the granularity of the time stamp in the record is insufficient.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
threat actioncandidateneeds classifying

No definition recorded.

Dependence on the products, systems, and services of external providers and the nature of the relationships with those providers present an increasing level of risk to an organization. Threat actions that may increase security risks include unauthorized production, the insertion or use of counterfeits, tampering, poor manufacturing and development practices in the supply chain, theft, and the insertion of malicious software, firmware, and hardware. Supply chain risks can be endemic or systemic within a system, component, or service. Managing supply chain risks is a complex, mult
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
system recoverycandidateneeds classifying

No definition recorded.

m to call; system administrators may require additional training on how to handle incidents; and incident responders may receive specific training on data collection techniques, forensics, reporting, system recovery, and system restoration. Incident response training includes user training in identifying and reporting suspicious activities from external and internal sources. Incident response training for users may be provided as part of 03.02.02. Events that may cause an update to incident response training content include incident response plan testing, response to an actual incident, audit
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
system modificationcandidateneeds classifying

No definition recorded.

Organizations apply systems security engineering principles to new development systems. For legacy systems, organizations apply systems security engineering principles to system modifications to the extent feasible, given the current state of hardware, software, and firmware components. The application of systems security engineering principles helps to develop trustworthy, secure, and resilient systems and reduce the susceptibility of organizations to disruptions, hazards, and threats. Examples include developing layered protections; establishing security policies
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security procedurecandidateneeds classifying

No definition recorded.

ithout lawful authority, the confidentiality, integrity, or availability of information or an information system; or constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. [79]
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security noticecandidateneeds classifying

No definition recorded.

Display a system use notification message with privacy and security notices consistent with applicable CUI rules before granting access to the system.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security informationcandidateneeds classifying

No definition recorded.

Require that users (or roles) with privileged accounts use non-privileged accounts when accessing non-security functions or non-security information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security capabilitycandidateneeds classifying

No definition recorded.

ference clocks (e.g., clocks synchronizing within hundreds or tens of milliseconds). Organizations may define different time granularities for system components. Time service can be critical to other security capabilities (e.g., access control and identification and authentication), depending on the nature of the mechanisms used to support those capabilities.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
relevant informationcandidateneeds classifying

No definition recorded.

Authorize access to [ Assignment: organization-defined security functions ] and [ Assignment: organization-defined security-relevant information ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
process identifiercandidateneeds classifying

No definition recorded.

Audit record content that may be necessary to support the auditing function includes time stamps, source and destination addresses, user or process identifiers, event descriptions, file names, and the access control or flow control rules that are invoked. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the system after the event occurred). Detailed information that organizations consider in audit records may include a full text recording of privileged commands o
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organization levelcandidateneeds classifying

No definition recorded.

ernal parties (e.g., contractors operating systems on behalf of the organization, service providers, individuals accessing systems, and outsourcing entities). Risk assessments can be conducted at the organization level, the mission or business process level, or the system level and at any phase in the system development life cycle. Risk assessments include supply chain-related risks associated with suppliers or contractors and the system, system component, or system service that they provide.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
notebook systemcandidateneeds classifying

No definition recorded.

Authentication feedback does not provide information that would allow unauthorized individuals to compromise authentication mechanisms. For example, for desktop or notebook systems with relatively large monitors, the threat may be significant (commonly referred to as shoulder surfing). For mobile devices with small displays, this threat may be less significant and is balanced against the increased likelihood of input errors due to small keyboards. Therefore, the means of obscuring authenticator feedback is selected accordingly. Obscuring feedback includes di
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
network appliancecandidateneeds classifying

No definition recorded.

s (e.g., servers, workstations), input and output devices (e.g., scanners, copiers, printers), network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors), operating systems, middleware, and applications.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
individual authenticatorcandidateneeds classifying

No definition recorded.

The requirement to protect individual authenticators may be implemented by 03.15.03 for authenticators in the possession of individuals and by 03.01.01, 03.01.02, 03.01.05, and 03.13.08 for authenticators stored in organizational systems. This includes passwords stored in hashed or encrypted formats or files that contain hashed or encrypted passwords that are accessible with administrator privileges. Actions can be taken to
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
incident-related informationcandidateneeds classifying

No definition recorded.

Incident-related information can be obtained from a variety of sources, including audit monitoring, network monitoring, physical access monitoring, user and administrator reports, and reported supply chain events. An effective incident handling capability involves coordination among many organizational entities, including mission and business owners, system owners, human resources offices, physica
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
firmware flawcandidateneeds classifying

No definition recorded.

Organizations identify systems that are affected by announced software and firmware flaws, including potential vulnerabilities that result from those flaws, and report this information to designated personnel with information security responsibilities. Security-relevant updates include patches, service packs, hot fixes, and anti-virus signatures. Organizations address the flaws discovered during security assessments, continuous monitoring, incident response activities, a
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
firmware elementcandidateneeds classifying

No definition recorded.

System components are discrete, identifiable assets (i.e., hardware, software, and firmware elements) that compose a system. Organizations may implement
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
agreement informationcandidateneeds classifying

No definition recorded.

Organizations may incorporate agreement information into formal contracts, especially for information exchanges established between federal agencies and nonfederal organizations (e.g., service providers, contractors, system developers, and system integrators). The types of information contained in exchange agreements include the interface characteristics, security requirements, controls, and responsibilities for each system.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security impactcandidateneeds classifying

No definition recorded.

Review proposed configuration-controlled changes to the system, and approve or disapprove such changes with explicit consideration for security impacts.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
united statecandidateneeds classifying

No definition recorded.

With respect to security, the effect on organizational operations, organizational assets, individuals, other organizations, or the Nation (including the national security interests of the United States) of a loss of confidentiality, integrity, or availability of information or a system. With respect to privacy, the adverse effects that individuals could experience when an information system processes their PII.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
smart phonecandidateneeds classifying

No definition recorded.

devices to protect wireless access to the system. Special attention is given to the variety of devices with potential wireless access to the system, including small form factor mobile devices (e.g., smart phones, tablets, smart watches). Wireless networking capabilities that are embedded within system components represent a potential vulnerability that can be exploited by adversaries. Strong authentication of users and devices, strong encryption, and disabling wireless capabilities that are not needed for essential mission or business functions can reduce susceptibility to threats by adversar
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
maintenance activitycandidateneeds classifying

No definition recorded.

Designate organizational personnel with required access authorizations and technical competence to supervise the maintenance activities of personnel who do not possess the required access authorizations.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
magnetic drivecandidateneeds classifying

No definition recorded.

System media include digital and non-digital media. Digital media include diskettes, flash drives, magnetic tapes, external or removable solid state or magnetic drives, compact discs, and digital versatile discs. Non-digital media include paper and microfilm. Physically controlling stored media includes conducting inventories, establishing procedures to allow individuals to check out and return media to libraries, and maintaining accountability for stored media. Secure storage includes a locked drawer, desk, or cabinet or a controlled media libra
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
established configuration settingcandidateneeds classifying

No definition recorded.

Identify, document, and approve any deviations from established configuration settings.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
defined configuration settingcandidateneeds classifying

No definition recorded.

Establish, document, and implement the following configuration settings for the system that reflect the most restrictive mode consistent with operational requirements: [ Assignment: organization-defined configuration settings ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
date of receiptcandidateneeds classifying

No definition recorded.

cations, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, model, serial number, and supplier information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
transmission of CUIcandidateneeds classifying

No definition recorded.

Assess the risk (including supply chain risk) of unauthorized disclosure resulting from the processing, storage, or transmission of CUI.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
status of individualcandidateneeds classifying

No definition recorded.

Characteristics that identify the status of individuals include contractors, foreign nationals, and non-organizational users. Identifying the status of individuals by these characteristics provides information about the people with whom organizational personnel are communicating. For example, it is useful for an employee to know that one of the individuals on an email message is a contractor.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
set of parametercandidateneeds classifying

No definition recorded.

Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the system and that affect the security posture or functionality of the system. Security-related configuration settings can be defined for systems (e.g., servers, workstations), input and output devices (e.g., scanners, copiers, printers), network components (e.g., firewalls, routers, gateways, voice and data sw
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
integrity of information technologycandidateneeds classifying

No definition recorded.

A collection of activities focused on establishing and maintaining the integrity of information technology products and systems through the control of processes for initializing, changing, and monitoring the configurations of those products and systems throughout the system development life cycle.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
information technology productcandidateneeds classifying

No definition recorded.

A collection of activities focused on establishing and maintaining the integrity of information technology products and systems through the control of processes for initializing, changing, and monitoring the configurations of those products and systems throughout the system development life cycle.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
collection of interconnected componentcandidateneeds classifying

No definition recorded.

A system implemented with a collection of interconnected components. Such components may include routers, hubs, cabling, telecommunications controllers, key distribution centers, and technical control devices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
manual procedurecandidateneeds classifying

No definition recorded.

Cryptographic keys can be established and managed using either manual procedures or automated mechanisms supported by manual procedures. Organizations satisfy key establishment and management requirements in accordance with applicable federal laws, Executive Orders, policies, directives, regulations, and standards that specify appropriate options, levels, and parameters. This requirement is related to 03.13.11.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
valid access authorizationcandidateneeds classifying

No definition recorded.

A valid access authorization and
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
store system mediacandidateneeds classifying

No definition recorded.

Physically control and securely store system media that contain CUI.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
specification of securitycandidateneeds classifying

No definition recorded.

A specification of security or privacy controls, control enhancements, supplemental guidance, and other supporting information employed during the tailoring process, that is intended to complement (and further refine) security control baselines. The overlay specification may be more stringent or less stringent than the original security control baseline specification and can be applied to multiple i
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
software license informationcandidateneeds classifying

No definition recorded.

fic information required for component accountability. The information necessary for effective accountability of system components includes the system name, software owners, software version numbers, software license information, hardware inventory specifications, and - for networked components - the machine names and network addresses for all implemented protocols (e.g., IPv4, IPv6). Inventory specifications include component type, physical location, date of receipt, manufacturer, cost, model, serial number, and supplier information.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
software integrity checkcandidateneeds classifying

No definition recorded.

datory protective software, scanning devices for malicious code, updating virus protection software, scanning for critical software updates and patches, conducting operating system and possibly other software integrity checks, and disabling unnecessary hardware. On mobile devices, secure containers provide software-based data isolation designed to segment enterprise applications and information from personal apps and data. Containers may present multiple user interfaces, one of the most common being a mobile application that acts as a portal to a suite of business productivity apps, such as em
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
security requirement compliancecandidateneeds classifying

No definition recorded.

Implement processes, methods, and techniques to monitor security requirement compliance by external service providers on an ongoing basis.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
professional security staffcandidateneeds classifying

No definition recorded.

This requirement addresses physical locations containing systems or system components that process, store, or transmit CUI. Organizations determine the types of guards needed, including professional security staff or administrative staff. Physical access devices include keys, locks, combinations, biometric readers, and card readers. Physical access control systems comply with applicable laws, Executive Orders, directives, policies, regulations, standards, and guidelines. Organizations have flexibility in the types of audit logs employed. Audit logs can be procedural, automated, o
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
previous authentication messagecandidateneeds classifying

No definition recorded.

Authentication processes resist replay attacks if it is impractical to successfully authenticate by recording or replaying previous authentication messages. Replayresistant techniques include protocols that use nonces or challenges, such as time synchronous or challenge-response one-time authenticators.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
personnel security officecandidateneeds classifying

No definition recorded.

events. An effective incident handling capability involves coordination among many organizational entities, including mission and business owners, system owners, human resources offices, physical and personnel security offices, legal departments, operations personnel, and procurement offices.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organizationdefined security requirementcandidateneeds classifying

No definition recorded.

security 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: [ Assignment: organizationdefined security requirements ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organizational security programcandidateneeds classifying

No definition recorded.

Plans of action and milestones (POAMs) are important documents in organizational security programs. Organizations use POAMs to describe how unsatisfied security requirements will be met and how planned mitigations will be implemented. Organizations can document system security plans and POAMs as separate or combined documents in any format. Federal agencies may consider system security plans and POAMs as inputs to risk-based decisions on whether to process, stor
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organizational monitoring objectivecandidateneeds classifying

No definition recorded.

r locations and near server farms that support critical applications with such devices being employed at managed system interfaces. The granularity of monitoring the information collected is based on organizational monitoring objectives and the capability of the system to support such objectives.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organization-wide situational awarenesscandidateneeds classifying

No definition recorded.

Analyze and correlate audit records across different repositories to gain organization-wide situational awareness.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
organization-defined response timecandidateneeds classifying

No definition recorded.

Remediate system vulnerabilities within [ Assignment: organization-defined response times ].
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
network monitoring softwarecandidateneeds classifying

No definition recorded.

ieved through a variety of tools and techniques (e.g., audit record monitoring software, intrusion detection systems, intrusion prevention systems, malicious code protection software, scanning tools, network monitoring software). Strategic locations for monitoring devices include selected perimeter locations and near server farms that support critical applications with such devices being employed at managed system interfaces. The granularity of monitoring the information collected is based on organizational monitoring objectives and the capability of the system to support such objectives.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
mobile device functionalitycandidateneeds classifying

No definition recorded.

t it can be carried by a single individual; is designed to operate without a physical connection; possesses local, non-removable, or removable data storage; and includes a selfcontained power source. Mobile device functionality may include on-board sensors that allow the device to capture information, voice communication capabilities, and/or built-in features for synchronizing local data with remote locations. Examples include smart phones, smart watches, and tablets. Mobile devices are typically associated with a single individual. The processing, storage, and transmission capabilities of mob
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
mobile device connectioncandidateneeds classifying

No definition recorded.

ing that results from the monitoring of account usage, remote access, wireless connectivity, configuration settings, the use of maintenance tools and nonlocal maintenance, system component inventory, mobile device connection, equipment delivery and removal, physical access, temperature and humidity, communications at system interfaces, and the use of mobile code. Findings can be reported to organizational entities, such as the incident response team, help desk, and security or privacy offices. If organizations are prohibited from reviewing and analyzing audit records or unable to conduct such
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
known system vulnerabilitycandidateneeds classifying

No definition recorded.

To reduce or eliminate known system vulnerabilities.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
fixed local timecandidateneeds classifying

No definition recorded.

Record time stamps for audit records that meet [ Assignment: organizationdefined granularity of time measurement ] and 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.
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗
external hard drivecandidateneeds classifying

No definition recorded.

In contrast to requirement 03.08.01, which restricts user access to media, this requirement restricts or prohibits the use of certain types of media, such as external hard drives, flash drives, or smart displays. Organizations can use technical and nontechnical measures (e.g., policies, procedures, and rules of behavior) to control the use of system media. For example, organizations may control the use of portable storage devices by using physical cages on workstations to prohibit access to external ports or disabling or removing the ability to insert,
NIST SP 800-171 Rev 3 - Protecting CUI in Nonfederal Systemsproposed by dorianc@moxywolf.comOct 22, 2026open in CKI ↗