Write usable security rules
Short label: RULES
Meaning
Write short instructions explaining how staff should use systems, handle information and report problems.
Why it matters
A clear rule helps people make a consistent decision without guessing.
What you can do
Start with software installation, suspicious messages and approved storage. Name the owner of each rule and make it easy to find.
Services that can help
Workshops help write practical rules. Sovereign Code adds agreed rules for code storage, company accounts and access keys.
Official reference — NIS2 Art. 21(2)(a)
2. The measures referred to in paragraph 1 shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the following:
— Directive (EU) 2022/2555 (NIS2), Art. 21(2)
(a) policies on risk analysis and information system security;
— Directive (EU) 2022/2555 (NIS2), Art. 21(2)(a)
You must know your risks and write down how you protect your systems: a risk analysis and a security policy, kept up to date.
Read the article on EUR-Lex → · Official text, quoted from the Official Journal of the EU
Acronyms used here: NIS2, GDPR, DORA, CRA
- NIS2 — Network and Information Systems Directive 2
- An EU cybersecurity directive with requirements for organisations covered by its scope.
- GDPR — General Data Protection Regulation
- The EU regulation on personal-data protection. RGPD is the French name and AVG the Dutch name.
- DORA — Digital Operational Resilience Act
- EU rules on digital operational resilience in the financial sector.
- CRA — Cyber Resilience Act
- EU cybersecurity rules for products with digital elements, including certain software and connected devices.