Risk
10/17/2010
07:48 PM
George V. Hulme
George V. Hulme
Commentary
Connect Directly
RSS
E-Mail
50%
50%

CloudAudit Now Under Cloud Security Alliance Umbrella

We've blogged often about the need for organizations to be able to see and understand the regulatory compliance and security efforts of their cloud providers. Now, two organizations - the Cloud Security Alliance and CloudAudit - that have been working toward exactly that are joining forces.

We've blogged often about the need for organizations to be able to see and understand the regulatory compliance and security efforts of their cloud providers. Now, two organizations - the Cloud Security Alliance and CloudAudit - that have been working toward exactly that are joining forces.Not being able to assess and validate, or even accurate compare, security efforts within public and managed private cloud computing models is one of the biggest knocks many models of cloud computing. We covered some of the reasons why previously:

Not being able to assess and validate compliance and security efforts within various cloud computing models is one of the biggest challenges cloud computing now faces. First, when a business tries to query a cloud provider, there may be lots of misunderstanding about what is really being asked for. For instance, when a business asks if the provider conducts periodic vulnerability assessments, and the provider responds affirmative they could be acknowledging an annual review, a quarterly review, or a daily vulnerability assessment. Perhaps they check yes when really all they perform is an annual penetration test. Too much ambiguity.

Additionally, cloud providers can't spend all of their time fielding questions about how they manage their infrastructure. And, regrettably, not many public cloud providers offer much transparency into their controls. And no, SAS 70 audits don't really account for much of anything when it comes to security.

As we noted in that post CloudAudit.org, has emerged with what it hopes will be part of the solution. The group is developing a common way for cloud computing providers to automate how their services can be audited and assessed and assertions provided on their environment for Infrastructure-, Platform-, and Software-as-a-Service providers.

This weekend it was announced that Cloud Audit has become part of the broader Cloud Security Alliance efforts:

Jim Reavis of the CSA and I are excited to announce that CloudAudit is now an official project of the Cloud Security Alliance! The CloudAudit working group's activities will now fall under the organizational and administrative auspices of the CSA. The M.O.U. was signed at a meeting during RSA Europe after discussions 
held previously amongst available available participating members. The reason for moving CloudAudit under the CSA are simple:

1) The CSA enjoys a well-balanced membership of volunteers from the 
enterprise, service providers and industry 
2) Most of the CloudAudit leadership are also key team members of the 
CSA 
3) CloudAudit's namespaces & CompliancePacks are all derived from the 
CSA's Cloud Control Matrix 
4) A single licensing scheme and roadmap simplifies both 
organizations' needs 
5) The CSA's other initiatives (CAI, TCI, etc) all align with 
CloudAudit and will enjoy a tighter coupling 
6) The CSA has the infrastructure and organizational membership needed 
to drive CloudAudit.

The working group's objectives and structure will likely not change 
but we'll enjoy greater coverage, exposure,
involvement and focus from the community.

I see this as great news for CloudAudit and am happy to see the effort has found a home with the Cloud Security Alliance. It makes a lot of sense to see the two unified, and CloudAudit now part of CSA could mean even broader adoption for the burgeoning standard.

For my security and technology observations throughout the day, find me on Twitter.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

CVE-2012-5487
Published: 2014-09-30
The sandbox whitelisting function (allowmodule.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote authenticated users with certain privileges to bypass the Python sandbox restriction and execute arbitrary Python code via vectors related to importing.

CVE-2012-5488
Published: 2014-09-30
python_scripts.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via a crafted URL, related to createObject.

CVE-2012-5489
Published: 2014-09-30
The App.Undo.UndoSupport.get_request_var_or_attr function in Zope before 2.12.21 and 3.13.x before 2.13.11, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote authenticated users to gain access to restricted attributes via unspecified vectors.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
In our next Dark Reading Radio broadcast, we’ll take a close look at some of the latest research and practices in application security.