Comparison Overview

Ville de Montréal

VS

Ministry of Health Saudi Arabia

Ville de Montréal

275, rue Notre Dame Est, Montréal, Québec, CA, H2Y 1C6
Last Update: 2026-01-16

Montréal est la plus grande ville francophone d’Amérique et elle se distingue par sa vitalité culturelle exceptionnelle et des forces créatrices reconnues mondialement. Elle se développe un peu plus chaque jour en une ville contemporaine, inclusive et dynamique sur les plans économique, culturel et social. Visant à offrir aux Montréalaises et aux Montréalais un lieu de vie agréable et prospère, la Ville de Montréal veut rester à l’écoute des besoins changeants de sa population afin de s’y adapter de façon continue. Pour ce faire, elle mise sur les compétences et l’expertise de ses 28 000 employés au service de 1,8 million de citoyens.

NAICS: 92
NAICS Definition: Public Administration
Employees: 11,950
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Ministry of Health Saudi Arabia

-, Riyadh, 11176, SA
Last Update: 2026-01-17
Between 750 and 799

The Ministry of Health (MOH), by way of its objectives, policies and projects included in this strategy, seeks to accomplish a promising future vision; namely, delivering best-quality integrated and comprehensive healthcare services. Carrying health conditions or health status of Saudi inhabitants to the best and highest possible level, in terms of justice and equality in providing healthcare, and in terms of effectiveness and the possibility of incurring the financial burden of the treatment and healthcare. In doing so, the MOH takes as its target meeting citizens’ aspirations in this regard, by providing them with high-quality general and specialized health services, and covering all the population with these services.  Creating a sole and exclusive entity to formulate health policies including health insurance services, etc. (such as operating the recently established Health Services Council.) Adopting a public and national health strategy which focuses of the main morbidity burdens; including non-communicable diseases, nutrition, reproductive health, smoking (tobacco-use), AIDS, traffic accidents, and injuries.   The system must have an effective and fair method for estimating risks and benefits.   Working to diversify sources of revenues to finance the system effectively. These sources must include also public revenues and insurance premiums, in addition to the equally allocated costs and taxes.

NAICS: 92
NAICS Definition: Public Administration
Employees: 28,664
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ville-de-montr-al.jpeg
Ville de Montréal
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/ministry-of-health-saudi-arabia.jpeg
Ministry of Health Saudi Arabia
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Ville de Montréal
100%
Compliance Rate
0/4 Standards Verified
Ministry of Health Saudi Arabia
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ville de Montréal in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ministry of Health Saudi Arabia in 2026.

Incident History — Ville de Montréal (X = Date, Y = Severity)

Ville de Montréal cyber incidents detection timeline including parent company and subsidiaries

Incident History — Ministry of Health Saudi Arabia (X = Date, Y = Severity)

Ministry of Health Saudi Arabia cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ville-de-montr-al.jpeg
Ville de Montréal
Incidents

No Incident

https://images.rankiteo.com/companyimages/ministry-of-health-saudi-arabia.jpeg
Ministry of Health Saudi Arabia
Incidents

No Incident

FAQ

Ministry of Health Saudi Arabia company demonstrates a stronger AI Cybersecurity Score compared to Ville de Montréal company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Ministry of Health Saudi Arabia company has disclosed a higher number of cyber incidents compared to Ville de Montréal company.

In the current year, Ministry of Health Saudi Arabia company and Ville de Montréal company have not reported any cyber incidents.

Neither Ministry of Health Saudi Arabia company nor Ville de Montréal company has reported experiencing a ransomware attack publicly.

Neither Ministry of Health Saudi Arabia company nor Ville de Montréal company has reported experiencing a data breach publicly.

Neither Ministry of Health Saudi Arabia company nor Ville de Montréal company has reported experiencing targeted cyberattacks publicly.

Neither Ville de Montréal company nor Ministry of Health Saudi Arabia company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds any compliance certifications.

Neither company holds any compliance certifications.

Ville de Montréal company has more subsidiaries worldwide compared to Ministry of Health Saudi Arabia company.

Ministry of Health Saudi Arabia company employs more people globally than Ville de Montréal company, reflecting its scale as a Government Administration.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds SOC 2 Type 1 certification.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds SOC 2 Type 2 certification.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds ISO 27001 certification.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds PCI DSS certification.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds HIPAA certification.

Neither Ville de Montréal nor Ministry of Health Saudi Arabia holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H