Managed SOC for companies in Malta and Cyprus

Managed SOC and MDR for firms in Malta and Cyprus: what NIS2, DORA and the MGA expect from detection and reporting, and what to check in a provider.

9 min read
Managed SOC for companies in Malta and Cyprus

Key takeaways

  • A managed SOC (often sold as MDR) gives you 24/7 monitoring, investigation and response as a service; the legal responsibility for incident handling and reporting stays with your organisation.
  • Under Article 23(4) of the NIS2 Directive the early warning is due within 24 hours of becoming aware of a significant incident, the notification within 72 hours and the final report within one month.
  • Malta's S.L. 460.41 asks essential and important entities to receive CSIRT monitoring services from an internal or an autonomous (outsourced) CSIRT meeting the requirements of article 9(1).
  • Cyprus shortens the NIS2 early warning to the Digital Security Authority to six hours (article 35B(4)(a) of Law 89(I)/2020 as amended by Law 60(I)/2025).
  • DORA firms supervised by the MFSA or CySEC send the initial notification within four hours of classifying an incident as major and no later than 24 hours from awareness (Delegated Regulation (EU) 2025/301, Article 5).
  • Before signing, check real 24/7 coverage, notification times in the contract, the data region (Article 30(2)(b) DORA), audit and exit rights, and the language of escalations and reports.

A managed SOC, often sold as managed detection and response (MDR), is an external team that monitors your systems around the clock, investigates alerts and responds to incidents with you. For organisations in Malta and Cyprus it is a practical way to keep up with the reporting clocks of NIS2, DORA and the MGA: 24 hours under the directive, 6 hours in Cyprus, 4 hours from classification under DORA. The legal responsibility stays with your organisation, so the choice of provider is a compliance decision as much as a technical one.

This guide is for IT managers, CISOs and compliance officers of companies established in Malta or Cyprus, including local subsidiaries of foreign groups. It explains what a managed SOC does, what each framework expects from detection and response, and what to check before you sign.

What a managed SOC does

A security operations centre (SOC) collects logs and telemetry from your endpoints, cloud, identity, network and applications into a SIEM, correlates them, and puts analysts on the alerts that matter. A managed SOC runs that operation for you as a service. In practice it covers:

  • 24/7 monitoring of the sources you connect, with detection rules tuned to your environment;
  • triage and investigation, so that what reaches your team is a qualified incident and not a queue of noise;
  • response: isolating a host, disabling an account, blocking an indicator, according to playbooks agreed in advance;
  • threat hunting based on threat intelligence, looking for activity that no rule has flagged yet;
  • reporting: incident timelines you can reuse for regulatory notifications, and periodic reports for management.

MDR and managed SOC are used almost interchangeably in the market. What matters is not the label but who does what at 3 a.m., which actions the provider can take without calling you, and what you receive in writing afterwards.

What the rules ask of detection and response

None of the frameworks below requires you to outsource your SOC. They require outcomes: detection, incident handling and reporting within fixed times. A managed SOC is one way to produce those outcomes. The national details are covered in our dedicated guides, so here we only look at what changes for detection and response.

NIS2: the directive baseline

Article 21(2) of Directive (EU) 2022/2555 lists incident handling among the minimum cybersecurity risk-management measures. Article 23(4) sets the reporting sequence for significant incidents:

  • an early warning without undue delay and in any event within 24 hours of becoming aware of the incident;
  • an incident notification within 72 hours of becoming aware, with an initial assessment of severity and impact and, where available, indicators of compromise;
  • a final report not later than one month after the incident notification, with root cause and mitigation measures.

The early warning and the incident notification run from awareness; the final report runs from the notification. An attack that nobody sees for a week does not stop the clock: it starts it late, and the questions start with why it was not seen. Detection is where reporting begins.

Malta: CSIRT monitoring services

