Risk analysis and security policies
Is there a written security policy approved by management, and a risk analysis reviewed at least once a year?
Directive (EU) 2022/2555 requires essential and important entities in 18 critical sectors to manage their cybersecurity risks (art. 21), to report significant incidents (art. 23) and to have their management approve the measures and undergo training (art. 20). Each country transposes it with its own law.
They are the minimum of art. 21.2, points (a) to (j), with their official wording. Answer each one honestly: Yes, Partly, No or N/A. The score counts Yes as 1 and Partly as ½ over the ones that apply, and the Plan orders what is missing. Each measure links to the Jarroba tools that genuinely check part of it.
Guidance based on the directive: sector in Annexes I or II, size (Recommendation 2003/361/EC: headcount, turnover and balance sheet) and the cases in scope regardless of size. It is not legal advice: each country’s law can add requirements or designate specific entities.
What you answer is a map of your security gaps. It is saved only in this browser, does not travel in the link and is not sent anywhere. You can export it to a file from the toolbar or delete it.
Saved only in this browser. Each measure’s text is the official wording of art. 21.2 of the directive.
Is there a written security policy approved by management, and a risk analysis reviewed at least once a year?
Do you know how to detect an incident, who decides, and how to report it to the CSIRT in time (early warning in 24 h, notification in 72 h, final report within a month)?
Are there offline backups, has restoring them ever been tested, and is there a plan to keep working if a key system goes down?
Do you know which suppliers and dependencies each service relies on, and do you require security from them by contract?
Are dependencies with known vulnerabilities reviewed, is patching done on deadlines, and is there a channel for outsiders to report a flaw to you?
Do you actually check that the measures work (audits, tests, drills) and fix what comes up?
Does all staff receive training, management included (art. 20.2), and are there basic rules: passwords, updates, suspicious email?
Is it decided what gets encrypted (in transit and at rest), with which algorithms, and who manages keys and certificates?
Is there an asset inventory, does each person have only the permissions they need, and are they removed when they change roles or leave?
Is a second factor required for the access that matters (email, VPN, admin, cloud), and is there a secure channel for an emergency?