Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

BIO2 (2026)

BIO2 (Baseline Informatiebeveiliging Overheid 2) v1.3 management-system clauses, ISO 27002-aligned Part 2 controls, and Part 2 government measures. The body text in this catalog consists of plain-language summaries authored for ISMS, not the verbatim text of BIO2 or ISO/IEC 27001/27002. Customers needing the authoritative baseline should reference the official BIO2 page at https://www.bio-overheid.nl/bio2/bio-producten/baseline-informatiebeveiliging-overheid-2-bio2/.

Requirement bodies below are plain-language summaries authored by Compliance. For the verbatim text of the standard, reference the publication from your national standards body (NEN, BSI, ANSI, ...).

Management system (30)

MS-4.1 Understanding the organisation and its context

Identify the internal and external issues that affect the organisation's ability to achieve the intended outcomes of its information security management system, and keep that understanding current.

MS-4.2 Understanding the needs and expectations of interested parties

Determine which parties are relevant to the ISMS, what their information security requirements are, and which of those requirements will be addressed through the management system.

MS-4.3 Determining the scope of the information security management system

Define and document the boundaries and applicability of the ISMS, taking account of the context, interested parties, interfaces, and dependencies with other organisations.

MS-4.4 Information security management system

Establish, implement, maintain, and continually improve the ISMS, including the processes needed and their interactions, in line with this standard.

MS-5.1 Leadership and commitment

Top management must demonstrate active leadership for the ISMS: setting direction, ensuring resources, integrating security into business processes, and holding people accountable for results.

MS-5.2 Policy

Top management must establish an information security policy that fits the organisation's purpose, sets objectives or a framework for them, commits to meeting requirements and to continual improvement, and is communicated and available.

MS-5.3 Organisational roles, responsibilities and authorities

Assign and communicate responsibility and authority for the ISMS, including who ensures it conforms to the standard and who reports on its performance to top management.

MS-6.1.1 Actions to address risks and opportunities - general

When planning the ISMS, consider the context and interested-party requirements to determine the risks and opportunities that must be addressed to assure intended outcomes, prevent undesired effects, and drive improvement.

MS-6.1.2 Information security risk assessment

Define and apply a repeatable risk assessment process with clear criteria, that identifies information security risks, their owners, and analyses and evaluates them to produce consistent, comparable results.

MS-6.1.3 Information security risk treatment

Define a risk treatment process that selects appropriate options and controls, compares them against Annex A, produces a Statement of Applicability, formulates a treatment plan, and obtains risk owner approval and acceptance of residual risk.

MS-6.2 Information security objectives and planning to achieve them

Set measurable information security objectives consistent with the policy, plan how to achieve them (what, resources, responsibility, timing, evaluation), and keep documented information about them.

MS-6.3 Planning of changes

When the organisation determines a need to change the ISMS, carry out those changes in a planned manner rather than ad hoc.

MS-7.1 Resources

Determine and provide the resources needed to establish, implement, maintain, and continually improve the ISMS.

MS-7.2 Competence

Determine the competence needed for people whose work affects information security performance, ensure they are competent through education, training, or experience, and retain evidence of it.

MS-7.3 Awareness

Ensure people doing work under the organisation's control are aware of the security policy, their contribution to the ISMS, and the implications of not conforming.

MS-7.4 Communication

Determine the internal and external communications relevant to the ISMS: what to communicate, when, with whom, and how.

MS-7.5.1 Documented information - general

The ISMS must include the documented information required by the standard plus whatever the organisation deems necessary for its effectiveness.

MS-7.5.2 Creating and updating documented information

When creating or updating documented information, ensure appropriate identification, format, and review and approval for suitability and adequacy.

MS-7.5.3 Control of documented information

Control documented information so it is available and suitable where needed and adequately protected, covering distribution, access, storage, version control, retention, and disposal, including documents of external origin.

MS-8.1 Operational planning and control

Plan, implement, and control the processes needed to meet requirements and treat risks, keep documented information to give confidence processes ran as planned, and control planned and unintended changes.

MS-8.2 Information security risk assessment (operational)

Perform information security risk assessments at planned intervals and when significant changes occur, using the defined criteria, and retain the results as documented information.

MS-8.3 Information security risk treatment (operational)

Implement the risk treatment plan and retain documented information on the results of the treatment.

MS-9.1 Monitoring, measurement, analysis and evaluation

Determine what needs monitoring and measuring, by which methods, and when, so the ISMS's security performance and effectiveness can be evaluated, and retain the evidence.

MS-9.2.1 Internal audit - general

