Identify what the ICT purchase will affect
Define the product or service, the systems it will connect to and the operational activities it will support. Map who will administer it, what information it will process and what dependencies it introduces.
The acquisition of an internet-facing management platform can present different risks from a local low-impact office tool. Classification should inform the depth of review rather than relying on a single standard purchasing form.
Set requirements before supplier selection
Specify necessary authentication, access controls, audit logging, update support, vulnerability communications and recovery expectations. Consider data portability and whether secure configurations can be maintained without continuous supplier assistance.
Procurement and security teams should resolve conflicting requirements early. If a vendor cannot supply an essential capability, record the consequence and identify alternatives or approved mitigations.
Evaluate assurance and lifecycle support
Review relevant security documentation, known vulnerabilities, support periods and supplier practices. Confirm that certificates or independent reports cover the version or service actually being bought.
Long-term support matters for devices or software with a lengthy operational life. Consider the practical cost and disruption of replacing an unsupported component before accepting it into a critical environment.
Validate delivery and integration
Test the delivered product against agreed security criteria before broad deployment. Confirm that default accounts, insecure settings or unexpected network permissions have been addressed. Involve system owners in accepting any exceptions.
Preserve the requirements, evidence reviewed, test results, decisions and ownership of remaining risks. Approval should not be inferred solely from payment or installation.
Connect procurement with operating controls
Transfer security commitments into the asset register, maintenance schedule, vulnerability process and supplier monitoring programme. Specify who is responsible for receiving advisories and implementing updates.
Under Implementing Regulation (EU) 2024/2690, certain digital and ICT entities have more detailed acquisition processes, including requirements throughout the lifecycle of critical ICT components. Other entities should not assume that each provision applies to them.
Reassess when the system changes
Major integration changes, supplier transitions, incidents and end-of-support notices can invalidate earlier acquisition assessments. Review the risk and update approved operating controls accordingly.
Verify the Member State law and relevant competent-authority guidance before describing a procedure as a statutory obligation.
Questions arising
Does NIS2 mandate a particular cybersecurity certification for all ICT purchases?
The Directive does not impose one universal purchasing certificate for every covered entity and product. Applicable additional measures depend on entity type and law.
When should acquisition security be assessed?
Before material commitments are made, with reassessment where integration, support or risk changes significantly.