iGaming cybersecurity: what regulators and PSPs ask for

iGaming cybersecurity across gaming regulators, payment partners and EU law: MGA, UKGC, PCI DSS v4.0.1, GDPR, DORA and NIS2, and the attacks behind them.

8 min read
iGaming cybersecurity: what regulators and PSPs ask for

Key takeaways

  • An iGaming operator answers to three audiences at once: the gaming regulator of each licence, the payment partners that take deposits, and EU law on data, payments and, for some group entities, DORA or NIS2.
  • The UKGC bases its remote gambling security requirements on Annex A of ISO/IEC 27001:2022, and the MGA exempts several documents for applicants with a relevant ISO certificate: ISO/IEC 27001 is a natural backbone.
  • PCI DSS v4.0.1 is required at the discretion of payment brands and acquirers; since 31 March 2025 it includes controls on payment page scripts, tamper detection on payment pages and automated audit log reviews.
  • Gaming is not a DORA financial entity nor a NIS2 sector, but a group company with a payment or e-money licence falls under DORA, and cloud or managed ICT services can bring an entity into NIS2.
  • Denial of service, account takeover, bonus abuse and payment page tampering map directly onto MGA, UKGC and PCI DSS controls, and a single incident playbook has to track MGA, GDPR, acquirer and, where relevant, DORA clocks.

iGaming cybersecurity is judged by three audiences at once: the gaming regulator of every market you hold a licence in, the payment partners that take your deposits, and EU law on data, payments and, for some group entities, DORA or NIS2. Their requirements overlap heavily. One set of controls, built on ISO/IEC 27001, monitored around the clock and tested against the attacks the sector actually sees, answers most of them. This guide maps who asks for what, the attacks that shape the controls and where to start. For the Malta Gaming Authority's own audits, see our guide to MGA security requirements.

Three audiences, one technical environment

A remote gaming operator rarely answers to a single rulebook. A group may hold a licence in Malta, serve players in other regulated markets, take card deposits through one or more payment service providers and process personal data under the GDPR. Each of these relationships comes with its own security expectations and its own audit or questionnaire:

  • Gaming regulators check the systems that hold player accounts, game outcomes and money.
  • Payment partners check how card data and payment pages are handled, mainly through PCI DSS.
  • EU law sets breach notification under the GDPR and, only for the right entities, the ICT risk rules of DORA and NIS2.

The controls behind the three are largely the same: access control, logging, change management, testing, incident response. What differs is the evidence each audience wants and the clock each one runs.

Gaming regulators: one licence per market

Malta

The MGA checks licensees through a system audit before go-live, a system review on the live environment and compliance audits during the licence; most of the technical rules they check sit in Directive 3 of 2018. Two points matter for the wider picture. Article 37(2) of the directive asks licensees to notify the Authority forthwith, and no later than three working days after, of any information security breach that adversely affects the confidentiality of player information and of any breach that keeps players out of their accounts for more than twelve hours. And the risk assessment of essential components covers the risks listed in the directive's First Schedule, which include denial of service. The full detail is in our MGA guide.

Great Britain

Operators serving players in Great Britain also meet the Gambling Commission's Remote gambling and software technical standards (RTS). Chapter 4 sets the security requirements and states that they are based on the relevant sections of Annex A to ISO/IEC 27001:2022. They apply to the systems the Commission calls critical: systems handling sensitive customer information such as card details, authentication data and account balances; random number generation; storage of results; the points of entry to and exit from those systems; and networks carrying sensitive customer information.

The selected controls include supplier relationships and the ICT supply chain (5.19 to 5.22), cloud services (5.23), incident management (5.24 to 5.26), privileged access (8.2), logging (8.15), network segregation (8.22), secure development (8.25) and change management (8.32). The RTS annex lists the licence categories that need the full security audit by an independent auditor, among them remote casino, remote bingo, general remote betting (excluding telephone-only betting and trading rooms) and all host licences.

