The first officially published work from the recently formed Cloud Security Aliance – Security as a Service (SecaaS) working group has been published. This is a great first step as we have identified the key categories of service that can / will make up security as a service.
This document can be found here;
I’m personally very proud of this work as I am the co-chair for the Security as a Service working group which has meant bringing together input from multiple streams of expersts working from many global locations and different time zones. I have also had to arbitrate any disagreements around content and ensure all experts who wanted to participate were able to provide their input.
In addition to the coordinating the various inputs and running steering meetings I also provided input into various categories where extra detail was required and also wrote most of one category that wasn’t picked up by the various experts who volunteered to help.
Our next steps are to to be finalised but they are likely to include;
– Finalising the version of the document that will be put forward towards an ISO standard
– Working on getting SecaaS added as the 14th domain of the official Cloud Security Alliance guidance
– Creating implementation guidance and examples for those looking to implement various SecaaS solutions
Watch this space and / or check in on the Cloud Security Alliance web site for progress updates.
We are currently in phase one of producing the Security as a Service guidance documentation;
– Agreeing and documenting categories of service and their definitions
– Agreeing and documenting categories of threats and their definitions
So far the top five categories of service are;
- Secure Web Gateway
- Vulnerability Assessments
- Pen Testing
- Intrusion Detection
- Log Management
With several further categories in the mix. We will be looking to consolidate the above categories and the others identified into sensible easy to understand groupings. For example it is likely that ‘vulnerability assessment’ and ‘pen testing’ will be a single category.
The top categories of threat identified are currently;
- Data Loss Leakage
- Traffic Hijacking
- Unauthorized Access
- Denial of Service
- Application Vulnerabilities
With about forty further ideas being assessed in the same way as for categories of service.
Should you have any ideas please do let me know either by posting a comment on this blog or by mailing me on LinkedIn, any assistance is greatly welcomed!
An overview of the Cloud Security as a Service (SecaaS) working group goals, outputs and proposed timeline was presented at the RSA conference on the 14th of February. His has been recorded for prosperity and uploaded to YouTube. The presentation can be found here;
This gives a great update on one of the things I’ll be working on during the next few months. Check the video out, fell free to ask me any questions you have, and of course if interested get involved and provide feedback via the surveys mentioned in the presentation.
For those interested in cloud security options, I am currently on the steering committee for the Security as a Service (SecaaS) working group. In this instance I mean how cloud computing can be used to secure everything, including cloud and non cloud based IT, rather than how to secure cloud computing (paraphrased from Jim Reavis).
If you are not familiar with the Cloud Security Alliance I suggest you check out their site, it is a great resource for all things cloud security related and can be found here;
The purpose of the specific SecaaS working group is to;
– Identify consensus definitions of what security as a Service means
– Categorise the different types of Security as a Service
– Provide guidance to organisations on reasonable implementation practices
The site specific to the SecaaS work can be found here;
Proposed timelines for the work we produce are for;
– Categories of service to be defined by late April.
– Draft SecaaS Guidance, mid-May.
– SME Guide, mid-July.
– Final Draft SecaaS Guidance, mid-September.
This should be a great piece of work so I will keep you updated with our progress.