Source
Security / trust page — HaloITSM
Checked for HaloITSM on 1 Nov 2026
- Page
- https://www.usehalo.com/security
- Checked
- 1 Nov 2026, 10:14 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:4b29bfc18936ab6e9635326eb1a7b23ef98ade9124a9c91491451ecae0182eac
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Provider Report an error
“All HALO cloud applications are deployed in Amazon Web Services (AWS), an industry leader in providing highly secure, scalable cloud infrastructure.”
-
Regions Report an error
“HALO utilises six AWS regions – London, North Virginia, Frankfurt, Montreal, Cape Town and Sydney. Each region has multiple availability zones, each physically separated from one another ensuring high availability.”
-
Certifications Report an error
“Halo Service Solutions has completed Cyber Essentials. Halo Service Solutions Ltd is SOC 2 Type 2 compliant and details can be shared on request. Halo Service Solutions Ltd is ISO 27001 compliant and details can be shared on request.”
-
Trust portal Report an error
“Alternatively, access via our trust portal: https://trust.usehalo.com/”
-
Stack Report an error
“The Halo application is built on ASP.NET Core and client-side React, and does not use PHP.”
-
Onpremise available Report an error
“On-premise 2.208.71 bundled patch released addressing .NET vulnerability CVE-205-55315”
-
Aws certifications Report an error
“AWS maintains and continues to enhance their SOC reports, certifications, including SOC, PCI, ISO and many more.”
-
Architecture Report an error
“Core applications are deployed in an N+1 configuration, so that in the event of a data center failure, there is sufficient capacity to enable traffic to be load balanced to the remaining sites.”
-
Auto scaling Report an error
“Automatically distribute application traffic across multiple availability zones that supports high availability, auto scaling and robust security.”
-
Incident management Report an error
“Robust incident management procedures allowing for reporting incidents and tracking them through to resolution. Following the ITIL framework, incidents are prioritised, and SLAs tracked.”
-
Backup schedule Report an error
“These include: hourly transactional database backups, daily full backups, and monthly full backups – stored for 3 days, 2 weeks, and 3 months respectively. Backups are stored at different Amazon data centres.”
-
Backup testing Report an error
“Monthly backup restore testing ensures backup restore process functions as expected, and that backups are taken in working condition.”
-
Qa procedure Report an error
“Every release goes through a strict QA procedure, which tests functionality, performance, configuration, user experience and stability.”
-
Version control Report an error
“A central repository is used to manage code and access to the repository is role based.”
-
Release notes Report an error
“A record of any change to the code is maintained and available to the customer in the form of release notes.”
-
Vulnerability reporting Report an error
“Please submit potential vulnerabilities via email or our support portal”
-
Acknowledgement SLA Report an error
“We acknowledge all reports within 3 business days”
-
Critical notification Report an error
“Critical/High: customers notified within 48 hours of confirmed impact”
-
Risk review Report an error
“We will implement this by maintaining a current risk assessment and treatment plan which will be reviewed not less than once a year.”
-
ISMS Report an error
“We will maintain appropriate resources by regular measurement and monitoring of our I.S. Management System (I.S.M.S.).”
-
Encryption Report an error
“Encrypt data and devices wherever possible and to maintain a pragmatic information classification scheme.”
-
Disclosure policy scope Report an error
“This policy applies to all Halo platforms, including: SaaS applications and APIs Integrated third-party components Cloud-hosted infrastructure On-premise customer deployments Internal systems supporting the platform”
-
Training awareness Report an error
“We will achieve this in part via regular Information Security (I.S.) training and awareness programmes.”
Scores citing this record
- The Change & Configuration Manager Deployment, integrations & multi-client operation
- The Change & Configuration Manager European sovereignty
- The MSP Owner Service desk, incidents & requests
- The MSP Owner Change, problem & release management
- The MSP Owner Deployment, integrations & multi-client operation
- The MSP Owner European sovereignty
- The Municipal IT Lead Service desk, incidents & requests
- The Municipal IT Lead Deployment, integrations & multi-client operation
- The Municipal IT Lead European sovereignty
- The Service Desk Lead Service desk, incidents & requests
- The Service Desk Lead Change, problem & release management
- The Service Desk Lead Deployment, integrations & multi-client operation
- The Service Desk Lead European sovereignty
- The Skeptic Service desk, incidents & requests
- The Skeptic Change, problem & release management
- The Skeptic Deployment, integrations & multi-client operation
- The Skeptic European sovereignty
- The Solo IT Admin Service desk, incidents & requests
- The Solo IT Admin Deployment, integrations & multi-client operation
- The Solo IT Admin European sovereignty