Comparison Overview

Abuan Gaming LLC

VS

Bluberi

Abuan Gaming LLC

undefined, Las Vegas, undefined, undefined, US
Last Update: 2025-11-27
Between 750 and 799

Abuan Gaming is a family-owned and operated company. Starting as early as 2005, Ray Abuan developed Lucky 9 table game. Abuan Gaming is currently, but not limited to, developing, leasing, and licensing internally-developed proprietary games, gaming procedures & methods. Lucky 9, our first proprietary game, will be entering field trial on March 23rd, and will be in field trial for 45 days. General release is expected soon after and no later than December 2011.

NAICS: 713
NAICS Definition:
Employees: 1
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Bluberi

7370 DEAN MARTIN DRIVE, LAS VEGAS, NEVADA, 89139, US
Last Update: 2025-11-27
Between 750 and 799

Headquartered in Las Vegas and backed by over 30 years of industry experience, Bluberi is an inventive company dedicated to developing and delivering the highest quality casino gaming experience to players and operators. Our team comprises seasoned, multi-talented innovators focused on bringing gaming to life with entertaining games and high-performing cabinets. Our products are designed to add vitality to gambling and transport players to an energetic world of winning. We are the risk-taking spirit of gambling, and we add imagination and innovation to everything we create. New ideas are Bluberi's lifeblood. We produce, design, create, and execute electric and efficient gaming experiences. Our research and development acumen is born from decades of experience in the casino industry and in-depth knowledge of multiple gaming environments. We strive to create procedures and processes to make everything easier for our customers while consistently elevating technology and vibrancy in our games and cabinets.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 216
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/abuan-gaming-llc.jpeg
Abuan Gaming LLC
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/bluberi.jpeg
Bluberi
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
Abuan Gaming LLC
100%
Compliance Rate
0/4 Standards Verified
Bluberi
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 Abuan Gaming LLC in 2025.

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

No incidents recorded for Bluberi in 2025.

Incident History — Abuan Gaming LLC (X = Date, Y = Severity)

Abuan Gaming LLC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bluberi (X = Date, Y = Severity)

Bluberi cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/abuan-gaming-llc.jpeg
Abuan Gaming LLC
Incidents

No Incident

https://images.rankiteo.com/companyimages/bluberi.jpeg
Bluberi
Incidents

No Incident

FAQ

Abuan Gaming LLC company demonstrates a stronger AI Cybersecurity Score compared to Bluberi company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Bluberi company has disclosed a higher number of cyber incidents compared to Abuan Gaming LLC company.

In the current year, Bluberi company and Abuan Gaming LLC company have not reported any cyber incidents.

Neither Bluberi company nor Abuan Gaming LLC company has reported experiencing a ransomware attack publicly.

Neither Bluberi company nor Abuan Gaming LLC company has reported experiencing a data breach publicly.

Neither Bluberi company nor Abuan Gaming LLC company has reported experiencing targeted cyberattacks publicly.

Neither Abuan Gaming LLC company nor Bluberi company has reported experiencing or disclosing vulnerabilities publicly.

Neither Abuan Gaming LLC nor Bluberi holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Abuan Gaming LLC company nor Bluberi company has publicly disclosed detailed information about the number of their subsidiaries.

Bluberi company employs more people globally than Abuan Gaming LLC company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Abuan Gaming LLC nor Bluberi holds SOC 2 Type 1 certification.

Neither Abuan Gaming LLC nor Bluberi holds SOC 2 Type 2 certification.

Neither Abuan Gaming LLC nor Bluberi holds ISO 27001 certification.

Neither Abuan Gaming LLC nor Bluberi holds PCI DSS certification.

Neither Abuan Gaming LLC nor Bluberi holds HIPAA certification.

Neither Abuan Gaming LLC nor Bluberi 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