Page 12 - COSO Guidance Book

4 | Enterprise Risk Management for Cloud Computing | Thought Leadership in ERM

3. The Risks

As defined in COSO’s 2004 Enterprise Risk Management • Legally, third-party cloud service providers and their
– Integrated Framework : “Risk is the possibility that an customer organizations are distinct enterprises.
3
event will occur and adversely affect the achievement of However, if the CSP neglects or fails in its
objectives.” responsibilities, it could have legal liability implications
for the CSP’s customer organizations. But if a cloud
The types of risks (e.g., security, integrity, availability, customer organization fails in its responsibilities, it is
and performance) are the same with systems in the less likely there would be any legal implications
cloud as they are with non-cloud technology solutions. to the CSP.
An organization’s level of risk and risk profile will in most
cases change if cloud solutions are adopted (depending • Cloud service providers and their customer
on how and for what purpose the cloud solutions are organizations are likely to have separate enterprise
used). This is due to the increase or decrease in likelihood risk management (ERM) programs to address their
and impact with respect to the risk events (inherent and respective universe of perceived risks. Only in a
residual) associated with the CSP that has been engaged minority of cases (involving very high-dollar contracts)
for services. will CSPs attempt to integrate portions of their ERM
programs with those of their customers. The universe
Some of the typical risks associated with cloud computing are: of risks confronting an organization using third-party
cloud computing is a combination of risks the individual
• Disruptive force – Facilitating innovation (with increased organization faces along with a subset of the risks
speed) and the cost-savings aspects of cloud computing that its CSP is facing (discussed further in Section 5,
can themselves be viewed as risk events for some “Approaching ERM in the Cloud Computing Paradigm”).
organizations. By lowering the barriers of entry for new
competitors, cloud computing could threaten or disrupt • Lack of transparency – A CSP is unlikely to divulge
some business models, even rendering them obsolete detailed information about its processes, operations,
in the future. For example, streaming media over the controls, and methodologies. For instance, cloud
Internet was a technology solution that significantly customers have little insight into the storage location(s) of
reduced the sales of CDs and DVDs and the need for data, algorithms used by the CSP to provision or allocate
physical retail stores. Existing competitors that fully computing resources, the specific controls used to secure
embrace the cloud might be able to bring new ideas components of the cloud computing architecture, or how
and innovation into their markets faster. Since cloud customer data is segregated within the cloud.
computing solutions yield considerable short-term
cost savings due to reduced capital expenditures, an • Reliability and performance issues – System failure is a
organization adopting the cloud might be able to extract risk event that can occur in any computing environment
better margins than its non-cloud competitors. Thus, but poses unique challenges with cloud computing.
when an industry member adopts cloud solutions, other Although service-level agreements can be structured
organizations in the industry could be forced to follow to meet particular requirements, CSP solutions might
suit and adopt cloud computing. sometimes be unable to meet these performance metrics
if a cloud tenant or incident puts an unexpected resource
• Residing in the same risk ecosystem as the CSP and demand on the cloud infrastructure.
other tenants of the cloud – When an organization adopts
third-party-managed cloud solutions, new dependency • Vendor lock-in and lack of application portability or
relationships with the CSP are created with respect interoperability – Many CSPs offer application software
to legal liability, the risk universe, incident escalation, development tools with their cloud solutions. When these
incident response, and other areas. The actions of the tools are proprietary, they may create applications that
CSP and fellow cloud tenants can impact the organization work only within the CSP’s specific solution architecture.
in various ways. Consider the following: Consequently, these new applications (created by these
proprietary tools) might not work well with systems
residing outside of the cloud solution. In addition, the more
applications developed with these proprietary tools and the
more organizational data stored in a specific CSP’s cloud
solution, the more difficult it becomes to change providers.

3 COSO, Enterprise Risk Management – Integrated Framework, September 2004, page 16.

w w w . c o s o . o r g