Comparison Overview

Svenska Spel

VS

Michigan Lottery

Svenska Spel

Katarinavägen 15, Stockholm, 11645, SE
Last Update: 2025-11-27
Between 750 and 799

Svenska Spel-koncernen består av cirka 1 000 medarbetare och omfattar tre affärsområden: 🎯 Sport & Casino med välkända varumärken som Stryktipset och Oddset 🍀 Tur med favoriterna Triss och Lotto 🕹️ Vegas med värdeautomater på restauranger och bingohallar Vi har kontor i Visby och Stockholm där vi träffas, teamar upp och skapar framtidens spelupplevelser tillsammans. Vi är också stolta över att vara Sveriges största idrottssponsor, från ungdom till elit. Är du nyfiken på Svenska Spel? Läs mer om oss på vår karriärsida, career.svenskaspel.se eller på om.svenskaspel.se. Följ oss även på: Instagram - @viarsvenskaspel

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

Michigan Lottery

101 East Hillsdale Street, Lansing, MI, 48933, US
Last Update: 2025-11-27

The Michigan Lottery was founded in 1972 to provide entertaining games of chance which deliver revenue to the state School Aid Fund. Today, the Michigan Lottery has a retail network of more than 10,500 local businesses offering our portfolio of products. About 97 cents of every dollar spent on Lottery tickets is returned to the state in the form of contributions to the state School Aid Fund, prizes to players and commissions to vendors and retailers. In the 2023 fiscal year, the Lottery provided more than $1.3 billion for Michigan’s public schools, its seventh record contribution. Since it began in 1972, the Lottery has contributed more than $28 billion to support public education in Michigan. Learn more about the Michigan Lottery at www.michiganlottery.com.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/svenska-spel.jpeg
Svenska Spel
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/michigan-lottery.jpeg
Michigan 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
Compliance Summary
Svenska Spel
100%
Compliance Rate
0/4 Standards Verified
Michigan Lottery
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 Svenska Spel in 2025.

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

No incidents recorded for Michigan Lottery in 2025.

Incident History — Svenska Spel (X = Date, Y = Severity)

Svenska Spel cyber incidents detection timeline including parent company and subsidiaries

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

Michigan Lottery cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/svenska-spel.jpeg
Svenska Spel
Incidents

No Incident

https://images.rankiteo.com/companyimages/michigan-lottery.jpeg
Michigan Lottery
Incidents

Date Detected: 8/2025
Type:Breach
Motivation: Prevent identity theft and protect consumer privacy by strengthening data breach accountability and corporate safeguards.
Blog: Blog

FAQ

Svenska Spel company demonstrates a stronger AI Cybersecurity Score compared to Michigan Lottery company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Michigan Lottery company has historically faced a number of disclosed cyber incidents, whereas Svenska Spel company has not reported any.

In the current year, Michigan Lottery company has reported more cyber incidents than Svenska Spel company.

Neither Michigan Lottery company nor Svenska Spel company has reported experiencing a ransomware attack publicly.

Michigan Lottery company has disclosed at least one data breach, while Svenska Spel company has not reported such incidents publicly.

Neither Michigan Lottery company nor Svenska Spel company has reported experiencing targeted cyberattacks publicly.

Neither Svenska Spel company nor Michigan Lottery company has reported experiencing or disclosing vulnerabilities publicly.

Neither Svenska Spel nor Michigan Lottery holds any compliance certifications.

Neither company holds any compliance certifications.

Michigan Lottery company has more subsidiaries worldwide compared to Svenska Spel company.

Svenska Spel company employs more people globally than Michigan Lottery company, reflecting its scale as a Gambling Facilities and Casinos.

Neither Svenska Spel nor Michigan Lottery holds SOC 2 Type 1 certification.

Neither Svenska Spel nor Michigan Lottery holds SOC 2 Type 2 certification.

Neither Svenska Spel nor Michigan Lottery holds ISO 27001 certification.

Neither Svenska Spel nor Michigan Lottery holds PCI DSS certification.

Neither Svenska Spel nor Michigan Lottery holds HIPAA certification.

Neither Svenska Spel nor Michigan Lottery 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