Skip to content

Secure the supply chain NIS2 holds you responsible for

Register the vendor, check it on criteria you set yourself, get the answers and documents out of it, then assess it as a risk in your NIS2 risk area and put a costed plan on what has to come down.

Unlimited users  •  Free onboarding and support  •  No commitment

Relations for the incident handling process: three assets, two suppliers and a processing activity
+400 companies use .legal
Region Sjælland
Aarhus Universitet
aj_vaccines_logo
Realdania
Right People
IO Gates
PLO
Finans Danmark
geia-food
Evida
Klasselotteriet
NRGI1
BLUE WATER SHIPPING
Karnov
Ingvard Christensen
VP Securities
AH Industries
Lægeforeningen
InMobile
AK Nygart
DEIF
DMJX
Axel logo
qUINT Logo
KAUFMANN (1)
SMILfonden-logo
kurhotel_skodsborg
nemlig.com
Molecule Consultancy
Novicell
The vendor list in .legal with four vendors, each with country, a certification such as ISO 27001, ISAE 3402 or SOC 2 and its number of assets

Supply-chain security under NIS2

Meridian knew who its vendors were. It could not say what any of them would cost.

Anders Krogh is CISO at Meridian Nordic, an energy group running around 1,200 active vendors and processors behind the metering platform, the customer portal and the field work. As an essential entity under NIS2 he is answerable for that chain, and the list he inherited told him who everyone was and nothing about what any of them could do to him. Now a vendor is checked on Meridian's own criteria, asked for the answers and documents Anders actually needs, and then assessed as a risk in its own right, with a plan and a price on the ones that matter.

  • The check happens once, on criteria Meridian set, and the result decides who gets looked at hardest.
  • Vendors answer and upload from their own inbox, so a chase for a certificate stops being an email thread.
  • The vendors behind a critical system are visible from the system itself, subcontractors included.
  • A vendor risk ends in a decision, not a colour: accept it, avoid it, or bring it down for a stated cost.

  • Your criteria, not ours

    Build the check you want, weight it yourself, and read a risk level that came out of your own answers.

  • No login for vendors

    They answer and upload documents from their own inbox, with no account and nothing to install.

  • The vendor as a risk

    Assess the vendor itself against concrete scenarios in a NIS2 risk area, with a justification on record.

  • A plan with a cost

    Accept it, avoid it or bring it down, and say what bringing it down is expected to cost.

A long list of suppliers with nothing attached to any of the rows, and a pile of documents lying apart from the list

Supply-chain security under NIS2

A list of vendors is not supply-chain security

Almost everybody has the list. What NIS2 asks about is what you did with it, and that is where most supply-chain work quietly stops.

  • The list says who a vendor is, not what would happen to you if they went down.
  • The evidence you gathered sits in a shared drive, so nobody can show what was checked, or when.
  • The one vendor everybody worries about is usually the one nobody has documented, because they are too big to chase.
The Classifications tab on Leverandør A/S in .legal with a completed data processor classification and a high risk

Supply-chain security under NIS2

Decide who deserves the scrutiny

Not every vendor needs the same treatment, and you should be the one deciding which is which. The classification is a questionnaire you build and answer yourself about the vendor, and it hands back a risk level.

  • Weight the sections, the questions and each answer option, and set the intervals that turn a set of answers into a level.
  • Nothing is scored for you, and nothing happens on its own: the level tells you who to look at, you decide what to send them.
  • Read the level rather than the number. The score runs the other way round to the level, which is exactly the sort of detail worth knowing before your first demo.
A new data processor audit in .legal sent to Leverandør A/S, Hosting ApS and CloudCo Ltd, each with country and contact

Supply-chain security under NIS2

Ask once, and let them answer from their inbox

You design the questionnaire: their security measures, their sub-vendors, the certificate you want a copy of. Then you send it, to one vendor or to a whole group of them at once.

  • The vendor needs no account. They open a link, answer, upload what you asked for, and it all lands on their record.
  • A group send gives every legal entity its own instance and its own contact, so responses stay separate and you can see who has opened and who has submitted.
  • The first reminder goes out on the notification date, a set number of days before the deadline, and then every 7 days until the vendor has answered.
