Set up and maintain your NIS2 file
The Cyber Security Act applies, with no transition period. Thousands of organisations are only now discovering that they fall under it. And their suppliers notice immediately afterwards: anyone subject to the law must assess their supply chain, so security questionnaires and contractual requirements follow. We establish where you stand and record what you have in place.
Three questions, no account, and no need to hand over your email address first.
Where organisations run into difficulty
"Do I actually fall under this?"
There is no letter. You must establish it yourself and register yourself. Sector and size determine it — but the largest group falls just outside and receives the requirements anyway, via customers who do fall under it.
Do the check →"My customer sent a security questionnaire"
Those questions always come down to the same ten topics, because they are based on the same provision. Only the form differs per customer: sometimes an Excel file, sometimes a portal. That is precisely why the second time round is much less work.
What it contains →"We do it, but it is not documented anywhere"
Back-ups, updates, password policy — almost everyone has them. Where things go wrong is proving it: no owner, no date, and no one who can show when the recovery was last tested. The duty of care demands exactly that.
The ten measures →Why you can check us
Every claim we make has its source: the article from the NIS2 Directive, or the national law that implements it. And the date on which we last checked that position — because the implementation differs per country and is still evolving. For a country where the law is not yet in place, we show no deadlines and no portal. There is nothing to report yet, and an invented portal is worse than none.
We do not report and register never on your behalf. That requires your own login credentials with your own supervisor, and that access should not be in a supplier's hands. What we do is prepare the text with the data from your file filled in; you submit it yourself.
The texts in the knowledge base are written with AI based on those sources, put through a technical review and approved by a person before they go online. We tell you that, on every page. See how we work.
What this is not: a certificate, an audit, a pentest or incident response. There is no NIS2 approval mark — no body issues that, not to us and not to anyone else. What you get is a file with which you can show what you have arranged. Demonstrability, not certification.
Latest articles
Is multi-factor authentication mandatory in the transport sector? Where it is and isn't expected
Multi-factor authentication appears in almost every NIS2 questionnaire for transport companies, but not every system is equally suited for it
Read more →Backups and recovery in the transport sector: when did you last test it?
A backup that has never been restored is an assumption, not certainty. This article explains why a recovery test in the transports
Read more →Incident registration in the transport sector: what do you record when things go wrong?
An overview of what a transport company records when a cyber incident occurs: from a hacked planning system to a down t
Read more →Start with the question of whether it applies to you
Three questions and you know where you stand — and what is then expected of you. Free, and it stays that way.
Do the NIS2 check