I look forward to discussing SaaS Contingency Planning in our upcoming webinar on Thursday, March 27, and hope you can join us.
Today, up to 85 percent of new software is being built for the cloud.* Yet, 79 percent of SaaS providers do not guarantee application continuity to their subscribers.**
With Software-as-a-Service, or SaaS, there are many changes in how we need to prepare for the “what ifs” of software acquisition as compared to traditional on premises software.
Although a fair amount of due diligence goes into every technology decision, we often see a lot of maverick spending at the business unit level that bypasses the traditional contracting process. As a result, subscribers are exposing themselves to undue risk that would have otherwise been addressed by the risk managers supporting the Contracts and Legal team. In any case, you should have a protection plan in place for your SaaS applications and data.
SaaS subscribers can face issues such as:
Sudden cessation of their SaaS providers’ business
Bankruptcy claims by their SaaS provider
Mergers or acquisitions involving the SaaS provider, with risks of “sun-setting” current products
Extended outages, and the provider’s ability to recover from them
Lack of access to their data, which is hosted in the cloud
To address these issues, a contingency plan should be put in place before the deal gets signed, and the subscriber should be able to execute the contingency plan independent of the provider.
Because of the inherent risks of SaaS, companies often have difficulty entrusting critical business processes to the cloud without certain protections in place. Depending on the technology investment, availability of the service and the value placed on precious data, you need to perform the due diligence which includes a workable contingency plan.
Here are the details of the session:
Thursday, March 27 at 11:00 a.m. EDT
Click here to Register
I hope you can join this session, which will include a live Q&A session, to have your questions about SaaS contingency planning answered.