Security rules

Security requirements by market

What gambling regulators and related laws require of operators' information security, with each requirement tied to its official source and dated.

At a glance

MarketSecurity frameworkIndependent testingBreach notice to gambling regulator
Great BritainRTS section 4, based on ISO/IEC 27001:2022 Annex AAnnual security audit; first within 6 months of licenseWithin 5 working days (LCCP 15.2.1)
OntarioA recognized industry standard framework (5.01)Regular independent assessments (5.11)Immediate (notification matrix I1)
MichiganISO 27001 or similar policy reviewWithin 90 days of launch, then annual, with penetration testsNot found in R 432.638
NevadaBest practices such as CIS v8, ISO/IEC 27001, NIST SP 800-53Annual review for Group I licenseesWithin 24 hours (Reg. 5.260)
EUGDPR security; NIS2 does not list gamblingNational rules varyNational rules vary; GDPR 72 hours to data authority
Summary only; see each page for sources. Checked 24 October 2026.

All rules pages

Security rules · Canada

Ontario: AGCO security standards

What the AGCO Registrar's Standards require on IT frameworks, monitoring and independent assessments, and the immediate notification rule for breaches.

Security rules · Europe

Europe: GDPR and NIS2 for gambling

GDPR's 72-hour breach notification, NIS2's sector lists (gambling is not one), and where national gambling regulators add technical rules.

Comparison

Breach notification deadlines compared

One table of who to tell and how fast after a security incident: gambling regulators and data protection authorities in GB, Ontario, the US and the EU.

Rules pages are reviewed at least every three months. See how we check sources or report a change via the contact page.