The Cyber Centre urges heightened vigilance amid global tensions and high-profile events

<article data-history-node-id="8183" about="/en/news-events/cyber-centre-urges-heightened-vigilance-amid-global-tensions-high-profile-events" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>The Communications Security Establishment Canada (CSE) and its Canadian Centre for Cyber Security (Cyber Centre) continue to urge Canadian organizations to remain vigilant during periods of heightened geopolitical tensions and high-profile events.</p> <p>Although malicious cyber activity can occur at any time, organizations should be especially vigilant during these periods as they can draw the attention of cyber threat actors, including ideologically motivated individuals or groups targeting organizations they perceive as adversaries. These actors may try to disrupt services, deface websites, attract publicity or undermine confidence in institutions and organizations.</p> <p>Threats may include distributed denial of service (DDoS) attacks against public-facing websites and online services, as well as website defacement and other disruptive activity. These attacks can disrupt operations, cause financial losses, damage reputations and reduce access to critical services. They may also be used to distract defenders from other malicious cyber activity targeting an organization at the same time.</p> <p>All Canadian organizations, especially essential service providers and critical infrastructure operators, should review their cyber security posture, and consult the following Cyber Centre resources.</p> <ul><li>Read our previous <a href="/en/news-events/cyber-centre-statement-distributed-denial-service-campaign-targeting-multiple-canadian-sectors">statement on a distributed denial of service (DDoS) campaign targeting multiple Canadian sectors</a></li> <li>Adopt our <a href="/en/cyber-security-readiness/cross-sector-cyber-security-readiness-goals-toolkit">Cross-Sector Cyber Security Readiness Goals</a></li> <li>Consult our <a href="/en/guidance/top-10-it-security-actions-protect-internet-connected-networks-and-information-itsm10089">Top 10 IT security actions to protect Internet connected networks and information</a></li> <li>Review and implement the advice and guidance on: <ul><li><a href="/en/guidance/defending-against-distributed-denial-service-ddos-attacks-itsm80110">Defending against distributed denial of service (DDoS) attacks</a></li> <li><a href="/en/guidance/distributed-denial-service-attacks-prevention-and-preparation-itsap80110">Distributed denial of service attacks - prevention and preparation</a></li> <li><a href="/en/alerts-advisories/distributed-denial-service-campaign-targeting-multiple-canadian-sectors">Distributed Denial of Service campaign targeting multiple Canadian sectors</a></li> <li><a href="/en/guidance/website-defacement-itsap00060">Website defacement</a></li> <li><a href="/en/guidance/developing-your-incident-response-plan-itsap40003">Developing your incident response plan</a></li> <li><a href="/en/guidance/security-considerations-critical-infrastructure-itsap10100">Security considerations for critical infrastructure</a></li> <li><a href="/en/guidance/protect-your-operational-technology-itsap00051">Protect your operational technology</a></li> <li><a href="/en/news-events/joint-guidance-principles-operational-technology-cyber-security">Joint guidance on the principles of operational technology cyber security</a></li> <li><a href="/en/news-events/joint-guidance-isolating-vital-systems">Joint guidance on isolating vital systems</a></li> </ul></li> <li>Explore our <a href="/en/cyber-security-readiness/critical-infrastructure-resilience-escalated-threat-navigation-initiative">Critical infrastructure resilience and escalated threat navigation initiative</a></li> </ul><p>The Cyber Centre continues to work closely with government, critical infrastructure operators, industry partners, and international allies to monitor the cyber threat environment and support the protection of Canadian systems and networks.</p> <p>Organizations should act now to strengthen their cyber defences and promptly report cyber incidents or suspicious cyber activity to the Cyber Centre through our <a href="https://www.cyber.gc.ca/en/incident-management">online portal</a>.</p> </div> </div> </div> </div> </div> </article>

2026/9/4
阅读更多

G7 Cybersecurity Working Group call to action on preparing for the post-quantum era

<article data-history-node-id="8160" about="/en/news-events/g7-cybersecurity-working-group-call-action-preparing-post-quantum-era" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>Canada is joining its G7 Cybersecurity Working Group partners in releasing the <strong>Preparing for the Post-Quantum Era: A Call to Action</strong>, a joint publication highlighting the growing risks that quantum computing poses to current public-key cryptography and urging organizations to begin transitioning to post-quantum cryptography (PQC) now.</p> <p>The publication emphasizes that while the timeline for cryptographically relevant quantum computers (CRQCs) remains uncertain, organizations face immediate risks such as "harvest now, decrypt later" attacks. In these attacks, threat actors collect encrypted data now, with the intention of decrypting it in the future using quantum computing capabilities. It also warns that quantum-enabled attacks could compromise authentication mechanisms, enabling attackers to impersonate trusted entities, forge data, and undermine secure communications.</p> <p>The publication recommends ways to support a coordinated global transition to <abbr title="post-quantum cryptography">PQC</abbr>. To help organizations and governments prepare for the transition, the publication outlines five priority areas for action:</p> <ul><li>raising awareness of quantum-related cybersecurity risks and the benefits of <abbr title="post-quantum cryptography">PQC</abbr></li> <li>developing national strategies to support the adoption and availability of <abbr title="post-quantum cryptography">PQC</abbr> technologies</li> <li>advancing research and development to support innovation and practical deployment of <abbr title="post-quantum cryptography">PQC</abbr> solutions</li> <li>strengthening public-private partnerships to share expertise, resources, and best practices</li> <li>integrating <abbr title="post-quantum cryptography">PQC</abbr> into cybersecurity requirements</li> </ul><p>The publication calls on public and private sector organizations to adopt a phased, risk-based approach to <abbr title="post-quantum cryptography">PQC</abbr> migration. This includes taking inventory of cryptographic assets, identifying critical systems, mapping dependencies, and developing transition plans to help protect sensitive data and digital infrastructure.</p> <p>Consult the full publication: <a href="https://cyber.gouv.fr/en/publications/jointly-led-international-publications/preparing-for-the-post-quantum-era-a-call-to-action/">Preparing for the post-quantum era: a call to action</a></p> <h2>Learn more</h2> <ul><li><a href="/en/news-events/g7-cybersecurity-working-group-statement-preparing-post-quantum-cryptography-migration">G7 Cybersecurity Working Group statement on preparing for a post-quantum cryptography migration</a></li> <li><a href="/en/guidance/preparing-your-organization-quantum-threat-cryptography-itsap00017">Preparing your organization for the quantum threat to cryptography (ITSAP.00.017) - Canadian Centre for Cyber Security</a></li> <li><a href="/en/guidance/roadmap-migration-post-quantum-cryptography-government-canada-itsm40001">Roadmap for the migration to post-quantum cryptography for the Government of Canada (ITSM.40.001)</a></li> </ul></div> </div> </div> </div> </div> </article>

2026/9/3
阅读更多

Joint guidance on best practices for service providers when communicating under pressure

This joint guidance explains why effective communications during outages is critical to minimize operational impacts, maintain credibility and situational awareness, and support response efforts.

2026/9/2
阅读更多

Joint guidance on opportunities for artificial intelligence in cyber defence

<article data-history-node-id="8082" about="/en/news-events/joint-guidance-opportunities-artificial-intelligence-cyber-defence" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>The Canadian Centre for Cyber Security (Cyber Centre) has joined the Australian Signals Directorate's Australian Cyber Security Centre (ASD's ACSC) and the following international partners in releasing cyber security guidance on opportunities for artificial intelligence (AI) in cyber defence:</p> <ul><li>New Zealand’s National Cyber Security Centre (NCSC-NZ)</li> <li>United Kingdom’s National Cyber Security Centre (NCSC-UK)</li> </ul><p>AI presents a significant opportunity for cyber defenders. When used safely, securely and responsibly, AI can:</p> <ul><li>strengthen prioritisation of cyber risks</li> <li>improve detection of threats and vulnerabilities</li> <li>support faster response and recovery</li> <li>reduce reliance on repetitive manual tasks</li> </ul><p>The joint guidance explains how organizations can use AI to improve their cyber security while also managing the risks that come with using AI. The guidance describes how the cyber security environment is changing and shows how AI can support key security activities, including governance, identifying risks, protecting systems, detecting threats, responding to incidents, and recovering from cyber attacks.</p> <p>The guidance also provides practical principles for adopting AI securely and includes important questions that cyber security teams should ask AI vendors to help ensure AI tools are used safely and securely.</p> <p>Consult the full joint guidance: <a href="https://www.cyber.gov.au/business-government/secure-design/artificial-intelligence/opportunities-for-ai-in-cyber-defence?ref=search">Opportunities for AI in cyber defence - Use of AI by cyber-security teams</a></p> </div> </div> </div> </div> </div> </article>

2026/8/12
阅读更多

Security considerations for electronic vote tabulators - ITSM.10.102