A supplier card with a questionnaire that is never sent, and instead a sealed report attached to the supplier

Supply-chain security under NIS2

The vendor who will not fill in your questionnaire

Every security team has the same three or four of them: too large to care, and too central to drop. There is a route for that, and it does not involve sending anything.

  • Close the check out with an auditor's report instead: upload the document or register a link against the vendor.
  • No email goes out at all, and the vendor's status shows that a report is in place.
  • We do not tie that route to a named assurance standard, so what counts as a good enough report stays your judgement.
The supplier Hosting ApS assessed in the NIS2 risk area in .legal with high risk, an exposure of DKK 2,400,000, DKK 400,000 after mitigation and the scenario supplier outage

Supply-chain security under NIS2

Then assess the vendor as a risk, not just as a record

This is where the newer half of the story sits. With Enterprise Risk Management (ERM), released in August 2026 and part of the Enterprise offer, a vendor is an entity you assess, alongside processes and assets.

  • Put the vendor in a NIS2 risk area with its own matrix and appetite, add concrete scenarios, and state consequence and probability with a justification on each.
  • Decide what happens next: accept it, avoid it by stopping the activity, or mitigate it with a plan that carries an estimated cost and the exposure left afterwards.
  • A relationship graph shows the connections you have already mapped between your entities, so an inherited risk is something you can see and follow rather than something you assume.
Two separate measuring cards, a gauge and a row of bars, each pointing down to the same supplier with no link between them

Supply-chain security under NIS2

Two checks on the same vendor, and they do not feed each other

We would rather tell you this than let you find it in a demo. There are two ways to put a number on a vendor here, and they are separate mechanics.

  • The classification is your own questionnaire, answered internally, producing a level. The risk assessment is scenarios against a matrix, in ERM. Neither updates the other.
  • We build the plan, not the filling-in. The level and the assessment both come out of judgements you made, not out of anything we worked out for you.
  • The platform documents your supply chain, it does not watch it. Nothing is scanned and nothing arrives on its own, so there is no incident reporting and no alerting here.
.legal in practice

Features for supply-chain security under NIS2

The vendor, and the chain behind it

Vendors sit as legal entities with their sub-vendors registered centrally on them, and a Vendors tab on an asset shows which of them sit behind that system, subcontractors included.

A classification you design

Weight the sections, the questions and each answer option, set the intervals that turn an answer set into a risk level, and use the level to decide who gets looked at hardest.

One check, many vendors

Send the same questionnaire to a whole group of legal entities at once. Each gets its own instance and its own contact, and you follow who has opened it and who has submitted.

For the vendor that will not answer

Close the check out with an auditor's report instead. Upload the document or register a link, and the vendor's status shows a report is in place. No email is sent to them at all.

Vendor risk in a NIS2 risk area (Enterprise)

Assess the vendor against concrete scenarios in a risk area with its own matrix and appetite, with a justification required on both consequence and probability. This sits in Enterprise Risk Management (ERM), which shipped in August 2026 and is part of the Enterprise offer.

Accept it, avoid it, or price the fix

Three named treatments for a vendor risk: accept, avoid or mitigate. Mitigation is the one that produces a plan, and that plan carries a cost you can put in front of whoever approves the spend.

Supply-chain security under NIS2

Frameworks this covers

One framework, and the part of it this page is about.

  • icon-framework-NIS2

    NIS2

    The supply-chain security an essential entity has to run: which vendors sit behind your services, what you checked, what they answered, and what you decided about the risk.

    Read about NIS2
.legal compliance platform

Secure your supply chain with...

Do you need to get on top of the vendors behind your services? We recommend the following modules for that task.

Vendor Management

Where vendors live, and the audit engine behind the classification, the questionnaires and the auditor's report route.

Explore Vendor Management

Information and Cyber Security

Where the NIS2 framework, its controls and your security documentation sit, next to the vendor work on this page. Enterprise Risk Management, which assesses the vendor itself, is part of the Enterprise offer and priced in it.

Explore Information and Cyber Security

Our Customers

+400

companies

+11.000

users

+79.000

contracts

+14.000

processing activities

Mikkel Friis

