03.05.02
Device Identification and Authentication
Apply device identification and authentication to prove that users, devices, and authenticators are unique, protected, and trustworthy for CPCSC Level 2 readiness.
CPCSC Level 2 Control
Last updated June 25, 2026
03.05.01Identification and authentication
CPCSC Level 2 03.05.01: User Identification, Authentication, and Re-Authentication
Apply user identification, authentication, and re-authentication to prove that users, devices, and authenticators are unique, protected, and trustworthy for CPCSC Level 2 readiness. This guide separates the official ITSP.10.171 control language from practical implementation, evidence, auditor questions, and related controls.
Formal Control Language
Official ITSP.10.171 wording for 03.05.01. Use the Cyber Centre publication and contract requirements as the source of truth for certification, assessment, or procurement submissions.
- Uniquely identify and authenticate system users and associate that unique identification with processes acting on behalf of those users
- Re-authenticate users when [Assignment: organization-defined circumstances or situations requiring re-authentication]
Contains information sourced from Government of Canada material used under the Open Government Licence - Canada.
What This Means In Plain English
User Identification, Authentication, and Re-Authentication is part of the CPCSC Level 2 Identification and authentication family. This is about proving each user, device, and authenticator is unique, managed, protected, and strong enough for the sensitivity of the work.
For a founder, CISO, engineer, or compliance owner, the practical question is whether user identification, authentication, and re-authentication is visible in real operating evidence: a setting, workflow, ticket, log, approval, review, or exception record that can survive an external assessment.
Level 2 is different from Level 1 because the evidence has to survive an external assessment. A policy statement helps, but the stronger answer is a record that shows who did the work, when it ran, what system setting or workflow enforced it, and how exceptions were handled.
How To Implement It
1
Define the in-scope systems, owners, users, vendors, and data flows affected by user identification, authentication, and re-authentication.
2
Use unique accounts, MFA, password or authenticator standards, lifecycle controls, and technical settings that prevent shared or weak authentication paths.
3
Translate the formal requirement into one or two operating procedures: who performs it, how often, where it is recorded, and who approves exceptions.
4
Configure the relevant systems so the control is enforced by identity, endpoint, cloud, network, ticketing, monitoring, vendor, or documentation workflows rather than memory.
5
Keep evidence in a consistent folder, GRC system, ticket queue, or audit workspace so an assessor can trace the control from requirement to implementation to review.
Evidence Normally Gathered
User Identification, Authentication, and Re-Authentication: identity provider settings.
User Identification, Authentication, and Re-Authentication: MFA reports.
User Identification, Authentication, and Re-Authentication: password policy screenshots.
User Identification, Authentication, and Re-Authentication: authenticator inventory.
User Identification, Authentication, and Re-Authentication: account lifecycle tickets.
User Identification, Authentication, and Re-Authentication: device authentication settings.
User Identification, Authentication, and Re-Authentication: owner assignment and review cadence.
User Identification, Authentication, and Re-Authentication: exception, remediation, or POA&M records when the control is not fully implemented.
Common Auditor Questions
Where is user identification, authentication, and re-authentication implemented in the in-scope environment?
Who owns user identification, authentication, and re-authentication, and how do they know it is operating?
Show the evidence that proves user identification, authentication, and re-authentication ran during the assessment period.
What happens when user identification, authentication, and re-authentication fails, is bypassed, or has an exception?
How does this control connect to the system security plan, risk register, POA&M, and related CPCSC controls?
Sources
Source and attribution.
Formal control language is sourced from the Canadian Centre for Cyber Security ITSP.10.171 publication. CPCSC Level 2 assessment context references the Government of Canada CPCSC program overview and ITSP.10.171-01 assessment guidance.
CPCSC Program OverviewITSP.10.171ITSP.10.171-01Open Government Licence - Canada