This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Policies and standards: which few do you need, and does anyone follow them?
This quarter, cut your security documents to one management-approved information security policy, an acceptable use page and about six topic policies of short, testable "must" rules, each with an owner and, wherever possible, a setting that enforces it. Review them at least yearly and after significant incidents or changes by checking each rule against the live settings, and keep one mapping table so the same set serves ISO 27001, Grundschutz++ and NIS2 audits.
If you only do five things
Keep one short, signed policy on top.
Two to five pages: scope, objectives, roles, topic policies, approval date. The BSI says more than 20 pages hasn't worked in practice9.
Cut the rest to about six topic policies.
ENISA counts ten that 2024/2690 requires of digital providers and lets you merge them3.
Write rules you can test.
One sentence per rule, saying who must do what, and one owner per document. Mark advice as advice, as the NCSC asks15.
Review against the settings, not the calendar.
Each year, compare every rule with a settings export, open exceptions and recent incidents, and log what changed.
Four document levels, and who signs each
Policy: what and why?
Intentions and direction formally expressed by management, as ISO/IEC 27002 defines a topic-specific policy3. 2024/2690 has digital providers' management body approve the top policy, an appropriate level of management the topic policies2.
Standard: which settings, exactly?
Mandatory settings, such as MFA methods, patch deadlines and baselines; NIST calls standards normally compulsory14. Our rule: the heads of security and IT approve them.
Procedure: which steps?
Steps for one task, such as creating an admin account14. The process owner approves them; in BSI terms, Arbeitsanweisungen9.
Guideline: what do we advise?
Advice that can be followed in more than one way14, published by its author without formal approval.
The documents you actually need
- Information security policy. Approach, objectives, resources, roles, topic policies, records, indicators and approval date, from 2024/2690's list2. ENISA maps it to ISO 27001 clause 5.2 and A.5.14.
- Acceptable use. One or two pages on devices, accounts, data, AI tools, reporting and sanctions8. Training: the security awareness sheet.
- Risk management. Method and acceptance1; see the risk register sheet.
- Access control. Accounts, MFA, admin accounts, joiners and leavers2.
- Incidents, continuity and backup1; see the incident response, backups and business continuity sheets.
- Suppliers. Criteria and contract clauses2; see the third-party risk sheet.
- Data handling and encryption. Classification, media, disposal, keys2.
- Development, change and testing, if you build or run software.
Write rules people follow
- One rule, one sentence, one "must". "Admins must sign in with a security key" can be tested; "appropriate authentication" can't. Write advice as "should", so staff can tell the two apart15.
- Name the owner, setting and evidence. The owner keeps the document current9; each rule names its setting and the report that proves it.
- Write for the reader. One page for staff, standards for admins. The CAF rates rules too detailed to remember as not achieved16.
- Ask the people who do the work whether each rule is usable15.
- In Germany, involve the works council. It co-determines rules on staff conduct and technical monitoring (BetrVG § 87(1) nos. 1 and 6)24.
What changed in 2026
- German duties apply. Since 6 December 2025, with no general transition period, the BSI expects processes, responsibilities and measures in writing and reviewed regularly6.
- Grundschutz++ arrived. BSI-Standard 300-1 (20 October 2026) has management release the policy and requires document control10. Certification applications open on 1 January 2027; classic IT-Grundschutz stays certifiable until 30 November 203111.
Approval and review
- NIS2. Management bodies approve the measures, oversee them and can be held liable1; digital providers date the approval in the policy2.
- Germany. BSIG § 38 has management implement and oversee the § 30 measures, whose compliance must be documented5. Minute the approval; the BSI recommends resolutions as proof of involvement7.
- Topic policies one level down, by the role the top policy names.
- Yearly and on triggers. Digital providers' management reviews the top policy at least annually and after significant incidents or changes2. Add new laws, audit findings3, new technology or an acquisition13.
- Stagger the rest: review each yearly9, two or three a quarter.
Versions, publishing and sign-off
- Same header everywhere. Title, owner, version, last and next review, approval, classification and distribution9, plus a change log.
- One source, one place to read. A versioned library or Git, one intranet page and old versions archived centrally8.
- Acknowledge at hire, yearly and on change13. 2024/2690 requires it for the top policy, from relevant staff and external parties2; ENISA accepts a digital one or a contract clause3.
- Collect it at sign-in. Entra terms of use (Entra ID P1) can require reacceptance of each version; deleting the terms or losing P1 deletes the records, so export them18.
Exceptions
- Write the route into the top policy. ENISA expects one, with requests, approvals and compensating controls on record and open exceptions reported to management. It has management bodies approve exceptions to the top policy itself3. Other levels: the risk register sheet.
- Count them per rule at each review. A rule that collects exceptions needs rewriting or funding.
One set for several audits
- One table, one row per rule: owner, setting, evidence, ISO 27001 Annex A control, Grundschutz++ or IT-Grundschutz requirement, NIS2 Article 21(2) point, BSIG § 30(2) number.
- Start from official tables. ENISA maps 2024/2690 to ISO/IEC 27001:2022 and CSF 2.04, the BSI § 30 BSIG to ISO 2700112. A mapping isn't equivalence, ENISA warns3. Certification: the ISMS sheet.
Mistakes that cost the most
- A template nobody adapted. It names tools you don't run. Yet SANS's templates, made with CRF20, can't be adapted without permission: SANS allows personal, non-commercial use without changes21, CRF internal business use without derivative works22. Use them as checklists.
- Settings that contradict the policy. It demands 90-day password changes, NIST says not to23, and your tenant doesn't.
- Reviews that only change the date. A new date without a change log shows nobody weighed the incidents and findings.
- A signed policy as the goal. The BSI asks for proof of effectiveness7.
What you can skip
- A 40-document library. ENISA accepts the topic policies in one document3.
- Signatures on every standard. Staff acknowledge the top policy and the acceptable use page.
- A policy tool before the first review. A versioned library and one intranet page will do.
- One set per framework or customer. Add a mapping column instead.
- Legal prose. Short sentences hold up better in audits.
What this looks like at your size
Small team, no security staff
- Write the top policy and acceptable use page with your IT provider; the managing director signs.
- Adapt CIS's acceptable use template for internal use; don't publish or sell your version19.
- Collect acknowledgment at onboarding and yearly.
Growing, with IT or security staff
- Keep a top policy, acceptable use and six topic policies with owners, and standards below them.
- Collect acknowledgment with Entra terms of use.
- Review two or three documents a quarter against settings exports.
Enterprise or regulated
- Approve one group policy and have each regulated entity's management adopt it with local annexes.
- Keep the mapping table in the GRC tool, linked to configuration checks.
- Have internal audit test a sample of rules yearly.