Bech-Bruun

Mikkel Friis Rossa (Partner)

.legal's team has consistently demonstrated a commitment to innovation while being responsive to the needs of our mutual clients.

Rasmus-boutrup-fenerum

Fenerum

Rasmus Boutrup (Financial Controller)

Case Study
With .legal, we've gained a simpler and more manageable solution that better suits our needs
Michael Berner 1

Lægeforeningen

Michael Berner (Lawyer)

.legal has been the right choice for us. .legal are professional and welcoming with skilled employees.
Nanna Rodian Christensen

Molecule Consultancy

Nanna Rodian Christensen (HR & Operational Manager)

Case Study
Firstly, it means that not all the work is in one place (me), and secondly, that the understanding of GDPR is implemented throughout the organisation.
ulrikdueholmbeckmann

Plum Safety

Ulrik Dueholm Beckmann (QC, CM og ESG Lead)

Case Study
From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs.
julie-oxenvad-novicell

Novicell

Julie Oxenvad (Legal Consultant)

Case Study
We are satisfied with the switch to .legal – it has strengthened our compliance work, made processes easier to manage and more transparent, and improved cross-team collaboration
Tinna Schultz

Min By Media

Tinna Schultz (HR Manager)

Case Study
It just works! It is so easy and user-friendly, and the overview of processing activities is brilliant.
ansat_Kaspar_Rochholz_005

DMJX

Kaspar Rochholz (GDPR Coordinator)

Case Study
.legal has really understood what it means to create a user-friendly and efficient solution. Privacy is an attractive product compared to price and functionality.
Profile-picture1

Axel Kaufmann ApS

Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)

Case Study
.legal continuously update the platform to ensure their customers always remain compliant. In our view, any other choice would be a downgrade.

NRGi

Mette Mühlendorph (Compliance Specialist)

Case Study
The implementation of .legal has made a difference in the way we handle compliance. The system has created structure and overview, which has had concrete benefits.
Use cases

Find the job you need done

Every use case is a real piece of compliance work, told the way it actually runs in the platform. Filter by who you are, what you work with, and which frameworks you answer to.

Book demo

24 use cases

Legal counsel

Run due diligence on your vendors

Classify a vendor on your own criteria, get the answers and documents you need with no login for them, and move the approved ones straight into contracts.
See vendor due diligence
CISO & IT security

Get NIS2-ready without starting from scratch

Build on the ISO 27001 work you've already done, switch NIS2 on, and let a simulated score show how far ahead you already are.
See NIS2 readiness
Compliance & GRC lead

Build one risk register for the whole organisation

One register across GDPR, NIS2, AI and information security, where each risk area keeps its own matrix, scale and appetite. It runs in ERM, the risk assessment module.
See the risk register
CISO & IT security

One incident log for GDPR and NIS2

A personal data breach and a security incident go in the same register, each with a template made for its type. Record it, attach the documentation, delegate the follow-up, and export it when somebody asks.
See the incident log
DPO

Every data processing agreement, and the ones that are missing

Put every data processor next to its agreement and the gaps stop hiding. Register the agreement once, reference it from everything that relies on it, and change it in one place.
See the agreements and the gaps
Compliance & GRC lead

Run awareness training that reaches every colleague

Send out training and policies, chase the stragglers automatically, and prove every colleague completed it. You bring the material, we run the rails.
See awareness training
A laptop showing a shield with a tick next to a list Executive & board

Run NIS2 without a security team

You keep the decisions, a partner does the advice and implementation, and the platform holds the structure, the templates and the follow-up. Task by task.
See who does what
A globe with a shield and a cog CISO & IT security

Risk-assess your critical assets under NIS2

Flag the assets your services depend on as critical, add them by hand to a NIS2 risk area in Enterprise Risk Management, and assess them against scenarios from the catalogue.
See the critical asset assessment

Frequently Asked Questions about supply-chain security under NIS2

What does supply-chain security under NIS2 actually look like in .legal?

As a sequence rather than a feature. You register the vendor, classify it on criteria you set yourself, send it a questionnaire and collect the documents you asked for, and then, with Enterprise Risk Management (ERM), part of the Enterprise offer, assess the vendor itself against concrete scenarios in a NIS2 risk area and decide what to do about the result. The platform stands the sequence up and keeps the record of it. It does not tell you which vendors are in scope, and it does not judge your chain for you.

