Published

A managed-service provider proposes a new way to administer a Canadian operator’s critical network. The security team has an assessment, procurement has the contract change, and operations has the test results. Before approving the change, the accountable owner needs one reviewable record showing what risk was identified, what mitigation was required and what was actually verified.
Prepare the evidence alongside the work. Canada’s Critical Cyber Systems Protection Act (CCSPA) makes this a useful readiness exercise: connect the critical system, program version, third-party risk, implemented measures and retained decisions. A current status dashboard should lead to the documents that explain its status.
The Act’s Schedule 1 lists telecommunications services, interprovincial or international pipeline and power-line systems, nuclear energy systems, federally regulated transportation systems, banking systems, and clearing and settlement systems. Sector membership alone does not establish designation. Sections 7–8 connect the designated class of operators to the critical cyber systems they own, control or operate.
Record the organisation’s scope assessment, responsible owner and source checked. Link each potentially affected system to the service it supports and the provider dependencies that matter to its continuity or security. Review the assessment when a designation, service boundary or dependency changes.
Section 30 identifies records of program implementation, reported incidents, supply-chain and third-party risk mitigation, and measures implementing directions, plus matters prescribed by regulation. The following filing model turns those categories into reviewable work.
| File | Connect the records | Review question |
|---|---|---|
| Program implementation | Program version, affected systems, assigned actions, implemented controls, tests and unresolved work. | What was implemented, and what evidence supports that status? |
| Supplier-risk mitigation | Provider and service, identified risk, required mitigation, contract commitments, verification and follow-up. | Can the owner trace the identified risk to measures actually taken? |
| Reported incident | Source facts, affected systems, assessment, submitted report, regulator notification and retained submission evidence. | What was reported, to whom, when and on what factual basis? |
| Direction implementation | Received direction, authorised access, required measures, assigned owners, verification and communications. | Which evidence supports the recorded completion of each measure? |
Section 30(2) provides for these records to be kept in Canada, at a prescribed place or otherwise the operator’s place of business, with manner and period determined by the appropriate regulator unless regulations prescribe otherwise. Plan record residency, connected-system copies and retention against those requirements. The Act does not supply one universal retention period for this file.
The enacted text contains different timing mechanisms. Sections 9–11 set 90-day periods for program establishment and availability, linked to membership in a designated class following the relevant order, with a regulator extension mechanism. They do not start a universal 90-day countdown at Royal Assent.
Section 17 provides for incident reporting to the Communications Security Establishment within a period prescribed by regulations, not exceeding 72 hours. Section 18 addresses the subsequent regulator notification and report copy. Record the applicable rules, trigger, deadline and owner; do not turn the statutory upper limit into a default waiting period. Keep other applicable reporting requirements in the assessment.
For third parties, section 15 requires mitigation when relevant risk is identified under the program. A recorded approval should show the measures and follow-up; a risk-acceptance label alone does not demonstrate mitigation.
Connect the system, service, provider change and reviewed source documents.
Link the authorised decision to implementation evidence and unresolved actions.
Keep the decision and its supporting set available when later changes trigger reassessment.
Use department and responsibility boundaries for access: operations may need implementation tasks, procurement the provider commitments, and the incident team restricted investigation documents. A record can support several reviews without making every attachment visible to every participant.
Direction records need particular care. Section 25 limits disclosure of the fact and content of a direction to what is necessary to comply, with further disclosure restrictions. Configure the permitted audience and disclosure review accordingly. Security monitoring systems remain the source of high-volume telemetry; link the relevant preserved extracts and their source references to the evidence file.
Fictional readiness exercise, identifiers and internal approval conditions. A Canadian telecommunications operator rehearses the record workflow before designation. A provider proposes a new remote-support service for system SYS-204, which supports network operations.
The owner creates review CR-204 and connects SYS-204, the supported service, provider agreement, proposed access arrangements and the current program version. The scope assessment records the designation and commencement sources checked.
Security and operations review the assessment; procurement records the provider commitments. Under the operator’s internal policy, the authorised owner requires named support accounts and access limited to an approved support window, with verification before activation.
The first test demonstrates the named accounts but does not establish the support-window restriction. CR-204 stays open, the activation decision remains pending, and the provider receives an assigned request for the missing evidence.
A later test supplies the missing evidence. The reviewer links both test results, records the completed checks and authorises activation under the internal approval process. The retained record identifies the exact assessment, contract and program versions used.
If the provider changes the service again, the owner opens a linked review. If an incident occurs, the response team preserves the facts and assesses the reporting duties then applicable. The earlier approval and its supporting evidence remain available for that assessment.
A useful CCSPA readiness file shows the system and service, the identified risk, the measures taken and the records supporting the review. Establish those links during normal work, and track commencement, designation and regulatory detail separately so the evidence workflow can follow the obligations that actually apply.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.