Comparison Overview

Ohio Lottery Commission

VS

US Environmental Protection Agency (EPA)

Ohio Lottery Commission

615 West Superior Avenue, None, Cleveland, OH, US, 44113
Last Update: 2025-11-25
Between 650 and 699

At the Ohio Lottery, we’re optimistic, innovative, and fun. We’ve been bringing fun lottery games to Ohioans for more than 40 years, all the while raising money in support of education in Ohio. The Ohio Lottery Commission was created in May 1973 by a voter-approved constitutional amendment. Today, the Ohio Lottery has grown to offer customers a variety of games including scratch offs, Keno, instant win and monitor games and the jackpot games Mega Millions, Powerball, Pick 3, Pick 4 and Pick 5, Rolling Cash 5 and Classic Lotto. We have a game for every player at over 9,100 licensed retail locations and seven racinos across the state. Operating entirely on revenue from game sales, the Ohio Lottery has generated over $29 billion for education in Ohio since 1974. Learn more about the Ohio Lottery at www.ohiolottery.com. Learn more about the Ohio Lottery at www.youtube.com/ohiolottery

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

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ohio-lottery-commission.jpeg
Ohio Lottery Commission
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-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
Compliance Summary
Ohio Lottery Commission
100%
Compliance Rate
0/4 Standards Verified
US Environmental Protection Agency (EPA)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ohio Lottery Commission in 2025.

Incidents vs Government Administration Industry Average (This Year)

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

Incident History — Ohio Lottery Commission (X = Date, Y = Severity)

Ohio Lottery Commission cyber incidents detection timeline including parent company and subsidiaries

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ohio-lottery-commission.jpeg
Ohio Lottery Commission
Incidents

Date Detected: 12/2023
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/us-epa.jpeg
US Environmental Protection Agency (EPA)
Incidents

No Incident

FAQ

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

Ohio Lottery Commission 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, US Environmental Protection Agency (EPA) company and Ohio Lottery Commission company have not reported any cyber incidents.

Neither US Environmental Protection Agency (EPA) company nor Ohio Lottery Commission company has reported experiencing a ransomware attack publicly.

Ohio Lottery Commission company has disclosed at least one data breach, while the other US Environmental Protection Agency (EPA) company has not reported such incidents publicly.

Neither US Environmental Protection Agency (EPA) company nor Ohio Lottery Commission company has reported experiencing targeted cyberattacks publicly.

Neither Ohio Lottery Commission company nor US Environmental Protection Agency (EPA) company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds any compliance certifications.

Neither company holds any compliance certifications.

Both US Environmental Protection Agency (EPA) company and Ohio Lottery Commission company have a similar number of subsidiaries worldwide.

US Environmental Protection Agency (EPA) company employs more people globally than Ohio Lottery Commission company, reflecting its scale as a Government Administration.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds SOC 2 Type 1 certification.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds SOC 2 Type 2 certification.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds ISO 27001 certification.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds PCI DSS certification.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) holds HIPAA certification.

Neither Ohio Lottery Commission nor US Environmental Protection Agency (EPA) 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