Getting NIS2-ready without starting from scratch

How do we decide which vendors to look at hardest?

With a classification you design. You choose the questions that matter to you, weight the sections, the questions and each answer option, and set the percentage intervals that turn a set of answers into a risk level. Nothing is scored for you. One thing worth knowing before a demo: the score runs the opposite way to the level, so a higher score means a lower risk. That is why we talk about the level and not the number, and why you should too.

Running the due diligence check itself

Is the classification the same thing as the risk assessment of the vendor?

No, and this is the seam most people find on their first demo, so we would rather say it here. The classification is a questionnaire you designed and answer yourself about the vendor, and it produces a risk level. The risk assessment in Enterprise Risk Management is a different mechanic: the vendor is an entity in a risk area, assessed against concrete scenarios on a matrix you configured. They sit side by side and they do not feed each other. A classification level does not become a risk assessment, and a risk assessment does not update a classification.

Does the vendor need a login to answer us?

No. You register a contact person on the vendor and pick that contact when you send. The link arrives in their own inbox, and they can both answer the questions and upload the documentation without ever creating an account. How they pull the answers together internally is up to them, and whatever comes back is filed against that vendor.

Can we send the same check to a lot of vendors at once?

Yes. One questionnaire goes out to a whole group of legal entities in a single send, and each one still gets its own instance with its own contact, so responses stay split per vendor. You see how many have opened it and how many have submitted. Reminders to anyone who has not responded go out automatically: the first on the notification date, a set number of days before the deadline, and then every 7 days until the audit is answered.

Our biggest vendors refuse to fill in our questionnaire. What then?

You close the check out with an auditor's report instead of sending anything. Either exclude the vendor from the send with the auditor's report as the reason and upload the document, which then also appears under that vendor's documents, or register it directly from the vendor's audit tab with a responsible person and a document or a link. No email goes to the vendor, and the status shows that a report is in place. We do not tie that route to any named assurance standard, so what the report has to be is your call.

Can we risk-assess a vendor, or only document it?

You can assess it. Vendors are one of the entity types Enterprise Risk Management assesses, alongside processes and assets, so a vendor is assessed directly rather than only inheriting risk from a system it sits behind. You choose which entities a risk area assesses, so nothing is attached by default, and you then add scenarios to the vendor and state consequence and probability with a justification on each. Enterprise Risk Management is part of the Enterprise offer and was released on 14 August 2026, and it sits beside the risk assessment you may already be using rather than replacing it.

Can we see which vendors sit behind a critical system?

Yes. Each asset has a Vendors tab showing the legal entities linked to it, including subcontractors, and sub-vendors are registered centrally on the vendor itself rather than typed in again everywhere it is used. With ERM there is also a relationship graph, and read from the vendor end it shows the same connections the other way round: which systems and processes a given vendor sits behind, so the reach of one vendor's risk is something you can actually see.

If a vendor has an incident, does .legal report it for us?

No, and we would rather be plain about it than let you find out later. There is no incident reporting to an authority in the platform, no statutory timers and no submission of any kind. What you get is the record: what you knew about the vendor, when you checked it, what it answered, how you assessed it and what you decided to do. We build the plan, not the filling-in. The platform documents your supply chain, it does not monitor it, so it is not a detection tool of any kind.

One incident log for GDPR and NIS2

Still unsure?

Ask Johannes directly, he runs most demos personally

Book him here
+400 companies use .legal
Region Sjælland
Aarhus Universitet
aj_vaccines_logo
Realdania
Right People
IO Gates
PLO
Finans Danmark
geia-food
Evida
Klasselotteriet
NRGI1
BLUE WATER SHIPPING
Karnov
Ingvard Christensen
VP Securities
AH Industries
Lægeforeningen
InMobile
AK Nygart
DEIF
DMJX
Axel logo
qUINT Logo
KAUFMANN (1)
SMILfonden-logo
kurhotel_skodsborg
nemlig.com
Molecule Consultancy
Novicell