Comparison Overview

US Environmental Protection Agency (EPA)

VS

City of Los Angeles

US Environmental Protection Agency (EPA)

1200 Pennsylvania Ave. N.W., Washington, DC, US, 20004
Last Update: 2025-11-26
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,703
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

City of Los Angeles

200 North Spring St., Los Angeles, California, US, 90012
Last Update: 2025-11-22

The City of Los Angeles employs more than 45,000 people in a wide range of careers. Visit our website for information on current openings, including regular civil service positions, exempt and emergency appointment opportunities, in addition to internships! The City of Los Angeles is a Mayor-Council-Commission form of government, as originally adopted by voters of the City of Los Angeles, effective July 1, 1925, and reaffirmed by a new Charter effective July 1, 2000. A Mayor, City Controller, and City Attorney are elected by City residents every four years. Fifteen City Council members representing fifteen districts are elected by the people for four-year terms, for a maximum of two terms. Members of Commissions are generally appointed by the Mayor, subject to the approval of the City Council. General Managers of the various City departments are also appointed by the Mayor, subject to confirmation by the City Council. Most employees of the City are subject to the civil service provisions of the City Charter.

NAICS: 92
NAICS Definition: Public Administration
Employees: 15,569
Subsidiaries: 4
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-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/city-of-los-angeles.jpeg
City of Los Angeles
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
City of Los Angeles
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 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for City of Los Angeles in 2025.

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 — City of Los Angeles (X = Date, Y = Severity)

City of Los Angeles 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/city-of-los-angeles.jpeg
City of Los Angeles
Incidents

No Incident

FAQ

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

Historically, City of Los Angeles company has disclosed a higher number of cyber incidents compared to US Environmental Protection Agency (EPA) company.

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

Neither City of Los Angeles company nor US Environmental Protection Agency (EPA) company has reported experiencing a ransomware attack publicly.

Neither City of Los Angeles company nor US Environmental Protection Agency (EPA) company has reported experiencing a data breach publicly.

Neither City of Los Angeles company nor US Environmental Protection Agency (EPA) company has reported experiencing targeted cyberattacks publicly.

Neither US Environmental Protection Agency (EPA) company nor City of Los Angeles company has reported experiencing or disclosing vulnerabilities publicly.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds any compliance certifications.

Neither company holds any compliance certifications.

City of Los Angeles company has more subsidiaries worldwide compared to US Environmental Protection Agency (EPA) company.

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

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds SOC 2 Type 1 certification.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds SOC 2 Type 2 certification.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds ISO 27001 certification.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds PCI DSS certification.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles holds HIPAA certification.

Neither US Environmental Protection Agency (EPA) nor City of Los Angeles 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