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.
Modules
.legal AI
All AI features →Integrations
See all integrations →Platform & features
Understand the rules
See it in action
All customer stories →Plan your switch
Stay up to date
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
Supply-chain security under NIS2
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.
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.
Supply-chain security under NIS2
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.
Supply-chain security under NIS2
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.
Supply-chain security under NIS2
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.
Supply-chain security under NIS2
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.
Supply-chain security under NIS2
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.
Supply-chain security under NIS2
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.
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.
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.
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.
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.
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.
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
One framework, and the part of it this page is about.
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.
Where vendors live, and the audit engine behind the classification, the questionnaires and the auditor's report route.
Explore Vendor ManagementWhere 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 Securitycompanies
users
contracts
processing activities
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
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.
24 use cases
No use cases match that combination yet. Try removing a filter.
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 scratchWith 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 itselfNo, 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.
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.
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.
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.
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.
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.
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