5.01.01 | Board-adopted information security policy with the required content | 0 |
5.01.02 | Annual policy review aligned with governance cycles | 0 |
5.02.01 | Board-defined roles and responsibilities across security, privacy, OT and BCM | 0 |
5.02.02 | Appoint a CISO authorised to advise and report independently | 0 |
5.04.01 | Regular cyber awareness courses for board and staff, and demonstrable board competence | 0 |
5.05.01 | Register of officials holding formal contacts with agencies and regulators | 0 |
5.08.01 | Explicit risk assessment for new systems and significant changes | 0 |
5.09.01 | Complete and verified asset inventory including OT, remote and cloud assets | 0 |
5.10.02 | Rules of conduct for asset use in contracts of external staff and volunteers | 0 |
5.10.03 | All employees formally made aware of the code of conduct for asset use | 0 |
5.12.01 | Classify information in all systems with an explicit risk assessment and impact methodology | 0 |
5.14.01 | Internet-facing systems and email comply with the mandatory open standards, monitored via internet.nl | 0 |
5.14.02 | Organisation Validated certificates for sensitive web traffic | 0 |
5.14.03 | Electronic signatures conform to the AdES baseline profiles | 0 |
5.14.04 | Up-to-date records of internet-facing systems, web applications, IP addresses and APIs | 0 |
5.14.05 | Publish public websites in the Government Register of Internet Domains, refreshed every six months | 0 |
5.15.01 | Access to a trusted zone only from authenticated devices or a secure enclave | 0 |
5.16.01 | Formal registration and de-registration procedure for user identities | 0 |
5.16.02 | Group accounts only when motivated, recorded and agreed with the CISO | 0 |
5.17.01 | Multi-factor authentication, mitigations where it is impossible, and authentication data management | 0 |
5.17.02 | Password manager available to all employees | 0 |
5.17.03 | Automated enforcement of password requirements | 0 |
5.18.01 | Monitor creation and modification of privileged accounts; unauthorised changes are incidents | 0 |
5.18.02 | Annual review of all access rights, with risk-based higher frequency | 0 |
5.19.01 | Risk-based information security requirements in every request for proposal | 0 |
5.20.01 | Security requirements written into procurement contracts | 0 |
5.20.02 | Exclude suppliers' general terms and define acceptable, mitigated and never-accepted consequences | 0 |
5.20.03 | Supplier demonstrates setup, existence and operation annually through independent assessment | 0 |
5.20.04 | Entity's own investigations, including the option of an external audit, and treatment of residual risk | 0 |
5.20.05 | Supplier transparency on vulnerabilities and incidents, including data leaks | 0 |
5.20.06 | Pre-contract dependency assessment and a detailed exit strategy | 0 |
5.21.02 | Supplier discloses its subcontractor chain and risks before contracting | 0 |
5.21.03 | Security requirements flow down the subcontractor chain, exclusions justified | 0 |
5.21.04 | Supplier reports changes in the subcontractor chain and their risks during the contract | 0 |
5.21.05 | Include supply chain security in the entity's risk analysis | 0 |
5.22.01 | Process owner reviews supplier compliance annually and treats the risks | 0 |
5.22.02 | Up-to-date register of suppliers and contracts | 0 |
5.23.01 | Cloud service provider policy covering inventory to termination, reviewed every three years | 0 |
5.24.01 | Low-threshold notification desk for all internal and external staff | 0 |
5.24.02 | Notification desk tasks and responsibilities in an incident reporting procedure | 0 |
5.24.03 | Process owner responsible for resolving incidents | 0 |
5.24.04 | Monthly incident follow-up report to the person ultimately responsible for operations | 0 |
5.24.05 | Incident procedure references the crisis management procedure | 0 |
5.24.07 | Incident procedure: statutory CSIRT reporting, CSIRT notifications and notifying PII principals | 0 |
5.24.08 | Coordinated Vulnerability Disclosure procedure, published, with reports feeding incident records | 0 |
5.26.02 | Handle incidents through the incident management process, with regulatory reporting built in | 0 |
5.27.01 | Root cause analysis and improvements after incidents | 0 |
5.27.02 | Share incident analysis reports widely among relevant partners | 0 |
5.28.01 | Retain incident information for at least three years | 0 |
5.30.01 | Annual test of continuity plans by the process owner | 0 |
5.30.02 | Identify critical systems in the asset inventory and update at least every three years | 0 |
5.33.01 | Retention periods set in selection lists, implemented and tested | 0 |
5.35.02 | Annual audit plan deciding which systems get which security audit | 0 |
5.36.01 | Information security reporting in the P&C cycle leading to an annual In Control Statement | 0 |
6.01.01 | Established screening policy, with Certificate of Conduct on a risk basis | 0 |
6.02.01 | Staff made aware of their security responsibilities on joining or changing roles, with easy access to the rules | 0 |
6.03.01 | Everyone shares responsibility and knows the rules, including for classified environments | 0 |
6.03.02 | Security awareness training completed within three months of appointment | 0 |
6.03.03 | Management promotes and encourages periodic security training | 0 |
6.03.04 | Secure mobile working behaviour in awareness programmes | 0 |
6.08.01 | All staff demonstrably informed of the incident notification procedure | 0 |
7.01.02 | Critical information never reachable through a single secure zone | 0 |
7.02.01 | Warnings on specific security risks shared within the government security domain | 0 |
7.07.01 | Automatic lock on removal of a chip card token | 0 |
7.10.01 | Removal instruction for reusable media leaving the entity | 0 |
7.10.02 | Verify and report irretrievable removal, using NBV-advised products where possible | 0 |
7.10.03 | Couriers for classified information meet predefined reliability requirements | 0 |
8.01.01 | Zero footprint on mobile devices, or encryption-based access control with remote wipe | 0 |
8.01.02 | Patching and hardening, MDM or MAM, signed mobile working agreement, checked periodically | 0 |
8.02.01 | Quarterly assessment of special privileges | 0 |
8.03.01 | Physical or logical isolation of information of specific importance | 0 |
8.03.02 | Need-to-know access to information of specific importance | 0 |
8.05.01 | Risk assessment before granting network access to external suppliers, with a rights register | 0 |
8.07.01 | Risk- and need-based restriction of downloads, always scanned | 0 |
8.07.02 | Users informed about risky browsing and unknown links | 0 |
8.07.03 | Anti-malware and recovery software kept up to date | 0 |
8.07.04 | Malware scanning across all environments, downloads and received files | 0 |
8.08.01 | Mitigate high-likelihood, high-damage vulnerabilities within a week | 0 |
8.08.02 | Mitigation approach based on an explicit risk assessment | 0 |
8.08.03 | Interim mitigations where installation cannot happen within a week | 0 |
8.08.04 | Technical compliance checks, with continuous testing of internet-facing systems | 0 |
8.08.05 | Automated penetration test at every release of internet-facing systems; annual test; no go-live with unmitigated high risks | 0 |
8.13.01 | Backup policy with storage and protection requirements, ransomware-resistant and integrity-preserving | 0 |
8.13.02 | Maximum data loss and recovery time set by explicit risk assessment | 0 |
8.13.03 | Location-separated backup storage | 0 |
8.13.04 | Annual recovery test, or after a big change | 0 |
8.15.01 | Minimum content of a log entry | 0 |
8.15.02 | Log entries never contain data that could cause a security breach | 0 |
8.15.03 | List of generated log files | 0 |
8.15.04 | Risk-based retention of logs and SIEM data allowing for long-undetected attackers | 0 |
8.15.05 | Improper modification or deletion of log data is an incident | 0 |
8.15.06 | Independent periodic verification that log files remain unchanged | 0 |
8.16.01 | Share newly discovered attacks with the designated CERT | 0 |
8.16.02 | SIEM and SOC rules on when to report incidents to responsible managers | 0 |
8.16.03 | Detection and response solution for the information processing environment | 0 |
8.16.04 | Logging and log monitoring on active network components | 0 |
8.18.01 | System utilities restricted to authorised staff when strictly necessary | 0 |
8.18.02 | Log use of system utilities and keep the logs six months | 0 |
8.19.01 | Control the risk of users installing unauthorised software | 0 |
8.20.01 | Network components meet the confidentiality level of their network | 0 |
8.20.02 | Management interfaces separated from the user network | 0 |
8.21.01 | Flag and mitigate availability attacks at connection points with external or untrusted zones | 0 |
8.21.02 | Detection tools monitoring traffic to and from the trusted environment | 0 |
8.21.03 | Share newly identified threats within government | 0 |
8.21.04 | Encrypt wireless and external wired transmissions, risk-based, with NBV-advised tools where possible | 0 |
8.22.01 | Each segregated network group has its own security level | 0 |
8.24.01 | Cryptography policy with the required topics | 0 |
8.24.02 | Cryptographic controls in the asset inventory with use, ownership and currency | 0 |
8.24.04 | Cryptographic strength per NCSC and AIVD Resilience Unit recommendations | 0 |
8.24.05 | Backup certificates from an alternative supplier where continuity risk requires | 0 |
8.27.01 | Security by design and by default principles adopted and applied in all development | 0 |
8.29.01 | Structured, automated-where-possible acceptance testing with reported results | 0 |
8.30.01 | Internal development measures apply fully to outsourced development, plus outsourcing measures | 0 |
8.31.01 | No testing in production without the process owner's prior approval | 0 |
8.31.02 | Significant production changes always tested first unless the process owner approves otherwise | 0 |
8.32.01 | Change management covering administration, risk assessment with roll-back plan, and approval | 0 |
8.32.02 | Change management based on a generally accepted framework | 0 |
P1-1-3 | Reading guide, purpose and application | 0 |
P1-10 | Supervision | 0 |
P1-11 | Other applicable standards, laws and regulations | 0 |
P1-11.1a | Mandatory application of the BIO under the Cybersecurity Act and board responsibilities | 0 |
P1-11.1b | Board and staff training and notification of significant incidents | 0 |
P1-12.2 | Line management owns information systems and applies the measures | 0 |
P1-12.3 | CISO role | 0 |
P1-13 | Pass BIO obligations to suppliers in purchase requirements | 0 |
P1-14-15 | Information security principles and a balanced set of measures | 0 |
P1-16 | Determine additional measures by type of information | 0 |
P1-17 | Assess incident impact across the required impact areas | 0 |
P1-18 | Connection with other topics | 0 |
P1-4a | Establish an ISMS to NEN-EN-ISO/IEC 27001 that covers at least the critical processes and systems | 0 |
P1-4b | Select controls from NEN-EN-ISO/IEC 27002 plus the mandatory government measures | 0 |
P1-4c | Operationalise the measures and prove their setup, existence and operation | 0 |
P1-5-6.1 | The management system, harmonized structure and context assessment | 0 |
P1-6.2 | Apply a risk management methodology with the required components | 0 |
P1-6.3-6.5 | Identify, analyse and treat risks, with government measures always mandatory | 0 |
P1-7 | Statement of Applicability with BIO measures and an exceptions annex | 0 |
P1-8 | Monitor and continually improve the management system | 0 |
P1-9 | Transparency and accountability on information security | 0 |
P2-intro | How Part 2 works: government measures as the obligatory minimum for each control | 0 |