Gartner: SaaS Contracts Need More Transparency to Improve Risk Management

Software as a Service (SaaS) contracts often have ambiguous terms regarding the maintenance of data confidentiality, data integrity and recovery after a data loss incident, according to Gartner, Inc. This leads to dissatisfaction among cloud services users. It also makes it harder for cloud service providers to manage risk and defend their risk position to auditors and regulators. 

saas-solutions
Alexa Bona, vice president and analyst at Gartner

Gartner said that, through 2015, 80 percent of IT procurement professionals will remain dissatisfied with SaaS contract language and protections that relate to security. “We continue to see frustration among cloud services users over the form and degree of transparency they are able to obtain from prospective and current service providers,” said Alexa Bona, vice president and distinguished analyst at Gartner.

Cloud Control Objectives

At a minimum, cloud services users need to ensure that SaaS contracts allow for an annual security audit and certification by a third party, with an option to terminate the agreement in the event of a security breach if the provider fails on any material measure. In addition, it is reasonable for cloud service buyers to ask a provider to respond to the findings of assessment tools.

The Cloud Security Alliance (CSA), for example, has a Cloud Controls Matrix in the form of a spreadsheet containing control objectives deemed by participants in the CSA to be important for cloud computing. “As more buyers demand it, and as the standards mature, it will become increasingly common practice to perform assessments in a variety of ways, including reviewing responses to a questionnaire, reviewing third-party audit statements, conducting an on-site audits and/or monitoring the cloud services provider,” said Ms. Bona.

Furthermore, cloud users should not assume that SaaS contracts include adequate service levels for security and recovery. “Whatever term is used to describe the specifics of the service-level agreement (SLA), IT procurement professionals expecting their data to be protected from attack, or to be restorable in case of an incident, must ensure their providers are contractually obligated to meet those expectations,” said Ms. Bona. “We recommend they also include recovery time and recovery point objectives and data integrity measures in the SLAs, with meaningful penalties if these are missed.”

Financial compensation, liability insurances…

The lack of meaningful financial compensation for losses of security, service or data also represents an undesirable form of risk exposure in SaaS contracts. “SaaS is a one-to-many situation in which a single service provider failure could impact thousands of customers simultaneously, so it represents a significant form of portfolio risk for the provider,” said Ms. Bona. Therefore, the majority of cloud providers avoid contractual obligation for any form of compensation, other than providing service in kind or penalties in the event that they miss a service level in the contract. SaaS users should negotiate for 24 to 36 months of fee liability limits, rather than 12 months, and additional liability insurances, where possible.

Analysts will discuss costs and risks of cloud agreements at the 2013 Gartner IT Financial, Procurement & Asset Management Summits, September 11-12 in London and September 25-27 in Orlando, Florida.