MCP · Item 2.2

How do I build an asset inventory for NIS2 with AI?

An AI assistant connected over MCP fills the lists in item 2.2 of the NIS 2 walkthrough from your own records: it ticks entries in the catalogue, adds your own and says who provides what. Every screen it wrote shows its name and the day. You check the list and finish the item in the app.

Try 30 days, money back
Simon OrzelCory Hisey

Book a call

Simon OrzelSimon Orzel·

How does an AI assistant build the inventory?

An asset inventory is the list of what your company needs for its work: processes, software, technology and rooms. In the NIS 2 walkthrough you keep it in item 2.2, and a connected AI assistant can fill it there from your records.

It connects through MCP (Model Context Protocol), an open standard that lets an assistant such as Claude read and enter data in an application. It then works with the rights of the person who connected it.

Give it what you already have: your IT provider's inventory, a licence list, or an export from your CMDB, the database where your IT keeps its devices and software. The assistant matches the lines to catalogue entries, ticks those and adds entries of its own for the rest.

The server tells every assistant to enter only what your records and systems show, and to leave a field empty rather than guess. Whether it did, you can see on the list itself.

What belongs in the asset inventory under NIS 2?

Item 2.2 keeps four lists: “What your company does every day” (your processes), “Software for customers, staff and money”, “Software everyone uses” and “Technology and rooms”. Each comes with a catalogue to tick, 132 entries in all, such as “Accounting software (DATEV, Lexware, sevDesk, lexoffice)” or “Laptops and desktops”.

Then come “Which software exactly, and from whom?” and “Which technology exactly, and from whom?”. For each entry they record what you actually use, what for, whether it runs in house or in the cloud, and who provides it.

The directive counts policies on risk analysis and asset management among the minimum measures. In Germany, the BSIG asks for concepts for managing your ICT systems, products and processes; a list is the usual first step.

A complete, up to date inventory is required in so many words by Implementing Regulation (EU) 2024/2690, Annex point 12.4. It applies directly only to certain digital services, such as cloud and data centre providers.

Art. 21(2)(a) and (i) NIS 2 · § 30(2) no. 1 and 9 BSIG

What does the AI not do with the inventory?

It does not finish item 2.2, and it takes nothing off the list: none of its tools deletes an entry from this list. If something wrong is on it, you take it off in the app.

It works on items that are still open or that you set aside. Once you have finished 2.2, the server takes nothing more from the assistant on that item; you make changes in the app.

While an item that relies on this list is signed off, such as 2.2 itself or 4.4 on backups, the tools refuse any change to the list. They name the items concerned.

The change would take that sign-off back. That is a person's step in the app, and the item then goes to management again.

How do I check what the AI entered?

Every screen an assistant wrote carries a mark at the top, for example “Filled in by the assistant claude-code/2.1.287 on 16 October 2026”. The assistant gives that name itself. The mark stays even if you change the screen afterwards.

The activity log lists every change under the name of the person who connected the assistant, with “via” and the assistant's name. That keeps changes made in the browser apart from changes made through the assistant.

Before you finish, go through all four lists and both detail screens. Look out for software you rent from the cloud, such as email or accounting: the walkthrough names it as often missed, and a plain device list will not contain it.

How the walkthrough does it

Item 2.2 turns into work on six screens, and item 2.3 builds directly on it.

2.2, the four lists from “What your company does every day” to “Technology and rooms”: the assistant ticks catalogue entries and adds entries of its own from your records.

2.2, “Which software exactly, and from whom?” and “Which technology exactly, and from whom?”: it records what exactly each thing is, where it runs and who provides it. Those providers then appear on your supplier list in 5.1.

You go through every screen that carries the assistant's mark, take off what is wrong, add what is missing and finish 2.2 in the app.

2.3 “Rate your risks”: every piece of software and technology on the list gets a level from frequency and damage. Management signs off at the end, in 7.3.

Common questions

Do I have to go through the whole catalogue myself?

No. You check what is on the list, add what is missing and take off what is wrong in the app. The walkthrough itself says the list does not have to be perfect: when something new comes along, you add it later.

Which records help the AI most?

What your company already keeps: your IT provider's inventory, a licence list, a CMDB export. For the providers, the list of creditors helps, because the provider is whoever sends you the invoice. Claude Code runs on your computer and can read such files there; an assistant in the browser gets the file however it accepts files, for example as an attachment in the chat.

What happens to the providers the AI names?

Every provider name not yet on your supplier list is added there as a new supplier, and is then already in 5.1. If the assistant leaves a provider out for a program, the two are no longer linked, and the provider stays on the supplier list. One call may name at most 50 different providers; for more, the assistant makes several calls.

Does the AI assistant itself belong in the asset inventory?

We recommend it, if you use one. Add it on “Software everyone uses” and its vendor on “Which software exactly, and from whom?”. The vendor then also appears on your supplier list in 5.1.

Does the vendor of my assistant see our inventory?

What the assistant reads goes to its vendor, under your company's agreement with that vendor. Which assistant you use is your choice. With an assistant and a model running on your own hardware, nothing leaves your network.

Read next

Sources

  • Directive (EU) 2022/2555 (NIS 2), Art. 21(2)(a) and (i), EUR-Lex
  • BSIG, § 30(2) no. 1 and 9, gesetze-im-internet.de
  • Implementing Regulation (EU) 2024/2690, Art. 1 and Annex point 12.4, EUR-Lex
  • open-isms, lib/durchgang/nis2.ts and lib/mcp/screens.ts (the screens of 2.2 and what an assistant sends there), github.com/NISD2/open-isms
  • open-isms, MCP server documentation, content/docs/self-hosting/mcp.md, github.com/NISD2/open-isms

In practice

Where this comes up in the walkthrough

The walkthrough turns this into steps you fill in, with the law explained beside each one. Open a step to see its screen, filled in for a made-up company.

  1. Risk Management

    Write down what your company has

    A list of the processes, software and devices you work with.

  2. Risk Management

    Rate your risks

    Place every piece of software, every device and every supplier on the matrix.

What the walkthrough costs

NIS2 walkthrough
Guided implementation at nisd2.eu.

€4,800 net a year, plus VAT

30 days money back

By invoice, due in 30 days. Cancel within the first 30 days, before the first export or sign-off: invoice cancelled or money back.

Guided NIS 2 implementation, step by step

A history of changes and sign-offs to show your regulator

Deadlines and reminders for each requirement

Security questionnaire for your suppliers

Export to PDF or CSV at any time

Pricing and terms

Been asked to handle NIS2?

In the end you have everything in one document: what is done, what is still open, and your management's approval with name and date. The app writes the texts.

Try 30 days, money back
Simon OrzelCory Hisey

Book a call

Free training for your Managing DirectorPricing and terms
The NIS2 walkthrough: your path step by step, the first items done