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.
CPCSC Level 2 Control
Last updated June 25, 2026
03.05.07Identification and authentication
CPCSC Level 2 03.05.07: Password Management
Apply password management 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.07. Use the Cyber Centre publication and contract requirements as the source of truth for certification, assessment, or procurement submissions.
- Maintain a list of commonly used, expected, or compromised passwords and update the list [Assignment: organization-defined frequency] and when organizational passwords are suspected to have been compromised
- Verify that passwords are not found on the list of commonly used, expected, or compromised passwords when users create or update passwords
- Transmit passwords only over cryptographically protected channels
- Store passwords in a cryptographically protected form
- Select a new password upon first use after account recovery
- Enforce the following composition and complexity rules for passwords: [Assignment: organization-defined composition and complexity rules]
Contains information sourced from Government of Canada material used under the Open Government Licence - Canada.
What This Means In Plain English
Password Management 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 password management 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 password management.
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
Password Management: identity provider settings.
Password Management: MFA reports.
Password Management: password policy screenshots.
Password Management: authenticator inventory.
Password Management: account lifecycle tickets.
Password Management: device authentication settings.
Password Management: owner assignment and review cadence.
Password Management: exception, remediation, or POA&M records when the control is not fully implemented.
Common Auditor Questions
Where is password management implemented in the in-scope environment?
Who owns password management, and how do they know it is operating?
Show the evidence that proves password management ran during the assessment period.
What happens when password management 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