Comparison Overview

Department of Health (Philippines)

VS

U.S. Department of the Treasury

Department of Health (Philippines)

San Lazaro Compound, Rizal Avenue, Santa Cruz, Manila City, 1014, PH
Last Update: 2026-01-18
View Profile
Between 750 and 799
https://www.doh.gov.ph/

The Philippine Department of Health (abbreviated as DOH; Filipino: Kagawaran ng Kalusugan) is the executive department of the Philippine government responsible for ensuring access to basic public health services by all Filipinos through the provision of quality health care and the regulation of all health services and products. It is the government's over-all technical authority on health. It has its headquarters at the San Lazaro Compound, along Rizal Avenue in Manila. The department is led by the Secretary of Health, nominated by the President of the Philippines and confirmed by the Commission on Appointments. The Secretary is a member of the Cabinet. The current Secretary of Health is Francisco Duque.

NAICS: 92
NAICS Definition: Public Administration
Employees: 35,478
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

U.S. Department of the Treasury

1500 Pennsylvania Ave NW, Washington, 20005, US
Last Update: 2026-01-17
Between 600 and 649
https://home.treasury.gov/

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,324
Subsidiaries: 0
12-month incidents
0
Known data breaches
3
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/dohgovph.jpeg
Department of Health (Philippines)
—
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-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
Compliance Summary
Department of Health (Philippines)
100%
Compliance Rate
0/4 Standards Verified
U.S. Department of the Treasury
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Department of Health (Philippines) in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for U.S. Department of the Treasury in 2026.

Incident History — Department of Health (Philippines) (X = Date, Y = Severity)

Department of Health (Philippines) cyber incidents detection timeline including parent company and subsidiaries

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/dohgovph.jpeg
Department of Health (Philippines)
Incidents

No Incident

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

FAQ

Department of Health (Philippines) 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 Department of Health (Philippines) company has not reported any.

In the current year, U.S. Department of the Treasury company and Department of Health (Philippines) company have not reported any cyber incidents.

Neither U.S. Department of the Treasury company nor Department of Health (Philippines) company has reported experiencing a ransomware attack publicly.

U.S. Department of the Treasury company has disclosed at least one data breach, while Department of Health (Philippines) company has not reported such incidents publicly.

U.S. Department of the Treasury company has reported targeted cyberattacks, while Department of Health (Philippines) company has not reported such incidents publicly.

Neither Department of Health (Philippines) company nor U.S. Department of the Treasury company has reported experiencing or disclosing vulnerabilities publicly.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Department of Health (Philippines) company nor U.S. Department of the Treasury company has publicly disclosed detailed information about the number of their subsidiaries.

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

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds SOC 2 Type 1 certification.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds SOC 2 Type 2 certification.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds ISO 27001 certification.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds PCI DSS certification.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds HIPAA certification.

Neither Department of Health (Philippines) nor U.S. Department of the Treasury holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

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