> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/nis2/readme.md).

# NIS2

NIS2: full text of Directive (EU) 2022/2555 with per-article pages and paragraph anchors.

**Directive (EU) 2022/2555** — of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive)

The full text is available article by article, one page per article (`articles/<number>`). Every numbered paragraph and point carries a stable anchor (`#p-3` for paragraph 3, `#p-3-a` for its point (a)), so any provision can be cited with a direct link. The English consolidated manifestation from CELLAR is reproduced verbatim; the official text remains the EU publication at [EUR-Lex](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:02022L2555-20221227).

## Structure

| Chapter / Section                                                                                                                                                                   | Articles   |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
| [Chapter I — General provisions](/nis2/chapter-i-general-provisions-art.-1-6/1.md)                                                                                                  | Art. 1–6   |
| [Chapter II — Coordinated cybersecurity regulatory frameworks](/nis2/chapter-ii-coordinated-cybersecurity-regulatory-frameworks-art.-7-14/7.md)                                     | Art. 7–14  |
| [Chapter III — Cooperation at Union and international level](/nis2/chapter-iii-cooperation-at-union-and-international-level-art.-15-19/15.md)                                       | Art. 15–19 |
| [Chapter IV — Cybersecurity risk-management measures and reporting obligations](/nis2/chapter-iv-cybersecurity-risk-management-measures-and-reporting-obligations-art.-20-25/20.md) | Art. 20–25 |
| [Chapter V — Jurisdiction and registration](/nis2/chapter-v-jurisdiction-and-registration-art.-26-28/26.md)                                                                         | Art. 26–28 |
| [Chapter VI — Information sharing](/nis2/chapter-vi-information-sharing-art.-29-30/29.md)                                                                                           | Art. 29–30 |
| [Chapter VII — Supervision and enforcement](/nis2/chapter-vii-supervision-and-enforcement-art.-31-37/31.md)                                                                         | Art. 31–37 |
| [Chapter VIII — Delegated and implementing acts](/nis2/chapter-viii-delegated-and-implementing-acts-art.-38-39/38.md)                                                               | Art. 38–39 |
| [Chapter IX — Final provisions](/nis2/chapter-ix-final-provisions-art.-40-46/40.md)                                                                                                 | Art. 40–46 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.mica.wtf/nis2/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.