<article data-history-node-id="8032" about="/en/guidance/security-considerations-electronic-vote-tabulators-itsm10102" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>The use of ballot counting systems, also known as vote tabulation technology, to replace manual ballot counting during democratic elections is gaining wider adoption. These technologies can help improve the efficiency of the ballot tabulation process, as well as reduce human-related errors during the ballot counting process.</p> <p>This publication provides guidance on the cyber security considerations and system requirements for deploying vote tabulators during democratic elections. It highlights the key risks, threats and safeguards that elections management authorities should assess when considering ballot counting systems.</p> <section><details class="mrgn-tp-md"><summary><h2 class="h3">Table of contents</h2> </summary><ul class="list-unstyled"><li><a href="#1">Scope</a></li> <li><a href="#2">Electronic voting</a> <ul><li><a href="#fig1">Figure 1: Generic elections system architecture</a></li> </ul></li> <li><a href="#3">Ballot counting and tabulation</a> <ul><li><a href="#3.1">Types of vote tabulators</a></li> </ul></li> <li><a href="#4">Threat analysis</a></li> <li><a href="#5">Security control considerations</a> <ul><li><a href="#5.1">Physical and hardware security</a></li> <li><a href="#5.2">Lifecycle security</a></li> <li><a href="#5.3">Continuous risk assessment</a></li> <li><a href="#5.4">Protect your data</a></li> <li><a href="#5.5">Network isolation safeguards</a></li> <li><a href="#5.6">Secure access controls</a></li> <li><a href="#5.7">Validate and authenticate devices</a></li> <li><a href="#5.8">Patches and system updates</a></li> <li><a href="#5.9">Secure application development</a></li> <li><a href="#5.10">Audit log monitoring</a></li> <li><a href="#5.11">Business continuity</a></li> <li><a href="#5.12">Educate users</a></li> <li><a href="#5.13">Security control effectiveness</a></li> </ul></li> <li><a href="#6">Conclusion</a></li> </ul></details></section><section class="mrgn-tp-md"><p>Adopting digital technologies to improve the efficient delivery of the electoral process is an increasingly attractive proposition for modern democratic elections. Elections administrators are embracing the use of modern digital methods to improve or replace traditional and manual voting processes. Manual counting can be subject to human errors from fatigue, eyestrain, or distractions, which can lead to ballots being misjudged and misallocated. In very tight electoral races, those errors can have serious consequences. Using electronic vote counting technologies to support aspects of the elections process can help prevent human-related computational errors, expand voter accessibility options, and improve election transparency. These technologies can also allow for the timely reporting of elections results.</p> <p>Although federal elections in Canada do not use vote tabulators or ballot counting systems, these systems have been used in provincial and municipal government elections. Vote tabulators are electronic devices used to automate the counting of marked paper ballots. Some specific models may support the storage of digital ballot records, integration with assistive devices or vote capturing capabilities, and other additional functionalities. However, despite their potential benefits, the associated risks must be carefully considered.</p> <p>Replacing traditional processes with vote tabulators can have many advantages; however, this can introduce new vulnerabilities and threats into the democratic process, allowing threat actors opportunities to inflict harm. These threats may come from sophisticated nation-state actors or unprincipled stakeholders interested in disrupting the peaceful conduct of the democratic process. Before deploying vote tabulators, elections authorities should conduct a detailed risk assessment to evaluate the potential risks and associated security threats. The Cyber Centre’s <a href="/en/guidance/cyber-threats-canadas-democratic-process-2025-update">Cyber threats to democratic process: 2025 update</a> assesses that the likelihood for state-sponsored cyber actors to target Canadian elections is <strong>almost certain</strong>. It is important to understand specific risks and threats that may be associated with electronic vote tabulation deployments.</p> <p>In this publication, we discuss important cyber security considerations for elections administrators when deciding whether to use vote tabulators, the recommended secure architecture model for deploying these devices, as well as the security controls required to safeguard the integrity of the system. Note that it is difficult to establish suitably secure network connectivity for any election’s infrastructure.</p> </section><h2 id="1">Scope</h2> <p>This guidance applies to vote-tabulation systems that process paper ballots only, not systems that handle electronic ballots. While some recommendations may also apply to electronic ballot systems, they may not fully address the distinct threats those systems face.</p> <h2 id="2">Electronic voting</h2> <p>Electronic voting system architectures are complex and can involve many disparate systems. An electronic voting system architecture describes the information systems components involved in electronic voting and how these components interact with each other. These systems may include:</p> <ul><li>public websites</li> <li>party registration systems</li> <li>voter registrations systems</li> <li>ballot creation and printing systems</li> <li>election management systems</li> <li>online voting systems</li> <li>ballot counting or vote tabulation systems</li> <li>results publishing systems</li> </ul><p>These systems often run distinct software and firmware technologies, can be interconnected, and may communicate across diverse network protocols. Figure 1 depicts a generic modern electronic voting systems architecture, based on the Center for Internet Security’s (CIS) <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=&amp;ved=2ahUKEwiyvL6B0MiCAxXQJjQIHXDTB0wQFnoECBYQAQ&amp;url=https%3A%2F%2Fwww.cisecurity.org%2Fwp-content%2Fuploads%2F2018%2F02%2FCIS-Elections-eBook-15-Feb.pdf&amp;usg=AOvVaw0Dq56eE-JFpTwo7r7o9ENs&amp;opi=89978449">Handbook for Elections Infrastructure Security</a>.</p> <div class="panel panel-default"> <div class="panel-body"> <figure id="fig1"><figcaption class="text-center"><strong>Figure 1: Generic elections system architecture</strong></figcaption><img alt="Generic elections system - Long description immediately follows" class="img-responsive" src="https://imgproxy.citrusreader.com/Qqm-WlLbHD87_sQSRiPOVKMkT6HoEvGRJfZbfDWbuuw/raw:1/aHR0cHM6Ly9jeWJlci5nYy5jYS9zaXRlcy9kZWZhdWx0L2ZpbGVzL2ltYWdlcy9pdHNtLjEwLjEwMi1maWcxLWUucG5n"></figure><p><strong>Figure 1: Generic elections systems architecture</strong> presents a visual representation of a generic electronic voting system architecture. The image provides additional details on how ballots go from creation and printing to having the results counted and tabulated to the results being published.</p> <p>The components outlined in the image represent the entirety of a generic elections system architecture, including:</p> <ol><li>voter registration systems</li> <li>party and candidate registration and verification</li> <li>campaign finance management</li> <li>election management systems</li> <li>ballot creation and printing</li> <li>electronic poll books</li> <li>ballot capturing devices</li> <li>ballot counting and tabulation <ul><li>ballot scanners</li> <li>ballot counting and tabulators</li> </ul></li> <li>results transmission and publishing</li> </ol></div> </div> <p>This guidance is focused on the ballot counting and ballot tabulation components of this architecture. Our recommendations address core cyber security and operational issues that require attention to safely operate and deploy these systems. First, we provide a generic description for ballot counting and tabulation systems.</p> <div class="clearfix"> </div> <div class="pull-right small text-muted mrgn-bttm-0"><a href="#wb-tphp">Top of page</a> <span aria-hidden="true" class="text-primary glyphicon glyphicon-circle-arrow-up"></span></div> <h2 id="3">Ballot counting and tabulation</h2> <p>Ballot counting and tabulation is the process of counting and aggregating used and unused ballots in an election. The process involves gathering valid and invalid (spoiled) ballots, counting unused ballots, and aggregating valid ballots for each candidate in the election. Ballot counting and tabulation can be completed manually (namely by hand-counting) or by using electronic systems such as vote tabulators. Both methods can introduce errors in the process for various reasons. For example, if elections workers are tired or distracted, counting ballots by hand may lead to computational errors. Similarly, software flaws or compromises of electronic vote tabulators may lead to votes being inaccurately categorized. In general, it is important for elections administrators to continually assess counting methods and implement mechanisms to determine or validate that their counting processes are operating within accepted error rates.</p> <p>The ballot counting method used is often determined by legal provisions. For example, the <a href="https://laws-lois.justice.gc.ca/eng/acts/E-2.01/index.html"><em>Canada Elections Act</em></a> requires ballots cast during federal elections to be hand-counted, while some provinces, territories and municipalities have changed local laws to allow the use of electronic vote tabulators in their local elections.</p> <p>At a high level, a typical ballot counting and tabulation process includes the following activities:</p> <ul><li>validating each ballot</li> <li>sorting and counting valid or invalid (spoiled) cast ballots</li> <li>aggregating valid cast ballots for each candidate</li> <li>generating a tabulated summary from tallied ballots</li> </ul><p>Note that the transmission of election outcomes is considered a separate process, as this may require additional system components for transmitting and sharing that information. Results aggregation may also require additional collation at a central facility before official results are released.</p> <p>The following are some methods that may be used to tabulate ballots during elections.</p> <h3 class="h4">Manual counting and tabulation</h3> <p>In this method, elections officials manually sort, validate, and count casted paper ballots. All activities are done by hand, including generating election results tables. As noted by Elections Canada in the <a href="https://www.elections.ca/content.aspx?section=res&amp;dir=pub/ecdocs/rom/vIII/ch_2&amp;document=ch_2&amp;lang=e">Returning Officer’s Manual</a>, in Canadian federal elections, ballots are counted manually at polling stations, and preliminary results are then transmitted (often by telephone) to Elections Canada .</p> <p>For elections where a different tabulation method is primarily used (e.g. provincial or municipal elections), manual ballot counting and tabulation are commonly used as a fallback measure. Manual ballot counting and tabulation are also used to perform election audits. Manually counting and tabulating ballots can be tedious and time-consuming, especially for polling stations with higher voter density. While manual counting processes may provide a greater degree of trust due to their inherent simplicity and easier security auditability, they may allow for human subjectivity and errors.</p> <h3 class="h4">Electronic counting and tabulation</h3> <p>This method involves using electronic vote tabulators to sort, validate, and count election ballots. This method can be used to count both paper and digital ballots. Paper ballots are fed into and analyzed by the device while digital ballots are captured and processed. Electronic vote tabulators may have built-in printing capabilities or may support connectivity with external printers. Note that any external or peripheral devices connected to a vote tabulator must adhere to the same security control standards as the vote tabulator system. We recommend maintaining independence between the counting system and the ballot creation system so that a threat or attack against one does not impact the other.</p> <h3 id="3.1">Types of vote tabulators</h3> <p>There are different types of vote tabulators, often defined by their function, capabilities, and use cases.</p> <h4>Unit vote tabulators</h4> <p>These are digital scan machines that read and record ballots at a polling station. They are designed for light use only. They may or may not contain additional programmable capabilities which can assist with ballot validation, sorting, calculations, and local results processing.</p> <h4>Central tabulators</h4> <p>These are devices used to process ballots at a central location. They are typically industrial-sized and designed to process large amounts of ballots. They can also be used to rapidly perform large-scale recounts or to process mail-in ballots.</p> <h4>Optical scan tabulators</h4> <p>These are optical scan readers commonly used to help process marked paper ballots. These scanners rely on optical character recognition (OCR) or optical mark recognition (OMR) technology to read ballots. The scanner generates a digital representation of the original ballot which can then be used for additional processing. Optical scan systems are often used to process mail-in ballots.</p> <h2 id="4">Threat analysis</h2> <p>The Cyber Centre periodically releases an assessment of <a href="/en/guidance/cyber-threats-canadas-democratic-process-2025-update">Cyber threats to Canada’s democratic process (TDP)</a>. In its most update, the Cyber Centre assesses that democratic processes across the globe remain a target of interest for cyber threat actors and that the likelihood for state-sponsored cyber actors to target Canadian elections is <strong>almost certain</strong>. Vote tabulation systems may certainly introduce new vulnerabilities within the electoral process and may become a target for motivated, state-sponsored threat actors. Election agencies should conduct detailed threat and risk assessments to ensure that they understand the risks associated with using these systems and that vote tabulator systems are protected against such threats.</p> <p>Threat actors often seek to undermine public confidence in the legitimacy of the democratic process. According to the 2025 <abbr title="Cyber threats to Canada’s democratic process">TDP</abbr> report, state-sponsored actors may attempt to weaken trust by altering content on devices used during the elections process. Threat actors can infiltrate and compromise the supply chains used to procure vote tabulator devices. They can also launch disruptive attacks against these devices to render them inoperative, thereby impacting the smooth conduct of elections. Malicious actors can use targeted misinformation or disinformation campaigns to spread inaccuracies about the operation of vote tabulator devices, thereby undermining voter trust and confidence.</p> <p>State-sponsored threat actors have conducted numerous attacks against electoral systems and processes in recent years. For example, Ukraine, Estonia, Ecuador, and even the <abbr title="United Kingdom">UK</abbr>, have been targeted. Some of the attack vectors have included deploying disruptive malware on servers used to tabulate votes and planting fake results with the intention of releasing them publicly.</p> <p>Based on the prevailing threat environment, it is very likely that cybercriminals and state-sponsored actors will target ballot counting and tabulation processes to achieve their overall objectives. The following are ways threat actors could launch attacks and target ballot counting and tabulation systems:</p> <ul><li>taking over vote tabulation systems for the purpose of altering the results</li> <li>infiltrating device or systems-component manufacturers to compromise the supply chain for ballot counting and tabulation devices</li> <li>compromising elections record databases, resulting in unauthorized disclosure of confidential electronic voter records and undermining confidence in the democratic process</li> <li>disrupting vote tabulation system functions through exhaustion and destruction attacks such as distributed denial of service (DDoS) and ransomware attacks</li> <li>impersonating elections authorities to spread misinformation or falsehoods about the integrity of the process or devices to sow mistrust and erode confidence in the democratic process</li> <li>compromise privileged credentials to gain access to back-end systems to alter tabulation records or trigger further disruptive attacks</li> </ul><div class="clearfix"> </div> <div class="pull-right small text-muted mrgn-bttm-0"><a href="#wb-tphp">Top of page</a> <span aria-hidden="true" class="text-primary glyphicon glyphicon-circle-arrow-up"></span></div> <h2 id="5">Security control considerations</h2> <p>In this section, we highlight important security controls you should consider when acquiring, deploying, and operating vote tabulation systems. These recommendations are aligned with the Cyber Centre’s <a href="/en/guidance/cyber-security-privacy-risk-management/itsp10033">Cyber security and privacy risk management: A lifecycle approach (ITSP.10.033)</a>. Election administrators should consider foundational system design and security principles to safeguard hardware, firmware, software components, and related processes.</p> <h3 id="5.1">Physical and hardware security</h3> <p>Physical layer protections in vote tabulator systems are critical in ensuring that other security controls can be trusted, and that the entire system operates as intended. Vote tabulators must be designed, manufactured, operated, and decommissioned in accordance with secure by design principles to better protect them against threats, such as supply chain compromise during any stage of its lifecycle.</p> <h4>Design systems to withstand physical and environmental hazards</h4> <p>Vote tabulators should be designed for operational resilience . The devices, storage media, and other system components should be able to withstand physical and environmental hazards, such as physical shocks, high humidity, and temperature fluctuations, to protect against data loss. These devices should also have an emergency power supply; an intelligent back-up power system will also allow for graceful power-down processes. It is important to protect devices and their electronic data from power surges and outages. We also recommend having electromagnetic shielding and tamper-evident seals as feature considerations.</p> <h4>Manufactured for purpose</h4> <p>Vote tabulators should be manufactured for a single purpose to ensure security functions are operating within defined security boundaries. Single purpose systems avoid the complexity associated with multi-use designs, while also ensuring system functions are strictly defined and security restrictions can be adequately enforced. General-purpose or multi-use systems extend the attack surface, providing additional opportunities for the adversary to compromise. We recommend that vote tabulators should be purpose-built and dedicated, single-use systems.</p> <h4>Operate systems with strict physical access controls</h4> <p>When deploying and operating vote tabulators, you should implement strict physical access controls. Only authorized individuals on approved access lists should have physical access to the devices before, during, and after elections. The locations where these devices are stored, deployed, or transported throughout their lifecycle should be monitored, and mechanisms should be in place to detect and deter unauthorized access. When choosing where to deploy vote tabulators, you should consider how you will secure them from unauthorized observation and access. Device screens should be set up to prevent on-screen information from being read or observed from a distance. Electoral management bodies (EMBs) should maintain access records for each device throughout its lifecycle, from acquisition to decommissioning.</p> <h4>Monitor systems and maintain strong chain of custody records</h4> <p>Maintaining chain of custody records plays a significant role in ensuring the physical and logical integrity of the vote tabulators. Elections administrators should implement rigorous chain of custody practices to prevent tampering and other malicious device alterations. The following are some ways of protecting vote tabulators and the data contained therein.</p> <ul><li>Record all vote tabulator devices movement and access throughout their lifecycles</li> <li>Use tamper-evident seals</li> <li>Transport vote tabulators in secure containers to and from polling centres</li> <li>Document and verify chain of custody when transporting vote tabulators</li> <li>Protect and authenticate all physical access to vote tabulation equipment</li> <li>Review security monitoring controls before, during, and after elections to validate their effectiveness</li> <li>Decommission devices when chain of custody records cannot be securely validated</li> </ul><p>Device decommissioning procedures must ensure devices are cryptographically sanitized before disposal or destruction. Use only approved sanitization methods appropriate for the device media and use-case. Some sanitization methods are not effective or suitable on some media types. For example, solid-state drives (SSD) require at least a double overwrite pass and a secure erasure (SE) to achieve the sanitization objectives. For more information on Cyber Centre recommended guidance, refer to <a href="/en/guidance/it-media-sanitization-itsp40006">IT media sanitization (ITSP.40.006)</a>.</p> <h3 id="5.2">Lifecycle security</h3> <p>Democratic processes may be vulnerable to planned, persistent threats because of system lifecycle risks. In the context of information technology (IT) security risk management, “lifecycle” refers to the design/development, acquisition, integration/installation, operation, monitoring, maintenance, and disposal of <abbr title="information technology">IT</abbr> assets which, for the purposes of this guidance, include electronic vote tabulators. Examples of lifecycle risks to electronic vote tabulators include procuring them through unsecure supply chains or having them designed or developed by unverified or untrusted manufacturers. Therefore, you should keep security in mind at every stage of a vote tabulator’s lifecycle and address and mitigate potential risks that could allow threat actors to compromise the integrity of an election.</p> <h4>Acquire devices through trusted supply chains</h4> <p>Vote tabulation systems typically contain millions of individual micro-components, as well as component sub-systems such as an image scanner unit, a paper ballot verification unit, device firmware or software, power systems, data storage units, and others. Threat actors can infiltrate supply chains to compromise the security of these devices and systems. The complexity of modern system lifecycles makes it difficult for commercially available systems to guarantee protection against supply chain embedded compromises. As a result, organizations should assume such compromises may exist on their device. We recommend adopting strategies to assess and mitigate supply chain-related risks by following the <a href="/en/guidance/cyber-supply-chain-approach-assessing-risk-itsap10070">Cyber Centre’s approach to assessing cyber supply chain risks</a>.</p> <p>Elections officials should source vote tabulators and system components through trusted supply chains and physically inspect the devices before and after acquiring them, as well as before, during and after elections. Vote tabulators should have tamper-evident seals, tape, or security labelling to aid the detection of unauthorized physical access or unauthorized changes to hardware or physical system components.</p> <p>Elections administrators should establish secure procurement procedures to limit the potential for threat actors to infiltrate supply chains. The following are some actions that could ensure the security of the vote tabulator infrastructure supply chain:</p> <ul><li>Establish a supply chain risk management (SCRM) program to assess risks associated with procurement processes <ul><li>Assess and vet all technology suppliers to ensure underlying processes and relationships are secure</li> <li>Periodically assess suppliers and their cyber security practices</li> </ul></li> <li>Ensure that only trusted and vetted supplier personnel have access to sensitive electoral and system data throughout the system development lifecycle</li> <li>Collaborate with technology vendors to ensure verification processes are in place <ul><li>Ensure that the components of vote tabulators are genuine and have not been compromised through third-party relationships</li> <li>Specifically, work with vote tabulator manufacturers to implement tools to validate the integrity of hardware, firmware, and software running on tabulation devices</li> </ul></li> <li>Election agencies can also request information on detailed Hardware Bill of Materials (HBOM) or Software Bill of Materials (SBOM) to adequately track vulnerability risks associated with hardware and software components</li> </ul><p>For more information on supply chain cyber security, read <a href="/en/guidance/supply-chain-threats-and-commercial-espionage">Supply chain threats and commercial espionage</a> and <a href="/en/guidance/supply-chain-security-small-and-medium-sized-organizations-itsap00070">Supply chain security for small and medium-sized organizations (ITSAP.00.070)</a>.</p> <h3 id="5.3">Continuous risk assessment</h3> <p>Electoral management authorities should conduct a comprehensive risk analysis of the use of vote tabulators and understand the potential impact on the security of the entire electoral process. Assessing the risks of using vote tabulators should not be done in isolation.</p> <h4>Ascertain the risks associated with using vote tabulation systems</h4> <p><abbr title="electoral management bodies">EMBs</abbr> should consider technology in elections from a risk-management approach. While vote tabulators may offer opportunities for improving elections operations, it is important to understand the associated risks, which then may be mitigated, accepted, or avoided. Transferring the risk is not acceptable, as a compromise of a democratic process can have substantial reputational impacts. <abbr title="electoral management bodies">EMBs</abbr> should also avoid using vote tabulators if they are unprepared or unwilling to accept the associated risks. For more information on evaluating and managing risk, please consult our guidance <a href="/en/guidance/cyber-security-privacy-risk-management/itsp10033">Cyber security and privacy risk management: A lifecycle approach</a> and Security risk assessment for online voting systems supporting democratic processes (ITSM.10.103)</p> <h3 id="5.4">Protect your data</h3> <p>Electronic vote tabulators process, create, and store ballot data. Data is a critical asset for any business process, and especially for democratic processes that rely on digital systems. Therefore, you should have security mechanisms in place to protect the confidentiality, integrity, and availability of all forms of data, whether it is stored on the tabulation device or is in transit for processing.</p> <h4>Establish a holistic data security strategy</h4> <p>A holistic election data security strategy should be established to govern and secure electoral data throughout its lifecycle. This strategy should include data policies, acceptable handling procedures, and guidelines for managing data on vote tabulators. Data security policies may include recommendations on storage media types, secure data processing mechanisms, cryptographic standards, storage data formats, and data encryption. You may also consider performing a data security assessment to identify all data flows, paths, inputs, and outputs to and from the vote tabulator. However, there is no fully secure way to connect vote tabulators to electronic networks. Your data security strategy should address how to secure vote tabulator data throughout its lifecycle, from creation to destruction. For example, it should address how you plan to secure physical and digital ballots, restrict and manage access, enforce data encryption, and ensure compliance with legal requirements wherever your data may reside.</p> <h4>Appropriately classify data</h4> <p>Data classification represents a crucial component upon which many other security activities rely, especially when identifying appropriate security control mechanisms to protect the data. Data on vote tabulators typically exists at different classification levels and the choice of safeguards or security controls should take this into account. The vote tabulation system should be designed based on the highest classification of data or system components. For example, vote tabulators may be required to process cryptographic keys and data validation certificates may be used to encrypt and validate the integrity of election data.</p> <p>Cryptographic keys represent highly sensitive data and may necessitate higher data classification. The vote tabulation system must be designed to implement security controls at the highest level determined. For more information on data classification assessments, read our publication <a href="/en/guidance/cyber-security-privacy-risk-management/itsp10033">Cyber security and privacy risk management: Security and privacy controls and assurance activities catalogue (ITSP.10.033)</a>.</p> <p>Classifying data properly, together with implementing matching secure handling controls, can reduce the risk of a data compromise. Elections authorities should put processes in place to ensure that assets are only accessible to users on a ‘need to know’ basis and that electoral systems are only accessed using devices with the appropriate security authorization. Furthermore, only authorized devices should be used for processing and disseminating of elections-related data.</p> <h4>Protect data with cryptographic controls</h4> <p>Vote tabulator data should be protected with cryptographic mechanisms whether it is at rest or in transit (including on portable devices). Ballot data and vote counts should be secured against unauthorized disclosure and integrity attacks prior before and after they are officially released through authorized channels. Encryption can help protect data from unauthorized disclosure and modification. You should identify where the data resides at various points and then ensure you apply appropriate security controls to mitigate the risk of unauthorized use or disclosure. We recommend using only approved cryptographic algorithms and protocols. For more information on recommended cryptographic algorithms, read <a href="/en/guidance/cryptographic-algorithms-unclassified-protected-protected-b-information-itsp40111">Guidance on cryptographic algorithms for Unclassified, Protected A, and Protected B information (ITSP.40.111</a>). Maintaining a secure cryptographic key management system is important. Ensure you securely manage when, how, and where your encryption keys are created, stored, and destroyed. Implement a secure backup procedure for encryption keys to enable data recovery.</p> <h4>Consider data privacy protections</h4> <p>In Canada, election data is subject to privacy laws, including the <a href="https://laws-lois.justice.gc.ca/eng/acts/P-21/"><em>Privacy Act</em></a>. These laws mandate that a minimum set of security controls, such as data encryption and access management controls, be implemented to protect information about the voting public and ballots. We recommend you implement appropriate data privacy protections for ballots and voters’ information. The <a href="https://laws-lois.justice.gc.ca/eng/acts/E-2.01/index.html"><em>Canada Elections Act</em></a> requires Elections Canada to share voting data, including elections results, with political parties and provincial governments. Vote tabulators must be evaluated to ascertain compliance and alignment with ballot secrecy and privacy laws. Data residency considerations should also be evaluated, as election laws may require data (in-transit or at rest) to reside within specific geographical boundaries.</p> <div class="clearfix"> </div> <div class="pull-right small text-muted mrgn-bttm-0"><a href="#wb-tphp">Top of page</a> <span aria-hidden="true" class="text-primary glyphicon glyphicon-circle-arrow-up"></span></div> <h3 id="5.5">Network isolation safeguards</h3> <p>Due to the threat environment and the associated risks posed by state-sponsored threat activity, we recommend that you do not connect vote tabulators to any network at any time. Prior to elections, vote tabulators should be configured without any network connectivity, including Bluetooth and Wi-Fi, and should never be connected to the Internet at any point of their lifecycle. Data should be transferred to and from vote tabulators using non-network procedures, such as trusted portable storage devices or paper-based procedures.</p> <p>Strict network isolation (airgaps) is the most effective means of mitigating pre-existing compromises that may have been introduced through lifecycle attacks. Network isolation greatly increases the amount of effort required to gain remote command and control of a compromised system and forces an adversary to activate or control the compromised vote tabulator or related system through an alternative data channel, such as acoustic, or through procedural means, such using a compromised systems administrator. Certain serious attacks, like “logic bombs” that autonomously activate based on pre-set conditions, could remain on the system even without network connectivity, but the scope and sophistication of the possible attacks is much smaller without network command and control.</p> <h4>Establish strict network defences</h4> <p>Although deploying vote tabulators on a network is not recommended, elections administrators may still choose to deploy these systems on a network. In such cases, the network infrastructure supporting vote tabulators should be protected against interception, unauthorized data disclosure, modification, and denial of service attacks. You should implement measures to protect against ransomware attacks that may target the tabulation systems. You should track vulnerabilities and fully patch all devices before deploying them for elections. The following are some actions that you can take to implement a defence-in-depth or layered defensive approach to protecting your networks from threat actors.</p> <ul><li>Use firewalls or network zoning protections to restrict network access to sensitive assets on the network</li> <li>Consider deploying network threat detection/protection systems to mitigate network-based attacks</li> <li>Update network devices regularly to minimize exposure to vulnerabilities</li> <li>Harden network devices by disabling unnecessary services, ports, protocols and applications</li> <li>Avoid connecting vote tabulators to public or untrusted networks</li> <li>Disable Internet connectivity on vote tabulators or interconnected systems</li> <li>Implement protection against threats associated with third-party (vendors or partners) network connectivity</li> </ul><h3 id="5.6">Secure access controls</h3> <p>When designing and building an electronic tabulation system, it is essential to properly manage user and administrative privileges, isolate sensitive functions, and incorporate security engineering principles. User access rights should be restricted to only those required to perform assigned tasks. System functions should implement the principle of least privilege, which only gives users the set of privileges that is essential for them to perform authorized tasks. The following are some recommended actions you can take to implement secure access controls within vote tabulation systems.</p> <ul><li>Verify that all personnel with administrative access to the system at any point in the lifecycle meet the necessary personnel security requirements <ul><li>For example, some electoral systems may require that administrative access be given only to Canadian citizens with a valid security clearance</li> </ul></li> <li>Maintain formal security vetting for all personnel with administrative access throughout the lifecycle <ul><li>Require personnel security screening and background checks for personnel requiring privileged or administrative access to the election and voting infrastructure; software developers, hardware assembly technicians, program managers, and election administrators responsible for administering federal elections will require a security clearance to support the voting infrastructure</li> <li>Ensure administrative accounts are used exclusively to perform administrative tasks and that these privileges are regularly audited</li> </ul></li> <li>Employ two-person control for all interactions with vote tabulators during their lifecycle, except for the moment when individual voters cast ballots</li> <li>Do not share access credentials; ensure that each user has unique credentials to access vote tabulation systems</li> <li>Enforce the use of passphrases or strong passwords on voting systems</li> <li>Use strong authentication protocols and never store passwords in plain text</li> <li>Protect authentication parameters with modern hashing algorithms to provide resilience against cryptographic attacks</li> <li>Require multi-factor authentication (MFA) mechanisms for administrative access to vote tabulation systems</li> </ul><p>For more information on account and access management, read <a href="/en/guidance/best-practices-passphrases-and-passwords-itsap30032">Best practices for passphrases and passwords (ITSAP.30.032)</a>, <a href="/en/guidance/secure-your-accounts-and-devices-multi-factor-authentication-itsap30030">Secure your accounts and devices with multi-factor authentication (ITSAP.30.030)</a>, and <a href="/en/guidance/top-10-it-security-actions-no3-managing-controlling-administrative-privileges-itsm10094">Top 10 <abbr title="information technology">IT</abbr> security actions: No. 3 Managing and controlling administrative privileges (ITSM.10.094)</a>.</p> <h4>Lock down devices</h4> <p>Elections administrators should ensure that the configuration and security settings shipped with vote tabulators are updated to align with organizational policies. Elections administrators should also consider taking the following actions to lock down vote tabulators:</p> <ul><li>Restrict the services enabled on the systems and devices, and prevent users from creating or changing system settings or configurations <ul><li>Only enable services that are required for performing intended tasks</li> </ul></li> <li>Disconnect external devices, such as printers, fax systems, and computing devices, from voting tabulators when they are not in use</li> <li>Restrict access to any existing auxiliary or data ports <ul><li>If there is an operational need to enable these ports, it should be evaluated through a risk assessment review process</li> </ul></li> </ul><h3 id="5.7">Validate and authenticate devices</h3> <p>It is important to implement robust authentication mechanisms to ensure that vote tabulation devices remain trusted. Consider mechanisms to continuously validate and authenticate the integrity of vote tabulators through their lifecycle. For example, confirm the validity of trusted public key infrastructure (PKI) digital signatures on software packages. Elections administrators should consider software logic and accuracy testing to validate that the vote tabulators operate as expected. Using device cryptographic certificates can also help with physical device certification.</p> <h3 id="5.8">Patches and system updates</h3> <p>It is essential to undertake regular patch management to protect the vote tabulator against known and unknown threats. You should also implement the following measures:</p> <ul><li>Ensure device firmware and software are kept up to date</li> <li>Apply device patches and software updates regularly</li> <li>Use cryptographic mechanisms to verify firmware and software before applying updates</li> <li>Validate that update deployment cycles do not operationally impact scheduled election events</li> </ul><h3 id="5.9">Secure application development</h3> <p>Elections administrators may require software application development or procurement to meet specific legal or bylaw requirements. Security considerations should be evaluated throughout all phases of the development or procurement process. Regardless of the software application acquisition model selected, security requirements should be clearly defined and documented to assess functional and security objectives. Threat modeling or threat assessment techniques can also be used to identify and address potential threats associated with software applications to be deployed on the vote tabulator. Modern software stacks are so complex that lifecycle compromises should be assumed. Elections agencies can reduce their attack surface by identifying and managing risks early during the application design stage and architect to adequately mitigate those risks.</p> <h4>Software application testing</h4> <p>Static and dynamic testing approaches may be used to test the security of system software. Static testing involves source and binary code testing, while dynamic testing involves testing the application in functional use. Your software assurance process should allow you to evaluate applications in a test environment. Adopt functional and penetration testing controls to validate security objectives and address all identified vulnerabilities. Do not assume that an application has been vetted; instead, conduct your assessment in line with your security objectives. Leverage formal testing standards such as those defined by <a href="https://www.cyber.gc.ca/en/tools-services/common-criteria">Common Criteria</a>, <a href="https://owasp.org/www-project-application-security-verification-standard/">OWASP Application Security Verification Standard (ASVS)</a>, and <a href="https://www.iso.org/obp/ui/en/#iso:std:iso-iec:27034:-1:ed-1:v1:en">ISO/IEC 27034-1 Information technology — Security techniques ― Application security</a>.</p> <h3 id="5.10">Audit log monitoring</h3> <p>Enable event and log collection capabilities on the vote tabulator to assist with incident investigations. Activity events should be logged in protected storage, like write-once media, and retention of log data should adhere to legal and privacy regulations. Make sure to coordinate logging activities with incident response and forensic objectives to ensure that the activity logs collected contain the information needed to investigate incidents.</p> <h3 id="5.11">Business continuity</h3> <p>You should establish and test business continuity plans and procedures to ensure your election activities can recover from adverse events. Business planning should identify which data must be backed up and establish testing and recovery procedures for your back-ups. In addition, you should consider which combination of onsite or offsite back-up options best meet your needs. Back-ups require the same security protections as actual devices, including physical security, network isolation, controlled access, and two-person-control.</p> <p>For more information on business continuity planning, read <a href="/en/guidance/developing-your-business-continuity-plan-itsap10005">Developing your business continuity plan (ITSAP.10.005).</a> For more information on back-ups, read <a href="/en/guidance/tips-backing-your-information-itsap40002">Tips for backing up your information (ITSAP.40.002)</a>.</p> <p>For live elections, ensure you have contingency procedures and can quickly recover from unplanned events such as vote tabulator failures or theft. You should secure access to and encrypt sensitive data back-ups. You should also back up encryption keys, security certificates and credentials to facilitate recovery when required and disconnect external storage when not in use to minimize the likelihood that back-up data will be corrupted.</p> <h4>Retain paper backups</h4> <p>When designing elections processes that use vote tabulators, it is important that administrators consider resilient solutions to protect against disruption attacks and electronic manipulation. While keeping electronic data back-ups is a critical step in enabling quick recovery from unplanned incidents, paper records or copies of voter ballots and tabulated results should be maintained. If a catastrophic incident impacts the functioning of electoral systems, paper records will ensure the democratic process can proceed.</p> <h4>Plan for incidents and recovery</h4> <p>Security incidents may still occur even if you implement the best cyber security. Elections administrators should be prepared to deal with and recover from cyber security compromises. Have an incident recovery plan in place which outlines roles and responsibilities of all stakeholders. Test your plan regularly to assure its effectiveness. Electoral processes that rely on electronic systems should have manual and off-the-grid back-up measures that can be deployed should electronic systems fail.</p> <p>For more information on incident response and recovery planning, read <a href="/en/guidance/developing-your-incident-response-plan-itsap40003">Developing your incident response plan (ITSAP.40.003)</a> and <a href="/en/guidance/developing-your-it-recovery-plan-itsap40004">Developing your <abbr title="information technology">IT</abbr> recovery plan (ITSAP.40.002)</a>.</p> <h3 id="5.12">Educate users</h3> <p>Educating elections staff and volunteers about cyber security risks is critical for maintaining the safe operation of vote tabulators. Frontline elections staff and volunteers should be trained on how their actions could help facilitate or thwart a cyber security attack. Ensure elections staff receive regular training to understand the threat environment. Training and awareness programs should target all users of electoral systems. You should also periodically evaluate the effectiveness of your training programs and ensure the content is aligned with threat assessment feedback and addresses key threat issues.</p> <p>For more information on tailored cyber security training, read <a href="https://www.cyber.gc.ca/en/guidance/top-10-it-security-actions-6-provide-tailored-cyber-security-training-itsm10093">Top 10 <abbr title="information technology">IT</abbr> security actions: No. 6 Provide tailored cyber security training (ITSM.10.093)</a>.</p> <h4>Personnel security</h4> <p>An effective security screening process for your staff and volunteers is crucial. Implement a personnel and volunteer screening process to ascertain and validate the integrity of people recruited to work as poll staff or elections officials. Conduct security background checks before employees and volunteers are hired. Ensure the screening process continuously assesses the suitability of employees or volunteers even as they change roles or positions.</p> <p>To limit the possibility of foreign legal compulsion, only Canadian citizens with the appropriate security clearance should be granted administrative access to the vote tabulation system during any phase of its system lifecycle.</p> <h3 id="5.13">Security control effectiveness</h3> <p>Assessing and testing the effectiveness of security controls deployed on vote tabulators is an important step in ensuring systems are functioning as expected and will be resilient against real-world attacks. Elections administrators can leverage controlled testing strategies such as procedural or physical penetration testing and threat modelling techniques. In addition, the following are some other measures that can help ensure that security controls remain effective:</p> <ul><li>Automating assessment measures to continuously validate that operational, technical, and management control measures are functioning as expected</li> <li>Identifying relevant security, operational and performance metrics that should be evaluated</li> <li>Assessing the cyber resiliency capabilities of the system to withstand disruptive events such as a logic bomb</li> </ul><div class="clearfix"> </div> <div class="pull-right small text-muted mrgn-bttm-0"><a href="#wb-tphp">Top of page</a> <span aria-hidden="true" class="text-primary glyphicon glyphicon-circle-arrow-up"></span></div> <h2 id="6">Conclusion</h2> <p>Vote tabulation devices provide electronic capabilities that can enable and enhance the democratic process and increase efficiency. However, potential threats to vote tabulators, such as disruptions or altered data, can negatively impact trust in the democratic process. The applications and deployment architecture of these systems must therefore be carefully considered. To lessen the impact of potential attacks when deploying and using vote tabulators, elections management bodies should adopt a rigorous focus on security, including appropriate control protections.</p> <p>Elections administrators must adopt a data-centric strategy which implements security controls across the data path to secure voting systems. They should ensure that vote tabulators used during democratic elections are validated and that appropriate security protections are in place. Elections administrators should further ensure that the integrity of software, firmware, and hardware deployed in tabulation devices is validated, and should continuously protect these devices and systems throughout their entire lifecycle.</p> <hr><h2>Effective date</h2> <p>This publication takes effect on August 6, 2026.</p> <p>This is an <span class="text-uppercase">UNCLASSIFIED</span> publication that has been issued under the authority of the Head of the Canadian Centre for Cyber Security (Cyber Centre). For more information, contact the Cyber Centre:</p> <ul><li>by email: <a href="mailto:contact@cyber.gc.ca">contact@cyber.gc.ca</a></li> <li>by phone: <a href="tel:+1-613-949-7048">613-949-7048</a>or <a href="tel:+1-833-292-3788">1-833-CYBER-88</a></li> </ul></div> </div> </div> </div> </div> </article>

