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.
HomeArticlesNIS2 Competent Authority Information Requests
Supervision Enforcement / 2026-10-11

NIS2 Competent Authority Information Requests

Under Articles 32 and 33 of NIS2, national competent authorities can request information and evidence from regulated entities within the legal limits applicable to essential and important entities. Preparing a reliable response requires identifying the request's legal basis, preserving accurate records and assigning accountability.

Confirm the authority, scope and legal basis

Identify the competent authority, legal entity, relevant NIS2 classification and deadline specified in a request. Article 32 governs supervisory measures for essential entities, while Article 33 addresses important entities through a generally ex post approach.

Do not assume a message purporting to come from an authority is authentic. Verify the sender through established official channels while preserving the original communication and observing applicable deadlines.

Assess exactly what evidence was requested

A request may concern Article 21 risk management, Article 23 incident reporting, incident records, policies, external audits or evidence of implementation. Route it to teams responsible for those systems and controls.

Distinguish an explanation of a policy from proof that the policy is followed. Records should identify dates, control owners, tested scope and any known exceptions.

Preserve information securely

Keep relevant documents, logs and correspondence intact and document their provenance. Restrict handling of sensitive material such as vulnerability reports, credentials and system diagrams to appropriate authorised staff.

Legal counsel should review privilege, confidentiality and personal-data considerations where relevant. These concerns should be handled through lawful procedures, not by altering or concealing responsive evidence.

Provide accurate answers and identify limitations

Respond to the questions actually posed, with citations to supplied records and a clear description of material gaps. Avoid representing planned remediation as a completed safeguard.

Where an audit sample or technical test does not cover an entire service, say so. A qualified factual answer is preferable to an unsupported declaration of complete compliance.

Coordinate remediation and follow-up

Assign owners to material deficiencies, record supervisory directions and track dates for corrective evidence. Confirm whether a formal order or voluntary information request has been issued because available rights and consequences can differ.

Maintain one authoritative log of submissions, decisions and subsequent corrections. Ensure the management body receives appropriate information about significant findings.

Review national procedural safeguards

NIS2 establishes EU minimum supervisory powers, but the national transposing law governs important practical details of authority procedures, deadlines and remedies.

A standard response package is helpful only when adapted to the actual request and jurisdiction. Obtain professional advice for contested orders or enforcement risks.

Questions on the text

Are supervision procedures identical for essential and important entities?

No. The NIS2 Directive distinguishes their supervisory treatment, subject to the applicable Member State law.

Is a written security policy enough to establish compliance?

No. Actual implementation, appropriate effectiveness checks and credible records are important.

More from the Desk

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.