How American Enterprises Ensure Business Continuity When Adopting SaaS | Receiver London

As a growing number of US and Canadian businesses turn to hosted SaaS applications, the demand for escrow software solutions capable of providing continuity is growing rapidly.

In the past, these companies would have avoided hosted SaaS applications due to concerns about the perceived risks of cloud-hosted systems.

In recent years, hosted SaaS applications have been widely adopted, including productivity apps such as Monday.com, Salesforce, Slack, and Trello. As these companies have become more comfortable with hosted SaaS applications, they are expanding their adoption of everything from entire banking systems, law enforcement, airline management systems, portals insurance, ERP systems and more.

Software vendors in North America largely host their applications within AWS, Microsoft Azure, and Google Cloud Platform (GCP). These platforms offer significant benefits by providing higher levels of information security, scalability, and efficiency compared to applications hosted on-premises or in a data center.

The risk for large North American companies is that the solution and all of their data is controlled by the software vendor. For businesses to adopt hosted SaaS solutions responsibly, they need to ensure that they have a third-party continuity process in place in the unlikely event that something happens to the software vendor. Such events may include bankruptcy, a major failure that has not been corrected, or a ransomware attack.

Companies in the United States and Canada are turning to trust service providers to develop robust SaaS continuity solutions that ensure continuity of service should anything happen to the software provider. The most popular SaaS Continuity Escrow solutions include:

  • Replicated SaaS continuity with 90 days of live availability – provide a replicated cloud environment with databases using CloudFormation/Terraform templates that can be activated in the event of a release situation. In the event of a release, the escrow seller will be on hand to keep the lights on and provide continuity of service for up to 90 days.
  • Replicated SaaS environment, source code and database escrow – incorporating repository cloud environment RPM packages, templates and automatic database and source code repositories from Git repositories, including relevant documentation.
  • SaaS Access Continuity – including the deposit of the developer’s access credentials with the cloud host. Solutions include the ability for the escrow provider to maintain the production environment for a period of 90 days to ensure continuity.
  • Financial monitoring of suppliers – helps to provide the beneficiary with preventive alerts if the promoter does not pay his bills.

Evan Lever, CEO of Escrow London, said: “We are seeing a dramatic increase in SaaS escrow requirements from Fortune 500 companies, primarily financial institutions, airlines and telecommunications companies that have moved from solutions hosted in data centers to applications hosted in AWS, Azure or GCP. These companies face major challenges due to regulatory requirements and the huge amounts of data under management. Often these companies opt for SaaS access continuity, including a repository of access credentials to production account, source code, and deployment scripts as the preferred solution for robust continuity in the event of a failure. from a SaaS provider.

Comments are closed.