Comparison Overview

Q: Between Workingfor.be company and FDA company, which one has the best AI Cybersecurity Score ?

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

Q: Between Workingfor.be company and FDA company, which one has experienced more cyber incidents in the past ?

Historically, FDA company has disclosed a higher number of cyber incidents compared to Workingfor.be company.

Q: Between Workingfor.be company and FDA company, which one has experienced more cyber incidents this year ?

In the current year, FDA company and Workingfor.be company have not reported any cyber incidents.

Q: Between Workingfor.be company and FDA company, which one has experienced at least one ransomware attack ?

Neither FDA company nor Workingfor.be company has reported experiencing a ransomware attack publicly.

Q: Between Workingfor.be company and FDA company, which one has experienced at least one data breach ?

Neither FDA company nor Workingfor.be company has reported experiencing a data breach publicly.

Q: Between Workingfor.be company and FDA company, which one has experienced at least one targeted cyberattack ?

Neither FDA company nor Workingfor.be company has reported experiencing targeted cyberattacks publicly.

Q: Between Workingfor.be company and FDA company, which one has experienced at least one vulnerability ?

Neither Workingfor.be company nor FDA company has reported experiencing or disclosing vulnerabilities publicly.

Q: Between Workingfor.be company and FDA company, which one holds the most compliance certifications ?

Neither Workingfor.be nor FDA holds any compliance certifications.

Q: Between Workingfor.be company and FDA company, which one has the most subsidiaries ?

FDA company has more subsidiaries worldwide compared to Workingfor.be company.

Workingfor.be

Simon Bolivarlaan 30, Bld. Simon Bolivar 30, Brussels, Brabant, BE, 1000

Last Update: 2026-01-18

View Profile

Between 750 and 799

www.workingfor.be

Workingfor.be is the job platform of the federal administration. Here, you will find a wide variety of jobs in different fields of profession. Every day thousands of our employees help build tomorrow's society. When you choose the federal administration, you choose an employer who embraces your talent and individuality and gives you the opportunity to develop yourself and your skills further every single day. Moreover, we offer you a job where you can easily find the balance between your professional and personal life. Do you want to contribute to the Belgium of tomorrow? Feel like making a difference and developing your talents? Discover our wide range of vacancies at www.workingfor.be

NAICS: 92

NAICS Definition: Public Administration

Employees: 17,078

Subsidiaries: 0

12-month incidents

0

Known data breaches

0

Attack type number

0

View Profile

FDA

10903 New Hampshire Ave, Silver Spring, 20993, US

Last Update: 2026-01-17

Between 800 and 849

http://www.fda.gov/

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,340

Subsidiaries: 2

12-month incidents

0

Known data breaches

0

Attack type number

0

Workingfor.be

—

ISO 27001

Not verified

—

SOC2 Type 1

Not verified

—

SOC2 Type 2

Not verified

—

GDPR

Not verified

—

PCI DSS

Not verified

—

HIPAA

Not verified

https://images.rankiteo.com/companyimages/fda.jpeg

FDA

—

ISO 27001

Not verified

—

SOC2 Type 1

Not verified

—

SOC2 Type 2

Not verified

—

GDPR

Not verified

—

PCI DSS

Not verified

—

HIPAA

Not verified

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Workingfor.be in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for FDA in 2026.

Incident History — Workingfor.be (X = Date, Y = Severity)

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

Workingfor.be

Incidents

No Incident

FDA

Incidents

No Incident

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

Historically, FDA company has disclosed a higher number of cyber incidents compared to Workingfor.be company.

In the current year, FDA company and Workingfor.be company have not reported any cyber incidents.

Neither FDA company nor Workingfor.be company has reported experiencing a ransomware attack publicly.

Neither FDA company nor Workingfor.be company has reported experiencing a data breach publicly.

Neither FDA company nor Workingfor.be company has reported experiencing targeted cyberattacks publicly.

Neither Workingfor.be company nor FDA company has reported experiencing or disclosing vulnerabilities publicly.

Neither Workingfor.be nor FDA holds any compliance certifications.

Neither company holds any compliance certifications.

FDA company has more subsidiaries worldwide compared to Workingfor.be company.

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

Neither Workingfor.be nor FDA holds SOC 2 Type 1 certification.

Neither Workingfor.be nor FDA holds SOC 2 Type 2 certification.

Neither Workingfor.be nor FDA holds ISO 27001 certification.

Neither Workingfor.be nor FDA holds PCI DSS certification.

Neither Workingfor.be nor FDA holds HIPAA certification.

Neither Workingfor.be nor FDA holds GDPR certification.

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g., execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss4

Base: 7.7

Severity: LOW

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

References

https://github.com/cloudflare/workers-sdk

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.1

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published

Date

2026-01-20

Updated

Date

2026-01-20

Risk Information

cvss3

Base: 8.2

Severity: LOW

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

References

https://www.oracle.com/security-alerts/cpujan2026.html

Badge your company to reduce your risk score and your cyber insurance costs!

Comparison Overview

Workingfor.be

VS

FDA

Workingfor.be

FDA

Compliance Badges Comparison

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

Incidents vs Government Administration Industry Average (This Year)

Incident History — Workingfor.be (X = Date, Y = Severity)

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

Notable Incidents

No Incident

No Incident

FAQ

Latest Global CVEs (Not Company-Specific)

CVE-2026-0933

Risk Information

CVE-2026-21990

Risk Information

CVE-2026-21989

Risk Information

CVE-2026-21988

Risk Information

CVE-2026-21987

Risk Information

Badge your company to reduce your risk score and your cyber insurance costs!

Comparison Overview

Workingfor.be

VS

FDA

Workingfor.be

FDA

Compliance Badges Comparison

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

Incidents vs Government Administration Industry Average (This Year)

Incident History — Workingfor.be (X = Date, Y = Severity)

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

Notable Incidents

No Incident

No Incident

FAQ

Between Workingfor.be company and FDA company, which one has the best AI Cybersecurity Score ?

Between Workingfor.be company and FDA company, which one has experienced more cyber incidents in the past ?

Between Workingfor.be company and FDA company, which one has experienced more cyber incidents this year ?

Between Workingfor.be company and FDA company, which one has experienced at least one ransomware attack ?

Between Workingfor.be company and FDA company, which one has experienced at least one data breach ?

Between Workingfor.be company and FDA company, which one has experienced at least one targeted cyberattack ?

Between Workingfor.be company and FDA company, which one has experienced at least one vulnerability ?

Between Workingfor.be company and FDA company, which one holds the most compliance certifications ?

Between Workingfor.be company and FDA company, which one holds the fewest compliance certifications ?

Between Workingfor.be company and FDA company, which one has the most subsidiaries ?

Between Workingfor.be company and FDA company, which one has the largest number of employees ?

Between Workingfor.be and FDA, which company holds both SOC 2 Type 1 certifications ?

Between Workingfor.be and FDA, which company holds both SOC 2 Type 2 certifications ?

Which company is ISO 27001 certified — Workingfor.be or FDA ?

Which company is PCI DSS compliant — Workingfor.be or FDA ?

Between Workingfor.be and FDA, which company complies with HIPAA regulations for healthcare data ?

Between Workingfor.be and FDA, which company complies with GDPR requirements ?

Latest Global CVEs (Not Company-Specific)

CVE-2026-0933

Risk Information

CVE-2026-21990

Risk Information

CVE-2026-21989

Risk Information

CVE-2026-21988

Risk Information

CVE-2026-21987

Risk Information