Security
We hold business information for ourselves and for clients, and we aim to protect it the way a careful client would expect.
Where we stand
We design our delivery practices with reference to ISO/IEC 27001:2022 (the international standard for information security management systems), the American Institute of Certified Public Accountants' SOC 2 Trust Services Criteria, and the Australian Signals Directorate's Essential Eight. We are not certified against ISO/IEC 27001 and have not undergone a SOC 2 examination. On request, we will complete a security questionnaire and describe the specific controls in place for your engagement.
Accounts and access
- Multi-factor authentication is required on company accounts.
- Hardware security keys protect the most sensitive accounts.
- Passwords and recovery codes are kept in a managed password vault, never in source code, chat or email.
- Administrative cloud access uses short-lived credentials rather than long-lived access keys.
- Access is limited to what each task needs, and removed when the task ends.
Secure development
- Every change passes automated checks for code quality and known vulnerable dependencies before release.
- Secrets are kept out of source control and are rotated when exposure is possible.
- Infrastructure is defined as code and reviewed before it changes.
- Important design decisions are recorded in writing.
- We test our own business systems' backups by restoring them on a schedule.
Hosting and data location
- Client application data is hosted in Amazon Web Services' Sydney region by default. Any exception is agreed with the client in writing.
- Our standard design keeps databases on private networks with no public internet address.
- Connections are encrypted in transit, and stored data is encrypted at rest.
- Changes to important records are written to an audit log.
Service providers
The service providers we use, and what for, are listed in the privacy policy. We keep a register of providers and update the list when it changes.
If something goes wrong
We keep a written incident plan that meets the strictest notification deadline that may apply to a client. Our target is to tell an affected client within 72 hours of confirming a breach, with what we know, what we are doing, and what the client may need to do. Where Australian law requires notification of the Office of the Australian Information Commissioner and affected people, we support the client in doing so.
Report a vulnerability
If you believe you have found a security problem in this website or in software we publish, email [email protected]. The vulnerability disclosure policy explains what to include and what to expect. Our security contact details are also published in machine-readable form at /.well-known/security.txt.