Comparison Overview

Belastingdienst

VS

Transportation Security Administration (TSA)

Belastingdienst

Korte Voorhout 7, Den Haag, 2500 EE, NL
Last Update: 2025-11-21

De organisatie bestaat uit diverse onderdelen, waaronder de Belastingdienst, Douane, Toeslagen, FIOD en enkele facilitaire organisaties. Met ruim 30.000 medewerkers werken we in kantoren die verspreid zijn over het hele land. Gezamenlijk heffen, innen en controleren we belastingen. Daarnaast zorgen we ook voor het uitbetalen van toeslagen. En zijn we verantwoordelijk voor douanetaken en het opsporen van fraude. De Belastingdienst is een organisatie die 24 uur per dag, 7 dagen per week in dienst staat van de samenleving. Waar jaarlijks miljoenen aangiften worden behandeld, en waar voor honderden miljoenen aan toeslagen worden uitbetaald. En waar de Douane dagelijks zorgt voor de vlotte en veilige in- en uitvoer van tonnen goederen. Ondanks deze grote aantallen streven wij waar mogelijk naar individuele en persoonlijke dienstverlening. En in de vorm van bijvoorbeeld convenanten en partnerships werken wij ook zo goed mogelijk samen met het bedrijfsleven en andere ketenpartners. De Belastingdienst: grootschalig, veelzijdig en altijd maatschappelijk relevant.

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

Transportation Security Administration (TSA)

601 12th Street South, None, Arlington, Virginia, US, 22202
Last Update: 2025-11-27
Between 750 and 799

The Transportation Security Administration (TSA) is a component agency of the U.S. Department of Homeland Security (DHS), committed to securing the nation’s transportation systems to ensure safe and efficient travel for all. Our mission is to protect the American people by preventing threats and disruptions in the transportation sector, while enhancing the overall passenger experience. 🔹 Mission: Safeguard transportation systems and prevent security threats 🔹 Vision: Achieve a secure and resilient transportation network 🔹 Values: Integrity, Excellence, Accountability, and Innovation More than 60,000 people around the world make up #TeamTSA and ensure the safety of millions of people each day as they travel by plane, train, automobile or ferry. From the officers you see on the frontlines to our cybersecurity and mission support teams, we’re working hard to combat evolving threats and keep you safe. Join us in our commitment to a more secure travel experience. For more information, visit tsa.gov.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/belastingdienst.jpeg
Belastingdienst
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/tsa.jpeg
Transportation Security Administration (TSA)
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
Belastingdienst
100%
Compliance Rate
0/4 Standards Verified
Transportation Security Administration (TSA)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Belastingdienst in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Transportation Security Administration (TSA) in 2025.

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

Belastingdienst cyber incidents detection timeline including parent company and subsidiaries

Incident History — Transportation Security Administration (TSA) (X = Date, Y = Severity)

Transportation Security Administration (TSA) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/belastingdienst.jpeg
Belastingdienst
Incidents

No Incident

https://images.rankiteo.com/companyimages/tsa.jpeg
Transportation Security Administration (TSA)
Incidents

Date Detected: 11/2025
Type:Breach
Motivation: Financial Gain (e.g., unauthorized loans, employment fraud, government benefits fraud)
Blog: Blog

Date Detected: 9/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement, Privilege Escalation
Motivation: Espionage, Data Theft, Potential Sabotage
Blog: Blog

Date Detected: 7/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement within Network
Motivation: Espionage, Data Theft
Blog: Blog

FAQ

Belastingdienst company demonstrates a stronger AI Cybersecurity Score compared to Transportation Security Administration (TSA) company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Transportation Security Administration (TSA) company has historically faced a number of disclosed cyber incidents, whereas Belastingdienst company has not reported any.

In the current year, Transportation Security Administration (TSA) company has reported more cyber incidents than Belastingdienst company.

Transportation Security Administration (TSA) company has confirmed experiencing a ransomware attack, while Belastingdienst company has not reported such incidents publicly.

Transportation Security Administration (TSA) company has disclosed at least one data breach, while Belastingdienst company has not reported such incidents publicly.

Transportation Security Administration (TSA) company has reported targeted cyberattacks, while Belastingdienst company has not reported such incidents publicly.

Transportation Security Administration (TSA) company has disclosed at least one vulnerability, while Belastingdienst company has not reported such incidents publicly.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds any compliance certifications.

Neither company holds any compliance certifications.

Transportation Security Administration (TSA) company has more subsidiaries worldwide compared to Belastingdienst company.

Belastingdienst company employs more people globally than Transportation Security Administration (TSA) company, reflecting its scale as a Government Administration.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds SOC 2 Type 1 certification.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds SOC 2 Type 2 certification.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds ISO 27001 certification.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds PCI DSS certification.

Neither Belastingdienst nor Transportation Security Administration (TSA) holds HIPAA certification.

Neither Belastingdienst nor Transportation Security Administration (TSA) 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