Conduct internal audits at planned intervals to confirm the ISMS conforms to the organisation's own requirements and the standard, and that it is effectively implemented and maintained.

MS-9.2.2 Internal audit programme

Plan, establish, and maintain an audit programme, defining criteria and scope, selecting objective auditors, and reporting results to relevant management, with documented evidence retained.

MS-9.3.1 Management review - general

Top management must review the ISMS at planned intervals to ensure it remains suitable, adequate, and effective.

MS-9.3.2 Management review inputs

The management review must consider inputs such as prior action status, changes in context, interested-party needs, performance and audit results, feedback, risk assessment outcomes, and improvement opportunities.

MS-9.3.3 Management review results

The results of the management review must include decisions on continual improvement and any changes needed to the ISMS, and be retained as documented information.

MS-10.1 Continual improvement

Continually improve the suitability, adequacy, and effectiveness of the ISMS.

MS-10.2 Nonconformity and corrective action

React to nonconformities, correct them, evaluate whether corrective action is needed to prevent recurrence, implement and review that action, and retain evidence of the nonconformity and the response.

Organizational (91)

5.1 Policies for information security

Establish and maintain a documented information security policy, supported by topic-specific policies, that defines management direction and the organisation's approach to information security. Review periodically and after significant changes.

5.01.01 Adopted information security policy

The organisation maintains an information security policy adopted by its administration. The policy covers strategic principles and preconditions (including alignment with overall security and information-management policy), how the information security function is organised, how line managers own chain, OT, privacy, and BCM responsibilities, the common reliability requirements that apply, how often the policy is reviewed, and how awareness is promoted. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.01.02 Annual policy review

Review the information security policy at least annually, aligned with governance and planning-and-control cycles and with external developments, and update it when needed. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.2 Information security roles and responsibilities

Clearly define and assign who is responsible for which aspects of information security. Everyone with a stake should know what is expected of them and who to escalate to.

5.02.01 Board-defined security roles

The board defines information security, privacy, OT, and BCM roles and responsibilities, including how those areas relate, with explicit attention to incident handling. Line managers and process owners who own assets also own the risks on those assets. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.02.02 Independent CISO

Appoint a CISO who may give independent advice and report on information security to the board and/or supervisory authority. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.3 Segregation of duties

Split conflicting tasks across different people so no single person can both perform and conceal a fraud, error, or unauthorised action. Where organisation size makes this impractical, compensate with monitoring or review.

5.4 Management responsibilities

Management must actively require personnel and contractors to apply information security in line with policies and procedures, and must visibly support the security program.

5.04.01 Board and staff cyber training

Board members and employees regularly train to recognise and prevent cybersecurity risks and to respond to information security incidents. Board members also show they can judge how information security risks affect the organisation's services or products. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.5 Contact with authorities

Maintain documented contacts with relevant authorities (law enforcement, regulators, national CERTs) so the organisation can engage them quickly when an incident or legal matter requires it.

5.05.01 Named external security contacts

Record which officials hold formal contacts with which agencies and regulators on information security, and refresh that overview at least annually. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.6 Contact with special interest groups

Maintain contact with security communities, industry groups, and professional bodies to stay current on threats, defences, and best practices.

5.7 Threat intelligence

Collect and analyse information about current and emerging information security threats relevant to the organisation, and use what you learn to inform defences.

5.8 Information security in project management

Build information security considerations into how projects are planned and run, so security requirements are addressed before delivery rather than retrofitted after.

5.08.01 Risk assessment for new or changed systems

For new information systems and for significant changes to existing ones, perform an explicit risk assessment using the organisation's established risk-management method so risks are identified and controlled and security requirements are set. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.9 Inventory of information and other associated assets

Maintain an inventory of information and information-processing assets, with each item having an identified owner accountable for it.

5.09.01 Asset inventory including OT and remote assets

Keep an inventory of assets relevant to information processing, including OT, with the attributes needed for management and maintenance. Cover remote assets, cloud environments, and assets that regularly connect to the network but are not under the organisation's control. Verify completeness and accuracy on a cadence that matches how often things change. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.10 Acceptable use of information and other associated assets

Document and communicate rules for the acceptable use and handling of information and assets so users know what is and is not allowed.

5.10.02 Asset-use rules in external contracts

Put the rules of conduct for using assets into contracts for external staff and volunteers, consistent with house rules or the internal code of conduct. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.10.03 Staff aware of asset-use code

Ensure all employees have been formally made aware of the code of conduct for using assets. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.11 Return of assets

Ensure personnel and external party users return all organisational assets in their possession on termination of employment, contract, or agreement.

5.12 Classification of information

