International (adopted by state and national gaming regulators)

GLI-33

195 controls. 100 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

195 controls 100 frameworks share controls with it International (adopted by state and national gaming regulators) verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

GLI-33 Event Wagering Evidence & Implementation Kit

195 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
GLI33-Audit-Logging-InfoSec-ChangeControlGLI-33 Audit, Significant Event Logging, Information Security, Change Control, Resilience0
GLI33-CertificationLifecycle-OngoingAuditGLI-33 Certification Lifecycle, Annual Audit, Re-Testing on Change0
GLI33-Crosswalk-PCI-NIST-ISO-StateStandardsGLI-33 Crosswalk to PCI DSS, NIST CSF, ISO 27001, State Technical Standards0
GLI33-EventWagering-System-ArchitectureGLI-33 Event Wagering System Architecture, Wager Engine, Odds Engine and Risk Management81
GLI33-Geolocation-Mobile-Internet-WageringGLI-33 Geolocation Verification, Mobile and Internet Wagering Security, Session Management0
GLI33-Implementation-Roadmap-Roles-ToolingGLI-33 Implementation Roadmap, Organizational Roles, Tooling and Metrics0
GLI33-PAM-KYC-AML-PaymentsGLI-33 Player Account Management, KYC, AML, Payment Processing and Account Lifecycle38
GLI33-ResponsibleGaming-Integrity-AntiFraudGLI-33 Responsible Gaming, Self-Exclusion, Integrity Monitoring, Anti-Fraud and Collusion Detection0
GLI33-Scope-GLI-CertModelGLI-33 Scope, Gaming Laboratories International Certification Model, GLI-19/21/27 Coordination0
GLI33-Sports-Integrity-DataProviders-ComplianceGLI-33 Sports Event Data Integrity, Provider Certification and Regulatory Reporting16
GLI33-StateRegulator-Adoption-MultistateGLI-33 State Regulator Adoption, Multi-State Mobile, International Adoption0
GLI33-Status-2024-2025-Pipeline-Brazil-AIGLI-33 2024-2025 Update Pipeline, Brazil Market Entry, AI Anti-Fraud, Cryptocurrency0
2.12.1 Introduction0
2.1.12.1.1 General Statement0
2.22.2 System Clock Requirements0
2.2.12.2.1 Sy tem Clock0
2.2.22.2.2 Time Synchronization0
2.32.3 Control Program Requirements0
2.3.22.3.2 Control Program Self-Verification0
2.3.32.3.3 Control Program Independent Verification0
2.3.42.3.4 Shutdown and Recovery0
2.42.4 Wagering Management0
2.4.12.4.1 Wagering Management0
2.52.5 Player Account Management0
2.5.22.5.2 Regi tration and Verification0
2.5.32.5.3 Player Acce0
2.5.42.5.4 Player Inactivity0
2.5.52.5.5 Limitation and Exclu ion0
2.5.62.5.6 Player Fund Maintenance0
2.5.72.5.7 Tran action Log or Account Statement0
2.5.82.5.8 Player Loyalty Program0
2.62.6 Wagering Instrument Functionality0
2.6.12.6.1 General Statement0
2.72.7 Location Requirements for Remote Wagering0
2.7.22.7.2 Location Fraud Prevention0
2.7.32.7.3 Location Detection for Remote Wagering on a WLAN0
2.7.42.7.4 Location Detection for Remote Wagering Over the Internet0
2.82.8 Information to be Maintained0
2.8.12.8.1 Data Retention and Time Stamping0
2.8.22.8.2 Wager Record Information0
2.8.32.8.3 Market Information0
2.8.42.8.4 Conte t/Tournament Information0
2.8.52.8.5 Player Account Information0
2.8.62.8.6 Promotion/Bonu Information0
2.8.72.8.7 Wagering Device Information0
2.8.82.8.8 Significant Event Information0
2.8.92.8.9 U er Acce Information0
2.92.9 Reporting Requirements0
2.9.12.9.1 General Reporting Requirement0
2.9.22.9.2 Operator Revenue Report0
2.9.32.9.3 Operator Liability Report0
2.9.42.9.4 Future Event Report0
2.9.52.9.5 Significant Event and Alteration Report0
3.13.1 Introduction0
3.23.2 Wagering Software0
3.2.23.2.2 Software Identification0
3.2.33.2.3 Software Validation0
3.2.43.2.4 U er Interface Requirement0
3.2.53.2.5 Simultaneou Input0
3.2.63.2.6 Wager Record Printer0
3.2.73.2.7 Communication0
3.33.3 Self-Service Wagering Devices0
3.3.13.3.1 General Statement0
3.43.4 POS Wagering Devices0
3.4.23.4.2 Touch Screen Di play0
3.4.33.4.3 Printing Wager Record0
3.4.43.4.4 Wirele POS Wagering Device0
3.53.5 Remote Wagering Devices0
3.5.13.5.1 General Statement0
3.5.23.5.2 Client-Server Interaction0
3.5.33.5.3 Compatibility Verification0
3.5.43.5.4 Software Content0
3.5.53.5.5 Cookie0
3.5.63.5.6 Information Acce0
4.14.1 Introduction0
4.24.2 Wagering Displays and Information0
4.2.14.2.1 Po ting of Wagering Rule0
4.2.24.2.2 Dynamic Wagering Information0
4.2.34.2.3 Player Re ource /Feature0
4.34.3 Wager Placement0
4.3.24.3.2 Placement of a Wager0
4.3.34.3.3 Automatic Acceptance of Change in Wager0
4.3.44.3.4 Wager Record0
4.3.54.3.5 Wagering Period Clo e0
4.3.64.3.6 Free Play Mode0
4.44.4 Results and Payment0
4.4.14.4.1 Re ult Di play0
4.4.24.4.2 Payment of Winning0
4.4.34.4.3 Winning Wager Record Redemption0
4.54.5 Virtual Event Wagering0
4.5.24.5.2 Randomization and Virtual Event0
4.5.34.5.3 Virtual Event Selection Proce0
4.5.44.5.4 Virtual Event Di play0
4.5.54.5.5 Simulation of Phy ical Object0
4.5.64.5.6 Phy ic Engine0
4.64.6 External Wagering Systems0
4.6.24.6.2 Information0
4.6.34.6.3 Wager0
4.6.44.6.4 Re ult0
A.1A.1 Introduction0
A.2A.2 Internal Control Procedures0
A.2.1A.2.1 Internal Control Procedure0
A.2.2A.2.2 Information Management0
A.2.3A.2.3 Ri k Management0
A.2.4A.2.4 Re tricted Player0
A.3A.3 Player Account Controls0
A.3.1A.3.1 Regi tration and Verification0
A.3.2A.3.2 Fraudulent Account0
A.3.3A.3.3 Term and Condition0
A.3.4A.3.4 Privacy Policy0
A.3.5A.3.5 Player Data Security0
A.3.6A.3.6 Financial Tran action0
A.3.7A.3.7 Limitation0
A.3.8A.3.8 Exclu ion0
A.3.9A.3.9 Inactive Account0
A.4A.4 General Operating Procedures0
A.4.1A.4.1 Operator Re erve0
A.4.2A.4.2 Protection of Player Fund0
A.4.3A.4.3 Taxation0
A.4.4A.4.4 Complaint/Di pute Proce0
A.4.5A.4.5 Player Protection Information0
A.5A.5 Wagering Rules and Content0
A.5.1A.5.1 Wagering Rule0
A.5.2A.5.2 Wagering Rule Content0
A.5.3A.5.3 Promotion and/or Bonu e0
A.5.4A.5.4 Conte t /Tournament0
A.6A.6 Wagering Procedures and Controls0
A.6.1A.6.1 Odd /Payout and Price0
A.6.2A.6.2 Stati tic /Line Data0
A.6.3A.6.3 Su pending Market or Event0
A.6.4A.6.4 Wager Cancellation0
A.6.5A.6.5 Wagering Period0
A.6.6A.6.6 Re ult0
A.6.7A.6.7 Winning Wager Payment0
A.6.8A.6.8 Virtual Event0
A.7A.7 Wagering Venue Specifications0
A.7.1A.7.1 Venue Verification Audit0
A.7.2A.7.2 Wagering Equipment0
A.7.3A.7.3 Wagering Operation0
A.7.4A.7.4 Surveillance and Recording0
A.8A.8 Monitoring Procedures0
A.8.1A.8.1 Monitoring for Collu ion and Fraud0
A.8.2A.8.2 Anti-Money Laundering (AML) Monitoring0
A.8.3A.8.3 Location Service Provider Monitoring0
B.1B.1 Introduction0
B.2B.2 System Operation and Security0
B.2.1B.2.1 Sy tem Procedure0
B.2.2B.2.2 Phy ical Location of Server0
B.2.3B.2.3 Logical Acce Control0
B.2.4B.2.4 U er Authorization0
B.2.5B.2.5 Server Programming0
B.2.6B.2.6 Verification Procedure0
B.2.7B.2.7 Electronic Document Retention Sy tem0
B.2.8B.2.8 A et Management0
B.3B.3 Backup and Recovery0
B.3.1B.3.1 Data Security0
B.3.2B.3.2 Data Alteration0
B.3.3B.3.3 Backup Frequency0
B.3.4B.3.4 Storage Medium Backup0
B.3.5B.3.5 Sy tem Failure0
B.3.6B.3.6 Accounting of Ma ter Re et0
B.3.7B.3.7 Recovery Requirement0
B.3.8B.3.8 Uninterruptible Power Supply (UPS) Support0
B.3.9B.3.9 Bu ine Continuity and Di a ter Recovery Plan0
B.4B.4 Communications0
B.4.2B.4.2 Connectivity0
B.4.3B.4.3 Communication Protocol0
B.4.4B.4.4 Communication Over Internet/Public Network0
B.4.5B.4.5 Wirele Local Area Network (WLAN) Communication0
B.4.6B.4.6 Network Security Management0
B.5B.5 Third-Party Service Providers0
B.5.1B.5.1 Third-Party Communication0
B.5.2B.5.2 Third-Party Service0
B.6B.6 Technical Controls0
B.6.1B.6.1 Domain Name Service (DNS) Requirement0
B.6.2B.6.2 Cryptographic Control0
B.6.3B.6.3 Encryption Key Management0
B.7B.7 Remote Access and Firewalls0
B.7.1B.7.1 Remote Acce Security0
B.7.2B.7.2 Remote Acce Procedure and Gue t Account0
B.7.3B.7.3 Remote Acce Activity Log0
B.7.4B.7.4 Firewall0
B.7.5B.7.5 Firewall Audit Log0
B.7.6B.7.6 Firewall Rule Review0
B.8B.8 Change Management0
B.8.2B.8.2 Program Change Control Procedure0
B.8.3B.8.3 Software Development Life Cycle0
B.8.4B.8.4 Patche0
B.9B.9 Periodic Security Testing0
B.9.1B.9.1 Technical Security Te ting0
B.9.2B.9.2 Vulnerability A e ment0
B.9.3B.9.3 Penetration Te ting0
B.9.4B.9.4 Information Security Management Sy tem (ISMS) Audit0
B.9.5B.9.5 Cloud Service Audit0
GLIGLI-33 Standards for Event Wagering Systems v1.1: purpose, interpretation, testing and audit model, status0

Tell me when GLI-33 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

  • Role inventory + RACI
  • Metrics + management review
  • Annual cycle documentation
  • Role inventory + RACI + DPO designation
  • Operational controls + tooling investment
  • Reporting process + content index
  • Pipeline tracking + impact assessment
  • Pipeline-tracking + implementation plan per rule
  • SEC Reg S-P readiness 2025-2026
  • Section 1033 readiness 2026-2030

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

What this page is

A control-level reference for GLI-33, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition