Security
Secure development, controlled access, vulnerability management and incident readiness.
Security, privacy, resilience and assurance information for Horizon Lab. We publish only claims we can support and show work that is still underway.
Version 1.0 · Assurance source reviewed 30 September 2026 · Next review by 31 December 2026Pre-launch position. This page describes the current assurance roadmap, not completed independent verification.
Secure development, controlled access, vulnerability management and incident readiness.
Purpose-limited data use, client confidentiality and accountable handling of personal information.
Monitoring, recovery planning and clear communication when service is affected.
Claims tied to evidence, named owners and review dates—not unsupported badges.
These labels distinguish work that is underway from independently completed assurance.
Adopted as the portal engineering baseline. Verification and independent testing remain release gates.
NIST Secure Software Development Framework guidance supports design, build, review and release practices.
Required before public release, with critical and high findings remediated and retested.
Horizon Lab does not currently claim ISO/IEC 27001 certification.
Horizon Lab has not completed a SOC 2 Type I or Type II examination.
How Horizon Lab proposes to handle personal information. Published for specialist review before launch.
Read the draftRules for authorised access, permitted use, confidentiality and security. Published for specialist review before launch.
Read the draftThe providers supporting the service, their processing locations and relevant transfer safeguards. The register remains pre-launch work.
A security questionnaire, high-level architecture and continuity overview, and available assurance evidence. Availability and scope are confirmed individually; the controlled-access workflow is still being prepared.
A summary that does not disclose exploitable detail, following independent testing, remediation and approval.
An independently hosted source of availability updates and incident communications. No live status service is connected yet.
Existing and prospective clients can discuss the evidence needed for their due diligence. Sensitive technical detail, vulnerabilities, client identities and client-specific evidence do not belong on a public website.
The planned process verifies the requester and purpose, limits the material shared and provides approved, logged, time-bound access. This workflow is not yet live.
Suspected vulnerabilities should be reported confidentially. Do not access client data or publish sensitive findings before they can be investigated.
The dedicated security reporting mailbox will be published once it is activated, monitored and tested. Do not submit exploitable detail through this prototype.
The Horizon Lab Privacy Officer will handle access, correction and other personal-information questions.
The dedicated privacy contact channel is being prepared and must be confirmed before launch. The draft privacy statement explains the proposed approach.
Read the privacy statement