Comparison Overview

US Environmental Protection Agency (EPA)

VS

State of California

US Environmental Protection Agency (EPA)

1200 Pennsylvania Ave. N.W., Washington, 20004, US
Last Update: 2026-01-17
Between 750 and 799

U.S. Environmental Protection Agency’s (EPA) mission is to protect human health and the environment. EPA works to ensure that: - Americans have clean air, land and water; - National efforts to reduce environmental risks are based on the best available scientific information; - Federal laws protecting human health and the environment are administered and enforced fairly, effectively and as Congress intended; - Environmental stewardship is integral to U.S. policies concerning natural resources, human health, economic growth, energy, transportation, agriculture, industry, and international trade, and these factors are similarly considered in establishing environmental policy; - All parts of society--communities, individuals, businesses, and state, local and tribal governments--have access to accurate information sufficient to effectively participate in managing human health and environmental risks; - Contaminated lands and toxic sites are cleaned up by potentially responsible parties and revitalized; and - Chemicals in the marketplace are reviewed for safety. The agency was founded in 1970 and is headquartered in Washington, District of Columbia with ten additional regional headquarters offices (Boston, New York, Philadelphia, Atlanta, Chicago, Dallas, Kansas City, Denver, San Francisco, and Seattle) as well as more than a dozen laboratories, and other regional and programmatic offices.

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

State of California

Sacramento, Sacramento, 95814, US
Last Update: 2026-01-18
Between 750 and 799

Californians deserve a government that works for them and with them. One that will work to ensure opportunity and justice. We are building a California not for the few, but for all — including those who have historically been left out. We are doing the work to make our state a place for every Californian and all the diversity that makes us strong. Our state will be known as a place where everyone is respected, protected, and connected.

NAICS: 92
NAICS Definition: Public Administration
Employees: 44,863
Subsidiaries: 29
12-month incidents
0
Known data breaches
27
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/us-epa.jpeg
US Environmental Protection Agency (EPA)
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/state-of-california.jpeg
State of California
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
US Environmental Protection Agency (EPA)
100%
Compliance Rate
0/4 Standards Verified
State of California
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for US Environmental Protection Agency (EPA) in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of California in 2026.

Incident History — US Environmental Protection Agency (EPA) (X = Date, Y = Severity)

US Environmental Protection Agency (EPA) cyber incidents detection timeline including parent company and subsidiaries

Incident History — State of California (X = Date, Y = Severity)

State of California cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/us-epa.jpeg
US Environmental Protection Agency (EPA)
Incidents

No Incident

https://images.rankiteo.com/companyimages/state-of-california.jpeg
State of California
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Inadvertent Email
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 2/2024
Type:Breach
Attack Vector: Unauthorized Dissemination
Blog: Blog

FAQ

US Environmental Protection Agency (EPA) company demonstrates a stronger AI Cybersecurity Score compared to State of California company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of California company has historically faced a number of disclosed cyber incidents, whereas US Environmental Protection Agency (EPA) company has not reported any.

In the current year, State of California company and US Environmental Protection Agency (EPA) company have not reported any cyber incidents.

State of California company has confirmed experiencing a ransomware attack, while US Environmental Protection Agency (EPA) company has not reported such incidents publicly.

State of California company has disclosed at least one data breach, while US Environmental Protection Agency (EPA) company has not reported such incidents publicly.

Neither State of California company nor US Environmental Protection Agency (EPA) company has reported experiencing targeted cyberattacks publicly.

Neither US Environmental Protection Agency (EPA) company nor State of California company has reported experiencing or disclosing vulnerabilities publicly.

Neither US Environmental Protection Agency (EPA) nor State of California holds any compliance certifications.

Neither company holds any compliance certifications.

State of California company has more subsidiaries worldwide compared to US Environmental Protection Agency (EPA) company.

State of California company employs more people globally than US Environmental Protection Agency (EPA) company, reflecting its scale as a Government Administration.

Neither US Environmental Protection Agency (EPA) nor State of California holds SOC 2 Type 1 certification.

Neither US Environmental Protection Agency (EPA) nor State of California holds SOC 2 Type 2 certification.

Neither US Environmental Protection Agency (EPA) nor State of California holds ISO 27001 certification.

Neither US Environmental Protection Agency (EPA) nor State of California holds PCI DSS certification.

Neither US Environmental Protection Agency (EPA) nor State of California holds HIPAA certification.

Neither US Environmental Protection Agency (EPA) nor State of California 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.

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

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

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

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

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