Custom BIO-compliant software development
Appfront builds custom software for government organisations in line with the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline). Designed on a risk basis, with logging and monitoring, least-privilege access management, encryption and patchability — and with the technical substantiation your CISO, auditor and procurement team need. The BIO is a framework of standards, not a certificate; we make it demonstrable that the software fits within your information security framework, while your organisation remains ultimately responsible.
What is BIO-compliant software?
The Baseline Informatiebeveiliging Overheid (BIO) is the framework of standards for information security in the Dutch government, based on the international standards NEN-EN-ISO/IEC 27001 and 27002. The current version, BIO2, replaces the earlier division into baseline security levels (BBNs) with a more explicit risk-based approach. BIO-compliant software is custom software that supports the controls a government organisation needs to meet the BIO.
In practice, that means: a risk-based design, least-privilege access management, encryption of data in transit and at rest, extensive and searchable logging and monitoring, a working patch and vulnerability process and data minimisation. Just as important is what it is not: the BIO is not a certificate. There is no BIO quality mark that a supplier can obtain — we make our software demonstrably compliant with the BIO, with technical documentation and substantiation for each control.
For many government processes, custom software is a better fit than a standard package: you decide which data is processed, how authorisation is set up and how far logging goes, without being tied to a supplier's choices. Appfront builds on a risk basis, in line with the BIO, and provides the supporting documentation that fits your information security policy and your accountability. You can find the official explanation of the BIO at digitaleoverheid.nl.
Designed on a risk basis
The strength of the security measures follows from the sensitivity of the data and the risk profile of the application — not a fixed checklist, but measures that match your risk assessment under the BIO2.
Demonstrable and traceable
Extensive logging, clearly documented access models and substantiation for each control. Your CISO and auditor get the information needed for accountability — and you can back up RFI and tender questions with facts.
You remain ultimately responsible
The BIO leaves ultimate responsibility with your organisation. We fulfil the supplier role in the chain: we build in such a way that you can implement and demonstrate the controls, and we record the division of responsibilities honestly.
How Appfront builds BIO-compliant software
We work on a risk basis, with information security built in from the first step. From a risk assessment carried out with your information security officer through to go-live and ongoing management, every step produces supporting evidence that fits your accountability under the BIO. That keeps your team in control and the software demonstrably secure.
Together with your CISO or information security officer, we map out which data is processed, what the risk profile is and which BIO measures apply. This results in a clear scope and division of responsibilities.
We design the architecture with access management, encryption, logging and authorisation built in, not added as an afterthought. Choices are justified and documented for each relevant BIO measure.
Implementation using secure development practices, automated tests, structured logging and monitoring. You see working versions along the way, and pentests are part of delivery.
A controlled go-live, followed by ongoing management with a working patch and vulnerability process, monitoring and agreed incident response, so the software stays BIO-compliant.
Controls we build in as standard
Exactly which measures are needed follows from your risk assessment, as the BIO is risk-based. Below are the controls we build in most often for government software, each justified and documented so that they support your accountability.
Access management and least privilege
Role-based authorisation where every user and system only has access to what is strictly necessary. Strong authentication, segregated permissions and periodic access reviews keep misuse and errors limited and traceable.
Logging and monitoring
Extensive, searchable and exportable logging of who did what and when, with monitoring and alerting on anomalies. This is the basis for incident detection, forensic investigation and annual accountability, for example towards ENSIA for municipalities.
Data encryption
Encryption of data in transit (TLS) and at rest, with careful secrets management. Keys and certificates are managed securely and rotated, so sensitive government data stays protected even in the event of a data breach at infrastructure level.
Patchability and vulnerability management
Software that is maintainable and quick to patch, with a working process for following up vulnerabilities in dependencies. Updates can be rolled out safely and in a controlled way without jeopardising the operation of the process.
Data minimisation
We only process the personal data needed for the process and document the data flows for your processing register. This way the software supports both the relevant BIO measures and the GDPR, without duplicate effort.
Evidence for every measure
Technical documentation showing how each relevant BIO measure has been implemented, with pentest reports and a clear division of responsibilities. Exactly the evidence buyers ask you for in an RFI or tender.
Which government organisations it applies to
Building to BIO standards matters wherever government data is processed. The organisations below almost always ask for it in an RFI or tender, and for each of them we tailor the measures to the risk profile and the applicable chain frameworks.
Municipalities
Municipalities process a great deal of personal data and report annually via ENSIA on, among other things, the BIO. Our software contributes to this with full logging and clear access models. Also read about software for municipalities and AI for municipalities and government.
Provinces and water boards
For provinces and water authorities, BIO2 is mandatory self-regulation. Custom software often fits better here than an off-the-shelf package, because processes and risk profiles differ greatly. We build on a risk basis and provide evidence per measure for your information security officer.
Executive agencies and independent administrative bodies
Implementing bodies and independent administrative bodies that connect to chain systems, such as Suwinet with its own set of standards, need strict authorisation and logging. We build integrations that fit within your BIO approach; see our example of a Suwinet integration.
Processes involving sensitive data
Social services, enforcement, healthcare and security: processes where the impact of a data breach is high. Here the risk assessment carries great weight, and encryption, least privilege and demonstrable logging are crucial. We tailor the measures to the sensitivity of the data.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and government integrations
We build on a modern, maintainable web stack that can be patched quickly, a prerequisite for BIO compliance. Where the government process requires it, we integrate with national services. These integrations have their own connection requirements and frameworks that apply alongside the BIO; we build them with appropriate encryption, authorisation and logging. See, for example, our pages on DigiD integration, Digikoppeling, ZGW API integration and the Suwinet integration as an example of a dedicated framework.
If you want a valid security.txt file on all your public domains, with a reference to your CVD policy, take a look at our security.txt integration.
For integrations between systems that must comply with the BIO, there is our BIO-compliant integrations service.
Why Appfront for BIO-compliant software?
Appfront builds custom software for organisations in the Netherlands and always starts with a thorough analysis of process, data and risks. Information security is not an afterthought but a starting point: we design on a risk basis, in line with the BIO, and provide the supporting evidence for your accountability.
On every project we write clear documentation, so that your own team, or a future supplier, can understand, manage and patch the software. No black box, but transparent code and clear agreements on monitoring, alerting, patching and incident handling.
We are honest about the chain: your organisation remains ultimately responsible for complying with the BIO, and we state up front which responsibilities lie with you and which with us. No empty claims such as "BIO-certified", which does not exist, but demonstrable work that fits within your framework.
Also see our software for municipalities and AI for municipalities and government, or get in touch directly for an advisory conversation.
- Risk-based design in line with the BIO2 (ISO 27001/27002)
- Access management with least privilege and role-based authorisation
- Encryption in transit and at rest, with careful secrets management
- Comprehensive, exportable logging and monitoring from day one
- A working patch and vulnerability process; periodic pentests
- Supporting evidence per measure for your CISO, auditor and RFIs
- An honest division of responsibilities across the chain
- Experience with government integrations (DigiD, Digikoppeling, ZGW, Suwinet)
- Clear documentation that your team can read and maintain
- No false claims: the BIO is a set of standards, not a certificate
BIO, GDPR and your accountability
The Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline) focuses on information security; the GDPR on the protection of personal data. In government software, the two almost always go hand in hand. Appfront builds on a risk basis, in line with the BIO2, and follows secure development practices such as the OWASP ASVS: least-privilege access management, encryption, logging and monitoring, and a working patch process.
We work with data minimisation as a starting point and document the data flows, so that your record of processing activities is complete and you demonstrably comply with the GDPR. Important, and honest: your organisation remains ultimately responsible for complying with the BIO, which cannot be outsourced. We fulfil the supplier role in the chain and provide the supporting evidence per measure that backs up your accountability and, for municipalities, the annual ENSIA reporting.
More about our approach to security: information security policy and CVD policy (coordinated vulnerability disclosure). The official explanation of the BIO is available at digitaleoverheid.nl.
- Risk-based, in line with the BIO2 (ISO 27001/27002)
- GDPR-compliant data processing and data minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Comprehensive, exportable audit logging
- Monitoring and alerting on anomalies
- Patching and vulnerability management process; periodic pentests
- Evidence per control for the CISO, auditor and ENSIA
See also the other procurement anchors: digitally accessible software (WCAG), procuring custom software and Appfront as a software supplier for government.
Frequently asked questions about BIO-compliant software
Answers to the questions that procurement officers and information security officers ask us most often about building to BIO.
The Baseline Informatiebeveiliging Overheid (BIO) is the information security framework for the Dutch government. It is based on the international standards ISO/IEC 27001 and 27002. The current version is BIO2, which replaces the earlier classification into baseline security levels (BBNs) with a more explicit risk-based approach. Building BIO-compliant software means the software supports the controls a government organisation needs in order to meet the BIO: risk-based design, logging and monitoring, access management with least privilege, data encryption and patchability. Importantly, the BIO is a framework, not a certificate. There is no BIO certification that a supplier can obtain.
No, and that question rests on a misunderstanding we are happy to clear up: the BIO is a framework, not a certification scheme. There is no official BIO certificate that a software supplier can obtain. What a supplier can do is build software in line with the requirements the BIO sets and demonstrate that demonstrably, with technical documentation, an overview of the implemented controls, logging and access models, and pentest reports. Appfront builds this way and supplies the evidence your information security officer (CISO) and auditor need. Anyone claiming to be 'BIO-certified' is describing something that formally does not exist.
The government organisation always remains ultimately responsible for meeting the BIO; this cannot be outsourced. A municipality, province or water board makes the risk assessments, sets the information security policy and is accountable for it. A software supplier such as Appfront plays a role in the chain: we build the software so that the organisation can implement and demonstrate the necessary controls. We record agreements on patching, monitoring, incident handling and the division of responsibilities in clear documentation and, where relevant, a data processing agreement. That way our work supports your accountability without taking it over.
Government organisations are bound by the BIO and must be able to demonstrate that the software they buy fits within their information security framework. That is why, in a Request for Information (RFI) or tender, procurement officers ask how a supplier handles logging, access management, encryption, patch management and incident handling. They often ask for evidence per BIO control, for the pentest policy and for the division of responsibilities in the chain. A supplier that can answer these questions concretely and honestly, including what is and is not its responsibility, demonstrably makes the buyer's assessment easier.
Building to BIO standards is risk-based: how stringent the measures need to be depends on the sensitivity of the data and the risk profile of the application. In practice, this means least-privilege access management with role-based authorisation, strong authentication, encryption of data in transit and at rest, extensive and searchable logging and monitoring, a working patch and vulnerability process, data minimisation, and secrets management. It also takes a process: periodic penetration tests, secure development practices and an agreed incident response. We tailor the package of measures to your risk assessment rather than ticking off a fixed checklist.
ENSIA (Eenduidige Normatiek Single Information Audit) is the way municipalities account annually for their information security, including for the BIO and for specific chains such as Suwinet and the BAG. Our software contributes to this indirectly: complete, exportable logging, clearly documented access models and demonstrable control measures make the annual ENSIA accountability easier to substantiate. We don't make the software 'ENSIA-proof' on your behalf, as the accountability remains with the municipality, but we make sure the information you need is available and traceable.
The BIO focuses on information security, the GDPR on the protection of personal data; they overlap but are not the same. In government software they almost always apply together. Appfront builds with data minimisation as a starting point, documents the data flows for your record of processing activities, and designs the security measures so that they support both the GDPR and the relevant BIO controls. Where personal data is processed, we put agreements in place in a data processing agreement. This lets you demonstrably comply with both frameworks without duplicated effort.
Yes. Integrations with national services such as DigiD, Digikoppeling and the case-oriented working APIs (ZGW) come with their own frameworks and connection requirements that apply alongside the BIO. Suwinet is a telling example: the connection has its own framework and strict requirements for logging and authorisation. Appfront builds these integrations so that they fit within your broader BIO approach: with appropriate encryption, authorisation and logging, and with documentation showing how the integration meets the applicable requirements. We state upfront, and honestly, which connection requirements and responsibilities lie with you and which with us.
Ready to build BIO-compliant software?
Tell us which government process you want to support, which data it involves and what requirements your procurement team or CISO has. We're happy to help think through the risk assessment, the appropriate control measures and the substantiation you need. A no-obligation first conversation will quickly give you a clear picture of an approach that fits within your accountability under the BIO.