NIS2 and DORA: Compliance clusters in Kubernetes
NIS2 and DORA require different assessments. In Kubernetes, technical separation depends on risk and applicable obligations.
NIS2 and DORA set requirements for digital security, but do not impose a blanket obligation to use separate Kubernetes clusters. The scope of the regulations, contracts and the risk associated with the services operated all matter for the architecture. A shared cluster may be suitable if its safeguards fit the respective environment and are checked. Where requirements are higher, a dedicated cluster can make separation easier.
Key takeaways
- NIS2 and DORA apply to different entities and have different requirements. DORA has applied to the financial entities it covers since 17 January 2025 and includes a specific oversight regime for critical ICT third-party service providers.
- The risk assessment determines the cluster boundary. Namespaces, network rules and separate clusters offer different options for isolation. Neither regulation imposes a blanket requirement for one cluster per regulation.
- Technical logs are only one part of the evidence. Teams must assign controls to responsible individuals, check their effectiveness and keep the results available alongside other documentation.
First establish scope and obligations
The NIS2 Directive applies to entities in numerous sectors. In Germany, the new version of the BSI Act has been in force since 6 December 2025. Whether an organisation is affected depends on factors including its activities and the statutory criteria.
DORA has applied directly since 17 January 2025 and covers the financial entities listed in the regulation. It also addresses risk arising from ICT third-party service providers and provides for specific oversight of providers designated as critical.
For financial entities, the relevant DORA provisions on ICT risk management and reporting ICT-related incidents take precedence over the corresponding NIS2 requirements. Other applicable obligations still need to be assessed. A cloud provider does not automatically become a financial entity merely because it has a bank as a customer. It may nevertheless be subject to contractual requirements.
Choose cluster boundaries based on risk
A compliance cluster is one possible term for a Kubernetes environment with defined safeguards and associated evidence. What matters is a documented mapping: which services run where, which controls apply and who is responsible for them?
A dedicated cluster can enable stronger separation of the control plane. Separate node pools, by contrast, isolate computing resources while central cluster services may still be shared. Even with dedicated clusters, shared infrastructure and administrative access must be considered.
Namespaces separate resources within a cluster. They do not, however, cover all cluster-wide resources. Network Policies can restrict communication between pods, but require a network plugin that supports them. The Kubernetes documentation on multi-tenancy also identifies access rights, storage and the shared control plane as relevant areas.
Connect controls and evidence in operations
For each requirement, teams should record which technical or organisational control addresses it. These include restricted administrative privileges, rules for deploying workloads and procedures for handling security incidents. Configurations must be checked regularly to establish whether they work as intended.
Audit logs, results of policy checks and alerts from runtime monitoring can support this assessment. A rejected deployment attempt, for example, shows that a particular rule worked in that case. On its own, it proves neither the effectiveness of all rules nor full compliance with a regulation.
For evidence to be usable in an audit, it must be clearly traceable to the system, period and control concerned. Defined retention arrangements, protected access and individuals responsible for analysis and follow-up are equally important.
Consider data location and service providers together
Data location requirements cannot be met through pod placement alone. An architecture review must also consider storage, backups, logs and administrative access. Teams should check which locations and access options the service actually uses.
Encryption and restricted access rights are technical safeguards. At the same time, responsibility for keys, support and subcontractors must be clarified contractually and organisationally. Financial entities must pay particular attention to DORA requirements concerning their ICT third parties.
Frequently Asked Questions
Can NIS2 and DORA apply to a company at the same time?
That depends on the company and the relevant provisions. For financial entities covered by DORA, its relevant provisions on ICT risk management and reporting ICT-related incidents take precedence over the corresponding NIS2 requirements. Other obligations must be assessed separately.
Can one shared Kubernetes cluster serve both use cases?
That may be possible. Whether isolation is sufficient depends on risks, protection needs, contracts and the controls in place. Namespaces and Network Policies do not automatically protect all shared resources.
What evidence helps during an audit?
Documented responsibilities, current configurations, results of control checks and relevant logs are useful. The evidence needed depends on the applicable obligations and the scope of the audit.
Editor's Picks
cloudmagazinKubernetes as the default OS for AI: Clusters as a compliance issuecloudmagazinAI sovereignty starts with infrastructurecloudmagazinCritical infrastructure in the cloud: What makes migration secureMore from the MBF Media Network
MyBusinessFutureWhen the agent posts the supplier invoice itselfDigital ChiefsEveryone is building AI agents. Who controls them?SecurityTodayThe emergency plan nobody rehearsedImage source: AI-generated (July 2026)
Translated from the German original using artificial intelligence. The German version is authoritative.

