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.

Application Security

1/2/2020
10:00 AM
Connect Directly
Twitter
RSS
E-Mail
100%
0%

6 Security Team Goals for DevSecOps in 2020

Huge opportunities await security teams that are finally ready move the needle on security problems that have plagued organizations for years.
Previous
1 of 7
Next

Image Source: Adobe (ASDF)

Image Source: Adobe (ASDF)

The world of IT delivery is undergoing seismic shifts as enterprises transform their technology infrastructure and software delivery models to stay ahead of market trends. This has driven rapid adoption of DevOps practices, cloud-native technology, containers, microservices, and rampant dependency on APIs and third-party code.
 
These changes, in turn, are blurring lines in infrastructure, in code, and in IT roles, all of which are completely disrupting the security function today. But for those security teams willing to stay flexible, it's also opening up huge opportunities to finally move the needle on security problems that have plagued organizations for years.
 
The demand for cloud-native apps and widespread adoption of DevOps to drive digital transformation is going to definitely "accelerate vulnerability risk" in 2020, says Rohit Ghai, president of RSA. But at the same time, he believes security teams that adapt with a DevSecOps model, baking security into the software pipeline, along with improvements in automation, will lead to huge strides in software security and security operations.
 
"It will enable pen testing and code analysis earlier in the development life cycle, and cyber-resilience to be designed into the fabric of the infrastructure, which will result in reduction of the attack surface," he explains.
 
In order to make this a reality, security and DevOps pundits believe organizations need to keep the following goals in mind for the coming year.

 

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio

Previous
1 of 7
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
SEODan
100%
0%
SEODan,
User Rank: Apprentice
1/17/2020 | 5:31:04 AM
Thanks Mrs Chickowski
Thank you Mrs Chickowski for these great slideshows
Cybersecurity Industry: It's Time to Stop the Victim Blame Game
Jessica Smith, Senior Vice President, The Crypsis Group,  2/25/2020
Google Adds More Security Features Via Chronicle Division
Robert Lemos, Contributing Writer,  2/25/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
6 Emerging Cyber Threats That Enterprises Face in 2020
This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-9431
PUBLISHED: 2020-02-27
In Wireshark 3.2.0 to 3.2.1, 3.0.0 to 3.0.8, and 2.6.0 to 2.6.14, the LTE RRC dissector could leak memory. This was addressed in epan/dissectors/packet-lte-rrc.c by adjusting certain append operations.
CVE-2020-9432
PUBLISHED: 2020-02-27
openssl_x509_check_host in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9433
PUBLISHED: 2020-02-27
openssl_x509_check_email in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-9434
PUBLISHED: 2020-02-27
openssl_x509_check_ip_asc in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.
CVE-2020-6383
PUBLISHED: 2020-02-27
Type confusion in V8 in Google Chrome prior to 80.0.3987.116 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.