Comparison Overview

Rijkswaterstaat

VS

U.S. Census Bureau

Rijkswaterstaat

Koningskade 4, Den Haag, The Netherlands, 2500 EX, NL
Last Update: 2025-11-27

Rijkswaterstaat is de uitvoeringsorganisatie van het Ministerie van Infrastructuur en Waterstaat. We beheren en ontwikkelen de rijkswegen, -vaarwegen en –wateren en zetten in op een duurzame leefomgeving. Samen met andere organisaties werken we aan een land dat beschermd is tegen overstromingen. Waar voldoende groen is, en voldoende en schoon water. En waar je vlot en veilig van A naar B kunt. Samenwerken aan een veilig, leefbaar en bereikbaar Nederland. Dat is Rijkswaterstaat. Bij Rijkswaterstaat werk je mee aan de toekomst van Nederland met de ruimte om jezelf te blijven ontwikkelen. Gun jezelf een baan met toekomst. Gun jezelf Rijkswaterstaat.

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

U.S. Census Bureau

4600 Silver Hill Road, Washington, DC, US, 20233
Last Update: 2025-11-26
Between 750 and 799

The Census Bureau serves as the nation’s leading provider of quality data about its people and economy. We have been headquartered in Suitland, Maryland since 1942, and currently employ about 4,285 staff members. We are part of the U.S. Department of Commerce and overseen by the Economics and Statistics Administration (ESA). We honor privacy, protect confidentiality, share our expertise globally, and conduct our work openly. We are guided on this mission by our strong and capable workforce, our readiness to innovate, and our abiding commitment to our customers. View our comment policy: https://www.census.gov/about/contact-us/comment-policy.html View our privacy policy: https://www.census.gov/about/policies/privacy/privacy-policy.html

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rijkswaterstaat.jpeg
Rijkswaterstaat
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-census-bureau.jpeg
U.S. Census Bureau
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
Rijkswaterstaat
100%
Compliance Rate
0/4 Standards Verified
U.S. Census Bureau
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Rijkswaterstaat in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for U.S. Census Bureau in 2025.

Incident History — Rijkswaterstaat (X = Date, Y = Severity)

Rijkswaterstaat cyber incidents detection timeline including parent company and subsidiaries

Incident History — U.S. Census Bureau (X = Date, Y = Severity)

U.S. Census Bureau cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rijkswaterstaat.jpeg
Rijkswaterstaat
Incidents

No Incident

https://images.rankiteo.com/companyimages/us-census-bureau.jpeg
U.S. Census Bureau
Incidents

Date Detected: 1/2020
Type:Cyber Attack
Attack Vector: Network Intrusion
Blog: Blog

FAQ

Rijkswaterstaat company demonstrates a stronger AI Cybersecurity Score compared to U.S. Census Bureau company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

U.S. Census Bureau company has historically faced a number of disclosed cyber incidents, whereas Rijkswaterstaat company has not reported any.

In the current year, U.S. Census Bureau company and Rijkswaterstaat company have not reported any cyber incidents.

Neither U.S. Census Bureau company nor Rijkswaterstaat company has reported experiencing a ransomware attack publicly.

Neither U.S. Census Bureau company nor Rijkswaterstaat company has reported experiencing a data breach publicly.

U.S. Census Bureau company has reported targeted cyberattacks, while Rijkswaterstaat company has not reported such incidents publicly.

Neither Rijkswaterstaat company nor U.S. Census Bureau company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rijkswaterstaat nor U.S. Census Bureau holds any compliance certifications.

Neither company holds any compliance certifications.

Rijkswaterstaat company has more subsidiaries worldwide compared to U.S. Census Bureau company.

Rijkswaterstaat company employs more people globally than U.S. Census Bureau company, reflecting its scale as a Government Administration.

Neither Rijkswaterstaat nor U.S. Census Bureau holds SOC 2 Type 1 certification.

Neither Rijkswaterstaat nor U.S. Census Bureau holds SOC 2 Type 2 certification.

Neither Rijkswaterstaat nor U.S. Census Bureau holds ISO 27001 certification.

Neither Rijkswaterstaat nor U.S. Census Bureau holds PCI DSS certification.

Neither Rijkswaterstaat nor U.S. Census Bureau holds HIPAA certification.

Neither Rijkswaterstaat nor U.S. Census Bureau 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.

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
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.

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
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.

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
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.

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
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.

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