Cyprus

In Cyprus, betting is regulated by the National Betting Authority under the Betting Law of 2019 (L.37(I)/2019), and online betting operators hold a Class B licence. The Authority issues binding directives to its licensees, so a group adding a Cypriot licence adds one more set of rules to map against the same technical environment.

Payment partners: PCI DSS and strong customer authentication

PCI DSS applies to entities that store, process or transmit cardholder data. The PCI Security Standards Council states that whether an entity is required to comply is at the discretion of the organisations that manage compliance programmes, such as a payment brand or an acquirer. In practice the questionnaire arrives from your acquirer or payment service provider.

The current version is PCI DSS v4.0.1, which the Council describes as a limited revision with no added or deleted requirements. The requirements that v4.0 introduced as best practice became mandatory on 31 March 2025, and several of them hit gaming operators directly, because deposits happen on web pages and inside apps:

  • Public-facing web applications sit behind an automated technical control that continually detects and prevents web-based attacks, and either blocks them or raises an alert that is immediately investigated (requirement 6.4.2).
  • Payment page scripts loaded in the player's browser are authorised, checked for integrity and kept in an inventory with a written justification (6.4.3).
  • A change- and tamper-detection mechanism alerts staff to unauthorised changes to the HTTP headers and content of payment pages, at least once every seven days or at the frequency set by a targeted risk analysis (11.6.1).
  • Audit log reviews, already required at least once daily for security events and critical systems (10.4.1), are performed by automated mechanisms (10.4.1.1).
  • Multi-factor authentication covers all access into the cardholder data environment (8.4.2).

Around these sit the long-standing ones: external vulnerability scans at least once every three months by an Approved Scanning Vendor (11.3.2), internal and external penetration tests at least once every 12 months and after significant changes (11.4), and an incident response plan that covers notifying payment brands and acquirers (12.10.1). How much of this applies to you depends on how card data reaches your systems; a payment page hosted by your provider reduces the scope but does not remove it, and your acquirer confirms which validation applies.

Payments also bring strong customer authentication. Under article 97 of PSD2 (Directive (EU) 2015/2366), the payment service provider applies it when the payer initiates an electronic payment, and for remote payments it dynamically links the transaction to a specific amount and payee. The obligation sits with the provider, but it shapes your deposit flow and the fraud signals you receive.

EU law: GDPR always, DORA and NIS2 only through the right entity

GDPR. A personal data breach is notified to the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people (article 33 of Regulation (EU) 2016/679). For a Malta licensee this runs alongside the MGA's three working days: two clocks, two recipients, often for the same incident.

DORA. Regulation (EU) 2022/2554 applies to the financial entities in its article 2(1), among them payment institutions and electronic money institutions. A gaming operator is not on the list. If a group company holds a payment or e-money licence, that company is in scope, and our guides on DORA in Malta and DORA in Cyprus cover what follows. A group IT company that provides ICT services to it is an ICT third-party service provider under article 3(19), and the contract between them carries the provisions of article 30.

NIS2. Gambling is not a sector in the annexes of Directive (EU) 2022/2555. A group entity can still come into scope through another listed activity, such as cloud, data centre or managed ICT services provided to other businesses, if it meets the size thresholds. Scope is assessed entity by entity: see NIS2 in Malta and NIS2 in Cyprus.

The attacks that shape the controls

Requirements describe controls; the sector's attack patterns decide where those controls are under pressure. Four of them map directly onto the requirements above.

Denial of service

Traffic floods aimed at the platform or its login and payment endpoints. The MGA already treats denial of service as a risk to assess, and an attack that keeps players out of their accounts for more than twelve hours can trigger the three-working-day notification. Controls: upstream filtering sized for peak traffic, capacity tests before high-traffic events and a runbook that names who decides on notification.

Account takeover

