DigitalXForce

Home » Automated GRC » Canada’s Critical Cyber Systems Protection Act (CCSPA): what Bill C-8 means for banks, and a 90-day readiness plan

Canada’s Critical Cyber Systems Protection Act (CCSPA): what Bill C-8 means for banks, and a 90-day readiness plan

The Critical Cyber Systems Protection Act (CCSPA) is the Canadian federal law, enacted by Bill C-8 with Royal Assent on June 15, 2026, that will require designated operators of vital services in banking, clearing and settlement, telecommunications, energy, nuclear and federally regulated transportation to set up a cyber security program within 90 days, mitigate their supply chain and third-party risks, and report cyber security incidents to the Communications Security Establishment within a period that the regulations set and that cannot exceed 72 hours.

I read the Act section by section for this guide, together with the OSFI guidance a Canadian bank already works under. This page is for the CISO, the head of third-party risk and the compliance team at a bank, a financial market infrastructure or another operator that expects to be designated. It gives the status of the law today, every obligation with its deadline, what changes for a bank already supervised by OSFI, and the 90-day plan I would run.

Is the CCSPA in force?

No, not yet. Bill C-8 received Royal Assent on June 15, 2026 as chapter 9 of the Statutes of Canada 2026. Its first part, the amendments to the Telecommunications Act, took effect that day. The CCSPA, its second part, is enacted but not in force: the Justice Laws text, current to October 29, 2026, marks every section “not in force”, and Schedule 2, the list of the classes of operators the Act will apply to, is still empty.

Two orders of the Governor in Council will start the clock. The first brings the Act into force, and Public Safety Canada has said it will do this gradually. The second fills Schedule 2 with classes of operators and pairs each class with its regulator. An operator’s 90 days begin on the day it becomes a member of a listed class, not on the day of Royal Assent, so the time to prepare is the time before that order.

Who does the CCSPA cover?

The Act protects six vital services and systems, listed in its Schedule 1:

  • Banking systems.
  • Clearing and settlement systems.
  • Telecommunications services.
  • Interprovincial or international pipeline and power line systems.
  • Nuclear energy systems.
  • Transportation systems within the legislative authority of Parliament.

It names six regulators: the Superintendent of Financial Institutions, the Bank of Canada, the Minister of Industry, the Minister of Transport, the Canadian Energy Regulator and the Canadian Nuclear Safety Commission. Schedule 2 will say which regulator oversees which class of operators.

Two of the six vital services are financial. The Bank of Canada already oversees the clearing and settlement systems designated under the Payment Clearing and Settlement Act, including Lynx and CDSX, and the Superintendent of Financial Institutions already supervises the federally regulated banks. That is why I expect the financial sector to feel the CCSPA early.

A supplier to a designated operator is not designated by the Act. It will still feel the law, because section 15 requires the operator to mitigate the risks it finds in its supply chain and in the third-party products and services it uses, and the operator will ask its suppliers for the evidence.

What the CCSPA requires, with every deadline

ObligationSectionThe clock
Establish a cyber security program9(1)Within 90 days after the operator becomes a member of a class in Schedule 2
Tell the regulator the program exists9(2)Immediately after the program is established
Provide the program to the regulator10Within the same 90 days, which the regulator may extend at the operator’s written request (section 11)
Implement and maintain the program12From then on
Review the program13Start on each anniversary or on dates the regulations set, finish within 60 days, report the result within 30 days after that
Report material changes in ownership, control, supply chain or third-party products and services14Within a period the regulations will set
Mitigate supply chain and third-party risks15Once the risks are identified
Report a cyber security incident to the Communications Security Establishment17Within a period the regulations will set, never more than 72 hours
Tell the regulator about the incident report and give it a copy18Immediately after reporting
Comply with a cyber security direction from the Governor in Council20As the direction sets
Keep records of the program, incidents, supply chain steps and directions, in Canada30Ongoing

The program itself must do four things under section 9: identify and manage the organization’s cyber security risks, including supply chain and third-party risks; protect its critical cyber systems from being compromised; detect cyber security incidents; and minimize the impact of the incidents that happen.

What the CCSPA adds for a bank already supervised by OSFI

A federally regulated bank does not start from zero. Three pieces of OSFI guidance already cover most of the ground, and the CCSPA adds a second reporting line and a legal deadline on top of them.

Incident reporting becomes two clocks. OSFI’s Technology and Cyber Security Incident Reporting advisory, in effect since August 13, 2021, asks a federally regulated financial institution to report a reportable incident to OSFI within 24 hours, or sooner if possible. The CCSPA adds a report to the Communications Security Establishment within the regulated period of at most 72 hours, and an immediate notice and copy to the appropriate regulator. A bank should plan to run both clocks from one incident record, so that the facts in the two reports agree.