Classify information by sensitivity and criticality so handling rules can apply consistently. The classification scheme should reflect legal, regulatory, and business needs.

5.12.01 Classification via impact methodology

Classify information in all information systems using an explicit risk assessment and a defined impact-classification method that is part of the established risk-management methodology. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.13 Labelling of information

Apply labels to information (digital or physical) so its classification is visible and the right handling rules are applied automatically.

5.14 Information transfer

Establish rules and controls for transferring information inside the organisation and to external parties, covering electronic, physical, and verbal transfer.

5.14.01 Internet.nl and Forum standards for public systems

Keep internet-facing information systems and email communications compliant with the mandatory standards published by the Netherlands Standardisation Forum and under the Cybersecurity Act (Cbw). Monitor compliance with internet.nl measurements and configure components for strong security without breaking the service. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.14.02 OV or government PKI certificates

Use at least publicly trusted Organisation Validated (OV) certificates for public web traffic that carries sensitive data. For sensitive data in internal web traffic, use at least public OV certificates or private PKIoverheid certificates. A risk assessment, connection conditions, or law may require stronger certificates. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.14.03 AdES baseline electronic signatures

Advanced and/or qualified electronic signatures comply with the AdES Baseline Profiles on the Netherlands Standardisation Forum open-standards list. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.14.04 Register of internet-facing systems

Keep up-to-date records of all internet-facing information systems, web applications, IP addresses, and APIs. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.14.05 Government Register of Internet Domains

Publish publicly accessible websites via the Government Register of Internet Domains and refresh that information at least every six months. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.15 Access control

Define and enforce rules that govern who gets access to which information and other assets, based on business and security requirements.

5.15.01 Trusted-zone access from authenticated devices or enclaves

Allow access to a trusted zone only from authenticated devices or from software running in a secure enclave. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.16 Identity management

Manage the full lifecycle of identities used by people and systems — creation, modification, removal — so each identity is tied to a real, accountable owner.

5.16.01 Formal identity registration and de-registration

Operate a comprehensive formal registration and de-registration procedure for managing user identities. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.16.02 Group accounts only with CISO coordination

Do not use group accounts unless the process owner motivates and records the exception and coordinates it with the CISO. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.17 Authentication information

Manage authentication information (passwords, keys, tokens) securely throughout its lifecycle: allocation, storage, distribution, rotation, and revocation.

5.17.01 Multi-factor authentication for high-risk access

Apply MFA at least for primary logins to the digital workplace, accounts for internet-facing services, administrative accounts, and other cases where risk analysis calls for it. Use passwordless access (for example PIN plus hardware token or passkey) or password plus a second factor. Where MFA is impossible, take other mitigating measures with CISO involvement and process-owner approval. Prefer combining MFA with federation such as single sign-on and a stepping-stone where safe. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.17.02 Password manager for employees

Provide all employees with a password manager or an equivalent solution. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.17.03 Automated password requirement enforcement

Enforce password requirements automatically. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.18 Access rights

Provision, review, modify, and revoke access rights in line with the organisation's access control policy. Reviews should happen periodically and on role change.

5.18.01 Monitor privileged account changes

Monitor creation of and changes to accounts with special privileges and respond when such an event is unexpected or unauthorised. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.18.02 Annual access-rights review

Review all issued access rights at least once a year. Use a risk assessment to decide whether a higher review frequency is needed for particular rights or environments. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.19 Information security in supplier relationships

Identify and document the information security risks associated with supplier relationships, and put processes in place to manage them.

5.19.01 Security requirements in proposals

When a request for proposal involves information or information systems, include information security requirements from the outset. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20 Addressing information security within supplier agreements

Capture the organisation's information security expectations in contracts with suppliers, scaled to the type of access and relationship involved.

5.20.01 Security requirements in supplier contracts

Carry the security requirements from the request for proposal explicitly into (procurement) contracts with suppliers. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20.02 Exclude supplier general terms on security

Explicitly exclude suppliers' general terms and conditions where they conflict, and record any additional terms that apply. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20.03 Independent evidence of supplier control operation

Require in the procurement contract that the supplier demonstrates design, existence, and operation of the required controls through assessments by independent third parties. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20.04 Independent validation of supplier reports

Independently investigate and validate reports the supplier provides about its security posture. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20.05 Supplier transparency on vulnerabilities and incidents

Agree that the supplier is transparent about vulnerabilities and information security incidents that affect the contracted services. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.20.06 Supplier dependency risk before contract

Before concluding a contract, assess whether dependency on a particular supplier creates unacceptable risk and address that risk. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.21 Managing information security in the ICT supply chain

Define and manage information security requirements specifically for the ICT supply chain (hardware, software, services) to address risks like tampered components and compromised vendors.

