Comparison Overview

Virginia Lottery

VS

BJ's Bingo

Virginia Lottery

600 East Main Street, Richmond, VA, 23219, US
Last Update: 2025-11-25
Between 750 and 799

At the Virginia Lottery, we take playing seriously. Fun matters. Excitement matters. And so does the education of Virginia's youngest residents. It's the reason we play so enthusiastically. Every time you scratch a ticket or pick your numbers for the big jackpot, you are creating winners in education all over Virginia. In Fiscal Year 2024, the Lottery contributed more than $934 million to Virginia's public schools.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 371
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

BJ's Bingo

None
Last Update:
Between 750 and 799

BJs Bingo is a family run group of purpose built modern Bingo clubs, consider by many to be one of the leading independent operators. We are highly focused on our customer service & experience, opening our first club in Reading in 2002, followed by Leigh in 2003 & then Kitt's Green in 2007. We are market leaders in our areas and pride ourselves on our innovative & technology driven approach to the industry. We are often a testing house for major suppliers for latest equipment and ideas. We have also developed our own sister company Shipley Creative which provides digital media & print to the whole gaming industry and beyond!

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 89
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/virginia-lottery.jpeg
Virginia Lottery
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/bjs-bingo.jpeg
BJ's Bingo
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
Virginia Lottery
100%
Compliance Rate
0/4 Standards Verified
BJ's Bingo
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Gambling Facilities and Casinos Industry Average (This Year)

No incidents recorded for Virginia Lottery in 2025.

Incidents vs Gambling Facilities and Casinos Industry Average (This Year)

No incidents recorded for BJ's Bingo in 2025.

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

Virginia Lottery cyber incidents detection timeline including parent company and subsidiaries

Incident History — BJ's Bingo (X = Date, Y = Severity)

BJ's Bingo cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/virginia-lottery.jpeg
Virginia Lottery
Incidents

No Incident

https://images.rankiteo.com/companyimages/bjs-bingo.jpeg
BJ's Bingo
Incidents

No Incident

FAQ

Virginia Lottery company demonstrates a stronger AI Cybersecurity Score compared to BJ's Bingo company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, BJ's Bingo company has disclosed a higher number of cyber incidents compared to Virginia Lottery company.

In the current year, BJ's Bingo company and Virginia Lottery company have not reported any cyber incidents.

Neither BJ's Bingo company nor Virginia Lottery company has reported experiencing a ransomware attack publicly.

Neither BJ's Bingo company nor Virginia Lottery company has reported experiencing a data breach publicly.

Neither BJ's Bingo company nor Virginia Lottery company has reported experiencing targeted cyberattacks publicly.

Neither Virginia Lottery company nor BJ's Bingo company has reported experiencing or disclosing vulnerabilities publicly.

Neither Virginia Lottery nor BJ's Bingo holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Virginia Lottery company nor BJ's Bingo company has publicly disclosed detailed information about the number of their subsidiaries.

Virginia Lottery company employs more people globally than BJ's Bingo company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Virginia Lottery nor BJ's Bingo holds SOC 2 Type 1 certification.

Neither Virginia Lottery nor BJ's Bingo holds SOC 2 Type 2 certification.

Neither Virginia Lottery nor BJ's Bingo holds ISO 27001 certification.

Neither Virginia Lottery nor BJ's Bingo holds PCI DSS certification.

Neither Virginia Lottery nor BJ's Bingo holds HIPAA certification.

Neither Virginia Lottery nor BJ's Bingo 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