<style>p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><p><strong>In this guide we will cover:</strong></p><p><strong>- FAQs around Security Management and Architecture</strong></p><p><br></p><p><br></p><p><span style="font-size: 12pt;"><strong>How is customer backup data retained with Halo?</strong></span></p><p><span style="font-size: 11pt;">Transactional backups are taken hourly, retained for 3 days.</span></p><p><span style="font-size: 11pt;">Daily full backups are retained for 2 weeks.</span></p><p><span style="font-size: 11pt;">Monthly full backups are retained for 90 days.</span></p><p><span style="font-size: 11pt;">UAT environments only have the daily backups taken, also retained for 2 weeks.</span></p><p><br></p><p><span style="font-size: 12pt;"><strong>Where is customer data stored?</strong></span></p><p><span style="font-size: 11pt;">Data is stored for the customer on their relevant AWS hosted data </span><span style="font-size: 14.6667px;">centre</span><span style="font-size: 11pt;"> zone within a regional S3 bucket solution</span></p><p><br></p><p id="isPasted"><span style="font-size: 12pt;"><strong>How is customer data encrypted at rest?</strong></span></p><p><span style="font-size: 11pt;">All databases and backups are encrypted at rest using AES-256 key encryption</span></p><p><br></p><p><span style="font-size: 12pt;"><strong>What IPs does Halo use for X component/process?</strong></span></p><p><span style="font-size: 11pt;">IPs relating to Halo internal components will not be useful to an external party, they are held within a private subnet(making them inaccessible to the outside internet) and change regularly. </span></p><p><br></p><p><span style="font-size: 12pt;"><strong>Is Halo compliant with X standard/guideline?</strong></span></p><p>All certifications and security reports completed by Halo can be viewed on our trust centre portal - <a target="_blank" rel="noopener noreferrer" data-fr-linked="true" href="https://trust.usehalo.com/" data-pasted="true">https://trust.usehalo.com/</a></p><p><br></p><p><strong><span style="font-size: 12pt;">What is the Halo release schedule/procedure for patches and upgrades?</span></strong></p><p>We have two different schedule paths available for customers, stable and beta. For clarity, upgrades refer to a change to the second number of a version IE 2.131.10 to 2.132.8 and may include changes to the schema, and a patch is a change to the last number IE 2.132.8 to 2.132.9 and will not include schema changes, only bug fixes/improvements.</p><p>The beta path is subject to version upgrades approximately every two weeks, and is rolled out to customers over two days. This will be out of working hours for all regions. Version rollouts may be delayed for the beta path during release candidate periods, as the development team prioritises bug fixes and optimisations for the upcoming stable.</p><p>The stable path is subject to version upgrades quarterly, and is rolled out to customers over a course of several weeks. The version that will become the stable (release candidate) is announced and available to customers to opt into 4 weeks before release as the stable. The upgrade schedule is communicated to customers 2 weeks before the start of the upgrade process. This will be out of working hours for all regions.</p><p>Patches are rolled out to customers at the discretion of the Halo team, this may include during working hours. </p><p><br></p><p><strong><span style="font-size: 12pt;">What is the target availability for Halo instances?</span></strong></p><p>We target a 99.95% uptime for all production instances</p><p><br></p><p><strong><span style="font-size: 12pt;">What are Halos recovery targets during an incident?</span></strong></p><p>Halo sets a recovery time objective of 4 hours for any given incident. This is the time taken during a disaster to restore a base level of operation. We set a recovery point target of 1 hour, meaning that data within the instance will be preserved from within an hour of the disaster incident occurring.</p><p><br></p><p><b style="font-size: 11pt;"><span style="font-size: 12pt;">How are different customers </span></b><span style="font-size: 12pt;"><strong>separated</strong><b style="font-size: 11pt;"> within Halo's system architecture?</b></span></p><p>Customers are separated only at the database level. Underlying backend infrastructure and application level systems are shared between a subset of customers, but each customer has their own database</p>
