Comparison Overview

U.S. Department of the Treasury

VS

FDA

U.S. Department of the Treasury

1500 Pennsylvania Ave NW, Washington, DC, US, 20005
Last Update: 2025-11-24

The Treasury Department is the executive agency responsible for promoting economic prosperity and ensuring the financial security of the United States. The Department is responsible for a wide range of activities such as advising the President on economic and financial issues, encouraging sustainable economic growth, and fostering improved governance in financial institutions. The Department of the Treasury operates and maintains systems that are critical to the nation's financial infrastructure, such as the production of coin and currency, the disbursement of payments to the American public, revenue collection, and the borrowing of funds necessary to run the federal government. The Department works with other federal agencies, foreign governments, and international financial institutions to encourage global economic growth, raise standards of living, and to the extent possible, predict and prevent economic and financial crises. The Treasury Department also performs a critical and far-reaching role in enhancing national security by implementing economic sanctions against foreign threats to the U.S., identifying and targeting the financial support networks of national security threats, and improving the safeguards of our financial systems.

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

FDA

10903 New Hampshire Ave, None, Silver Spring, MD, US, 20993
Last Update: 2025-11-21
Between 800 and 849

The Food and Drug Administration is an agency within the Department of Health and Human Services. The FDA is responsible for protecting the public health by ensuring the safety, efficacy, and security of human and veterinary drugs, biological products, and medical devices; and by ensuring the safety of our nation's food supply, cosmetics, and products that emit radiation. FDA also has responsibility for regulating the manufacturing, marketing, and distribution of tobacco products to protect the public health and to reduce tobacco use by minors. FDA is responsible for advancing the public health by helping to speed innovations that make medical products more effective, safer, and more affordable and by helping the public get the accurate, science-based information they need to use medical products and foods to maintain and improve their health. FDA also plays a significant role in the Nation's counterterrorism capability. FDA fulfills this responsibility by ensuring the security of the food supply and by fostering development of medical products to respond to deliberate and naturally emerging public health threats.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/us-treasury.jpeg
U.S. Department of the Treasury
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/fda.jpeg
FDA
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
U.S. Department of the Treasury
100%
Compliance Rate
0/4 Standards Verified
FDA
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

U.S. Department of the Treasury has 669.23% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for FDA in 2025.

Incident History — U.S. Department of the Treasury (X = Date, Y = Severity)

U.S. Department of the Treasury cyber incidents detection timeline including parent company and subsidiaries

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

FDA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/us-treasury.jpeg
U.S. Department of the Treasury
Incidents

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: exploitation of trusted cloud relationships (SaaS providers, Microsoft CSPs), zero-day vulnerabilities (e.g., Citrix NetScaler CVE-2023-3519, Ivanti Pulse Connect CVE-2025-0282), ProxyLogon (Microsoft Exchange), compromised SOHO devices as proxies, web shells (Neo-reGeorg, China Chopper), custom Linux RAT (CloudedHope)
Motivation: cyberespionage (targeting government, technology, legal, and professional services for sensitive data)
Blog: Blog

Date Detected: 3/2025
Type:Breach
Motivation: Espionage, Strategic Advantage
Blog: Blog

Date Detected: 1/2025
Type:Breach
Attack Vector: Exploited flaws in BeyondTrust software
Motivation: Data Theft
Blog: Blog
https://images.rankiteo.com/companyimages/fda.jpeg
FDA
Incidents

No Incident

FAQ

FDA company demonstrates a stronger AI Cybersecurity Score compared to U.S. Department of the Treasury company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

U.S. Department of the Treasury company has historically faced a number of disclosed cyber incidents, whereas FDA company has not reported any.

In the current year, U.S. Department of the Treasury company has reported more cyber incidents than FDA company.

Neither FDA company nor U.S. Department of the Treasury company has reported experiencing a ransomware attack publicly.

U.S. Department of the Treasury company has disclosed at least one data breach, while the other FDA company has not reported such incidents publicly.

U.S. Department of the Treasury company has reported targeted cyberattacks, while FDA company has not reported such incidents publicly.

Neither U.S. Department of the Treasury company nor FDA company has reported experiencing or disclosing vulnerabilities publicly.

Neither U.S. Department of the Treasury nor FDA holds any compliance certifications.

Neither company holds any compliance certifications.

FDA company has more subsidiaries worldwide compared to U.S. Department of the Treasury company.

FDA company employs more people globally than U.S. Department of the Treasury company, reflecting its scale as a Government Administration.

Neither U.S. Department of the Treasury nor FDA holds SOC 2 Type 1 certification.

Neither U.S. Department of the Treasury nor FDA holds SOC 2 Type 2 certification.

Neither U.S. Department of the Treasury nor FDA holds ISO 27001 certification.

Neither U.S. Department of the Treasury nor FDA holds PCI DSS certification.

Neither U.S. Department of the Treasury nor FDA holds HIPAA certification.

Neither U.S. Department of the Treasury nor FDA 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