Security depends on the application, its hosting and the people operating it. This page distinguishes implemented engineering from independently verified production assurance. Rollout status: the latest hardening has been implemented and validated before production rollout. Production activation and operational assurance remain pending; the controls below are not a blanket claim about the live service. Identity and access The application separates tenant, staff, platform support and verifier authority. Access is scoped to organisations and sites, with explicit verifier assignments and restricted support access. The hardening adds enforced MFA for remaining privileged owner/admin and manager sessions, recovery protections, session revocation, shared authentication limits and stronger device token handling. These changes require a coordinated production rollout. Evidence and information protection The engineering includes tenant/site isolation tests, access auditing, encrypted authenticator material, encrypted offline persistence and an audit-forwarding mechanism. HTTPS protects supported service connections. Database, volume and backup access settings, key custody and independently retained security logs require operating evidence. We do not claim NZ-only hosting or protection against a compromised device or browser. Testing, resilience and incident response Application tests and dependency, secret, source and container checks support release review. Encrypted database backup and restore procedures have been tested with synthetic data. A synthetic database restore is not proof of complete production recovery. Uploaded-file recovery, alert delivery and a timed whole-service recovery exercise remain assurance work. An incident-response procedure is prepared; no independent penetration-test report or completed participant exercise is claimed. Your responsibilities Use individual accounts, protect credentials and recovery codes, and review staff, administrator, device and verifier access. Secure shared tablets and computers, install supported updates, and reconcile offline records before replacing or resetting devices. Report unexpected access, missing evidence or suspected compromise promptly. Request deployment-specific assurance before relying on a control for procurement.
This page needs JavaScript to display in full.