Risk

10/17/2010
07:48 PM
George V. Hulme
George V. Hulme
Commentary
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
Comments
Threaded  |  Newest First  |  Oldest First
5 Reasons the Cybersecurity Labor Shortfall Won't End Soon
Steve Morgan, Founder & CEO, Cybersecurity Ventures,  12/11/2017
BlueBorne Attack Highlights Flaws in Linux, IoT Security
Kelly Sheridan, Associate Editor, Dark Reading,  12/14/2017
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2017
A look at the biggest news stories (so far) of 2017 that shaped the cybersecurity landscape -- from Russian hacking, ransomware's coming-out party, and voting machine vulnerabilities to the massive data breach of credit-monitoring firm Equifax.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.