Comparison Overview

Peppermill Inc

VS

GoldBet

Peppermill Inc

US, 89502
Last Update: 2025-11-28

The Peppermill Hotel Casino is a resort located in Reno, Nevada, and it is currently owned by Peppermill Casinos Inc. It first opened in 1971. This resort includes a pool, 1,100 hotel rooms, and several shopping areas and a 80,000 sq ft (7,400 m2) casino. Peppermill was originally founded as a coffeeshop and lounge in 1971 by Bill Paganetti and Nat Carasali when they first purchased the business. In 1979, Tom and Albert Seeno joined to form what is now known as Peppermill Casinos, Inc. with other properties now in Henderson and West Wendover.

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

GoldBet

Via della Maglianella, 65, Rome, 00166, IT
Last Update: 2025-11-23
Between 750 and 799

GoldBet è un nuovo Concessionario di Stato Italiano per le scommesse ed il gioco a distanza, con sede a Roma, che opera in Italia con una rete di punti vendita (PdV) ed un’offerta completa attraverso il canale online/mobile. In Italia GoldBet garantisce oggi la presenza di una rete costituita da 989 PdV autorizzati, in 18 diverse regioni. Attraverso il canale online/mobile, tramite il sito www.goldbet.it propone un’offerta completa con scommesse, giochi da casinò, poker, bingo e skill game.

NAICS: 7132
NAICS Definition: Gambling Industries
Employees: 655
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/defaultcompany.jpeg
Peppermill Inc
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/goldbet.jpeg
GoldBet
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
Peppermill Inc
100%
Compliance Rate
0/4 Standards Verified
GoldBet
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 Peppermill Inc in 2025.

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

No incidents recorded for GoldBet in 2025.

Incident History — Peppermill Inc (X = Date, Y = Severity)

Peppermill Inc cyber incidents detection timeline including parent company and subsidiaries

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

GoldBet cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Peppermill Inc
Incidents

Date Detected: 10/2014
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/goldbet.jpeg
GoldBet
Incidents

No Incident

FAQ

GoldBet company demonstrates a stronger AI Cybersecurity Score compared to Peppermill Inc company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Peppermill Inc company has historically faced a number of disclosed cyber incidents, whereas GoldBet company has not reported any.

In the current year, GoldBet company and Peppermill Inc company have not reported any cyber incidents.

Neither GoldBet company nor Peppermill Inc company has reported experiencing a ransomware attack publicly.

Peppermill Inc company has disclosed at least one data breach, while the other GoldBet company has not reported such incidents publicly.

Neither GoldBet company nor Peppermill Inc company has reported experiencing targeted cyberattacks publicly.

Neither Peppermill Inc company nor GoldBet company has reported experiencing or disclosing vulnerabilities publicly.

Neither Peppermill Inc nor GoldBet holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Peppermill Inc company nor GoldBet company has publicly disclosed detailed information about the number of their subsidiaries.

GoldBet company employs more people globally than Peppermill Inc company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Peppermill Inc nor GoldBet holds SOC 2 Type 1 certification.

Neither Peppermill Inc nor GoldBet holds SOC 2 Type 2 certification.

Neither Peppermill Inc nor GoldBet holds ISO 27001 certification.

Neither Peppermill Inc nor GoldBet holds PCI DSS certification.

Neither Peppermill Inc nor GoldBet holds HIPAA certification.

Neither Peppermill Inc nor GoldBet 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