Category:OWASP CSA Project

Revision as of 14:35, 29 June 2009 by Jm04469 (talk | contribs)

Jump to: navigation, search

Last Updated: 6/25/2009

Mission of CSA_Project Collective To promote the use of best practices for providing security assurance within Cloud Computing, and provide education on the uses of Cloud Computing to help secure all other forms of computing

Primary Project Website:
Project leaders: Warren Axelrod & Michael Sutton

Version 1.0 Document: Get it Now and Additional CSA resources

Deadline for RFC July 8th 2009

If you would like to contribute to this effort as a OWASP voice of Industry/Projects you can and its VERY simple to get started.

Step #1 - Review V1.0

Step #2 - Condense your written comments, references for improvement and suggestions and review/post them to the WIKI - This location will be monitored by CSA for inclusion into Version 2.0

Step #3 - Add your name to the wiki page if you would like to work on this effort. The goal is to utilize the experts at OWASP to review and comment as a collective group and reference OWASP existing materials to help the CSA effort and to raise awareness to others about OWASP.


Tom Brennan/tomb(at)

Michael Coates/michael.coates(at)

Adam Muntner/Adam.Muntner(at)

Comments on the Domain 11: Application Security Page 65-71 (not limited to that domain BTW)

Page # Comment Your Name
4 Include OWASP member attribution and affiliation. The more names, the betterJames McGovern
27 PCI defines requirements above and beyond just payment processing. Challenges such as file integrity monitoring and patch management become more nebulous in a cloudJames McGovern
34 Additional considerations may include constructs such as receiving a document preservation notice where a court may order you to restore a system to a known point in time. The fluidity of a cloud makes this challengingJames McGovern
72 The second sentence of the Issuance and Guidance on page 72 is misleading and factually incorrect. "Encrypted data is intrinsically protected; if someone has the data without its corresponding keys, they cannot use the data at all." Encrypting data will guarantee that the data is not viewed or modified by a party that does not possess the corresponding keys. However, encrypted data can be used in reply attacks. As such, it is imperative that the transfer of encrypted data utzilize secure tokens and timestamps to ensure the transmission is not subject to replay attacks. The use of SSL/TLS for data transmission will provide both encryption of data and protection against replay attacks.Michael Coates
65The entire Domain 11, Application Security, seems to focus more on some minor architecture differences, but doesn't focus on acutal application level threats - XSS, CSRF, SQL etc injection attacks, and business logic holes such as authentication/authorization issues. Adam Muntner
65 "For application security, the answer to each of these questions has two: what

security controls must the application provide over and above the controls inherent in the cloud platform and how must an enterprise’s secure development lifecycle change to accommodate cloud computing?"

This is the only quote in the Problem Statement which is relevant. The rest can safely be scrubbed.
Adam Muntner
70 "Final Thoughts" section: Attack methods are well known. OWASP Testing Guide is one point of reference, and OSSTM is another. How will malicious actors react? By being malicious actors. A list of web links for further research would be more useful. Adam Muntner
13 Authentication mentioned - should refer to Authorization as well Adam Muntner
71 The OWASP Application Security Verification Standard, OWASP Enterprise Security API and OWASP Software Assurance Maturity Model should be added to the list of references Colin Watson
page# Comment Here Name here
page# Comment Here Name here
page# Comment Here Name here
page# Comment Here Name here
page# Comment Here Name here

Comments on the Domain 11: Application Security Page 65-71

Page # Comment Your Name


This category currently contains no pages or media.