5.21.02 Visibility of subcontractor chain before contract

Before the contract is concluded, require the supplier to show the chain of subcontractors relevant to the service. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.21.03 Flow-down of security requirements in the chain

Ensure security requirements imposed on the supplier apply equally and fully down the subcontractor chain. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.21.04 Ongoing notice of chain changes

During the contract, require the supplier to communicate changes in the subcontractor chain that affect security. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.21.05 Supply-chain security in entity risk analysis

Include supply-chain security in the organisation's risk analysis and keep that analysis current for the contracted services. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.22 Monitoring, review and change management of supplier services

Regularly monitor, review, and audit supplier security practices and service delivery; manage changes to supplier services so security posture is not degraded over time.

5.22.01 Process owner review of supplier evidence

Using evidence from the supplier (see 5.20.03), the process owner annually reviews supplier compliance with information security requirements, follows up on deviations, and records the outcome. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.22.02 Register of suppliers and contracts

Keep an up-to-date registration of suppliers and concluded contracts. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.23 Information security for use of cloud services

Establish processes for acquiring, using, managing, and exiting cloud services in line with the organisation's information security requirements.

5.23.01 Cloud and service selection oversight policy

Establish and apply a policy for inventorying, classifying, selecting, assuring, and overseeing use of cloud and similar external information services. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24 Information security incident management planning and preparation

Plan and prepare for managing information security incidents — define roles, processes, communication paths, and decision-making authority before an incident occurs.

5.24.01 Low-threshold incident notification desk

Give all internal and external employees access to a low-threshold desk where they can report (suspected) information security incidents. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.02 Documented incident notification desk duties

Document the notification desk's tasks and responsibilities in an incident reporting procedure. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.03 Process owner owns incident resolution

The process owner is responsible for resolving information security incidents. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.04 Monthly incident follow-up reporting

Each month the process owner reports on follow-up of information security incidents to the agreed governance forum. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.05 Incident procedure links to crisis management

The information security incident procedure references the crisis-management procedure where escalation may be needed. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.07 Minimum content of the incident procedure

The incident procedure states at least that information security incidents are reported to the CSIRT within the statutory time, that CSIRT notifications are received, assessed, and fed into risk treatment, and that PII principals are notified within the statutory time. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.24.08 Published coordinated vulnerability disclosure

Design and publish a Coordinated Vulnerability Disclosure (CVD) procedure consistent with applicable Dutch government CVD guidance. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.25 Assessment and decision on information security events

Assess reported information security events and decide whether each one should be classified as an incident, with documented criteria for that decision.

5.26 Response to information security incidents

Respond to information security incidents according to documented procedures, with appropriate escalation, containment, communication, and recovery steps.

5.26.02 Incident management including regulatory notification

Handle information security incidents through the incident-management process, including when relevant incidents must be reported to the regulatory authorities named in law and regulations. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.27 Learning from information security incidents

After incidents, capture lessons learned and feed them back into policies, procedures, and controls to reduce the likelihood and impact of recurrence.

5.27.01 Root-cause analysis and improvements after incidents

Assess information security incidents to find root causes and implement improvements that reduce recurrence. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.27.02 Share incident analysis lessons

Share incident analysis reports, including root causes and improvements, with parties that need them for learning and oversight. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.28 Collection of evidence

Establish procedures for identifying, collecting, acquiring, and preserving evidence related to information security events in a way that is defensible in disciplinary or legal proceedings.

5.28.01 Retention of incident investigation material

Define and apply a retention period for (suspected) information security incidents and for the information needed to investigate them, consistent with legal and business needs. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.29 Information security during disruption

Plan how information security is maintained during disruption (outages, crises, recovery) so security does not lapse when the organisation is under stress.

5.30 ICT readiness for business continuity

Plan, implement, maintain, and test the ICT readiness needed to meet business continuity objectives and recovery time/point requirements.

5.30.01 Annual continuity plan testing

Every year the process owner tests continuity plans for effectiveness, completeness, and currency. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.30.02 Critical systems inventory refreshed every three years

In the inventory for control 5.12, the process owner identifies critical systems using the established risk-management methodology and an explicit risk assessment, and updates that overview at least every three years. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.31 Legal, statutory, regulatory and contractual requirements

Identify, document, and keep up to date the legal, statutory, regulatory, and contractual requirements relevant to information security, along with the organisation's approach to meeting them.

5.32 Intellectual property rights

Implement procedures to ensure compliance with intellectual property rights — licensing, attribution, restrictions on use — for software and other protected material. Per the BIO2 FAQ, this control is excepted from Cyberbeveiligingswet (Cbw) legal duty and remains obligatory BIO self-regulation.