2026/8/6
阅读更多

How the Canadian Centre for Cyber Security used frontier AI to accelerate detection engineering

Discover how CSE's Frontier AI Lab is exploring the ways artificial intelligence can strengthen cyber defence, beginning with detection engineering.

2026/8/5
阅读更多

Protect your organization from malware - ITSAP.00.057

<article data-history-node-id="705" about="/en/guidance/protect-your-organization-malware-itsap00057" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><div class="row "> <div class="col-md-4 pull-left hidden-xs hidden-sm"> <p class="text-left"><strong>August 2026</strong></p> </div> <div class="col-md-4 hidden-xs hidden-sm"> <p class="text-center"><strong>Awareness series</strong></p> </div> <div class="col-md-4 pull-right hidden-xs hidden-sm"> <p class="text-right"><strong>ITSAP.00.057</strong></p> </div> <!--MOBILE STARTS HERE--> <div class="hidden-lg hidden-md text-center"> <p><strong>August 2026 | Awareness series</strong></p> </div> </div> <div class="clearfix"> </div> <p>Malware, also known as malicious software, is used by threat actors to compromise networks, systems and devices. When malware infects an organization, threat actors may be able to gain access to sensitive information, monitor activity and disrupt operations.</p> <p>This publication outlines common types of malware, the warning signs of an infected device and the steps to take when a device is compromised. It also provides practical tips to help protect your organization from future threats.</p> <section><h2>On this page</h2> <ul><li><a href="#1">How malware is introduced</a></li> <li><a href="#2">Malware types and behaviour</a></li> <li><a href="#3">How artificial intelligence is transforming malware</a></li> <li><a href="#4">Signs of an infected device</a></li> <li><a href="#5">Steps to address infected devices</a></li> <li><a href="#6">Tips to protect against malware</a></li> <li><a href="#7">Learn more</a></li> </ul></section><h2 id="1">How malware is introduced</h2> <p>Malware can enter a network, system or device through vulnerabilities or risky actions. The following examples highlight common ways in which users might inadvertently introduce malware into systems and devices.</p> <h3>Downloads and files</h3> <ul><li>Opening malicious email attachments</li> <li>Downloading software, apps or updates from untrusted sources</li> <li>Downloading or sharing files through peer-to-peer or unofficial file-sharing platforms</li> <li>Connecting unverified or unscanned removable media (for example, USBs or external drives)</li> </ul><h3>Browsing and access</h3> <ul><li>Clicking deceptive pop-ups, ads or fake warnings</li> <li>Installing unauthorized browser extensions or toolbars</li> <li>Visiting unsafe or compromised websites</li> <li>Using unsecured or untrusted Wi-Fi networks</li> </ul><h3>Device and account security</h3> <ul><li>Using outdated, unsupported or unpatched software or devices</li> <li>Using weak, default or reused passwords</li> </ul><h2 id="2">Malware types and behaviour</h2> <p>Malware appears in many forms, each designed to exploit systems in different ways. Understanding the different types of malware can help you detect malicious activity early and respond with confidence. Malware can be described by how it spreads and what it does once it is running. A single attack may involve more than one method and more than one capability.</p> <h3>How malware spreads</h3> <p>Malware can spread through different techniques that allow it to install itself and move between systems or networks. The types below describe how malware gains access and propagates.</p> <ul><li><strong>Trojan horse:</strong> disguises itself as harmless software to persuade users to install it, enabling unauthorized access or harmful actions</li> <li><strong>Virus:</strong> infects files and spreads to other systems through user actions, such as opening or sharing infected files</li> <li><strong>Worm:</strong> executes independently and self-replicates, usually through network connections, to cause damage such as deleting files, sending unauthorized emails or taking up bandwidth</li> </ul><h3>What malware can do</h3> <p>Once malware is running, it may perform a range of harmful actions that affect systems, data or users. The malware types below describe the impact or effects of malware on infected devices.</p> <ul><li><strong>Adware:</strong> tracks Internet activity to deliver targeted pop-up advertisements <ul><li>it is often installed without user consent through bundled software or malicious websites</li> <li>it may redirect browsing traffic or collect user data</li> </ul></li> <li><strong>Browser hijacker:</strong> manipulates browser settings to redirect users to unwanted websites or ads, often changing the homepage, modifying search defaults or adding unauthorized toolbars</li> <li><strong>Botnet:</strong> connects a network of infected devices (called "bots" or "zombies")</li> <li><strong>Cryptojacking:</strong> hijacks a device's processing power to mine cryptocurrency without the owner's knowledge, often causing significant slowdowns and overheating</li> <li><strong>Logic bomb:</strong> triggers malicious actions on a system when specific conditions are met, such as a particular date, time or user action, and often remains hidden until activated</li> <li><strong>Rootkit:</strong> grants hidden access to networks, systems or devices by masking itself as a legitimate operating system (OS) component. <ul><li>it frequently embeds itself deep within OS components or firmware to avoid detection</li> </ul></li> <li><strong>Ransomware:</strong> denies access to data or systems, typically by encrypting data and withholding the decryption keys until payment is made to the threat actor</li> <li><strong>Spyware:</strong> designed to monitor user activity and collect sensitive information, including browsing data, login details or personal information. Common types of spyware include: <ul><li><strong>information stealers:</strong> extract sensitive data from a device, including user credentials, browser history, browser session cookies and tokens, autofill information such as saved payment card details, communication logs, documents, system information, and even screenshots</li> <li><strong>keyloggers:</strong> capture and record keystrokes so threat actors can obtain sensitive information such as passwords, personal data or financial information <ul><li>they often operate within the OS or within keyboard input software to collect this information discreetly</li> </ul></li> </ul></li> <li><strong><abbr title="virtual private network">VPN</abbr>filter: </strong>compromises routers to allow threat actors to intercept traffic, harvest information, exploit connected systems and disrupt or manipulate network traffic</li> <li><strong>Wiper:</strong> destroys data by permanently erasing, overwriting or corrupting files and system components, often rendering devices inoperable and leaving little or no chance of recovery</li> </ul><h2 id="3">How artificial intelligence is transforming malware</h2> <p>Threat actors are taking advantage of artificial intelligence (AI) to make common types of malware more effective. The following sections outline the three ways <abbr title="artificial intelligence">AI</abbr> is transforming malware.</p> <h3>Method 1: <abbr title="artificial intelligence">AI</abbr>-assisted malware</h3> <p>This form of malware relies on <abbr title="artificial intelligence">AI</abbr> tools that operate outside the malware itself to assist in how attacks are developed or delivered. This can make malicious activity faster, more targeted and more convincing.</p> <p>For example, threat actors may use <abbr title="artificial intelligence">AI</abbr> to generate messages, craft malicious code, automated scanning of public information to identify valuable targets and craft tailored social engineering content designed to increase infection rates.</p> <p>Entry points include phishing emails with malicious links or attachments, downloads from compromised websites and the use of stolen or weak credentials to log into systems.</p> <h3>Method 2: <abbr title="artificial intelligence">AI</abbr>-augmented malware</h3> <p>This form of malware uses <abbr title="artificial intelligence">AI</abbr> to strengthen traditional malicious functions during execution to enhance stealth, speed or decision making. <abbr title="artificial intelligence">AI</abbr> enhances these actions but does not completely control or replace the underlying malware processes.</p> <p>For example, threat actors may use <abbr title="artificial intelligence">AI</abbr> to choose less visible routes for lateral movement, shape data exfiltration to resemble routine traffic, prioritize targets based on observed activity or automatically fine-tune tactics to avoid malware detection tools.</p> <p>Entry points include phishing emails with malicious links or attachments, exploitation of unpatched systems and misuse of remote access, which the malware then builds on using <abbr title="artificial intelligence">AI</abbr> to improve how it spreads or hides.</p> <h3>Method 3: Embedded <abbr title="artificial intelligence">AI</abbr> malware</h3> <p>This form of malware is designed with <abbr title="artificial intelligence">AI</abbr> embedded into the payload so it can analyze the system it infects and adjust its behaviour in real time. This allows it to identify targets, respond to security controls and choose actions that maximize its effectiveness.</p> <p>For example, <abbr title="artificial intelligence">AI</abbr> may be used to select high-value files to steal, alter activity when security tools are detected, adjust execution timing based on user behaviour or learn from system conditions to refine future actions (for example, self-modifying code).</p> <p>Entry points include phishing emails with malicious links or attachments and vulnerable or misconfigured Internet-facing services that allow threat actors to place the malware on a device or system.</p> <h2 id="4">Signs of an infected device</h2> <p>Malware often disrupts devices in subtle ways before the damage becomes obvious. Staying aware of the following indicators can help you identify potential threats early and protect your information effectively.</p> <h3>Changes on your device</h3> <ul><li>Pop-up windows appearing on your device</li> <li>Homepage changes</li> <li>Browser redirects, new or unknown toolbars or unexpected icons</li> </ul><h3>Performance issues</h3> <ul><li>Slow computer performance</li> <li>Page or system crashes</li> <li>Unusual or excessive hard drive activity, especially when the system is idle</li> </ul><h3>Security or software changes</h3> <ul><li>Unknown programs running on your device</li> <li>Antivirus or malware protection software being disabled</li> <li>Security settings or administrative controls being locked or altered</li> <li>Files becoming inaccessible, encrypted or renamed</li> <li>Ransom notes or payment demands appearing on the device</li> </ul><h3>Unusual account activity</h3> <ul><li>Spam emails or messages sent from your account</li> <li>Unauthorized password changes or unusual login activity</li> </ul><h3>Network and device behaviour</h3> <ul><li>High network traffic when the device is idle</li> <li>Overheating, rapid battery drain or unusual data use on your mobile device</li> </ul><h2 id="5">Steps to address infected devices</h2> <p>When a device becomes infected with malware, quick action is essential to limit damage, prevent further spread and protect sensitive information. The following steps outline current best practices to help you contain the threat, clean your device safely and restore it to a secure state.</p> <h3>Immediate actions</h3> <ul><li>Contact your information technology (IT) security service desk or <abbr title="information technology">IT</abbr> provider immediately</li> <li>Disconnect the infected device from all networks (for example, Wi-Fi, Ethernet, and mobile data)</li> <li>If malware appears to be active or spreading, power off the device to prevent further damage</li> <li>Refrain from using the infected device to sign into sensitive accounts, such as email, financial systems or administrative portals</li> </ul><h3>Containment and recovery</h3> <ul><li>Run antivirus scans offline when possible</li> <li>Restore data only from known, clean backups that were created before the infection</li> <li>Scan all backup files before restoring them to ensure they are free of malware <ul><li>Use trusted malware analysis tools, such as <a href="/en/tools-services/assemblyline">Assemblyline</a>, the Canadian Centre for Cyber Security's malware detection and analysis platform, to help assess suspicious files before restoration</li> </ul></li> <li>Reset all passwords associated with the device, revoke active sign-in sessions and access tokens and re-enrol multi-factor authentication (MFA) to prevent misuse of stolen credentials</li> </ul><h3>Post-incident monitoring</h3> <ul><li>Reconnect the device to your network only after the <abbr title="operating system">OS</abbr> is reinstalled and all malware scans confirm the device is clean</li> <li>Continue monitoring the device for unusual behaviour, suspicious traffic or new alerts</li> <li>Perform regular antivirus scans to ensure no malware remains</li> </ul><h2 id="6">Tips to protect against malware</h2> <p>Staying safe online requires more than just good habits; it requires intentional and proactive cyber hygiene. Malware threats continue to evolve, targeting personal devices, corporate systems and everything in between. By following best practices such as our <a href="/en/guidance/top-10-it-security-actions">Top 10 <abbr title="information technology">IT</abbr> security actions</a> and using trusted protective tools, you can significantly reduce your risk of compromise. The following tips outline the most effective steps you can take to strengthen your defences and help keep your information, devices and accounts secure.</p> <h3>Authentication and identity security</h3> <ul><li>Enable passkeys or phishing-resistant MFA for all accounts, choosing authentication methods that align with the sensitivity of the account and the level of risk</li> <li>Use a password manager to generate and store long, unique passwords</li> <li>Limit user and administrator access to only what is required for their roles and regularly remove excess permissions</li> </ul><h3>Device and system hardening</h3> <ul><li>Install software, <abbr title="operating system">OS</abbr> and firmware updates immediately</li> <li>Use anti-virus, anti-malware and endpoint detection and response tools</li> <li>Use a firewall to block and restrict unauthorized network access</li> <li>Enable full-disk or file-based encryption</li> <li>Use host intrusion detection systems where supported</li> <li>Use application allowlisting so only authorized apps can run</li> <li>Turn off wireless features like Wi-Fi, Bluetooth, GPS and near-field communication when not in use</li> </ul><h3>Network and Internet safety</h3> <ul><li>Avoid public Wi-Fi or use a virtual private network when public Wi-Fi is necessary</li> <li>Use anti-phishing protections and align email systems with Domain-based Message Authentication, Reporting, and Conformance (DMARC)</li> <li>Use an ad blocker to reduce risk from malicious ads or a tracker blocker and limit the collection of browsing activity information</li> <li>Verify files, links and attachments before downloading or opening them</li> <li>Provide regular security awareness training so users can recognize phishing emails, malicious links, fake websites and social engineering attempts</li> <li>Encourage users to report suspected phishing or malware quickly to reduce spread and impact</li> <li>Use a protective domain name system to prevent access to malicious or suspicious domains</li> <li>Monitor device data usage for suspicious or unusual activity</li> </ul><h3>Backup and data protection</h3> <ul><li>Follow the 3-2-1 backup rule: 3 copies, 2 types of media, 1 offsite</li> <li>Encrypt sensitive data stored in backups</li> </ul><h3>Zero-trust and enterprise controls</h3> <ul><li>Implement zero-trust architecture</li> <li>Use identity threat detection and response tools</li> <li>Strengthen supply chain security and monitor third-party risks</li> </ul><h2 id="7">Learn more</h2> <ul><li><a href="/en/guidance/ransomware-playbook-itsm00099">Ransomware playbook (ITSM.00.099)</a></li> <li><a href="/en/guidance/spotting-malicious-email-messages-itsap00100">Spotting malicious email messages (ITSAP.00.100)</a></li> <li><a href="/en/guidance/how-updates-secure-your-device-itsap10096">How updates secure your device (ITSAP.10.096)</a></li> <li><a href="/en/guidance/best-practices-passphrases-and-passwords-itsap30032">Best practices for passphrases and passwords (ITSAP.30.032)</a></li> <li><a href="/en/guidance/password-managers-security-itsap30025">Password managers: Security tips (ITSAP.30.025)</a></li> <li><a href="/en/guidance/protective-domain-name-system-itsap40019">Protective Domain Name System (ITSAP.40.019)</a></li> <li><a href="/en/guidance/preventative-security-tools-itsap00058">Preventative security tools (ITSAP.00.058)</a></li> <li><a href="/en/guidance/dont-take-bait-recognize-and-avoid-phishing-attacks">Don't take the bait: Recognize and avoid phishing attacks (ITSAP.00.101)</a></li> </ul></div> </div> </div> </div> </div> </article>