The Maltese transposition, Subsidiary Legislation 460.41, goes further than the directive on monitoring. Article 19(1)(d) asks essential and important entities to receive CSIRT monitoring services from an internal CSIRT or an autonomous CSIRT, which the Order defines as an outsourced CSIRT providing a monitoring function. Whichever you use, it has to meet the requirements of article 9(1), among them communication channels available at all times without single points of failure, staff adequate to ensure availability of services at all times, and redundant systems with backup working space. Article 10 lists its tasks: real-time or near real-time monitoring, early warnings, incident response, forensic analysis and proactive vulnerability scanning.

That is close to the scope of a managed SOC, and the name of the CSIRT that monitors you, internal or autonomous, is part of the registration with the CIP Department. Scope, authorities and the full set of Maltese duties are in our guide to NIS2 in Malta.

Cyprus: a 6-hour early warning

Cyprus transposed NIS2 by amending Law 89(I)/2020 with Law 60(I)/2025. Article 35B(4)(a) of the Cypriot law shortens the early warning to the Digital Security Authority to six hours from becoming aware of a significant incident, against the 24 hours of the directive. Six hours leaves no room for an alert that sits unread overnight or for a provider that escalates only in office hours. The rest of the Cypriot framework is in NIS2 in Cyprus.

DORA: firms supervised by the MFSA and CySEC

For banks, payment and e-money institutions, investment firms, insurers and the other financial entities in its scope, Regulation (EU) 2022/2554 (DORA) has applied since 17 January 2025 and takes the place of NIS2 for ICT risk and incident reporting. Article 10 asks for mechanisms to promptly detect anomalous activities, with alert thresholds and automatic alerts to the staff in charge of response. Article 17 asks for an incident management process to detect, manage and notify ICT-related incidents.

The reporting times are in Article 5 of Delegated Regulation (EU) 2025/301: the initial notification as early as possible and within four hours from classifying the incident as major, and no later than 24 hours from becoming aware of it; the intermediate report within 72 hours from the initial notification; the final report no later than one month after the latest intermediate report. Article 19(5) of DORA allows the reporting to be outsourced to a third-party provider, but the financial entity remains fully responsible for it.

The MFSA and CySEC each use their own reporting channel and templates. We cover them in DORA for MFSA-licensed firms and DORA for CySEC-regulated investment firms.

MGA licensees

Gaming licensees in Malta have their own clock. Under article 37(2) of the MGA Directive 3 of 2018, licensees notify the Authority forthwith, and in any case 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. Article 17(1) places the key technical setup in Malta or another EU or EEA state, unless the MGA accepts another location. Both points are worth raising with a SOC provider that collects logs from the gaming platform. Details in MGA security requirements for gaming licensees.

Your provider is regulated too

Managed security service providers are listed in Annex I of the directive, so a managed SOC provider of sufficient size is itself an entity under NIS2. Under Article 26(1)(b) it falls under the jurisdiction of the Member State of its main establishment in the Union, which may not be yours. On your side, Article 21(2)(d) and 21(3) ask you to take into account the security practices and specific vulnerabilities of each direct supplier and service provider. A SOC provider sees almost everything you run, so it sits near the top of that list.

What to check before choosing a provider

24/7 coverage that is real

Ask who is on shift at night and at weekends, how many analysts cover your account, and how an escalation reaches a named person on your side. Ask for the escalation tree in writing, with phone numbers. If you plan to use the provider as your autonomous CSIRT in Malta, ask how it meets article 9(1) of the Maltese Order point by point, starting with availability at all times and redundant systems.

Notification times written into the contract

Map your shortest clock first: 6 hours in Cyprus, 24 hours under NIS2 in Malta, 4 hours from classification under DORA, three working days for the MGA. Then check that the provider's service levels leave you time inside it, from detection to escalation to a draft report. For ICT services supporting critical or important functions, Article 30(3)(a) of DORA asks for service level descriptions with precise quantitative and qualitative performance targets, and Article 30(3)(b) for the provider's notice periods and reporting obligations towards you.

Ask also who drafts the content of the early warning or initial notification, in which template, and who files it. The provider can prepare it; your organisation signs and remains responsible.