5.33 Protection of records

Protect records from loss, destruction, falsification, unauthorised access, and unauthorised release, in line with legal, regulatory, contractual, and business requirements. Per the BIO2 FAQ (which prevails over the v1.3 PDF marking), this control stays in Cyberbeveiligingswet (Cbw) scope and remains a legal duty under the Cyberbeveiligingsregeling sector Overheid.

5.33.01 Retention periods in selection lists

The process owner records retention periods for all information and information systems in applicable selection lists (including under the Archiefwet). Per the BIO2 FAQ, this government measure is excepted from Cyberbeveiligingswet (Cbw) legal duty and remains obligatory BIO self-regulation. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.34 Privacy and protection of PII

Identify and meet privacy and personally identifiable information (PII) protection requirements applicable to the organisation, including those imposed by law and regulation. Per the BIO2 FAQ, this control is excepted from Cyberbeveiligingswet (Cbw) legal duty and remains obligatory BIO self-regulation.

5.35 Independent review of information security

Independently review the organisation's approach to managing information security and its implementation at planned intervals or after significant changes.

5.35.02 Annual audit plan for systems and processes

Maintain an established audit plan that decides each year which systems and processes are audited for information security. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.36 Compliance with policies, rules and standards for information security

Verify that information security is being implemented and operated in accordance with the organisation's policies, rules, and applicable standards.

5.36.01 Security reporting in the P&C and PDCA cycles

Within the planning-and-control cycle and as part of PDCA, report on information security performance and on conformity with policy and with BIO2 measures. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

5.37 Documented operating procedures

Document operating procedures for information processing activities and make them available to those who need them, so consistent execution is possible across the team.

People (15)

6.1 Screening

Perform background verification checks on candidates for employment proportional to the role's access to information and risk, in line with applicable law.

6.01.01 Screening policy and risk-based VOG

Maintain an established screening policy. On hire and on job change, a Certificate of Conduct (VOG) may be requested based on a risk assessment. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.2 Terms and conditions of employment

Employment contracts should state the employee's and the organisation's responsibilities for information security, so expectations are unambiguous from day one.

6.02.01 Terms and conditions of employment on security

On hire or job change, ensure internal and external employees accept terms that cover information security responsibilities and sanctions. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.3 Information security awareness, education and training

Provide ongoing awareness, education, and training for all personnel (and relevant external parties) on the organisation's information security policies and their role in upholding them.

6.03.01 Shared responsibility to protect information

Make clear that employees, line managers, and board members share responsibility for protecting business information and information systems. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.03.02 Completed awareness before system use

Ensure employees and contractors who use information systems and services have successfully completed the required awareness activities before or as they gain access. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.03.03 Ongoing awareness at transfer and reviews

Reinforce information security expectations on appointment, internal transfer, and in team meetings or performance reviews. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.03.04 Secure mobile working in awareness programmes

Cover behavioural aspects of secure mobile working in awareness programmes. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

6.4 Disciplinary process

Establish a formal disciplinary process for personnel who have committed an information security breach, and communicate it so it acts as a deterrent.

6.5 Responsibilities after termination or change of employment

Define and enforce information security responsibilities that remain in effect after termination or change of role, and make sure they are communicated at the relevant moments.

6.6 Confidentiality or non-disclosure agreements

Use confidentiality or non-disclosure agreements that reflect the organisation's information protection needs, with personnel and relevant external parties, and review them periodically.

6.7 Remote working

Implement security measures specific to remote working to protect information accessed, processed, or stored outside the organisation's premises.

6.8 Information security event reporting

Provide a clear mechanism for personnel to report observed or suspected information security events promptly, without friction or fear of blame.

6.08.01 Demonstrable knowledge of reporting procedure

Ensure all internal and external employees can show they have taken note of the procedure for reporting information security events and weaknesses. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

Physical (20)

7.1 Physical security perimeters

Define and use physical security perimeters to protect areas containing information and information processing facilities.

7.01.02 No single-zone access to critical systems

Do not make critical information or information systems reachable through only one secure zone; use layered zoning. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.2 Physical entry

Protect secure areas with appropriate entry controls so only authorised people can enter, with records of who went where and when.

7.02.01 Physical security warnings on agreed triggers

When specific physical security risks arise, send warnings according to mutual agreements with the parties that need to act. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.3 Securing offices, rooms and facilities

Design and apply physical security measures to offices, rooms, and facilities containing information and information processing assets.

7.4 Physical security monitoring

