An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesSecurity Acceptance Testing Under NIS2
Secure Acquisition Development Vulnerabilities / 2026-10-10

Security Acceptance Testing Under NIS2

Security acceptance testing checks whether a newly acquired, developed or significantly changed system meets agreed cyber requirements before it supports production services. It helps operationalise NIS2 Article 21(2)(e), while the depth of testing should reflect the service risk and applicable obligations.

Define security acceptance criteria early

Translate procurement requirements and design risk assessments into verifiable conditions for authentication, access restrictions, logging, secure configuration, vulnerability handling and relevant resilience features.

A statement that a product must be secure is not an acceptance criterion. A defined requirement to restrict administrator access and produce reviewable audit events can be tested.

Choose tests that address the actual exposure

Combine proportionate configuration review, access-control checks, relevant code or dependency analysis, vulnerability assessment and functional security tests. Cover sensitive interfaces and the effects of untrusted data.

No single test tool covers every weakness. Record the boundaries of the tests and distinguish evidence of an assessed function from assurance about the entire environment.

Protect the test process

Agree test authorisation, environments, test identities and handling of sensitive data. Where a live service must be assessed, coordinate service owner approval and measures to reduce disruption.

Security testing can itself create availability risk. Plans should address that risk without preventing appropriate verification.

Evaluate results and risk exceptions

Identify failed criteria, likely consequences and remediation options. Set owners and deadlines, then retest material fixes. Where acceptance is conditional, document residual risk and the accountable approver.

Do not treat vendor claims or a passed functional test as evidence that all agreed cyber controls were met. Identify which controls were verified and which remain untested.

Support production handover

Transfer relevant security settings, monitoring needs, administrator instructions, software versions, supplier contacts and unresolved findings to operations. Confirm that ownership of future patching and vulnerability response is established.

A secure pre-production build can become unsafe if its configuration or release controls are lost during deployment.

Measure outcomes and respect legal scope

Retain requirements, test cases, results, remediation and acceptance decisions, and use recurring failures to improve purchasing and development criteria.

Article 21 requires proportionate measures; specified digital and ICT providers may have further detailed requirements under Implementing Regulation (EU) 2024/2690. Check applicable national legislation and scope.

Questions arising

Is acceptance testing the same as a penetration test?

No. Acceptance testing assesses agreed security criteria and can include a range of techniques, of which penetration testing is only one.

Can production go live with open security findings?

That requires a reasoned risk decision under applicable obligations, considering severity, mitigations, accountability and planned remediation.

Related entries

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.