Topic · 21 articles
Every article we have filed under Technical Standards, newest first, each one tied back to the standards and regulators it concerns.
Three major regulators set distinct game round logging obligations covering mandatory fields, retention periods, and immutability. Map each requirement before your next audit.
AGLC SRIG sets exacting technical obligations for Alberta's July 2026 launch: ATF certification, API integration, log retention, and platform-level RG enforcement. Built for CTOs and QA teams.
Map which iGaming jurisdictions mandate on-soil servers, which accept replication, and which are outcomes-based. Architecture patterns and B2B cost implications included.
PAM vendors are accountable parties for data, RG hooks, AML logs, and change control across UKGC, MGA, AGCO, and AGLC frameworks. Here is what that means operationally.
Compliance teams across licensed iGaming operations routinely misconfigure their ISO/IEC 27001 implementations, treating certification as a point-in-time exercise rather than a functioning ISMS. This article examines the most consequential mistakes, how they map to UKGC and MGA regulatory obligations, and what auditors are actually testing for.
MGA licensees facing a compliance audit must present a structured evidence pack covering technical infrastructure, transaction logging, change control, and information security. This article maps the audit scope defined in the MGA Compliance Audit Manual (MGA/G/001) and the MGA Technical Infrastructure requirements to the operational documentation your team must maintain.
Compliance teams preparing for product certification must understand the distinct scope, architecture requirements, and jurisdictional adoption of GLI-19 (Interactive Gaming Systems) and GLI-33 (Event Wagering Systems) before selecting a certification path. This article maps the key differences, overlapping requirements, and practical decision points.