Guideline B-13 already covers the program. OSFI’s Guideline B-13, Technology and Cyber Risk Management, applies to all federally regulated financial institutions and is organized in three domains: governance and risk management, technology operations and resilience, and cyber security. A bank that can show B-13 working with current evidence has most of what section 9 of the CCSPA asks a program to do.

Guideline B-10 already covers third parties. OSFI’s Guideline B-10, Third-Party Risk Management, expects an institution to manage the risks of all its third-party arrangements across their lifecycle, including the technology and cyber operations that third parties carry out. The CCSPA turns that expectation into a legal duty under sections 14 and 15.

Guideline E-21 already mapped the critical operations. OSFI’s Guideline E-21, Operational Risk Management and Resilience, asked institutions for full adherence by September 1, 2026, including the mapping of critical operations and tolerances for disruption, with scenario testing of all critical operations due by September 1, 2027. That mapping is much of the groundwork for deciding which systems are critical cyber systems under the CCSPA.

The gap a bank has to close is rarely a missing policy. It is showing one regulator, with current evidence, that the controls behind B-13, B-10 and E-21 deliver the four outcomes the CCSPA names, for the systems the CCSPA calls critical.

The CCSPA names outcomes, not controls

Nothing in the Act tells an operator which controls to run. Section 9 asks for four outcomes, and those four outcomes line up with the functions of the NIST Cybersecurity Framework: identify, protect, detect, and respond and recover. An operator that already tests its controls against NIST CSF or ISO/IEC 27001 does not need a second control set for the CCSPA.

DigitalXForce for financial services maps each control once to every framework it belongs to, from 50+ frameworks, and tests it against live evidence from the tools the bank connects through 250+ technology integrations. One test result then answers the CCSPA, OSFI’s guidelines and every other rule the bank reports against, instead of being collected again for each of them.

The 72 hours are a decision clock

The Act defines a cyber security incident as one that “interferes or may interfere” with the continuity or security of a vital service, or with the confidentiality, integrity or availability of a critical cyber system. The words “may interfere” matter. An operator cannot wait for confirmed harm before it decides whether to report, and the 72 hours are a ceiling that the regulations may lower. For a bank, OSFI’s 24 hours arrive first.

In my experience the slow part of incident reporting is rarely detection. It is the hours spent working out which system is affected, whether that system is critical, which supplier is involved and what the evidence shows. A team that has to assemble that picture from four tools during an incident will spend its reporting window on assembly.

In DigitalXForce, a failed control, a posture change or a vendor event arrives in X-ROC, the XForce Risk Operations Center, as a real-time alert with the evidence attached. X-ROC triages alerts, escalates them and tracks remediation to closure, and it ranks them by quantified business impact rather than by a severity label alone. When a supplier reports a breach, AI JedAI maps it to the services and data that depend on that supplier. Those are the answers a reporting decision needs, already in one place when the clock starts.

Supply chain and third-party risk is a standing duty

Sections 14 and 15 turn third-party risk management from a procurement exercise into a legal duty. The operator must mitigate supply chain and third-party risks once it identifies them, and it must tell its regulator about material changes in its supply chain or in the third-party products and services it uses.

An annual questionnaire cannot carry that duty, because a supplier’s risk changes between reviews. DigitalXForce scores every vendor from its questionnaire answers, its evidence and external signals. A core banking or payments provider placed in Tier 1 Critical is monitored continuously, with connector evidence from its own systems and AI review of its SOC 2 and ISO reports. Tier 2 vendors are refreshed weekly and Tier 3 vendors monthly, with triggered alerts in between.

The External Risk View watches a supplier from the outside without an agent, a questionnaire or the supplier’s cooperation, and it maps fourth-party and nth-party dependencies. That is how an operator finds the supplier of its supplier before an incident introduces them.

How fast can an operator be ready for the CCSPA?

The law gives 90 days from designation. Ninety days sounds generous until the first thirty go to finding out who owns each system. The fastest operators will be the ones who start before Schedule 2 is filled, and this is the plan I would run.

Days 1 to 30: know what is critical and what the evidence says. List the systems that support the vital service and decide which ones are critical cyber systems, starting from the critical operations a bank mapped for E-21. Connect the security, cloud and identity tools that hold the evidence, and tier the suppliers behind each critical system. DigitalXForce’s standard proof of value runs for 4 weeks on the customer’s own systems and frameworks: connectors are configured in week 1, the attack surface and External Risk View are set up in week 2, the security blueprint, the first risk assessment and the third-party assessments run in week 3, and the results are reviewed in week 4. The first month of the 90 days can therefore also be the evaluation, with scope and success criteria agreed before it starts.

Days 31 to 60: write the program from the evidence. Map the controls you already test to the four outcomes in section 9, and write the program document from what the controls show today rather than from what a policy says they should do. Set the internal steps for an incident report so that the decision, the report to the Communications Security Establishment, the notice to the regulator and, for a bank, the 24-hour report to OSFI each have an owner.