2026/8/4
阅读更多

Cyber threat bulletin: Non-state activity targeting Canadian operational technology

<article data-history-node-id="8047" about="/en/guidance/cyber-threat-bulletin-non-state-activity-targeting-canadian-operational-technology" class="cccs-basic-page full clearfix"> <div class="content"> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <div data-block-plugin-id="extra_field_block:node:cccs_basic_page:links" class="block block-layout-builder block-extra-field-blocknodecccs-basic-pagelinks clearfix"> </div> <div data-block-plugin-id="field_block:node:cccs_basic_page:body" class="block block-layout-builder block-field-blocknodecccs-basic-pagebody clearfix"> <div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"><p>The Canadian Centre for Cyber Security (Cyber Centre) has continued to observe non-state cyber threat actors targeting and attempting to disrupt vulnerable, internet-exposed operational technology (OT) systems in Canada. Non-state actors often use cyber threat activity to intimidate or coerce their targets, either to influence public opinion or government decision making related to international events.</p> <p>We assess that non-state activity against Canada very likely increases around events like public statements or policy announcements by Canada that these actors perceive as being counter to their ideological goals, and around other high-profile events, for example diplomatic summits or major international sporting events, that amplify the visibility and impact of their activity. However, we assess that some non-state actors likely continuously scan for vulnerable systems in Canada and may conduct disruptive or destructive cyber threat activity at any time.</p> <p>Although some non-state actors appear to receive support from state actors, we assess that most non-state cyber threat activity against Canadian <abbr title="operational technology">OT</abbr> systems is almost certainly independently planned and executed. Relationships between state and non-state actors are frequently ad hoc, and the degree of connection can vary over time. As such, state-aligned non-state activity should not necessarily be interpreted as representing state interests or policy toward Canada.</p> <h2>Tactics, techniques, and procedures</h2> <p>A growing number of non-state actors are targeting internet-connected <abbr title="operational technology">OT</abbr> systems intending to cause disruptive or destructive effects. These actors generally demonstrate low to moderate technical sophistication but are effective due to poor exposure hygiene and insecure remote access in <abbr title="operational technology">OT</abbr> environments.</p> <p>In October 2025 alone, there were several incidents of non-state actors affecting <abbr title="operational technology">OT</abbr> systems in Canada including:</p> <ul><li>A pro-Russia non-state actor compromised a municipal water system and successfully manipulated water pressure valve controls, causing minor impacts to water service delivery.</li> <li>A pro-Hamas non-state actor gained access to a fuel tank gauging system located at an airport. The actor was able to view system information but did not gain the ability to manipulate system controls.</li> <li>A pro-Russia non-state actor gained access to a grain drying silo's control system. The actor manipulated temperature and humidity levels within the silo, but there was no evidence that damage was caused.</li> </ul><p>This activity frequently uses publicly available scanning tools to identify internet-connected <abbr title="operational technology">OT</abbr> and exploits outdated or insecurely configured remote access tools like virtual network computing (VNC), weak or default passwords, or systems that do not use multi-factor authentication.</p> <p>After gaining access to these systems, non-state actors attempt to disrupt them by defacing system interfaces, changing configurations, and manipulating system controls. This can lead to operational disruptions, systems operating in unintended ways, and potentially physical damage to the systems. In some cases, this activity may create dangerous conditions that implicate operator or public safety.</p> <h3>Non-state actor <abbr title="operational technology">OT</abbr> <abbr title="tactics, techniques, and procedures">TTPs</abbr> mapped to <span class="text-uppercase">MITRE ATT&amp;CK</span> for <abbr title="industrial control systems">ICS</abbr></h3> <dl class="dl-horizontal"><dt>T0888 – Remote System Discovery</dt> <dd>Internet wide scanning for exposed <abbr title="operational technology">OT</abbr> systems and remote access services</dd> <dt>T0866 – Valid Accounts</dt> <dd>Exploitation of internet accessible remote access services using weak, default, or reused credentials (e.g., <abbr title="virtual network computing">VNC</abbr>, remote desktop, vendor maintenance portals)</dd> <dt>T0886 – Remote Services</dt> <dd>Use of legitimate remote services to access <abbr title="operational technology">OT</abbr> environments</dd> <dt>T0856 – Control Device Identification</dt> <dd>Direct interaction with human machine interfaces (HMIs), engineering workstations, or control system interfaces</dd> <dt>T0831 – Manipulation of Control<br> T0809 – Modify Controller Tasking</dt> <dd>Manipulation of <abbr title="operational technology">OT</abbr> system configurations and setpoints (e.g., pressure, temperature, alarms)</dd> </dl><h2>Outlook</h2> <p>The cyber threat picture facing <abbr title="information technology">OT</abbr> and <abbr title="operational technology">OT</abbr> asset operators is deteriorating. Although Canada has avoided a high-impact <abbr title="operational technology">OT</abbr> incident to date, the expanding threat surface associated with vulnerable <abbr title="operational technology">OT</abbr> deployments and the increase in threat actor capability and intent against those systems increases the likelihood that future incidents will be more severe.</p> <p>Cyber threat actors continue to adapt their activities in response to geopolitical events, technological developments, and mitigation efforts by defenders. Artificial intelligence (AI) tools capable of supporting cyber threat activity are rapidly improving and becoming increasingly available. These tools allow even low sophistication cyber threat actors to conduct more complex and disruptive attacks against <abbr title="operational technology">OT</abbr> systems.</p> <p>The cyber threat identified in this advisory can largely be mitigated through awareness and by applying cyber security best practices. The Cyber Centre encourages <abbr title="information technology">OT</abbr> and <abbr title="operational technology">OT</abbr> system owners to implement the recommended mitigation advice below.</p> <h2>Mitigations</h2> <p>The Cyber Centre recommends that critical infrastructure organizations implement the following mitigations to help establish robust cyber defences against non-state cyber threat actors. Each of the mitigations below are linked to the Cyber Centre's <a href="/en/cyber-security-readiness/cyber-security-readiness-goals-securing-our-most-critical-systems">Cyber Security Readiness Goals (CRGs)</a>, which are baseline practices for organizations to bolster their cyber security posture. Further details of each goal can be found in the <a href="/en/cyber-security-readiness/cross-sector-cyber-security-readiness-goals-toolkit">Cross-Sector Cyber Security Readiness Goals Toolkit</a>.</p> <h3>Primary mitigation</h3> <p>The most effective defence against this threat is the removal of <abbr title="operational technology">OT</abbr> systems from direct internet exposure and the establishment of a strictly controlled, monitored boundary between <abbr title="information technology">OT</abbr> and <abbr title="operational technology">OT</abbr> networks. Many of the additional controls below are compensating measures and are insufficient on their own if <abbr title="operational technology">OT</abbr> systems remain internet‑accessible.</p> <h3>Establish and protect the <abbr title="operational technology">OT</abbr> boundary and isolate administrative access</h3> <p><strong>Network segmentation (CRG 2.5)</strong></p> <ul><li>This will reduce the likelihood that threat actors will access the <abbr title="operational technology">OT</abbr> network after compromising the <abbr title="information technology">OT</abbr> network.</li> <li>All connections to the <abbr title="operational technology">OT</abbr> network are denied by default unless explicitly allowed (for example, by <abbr title="internet protocol">IP</abbr> address and port) for specific system functionality. Necessary communications paths between the <abbr title="information technology">OT</abbr> and <abbr title="operational technology">OT</abbr> networks must pass through an intermediary, such as a properly configured firewall, bastion host, jump box, or a demilitarized zone, which is closely monitored, captures network logs, and only allows connections from approved assets. <ul><li>Note that segmentation could break or disrupt processes and services as legacy <abbr title="operational technology">OT</abbr> environments are often flat. Segmentation should be done when possible, and under controlled processes.</li> </ul></li> </ul><p><strong>Prohibit connection of unauthorized devices (CRG 2.17)</strong></p> <ul><li>Maintain policies and processes to ensure that unauthorized media and hardware are not connected to <abbr title="operational technology">OT</abbr> assets, such as by limiting use of USB devices and removable media or disabling AutoRun.</li> <li>Establish procedures to remove, disable, or otherwise secure physical ports in <abbr title="operational technology">OT</abbr> environments to prevent the connection of unauthorized devices, or establish procedures for granting access through approved exceptions.</li> </ul><p><strong>Limit <abbr title="operational technology">OT</abbr> connections to public internet (CRG 2.18)</strong></p> <ul><li>Ensure no <abbr title="operational technology">OT</abbr> assets are on the public internet, unless explicitly required for operation.</li> <li>Require that exceptions be justified and documented and that excepted assets have additional protections in place to prevent and detect exploitation attempts. For example, logging, multi-factor authentication (MFA), mandatory access via proxy or another intermediary.</li> </ul><p><strong>No exploitable services on the internet (CRG 2.20)</strong></p> <ul><li>Ensure assets on the public internet do not expose any exploitable services, such as remote desktop protocol. Where these services must be exposed, implement appropriate compensating controls to prevent common forms of abuse and exploitation. Disable all unnecessary <abbr title="operating system">OS</abbr> applications and network protocols on internet-facing assets.</li> </ul><p><strong>Secure administrator workstation (SAW) (CRG 2.21)</strong></p> <ul><li>Provide administrators with <abbr title="secure administrator workstations">SAWs</abbr> to perform their administrative tasks. Create secure and hardened <abbr title="secure administrator workstations">SAWs</abbr> by implementing the following: <ul><li>Isolate <abbr title="secure administrator workstations">SAWs</abbr> from the public <abbr title="information technology">OT</abbr> network, and when present, from the data plane.</li> <li>Deactivate capability to install other software.</li> <li>Restrict access to the internet or email services.</li> <li>For cloud administration from this dedicated workstation, ensure it requires a <abbr title="virtual private network">VPN</abbr> or allow lists to access the cloud tenancy.</li> </ul></li> </ul><h3>Use strong access controls</h3> <p><strong>Changing default password (CRG 2.0)</strong></p> <ul><li>Enforce an organization-wide policy or process that requires changing default manufacturer passwords for all hardware, software, and firmware before putting them on any internal or external networks. This includes <abbr title="information technology">OT</abbr> assets for <abbr title="operational technology">OT</abbr>, such as <abbr title="operational technology">OT</abbr> administration web pages. This should be done in consultation with vendor advice and guidance or following an approved vendor process.</li> <li>Enforce a policy to change default credentials for all new or future devices. This reduces potential risk in the future if adversary <abbr title="tactics, techniques, and procedures">TTPs</abbr> change and requires significantly less work than changing default passwords on an organization's existing <abbr title="operational technology">OT</abbr>.</li> </ul><p><strong>Minimum password length (CRG 2.1)</strong></p> <ul><li>Implement a system-enforced policy that requires a minimum password length of 15 or more characters for all password-protected <abbr title="operational technology">OT</abbr> assets where technically feasible.</li> <li>OT assets that use a central authentication mechanism (such as Active Directory) are most important to address. Examples of low-risk <abbr title="operational technology">OT</abbr> assets that may not be technically feasible include those in remote locations, such as on offshore rigs or wind turbines.</li> </ul><p><strong>Unique credentials (CRG 2.2)</strong></p> <ul><li>Provision unique and separate credentials for similar services and asset access on <abbr title="operational technology">OT</abbr> networks.</li> <li>Ensure users do not and cannot reuse passwords for accounts, applications, services, etc.</li> <li>Require that service accounts/machine accounts have unique passwords from all member user accounts.</li> </ul><p><strong>Separating user and privileged accounts (CRG 2.4)</strong></p> <ul><li>User accounts do not always have administrator or super-user privileges. Administrators should maintain separate user accounts for all actions and activities not associated with the administrator role (for example, for business email, web browsing).</li> <li>Reevaluate privileges on a recurring basis to validate continued need for given permissions.</li> </ul><p><strong>Phishing-resistant multi-factor authentication (MFA) (CRG 2.7)</strong></p> <ul><li>Within <abbr title="operational technology">OT</abbr> environments, enable <abbr title="multi-factor authentication">MFA</abbr> on all accounts and systems that can be accessed remotely, including vendors/maintenance accounts, remotely accessible user and engineering workstations, and remotely accessible human-machine interfaces.</li> </ul><h3>Understand and reduce exposure</h3> <p><strong>Asset inventory and network topology (CRG 1.0)</strong></p> <ul><li>Maintain a regularly updated inventory of all assets within the organization's <abbr title="information technology">OT</abbr> (including IPv6) and <abbr title="operational technology">OT</abbr> networks (if applicable).</li> <li>Include in the inventory accurate documentation of network topology and identified data assets, in particular sensitive or classified information.</li> <li>Update this inventory on a regular basis for both <abbr title="information technology">OT</abbr> and <abbr title="operational technology">OT</abbr> and immediately log in the existing inventory any new asset that is integrated into the organization's infrastructure.</li> </ul><p><strong>Mitigate known vulnerabilities (CRG 1.1)</strong></p> <ul><li>Patch all known exploited vulnerabilities (listed in <abbr title="Cybersecurity &amp; Infrastructure Security Agency">CISA</abbr> 's Known Exploited Vulnerabilities Catalog) in internet-facing systems within a risk-informed timespan, prioritizing more critical assets first. Identify security vulnerabilities in your systems by conducting penetration tests and using automated vulnerability scanning tools, activities which are part of a comprehensive vulnerability management strategy.</li> <li>For assets where patching is not possible or may substantially compromise availability or safety, apply and record compensating controls (e.g., segmentation, monitoring). Sufficient controls either make the asset inaccessible from the public internet or reduce the ability of threat actors to exploit the vulnerabilities in these assets.</li> <li>Carefully select automated vulnerability detection tools as they can scan systems aggressively. These tools may cause devices to behave erratically, stop working/crash, or restart, or need manual intervention to revert to an operational state.</li> </ul><h3>Improve detection and response</h3> <p><strong>Detection of unsuccessful (automated) login attempts (CRG 2.6)</strong></p> <ul><li>Log all unsuccessful logins and send to an organization's security team or relevant logging system.</li> <li>Ensure security teams are notified (e.g., by an alert) after a specific number of consecutive, unsuccessful login attempts in a short period (e.g., 5 failed attempts over 2 minutes). Log and store these alerts in the relevant security or ticketing system for retroactive analysis.</li> <li>For <abbr title="information technology">OT</abbr> assets, implement a system-enforced policy that prevents future logins for the suspicious account. For example, this could be for some minimum time or until the account is re-enabled by a privileged user. Enable this configuration when available on an asset. For example, Windows 11 can automatically lock out accounts for 10 minutes after 10 incorrect logins in a 10-minute period.</li> </ul><p><strong>Log collection (CRG 2.15)</strong></p> <ul><li>Collect and store logs for use in both detection and incident response activities (e.g., forensics), including the following logs: <ul><li>access- and security-focused (e.g., intrusion detection systems / intrusion prevention systems (IDS/IDPS)</li> <li>firewalls</li> <li>data loss prevention (DLP)</li> <li>virtual private networks (VPN)</li> </ul></li> <li>Security teams are notified when a critical log source is disabled, such as Windows event logging.</li> <li>For <abbr title="operational technology">OT</abbr> assets where logs are non-standard or not available, collect network traffic and communications between those assets and other assets.</li> </ul><h3>Conduct risk assessments</h3> <p><strong>Detect relevant threat and <abbr title="tactics, techniques, and procedures">TTPs</abbr> (CRG 3.0)</strong></p> <ul><li>Document a list of threats and cyber threat actor <abbr title="tactics, techniques, and procedures">TTPs</abbr> relevant to the organization (for example, based on industry, sectors, etc.) and ensure the ability to detect instances of those key threats (for example, through rules, alerting, or commercial prevention and detection systems).</li> </ul><p>Organizations should conduct self-assessments using the <abbr title="Cyber Security Readiness Goals">CRGs</abbr> toolkit to identify gaps and track progress.</p> <h3>Develop incident response plans</h3> <p><strong>Incident response plan (CRG 1.3)</strong></p> <ul><li>Develop, maintain, update, and regularly drill <abbr title="operational technology">OT</abbr> cyber security incident response plans for both common and organization-specific threat scenarios (for example, by sector or locality) and <abbr title="tactics, techniques, and procedures">TTPs</abbr>.</li> <li>Consider engaging with appropriate stakeholders to conduct tabletop exercises focused on emerging threats such as artificial intelligence-enhanced attacks.</li> </ul><p><strong>Incident planning and preparedness (CRG 5.0)</strong></p> <ul><li>Develop, maintain, and execute plans to recover and restore to service business or mission-critical assets or systems that might be impacted by a cyber security incident.</li> <li>If a cyber incident does occur, perform a hotwash post-recovery to determine lessons learned and prevent future incidents. Integrate any lessons learned into improvements in governance processes and/or the incident response plan.</li> </ul><h3>Train staff and vendors</h3> <p><strong>Basic and <abbr title="operational technology">OT</abbr> cyber security training (CRG 2.8)</strong></p> <ul><li>Provide training that covers basic cyber security and privacy concepts, such as phishing, business email compromise, basic operational security, password security, privacy breaches, etc., and foster an internal culture of security and cyber awareness.</li> <li>Ensure that personnel who maintain or secure <abbr title="operational technology">OT</abbr> as part of their regular duties receive <abbr title="operational technology">OT</abbr>-specific cyber security training at least annually.</li> </ul><h3>Maintain backups</h3> <p><strong>System backups and redundancy (CRG 2.14)</strong></p> <ul><li>Regularly back up all systems that are necessary for operations. Determine on a case-by-case basis what systems to back up and the exact frequency since every system will have different backup and recovery requirements.</li> <li>Store backups separately from the source systems and test on a recurring basis, no less than once per year, to ensure they are usable.</li> <li>Ensure stored information for <abbr title="operational technology">OT</abbr> assets includes at a minimum: <ul><li>Configurations</li> <li>Roles</li> <li>Programmable controller (PLC) logic</li> <li>Engineering drawings</li> <li>Tools</li> </ul></li> </ul><p>These mitigations can help critical infrastructure organizations prevent non-state cyber threat actors from exploiting vulnerable systems. We encourage organizations facing a suspected cyber incident to engage with the Cyber Centre for mitigation and recovery assistance.</p> <h2>Resources</h2> <ul><li><a href="/en/guidance/national-cyber-threat-assessment-2025-2026">National Cyber Threat Assessment 2025-2026</a></li> <li><a href="/en/guidance/cyber-threat-bulletin-cyber-threat-operational-technology">Cyber Threat Bulletin: Cyber Threats to Operational Technology</a></li> <li><a href="https://www.cisa.gov/news-events/alerts/2025/05/06/unsophisticated-cyber-actors-targeting-operational-technology">Cybersecurity &amp; Infrastructure Security Agency. Unsophisticated Cyber Actor(s) Targeting Operational Technology</a></li> <li><a href="https://www.justice.gov/opa/pr/justice-department-announces-actions-combat-two-russian-state-sponsored-cyber-criminal">U.S. Department of Justice. Justice Department Announces Actions to Combat Two Russian State-Sponsored Cyber Criminal Hacking Groups</a></li> <li><a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog">U.S. Cybersecurity &amp; Infrastructure Security Agency. Known Exploited Vulnerabilities Catalog</a></li> </ul><hr><h2>About this document</h2> <p>This cyber bulletin aims to raise awareness among both information technology (IT) and operational technology (OT) system owners and operators and urges all Canadians to be vigilant of this threat. It builds on a Cyber Centre alert issued on October 29, 2025 on <a href="/en/alerts-advisories/al25-016-internet-accessible-industrial-control-systems-ics-abused-hacktivists">Internet-accessible industrial control systems (ICS) being abused by hacktivists</a>, and a <a href="https://www.cisa.gov/news-events/cybersecurity-advisories/aa25-343a">joint cyber security advisory on pro-Russia hacktivism</a> authored by the Cyber Centre and international partners in December 2025, to provide additional threat context and mitigation advice.</p> <p>For follow-up questions or issues, contact the Cyber Centre at <a href="mailto:contact@cyber.gc.ca">contact@cyber.gc.ca</a>.</p> <h3>Assessment base and methodology</h3> <p>The judgements in this bulletin rely on reporting from multiple sources, both classified and unclassified. They are based on the Cyber Centre's knowledge and expertise in cyber security. Defending the Government of Canada's information systems provides the Cyber Centre with a unique perspective to observe trends in the cyber threat environment, which also informs our assessments. The Communications Security Establishment Canada's (CSE) foreign intelligence mandate provides us with valuable insight into adversary behaviour in cyberspace. While we must always protect classified sources and methods, we provide the reader with as much justification as possible for our judgements.</p> <p>Our judgements are based on an analytical process that includes evaluating the quality of available information, exploring alternative explanations, mitigating biases and using probabilistic language. We use terms such as "we assess" or "we judge" to convey an analytic assessment. We use qualifiers such as "possibly", "likely" and "very likely" to convey probability.</p> <p>The assessments and analysis are based on information available as of <strong>January 23, 2026.</strong></p> <div class="panel panel-default col-md-12"> <div class="panel-body"> <figure><figcaption class="mrgn-bttm-md"><h3>Estimative language guide</h3> </figcaption></figure><p class="mrgn-bttm-lg">The chart below matches estimative language with appropriate percentages. These percentages are not derived via statistical analysis, but are based on logic, available information, prior judgements and methods that increase the accuracy of estimates.</p> <img alt="Long description immediately follows" class="img-responsive center-block mrgn-bttm-lg" src="https://imgproxy.citrusreader.com/_l05DaK0YeaZpdja6GZ2wPWxUfnTQnyGIaObeUeCtSQ/raw:1/aHR0cHM6Ly9jeWJlci5nYy5jYS9zaXRlcy9kZWZhdWx0L2ZpbGVzL2ltYWdlcy90YXJwLWxhbmd1YWdlLWNoYXJ0LXRyYW5zcGFyZW50LWUucG5n"><details class="brdr-tp brdr-rght brdr-bttm brdr-lft mrgn-bttm-sm"><summary>Long description - Estimative language chart </summary><ul class="list-unstyled mrgn-tp-md"><li>1 to 9% Almost no chance</li> <li>10 to 24% Very unlikely/very improbable</li> <li>25 to 39% Unlikely/improbable</li> <li>40 to 59% Roughly even chance</li> <li>60 to 74% Likely/probably</li> <li>75 to 89% Very likely/very probable</li> <li>90 to 99% Almost certainly</li> </ul></details></div> </div> </div> </div> </div> </div> </div> </article>

2026/7/30
阅读更多

Joint guidance on minimum elements for a software bill of materials

This publication updates and replaces the 2021 Minimum Elements for a Software Bill of Materials published by the United States’ National Telecommunications and Information Administration.

2026/7/29
阅读更多

Joint guidance on isolating vital systems

This joint guidance is intended to support senior decision-makers within CI organizations.

2026/7/28
阅读更多

推荐订阅