03.14.01
Flaw Remediation
Apply flaw remediation to find flaws, detect threats, monitor activity, and retain information appropriately for CPCSC Level 2 readiness.
Last updated June 25, 2026
Apply information management and retention to find flaws, detect threats, monitor activity, and retain information appropriately 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.14.08. 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.
Information Management and Retention is part of the CPCSC Level 2 System and information integrity family. This is about keeping systems healthy and watching for compromise through patching, malware protection, advisories, monitoring, and retention controls.
For a founder, CISO, engineer, or compliance owner, the practical question is whether information management and retention 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 information management and retention.
Define patch timelines, monitor alerts, deploy malicious-code protection, review advisories, use dedicated admin paths, and keep information according to retention rules.
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.
Information Management and Retention: patch reports.
Information Management and Retention: EDR coverage.
Information Management and Retention: alert review tickets.
Information Management and Retention: advisory tracking records.
Information Management and Retention: monitoring dashboards.
Information Management and Retention: retention settings.
Information Management and Retention: owner assignment and review cadence.
Information Management and Retention: exception, remediation, or POA&M records when the control is not fully implemented.
Where is information management and retention implemented in the in-scope environment?
Who owns information management and retention, and how do they know it is operating?
Show the evidence that proves information management and retention ran during the assessment period.
What happens when information management and retention 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