Montro
NIS2 compliance register

Supply-chain records that keep pace with your suppliers

NIS2 sets cybersecurity risk-management duties for essential and important entities across 18 sectors, and national transposition is rolling out across member states. Article 21 includes supply-chain security, taking into account the practices of each direct supplier.

Montro keeps the suppliers behind your network and information systems in one register, each with an owner. Changes are raised with their source, the supplier confirms them, and your team decides.

Framework

How NIS2 is structured

NIS2 covers medium and large organisations in 18 sectors, split into essential and important entities, and requires each to manage cybersecurity risk, including risk from its suppliers. Both take the same security measures under Article 21, while supervision is stricter for essential entities. Management bodies approve and oversee those measures.

Scope

Essential and important entities

Annex I lists sectors of high criticality, Annex II other critical sectors. Size and role decide which category applies.

Measures

Article 21 risk management

Ten areas of measures, from incident handling to supply-chain security, set in proportion to the risk.

Supply chain

Each direct supplier, considered

Article 21(3) asks entities to consider each direct supplier’s vulnerabilities and cybersecurity practices, including secure development.

How Montro helps

Supply-chain records you can show

Montro builds the record of who your network and information systems depend on, from the identity, finance and cloud systems you already run.

Organisation info — EU hosting and regulatory scope

Each supplier tied to what it supports

Every entry records the business function the supplier supports, so the effect of a change is clear before anyone decides.

Lapsed certificates raised

When a supplier’s security certificate lapses, it appears against that supplier’s entry for the owner to review.

A summary for the management body

Supplier posture rolled up with the exceptions that need attention, giving the people who approve NIS2 measures something concrete to oversee.

Book a conversation

What you get

What the record does for you under NIS2

Three things that help when NIS2 questions come from your board, a client or your authority.

Incidents

Facts on hand when a supplier incident hits

The supplier’s entry already holds the contract, owner and history. Montro supplies the facts and timestamps; your team writes the notification.

Proportion

Review time where it matters

Suppliers are tiered by how critical they are to your systems, so attention goes to the few that carry the most weight.

Transposition

One record, whatever the national rules

Member states are transposing NIS2 at different speeds. The supplier record you keep stays the same while the national detail settles.

Governance

NIS2 Article 20: accountability at the top

NIS2 Article 20 makes the management body approve the cybersecurity measures, oversee how they are carried out and take regular training, and its members can be held liable for failures. National law can hold its members accountable when those duties are not met.

Montro gives the management body a supplier record it can approve with confidence. Every supplier decision carries its owner, the evidence behind it and the date it was made. When the board is asked how supply-chain risk is overseen, the answer is already on file.

Questions

What NIS2 covers, when it applies, and what it asks of your suppliers.

NIS2 applies through each member state’s national law. Member states had until 17 October 2024 to transpose it, and that work is still rolling out. It covers medium and large organisations in the sectors listed in its annexes, from energy, transport and health to manufacturing and digital providers. Your sector and size decide whether you are an essential or an important entity.

Article 21 treats it as risk that comes from your direct suppliers and service providers. For each one, you are asked to take into account its vulnerabilities, the quality of its products and its cybersecurity practices, including how it develops software securely.

Yes. The duty sits with your organisation, not with the supplier. Article 21 asks you to address the security of your relationships with direct suppliers, whether or not those suppliers fall under NIS2 themselves.

NIS2 replaces the 2016 NIS Directive. It reaches more sectors and uses a size threshold to decide who is in scope, where member states used to name operators themselves. It also adds supply-chain security to the required measures, sets out staged incident reporting, and holds the management body accountable.

NIS2 does not set a format. What matters is that the record stays current and that you can show how each supplier was reviewed. Montro keeps the supplier register in one place, raises changes with their source, and asks the supplier to confirm. Your team decides, and each review stays with the supplier’s entry.

Keep reading

The same suppliers, under other rules

A supplier you track for NIS2 often belongs in your other records as well. These pages cover them.

EU AI Act

When a supplier switches on AI inside a product you approved, it may need an entry in your AI inventory.

Read more

DORA

For financial entities, DORA’s ICT rules take precedence, and suppliers belong in the register of information.

Read more

GDPR & RoPA

Suppliers that handle personal data for you are processors and belong in your record of processing.

Read more

Third-party records are becoming decision logs. The firms that get this right will be the ones that can show who decided, on what evidence, and when.

  • Pen-test summary on request
  • Frankfurt hosting
  • Sample register
  • Expert Series guests
  • Cyber Ireland member

See it on your own suppliers

A read-only connection, about an hour to set up, and a named person who can say yes to a decision.

Priced to scope — never per seat, never per supplier. Upgrade only when the evidence earns it.

Montro AI discovery audit dashboard