ARL Logo
Risky Thinking
– On Risk Assessment, Risk Management, and Business Continuity
 
Risky Thinking
Home Page
BCP Training & Seminars
BCP Consulting
BCP Software
Risk/BCP Articles
Newsletter
Risky Blog
Risk/BCP Glossary
BCP Tools
Risk Resources
Older Articles
Article RSS Feed
About Us
Michael Z. Bell
Contact Info


 

 

Software Escrow Agreement (Definition)

Method of protecting against software vendor failure. A copy of the vendor's source code is kept by a trusted third party to ensure that the customer will have access to the source code in the event that the vendor is unable to support the software. If, for example, the vendor goes out of business, the trusted third party releases the source code to the customer, allowing the customer to maintain the software.

Note that even with a software escrow agreement, for older pieces of software it may not be possible to find a developer with the skills or resources to modify or maintain the software. The tools required to rebuild the software package may themselves be obsolete, or the additional packages required may no longer be available due to failure of the vendor's suppliers.

Risky Thinking Newsletter

Are you responsible for Business Continuity, Disaster Recovery, or Risk Management in your organization? Then you may wish to receive a free subscription to the the monthly Risky Thinking Newsletter. It contains news, opinions and articles of interest to people working in these areas.

View a sample issue, or click here to subscribe.

Recent articles have included:

A question that is often asked when designing a disaster recovery plan is how far away a hot site or mirror site should be. Is there a simple answer? Read more...

You're welcome to use these defintions for any purpose provided that an acknowledgement is made to www.riskythinking.com and (if you're using HTML) you provide a link back to this site.

[ Up to Risk Glossary ]

© Albion Research Ltd. 2010