Identifier Management
✓ LOW ✓ MODERATE ✓ HIGHRequirements NIST SOURCE
Manage system identifiers by:
Requirement Context
This element is part of IA-4 — Identifier Management. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Requirement Context
This element is part of IA-4 — Identifier Management. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Requirement Context
This element is part of IA-4 — Identifier Management. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Requirement Context
This element is part of IA-4 — Identifier Management. See the Assessment section below for the related SP 800-53A examine/interview/test procedures. No engineering interpretation has been authored for this control yet.
Discussion (NIST Supplemental Guidance)
Common device identifiers include Media Access Control (MAC) addresses, Internet Protocol (IP) addresses, or device-unique token identifiers. The management of individual identifiers is not applicable to shared system accounts. Typically, individual identifiers are the usernames of the system accounts assigned to those individuals. In such instances, the account management activities of AC-2 use account names provided by IA-4 . Identifier management also addresses individual identifiers not necessarily associated with system accounts. Preventing the reuse of identifiers implies preventing the assignment of previously used individual, group, role, service, or device identifiers to different individuals, groups, roles, services, or devices.
Enhancements NIST SOURCE
IA-4(1) Prohibit Account Identifiers as Public Identifiers LOW MODERATE HIGH
Prohibit the use of system account identifiers that are the same as public identifiers for individual accounts.
Discussion
Prohibiting account identifiers as public identifiers applies to any publicly disclosed account identifier used for communication such as, electronic mail and instant messaging. Prohibiting the use of systems account identifiers that are the same as some public identifier, such as the individual identifier section of an electronic mail address, makes it more difficult for adversaries to guess user identifiers. Prohibiting account identifiers as public identifiers without the implementation of other supporting controls only complicates guessing of identifiers. Additional protections are required for authenticators and credentials to protect the account.
IA-4(2) Supervisor Authorization WITHDRAWN
Withdrawn. Incorporated into IA-12(1).
IA-4(3) Multiple Forms of Certification WITHDRAWN
Withdrawn. Incorporated into IA-12(2).
IA-4(4) Identify User Status LOW ✓ MODERATE ✓ HIGH
Manage individual identifiers by uniquely identifying each individual as [characteristics].
Discussion
Characteristics that identify the status of individuals include contractors, foreign nationals, and non-organizational users. Identifying the status of individuals by these characteristics provides additional information about the people with whom organizational personnel are communicating. For example, it might be useful for a government employee to know that one of the individuals on an email message is a contractor.
IA-4(5) Dynamic Management LOW MODERATE HIGH
Manage individual identifiers dynamically in accordance with [dynamic identifier policy].
Discussion
In contrast to conventional approaches to identification that presume static accounts for preregistered users, many distributed systems establish identifiers at runtime for entities that were previously unknown. When identifiers are established at runtime for previously unknown entities, organizations can anticipate and provision for the dynamic establishment of identifiers. Pre-established trust relationships and mechanisms with appropriate authorities to validate credentials and related identifiers are essential.
IA-4(6) Cross-organization Management LOW MODERATE HIGH
Coordinate with the following external organizations for cross-organization management of identifiers: [external organizations].
Discussion
Cross-organization identifier management provides the capability to identify individuals, groups, roles, or devices when conducting cross-organization activities involving the processing, storage, or transmission of information.
IA-4(7) In-person Registration WITHDRAWN
Withdrawn. Incorporated into IA-12(4).
IA-4(8) Pairwise Pseudonymous Identifiers LOW MODERATE HIGH
Generate pairwise pseudonymous identifiers.
Discussion
A pairwise pseudonymous identifier is an opaque unguessable subscriber identifier generated by an identity provider for use at a specific individual relying party. Generating distinct pairwise pseudonymous identifiers with no identifying information about a subscriber discourages subscriber activity tracking and profiling beyond the operational requirements established by an organization. The pairwise pseudonymous identifiers are unique to each relying party except in situations where relying parties can show a demonstrable relationship justifying an operational need for correlation, or all parties consent to being correlated in such a manner.
IA-4(9) Attribute Maintenance and Protection LOW MODERATE HIGH
Maintain the attributes for each uniquely identified individual, device, or service in [protected central storage].
Discussion
For each of the entities covered in IA-2, IA-3, IA-8 , and IA-9 , it is important to maintain the attributes for each authenticated entity on an ongoing basis in a central (protected) store.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for IA-4 yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- personnel or roles from whom authorization must be received to assign an identifier are defined;
- a time period for preventing reuse of identifiers is defined;
- system identifiers are managed by receiving authorization from <IA-04_ODP[01] personnel or roles> to assign to an individual, group, role, or device identifier;
- system identifiers are managed by selecting an identifier that identifies an individual, group, role, service, or device;
- system identifiers are managed by assigning the identifier to the intended individual, group, role, service, or device;
- system identifiers are managed by preventing reuse of identifiers for <IA-04_ODP[02] time period>.
Examine
[SELECT FROM: Identification and authentication policy; procedures addressing identifier management; procedures addressing account management; system security plan; system design documentation; system configuration settings and associated documentation; list of system accounts; list of identifiers generated from physical access control devices; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with identifier management responsibilities; organizational personnel with information security responsibilities; system/network administrators; system developers].
Test
[SELECT FROM: Mechanisms supporting and/or implementing identifier management].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for IA-4. This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Identification and authentication policy
- system security plan
Configuration
- system design documentation
- system configuration settings and associated documentation
Testing
- Mechanisms supporting and/or implementing identifier management
Other Records
- procedures addressing identifier management
- procedures addressing account management
- list of system accounts
- list of identifiers generated from physical access control devices
- other relevant documents or records