Difference between revisions of "Data Security Commitment"
Jump to navigation
Jump to search
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Hornbills commitment to data security and confidentiality is paramount in everything we do. To this end we have undertaken a number of objectives (including ISO27001 and 27018) to ensure your data remains secure at all times. The pages within the wiki and your contract agreements detail how we do this in detail, however below are the key points | + | This document can now be found at its new location in the [https://docs.hornbill.com/hornbill-cloud/data-security-commitment/ Hornbill Document Library]. |
| + | |||
| + | [[file:hornbill-document-library.png|Hornbill Cloud|link=https://docs.hornbill.com/hornbill-cloud/data-security-commitment/]] | ||
| + | |||
| + | <!-- | ||
| + | Hornbills commitment to data security and confidentiality is paramount in everything we do. To this end we have undertaken a number of objectives (including ISO27001 and 27018) to ensure your data remains | ||
| + | secure at all times. The pages within the wiki and your contract agreements detail how we do this in detail, however below are the key points | ||
| Line 11: | Line 17: | ||
*Any processing of log files for analytics will be anonymized. | *Any processing of log files for analytics will be anonymized. | ||
*We will inform you within 24 hours of any suspected data breach. | *We will inform you within 24 hours of any suspected data breach. | ||
| − | *Any questions or concerns can be raised via data.processor@live.hornbill.com | + | *We will report any malicious or abnormal activity on the services we provide, should the need arise (for example, Low level "background" threats such as port scans etc that may occur will not be reported, however a sustained attack against a specific instance or end point may, even if not successful) within 1 hour. |
| + | *Any questions or concerns can be raised via data.processor-hornbill@live.hornbill.com | ||
Trust and Security is a two way path and to this end we request that you meet the following | Trust and Security is a two way path and to this end we request that you meet the following | ||
| Line 18: | Line 25: | ||
*Always use the encrypted protocols when given the change (POP3s\SMPTS etc) | *Always use the encrypted protocols when given the change (POP3s\SMPTS etc) | ||
*Inform us within 24 hours if you suspect accounts linked to Hornbill have been breached. | *Inform us within 24 hours if you suspect accounts linked to Hornbill have been breached. | ||
| + | *Customers as per Terms of Service will not use any other individual’s or entity’s login or identity or any other unauthorised method to access or use the SaaS Service | ||
| − | Hornbill believes in being open and we provide our documentation\polices and procedures at https://wiki.hornbill.com/FAQ:ISO/ for all. However, Enterprise customers can schedule | + | Hornbill believes in being open and we provide our documentation\polices and procedures at https://wiki.hornbill.com/FAQ:ISO/ for all. However, Enterprise customers can schedule an annual full review of all polices\controls should they wish and if required you should contact your account manager. |
| + | --> | ||
| + | [[Category:HDOC]] | ||
| + | <!-- /hornbill-cloud/data-security-commitment --> | ||
Latest revision as of 22:15, 13 September 2023
This document can now be found at its new location in the Hornbill Document Library.
