Hosting Security Sample Clauses
The Hosting Security clause establishes the security requirements and standards that must be maintained by the party providing hosting services. It typically outlines measures such as data encryption, access controls, regular security audits, and incident response protocols to protect hosted data and systems from unauthorized access or breaches. By clearly defining these obligations, the clause ensures that sensitive information remains secure and helps mitigate the risk of data loss or cyberattacks.
Hosting Security. Physical Security Requirements
Hosting Security. 8.1. The Licensor is committed to ensuring that your information is secure. In order to prevent unauthorised access or disclosure, we have put in place suitable physical, electronic and managerial procedures to safeguard and secure the information we collect online.
8.2. The software (Evide Impact Tracker) is hosted on a secure server encrypted using 256 bit strong SSL encryption to maintain data privacy and integrity. The system is password protected and secure programming techniques are used to prevent unauthorised access. The software will be regularly scanned for vulnerabilities.
8.3. The Evide Impact Tracker Online hosting platform is managed and maintained by MCL Services Ltd. and hosted by Rackspace in one of their secure data centres in London, UK. The facility has security on site 24/7 with offsite backup to deal with any major event. CCTV cameras, motion detection and biometric access system ensure multiple layers of security and peace of mind. Access to our server is strictly limited to authorised personnel only.
8.4. Our hosting centre is ISO 27001 certified. ISO 27001 is a specification for an information security management system (ISMS) and framework of policies and procedures that includes all legal, physical and technical controls involved in an organisation’s information risk management processes.
Hosting Security. Depending on the datacenter, the Platform may be hosted in a private cloud or public cloud.
5.1. Private Cloud data centers are third party data center providers’ hosting facilities. GoodData has directly entered into “Managed Colocation Service” agreement that provides GoodData, its customers and partners a private cloud built to GoodData’s specifications and requirements inside hosting party’s facilities. The Managed Colocation Service includes highly secure, scalable and redundant data centers and network, 24x7x365 monitoring and support, and industry-leading service levels; all certified with industry standard security certifications including ISO 27001 and SOC 2 Type II. Under this arrangement, GoodData retains operational control of its hosted infrastructure, procuring only physical hardware from the provider. The provider at no times has access to log on to any GoodData system.
5.2. Public Cloud data centers are hosted in highly secure and available facilities of IaaS providers. Under this arrangement, the provider manages the underlying hardware infrastructure, including but not limited to its physical security, and GoodData Operations manage the virtual layers. Segmentation from other customers of the IaaS provider is ensured by following best practices for virtual private clouds including virtual networks, security groups and firewall, and encryption controls. The IaaS providers maintain industry standard security certifications including ISO 27001 and SOC 2 Type II.
Hosting Security. 11.1 The Platform is hosted in the Microsoft Azure cloud. All resources are monitored by Azure Security Centre. All resources are located in the North / West European regions. Primary resources are located in the North Europe region with secondary backup/read-only resources located in UK South or West Europe regions.
11.2 All requests are over a secure HTTPS connection. Databases are encrypted at rest and do not allow external/public access.
11.3 The Azure cloud allows the Platform to scale up/down our resources as capacity demands.
11.4 Should a 3rd party service/API go offline – the Platform degrades gracefully and handles any errors appropriately.
11.5 All users require a strong password with a minimum of upper case, number, character, and symbol.
11.6 2FA two-factor authentication can be enabled for administrative users (upon request to our helpdesk).