For the CISO and the IT manager
One meeting. Every control in writing.
Inora runs in the EU or on your own servers, and staff sign in through your own identity provider. The answers are here; the IT pack goes in your archive.
IT and security pack · PDFv1.13 · 11 Nov 2026 · 393 kB
Does this cost my team work?
Decree on electronic data processing by care providers
art. 3(2), under art. 15j of the Wabvpz
Health and Youth Care Inspectorate (IGJ)
Questions about NEN 7510, on your IT suppliers
Dutch Cybersecurity Act (Cbw)
art. 21(3)(d), in force since 15 August 2026
Your audit file starts with these answers.
The short form here. The full security overview goes with it.
Who can reach production?
Only the engineers who build Inora.
Named in the processing agreement, with a personal account, multi-factor authentication and a certificate of conduct. Every access is logged.
How can Inora read the record without a connection?
In a machine of its own per user, with that person’s login and rights. We show it to you in a demonstration.
It is designed like this: each user gets a microVM with its own kernel. The care worker logs in personally; Inora stores no passwords. The session is held encrypted inside that machine, never longer than the task; then the machine is destroyed with everything in it. Inora can read only under your organisation’s own agreement with its ECD vendor, and only in the systems you name. Every step is logged in the user’s name. Scheduled work, such as at night, is logged in the name of its scheduled owner: whoever is on the roster or owns the rule, and approved it beforehand. The log will show both.
What can go back into the record?
Only the report, on the care worker’s approval.
Inora works on someone’s behalf, never with more rights than that person has. The log will show both. An incident report or care plan change can be prepared as a draft and then goes through its own system on approval. We show this in the demonstration too.
Does processing stay in the EU?
Yes, the backups and the language model too.
Nobody trains a model on your data: not us, and not the model’s supplier.
How is the data encrypted?
TLS 1.2 or higher in transit, AES-256 at rest.
Databases, document stores, search indexes and backups.
Someone leaves. What do I do?
Switch the account off in your identity provider.
An open session stops after eight hours at most.
How long are backups kept?
Daily, encrypted, 30 days, in the EU.
Every quarter we restore a backup to check that it works.
What is logged?
Sign-ins, admin actions and every access by Axiomatic, for 12 months.
On request you receive the security logs of your environment. Once Inora reads the record, through a connection or the user’s own login, Inora also keeps a record log, set up to NEN 7513: per step what Inora did and on whose behalf, open to the function you appoint.
How fast do security updates land?
Critical ones within 72 hours, others within 30 days.
New features are announced a week ahead, with the outcome of the test.
How available is Inora?
Built for 99.9%. A response within an hour, day and night.
95% of outages resolved within four hours. During an outage your organisation’s contact gets notices by email. How much data can be lost at most and how fast we recover is under control 5.30.
Is Inora tested for vulnerabilities?
Yes, every year with a penetration test by an independent party.
The summary of the report is yours on request. Findings are fixed within the terms for security updates.
May we audit Inora ourselves?
Yes.
We cooperate with audits by your organisation or your auditor.
And if there is an incident?
We report a data breach within 24 hours.
With what you need for your own report. The written report follows within ten working days. Found a weakness? Mail us with ‘Security’ in the subject line.
Report a vulnerability
One consent in your identity provider. Nothing else.
No IT project: no installation, no VPN, no firewall rule.
Your own identity provider
Entra ID, Okta, Google or any other provider. SCIM creates and closes accounts. Inora stores no passwords.
SAML 2.0 · OpenID Connect · SCIM 2.0
Nothing on your network
Inora runs in the EU or on your own servers; your network does not change.
No VPN · no firewall rule
No installation
Inora runs in the browser and the app; we do the updates.
One shortcut in the Start menu, if you like; beyond that nothing on the workstation
0hoursWith single sign-on, for the whole pilot, from the first sign-in to the evaluation. Reading the record is not in it: your IT turns that on, per system.
Your administrator gives Inora consent once and picks the groups that may use it; from then on SCIM keeps the accounts in step. The pilot needs no connection: staff work with their own login. Connections come after it, and your IT turns them on.
With Entra ID, the consent gives Inora only openid, profile, email and User.Read, delegated and read-only; your groups arrive as a claim in the sign-in token. Inora reads only the groups you assign to the app, so the claim never overflows. No access to mail, files, Teams or SharePoint.
Read the email to your administrator, with the four connectors after the pilot
- From
- Axiomatic, the Inora team
- To
- Your IT administrator
- Subject
- Team North works with Inora from Monday
Dear administrator,
From Monday, team North works with Inora. Sign-in through your own identity provider, with single sign-on. One shortcut in the Start menu, if you like; beyond that nothing on the workstation and nothing on your servers. Inora runs as a service, in the EU.
This is what we ask: grant Inora consent in Entra ID once and assign the groups Inora may use. Inora then receives the name, e-mail address and profile of each member of staff in those groups (openid, profile, email, User.Read), and nothing else: no mail, no files, no Teams or SharePoint. Whoever you disable in Entra ID is out of Inora the same day.
The Inora team
P.S.After the pilot your IT turns on the four connectors, each with its own rights.
- WritesNedap OnsThe report in the client record, on the care worker’s approval; Inora acts on that person’s behalf, never with more rights than they have.Switched on by: Your IT
- ReadsSharePoint and OneDriveOnly the documents your organisation has approved.Switched on by: Your IT
- FollowsZenyaAlways the released version of your protocol.Switched on by: Your IT
- FeedsMicrosoft CopilotYour approved agreements, with your handbook as the source, and what the care worker may see in the record, in your own Microsoft 365 tenant. For mail, files and Teams your own Microsoft 365 permissions apply.Switched on by: Your IT
Your data never leaves the EU.
One environment per organisation. Only the engineers who build Inora can reach it.
European Union
Your organisation
Care workers. In the browser or the app, on any device. Nothing installed.
Your identity provider. SAML or OpenID Connect, with SCIM. You set MFA and password rules yourself.
Amazon Web Services EMEA SARLRegion Europe (Ireland) · eu-west-1
Your environment. For your organisation only.
Database (AES-256) · Document storage (AES-256) · Search index (AES-256) · Backups (Daily · 30 days) · Logs (12 months)
Other organisations. Each in its own environment, separated in the infrastructure.
The language model, in the EUEU inference profile · AWS Regions in the EU
Language model · EU. At AWS
The question and the passages are not stored and do not go to the model’s maker.
Microsoft Azure · EU regionSub-processor
Language model · EU region. At Microsoft Azure
Question, passages and topic · TLS 1.2+
With the modified abuse monitoring Microsoft approves: Microsoft stores no questions or answers, and no Microsoft employee reads them.
No model trains on your data.
Axiomatic, Delft
The engineers who build Inora. Personal account, MFA, screened
Every access logged
Everyone else at Axiomatic: no access
Data, backups and logs never cross this boundary.
- One environment per organisationIts own database, document storage and search index, encrypted with AES-256; TLS 1.2 or higher in transit. Backups daily and encrypted, kept as long as the drawing shows, in the Europe (Ireland) region, across several availability zones. The separation is in the infrastructure, not only in the software.
- The language modelThe system picks the language model for each task, always in the EU. No model trains on your data. For the team reports the language model that writes the answer sets the topic at the same time; no person reads along, and the model keeps nothing. The sorting stays in the environment and is deleted with the conversation.
Set out in SecuritySub-processorsAbuse monitoring in Azure OpenAI
Built to NEN 7510 and ISO 27001.
All 101 controls, each with how we built it.
Organisational3737 in place37 in place
5.1
Policies for information security
In place
The security policy and the security overview set out how Inora is secured, and both are public. Everyone at Axiomatic reads and signs the security rules at the start and every year after. The director approves the policy and reviews it every year and after every serious security incident.
5.2
Information security roles and responsibilities
In place
The director is responsible for security and privacy at Axiomatic. The security overview names who can reach production and who cannot.
5.3
Segregation of duties
In place
No change reaches production without review by a second engineer. Whoever guides organisations through implementation has no access to production or to their data.
5.4
Management responsibilities
In place
Management requires everyone to sign the security rules at the start and every year, and carries the responsibility for security and privacy itself.
5.5
Contact with authorities
In place
In a data breach we help the organisation notify the Autoriteit Persoonsgegevens. We answer a request from an authority only where Union or Dutch law obliges us, with no more than necessary and, unless the law forbids it, after the organisation knows.
5.6
Contact with special interest groups
In place
We follow the security advisories of the NCSC and Z-CERT and the security notices of every building block Inora runs on.
5.7
Threat intelligence
In place
With the advisories from 5.6 we review every month which threats bear on Inora, and record it. Known vulnerabilities in the libraries are tracked automatically.
5.8
Information security in project management
In place
Every implementation and every new feature starts with its security questions answered in writing: which data, who can reach it, which supplier.
5.9
Inventory of information and other associated assets
In place
A register lists every system, supplier, data store and laptop, each with an owner, checked every quarter.
5.10
Acceptable use of information and other associated assets
In place
The security rules everyone signs say how information and laptops may be used. Organisation data never sits on a laptop.
5.11
Return of assets
In place
When someone leaves, the laptop comes back on the last working day and is wiped. Access ends the same day.
5.12
Classification of information
In place
Everything users type into Inora is classed as health data and protected as such. The organisation’s documents are classed as internal.
5.13
Labelling of information
In place
Every environment, store and search index carries the label of its organisation and its data class in the infrastructure.
5.14
Information transfer
In place
All traffic to and from Inora, and between its parts, is encrypted with TLS 1.2 or higher. What we do with data, and with whom, is set down in the data processing agreement.
5.15
Access control
In place
The organisation decides which groups of staff get access and who administers. Only the engineers who build Inora can reach production, each by name.
5.16
Identity management
In place
Staff sign in with their own account through the organisation’s identity provider, by SAML or OpenID Connect; SCIM creates and closes accounts. When the organisation disables an account there, that person can no longer sign in. There are no shared accounts.
5.17
Authentication information
In place
With single sign-on Inora stores no passwords. Administrative access to production needs a physical security key, and service keys and certificates sit in a key vault, never in the source code.
5.18
Access rights
In place
Every quarter we review access rights. When someone leaves, their access ends the same day.
5.19
Information security in supplier relationships
In place
We work with as few sub-processors as we can: for Inora Amazon Web Services, and Microsoft (Azure OpenAI, EU). We remain responsible for what our suppliers do.
5.20
Addressing information security within supplier agreements
In place
Every sub-processor has signed an agreement with obligations no weaker than those in our data processing agreement.
5.21
Managing information security in the ICT supply chain
In place
Inora runs on open building blocks and its language model can be exchanged, so it depends on no single vendor. The libraries it runs on are checked for known vulnerabilities.
5.22
Monitoring, review and change management of supplier services
In place
We announce a new sub-processor 30 days ahead. The organisation can object. If we find no solution together, it may end the agreement for the part that cannot be delivered without the new sub-processor, at no cost.
5.23
Information security for use of cloud services
In place
Inora runs at Amazon Web Services EMEA SARL in the Europe (Ireland) region, its language model through Amazon Bedrock’s EU inference profile or through Azure OpenAI in the EU; the system picks the model. No one trains models on this data. Amazon Bedrock does not store the question or the passages and does not pass them to the model’s maker, and Azure OpenAI runs with the modified abuse monitoring Microsoft approves for sensitive data, so Microsoft stores no questions or answers and no Microsoft employee reads them.
5.24
Information security incident management planning and preparation
In place
A written incident procedure in seven steps: detect, contain, assess, notify, support, report and learn.
5.25
Assessment and decision on information security events
In place
Every event is assessed for the organisations, data and people it touches, and placed in one of four severity classes, critical to low, as Responsible disclosure describes them.
5.26
Response to information security incidents
In place
We notify the organisation of a breach, or a suspected one, no later than 24 hours after becoming aware, with what is known. A written report follows within ten working days.
5.27
Learning from information security incidents
In place
We investigate every incident without blame, with the cause sought in the system, and change the system or the procedure so it does not recur.
5.28
Collection of evidence
In place
In an incident we capture a snapshot of the affected environment before anything changes, with who took it and when. The logging is immutable (5.33).
5.29
Information security during disruption
In place
The restore procedure is written down, so any engineer can run it alone. After a restore we apply deletions again.
5.30
ICT readiness for business continuity
In place
A backup every day, a restore test every quarter, at most 24 hours of data lost. A restore from back-up takes at most 8 hours. Built for 99.9% availability, with the target of 95% of outages resolved within 4 hours and a response within an hour, day and night.
5.31
Legal, statutory, regulatory and contractual requirements
In place
The GDPR, the Dutch UAVG and the AI Act are worked through for Inora in the published policies. The data processing agreement follows Article 28 GDPR.
5.32
Intellectual property rights
In place
Protocols and handbooks stay the property of the organisation that wrote them. For sources from others, such as national guidelines, their publisher’s licence applies.
5.33
Protection of records
In place
Logs are kept for 12 months in the EU and cannot be changed by the application. Invoices and the records behind them are kept for seven years, as Dutch tax law requires.
5.34
Privacy and protection of PII
In place
The organisation is the controller, we are the processor. No one in the organisation reads a member of staff’s conversation, and no model trains on the data.
5.35
Independent review of information security
In place
The organisation or its auditor audits every obligation in the data processing agreement, in principle once a year.
5.36
Compliance with policies, rules and standards for information security
In place
Every year we check this matrix against what runs in production; a deviation is fixed or recorded.
5.37
Documented operating procedures
In place
The incident procedure and the restore procedure are written down, so any engineer can run them alone.
People88 in place8 in place
6.1
Screening
In place
Everyone with access to production holds a Dutch certificate of conduct (VOG).
6.2
Terms and conditions of employment
In place
Everyone signs a confidentiality agreement that holds after they leave, and the security rules, at the start and every year after.
6.3
Information security awareness, education and training
In place
Twice a year the team trains on phishing and on handling care data. Everyone signs the security rules at the start and every year.
6.4
Disciplinary process
In place
The security rules state what follows a breach of them, from a conversation to withdrawn access and dismissal.
6.5
Responsibilities after termination or change of employment
In place
Confidentiality continues after someone leaves, and their access ends the same day.
6.6
Confidentiality or non-disclosure agreements
In place
Everyone at Axiomatic has signed a confidentiality agreement, as Article 30(4) UAVG asks of anyone who processes health data without a professional duty of secrecy.
6.7
Remote working
In place
Work laptops have full-disk encryption, a firewall and automatic security updates, and lock after a few minutes. Organisation data never sits on a laptop.
6.8
Information security event reporting
In place
A lost or stolen laptop is reported the same day. Researchers report a vulnerability by email and hear back within three working days.
Physical143 in place11 in place at AWS3 in place11 in place at AWS
7.1
Physical security perimeters
In place at AWSInora runs only in Amazon Web Services data centres in the EU; their physical security lies with AWS, under its own ISO/IEC 27001 and SOC 2 reports. Axiomatic’s office holds no organisation data.
7.2
Physical entry
In place
Axiomatic has no server room of its own; no one from Axiomatic enters a data centre. We reach Inora only remotely, with a personal account and a physical security key (the data centres themselves: 7.1).
7.3
Securing offices, rooms and facilities
In place at AWSThe rooms that hold organisation data are AWS’s. No Axiomatic office holds organisation data.
7.4
Physical security monitoring
In place at AWSAWS monitors its data centres, as its own audit reports describe.
7.5
Protecting against physical and environmental threats
In place at AWSFire, water, power and climate in the data centres are AWS’s responsibility. Backups are kept apart from production, encrypted, in the EU.
7.6
Working in secure areas
In place at AWSWork inside the data centres’ secure areas is done by AWS; Axiomatic does not work there.
7.7
Clear desk and clear screen
In place
Laptops lock after a few minutes unattended. Organisation data never sits on a laptop, so it never sits on a desk either.
7.8
Equipment siting and protection
In place at AWSInora’s servers are AWS’s, sited and protected by AWS.
7.9
Security of assets off-premises
In place
Laptops have full-disk encryption. A lost or stolen laptop is reported the same day, and its access is withdrawn.
7.10
Storage media
In place at AWSStorage holding organisation data is AWS’s, encrypted with AES-256. Laptop disks are fully encrypted.
7.11
Supporting utilities
In place at AWSPower, cooling and network in the data centres are AWS’s responsibility.
7.12
Cabling security
In place at AWSCabling in the data centres is AWS’s responsibility. All of Inora’s traffic is encrypted, over those cables too.
7.13
Equipment maintenance
In place at AWSAWS maintains the equipment in its data centres. Laptops install security updates automatically.
7.14
Secure disposal or re-use of equipment
In place at AWSDisks that held organisation data are AWS’s, which wipes or destroys them under its own audited procedure. Laptops hold no organisation data.
Technological3434 in place34 in place
8.1
User endpoint devices
In place
Work laptops: full-disk encryption, a firewall, automatic updates and a screen lock. The organisation’s staff use Inora in the browser, signed in through the organisation’s own identity provider.
8.2
Privileged access rights
In place
Only the engineers who build Inora have administrative access to production, each with a personal account, multi-factor authentication and a physical security key. Every access is logged.
8.3
Information access restriction
In place
A question in one organisation can reach only that organisation’s documents. No one in the organisation reads a member of staff’s conversation. Axiomatic reads a conversation only on a written request from the function the organisation names, for an incident or a complaint, or on a legal demand (art. 5.6); every access is logged and the member of staff is told, unless the law forbids it. In an outage or security incident Axiomatic examines the system logs and the answer record, never a conversation. For the team reports the language model that writes the answer sorts the conversation by topic in the same step, without names; no person reads along (art. 5.6).
8.4
Access to source code
In place
The source code is reachable only through a personal account with multi-factor authentication, and every change to it is reviewed by a second engineer.
8.5
Secure authentication
In place
Sign-in runs through the organisation’s own identity provider, by SAML or OpenID Connect, under its own multi-factor rules; SCIM creates and closes accounts. With Entra ID the consent gives Inora only openid, profile, email and User.Read, delegated and read-only; no access to mail, files, Teams or SharePoint. Inora reads only the groups the organisation assigns to the app, so the claim never overflows. A session ends no later than eight hours after it starts.
8.6
Capacity management
In place
Load, storage and model capacity are measured per environment, with an alert before a limit is reached.
8.7
Protection against malware
In place
Every document that enters Inora is scanned for malware before it reaches the search index. Laptops run the operating system’s malware protection.
8.8
Management of technical vulnerabilities
In place
Inora’s libraries are checked automatically for known vulnerabilities. Critical security updates are applied within 72 hours, others within 30 days.
8.9
Configuration management
In place
The infrastructure is defined as code and reviewed like software, by the same second engineer as a change to Inora.
8.10
Information deletion
In place
Conversations are deleted after 90 days, or after the period the organisation sets; a conversation the function in annex 3 to the data processing agreement asked for stays until the investigation is complete (art. 5.5). After the agreement, active systems are empty by day 30 and backups by day 60, confirmed in writing.
8.11
Data masking
In place
Development and testing use no organisation data. The measurements Axiomatic sees contain no names and no content of documents, questions or answers.
8.12
Data leakage prevention
In place
A question can reach only its own organisation’s documents. Organisation data never goes onto a laptop or into the AI tools we use to write software.
8.13
Information backup
In place
A backup of every environment every day, encrypted, kept for 30 days, in the Europe (Ireland) region. Every quarter we restore one to check that it works.
8.14
Redundancy of information processing facilities
In place
Inora runs across several availability zones of the Europe (Ireland) region, so the loss of one data centre does not stop it. The stored data also sits across several zones at AWS.
8.15
Logging
In place
Inora records sign-ins, administrative actions and every access by Axiomatic staff, for 12 months. On request an organisation receives its environment’s security logging, totalled per team of at least five people and per day, and every access by Axiomatic; a day with fewer than five sign-ins shows as ‘<5’. The sign-in times and IP addresses of one member of staff never go to the organisation. In a security incident Axiomatic investigates the log itself and reports a finding about the system, naming no care worker.
8.16
Monitoring activities
In place
We are alerted to repeated failed sign-ins, unusual traffic, errors and unavailability.
8.17
Clock synchronization
In place
Every server takes its time from the cloud provider’s time service, so the logs of every part line up to the second.
8.18
Use of privileged utility programs
In place
Administrative tools that can bypass the application reach production only through the engineers’ personal accounts, with a physical security key. Every access is logged.
8.19
Installation of software on operational systems
In place
Software reaches production only as a reviewed release through the deployment pipeline; no one installs anything on a running server by hand.
8.20
Networks security
In place
All traffic to Inora and between its parts uses TLS 1.2 or higher; older protocols are refused.
8.21
Security of network services
In place
Inora is reachable only through AWS’s load balancer, behind a web application firewall that blocks known attack patterns.
8.22
Segregation of networks
In place
Each organisation has its own environment, separated in the infrastructure and not only in the software. Development and testing run apart from production.
8.23
Web filtering
In place
Work laptops filter web traffic at DNS level and block known malicious domains.
8.24
Use of cryptography
In place
TLS 1.2 or higher in transit, AES-256 at rest for databases, document storage, search indexes and backups. The keys sit in AWS Key Management Service, in the EU; every use is logged. Secrets sit in a key vault.
8.25
Secure development life cycle
In place
Every change is reviewed by a second engineer, with the OWASP Top 10 as checklist. If the organisation gives a written instruction for it, after the consent of its works council where it has one, every new version is tested on its test set, its own questions and flagged answers stripped of names, before its staff see that version.
8.26
Application security requirements
In place
Beside the OWASP Top 10, what is particular to Inora counts as a security fault: an answer outside the organisation’s sources, or one organisation reaching another. The severity classes on Responsible disclosure name them.
8.27
Secure system architecture and engineering principles
In place
Each organisation has its own database, document storage and search index; no shared database with organisations told apart by a column. The language model can be exchanged, and processing stays in the EU.
8.28
Secure coding
In place
The OWASP Top 10 is the checklist at every review. Secrets never sit in the source code, and libraries are checked for known vulnerabilities.
8.29
Security testing in development and acceptance
In place
If the organisation gives a written instruction for it, after the consent of its works council where it has one, every new version is tested on its test set, its own questions and flagged answers stripped of names, before it goes live.
8.30
Outsourced development
In place
Inora is built by Axiomatic’s own engineers. No outside contractor has access to production or to organisation data.
8.31
Separation of development, test and production environments
In place
Development and testing happen in a separate environment, without organisation data.
8.32
Change management
In place
Every change is reviewed by a second engineer before it reaches production. Planned maintenance is announced in advance, and a function the organisation relies on is never removed unannounced.
8.33
Test information
In place
Test data contains no organisation data; development and testing happen without it.
8.34
Protection of information systems during audit testing
In place
Audits and tests on production are agreed in advance, read-only where possible and outside the busiest hours.
Healthcare (NEN 7510)88 in place8 in place
5.38
Analysis and specification of information security requirements
In place
Every feature is held in advance to the OWASP Top 10 and to the faults particular to Inora: an answer outside the sources, or one organisation reaching another.
5.39
Uniquely identifying subjects of care
In place
Inora keeps no register of care recipients, so it has no duplicates; unique identification and merging happen in the organisation’s ECD. Inora asks for no citizen service number.
5.40
Validation of displayed or printed data
In place
Inora keeps no register of care recipients. A report about a client goes, on the care worker’s approval, into the record of the client they have open in the ECD, where the organisation identifies the client. Every sentence that rests on a source of the organisation carries a marker that shows the document and the passage.
5.41
Publicly available health information
In place
Public sources the organisation designates, such as national guidelines, are read as published, under their publisher’s licence, and every answer shows the source it rests on.
5.42
Communication in emergencies
In place
The organisation reports an outage that makes Inora unusable to support@axiomatic.digital, day and night; a response within an hour. In a breach its contact hears no later than 24 hours after we become aware. We test the channel and a second contact every year with the organisation’s contact.
5.43
Reporting incidents externally
In place
We notify the organisation of a breach no later than 24 hours after becoming aware and help it notify the Autoriteit Persoonsgegevens, which it must do within 72 hours where feasible.
6.9
Management training
In place
Management takes training every year in the duties the Cyberbeveiligingswet and NEN 7510 place on it.
8.35
Zero trust principles
In place
No access rests on a network location: every user signs in through the organisation’s own identity provider, every administrative access takes a personal account and a physical key, and every access is logged.
Beneath Inora: the certificates of AWS and Microsoft.
Their own certificates for their own services, each with its source.
Amazon Bedrock
The same ISO certificates, C5 and SOCAs the hosting below, with Amazon Bedrock in scope; Bedrock Marketplace is not.- ISO/IEC 42001:2023SchellmanThe management of AI systems, with Amazon Bedrock in scope.
Microsoft Azure
ISO/IEC 27001, 27017 and 27018Information security, cloud services and personal data in the cloud; which Azure services are in scope is on the Service Trust Portal.- SOC 2 Type 2The auditor’s report on Azure, every six months, available on the Service Trust Portal.
- ISO/IEC 27001, 27017, 27018 and 27701EY CertifyPointInformation security, cloud services, personal data in the cloud and privacy management, for the services and Regions on AWS’s list.
- BSI C5The German cloud standard, with the Ireland Region in scope.
- SOC 1, 2 and 3The auditor’s reports, available in AWS Artifact.
What the Dutch Cybersecurity Act asks is ready.
Duty by duty: what we do, and which document you file with it.
- 01Duty of careArt. 21(3)(d): the supply chain
Every control is described, with how we built it. The data processing agreement binds us to them, and we cooperate with your audit.
- 02Duty to reportArt. 26: the early warning
A personal-data breach in your environment, or a suspected one, we report no later than 24 hours after becoming aware of it, with what you need for your own notification. The report follows within ten working days.
- Notice and report of a data breachIn the file
- SecurityOpen
- 03Board’s trainingArt. 24(2) to (5)
A briefing for your board: what Inora is, where it stops and how it is secured.
- Briefing for your board’s trainingOn request
- 04AccountabilityArt. 24(1): the board approves
One party answers for it: we build Inora, implement it and run it. We stay responsible for our sub-processors.
The file is ready for your records.
What IT receives from Inora, and when.
- PDFv1.13 · 11 Nov 2026IT and security packWhat day one costs your team, where the data is, who can reach it, and every measure.it-security-pack.en.pdf
- PDFv1.3 · 9 Nov 2026Control matrixEvery control of NEN 7510 and ISO 27001, and how we built it. Updated every quarter and checked once a year against what runs in production. The basis for your statement of applicability.control-matrix.en.pdf
- PDFv1.4 · 9 Nov 2026Security overview (full)Every security measure, and the connection to your identity provider.security-overview.en.pdf
- PDFv1.6 · 11 Nov 2026Sub-processorsWho else processes data, and where.sub-processors.en.pdf
Security
Inora and your data are secured, with fixed measures for protection and recovery.
3 Nov 2026
Before the first question
Responsible disclosure
How to report a vulnerability in Inora or on this site, and what we do next.
9 Nov 2026
Before the first question
What changed, with every new version
What each new version changes, with the outcome of the test: new features announced ahead, security updates reported afterwards.
With every new version
ConfidentialRequest an example
An example of every confidential document, with made-up data, is available from us.