Comments
Security vs. Speed: The Risk of Rushing to the Cloud
Newest First  |  Oldest First  |  Threaded View
REISEN1955
100%
0%
REISEN1955,
User Rank: Ninja
2/14/2018 | 1:37:11 PM
Re: Not safe
Woz - our great ancient savant from Apple - stated flat out that there is no security in the cloud.  That said, the cloud is - at most base - just a longer RJ-45 or optic cable from your endpooint to another server somewhere in the world hosted by god knows who.  The cloud has to reside on something somewhere and adding layers of exposure on top of your own protection increases risk many times over.   Not to add too that another set of human hands on a distant keyboard working with your data as an unknown too.

No safety in the cloud - it is a snake oil pitch worthy of W.C. Fields
Alsec
50%
50%
Alsec,
User Rank: Apprentice
2/9/2018 | 6:20:26 AM
Re: Not safe
Thumbs up. I totally agree.
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
2/7/2018 | 7:34:27 PM
Re: Not safe
As with all optimization choices, it depends on your priorities.  For many use-cases, the hybrid-cloud model provides the best balance of security vs. cost tradeoffs.  As other commenters have mentioned, the physical location of the public-cloud assets can have important security implications.  Most important is which of your organization's data assets you trust to the public-cloud, and which do you keep within your own perimeter.  Start there; then evaluate public-cloud vendors/services. 
nosmo_king
50%
50%
nosmo_king,
User Rank: Strategist
2/7/2018 | 10:14:59 AM
Re: Not safe
I am sorry you feel that way, I know it can be overwhelming at times and I have felt that pain.

It is possible to use cloud services safely, when thought and care are woven into the decision-making process from the very start, not least of all determining what services and data are eligible to be shipped to the cloud and which must stay within the enterprise.

If the course of technology has taught us anything it is that over a shortish period of time the market will consolidate into fewer potential suppliers and the less than spectacular ones will go out of business relatively quickly.

Don't throw the metaphoric baby out with the bathwater just yet.
nosmo_king
100%
0%
nosmo_king,
User Rank: Strategist
2/7/2018 | 10:06:26 AM
Understanding the kill chain is a key part of due diligence
When selecting a SaaS provider it amazes me how infrequently someone thinks to ask the provider who supplies their platform, their infrstructure and their support services.

It is not very often that a second-tier or lower SaaS provider houses their own servers, does their own maintenance and backups, or provides their own customer support.

These are usually spread out to multiple providers, and understanding who they are and who provides service to them must be a part of security due diligence. You have to know where your data is going to end up and who will have what level of access to it.

While the initial supplier may do and say all the right things in regard to security and privacy, it is necessary to go through the whole chain of suppliers to determine the complete truth.
aumickmanuela
100%
0%
aumickmanuela,
User Rank: Strategist
2/7/2018 | 9:56:31 AM
Not safe
Yeah, i can tottaly agree with your tips, you are right) Cloud is not safe at all 


Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Australian Teen Hacked Apple Network
Dark Reading Staff 8/17/2018
Data Privacy Careers Are Helping to Close the IT Gender Gap
Dana Simberkoff, Chief Risk, Privacy, and Information Security Officer, AvePoint, Inc.,  8/20/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-17305
PUBLISHED: 2018-08-21
Some Huawei Firewall products USG2205BSR V300R001C10SPC600; USG2220BSR V300R001C00; USG5120BSR V300R001C00; USG5150BSR V300R001C00 have a Bleichenbacher Oracle vulnerability in the IPSEC IKEv1 implementations. Remote attackers can decrypt IPSEC tunnel ciphertext data by leveraging a Bleichenbacher R...
CVE-2017-17311
PUBLISHED: 2018-08-21
Some Huawei Firewall products USG2205BSR V300R001C10SPC600; USG2220BSR V300R001C00; USG5120BSR V300R001C00; USG5150BSR V300R001C00 have a DoS vulnerability in the IPSEC IKEv1 implementations of Huawei Firewall products. Due to improper handling of the malformed messages, an attacker may sent crafted...
CVE-2017-17312
PUBLISHED: 2018-08-21
Some Huawei Firewall products USG2205BSR V300R001C10SPC600; USG2220BSR V300R001C00; USG5120BSR V300R001C00; USG5150BSR V300R001C00 have a DoS vulnerability in the IPSEC IKEv1 implementations of Huawei Firewall products. Due to improper handling of the malformed messages, an attacker may sent crafted...
CVE-2018-12115
PUBLISHED: 2018-08-21
In all versions of Node.js prior to 6.14.4, 8.11.4 and 10.9.0 when used with UCS-2 encoding (recognized by Node.js under the names `'ucs2'`, `'ucs-2'`, `'utf16le'` and `'utf-16le'`), `Buffer#write()` can be abused to write outside of the bounds of a single `Buffer`. Writes that start from the second...
CVE-2018-7166
PUBLISHED: 2018-08-21
In all versions of Node.js 10 prior to 10.9.0, an argument processing flaw can cause `Buffer.alloc()` to return uninitialized memory. This method is intended to be safe and only return initialized, or cleared, memory. The third argument specifying `encoding` can be passed as a number, this is misint...