Continuously monitor physical premises for unauthorised access using appropriate detection mechanisms — alarms, surveillance, intrusion detection.

7.5 Protecting against physical and environmental threats

Design and implement protection against physical and environmental threats — fire, flood, earthquake, civil unrest — proportional to the risk and the value of the assets at stake.

7.6 Working in secure areas

Define and apply security measures for working in secure areas, including supervision of personnel and control of equipment brought in or taken out.

7.7 Clear desk and clear screen

Apply clear-desk and clear-screen rules to reduce the risk of unauthorised access to information left visible on desks or on unattended screens.

7.07.01 Clear-desk lock when chip-card token removed

Where a chip-card token controls system access, the access lock engages automatically when the token is removed. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.8 Equipment siting and protection

Site equipment so it is protected from environmental threats, opportunities for unauthorised observation, and physical interference.

7.9 Security of assets off-premises

Protect assets that are taken off-premises (laptops, devices, documents) with measures appropriate to the risks they face outside the secure perimeter.

7.10 Storage media

Manage storage media (USB drives, tapes, disks, removable media) throughout their lifecycle — acquisition, use, transport, disposal — with classification-appropriate protection.

7.10.01 Irreversible wipe of reusable media leaving the entity

Removal instructions require that business-sensitive content has been irretrievably removed from reusable removable media that leave the organisation. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.10.02 Verified irreversible media sanitisation

Check that all data on the medium were removed irretrievably and record that check. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.10.03 Courier rules for classified media transport

Using couriers or forwarders to transport classified information meets predefined security requirements. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

7.11 Supporting utilities

Protect information processing facilities from disruption caused by failures in supporting utilities — power, cooling, water, telecommunications.

7.12 Cabling security

Protect power, data, and telecommunications cabling against interception, interference, or physical damage.

7.13 Equipment maintenance

Maintain equipment correctly to ensure continued availability and integrity of information, and protect information when equipment is being serviced (especially by external technicians).

7.14 Secure disposal or re-use of equipment

Verify that sensitive data and licensed software has been removed or securely overwritten before equipment is disposed of, sold, or re-used.

Technological (84)

8.1 User end point devices

Protect information stored on, processed by, or accessible from user endpoint devices (laptops, mobile devices, workstations) through configuration, policy, and centralised management.

8.01.01 No business data stored on user mobile devices

Configure mobile equipment so business information is not stored on user devices unless an approved exception applies. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.01.02 Minimum mobile working controls

When mobile equipment is used, at least: keep the device under patch management and hardening; use MDM or MAM; and have users sign a mobile-working agreement acknowledging mobile risks for every business-used mobile device. Check these three points periodically. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.2 Privileged access rights

Restrict, review, and monitor the allocation and use of privileged access rights — those that grant broader permissions than ordinary users — so they are used only when necessary.

8.02.01 Quarterly review of special privileges

At least quarterly, assess assigned or exercised special privileges for necessity and correct use. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.3 Information access restriction

Restrict access to information and other assets in line with the access control policy, so people can only reach what they need for their role.

8.03.01 Isolation of information of specific importance

Safeguard physical and/or logical isolation of information of specific importance from other information. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.03.02 Need-to-know for information of specific importance

Users may view and process information of specific importance only as needed for their tasks. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.4 Access to source code

Restrict access to program source code, software libraries, and related artefacts to authorised personnel, and manage changes through documented processes.

8.5 Secure authentication

Implement secure authentication technologies and procedures appropriate to the sensitivity of what is being protected, including multi-factor authentication where warranted.

8.05.01 Risk assessment before supplier network access

Before granting network access to external suppliers, perform a risk assessment to set the conditions of that access. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.6 Capacity management

Monitor and adjust resource usage so the required system performance, capacity, and availability are sustained as demand evolves.

8.7 Protection against malware

Implement layered protection against malware — detection, prevention, recovery, and user awareness — to keep systems and information safe from malicious code.

8.07.01 Risk-based download control and antimalware

Control and restrict downloads based on risk and need-to-use, supported by antimalware appropriate to the environment. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.07.02 Awareness of unsafe browsing and links

Inform users about risks of browsing behaviour and of clicking unknown links. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.07.03 Current antimalware and recovery tooling

Keep antimalware and related recovery software up to date and backed by periodic updates from the vendor. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.07.04 Malware scanning across environments and gateways

Run malware scans on servers, desktops, and gateways (including mail) and on other environments where risk requires it. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.8 Management of technical vulnerabilities

Identify, assess, and remediate technical vulnerabilities in systems and software in a timely way, with priority based on risk.

8.08.01 Urgent response to high-likelihood high-impact vulnerabilities

