Frameworks
Eleven laws, standards and norms Gluon is designed around. For each one: what it asks, where Gluon answers it, and who works to it.
European rules
European Union
GDPREU REGULATION 2016/679The European rules for personal data.4 requirements
In Gluon only the context that applies reaches an answer, and sensitive fields are masked with a reason.
Are sensitive fields masked, with a reason? Yes. What someone may not see never reaches the model or the answer. Sensitive fields are masked by policy and say why, and withheld records show as withheld.
- Applicability Engine03 Decide
Use personal data only for its purpose, and no more than needed.
Only the context that applies to this question and person.
- Permission Engine03 Decide
Appropriate security and restricted access.
What someone may not see never reaches an answer; sensitive fields are masked.
- Gluon Gateway03 Decide
Transfers outside the EU only with safeguards.
Your environment, and rules for which model may see which data.
- Evidence Engine05 Prove
Be able to demonstrate that you comply.
The decision trail shows who could see what, and why.
EU AI ActEU REGULATION 2024/1689The European regulation for trustworthy AI.3 requirements
In Gluon every answer names its source and version, and an action needs a person’s approval where your rules say so.
Is AI that assesses students high risk? Under the EU AI Act, AI that admits or assesses students is high risk.
- Authority Graph03 Decide
Transparency: it is clear what an outcome is based on.
Every answer names its source and version, and gaps are shown instead of filled in.
- Action control04 Act
Human oversight of AI that touches decisions.
Approval required where your rules say so, and a kill switch.
- Evidence Engine05 Prove
Record-keeping, so what the system did can be traced.
The decision trail for every answer and every action.
NIS2EU DIRECTIVE 2022/2555The European rules for cybersecurity, in the Netherlands the Cyberbeveiligingswet.3 requirements
In Gluon access follows your identity provider, and every decision is on a record your SIEM receives.
- Permission Engine03 Decide
Control access to systems and data, with strong authentication.
Access follows your identity provider and its sign-in rules, for people and for agents.
- Gluon Gateway03 Decide
Manage the risks of suppliers in the chain.
Models run where you choose and can be replaced, so no single supplier holds your data.
- Evidence Engine05 Prove
Detect incidents and report them in time.
Every decision is on a hash-chained record your SIEM receives, so an incident can be reconstructed.
DORAEU REGULATION 2022/2554The European rules for digital resilience in finance.3 requirements
In Gluon a model provider is replaced in configuration, so there is always a way out.
- Permission Engine03 Decide
Manage ICT risk, with access limited to what each role needs.
The permissions you already have, enforced for every answer and every action.
- Gluon Gateway03 Decide
Manage the risk of ICT suppliers, with a way out.
Providers are replaced in configuration, and the core is open source, so you can always leave.
- Evidence Engine05 Prove
Keep records that let an ICT incident be traced.
The decision trail for every answer and every action, append-only and hash-chained.
Dutch government standards
Ministerie van Binnenlandse Zaken en Koninkrijksrelaties

