Preparing for a NIS2 review
Keep a clear record of how you handle vulnerabilities
Review dependency findings, assign owners, and record what your team decides. Use the history to explain how you handled each finding.
What this covers
Where vulnerability records fit
Directive (EU) 2022/2555 (NIS2), Article 21
Article 21 includes vulnerability handling and disclosure among its security measures. Check the national rules that apply to your organisation and the evidence your reviewer needs.
Before the review
What your reviewer asks for, and where it lives in Proveta
Confirm the evidence you need with your reviewer.
01How reported vulnerabilities reach the right people
Findings from every connected repo land in one ranked list, and each gets an owner who’s responsible for the next step.
02Who’s responsible for each decision
Each decision names an owner and the person who recorded it. A later change adds to the history and keeps the earlier decision.
03Fix records or accepted risks with review dates
Give each accepted risk an owner, a reason, and an expiry date. Proveta flags risks nearing expiry and emails the owner when one expires.
04Time limits and a record of missed deadlines
Set deadlines by severity and see where findings stayed open too long. Missed deadlines stay on record for your review.
Start now
Prepare for your NIS2 review
Scan your dependencies, bring in your Dependabot alerts, and export the decision record for your NIS2 review dates.
- Free for 1 repo
- Your team controls merging
- No password to create