When both likelihood of abuse and expected damage of a vulnerability warning are high, treat remediation as urgent. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.08.02 Risk-based choice of mitigating measures

Base how mitigating measures are implemented on an explicit risk assessment. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.08.03 Interim mitigation when patching is delayed

Meanwhile, or if installation cannot be finished within a week, apply mitigating measures that reduce exposure. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.08.04 Technical compliance and security configuration checks

Check information systems for technical compliance with security standards and for actual security configuration. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.08.05 Penetration tests before release and annually

Where possible, run an obligatory automated penetration test on internet-facing information systems at every new release or major update. If high-risk findings cannot be mitigated otherwise, do not take the system into operation. Test all internet-facing systems for weaknesses at least annually. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.9 Configuration management

Establish and maintain secure configurations for hardware, software, services, and networks, and manage changes to those configurations under formal control.

8.10 Information deletion

Delete information stored in systems, devices, and other media when it is no longer required, using methods appropriate to its classification.

8.11 Data masking

Where appropriate, apply data masking techniques (anonymisation, pseudonymisation, tokenisation) to limit exposure of sensitive data — especially in non-production environments.

8.12 Data leakage prevention

Apply measures to detect and prevent the unauthorised disclosure or exfiltration of sensitive information from systems, networks, and endpoints.

8.13 Information backup

Maintain backups of information, software, and system images, and test restoration regularly to ensure recoverability after loss or corruption.

8.13.01 Backup policy including ransomware protection

Maintain a backup policy that defines storage and protection requirements, with particular attention to protecting backups against ransomware and preserving backup integrity. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.13.02 RPO and RTO from explicit risk assessment

Determine maximum permissible data loss and maximum recovery time after an incident based on an explicit risk assessment. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.13.03 Offsite backups surviving site loss

Store backups so that a site-level incident does not also destroy the recoverable copies. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.13.04 Annual or post-change recovery tests

Test the recovery procedure at least annually and after major changes so it works under emergency conditions. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.14 Redundancy of information processing facilities

Implement redundancy in information processing facilities sufficient to meet availability requirements set by the business.

8.15 Logging

Produce, store, and protect logs of events, exceptions, faults, and security-relevant activity, and make sure they are useful for investigation later.

8.15.01 Minimum fields in each log entry

Each log entry records at least the action, the object affected, the result, the origin (device or network location), the actor (person or process), and a timestamp. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.15.02 No security-breaching data in logs

Log entries must not contain data that could themselves lead to a security breach. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.15.03 Inventory of generated log files

Maintain a list of the log files that are generated. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.15.04 Risk-based SIEM and log retention

Set retention for log files and SIEM data on the basis of risk, including scenarios where attackers stay undetected for a long time. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.15.05 Report log tampering as an incident

Treat improper modification or deletion of log data (or attempts) as an information security incident and report it quickly under the incident procedure tied to control 5.24. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.15.06 Independent check that logs still exist

Based on an explicit risk assessment, regularly verify that log files still exist unchanged during their retention period. An independent official, separate from operations, performs that verification. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.16 Monitoring activities

Continuously monitor networks, systems, and applications for anomalous behaviour and potential security events, and act on what is detected.

8.16.01 Share detected attacks with the designated CERT

Share new threats or attacks discovered under government measure 8.16.03 with the designated CERT within the applicable legal framework. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.16.02 SIEM or SOC rules for escalating to managers

SIEM and/or SOC monitoring processes include clear rules for when an incident is reported to the responsible managers. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.16.03 Detection and response monitoring of the environment

Monitor the information-processing environment with a detection-and-response solution that can detect attacks and treat nonconformities adequately and in time. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.16.04 Logging on active network components

Active network components include logging and log-monitoring functions so anomalous events can be detected and handled. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.17 Clock synchronization

Synchronise the clocks of all information processing systems to a reliable time source so logs and events can be correlated accurately across systems.

8.18 Use of privileged utility programs

Restrict and tightly control the use of utility programs that could override system or application controls, since they are a frequent vector for abuse.

8.18.01 Restricted access to system utilities

Restrict system utilities to authorised staff and only for the tasks that require them. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.18.02 Logging of system utility use

Log use of system utilities and keep those logs available for investigation. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.19 Installation of software on operational systems

Implement procedures to control the installation of software on operational systems, including approval workflows and limits on who can install what.

8.19.01 Control installation of unauthorised software

Control the risk that users install software that has not been authorised. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.20 Networks security

Manage and control networks to protect the information in systems and applications connected to them.

8.20.01 Network components match network confidentiality

Network components meet at least the confidentiality level of the network they belong to. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.20.02 Management interfaces separated from user networks

