Difference between revisions of "Category:OWASP Cloud ‐ 10 Project"

Jump to: navigation, search
Line 143: Line 143:
[[:User:vinaykbansal|'''Vinay Bansal''']]
[[:User:vinaykbansal|'''Vinay Bansal''']]
<br>[[User:Shankar Babu Chebrolu|Shankar Babu Chebrolu]]
<br>[[User:Shankar Babu Chebrolu|Dr. Shankar Babu Chebrolu]]
<br>[[User:Pankaj Telang|Pankaj Telang]]
<br>[[User:Pankaj Telang|Pankaj Telang]]
<br>[http://www.owasp.org/index.php/User:Ken_Huang Ken Huang]
<br>[http://www.owasp.org/index.php/User:Ken_Huang Ken Huang]

Revision as of 13:01, 31 October 2010


Cloud Top 10 Security Risks


According to Gartner, by 2012, 20% of businesses will adopt cloud services and own no IT assets. Goal of the project is to maintain a list of top 10 security risks faced with the Cloud* Computing and SaaS Models. List will be maintained by input from community, security experts and security incidences at cloud/SaaS providers.

  • Most of the risks are based on the assumption that Cloud is a public or a hybrid cloud


Audience for the project will be organizations planning on leveraging external cloud environment to host their applications or rent application in a SaaS model (Software as a Service). Aim of the "OWASP Cloud-10" list is to help balance security risks with the cost advantage that the Cloud and SaaS model provides. We expect the Cloud and SaaS providers to be indirect audience for "OWASP Cloud-10", when they try to showcase their security controls to potential customers against this list.

Also refer the recent presentation - http://www.owasp.org/images/4/47/Cloud-Top10-Security-Risks.pdf

Initial pre-alpha list of OWASP Cloud Top 10 Security Risks

R1 - Accountability and Data Ownership A traditional data center of an organization is under complete control of that organization. The organization logically and physically protects the data it owns. An organization that chooses to use a public cloud for hosting its business service loses control of its data. This poses critical security risks that the organization needs to carefully consider and mitigate. (Pankaj, Vinay)
R2 - User Identity Federation It is very important for the enterprises to keep control over user identities as they move services and applications to the different cloud providers. Rather than letting cloud providers create multiple islands of identities that become too complex to manage down the line. Users should be uniquely identifiable with a federated authentication (e.g. SAML) that works across the cloud providers. User experience is enhanced when he/she does not manage multiple userids and credentials. This allows easier back-end data integrations between cloud provides. (Vinay, Pankaj)
R3 - Regulatory Compliance - Complex to Demonstrate regulatory compliance. Data that is perceived to be secure in one country may not be perceived secure in another due to different regulatory laws across countries or regions. For eg., European Union has very strict privacy laws and hence data stored in US may not comply with those EU laws. (Shankar, Ove)
R4 - Business Continuity and Resiliency Business Continuity is an activity an IT organization performs to ensure that the business can be conducted in a disaster situation. In case of an organization that uses cloud, the responsibility of business continuity gets delegated to the cloud provider. This creates a risk to the organization of not having appropriate business continuity. (Pankaj, Shankar)
R5 - User Privacy and Secondary Usage of Data User's personal data gets stored in the cloud as users start using social web sites. Most of the social sites are vague about how they will handle users personal data. Additionally most of the social sites go with the default share all (least restrictive) setup for the user. E.g. via LinkedIn, Twitter, Facebook it is very easy to deduct personal details of the users (Vinay) - Need to ensure with your cloud providers what data can or cannot be used by them for secondary purposes. It includes data that can be mined directly from user data by providers or indirectly based on user behavior (clicks, incoming outgoing URLs etc.). Many social application providers mine user data for secondary usage e.g. directed advertising. No wonder when many of us use their personal gmail/hotmail or yahoo account to tell a friend your vacation plans and immediately you start seeing advertisements on hotels/flights near your destination. (Vinay, Ove)
R6 - Service and Data Integration Organizations must be sure that their proprietary data is adequately protected as it is transferred between the end user and the cloud data center. While interception of data in transit should be of concern to every organization, the risk is much greater for organizations utilizing a cloud computing model, where data is transmitted over the Internet. Unsecured data is susceptible to interception and compromise during transmission. (Shankar, Ove)
R7 - Multi Tenancy and Physical Security Multi-tenancy in cloud means sharing of resources and services among multiple clients(CPU, networking, storage/databases, application stack). It increases dependence on logical segregation and other controls to ensure that one tenant deliberately or inadvertently can not interfere with the security ( confidentiality, integrity, availability) of the other tenants. (Vinay, Pankaj)
R8 - Incidence Analysis and Forensic Support In the event of a security incident, applications and services hosted at a cloud provider are difficult to investigate as logging may be distributed across multiple hosts and data centers which could be located in various countries and hence governed by different laws. Also, along with log files, data belonging to multiple customers may be co-located on the same hardware and storage devices and hence a concern for law enforcing agencies for forensic recovery. (Shankar, Ove)
R9 - Infrastructure Security All infrastructure must be hardened and configured securely, and the hardening/configuration baselines should be based on Industry Best Practices. Applications, systems and networks must be architected and configured with tiering and security zones, and access must be configured to only allow required network and application protocols. Administrative access must be role-based, and granted on a need-to-know basis. Regular risk assessments must be done, preferably by an independent party. A policy and process must be in place for patching/security updates, and can based on risk/threat assessments of new security issues. (Ove, Shankar)

Although the fine details of the items above must be regarded as highly sensitive information, it is reasonable to expect a customer to want to see at least the high-level details. The Provider must be willing to provide this.

R10 - Non Production Environment Exposure An IT organization that develops software applications internally employs a set of non-production environments for design, development, and test activities. The non-production environments are generally not secured to the same extent as the production environment. If an organization uses a cloud provider for such non-production environment, then there is a high risk of unauthorized access, information modification, and information theft. (Pankaj, Ove)
Table 1: Top 10 Cloud - Security Risks

Other OWASP Cloud-10 Candidates

  • exposure to non-prod and internal environments
  • Integration between cloud and internally hosted services
  • Patching and Vulnerability Management
  • Lack of Transparency in Internal Security Controls and difficulty/complexity of auditing
  • Enterprise Intranets exposed directly on Internet (if they move on a Public Cloud)

This needs to be debated and for each of these we may need to add a separate page-holder with the following details.

  • Various Risk Scenarios
  • Real World Examples
  • Possible Mitigation and Security Controls
  • Reference to any related Incident

Roadmap (Status)

Managing OWASP Cloud-10 List (Pre-Alpha)

“OWASP Cloud-10” list will be maintained by input from, community, security experts and security incidences at cloud/SaaS providers.

Each of the identified risk in "OWASP Cloud-10" will provide details on:

  • Various Risk Scenarios
  • Real World Examples
  • Possible Mitigations and Security Controls
  • Reference to any related Incident

Risk Criteria:

  1. Easily Executable
  2. Most Damaging
  3. Incidence Frequency (Known)

Alpha Release

  1. Identify and publish a first draft of potential "OWASP Cloud-10" candidates (Dec 2009)
  2. Ask contributors to collect more data and details on each of the risk item. (till Jan 2010)
  3. Get initial community feedback by discussing it in various blogs, discussion forums etc. (Jan-Feb 2010)

Beta Release

  1. Writeup to be finished by April 5th (All)
  2. Provide feedback by April 19th
  3. Incorporate all the comments feedback by 26th April
  4. Publish the first (beta) list of "OWASP Cloud-10" (April 3rd 2010)
  5. Identify additional candidates
  6. ……. (repeat steps as in Alpha)





Related Efforts

  1. Cloud Security Alliance - http://www.cloudsecurityalliance.org/
  2. IDC Aug 2008 Survey (Security #1) Challenge for Cloud/On-Demand Models - http://blogs.idc.com/ie/?p=210

Related OWASP Projects

  1. OWASP Top Ten Project
  2. OWASP Legal Project


Project Leaders

Vinay Bansal
Dr. Shankar Babu Chebrolu
Pankaj Telang
Ken Huang
Ove Hansen


  1. Subscribe or read the Cloud-10 mail archives

Project Details

What does this OWASP project offer you?
What does this OWASP project release offer you?
what is this project?
OWASP Cloud ‐ 10 Project

Purpose: Goal of the project is to maintain a list of top 10 security risks faced with the Cloud Computing and SaaS Models. List will be maintained by input from community, security experts and security incidences at cloud/SaaS providers.

License: N/A

who is working on this project?
Project Leader: Vinay Bansal @

Project Maintainer:

Project Contributor(s):

how can you learn more?
Project Pamphlet: N/A

3x slide Project Presentation: N/A

Mailing list: Subscribe or read the archives

Project Roadmap: To view, click here

Main links: N/A

Project Health: Yellow button.JPG Not Reviewed (Provisional)
To be reviewed under Assessment Criteria v2.0

Key Contacts
  • Contact Vinay Bansal @ to contribute, review or sponsor this project
  • Contact the GPC to report a problem or concern about this project or to update information.
current release
First Release - Unknown Date - (no download available)

Release Leader: N/A

Release details: Main links, release roadmap and assessment

Rating: Yellow button.JPG Not Reviewed
To be reviewed under Assessment Criteria v2.0