Cloud

10/24/2017
10:10 AM
50%
50%

One-Third of Businesses Can't Keep Up with Cloud Security

One in three organizations cannot maintain security as cloud and container environments expand.

The growth of cloud and container environments is causing major problems for one-third of organizations who report they cannot keep up with changes in customers' security and compliance requirements.

Threat Stack and the Enterprise Strategy Group partnered to explore cloud security challenges in their "Cloud Security Report 2017: Security at Speed and Scale." They found 57% of 167 respondents report "significant delays" in sales due to trouble meeting customers' security standards, and 59% have the same problem with customers' compliance requirements.

Businesses' mounting concerns are not impeding container adoption, however: More than 40% have deployed containerized product applications, and 45% intend to test or deploy within the next year. Nearly all (94%) say containerization has a negative impact on security.

Researchers found hybrid environments are becoming more popular. Sixty percent of respondents plan to use a single cloud provider "for the foreseeable future" and 40% say they will have hybrid environments within twelve months.

Read more details here.

Join Dark Reading LIVE for two days of practical cyber defense discussions. Learn from the industry’s most knowledgeable IT security experts. Check out the INsecurity agenda here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:35:12 AM
Container and data Security
 

Data has to be encrypted in all cases, so containers do not really pose any additional risks to the data.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:34:37 AM
Re: Containers
" nowadays network proximity is a major factor."That is true, this may increase Inshoring. I also think network proximity will be covered in another way such a WAN optimization.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:31:42 AM
Re: Containers
" Tech Empire of the World - Bangalore - and cheaper-faster-better too.  "

Yes, I know a few friends who are working there. I see your point tough.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:29:58 AM
Re: Containers
"ill-informed execs make hasty purchasing and implementation decisions"

I would agree with this too. I would think it is because of the pressure in the market, everybody uses containers, let us use it too mentality. However I see benefits of containers for certain environment.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:27:32 AM
Re: Containers
" Rapidly jumping into the cloud is a poor choice"

I would agree with that. There has to be proper mechanism in place for bot security and stability point of view.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:26:17 AM
Re: Containers
"I'm curious to what extent this is inherent to containerization and to what extent it's a more a matter of complexity and lack of diligence."

Agree. I am not getting this part either.
Dr.T
50%
50%
Dr.T,
User Rank: Ninja
10/26/2017 | 11:24:56 AM
Container Security
There is no reason why containers should be unsecure if implemented properly. Security has to be put in place before it comes to the container, nothing different than how you would secure a virtual machine.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/26/2017 | 8:23:55 AM
Re: Containers
Interestingly, the trend to digital transformation may help to reverse the offshoring trend because nowadays network proximity is a major factor.

But then, even if that's so, expect it to re-reverse as more service-provider and content-delivery network gateways proliferate globally.
REISEN1955
50%
50%
REISEN1955,
User Rank: Ninja
10/25/2017 | 10:43:06 AM
Re: Containers
And do not forget the additional layer of complexity that American management believes that ALL IT issues can be managed from the Tech Empire of the World - Bangalore - and cheaper-faster-better too.  
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
10/25/2017 | 9:30:36 AM
Re: Containers
Indeed. The tech specifics may be different, but things haven't changed much over the decades. Enterprise technologies get hyped, ill-informed execs make hasty purchasing and implementation decisions, and then fundamentals at the orchestration layer suffer.
Page 1 / 2   >   >>
White House Cybersecurity Strategy at a Crossroads
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/17/2018
Lessons from My Strange Journey into InfoSec
Lysa Myers, Security Researcher, ESET,  7/12/2018
What's Cooking With Caleb Sima
Kelly Jackson Higgins, Executive Editor at Dark Reading,  7/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-14339
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the MMSE dissector could go into an infinite loop. This was addressed in epan/proto.c by adding offset and length validation.
CVE-2018-14340
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, dissectors that support zlib decompression could crash. This was addressed in epan/tvbuff_zlib.c by rejecting negative lengths to avoid a buffer over-read.
CVE-2018-14341
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the DICOM dissector could go into a large or infinite loop. This was addressed in epan/dissectors/packet-dcm.c by preventing an offset overflow.
CVE-2018-14342
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the BGP protocol dissector could go into a large loop. This was addressed in epan/dissectors/packet-bgp.c by validating Path Attribute lengths.
CVE-2018-14343
PUBLISHED: 2018-07-19
In Wireshark 2.6.0 to 2.6.1, 2.4.0 to 2.4.7, and 2.2.0 to 2.2.15, the ASN.1 BER dissector could crash. This was addressed in epan/dissectors/packet-ber.c by ensuring that length values do not exceed the maximum signed integer.