03.05.05Identifier managementITSP.10.171Identification and authentication
Official Requirement
A. Receive authorization from organizational personnel or roles to assign an individual, group, role, service, or device identifier. B. Select and assign an identifier that identifies an individual, group, role, service, or device. C. Prevent reuse of identifiers for [Assignment: organization-defined time period]. D. Manage individual identifiers by uniquely identifying each individual as [Assignment: organization-defined characteristic identifying individual status].
Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3
In Plain English
Every identifier (username, service account name, device ID) must be formally authorized, uniquely assigned, and managed throughout its lifecycle. Identifiers must not be reused for a defined period after deactivation. The status of each identifier (active, suspended, terminated) must be tracked.
These are typical controls and implementation steps. Your systems and environment may differ.
Typical Control Identifier lifecycle management
Implementation Steps
Automate identifier provisioning through HR-to-IdP integration ensuring each identifier is unique and authorized
Implement naming conventions for identifiers (user accounts, service accounts, device identifiers) that prevent ambiguity and ensure uniqueness
Configure the IdP to prevent identifier reuse for a defined period (e.g., 2 years) after account deletion
Track identifier status (active, disabled, deleted) in the IdP and conduct periodic reviews to ensure status accuracy
Tools / Systems
IdP with automated provisioning (Azure AD, Okta)HR integration (SCIM, Workday connector)Identifier naming convention documentationGRC platform for identifier review tracking
Typical Control Identifier lifecycle management
Evidence Artifacts
IdP configuration showing identifier uniqueness and reuse prevention settings
Identifier provisioning workflow with authorization records
📅Continuous automated management; quarterly identifier status review
Cross-framework mappings coming in v1.1
When we add ISO 42001 and ISO 27001, you'll see which controls map to this criterion.
ISO
ISO 42001
AI Management Systems
ISO
ISO 27001
Information Security
Mapping data will appear here automatically when the frameworks are published.