Days 61 to 90: prove the program works, then file it. Run an incident reporting exercise against both clocks. Decide where the records will be kept, since section 30 requires them in Canada. Establish the program, notify the regulator immediately, and provide the program before day 90. If a gap cannot close in time, section 11 lets the operator ask the regulator in writing for an extension, and the request is stronger with the evidence behind it.

After day 90 the work becomes Continuous Control Assurance, which uses evidence, monitoring and validation to determine whether controls continue to operate as expected. In DigitalXForce every test result is stored with the evidence it read and a timestamp, so the annual review under section 13 starts from a record instead of a scramble.

What to ask a platform before you rely on it for the CCSPA

A bank choosing a platform for CCSPA readiness should ask any vendor, DigitalXForce included, to show these on the bank’s own systems rather than describe them.

  • Show one control test result that answers the CCSPA, OSFI’s guidelines and our other frameworks without being collected twice.
  • Show an incident record that carries the affected system, its criticality, the suppliers involved and the evidence, so that the 24-hour and 72-hour reports can be written from it.
  • Show how a Tier 1 supplier is watched between reviews, and what happens when its evidence changes.
  • Show the evidence behind a supplier’s score, traced to the tool it came from and the date it was read.
  • Show what your connectors read, and confirm that they never read business records or customer data.

DigitalXForce’s connectors read configuration and compliance signals only, never business records or customer data, and an analyst reviews every conclusion of AI JedAI and every draft of XForce GPT before anyone relies on it.

What are the penalties under the CCSPA?

The regulations will set the amounts, within a maximum the Act fixes under section 91: $500,000 per violation for an individual and $15,000,000 per violation for any other person. Under section 94, a violation that continues on more than one day counts as a separate violation for each day. The Act also sets out offences, which is one more reason to keep the evidence of every step.

Frequently asked questions

What is the Critical Cyber Systems Protection Act?

The Critical Cyber Systems Protection Act (CCSPA) is the Canadian federal law, enacted by Bill C-8 in June 2026, that requires designated operators of vital services in banking, clearing and settlement, telecommunications, energy, nuclear and federally regulated transportation to run a cyber security program, mitigate supply chain risks and report cyber security incidents.

Is the CCSPA in force?

Not yet. Bill C-8 received Royal Assent on June 15, 2026, but the CCSPA comes into force by order of the Governor in Council, and as of the Justice Laws text current to October 29, 2026, no section was in force and no class of operators was listed in Schedule 2.

Does the CCSPA apply to Canadian banks?

Banking systems and clearing and settlement systems are two of the six vital services in Schedule 1 of the CCSPA, and the Act names the Superintendent of Financial Institutions and the Bank of Canada among its regulators, so a bank or a financial market infrastructure is covered once its class of operators is listed in Schedule 2.

How long does an operator have to report a cyber security incident under the CCSPA?

The operator reports to the Communications Security Establishment within a period the regulations will set, which section 17 caps at 72 hours, and then immediately notifies its regulator and gives it a copy of the report.

How does the CCSPA relate to OSFI’s incident reporting?

OSFI’s Technology and Cyber Security Incident Reporting advisory asks a federally regulated financial institution to report to OSFI within 24 hours, or sooner if possible, and the CCSPA adds a report to the Communications Security Establishment within at most 72 hours, so a designated bank should expect to run both clocks from one incident record.

How long does a designated operator have to set up a cyber security program?

Section 9 gives a designated operator 90 days after it becomes a member of a class of operators in Schedule 2, and section 11 lets the regulator extend that period at the operator’s written request.

How quickly can DigitalXForce help an operator get ready for the CCSPA?

DigitalXForce’s standard proof of value runs for 4 weeks on the operator’s own systems and frameworks, with connectors configured in week 1 and the results reviewed in week 4, which leaves the rest of the 90-day window for writing, approving and filing the cyber security program.

Does the CCSPA apply to suppliers of designated operators?

The Act designates operators, not their suppliers, but section 15 requires each designated operator to mitigate its supply chain and third-party risks, so suppliers to those operators should expect to be asked for evidence.

What are the maximum penalties under the CCSPA?

Section 91 caps administrative monetary penalties at $500,000 per violation for an individual and $15,000,000 per violation for any other person, and section 94 treats each day a violation continues as a separate violation.

Sources

A 30 minute walkthrough shows how the 4 week proof of value would run on your own systems, suppliers and frameworks. The DigitalXForce team replies to every request within 1 business day.

Request a demo

Scroll to Top
Title banner reading Era of Automated Security Risk and Posture Management with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Security Risk and Posture Management

Title banner reading Era of Automated Third Party Risk Management with Trust but Verify, with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Third Party Risk Management: Trust but Verify

Title banner reading Era of Automated Security Plans, Standards, Policies and Procedures, with the DigitalXForce logo beside a hand holding connected user icons and a report

Era of Automated Security Plans, Standards, Policies and Procedures