Credential stuffing with passwords leaked elsewhere, followed by a change of withdrawal details. The MGA System Audit Checklist already asks for hashed passwords and lock-out after failed logons. What closes the gap is detection: alerts on login spikes from new devices or networks, on changes to payout details and on withdrawals shortly after a login from an unusual location.

Bonus abuse and multi-accounting

Networks of linked accounts created with automated tools to collect welcome offers. It is a fraud problem more than a security one, but it uses the same signals: device, IP address, payment instrument, behaviour. Teams that share those signals between fraud and security operations see the pattern earlier.

Payment page tampering

Malicious scripts injected into the deposit page to copy card data in the browser, including through scripts loaded from third parties. This is the reason PCI DSS 6.4.3 and 11.6.1 exist: an inventory of scripts and an alert when the page changes.

Behind all four sits a common entry point: back-office and supplier access. Game providers, platform suppliers, affiliates and outsourced support teams connect to critical systems. Privileged access, multi-factor authentication and supplier controls are where the UKGC, PCI DSS and the MGA converge.

One control set, mapped to every audience

  1. Use ISO/IEC 27001 as the backbone. The UKGC builds its security requirements on Annex A of the 2022 edition, and the MGA's System Documentation Checklist exempts several documents if the applicant holds a relevant ISO certificate. An ISO/IEC 27001 management system gives you one risk assessment and one set of policies to map against each regulator.
  2. Collect logs once, monitor around the clock. Daily log review for PCI DSS, audit trails on regulatory data for the MGA, and notification clocks of 72 hours and three working days all assume you detect the incident in time. A managed detection and response service on a platform such as Google Security Operations, with Google Threat Intelligence for context on the groups targeting the sector, covers nights and weekends as well as office hours.
  3. Test against the sector's attacks. Plan penetration tests around the PCI DSS cycle and around major releases, and include account takeover, payment page and back-office scenarios, not only the network perimeter.
  4. Write one incident playbook with every clock in it. MGA, other gaming regulators, the GDPR supervisory authority, acquirers and payment brands, and DORA reporting if a group entity is in scope. Name who notifies whom.
  5. Keep one evidence file. Access reviews, change logs, scan and test reports, incident records. The same file answers the MGA auditor, the UKGC security audit and the acquirer's questionnaire.

If you want to see how your current setup maps against your regulators and payment partners, talk to us.

Frequently asked questions

PCI DSS applies to entities that store, process or transmit cardholder data. The PCI Security Standards Council states that whether an entity is required to comply is at the discretion of the organisations that manage compliance programmes, such as payment brands and acquirers, so in practice your acquirer or payment service provider sets the validation. A payment page hosted by your provider reduces the scope but does not remove it.
Not as gaming operators. DORA (Regulation (EU) 2022/2554) applies to the financial entities listed in its article 2(1), such as payment institutions and electronic money institutions. If a company in a gaming group holds one of those licences, that company is in scope, and a group IT company providing ICT services to it is an ICT third-party service provider whose contract carries the provisions of article 30.
Gambling is not a sector in the annexes of the NIS2 Directive (Directive (EU) 2022/2555). A group entity can still come into scope through another listed activity, such as cloud, data centre or managed ICT services provided to other businesses, if it meets the size thresholds. Scope is assessed entity by entity under the national transposition.
Under article 37(2) of Directive 3 of 2018, licensees notify the MGA forthwith, and no later than three working days after, of any information security breach that adversely affects the confidentiality of player information and of any breach that keeps players out of their accounts for more than twelve hours. If personal data is involved, the GDPR notification to the supervisory authority runs in parallel, within 72 hours where feasible.
It covers a large part of the ground but does not replace their audits. The UKGC bases its remote gambling security requirements on Annex A of ISO/IEC 27001:2022 and requires a full security audit by an independent auditor for listed licence categories, while the MGA exempts several documents for applicants with a relevant ISO certificate but still runs its own system and compliance audits.

Let's talk about your security.

A 30-minute call to understand where you stand today and tell you, with no commitment, where it pays to start.

Book a call