Components of the SaaS escrow arrangement

Whatever arrangement you need, it consists of three components: escrow agreement, verification & deposit.
Consult on Escrow Arrangements

1. The escrow agreement (legal)

The escrow arrangement is the legal document in which you record all agreements made.

We release the materials that have been entrusted to us (the deposit) to the beneficiary or foundation if the software supplier can no longer guarantee the continuity of the software application. Then the agreements on temporary continuation of the services, which may have been agreed with the service provider, come into effect. We release the materials under strict conditions and based on verifiable facts that must be in accordance with the grounds for continuation from the escrow agreement.

Therefore:

  • the escrow agreement protects the continuity of the beneficiary
  • the strict control on the predetermined grounds for continuation also protect the continuity of the supplier

2. Technical verification (audit)

We verify the material deposited to ensure that software suppliers and users can be certain that the material is complete and functions correctly. We call this Technical Verification Service (TVS). We perform this at four levels (TVS Levels), depending on the situation and the requirements of the supplier and user.

TVS Level I – Integrity Verification

This basic verification is standard in our service offering; we perform it on every material submission. It is a basic verification, including a check on the integrity of the material. It provides assurance that the deposited material is, among other things, virus-free, accessible, and of the expected type.

TVS Level 2 – Material Audit

Dit is een basisverificatie, inclusief een audit op het materiaal dat in depot wordt gegeven.

  • We verifiëren onder meer door steekproeven (spotchecks) op het materiaal.
  • We verify that specific agreements regarding the material have been complied with.
  • We determine whether libraries or files are present.

TVS Level 3 – Full Verification

Full verification can demonstrate that the material deposited meets the stated continuity objectives of the escrow arrangement. An escrow for SaaS has different interpretations of the full verification, entirely dependent on the construction of the escrow for SaaS arrangement, where the main goal is always to check whether the deposited material meets the stated continuity objectives. For example, the verification can focus on the technical continuation of the application and hosting environment, the re-deployment of the application in another environment, the rebuilding of the application, up to and including a fallback similar to disaster recovery. A full verification can be compared to a fire drill — our verification consultant simulates the steps that are also taken in an escrow situation.

The scope of the full verification is discussed in advance with the parties involved and recorded in a project plan. This makes it clear to all parties which tests are carried out and what the expected results should be. In general, the full verification of SaaS is therefore customized and may include:

  • Is there access to the necessary servers and application environment?
  • Is there sufficient information and documentation available to continue the SaaS service?
  • Have sufficient (management) rights been granted to continue the SaaS service?
  • Can the application environment be rebuilt or deployed elsewhere?
  • Can the application be switched to the fallback environment?
  • Does the source code compile, among other things, based on the information included in the deposit?
  • Is there access to the necessary data?

    TVS-level 3 is carried out in the software lab of Escrow Alliance or, if necessary or desirable, at the location of the software supplier.

TVS Level 4 – Custom Verification

Custom verification is possible, such as:

  • testing software components
  • check how the software behaves in a complex environment
  • specific checks that apply to your situation

3. The deposit (secure storage)

The deposit (escrow deposit) consists of materials needed to ensure continuity if the supplier fails. The material must therefore contain everything to guarantee the desired continuity.

Consider:

  • Source code
  • Executables
  • Application
  • Virtualized machines (VMs)
  • Containers, such as Docker Container, for a quick deploy of the applications in your own environment
  • Data
  • (Access) data hosting/cloud services
  • Documentation reorganisation SaaS environment


With escrow for SaaS, the material therefore does not only consist of source code. In some cases, the source code does not even play a role.

How to submit?

We aim to make the submission of material as simple, efficient, and manageable as possible. Therefore, we consider the options available to the software supplier.

Submission can be done, for example, via:

  • secure FTP
  • various source code management systems such as GitLab, GitHub, Bitbucket
  • Cloud environments
  • a mix of delivery methods

Dual Storage

Escrow Alliance offers standard dual storage of material. This means that we store a copy of the deposit in a geographically separate location.  

Storage takes place in the Netherlands and can be:

  • physical, in specially equipped data vaults
  • electronic, on highly secure servers
  • both physical and electronic

 

The vaults are ISO 9001 and ISO 27001 certified, just like Escrow Alliance itself. Only authorized and screened personnel have access to the vaults.


What if Escrow Alliance ceases to exist?

In the escrow agreement, we standardly stipulate that the deposits will be returned to the supplier or transferred to a newly designated Escrow agent if Escrow Alliance unexpectedly fails. To fulfill this promise, the Foundation for Continuity and Guarantee Escrow Alliance (SCWEA) manages the vaults. The foundation has the right to return materials in that case.

What is the best fitting solution for your situation
?

Find out about the possibilities, we are happy to think along with you.