Government of the Netherlands
Last Update: 2026-04-01
Between 800 and 849
Government of the Netherlands
NAICS: 92
NAICS Definition: Public Administration
Employees: 41
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1
Comparison Overview
Government of the Netherlands
VS
Ville de Montréal
Ville de Montréal
Last Update: 2026-04-02
Between 750 and 799
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
Compliance Badges Comparison
Security & Compliance Standards Overview
Government of the Netherlands
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Ville de Montréal
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Government of the Netherlands
100%
Compliance Rate
0/4 Standards Verified
Ville de Montréal
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Average (This Year)
No incidents recorded for Government of the Netherlands in 2026.
Incidents vs Government Administration Industry Average (This Year)
No incidents recorded for Ville de Montréal in 2026.
Incident History — Government of the Netherlands (X = Date, Y = Severity)
Government of the Netherlands cyber incidents detection timeline including parent company and subsidiaries
Incident History — Ville de Montréal (X = Date, Y = Severity)
Ville de Montréal cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Government of the Netherlands
Incidents
Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: DDoS
Motivation: Ideologically pro-Russian
Blog: Blog
Ville de Montréal
Incidents
No Incident
FAQ
Government of the Netherlands company demonstrates a stronger AI Cybersecurity Score compared to Ville de Montréal company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Government of the Netherlands company has historically faced a number of disclosed cyber incidents, whereas Ville de Montréal company has not reported any.
In the current year, Ville de Montréal company and Government of the Netherlands company have not reported any cyber incidents.
Neither Ville de Montréal company nor Government of the Netherlands company has reported experiencing a ransomware attack publicly.
Neither Ville de Montréal company nor Government of the Netherlands company has reported experiencing a data breach publicly.
Government of the Netherlands company has reported targeted cyberattacks, while Ville de Montréal company has not reported such incidents publicly.
Neither Government of the Netherlands company nor Ville de Montréal company has reported experiencing or disclosing vulnerabilities publicly.
Neither Government of the Netherlands nor Ville de Montréal holds any compliance certifications.
Neither company holds any compliance certifications.
Ville de Montréal company has more subsidiaries worldwide compared to Government of the Netherlands company.
Ville de Montréal company employs more people globally than Government of the Netherlands company, reflecting its scale as a Government Administration.
Neither Government of the Netherlands nor Ville de Montréal holds SOC 2 Type 1 certification.
Neither Government of the Netherlands nor Ville de Montréal holds SOC 2 Type 2 certification.
Neither Government of the Netherlands nor Ville de Montréal holds ISO 27001 certification.
Neither Government of the Netherlands nor Ville de Montréal holds PCI DSS certification.
Neither Government of the Netherlands nor Ville de Montréal holds HIPAA certification.
Neither Government of the Netherlands nor Ville de Montréal holds GDPR certification.
Latest Global CVEs (Not Company-Specific)
Description
nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Description
PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description
PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
