← Frameworks / Government Baseline

Baseline Informatiebeveiliging Overheid 2 (Dutch Government Information Security Baseline)

Mandatory information security baseline for all Dutch government organisations at all levels: central government, provinces, municipalities, and water authorities. Aligned with ISO/IEC 27002:2022 with 93 controls plus government-specific measures (overheidsmaatregelen). Integrates NIS2 Article 21 requirements and supports ENSIA audit compliance. Replaces BIO 1.04 with a risk-based approach.

Clause Title SP 800-53 Controls
5.1 Setting information security policies, including topic-specific ones (BIO2)
5.2 Defining and assigning information security roles (BIO2)
5.3 Segregation of duties between conflicting roles (BIO2)
5.4 Management responsibilities: requiring staff to follow security policies (BIO2)
5.5 Staying in contact with authorities such as regulators (BIO2)
5.6 Joining special interest groups and security forums (BIO2)
5.7 Gathering and analysing threat intelligence (BIO2)
5.8 Building security into project management (BIO2)
5.9 Inventory and ownership of information and related assets (BIO2)
5.10 Acceptable use rules for information and related assets (BIO2)
5.11 Return of assets when people leave or change roles (BIO2)
5.12 Classification of information by security needs (BIO2)
5.13 Labelling of information to show its classification (BIO2)
5.14 Rules and agreements for information transfer (BIO2)
5.15 Access control policy and rules (BIO2)
5.16 Identity management from creation to removal (BIO2)
5.17 Issuing and managing authentication information such as passwords (BIO2)
5.18 Managing access rights, including regular reviews (BIO2)
5.19 Managing security risks in supplier relationships (BIO2)
5.20 Security requirements in supplier agreements (BIO2)
5.21 Managing ICT supply chain security risks (BIO2)
5.22 Monitoring supplier services and managing their changes (BIO2)
5.23 Security of cloud services from adoption to exit (BIO2)
5.24 Setting up incident management plans and roles (BIO2)
5.25 Assessing whether security events are incidents (BIO2)
5.26 Incident response following documented procedures (BIO2)
5.27 Lessons learned from security incidents (BIO2)
5.28 Collecting and preserving evidence of security events (BIO2)
5.29 Keeping security in place during disruption (BIO2)
5.30 ICT readiness to support business continuity (BIO2)
5.31 Identifying legal and regulatory requirements, including contractual ones (BIO2)
5.32 Intellectual property rights and software licence compliance (BIO2)
5.33 Protection of records against loss and misuse (BIO2)
5.34 Protecting PII and meeting privacy requirements (BIO2)
5.35 Independent review of how security is managed (BIO2)
5.36 Regularly checking compliance with security policies and standards (BIO2)
5.37 Documented operating procedures for IT systems (BIO2)
6.1 Background screening before joining and during employment (BIO2)
6.2 Security responsibilities in employment contracts (BIO2)
6.3 Security awareness training and education for staff (BIO2)
6.4 Disciplinary process for security policy breaches (BIO2)
6.5 Security duties that continue after termination or role change (BIO2)
6.6 Non-disclosure agreements to protect confidential information (BIO2)
6.7 Protecting information during remote working (BIO2)
6.8 Security event reporting by staff through agreed channels (BIO2)
7.1 Physical security perimeters around sensitive areas (BIO2)
7.2 Controlling physical entry to secure areas (BIO2)
7.3 Physical security of offices and other facilities (BIO2)
7.4 Physical security monitoring of premises, such as CCTV (BIO2)
7.5 Protecting sites from physical and environmental hazards (BIO2)
7.6 Rules for work inside secure areas (BIO2)
7.7 Rules for a clear desk and a clear screen (BIO2)
7.8 Siting equipment securely and protecting it from hazards (BIO2)
7.9 Protecting assets used off-premises, such as laptops (BIO2)
7.10 Managing storage media from acquisition to disposal (BIO2)
7.11 Reliable supporting utilities, such as power and cooling (BIO2)
7.12 Security of power and data cabling (BIO2)
7.13 Secure and timely equipment maintenance (BIO2)
7.14 Removing data and software before equipment disposal or reuse (BIO2)
8.1 Protecting information on user endpoint devices (BIO2)
8.2 Limiting and controlling privileged access rights (BIO2)
8.3 Restricting access to information under access control rules (BIO2)
8.4 Controlling who can read and change source code (BIO2)
8.5 Secure authentication methods, such as multi-factor sign-in (BIO2)
8.6 Capacity management to meet current and future demand (BIO2)
8.7 Malware protection backed by user awareness (BIO2)
8.8 Technical vulnerability management, including patching (BIO2)
8.9 Secure configuration management for systems and networks (BIO2)
8.10 Deleting information once the need for it ends (BIO2)
8.11 Data masking, such as pseudonymisation and anonymisation (BIO2)
8.12 Data leakage prevention for sensitive information (BIO2)
8.13 Information backup with regular restore tests (BIO2)
8.14 Redundancy in IT systems to keep services available (BIO2)
8.15 Event logging, with logs kept safe and reviewed (BIO2)
8.16 Monitoring networks and systems for unusual behaviour (BIO2)
8.17 Clock synchronisation to a trusted time source (BIO2)
8.18 Restricting privileged utility programs able to bypass controls (BIO2)
8.19 Controlling what software is installed on operational systems (BIO2)
8.20 Network security and management of network devices (BIO2)
8.21 Security features and service levels for network services (BIO2)
8.22 Network segregation into separate security zones (BIO2)
8.23 Web filtering to block harmful websites (BIO2)
8.24 Using cryptography, including encryption and key management (BIO2)
8.25 Security built into the development life cycle (BIO2)
8.26 Application security requirements when building or buying software (BIO2)
8.27 Applying secure engineering principles to system architecture (BIO2)
8.28 Secure coding practices in software development (BIO2)
8.29 Security and acceptance testing of new or changed systems (BIO2)
8.30 Overseeing outsourced development from contract to acceptance (BIO2)
8.31 Separating development and test environments from production (BIO2)
8.32 Change management for IT systems and services (BIO2)
8.33 Choosing and protecting test data (BIO2)
8.34 Planning audit testing to protect live systems (BIO2)