03.01.01
Account Management
Apply account management to control who can access in-scope systems, how information flows, and which access paths are allowed for CPCSC Level 2 readiness.
Last updated June 25, 2026
Apply access control for mobile devices to control who can access in-scope systems, how information flows, and which access paths are allowed for CPCSC Level 2 readiness. This guide separates the official ITSP.10.171 control language from practical implementation, evidence, auditor questions, and related controls.
Official ITSP.10.171 wording for 03.01.18. Use the Cyber Centre publication and contract requirements as the source of truth for certification, assessment, or procurement submissions.
Contains information sourced from Government of Canada material used under the Open Government Licence - Canada.
Access Control for Mobile Devices is part of the CPCSC Level 2 Access control family. This is about making access decisions enforceable. The organization needs to know who can reach specified information, which systems can exchange it, and which access paths are approved.
For a founder, CISO, engineer, or compliance owner, the practical question is whether access control for mobile devices 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.
Define the in-scope systems, owners, users, vendors, and data flows affected by access control for mobile devices.
Use identity groups, network rules, conditional access, remote-access approvals, data-flow boundaries, and exception records to make the access rule real in systems.
Translate the formal requirement into one or two operating procedures: who performs it, how often, where it is recorded, and who approves exceptions.
Configure the relevant systems so the control is enforced by identity, endpoint, cloud, network, ticketing, monitoring, vendor, or documentation workflows rather than memory.
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.
Access Control for Mobile Devices: access policy and role matrix.
Access Control for Mobile Devices: identity provider groups.
Access Control for Mobile Devices: access review records.
Access Control for Mobile Devices: remote access configuration.
Access Control for Mobile Devices: data-flow or boundary diagram.
Access Control for Mobile Devices: exception approvals.
Access Control for Mobile Devices: owner assignment and review cadence.
Access Control for Mobile Devices: exception, remediation, or POA&M records when the control is not fully implemented.
Where is access control for mobile devices implemented in the in-scope environment?
Who owns access control for mobile devices, and how do they know it is operating?
Show the evidence that proves access control for mobile devices ran during the assessment period.
What happens when access control for mobile devices 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?
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