Where your data lives

Article 30(2)(b) of DORA asks the contract to state the regions or countries where services are provided and data is processed and stored, and to require advance notice if the provider plans to change them. Even outside DORA, logs carry personal data and sensitive configuration, so the question is the same.

On Google Security Operations the data location is a configuration choice. Google's SecOps Services Locations page, last modified on 24 June 2026, lists for the SIEM and SOAR a Europe multi-region with data centres in Belgium, the Netherlands and Finland, and single regions in Frankfurt, Paris, Turin and Warsaw, among others. London and Zurich are also available, outside the EU. Ask your provider which region holds your data and whether any analyst tooling copies it elsewhere.

Audit, access and exit

Article 30(3)(e) of DORA gives the financial entity, an appointed third party and the competent authority unrestricted rights of access, inspection and audit for services supporting critical or important functions. Article 30(2)(d) covers access to and return of your data in an easily accessible format when the contract ends. Check that detection rules, playbooks and log retention stay usable if you change provider, and that the platform is not locked to the provider's own tenant.

Language and reporting format

Incident reports go to authorities, boards and sometimes a parent company in another country. Ask in which language analysts escalate and reports are written, whether reports are usable as they are for the notification to your authority, and whether monthly reports speak to management as well as to the technical team.

Integration with your stack

Ask which sources are onboarded in the first weeks and which come later, and whether the provider works with the tools you already have. A SOC that sees only endpoints will miss identity abuse and cloud misconfiguration. If you are still choosing the platform, our comparison of SIEM tools is a useful starting point.

How we work

AmagisTech runs a managed SOC on Google Security Operations, with Google Threat Intelligence for detection and hunting, as part of our observability and 24/7 security operations service. We start with an assessment of log sources and coverage gaps, onboard the stack with detection rules written for your environment, and then run continuous monitoring, threat hunting and incident response with monthly reports. The data region is chosen with you from the locations Google offers. Alongside our Milan base we have an address in Gżira, Malta, and we work with regulated organisations on NIS2 and DORA as well as on the SOC itself.

If you want to see how a managed SOC would fit your reporting clocks in Malta or Cyprus, talk to us.

In short: a managed SOC gives you 24/7 detection, investigation and response without building the team in house. In Malta the NIS2 Order asks for CSIRT monitoring services, internal or outsourced; in Cyprus the early warning is due within 6 hours; DORA firms supervised by the MFSA or CySEC report major incidents within 4 hours of classification; MGA licensees report certain breaches within three working days. Choose a provider whose coverage, contractual service levels, data location and exit terms fit those clocks, and remember that the responsibility stays with you.

Frequently asked questions

In practice the two labels are used almost interchangeably. Both describe an external team that monitors your systems 24/7, investigates alerts and responds to incidents. What matters is the scope in the contract: which sources are monitored, which response actions the provider can take without calling you, and what reporting you receive.
No. Article 19(1)(d) of the Maltese Order (S.L. 460.41) asks essential and important entities to receive CSIRT monitoring services from either an internal CSIRT or an autonomous CSIRT, which the Order defines as an outsourced CSIRT. Either way, the CSIRT has to meet the requirements of article 9(1), such as availability at all times and redundant systems.
An early warning goes to the Digital Security Authority within six hours of becoming aware of a significant incident, under article 35B(4)(a) of Law 89(I)/2020 as amended by Law 60(I)/2025. The directive allows 24 hours. The incident notification follows within 72 hours and the final report within one month.
Yes. Article 19(5) of Regulation (EU) 2022/2554 allows financial entities to outsource the reporting of major ICT-related incidents to a third-party service provider, but the financial entity remains fully responsible for meeting the reporting requirements.
In the region chosen at configuration. Google's SecOps Services Locations page (last modified 24 June 2026) lists a Europe multi-region with data centres in Belgium, the Netherlands and Finland, and single regions such as Frankfurt, Paris, Turin and Warsaw. Under DORA the contract states where data is processed and stored (Article 30(2)(b)).

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