Define configuration baselines around service risk
Identify the network and information systems underpinning covered services and assign configuration owners. Establish documented expectations for administrative access, logging, remote interfaces, cryptography and unnecessary services, suited to each technology class.
A baseline should be specific enough for an operator to implement and verify. A generic instruction to harden every system offers little assurance if administrators must guess what settings are expected.
Control changes and prevent drift
Use approved change procedures, suitable automation and configuration review to distinguish intended modifications from unexpected changes. Maintain visibility of material deviations, especially those exposing internet-facing or privileged functions.
Not every deviation is malicious or unacceptable. Record legitimate exceptions, their security consequences, accountable approvers and review dates so controls do not silently weaken.
Protect configuration and management access
Restrict who can edit important settings, protect management credentials and log meaningful administrative operations where feasible. Separate production privileges from ordinary user identities and review vendor maintenance routes.
Consider the consequences of compromised central management tooling. A shared automation account can affect many systems, so its permissions and security deserve particular scrutiny.
Test secure defaults during deployment
Verify configuration before new systems enter service and after significant upgrades. Check that default accounts, exposed services and excessive permissions have been removed or constrained according to the risk assessment.
Retain test evidence and transfer ownership to the team that maintains the deployed service. A handover gap can allow initial security improvements to deteriorate.
Measure drift and remediate exposure
Compare deployed settings with approved baselines, prioritising deviations according to reachable attack paths and service impact. Investigate repeated exceptions to determine whether the standard or deployment process needs adjustment.
Collect evidence of identified deviations, fixes and accepted risk. Do not claim universal technical baseline values under NIS2 Article 21; specific sectors or providers may face more detailed rules.
Connect configuration to lifecycle management
Review baselines as threats, supported versions and operational dependencies change. Link findings to vulnerability handling, asset ownership and procurement requirements.
Implementing Regulation (EU) 2024/2690 contains detailed requirements for specific digital and ICT providers. Check applicability and national implementation instead of extending those details to all covered entities.
Questions arising
Does NIS2 prescribe one identical technical configuration for every system?
No. The Directive requires appropriate and proportionate measures; detailed obligations may depend on entity type and national law.
What should happen when a required control cannot be applied?
Document the exposure, accountable approval, compensating measures, review triggers and a credible remediation plan.