Determine whether gatekeeper designation exists
DMA obligations attach to designated gatekeepers for identified core platform services under the Regulation. NIS2 scope depends instead on defined entity types, sectoral conditions, size rules, exceptions and national jurisdiction.
A prominent technology provider is not automatically a DMA gatekeeper merely because it operates a widely used platform. Nor does DMA designation alone establish which NIS2 obligations apply.
Compare regulatory goals and requirements
The DMA sets conduct obligations and prohibitions relevant to platform markets, including issues involving interoperability, data use and business-user access. NIS2 focuses on cybersecurity risk management, service continuity and significant incidents.
An interoperability duty under market regulation may present security design questions, but it does not transform the DMA into a general cybersecurity standard.
Address interoperability without compromising security
When compliance projects involve technical interfaces or service access, security teams should assess authentication, authorisation, monitoring and dependencies. Document how implementation decisions satisfy each applicable legal duty.
Avoid using a vague cybersecurity concern as a universal justification for disregarding DMA obligations. Specific legal exceptions, safeguards and Commission requirements must be assessed under the DMA.
Keep supervision and sanctions distinct
DMA enforcement is centred on the European Commission and has its own procedures and penalty regime. NIS2 is implemented through national competent authorities, with different essential and important entity supervision provisions.
Do not apply NIS2 Article 34 fine thresholds to DMA infringements or assume that a DMA investigation establishes a NIS2 breach. Each authority considers the relevant legal elements.
Recognise overlapping operational facts
An outage, cyberattack or compromised integration could prompt internal security action while also affecting technical commitments under platform regulation. Establish an incident and legal escalation process that routes issues to appropriate owners.
A single technical event can have several business and legal consequences, but reporting triggers and deadlines must be determined separately for each applicable instrument.
Maintain distinct scope records and controls
Record NIS2 entity classification, DMA designation and designated core platform services separately. Map technical interfaces, change approval and supplier controls to their respective obligations.
Reassess after new designation decisions, changes to services, amended legislation or national NIS2 guidance. Existing market-law compliance documents cannot by themselves demonstrate NIS2 risk-management effectiveness.
Points of clarification
Is a DMA gatekeeper automatically a NIS2 essential entity?
No. DMA designation and NIS2 classification use different legal criteria.
Are DMA penalties the same as NIS2 administrative fines?
No. They arise under separate statutory enforcement frameworks.