Separate access to network-component management interfaces from the user network as far as practicable. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.21 Security of network services

Define and document the security mechanisms, service levels, and management requirements of all network services, whether provided internally or externally.

8.21.01 Flag and mitigate availability attacks at trust boundaries

At connection points with external or untrusted zones, and because of network segmentation, take measures that flag and mitigate potential attacks that would harm availability of information provision. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.21.02 Detection tools on traffic to and from trusted environments

Deploy detection tools that monitor and analyse data traffic to and from the trusted environment. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.21.03 Share newly detected threats within government

Pass on and share within government any new threats identified under 8.21.02, respecting applicable legal frameworks. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.21.04 Encrypt data on wireless and uncontrolled wired links

Encrypt data sent over wireless links such as Wi-Fi and over wired links outside the controlled area, except metadata needed to establish the transmission. Base encryption configuration on risk, required duration, and protection level. Prefer tools with a positive NBV/AIVD Resilience Unit deployment advice when available; otherwise select and configure another suitable method. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.22 Segregation of networks

Segregate networks into separate groups (by service, user community, sensitivity) and control traffic between them with rules appropriate to each segment.

8.22.01 Own security level per segregated group

Give each segregated group its own security level matched to its trust requirements. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.23 Web filtering

Manage access to external websites to reduce exposure to malicious content and unwanted services.

8.24 Use of cryptography

Define and implement rules for the effective use of cryptography, including cryptographic key management, for protecting information confidentiality, integrity, and authenticity.

8.24.01 Cryptography policy required topics

The cryptography policy covers at least when cryptography is used, who implements it, who manages keys, how applied cryptography is recorded and where, which standards underpin cryptography and how they stay current, and how compliance is checked. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.24.02 Cryptographic controls in the asset inventory

Include cryptographic controls in the business-asset inventory and record the information each control protects. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.24.04 Cryptographic strength per NCSC and AIVD guidance

Base cryptographic strength on current NCSC and AIVD recommendations. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.24.05 Backup certificates from an alternative supplier

Agree backup certificates from an alternative supplier when the risk assessment shows dependence on a single certificate supplier is unacceptable. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.25 Secure development life cycle

Establish and apply rules for secure software and systems development across the entire development lifecycle, not just at security review gates.

8.26 Application security requirements

Identify, specify, and approve information security requirements for new or modified applications before development or acquisition begins.

8.27 Secure system architecture and engineering principles

Establish, document, and apply secure architecture and engineering principles to the design and implementation of information systems.

8.27.01 Adopt and apply security-by-design principles

Adopt, document, maintain, and apply architectural principles such as security by design and security by default for all activities in developing information systems. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.28 Secure coding

Apply secure coding principles and standards during software development to reduce the introduction of vulnerabilities.

8.29 Security testing in development and acceptance

Include security testing in development and acceptance processes so vulnerabilities are caught before software reaches production.

8.29.01 Structured acceptance tests with reported results

Use structured methodologies for system acceptance testing, automate the tests where possible, and record the results in a report. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.30 Outsourced development

When outsourcing software development, define and enforce the security requirements that apply to the development activity and its outputs, and verify they are met.

8.30.01 Same development controls when work is outsourced

Apply internal system-development measures in full to outsourced development, with any extra controls the outsourcing arrangement requires. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.31 Separation of development, test and production environments

Keep development, test, and production environments separated to reduce the risk of unauthorised access or unintended changes affecting production.

8.31.01 No production testing without approved exception

Do not test in production. Allow departures only with an approved exception that states compensating controls. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.31.02 Test significant production changes before go-live

Always test significant changes to the production environment before they go live. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.32 Change management

Subject changes to information processing facilities and systems to formal change management processes that control the risk of unintended consequences.

8.32.01 Change management with risk, rollback, and approval

Change management at least administers changes including test-plan results, assesses potential consequences with a written rollback plan, and follows an approval procedure for changes. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.32.02 Change management on an accepted framework

Conduct change management using a generally accepted management framework suited to the organisation. This government measure is BIO2 Basishygiëne and is a Cyberbeveiligingswet (Cbw) legal duty for network and information systems. Exclude this government measure only when it does not apply to the organisation; do not exclude it merely because residual risk looks acceptable.

8.33 Test information

Select and protect test data carefully; avoid using real personal data in non-production environments unless adequately masked or otherwise protected.

8.34 Protection of information systems during audit testing

Plan and agree audit tests of operational systems with management to minimise disruption to business processes during the test.

Are you sure?

This action cannot be reverted.

Leave this page?

Your changes on this form are not saved. If you leave, they are lost.