ISO/IEC 27001: work towards certification has started
ISO/IEC 27001 is the international standard for an information security management system: the policies, risk assessments and controls an organisation uses to protect the information it holds, and the evidence that it keeps using them. Certification means an independent auditor has checked that system. If you run a hospital, a residential aged care home or a home care service, it is one way to judge a supplier that will hold health information about the people in your care. This page shows what HealthOS already has in place, and what we are still working on.
In short
- Work towards ISO/IEC 27001 certification has started. HealthOS does not hold the certificate today.
- Much of what the standard asks for is already running: your data stored in Australia, each organisation’s records kept apart by the database, an independent penetration test and audit logs nobody can change.
- Our security policies are written and published, and formal adoption is under way.
- For the penetration test report, our policies or help with your security questionnaire, email security@healthos.net.au.
Where we are
Work towards ISO/IEC 27001 certification has started. That is our status today. We will update this page as the work moves forward, and we will only call HealthOS certified once a certificate has been issued.
A management system starts with written policies. These are the ones we publish as part of it. Each is drafted for adoption, and adopting them is part of the work under way.
- Information Security Policy: how we protect the information we hold, who is accountable, how information is classified and handled, and the suppliers involved.
- Risk Management Framework: how risks to information are found, rated, treated or accepted, and reviewed.
- Security Incident and Data Breach Response: how an incident is contained and investigated, and who is told and when.
- Personnel Security: screening, confidentiality, training, and what happens when someone leaves.
- Encryption and Key Management: encryption in transit and at rest, and how keys are stored, rotated and recovered.
- Audit Logging: what we log, and the properties every audit log has.
All six are on one page, with PDFs, at Security policies.
Already in place
These controls run today, in HealthOS SaaS, HealthOS PaaS or both. We have grouped them under the four themes the 2022 edition of the standard uses for its controls: Organisational, People, Physical and Technological.
Organisational
- Your data stored in Australia. HealthOS SaaS keeps its database, uploaded files and backups in Microsoft Azure’s Australia East region, and HealthOS PaaS runs in a cloud account you control, onshore. The one thing that leaves that boundary, de-identified text sent to Code Captain’s AI model, is explained on the trust page. Where your data lives
- Our suppliers, listed openly. Everyone who handles data for us is named on our sub-processors page. Sub-processors
- An independent penetration test. Penti, an independent security firm, tested HealthOS SaaS from outside on 1 November 2026 and found nothing critical, and we checked every finding against the code. Security testing
- A way to report a vulnerability. Anyone can report a security problem to one published address, also listed in our security.txt, and we will not pursue anyone who reports in good faith. Reporting a vulnerability
- Incident and data breach response, written down. Our response plan sets out how an incident is contained and investigated and who is told, and we will help you meet your own duties under the Notifiable Data Breaches scheme. The response plan · Notifiable data breaches
People
Screening before someone starts, confidentiality and security training are set out in our Personnel Security policy. Putting it into practice, with its training register, is part of adopting our policies, so we list it under Still in progress.
Physical
- Servers in secured data centres. HealthOS SaaS runs in Microsoft Azure’s data centres in Australia, so the physical protection of its servers is Microsoft’s. HealthOS PaaS runs in your own cloud account, under your provider’s physical controls.
Technological
- Records kept apart by the database itself. PostgreSQL row-level security, forced on every table, returns only the rows of the organisation signed in, and the application connects as a database role that cannot bypass it. Kept apart from other subscribers
- Refused attempts recorded. An attempt to reach another organisation’s records is refused and recorded as a security event, so a run of them can be seen and alerted on. Audit trails
- Audit logs nobody can change. Sign-ins, access to records, use of your government credentials and every lodgement are kept in append-only tables the database refuses to change or delete. Audit Logging
- Credentials and keys encrypted, and rotated. The credentials you connect are stored encrypted and never shown again, each key and secret has a written rotation procedure, and stored values are re-encrypted under a new key without downtime. Encryption and Key Management
- Encrypted in transit and at rest. Traffic travels over HTTPS, and the database, file storage and backups are encrypted at rest. Encryption
- Breached passwords refused. A passphrase is checked against passwords known from data breaches, and only the first five characters of a hash of it leave our servers for that check. Signing in
- Multi-factor sign-in. HealthOS SaaS accounts can sign in with a code from an authenticator app, and HealthOS PaaS signs staff in through your own identity provider, with multi-factor authentication enforced for administrator accounts. Signing in
- Personal details expire by default. In HealthOS SaaS, personal details are removed every night once they are older than the period you choose. Personal details expire
- Backups and recovery targets. The database is backed up automatically, with point-in-time recovery, and backups are kept for 35 days in Australia. Our continuity and disaster recovery plan sets recovery targets for each kind of failure, and is available on request. Recovery has been tested: we have restored the database from backup in a timed test, and redeployed the whole service into a new Azure tenancy from its infrastructure code. Backups
- Vulnerabilities found and patched. Every change to the code is scanned before release, a weekly scan checks our libraries and container images, and a critical vulnerability is patched or mitigated ahead of other work. Vulnerabilities and patching
Still in progress
Certification needs more than controls that run. It needs them adopted, owned and shown to work over time. This is what we are working on now.
- Formal adoption of our policies. The policies above are written and published as drafts. Naming an owner for each, settling the values still marked to be confirmed and adopting them is under way, and that includes putting the Personnel Security policy into practice.
- A second-region backup copy. Our backups are kept in one Australian region today. We have decided to add a daily copy of every database and stored document to a second Australian region, and it is still to be built.
- Deleting a closed workspace on schedule. Our Privacy Policy and SaaS terms promise that a closed HealthOS SaaS workspace is deleted 90 days after it closes. The date is recorded when a workspace closes, and the automatic deletion is still to be built. Personal details in a workspace are still removed every night in the meantime.
- Testing signed in. Penti tested from outside, without signing in. Testing signed in as users is next.
We will move each item from this list to the one above when it is done.
Ask us for more
- The penetration test. Penti’s certificate and report, with our response to each finding, are available to customers under a confidentiality agreement.
- Your security questionnaire. Send it to us and we will complete it.
- Our policies. The public editions are on Security policies. Ask for the detailed security pack, under a confidentiality agreement, and we will walk your team through it.
Email security@healthos.net.au
ISO/IEC 27001 is published by ISO and IEC. HealthOS does not hold certification to it today.