Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

7/2/2014
03:15 PM
John Klossner
John Klossner
Cartoon Contest
100%
0%

Cartoon: Cloud Conundrum

John Klossner has been drawing technology cartoons for more than 15 years. His work regularly appears in Computerworld and Federal Computer Week. His illustrations and cartoons have also been published in The New Yorker, Barron's, and The Wall Street Journal. Web site: ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
7/8/2014 | 10:52:07 AM
SOC v CSP: Chicken or the egg?
The chicken or the egg metaphor is a great analogy for the cloud security debate. So I ask you all, when it comes to cloud security, who's bears the greatest resposible? the CSP or the SOC team? 
aws0513
100%
0%
aws0513,
User Rank: Ninja
7/8/2014 | 12:45:09 PM
Re: SOC v CSP: Chicken or the egg?
In my experiences, the following rule always applies:

"The data owner is responsible for protecting the data they manage and use for their business operations."

This means that no matter where the data is stored, the data owner must ensure that necessary security controls are in place to help protect the data.  If the choice is to use cloud services of any kind, they data owner must validate (accredit) and audit the cloud services that will be utilized... on a consistent and continuous basis.

The hard part is that cloud services often tout their product as a secure environment without providing security control implementation specifics.  I have yet to see any cloud service provide a security control "mapping" to NIST (or other framework) controls in detail that was sufficient.  They will brush some sales lines on a few common security controls, but I am still waiting on that "comprehensive" security control implementation documentation.

I am currently working with my employer (government entity) to establish a common security requirement "checklist" approach to cloud services assessment.  We plan to tell data owners within the organization that if a cloud service is going to be used for any solution our organization establishes, the service will be reviewed as if it were an extension of the organization and subject to the same auditing requirements.  In general, for us this means that NIST controls will need to be mapped to the cloud service equivalent where applicable.  The cloud service vendor(s) will need to provide an acceptable control implementation/solution for each required control that our risk assessment team (management) has deemed necessary to protect the data.  If there are any issues with how the cloud service supports or provides a specific controls, along with how they will be audited and monitored, they will likely not get any of our business unless our management can establish compensating controls or assume ownership of the control requirement.  Risk acceptance is a reality as well, but it is our hope that we can reduce the risk on all points possible before any risk acceptance takes place.

I know that what we are trying to do will very likely make things difficult for cloud service vendors to get our business, but the glaring fact is if there is an unauthorized breach of our data environments, all the finger pointing in the world would not take my employers name out of the newspapers and very likely will not protect my employer from legal filings unless the risk assumption is fully documented in the contract with the vendor.  Even if the contract is specificially established, my employer would still get a black eye in the reputation arena.

So...  big foot stomping hint to you cloud vendors out there.... Make it easier for organizations that handle sensitive or regulatory affected data to know EXACTLY how security controls are implemented in your environments...  from the physical to the virtual.  A to Z...  top to bottom.  And be prepared to provide auditing capabilities that are verifiable via 3rd party were necessary. 
I suggest NIST SP800-53 as a starting point.  Be ready to talk to other risk management frameworks (ISO anyone?). 
And NO...  a fancy letter from an external auditing firm does not come close to acceptable.  The devil is in the details...  so break out all the details as much as possible for your potential customers.  You want extra points?  Provide verifiable case documentation of security events that your environment identified and/or thwarted.  Full disclosure is a good thing!!
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
7/8/2014 | 4:59:55 PM
Re: SOC v CSP: Chicken or the egg?
Thanks for your thoughtful and detailed reply @aws0513. I hope you will tell us how your checklist approach works to cloud services assessment works. When do you thnk you will see some results?
Kelly Jackson Higgins
50%
50%
Kelly Jackson Higgins,
User Rank: Strategist
7/10/2014 | 4:29:24 PM
Re: SOC v CSP: Chicken or the egg?
This actually applies to a lot of things in security, so it's a wise joke well-taken. 
freespiritny25
50%
50%
freespiritny25,
User Rank: Apprentice
8/1/2014 | 4:24:57 PM
Re: Cartoon: Cloud Conundrum
LOL so true- pointing the blame!
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
CVE-2019-5254
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...