← Breach analysis by the Dual Vulnerabilities framework

Ottawa Hospital, Canadian Armed Forces and Elections and Democracy DDoS disruption (Indian Cyber Force, 2023)

2023 · Canada · O - Public administration and defence · DDoS disruption of public websites

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS disruption of public websites

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) Strategic expectation: at the national level the Canadian Centre for Cyber Security had identified the DDoS campaign and warned IT professionals from 15 September 2023 (Alert AL23-014), repeating the vigilance notice on 22 September, and the three victim organizations each maintained the standard public-web-service posture: the CAF public website isolated from Department of National Defence servers and internal military networks, the Elections and Democracy site carrying no sensitive data, hosted externally and in no way connected to the elections.ca network, and the Ottawa Hospital's external websites separate from its internal systems. (2) In practice: the Indian Cyber Force's low-capacity DDoS attacks on 26-27 September 2023 made the Ottawa Hospital external websites briefly unavailable (Tuesday morning, sites quickly back up), the CAF website unavailable to mobile users for roughly two hours (fixed the same afternoon), and the Elections and Democracy site unavailable for about an hour; Elections Canada detected the anomaly through real-time internal and Cyber Centre monitoring; no data was put at risk and no system was breached, per the organizations' own statements and the Cyber Centre's assessment that DDoS activity is a nuisance event that rarely puts information at risk and has no permanent impact on systems. (3) Why this is alignment rather than a dual vulnerability: the classification rests on the whole lifecycle - entry (a public web service, the expected exposure of these organizations), containment (the blast radius stopped at the targeted front ends; each organization stated no broader impacts), detection (real-time monitoring flagged the events; the attacks were publicized by the attacker within the same window), egress (not in play: denial of service with no data breach or exfiltration), recovery (services restored within an hour to a few hours), response and disclosure (each victim publicly stated the facts within a day, matching the documented impact) - and every stage shows the doctrinal expectation realized in operation: the national alert was acted on, the architecture kept the disruption off core systems, and mitigation and communication were prompt and accurate. The only victim-side condition that appears anywhere in the sources is that standard web availability was briefly not held under a deliberate flood, which the national authority itself assessed as manageable nuisance activity, not a control failing; no knowing-doing gap and no doctrinal-material misalignment is documented at any stage, so this is a confirmed negative case rather than Unknown (the evidence is sufficient and affirmatively shows alignment).

Risk markers

Sources

Notes

EuRepoC row: victim, dates, actor and impact follow the case-file description and are confirmed by the cited reporting and official pages. Attribution rests on the group's own claims on Telegram/X as reported by the press (case file attribution_basis: Attacker confirms); the group's Telegram posts (t.me/TeamIndianCyberForce) are the attacker's own outlet and were not opened, per the research boundaries, so attribution is recorded as self-attribution only. The dataset records the disruption as short-term (< 24h, weighted intensity 1) and no data breach, exfiltration or corruption, matching the sources. Risk markers state the two conditions the evidence shows, without a DV claim (the case is No DV evidenced): brief failure of standard web availability under a deliberate flood (RM32), and the election-information service running on an externally hosted site - a trust boundary that was the path to the target, where the external hosting also limited the blast radius (RM13). Sector: the row carries three victims (health, military, election infrastructure under state institutions); the state-institution victims are two of three and the campaign was a state-linked political disruption, so the row is coded O Public administration and defence rather than Q. The attack also hit the House of Commons and Senate websites and several small-business sites, outside this row's stated victims; noted for context only. No consent-requiring actions were needed in this unattended run.