Comparison Overview

USPS OIG

VS

FDA

USPS OIG

1735 North Lynn Street, Arlington, VA, US, 22209-2020
Last Update: 2025-12-17
Between 700 and 749

Welcome to the U.S. Postal Service Office of Inspector General (USPS OIG) fan page on LinkedIn. We play a key role in maintaining the integrity and accountability of America’s postal service, its revenue and assets, and its employees. On our page, you will find the most recent news stories and reports. We want to hear what you have to say! We encourage you to share your comments, ideas, and concerns. All we ask is that you please keep your comments and wall posts clean and respectful and follow our posting guidelines. We reserve the right to determine which comments are acceptable for this page. If you don't comply, we’ll remove your message: -We don’t allow graphic, obscene, explicit or racial comments or submissions nor do we allow comments that are abusive, hateful or intended to defame anyone or any group. -We do not allow solicitations or advertisements for outside entities. This also applies to spam and chain-letters. -Comments that make unsupported accusations will be removed. This is a public forum and any information provided in comments may be publicly available on LinedIn. LinkedIn's privacy policies apply. As such, please do not post personal information you do not want available to the general public. You post at your own risk, taking personal responsibility for your comments, your username and any information provided. Note that the appearance of external links on this page does not constitute official endorsement on behalf of the USPS OIG or the Postal Service. USPS OIG is not liable for any loss or damage resulting from any comments posted on this page. Our page is not the place to report violations of laws, rules, or regulations; misconduct; waste of funds; abuse of authority; theft of mail by employee or contractor; or know of a situation in the Postal Service that is a danger to public health and safety. These concerns should be reported directly to our Hotline at http://www.uspsoig.gov/hotline.

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

FDA

10903 New Hampshire Ave, None, Silver Spring, MD, US, 20993
Last Update: 2025-12-17
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/usps-oig.jpeg
USPS OIG
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
USPS OIG
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)

No incidents recorded for USPS OIG in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for FDA in 2025.

Incident History — USPS OIG (X = Date, Y = Severity)

USPS OIG 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/usps-oig.jpeg
USPS OIG
Incidents

Date Detected: 8/2024
Type:Breach
Attack Vector: Phishing
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/fda.jpeg
FDA
Incidents

No Incident

FAQ

FDA company demonstrates a stronger AI Cybersecurity Score compared to USPS OIG company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

USPS OIG company has historically faced a number of disclosed cyber incidents, whereas FDA company has not reported any.

In the current year, FDA company and USPS OIG company have not reported any cyber incidents.

Neither FDA company nor USPS OIG company has reported experiencing a ransomware attack publicly.

USPS OIG company has disclosed at least one data breach, while the other FDA company has not reported such incidents publicly.

Neither FDA company nor USPS OIG company has reported experiencing targeted cyberattacks publicly.

Neither USPS OIG company nor FDA company has reported experiencing or disclosing vulnerabilities publicly.

Neither USPS OIG nor FDA holds any compliance certifications.

Neither company holds any compliance certifications.

FDA company has more subsidiaries worldwide compared to USPS OIG company.

FDA company employs more people globally than USPS OIG company, reflecting its scale as a Government Administration.

Neither USPS OIG nor FDA holds SOC 2 Type 1 certification.

Neither USPS OIG nor FDA holds SOC 2 Type 2 certification.

Neither USPS OIG nor FDA holds ISO 27001 certification.

Neither USPS OIG nor FDA holds PCI DSS certification.

Neither USPS OIG nor FDA holds HIPAA certification.

Neither USPS OIG nor FDA holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.

Risk Information
cvss3
Base: 9.9
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Description

FastAPI Users allows users to quickly add a registration and authentication system to their FastAPI project. Prior to version 15.0.2, the OAuth login state tokens are completely stateless and carry no per-request entropy or any data that could link them to the session that initiated the OAuth flow. `generate_state_token()` is always called with an empty `state_data` dict, so the resulting JWT only contains the fixed audience claim plus an expiration timestamp. On callback, the library merely checks that the JWT verifies under `state_secret` and is unexpired; there is no attempt to match the state value to the browser that initiated the OAuth request, no correlation cookie, and no server-side cache. Any attacker can hit `/authorize`, capture the server-generated state, finish the upstream OAuth flow with their own provider account, and then trick a victim into loading `.../callback?code=<attacker_code>&state=<attacker_state>`. Because the state JWT is valid for any client for \~1 hour, the victim’s browser will complete the flow. This leads to login CSRF. Depending on the app’s logic, the login CSRF can lead to an account takeover of the victim account or to the victim user getting logged in to the attacker's account. Version 15.0.2 contains a patch for the issue.

Risk Information
cvss3
Base: 5.9
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
Description

FileZilla Client 3.63.1 contains a DLL hijacking vulnerability that allows attackers to execute malicious code by placing a crafted TextShaping.dll in the application directory. Attackers can generate a reverse shell payload using msfvenom and replace the missing DLL to achieve remote code execution when the application launches.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/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

LDAP Tool Box Self Service Password 1.5.2 contains a password reset vulnerability that allows attackers to manipulate HTTP Host headers during token generation. Attackers can craft malicious password reset requests that generate tokens sent to a controlled server, enabling potential account takeover by intercepting and using stolen reset tokens.

Risk Information
cvss3
Base: 7.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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

Kimai 1.30.10 contains a SameSite cookie vulnerability that allows attackers to steal user session cookies through malicious exploitation. Attackers can trick victims into executing a crafted PHP script that captures and writes session cookie information to a file, enabling potential session hijacking.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
cvss4
Base: 8.5
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/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