Key takeaways
- No general law in Malta or Cyprus requires every company to run a yearly penetration test: the obligation depends on the regulator (DORA, NIS2, MGA or PCI DSS).
- DORA (Articles 24 and 25) requires appropriate tests at least yearly on all ICT systems supporting critical or important functions, by independent testers, with remediation and validation; penetration testing is one of the listed tests.
- TLPT is required at least every three years only from entities the authority identifies; Delegated Regulation (EU) 2025/1190 sets the default list and an active red team phase of at least 12 weeks.
- In Malta the MFSA is the TLPT Authority and runs tests under TIBER-MT; in Cyprus DORA supervision is split between CySEC, the Central Bank of Cyprus, the Superintendent of Insurance and the supervisor of occupational pension institutions, and CySEC charges EUR 20,000 to assess a TLPT.
- NIS2 in both countries asks you to show that measures work: Malta adds a qualified auditor approved by the CIP Department, Cyprus lets the DSA or a body it authorises run audits, and the Cypriot CSIRT can provide penetration testing on request.
- MGA auditors ask whether the licensee obtained an independent security review; PCI DSS (v4.0, carried into v4.0.1) asks for internal and external penetration tests at least every 12 months and after significant changes.
No single rule in Malta or Cyprus tells every company to commission a penetration test once a year. What you test, how often and with whom depends on who regulates you. Financial entities under DORA test every system supporting critical or important functions at least yearly, and those identified by their authority also run threat-led penetration testing (TLPT) every three years. NIS2 entities show that their measures work and can be audited and scanned. MGA auditors ask whether you obtained an independent security review, and PCI DSS asks for internal and external penetration tests every 12 months.
This guide is for IT managers, CISOs and compliance officers of organisations licensed or established in Malta or Cyprus. It maps each regime to the testing it asks for, so that one programme can serve several regulators. If you need the basics first (test types, phases, what a report should contain), start from our guide to penetration testing services.
The short answer, regulator by regulator
- MFSA and CySEC (DORA): a risk-based testing programme, appropriate tests at least yearly on all ICT systems and applications supporting critical or important functions, and TLPT at least every three years for the entities the authority identifies (Regulation (EU) 2022/2554, Articles 24 to 27).
- NIS2 authorities (the CIP Department in Malta, the Digital Security Authority in Cyprus): policies and procedures to assess whether security measures are effective, plus audits and security scans the authority can order. Malta adds a qualified auditor approved by the CIP Department.
- Malta Gaming Authority: system audits and compliance audits by MGA-approved auditors, who ask whether the licensee obtained an independent review of its information security.
- Card payments (PCI DSS): vulnerability scans every three months, and internal and external penetration tests at least once every 12 months and after any significant change.
DORA: the yearly testing programme
DORA has applied since 17 January 2025 to credit institutions, investment firms, payment and e-money institutions, insurers, crypto-asset service providers and the other financial entities listed in its Article 2. Article 24 asks every financial entity other than a microenterprise to keep a digital operational resilience testing programme as part of its ICT risk-management framework. Four points shape the work:
- at least yearly, appropriate tests on all ICT systems and applications supporting critical or important functions (Article 24(6));
- tests carried out by independent parties, internal or external; an internal tester needs sufficient resources and no conflicts of interest during design and execution (Article 24(4));
- procedures to prioritise, classify and remedy every issue found, and internal validation that each weakness has been fully addressed (Article 24(5));
- a risk-based approach that considers the evolving ICT risk landscape and the criticality of information assets and services (Article 24(3)).
Article 25 lists the tests the programme can draw on, from vulnerability assessments and scans, network security assessments and source code reviews to scenario-based, end-to-end and penetration testing. DORA does not say that every yearly test has to be a penetration test. It asks for tests appropriate to each system, and for an internet-facing platform that handles client money or data, a penetration test is the natural candidate. Microenterprises test too, combining a risk-based approach with strategic planning of ICT testing (Article 25(3)).
TLPT: who is in and how it runs
Threat-led penetration testing is a different exercise: an intelligence-led red team test on live production systems, covering several or all critical or important functions (Article 26(2)). It is required at least every three years only from the financial entities that the competent authority identifies (Article 26(1) and (8)). Microenterprises and entities using the simplified ICT risk-management framework of Article 16 are outside it.
The detail sits in Commission Delegated Regulation (EU) 2025/1190, the regulatory technical standards on TLPT, published on 18 June 2025 and drafted in line with the TIBER-EU framework. Its Article 2(2) lists who is in by default, unless the authority's assessment shows that a TLPT is not justified:
- credit institutions identified as global or other systemically important institutions (G-SIIs or O-SIIs), or part of one;
- payment institutions above EUR 150 billion of payment transactions, and e-money institutions above that figure or above EUR 40 billion of outstanding e-money, in each of the two calendar years before the assessment;
- central securities depositories and central counterparties;
- trading venues with an electronic trading system that, in each of the two calendar years before the assessment, had the highest national market share or more than 5% of Union turnover in certain instruments;
- the largest insurance and reinsurance undertakings, selected on gross written premium, technical provisions and total assets.
Investment firms are not on the default list. An authority can still identify any financial entity on the basis of its size, interconnectedness, the criticality and substitutability of its services, the complexity of its business model and its ICT risk profile (Article 2(1)).
What a TLPT asks of you
The RTS sets a sequence that starts with the authority's notification:
- within 3 months, the initiation documents: project charter, control team lead, use of internal or external testers, communication channels and a code name (Article 9(2));
- within 6 months, a scope specification document approved by the management body (Article 9(6));
- a targeted threat intelligence report, from which at least three scenarios are selected (Article 10);
- an active red team phase lasting at least 12 weeks (Article 11(5));
- closure: the red team report within 4 weeks of the end of the active phase, and the blue team report, replay and purple teaming within 10 weeks (Article 12);
- within 8 weeks of the authority's notice that both reports are complete, the summary of findings and the remediation plans, followed by the authority's attestation (Articles 12(7), 13 and 14).
Who can test
Article 27 of DORA asks for testers with expertise in threat intelligence, penetration testing and red team testing, certified by an accreditation body in a Member State or bound by formal codes of conduct or ethical frameworks, and covered by professional indemnity insurance. Article 7 of the RTS adds numbers: an external red team led by a manager with at least 5 years of penetration testing and red team experience, plus at least two testers with at least 2 years each. Internal testers need the authority's approval, and an entity using them contracts external testers every three tests (Articles 26(8) and 27(2)).
Malta: the MFSA runs TIBER-MT
In its circular of 7 July 2025, the MFSA states that it is the TLPT Authority for tests under DORA and the RTS in the Maltese jurisdiction, and that TLPT follows TIBER-EU. Under its TIBER-MT and DORA TLPT-MT National Implementation Document, entities licensed by the MFSA and identified for TLPT undergo a TIBER-MT test, which is recognised under TIBER-EU and leads to attestation, provided the DORA and RTS requirements are met throughout. The rest of the MFSA's DORA set-up is in our guide to DORA for MFSA-licensed firms.
Cyprus: four supervisors and a TLPT fee
Cyprus split DORA supervision by sector. The Minister of Finance's notice K.D.P. 252/2025, published in the Official Gazette on 14 August 2025, designates CySEC for investment firms, crypto-asset service providers, market infrastructures, fund managers and crowdfunding platforms; the Central Bank of Cyprus for credit institutions (other than significant ones, which the ECB supervises), payment and e-money institutions; the Superintendent of Insurance for insurers; and a separate supervisor for institutions for occupational retirement provision. Under Article 26(8) of DORA, identifying who performs TLPT is a task of the competent authority.
For the entities it supervises, CySEC's Directive OD 73-2009-07 on DORA fees and subscriptions, published on 29 August 2025, sets a fee of EUR 20,000 for assessing a TLPT under Articles 26(6) and 26(7). The CySEC circulars on DORA, from reporting to the register of information, are covered in DORA for CySEC-regulated investment firms.
NIS2: testing as evidence that controls work
The NIS2 Directive does not name penetration testing as a mandatory measure. Article 21(2) of Directive (EU) 2022/2555 asks for vulnerability handling and disclosure (point (e)) and for policies and procedures to assess the effectiveness of cybersecurity risk-management measures (point (f)). Both national laws copy those points: Article 19(2) of Malta's S.L. 460.41 and Article 35(2) of Cyprus's Law 89(I)/2020, as amended by Law 60(I)/2025. A documented test programme is a direct way to show point (f) in practice. Financial entities covered by DORA follow DORA for these matters.
Malta: a qualified auditor and CSIRT scanning
- Qualified auditor (Article 14): every essential and important entity appoints one to verify that the Article 19 measures are in place. The CIP Department, or the competent authority, approves the appointment once the auditor shows independence, a background check, a recognised cybersecurity certification and the required experience.
- Proactive scanning (Article 10): the internal or autonomous CSIRT that monitors the entity carries out proactive scanning to detect vulnerabilities with a potential significant impact, and the national CSIRT can run non-intrusive scans of publicly accessible systems, notifying the entity in writing of the scan and of any vulnerable systems it finds.
- Supervision (Articles 29 and 30): the authority can order regular and targeted security audits and security scans for essential entities, and targeted audits and scans for important ones. A targeted audit by an independent body is paid by the audited entity, unless the authority decides otherwise.
Scope, authorities and the other Maltese additions are in our guide to NIS2 in Malta.
Cyprus: audits by the DSA or a body it authorises
- CSIRT services (Article 31A(4)(e)): under the law, the national CSIRT provides, on request of an essential or important entity, proactive scanning and/or penetration testing of its systems. The directive's equivalent task mentions scanning only. The CSIRT can also run non-intrusive scans of publicly accessible systems (Article 31A(5)).
- Supervision of essential entities (Article 36A): regular and targeted security audits by the Authority or a qualified independent body it authorises, with targeted audits and their frequency based on risk assessments, results made available to the Authority and costs borne by the entity unless the Authority decides otherwise; security scans; and requests for the results of security audits by an auditor authorised under a DSA decision or by an independent auditor.
- Important entities (Article 36B): ex post supervision, including targeted security audits and security scans.
The Cypriot law also shortens the early warning to 6 hours; see our guide to NIS2 in Cyprus.
Cloud, managed and managed security service providers
For cloud, data centre, managed service and managed security service providers and the other digital providers it lists, Commission Implementing Regulation (EU) 2024/2690 applies directly in both countries. Point 6.5 of its Annex requires a security testing policy: need, scope, frequency and type of tests set from the risk assessment, a documented methodology, and documented results with mitigating actions for each finding. Recital 15 names penetration tests among the tests that may be used.
Gaming: what MGA auditors look for
The MGA checks systems through system audits, system reviews and compliance audits carried out by approved audit service providers. Its Compliance Audit Manual (MGA/G/001) asks the auditor to find out whether the licensee obtained an independent review of its information security and its implementation, when, from whom and with which critical findings. A recent penetration test with a closed remediation list answers that question directly. Where player card numbers are stored, the manual has the auditor check that they are encrypted and ask for PCI DSS compliance evidence.
Keep preparation and audit apart. The MGA's Approved Audit Service Provider Policy treats consultancy, help with the application, implementation of the systems and some other services provided to the licensee in the previous two years as a conflict of interest for the auditor. The full picture is in our guide to MGA security requirements.
Payments: PCI DSS
PCI DSS is set by the PCI Security Standards Council, not by a national regulator, and applies to organisations that store, process or transmit cardholder data. Unlike the other regimes in this guide, it fixes both method and frequency. In version 4.0, as set out in the Council's Self-Assessment Questionnaire D for merchants (v4.0 was retired on 31 December 2024 and replaced by v4.0.1, which added no new requirements):
- internal vulnerability scans at least once every three months, with high-risk and critical findings resolved and rescanned (requirement 11.3.1);
- external scans at least once every three months by a PCI SSC Approved Scanning Vendor (11.3.2);
- a documented penetration testing methodology covering the whole cardholder data environment perimeter and critical systems, at network and application layer (11.4.1);
- internal and external penetration tests at least once every 12 months and after any significant infrastructure or application upgrade or change, by a qualified internal resource or third party with organisational independence, not necessarily a QSA or ASV (11.4.2 and 11.4.3);
- exploitable findings corrected and the test repeated to verify the fixes (11.4.4);
- where segmentation reduces scope, tests of the segmentation controls at least every 12 months and after changes to them (11.4.5).
Service providers have further requirements on segmentation testing and multi-tenant environments (11.4.6 and 11.4.7).
One programme for several regulators
A Maltese gaming operator that takes card payments, or a Cypriot payment institution, can answer to two or three of these regimes at once. Planning a separate test for each regime duplicates work on the same systems. A single calendar is easier to run and to evidence:
- Map the regimes per legal entity. DORA or NIS2 (where DORA applies, it takes precedence on risk management and incident reporting), MGA licence, PCI DSS scope. Groups with entities in both countries map each one separately.
- Start from the fixed clocks. PCI DSS and DORA both work on a yearly cycle; align the yearly tests on systems supporting critical or important functions with the cardholder data environment.
- Test before change, not only by date. PCI DSS asks for a test after significant changes, and MGA system audits follow major changes to the key technical setup.
- Document independence. DORA Article 24(4), PCI DSS 11.4, the Maltese qualified auditor and the MGA policy all look at it from different angles.
- Close the loop. Remediation tracking and retest evidence are what DORA Article 24(5), PCI DSS 11.4.4 and point 6.5 of Regulation 2024/2690 actually check.
- Keep the file ready. NIS2 supervisors in both countries can ask for the results of security audits and the underlying evidence (Article 29(2)(g) of the Maltese Order, Article 36A(2)(g) of the Cypriot law).
How AmagisTech can help
We run penetration tests and continuous vulnerability management as part of our cybersecurity services, with reports built to serve as evidence across DORA, NIS2, MGA and PCI DSS reviews: scope, method, findings with evidence, prioritised fixes and a retest. For TLPT, Article 27 of DORA and Article 7 of the RTS set specific requirements for testers and threat intelligence providers: check them against any provider, us included.
In short: in Malta and Cyprus the obligation to test comes from your regulator. DORA asks for yearly tests and, for identified entities, TLPT; NIS2 asks you to show your measures work; the MGA looks for an independent security review; PCI DSS sets a 12-month penetration testing cycle. If you want to plan one test calendar that covers all of them, talk to our team.
