Who Is Responsible For Managing Your Deployment?

Have you considered who would redeploy your software application in the event of a release?

This often overlooked aspect of software resilience is one of the most important to consider. In the unfortunate event your supplier is no longer available to support your application and the Software Escrow agreement is called upon, you need a clear plan of action detailing how you will get your critical systems back online and who will take responsibility for the deployment.

How do you choose who should take this responsibility?

Do you have the in-house expertise to redeploy your application? Many businesses do not and therefore turn to 3rd party developers to complete this task. However, things are not as simple as taking your source code and data to another software developer and asking them to deploy it for you.

To swiftly and accurately redeploy your application in the event of a release you need to have first performed validation testing on the source code deposit. At SES we recommend Remote Code Validation testing. This validation test involves the Software Developer (Licensor) rebuilding the application in their own environment whilst an SES testing consultant witnesses the full rebuild of the application via a secure remote connection and documents the entire process. (This process can also be completed with the SES testing consultant on-site at the Licensors premises if required).

The independent report compiled by the SES testing consultant coupled with the audio and visual recording of the build enables you or a third party to accurately redeploy your software application in the event of a release.

With the build guide accompanying the source code and data, a 3rd party developer should have everything they need to follow the instructions provided by the validation exercise and redeploy your application on your behalf.

However, this takes time

Time is a luxury most businesses do not have when their critical software applications are either no longer accessible. To make things easier and ensure your application can be deployed as quickly and accurately, SES has developed a SaaS continuity service called the Licensee Continuity Plan (LCP) agreement.  

SES's LCP provides a real-time Interim Release that bridges the gap between initiating the release process and its completion. Upon receipt of a release request, SES can switch on the Interim Release and provide the software user with continued access to their services, in some cases within minutes. This protects the software user and ensures the business can continue to operate without disruption until the release process finalises. The LCP will set out the timeframe for operating the Interim Release and once the release has been confirmed the Licensee Continuity Plan would become fully operational.

If you have concerns about the redeployment of your critical applications and would like to discuss the details of your business continuity plan or speak to us about our LCP agreement, please click here to speak to one of our specialists.

© SES Secure Limited and ses-escrow.co.uk, 2021. Unauthorised use and/or duplication of this material without express and written permission from this site’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to SES Secure Limited and ses-escrow.co.uk, with appropriate and specific direction to the original content