03.12.01
Security Assessment
Apply security assessment to assess controls, track remediation, monitor effectiveness, and manage information exchanges for CPCSC Level 2 readiness.
CPCSC Level 2 Control
Last updated June 25, 2026
03.12.03Security assessment and monitoring
CPCSC Level 2 03.12.03: Continuous Monitoring
Apply continuous monitoring to assess controls, track remediation, monitor effectiveness, and manage information exchanges 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.12.03. Use the Cyber Centre publication and contract requirements as the source of truth for certification, assessment, or procurement submissions.
- Develop and implement a system-level continuous monitoring strategy that includes ongoing monitoring and security assessments.
Contains information sourced from Government of Canada material used under the Open Government Licence - Canada.
What This Means In Plain English
Continuous Monitoring is part of the CPCSC Level 2 Security assessment and monitoring family. This is about proving controls are assessed, gaps are tracked, monitoring continues between assessments, and information exchanges are governed.
For a founder, CISO, engineer, or compliance owner, the practical question is whether continuous monitoring 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 continuous monitoring.
2
Maintain an assessment plan, test controls, track POA&M items, monitor control health, and document exchange agreements for specified information.
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
Continuous Monitoring: assessment plan.
Continuous Monitoring: control test records.
Continuous Monitoring: POA&M.
Continuous Monitoring: continuous monitoring reports.
Continuous Monitoring: information exchange agreements.
Continuous Monitoring: remediation status reports.
Continuous Monitoring: owner assignment and review cadence.
Continuous Monitoring: exception, remediation, or POA&M records when the control is not fully implemented.
Common Auditor Questions
Where is continuous monitoring implemented in the in-scope environment?
Who owns continuous monitoring, and how do they know it is operating?
Show the evidence that proves continuous monitoring ran during the assessment period.
What happens when continuous monitoring 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