Write requirements around operational risk
Begin with the business service, potential harm from compromise and integration dependencies. Identify the minimum functions needed to protect confidentiality, integrity and availability.
Avoid generic clauses that merely promise good security. Requirements should allow a bidder or evaluator to determine what evidence would demonstrate compliance.
Specify access and identity protections
Address administrator privileges, service accounts, remote support, multifactor authentication where appropriate, auditability and how access will be removed after a supplier relationship ends.
The importance of each control varies with the product's role. An identity service with privileged control over many applications can justify more stringent provisions than an isolated tool.
Cover updates, vulnerabilities and support
Ask for security update availability, support end dates, vulnerability reporting contacts and expected cooperation during a serious weakness. Clarify responsibility for deploying fixes and testing compatibility.
For long-lived equipment, plan replacement or mitigation when vendor support expires. Procurement terms should not promise indefinite patches that the supplier cannot actually provide.
Evaluate resilience, data and interoperability
Identify recovery expectations, backup responsibilities, data export capabilities and critical subprovider dependencies. Where feasible, request the technical documentation necessary to restore or replace the service.
A vendor's uptime figure does not demonstrate that the customer's full business process can be recovered. Examine dependencies outside the vendor's formal service boundary.
Define validation and exception handling
Agree how requirements will be verified before acceptance, whether through documentation review, configuration inspection or proportionate technical tests. Track deviations, risk owners and the decision authority for accepting residual weaknesses.
Procurement records should be usable by operations teams after deployment. Link accepted requirements with asset ownership, monitoring and maintenance processes.
Check entity-specific legal detail
Article 21 sets a risk-based framework, while the Annex to Implementing Regulation (EU) 2024/2690 contains detailed procurement security provisions for specified digital and ICT providers.
Check national law, sector obligations and contract enforceability. Do not describe the implementing regulation's detailed Annex requirements as universally binding across all NIS2 sectors.
Questions arising
Is there a universal NIS2 ICT procurement checklist?
No single checklist in Article 21 is prescribed for every entity. Risk and applicable national or entity-specific obligations determine the appropriate requirements.
Should requirements be checked after delivery?
Yes. Verification and the handover of ongoing responsibilities help ensure acquisition decisions translate into operating safeguards.