Comparison Overview

Ville de Montréal

VS

US Government Accountability Office

Ville de Montréal

275, rue Notre Dame Est, Montréal, Québec, H2Y 1C6, CA
Last Update: 2025-11-25
View Profile
Between 750 and 799
https://montreal.ca/articles/offres-demploi-2944

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,464
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

US Government Accountability Office

441 G Street, N.W., Washington, DC, US, 20548
Last Update: 2025-11-20
Between 750 and 799
http://www.gao.gov

For more information about GAO, please visit www.gao.gov. General Information The U.S. Government Accountability Office (GAO) is an independent, nonpartisan agency that works for Congress. Often called the "congressional watchdog,"​ GAO investigates how the federal government spends taxpayer dollars. Mission Our Mission is to support the Congress in meeting its constitutional responsibilities and to help improve the performance and ensure the accountability of the federal government for the benefit of the American people. We provide Congress with timely information that is objective, fact-based, nonpartisan, non-ideological, fair, and balanced. GAO Social Media Terms of Use: https://www.facebook.com/usgao/app/250336418365488/

NAICS: 92
NAICS Definition: Public Administration
Employees: 17,311
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/us-government.jpeg
US Government Accountability Office
—
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
US Government Accountability Office
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 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for US Government Accountability Office in 2025.

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 — US Government Accountability Office (X = Date, Y = Severity)

US Government Accountability Office 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/us-government.jpeg
US Government Accountability Office
Incidents

No Incident

FAQ

Ville de Montréal company demonstrates a stronger AI Cybersecurity Score compared to US Government Accountability Office company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, US Government Accountability Office company has disclosed a higher number of cyber incidents compared to Ville de Montréal company.

In the current year, US Government Accountability Office company and Ville de Montréal company have not reported any cyber incidents.

Neither US Government Accountability Office company nor Ville de Montréal company has reported experiencing a ransomware attack publicly.

Neither US Government Accountability Office company nor Ville de Montréal company has reported experiencing a data breach publicly.

Neither US Government Accountability Office company nor Ville de Montréal company has reported experiencing targeted cyberattacks publicly.

Neither Ville de Montréal company nor US Government Accountability Office company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ville de Montréal nor US Government Accountability Office holds any compliance certifications.

Neither company holds any compliance certifications.

Ville de Montréal company has more subsidiaries worldwide compared to US Government Accountability Office company.

US Government Accountability Office company employs more people globally than Ville de Montréal company, reflecting its scale as a Government Administration.

Neither Ville de Montréal nor US Government Accountability Office holds SOC 2 Type 1 certification.

Neither Ville de Montréal nor US Government Accountability Office holds SOC 2 Type 2 certification.

Neither Ville de Montréal nor US Government Accountability Office holds ISO 27001 certification.

Neither Ville de Montréal nor US Government Accountability Office holds PCI DSS certification.

Neither Ville de Montréal nor US Government Accountability Office holds HIPAA certification.

Neither Ville de Montréal nor US Government Accountability Office holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/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
References
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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
References
Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/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
References
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

Published
Date
2025-11-26
Updated
Date
2025-11-26
Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References