Key takeaways
- The MGA has no single security audit: it uses a system audit before go-live, a system review on the live environment and compliance audits during the licence, all run by MGA-approved audit service providers.
- Most technical rules sit in Part III of Directive 3 of 2018: documented key technical setup, prior approval for changes to essential components, two years of change logs, EU or EEA hosting by default and a real-time mirror of regulatory data.
- The System Audit Checklist turns those rules into concrete checks: secure protocols, session time-outs, hashed passwords, encrypted card numbers, need-to-know access, audit trails on regulatory data, replication to Malta.
- Information security is a named key function, held by an individual approved by the MGA, and two kinds of security breach are reported forthwith and no later than three working days after.
- Gambling is not a NIS2 sector, in the directive or in the Maltese Order; a gaming group comes into scope only through another listed activity.
The Malta Gaming Authority does not run one single security audit. It checks licensees' systems through three reviews: a system audit before go-live, a system review on the live environment, and compliance audits throughout the licence. All three are carried out by audit service providers approved by the MGA, using the Gaming Authorisations and Compliance Directive (Directive 3 of 2018) and the MGA's published checklists. This guide sets out what each review looks at, which technical controls come up, what you report and when, and where NIS2 fits. It is a reading of the MGA's own documents, not legal advice.
Which rules set the MGA's security requirements
The framework has four layers, all linked from the MGA's regulatory framework page: the first three are published on legislation.mt, the directive on the MGA's own site.
- The Gaming Act (Cap. 583 of the Laws of Malta), which gives the MGA the power to issue binding directives (article 7(2)).
- The Gaming Authorisations Regulations (S.L. 583.05), whose Fourth Schedule lists the key functions a licensee has to fill, including responsibility for technology and information security.
- The Gaming Compliance and Enforcement Regulations (S.L. 583.06), which give the MGA the power to order compliance audits.
- Directive 3 of 2018, the Gaming Authorisations and Compliance Directive (the version on the MGA site is V2, October 2021), which holds most of the technical rules: key technical setup, essential components, outsourcing and notifications.
On top of these, the MGA publishes the working documents auditors use: the System Documentation Checklist (MGA/F/001), the System Audit Checklist (MGA/F/016), the System Review Checklist (MGA/F/020) and the Compliance Audit Manual (MGA/G/001).
Three reviews: system audit, system review, compliance audit
System audit, before go-live
According to the MGA's guidance note on the application process, once the technical documentation has been reviewed the applicant is asked to deploy its systems on a technical environment ready for go-live, and has 60 days to do so. Within that window the applicant requests an external system audit from a provider on the MGA's approved list, which checks the staged environment against the policies and procedures submitted.
The System Audit Checklist adds that system audits are generally required before a new licence is issued, before a voluntarily suspended licence is re-activated, after major changes to the key technical setup or essential components, and whenever the MGA asks. It comes in four versions: B2C, B2C with distributed ledger technology, B2B service and B2B back-office.
System review, on the live environment
The System Review Checklist builds on the system audit checks and is carried out on the live environment, with the licensee's staff demonstrating functionality and providing evidence. The MGA states that system reviews are generally required one year after a new licence is issued, or earlier if a system audit was not required when the licence was issued.
Compliance audit, throughout the licence
Regulation 5 of S.L. 583.06 allows the MGA to require any authorised person to undergo a compliance audit, on a regular or ad hoc basis, and only audits carried out by MGA-approved auditors are recognised. The regulation does not set a fixed frequency.
The Compliance Audit Manual states that its procedures are mandatory for each compliance review. Its information technology chapter covers system access control, the information security policy, incident response, change management, business partners, business continuity and disaster recovery, backups, system architecture, application architecture and network infrastructure. Auditors also check whether findings from earlier system and compliance audits have been fixed.
The technical requirements auditors check
Key technical setup and essential components
Part III of Directive 3 of 2018 is the core of the security rules. The licensee keeps up-to-date documentation of its key technical setup: hardware with make, model and location, virtual machines, the connections in the network, firewall and router specifications, and installed applications (article 16(1)). Where the directive refers to premises hosting the key technical setup, the same requirements extend to cloud service providers (article 15).
Essential components get stricter treatment. The directive defines them as the components hosting random number generators, jackpots and games, the gaming, player and financial databases, the control system, and any other component the MGA considers critical. For these and for the wider setup:
- changes to essential components need the MGA's prior written approval; in an urgency the licensee may make the strictly necessary changes first and notify within 72 hours (article 16(3));
- audit logs of changes to the key technical setup are kept for at least two years (article 16(6));
- the key technical setup is located in Malta or another EU or EEA state, unless the MGA accepts another location case by case (article 17(1));
- hardware sits in premises which adhere to a high level of information security (article 17(2)), and hosting providers are instructed to assist the MGA's checks (article 17(3));
- a live or real-time mirror server for essential regulatory data stays readily accessible to the MGA (article 17(4));
- a risk assessment of the essential components is filed with the documentation and kept updated, covering the risks in the directive's First Schedule, among them loss of governance, insecure data storage, data leakage in the cloud, unauthorised access through management interfaces and denial of service (article 18).
Controls in the System Audit Checklist
The B2C checklist turns these principles into checks an auditor can verify. Among the security items:
- a secure communication protocol during registration, password change, logon, play, deposits and withdrawals;
- server clocks synchronised with a reputable source;
- physical or logical segregation of data when one setup serves several licences or licensees;
- back-end log-off after at most one hour of inactivity, and player log-off after thirty minutes;
- player passwords stored as one-way cryptographic hashes, and card numbers stored encrypted;
- passwords of at least eight characters that differ from the username, and account lock-out after failed logons;
- access levels granted on a need-to-know basis;
- an audit trail of every change to regulatory data (player, financial and game data);
- a backup inventory in line with the backup policy submitted and, where primary servers are outside Malta, real-time replication of game play, player and financial transactions to a replication server in Malta.
Documented policies
The System Documentation Checklist asks for an information security policy (objectives, data classification and access control, network security, security awareness, training), business continuity and disaster recovery plans with a business impact analysis and routine testing, and a backup procedure with offsite storage and restore testing. For most of these items the checklist notes an exemption if the applicant holds a relevant ISO certificate. It does not name the standard; for an information security management system the usual reference is ISO/IEC 27001. The exemption covers the documents, not the audits: auditors still test whether the controls work.
Who answers for security inside the licensee
Information security is a named key function. Article 6 of Directive 3 of 2018 lists, for B2C remote gaming licensees and for B2B licensees, the technological affairs of the licensee, including the management of the back-end and control system holding essential regulatory data and the network and information security of the licensee. The Fourth Schedule to S.L. 583.05 describes the same role as responsibility for technology, including information security and the operation and management of the control system.
The role is held by a natural person with a certificate of approval from the MGA, valid for three years (article 10). Where no approved person holds a key function, responsibility vests in the directors (article 5A).
Incidents and changes: what you notify and when
- Forthwith, and no later than three working days after: any breach of information security that adversely affects the confidentiality of player information, and any breach that keeps players out of their accounts for more than twelve hours (article 37(2)(c) and (d)).
- Forthwith, and no later than thirty days after: changes to the key technical setup that are not changes to essential components (article 37(1)(g)).
- Before the change: changes to essential components (article 38(1)(f)), with the 72-hour urgency route of article 16(3).
The Compliance Audit Manual, a 2018 document, also asks auditors to obtain the incident log, check it against the incident response policy and verify whether incidents were reported to the MGA within 72 hours. If the two timings leave you unsure for a specific incident, ask the Authority before the clock runs out rather than after.
Hosting and cloud
The MGA's guidance paper on technical infrastructure for remote gaming is still listed among its guidance notes, but it is dated December 2015 and was written under the previous remote gaming regulations, so read it alongside Directive 3 of 2018. It states that the information security level the MGA seeks at hosting locations is that of ISO/IEC 27001:2013 (since replaced by the 2022 edition), with PCI DSS Level 1 certification for card data.
The same paper asks for a risk assessment, following ISO 31000, before critical components move to the cloud. It says the MGA is satisfied when critical components run on a private cloud not shared with other tenants, and that a virtual private cloud is allowed when the integrity and security of those components are not at risk. If a migration is on your roadmap, our cloud security page explains how we approach it.
Does NIS2 apply to MGA licensees?
Gambling is not a sector in the annexes of the NIS2 Directive (Directive (EU) 2022/2555), and it is not listed in the schedules of the Maltese transposition, the Measures for a High Common Level of Cybersecurity across the European Union (Malta) Order (S.L. 460.41, Legal Notice 71 of 2025 as amended by Legal Notice 89 of 2026). The MGA does have a representative on the National Cyber Security Steering Committee under that Order (article 15A(1)(f)).
A gaming group can still come into scope through another activity, if a group entity is a type listed in the annexes, such as a provider of cloud computing, data centre or managed ICT services to other businesses, and meets the size thresholds. In that case the NIS2 risk-management measures of article 21 apply to that entity alongside the MGA rules, not instead of them. Scope is assessed entity by entity, so confirm it with your legal advisers. Our NIS2 page sets out how we work on scope and measures.
How to prepare for an MGA system audit or compliance audit
- Bring the documentation up to date. System architecture, application architecture and network schematic match what runs today, internal IP addresses included. The manual has auditors sample servers, virtual machines and applications against these documents.
- Reconcile changes with notifications. Every change in the last two years has a log entry and, where required, an MGA notification or approval.
- Test the checklist controls yourself. Session time-outs, password storage, lock-out, access reviews, audit trails, clock synchronisation, replication to Malta.
- Show the policies in practice. The manual checks implementation, not only documents: keep access review records, incident logs, disaster recovery tests and restore tests.
- Get an independent view of your security. The manual asks whether you obtained an independent review of information security, when, from whom and with which critical findings. A security assessment or penetration test before the audit gives you that evidence.
- Close earlier findings and check outsourcing contracts. Auditors start from previous findings, and contracts with providers that need no MGA licence carry the clauses of article 27(4) of the directive.
Keep preparation and audit separate. Under the MGA's Approved Audit Service Provider Policy, consultancy, help with the application or implementation of the systems given to the licensee in the previous two years counts as a conflict of interest for the auditor.
If you are getting ready for a system audit or a compliance audit and want an independent look at your setup first, talk to us.
