	Risky Thinking – On Risk Management, Disaster Recovery, and Business Continuity
Home / Risk Glossary / Software Escrow Agreement		12 May, 2008

Risky Thinking

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.

How far away should a hot site or mirror site be?
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? (More...)

The Risky Thinking Newsletter contains news, opinions and articles on Business Continuity, Disaster Recovery, and Risk Management. It's free for people working in the area. Click here to subscribe.

[ Up to Risk Glossary ]

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.