We know that security is one of the key considerations for businesses when committing to the new technology. At CloudCall, we recognize that having a secure and reliable phone service is critical to your business’s operations. CloudCall is a proprietary service, built from the ground up to support hundreds of thousands of users effectively.
We offer a robust multi-tenant cloud communications service, with several layers of built-in security to ensure that customer data is fully protected. Security is implemented via policies and governance practices during the service, development and operations processes and the application and infrastructure layers.
01. Application Security
Our applications are designed to be resilient, both operationally and in terms of security. All security considerations are taken into account during the design, development and QA stages, with thorough security testing being undertaken throughout the year.
Our service perimeter is protected with firewalls and session border controllers. Our service environment is protected through the use of VPNs; two-factor authentication is enforced for additional security.
We use TLS to encrypt web session traffic and to encrypt provisioning sessions for CloudCall desk phones. Additionally, desk phones, mobile applications, and desktop applications, support encrypted calls using SIP over TLS for signalling and SRTP for media.
04. Physical Security
Our services are hosted in data centers that undergo SSAE16 and/or ISO 270001 audits.
In the UK, our systems are stored at the Telehouse data center facility, located in London Docklands and have secure backup links to data center facilities in Telehouse North and West.
In the US, our systems are stored with the Markley Group of Boston at One Summer Street, with a disaster recovery facility in Lowell, MA.
The data centers that host CloudCall share hosted facilities space with some of the world’s largest Internet companies and financial institutions. The geographic diversity of these locations act as an additional safeguard, minimizing the risk of loss and service interruption as a result of natural disasters and other catastrophic situations.
05. Disaster Recovery and Contingency Planning
Our services are architected to support failover conditions, in case of emergencies. The CloudCall service is built with geographically distributed redundancy. We don’t just provide primary and backup locations; we have Active/Active sites online, simultaneously. Database replication between locations is in real-time, with failover being built into the service. If a primary location is unavailable, the other Active location will continue service.
As well as infrastructure and application redundancy, we have geographically distributed operations so that service operations can continue if one location is not available.
We operate our own disaster recovery procedures. The CloudCall platform is automatically backed up on a daily, weekly and monthly basis. For contingency planning, we operate multiple backup connections and redundant servers. Our network systems securely monitor alarm signaling through to the network operations center, which automatically alerts us, in the event of an emergency within the data center.