Logius
BIO2BASELINE FOR ALL DUTCH GOVERNMENTThe information security baseline for Dutch government.3 requirements
In Gluon access follows the permissions you already have, for people and for agents alike.
- Permission Engine03 Decide
Access to information follows from role and need.
The existing permissions, enforced for users and for agents.
- Evidence Engine05 Prove
Events are recorded and can be verified afterwards.
Every decision in an append-only, hash-chained audit trail.
- Gluon Gateway03 Decide
Supplier and cloud risks are managed.
Your own environment, with models you can swap.
Logboek DataverwerkingenVERSION 1.0The standard for logging what government does with personal data.3 requirements
Gluon logs every answer and action as a processing step, and passes the trace on.
- Evidence Engine05 Prove
Log every processing step, so what happened to someone’s data can be traced.
Every answer and every action is logged as a processing step, beside the hash-chained audit trail.
- Evidence Engine05 Prove
Link each entry to its processing activity, and record a person only by a pseudonym.
Each entry names the processing activity it belongs to, and a person appears only under a pseudonym.
- Gluon Tools03 Decide
Keep the chain traceable when one system calls another, without sharing the data itself.
The trace is passed on to every system Gluon calls, so the chain can be followed from both ends.
AlgoritmekaderThe framework for responsible algorithms and AI.3 requirements
In Gluon every use of AI carries its risk tier and autonomy, is tested on every change, and can be stopped at once.
- Authority Graph03 Decide
Know which algorithms and AI you use, and what risk each carries.
Every use of AI is described in the versioned rules, with its risk tier and how far it may act on its own.
- Evaluation runs06 Improve
Test before use, and keep checking once in use.
Every version is scored against known answers before it goes live, and again after every change.
- Action control04 Act
Human oversight, and a way to stop.
Approval where your rules require it, and a kill switch that stops a use at once.
Audit norms
ISO/IEC 27001 · 27701INFORMATION SECURITY AND PRIVACYThe international norm for information security management, which BIO2 builds on, and its extension for privacy.6 requirements
Gluon supplies access by role, protected logs and reviewed changes, and every processing of personal data is on the record.
- Permission Engine03 Decide
Access to information follows role and need.
The existing permissions, enforced for users and for agents.
- Evidence Engine05 Prove
Events are logged, and the logs are protected.
An append-only, hash-chained audit log, streamed to your SIEM.
- Review and approval01 Model
Changes are reviewed and approved before they go live.
Proposals with diffs, owner and security approvals, and signed versions.
- Applicability Engine03 Decide
Process personal data only for its purpose.
Only the context that applies to this question and person reaches an answer.
- Permission Engine03 Decide
Limit who sees personal data, and how much.
Sensitive fields are masked by policy and say why, and withheld records show as withheld.
- Evidence Engine05 Prove
Keep a record of processing.
Every processing step is logged, linked to its processing activity, the person as a pseudonym.
ISO/IEC 42001AI MANAGEMENTThe international norm for managing AI.3 requirements
In Gluon every use of AI is described with its risk, tested before and after every change, and overseen by people.
- Authority Graph03 Decide
Know your AI systems, what they are for and the risk they carry.
Every use of AI is described in the versioned rules, with its risk tier and how far it may act on its own.
- Evaluation runs06 Improve
Check that AI works as intended, before and during use.
Every version is scored against known answers before it goes live, and again after every change.
- Action control04 Act
Keep people in control of what AI does.
Approval where your rules require it, and a kill switch that stops a use at once.
SOC 2AICPA TRUST SERVICES CRITERIAThe attestation enterprise and finance customers ask of their suppliers.3 requirements
Gluon supplies the controls and the evidence for your own audit.
- Permission Engine03 Decide
Security: protect systems against access that is not allowed.
What someone may not see never reaches an answer, for people and for agents.
- Gluon Gateway03 Decide
Confidentiality: protect information marked as confidential.
Rules for which model may see which data, by classification.
- Evidence Engine05 Prove
Processing integrity: processing is complete, valid and authorised.
Every decision on an append-only, hash-chained record.
NEN 7510 · NEN 7513DUTCH HEALTHCAREThe Dutch norms for information security and access logging in healthcare.3 requirements
In Gluon an answer holds only what the care worker may see, and every access is on the record.
- Permission Engine03 Decide
Care workers see only what their role allows.
An answer holds only what this care worker may see, and withheld sections show as withheld.
- Evidence Engine05 Prove
Log who accessed which information, and when.
Every answer records who asked, what was read and when, on a hash-chained record.
- Gluon Gateway03 Decide
Health data stays protected, also from models.
Rules for which model may see which data, in your own environment.
Your audit
- Your assessmentIs Gluon certified for these frameworks?
No. Gluon is designed around them. Gluon holds none of these certificates. Your organisation is audited; Gluon supplies the controls and the evidence.
- Your evidenceWhere does the evidence live?
In the environment where Gluon runs, your own or ours in Europe. Questions, documents and decision trails stay there, and the audit log streams to your SIEM.
- Your rulesWho changed the rules, and who approved it?
Its owner. Every change to the model is a proposal with a diff, reviewed and approved before it is published as a new version. What applies, who may see what and which actions need a person are written in your model and approved by their owner.
