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

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.
4 of 7

Make Big Security Gains with Policy as Code 

In the DevOps world, the biggest gains have been achieved through an 'everything-as-code' approach that has made it so much easier to spin up and down reliable, repeatable infrastructure components. In the future this could be a huge boon for security and compliance purposes, but right now there's a big gap between DevOps and security teams, says Tim Hinrichs, CTO and co-founder of Styra.

'This is particularly the case when audit time rolls around; auditors often have to be manually walked through security practices in containerized environments,' he says.

Hinrichs believes that teams should be seeking to adopt policy-based controls that are manifested in a policy-as-code format to help 'eliminate manual code reviews, ease compliance efforts, and eliminate process bottlenecks.' 

Sid Phadkar, a senior product manager at Akamai, agrees that many organizations are going to be building security policies directly within code to help deal with big compliance demands set upon them by regulations like GDPR.

'There will be an uptick in DevOps tools that cater to automating more compliance-related tasks within infosec teams, thus incorporating security and compliance measures into everyday CI workflows,' Phadkar says.

This will not only be a boon for compliance but also to generally ease security automation and container orchestration, says Glen Kosaka, vice president of product at NeuVector, explaining that DevSecOps teams should be looking to set security policies for 'any and all workload deployments' through YAML files.

'Security 'policy as code' -- and, overall, easier security automation -- will change how DevSecOps teams approach container security in 2020,' Kosaka says. Expect this evolution of more efficient and automated security integration processes to be a particularly welcome change for DevOps next year.

Image Source: Adobe (joyfotoliakid)

Make Big Security Gains with Policy as Code

In the DevOps world, the biggest gains have been achieved through an "everything-as-code" approach that has made it so much easier to spin up and down reliable, repeatable infrastructure components. In the future this could be a huge boon for security and compliance purposes, but right now there's a big gap between DevOps and security teams, says Tim Hinrichs, CTO and co-founder of Styra.

"This is particularly the case when audit time rolls around; auditors often have to be manually walked through security practices in containerized environments," he says.

Hinrichs believes that teams should be seeking to adopt policy-based controls that are manifested in a policy-as-code format to help "eliminate manual code reviews, ease compliance efforts, and eliminate process bottlenecks."

Sid Phadkar, a senior product manager at Akamai, agrees that many organizations are going to be building security policies directly within code to help deal with big compliance demands set upon them by regulations like GDPR.

"There will be an uptick in DevOps tools that cater to automating more compliance-related tasks within infosec teams, thus incorporating security and compliance measures into everyday CI workflows," Phadkar says.

This will not only be a boon for compliance but also to generally ease security automation and container orchestration, says Glen Kosaka, vice president of product at NeuVector, explaining that DevSecOps teams should be looking to set security policies for "any and all workload deployments" through YAML files.

"Security 'policy as code' -- and, overall, easier security automation -- will change how DevSecOps teams approach container security in 2020," Kosaka says. Expect this evolution of more efficient and automated security integration processes to be a particularly welcome change for DevOps next year.

Image Source: Adobe (joyfotoliakid)

4 of 7
Comment  | 
Print  | 
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-16632
PUBLISHED: 2021-05-15
A XSS Vulnerability in /uploads/dede/action_search.php in DedeCMS V5.7 SP2 allows an authenticated user to execute remote arbitrary code via the keyword parameter.
CVE-2021-32073
PUBLISHED: 2021-05-15
DedeCMS V5.7 SP2 contains a CSRF vulnerability that allows a remote attacker to send a malicious request to to the web manager allowing remote code execution.
CVE-2021-33033
PUBLISHED: 2021-05-14
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
CVE-2021-33034
PUBLISHED: 2021-05-14
In the Linux kernel before 5.12.4, net/bluetooth/hci_event.c has a use-after-free when destroying an hci_chan, aka CID-5c4c8c954409. This leads to writing an arbitrary value.
CVE-2019-25044
PUBLISHED: 2021-05-14
The block subsystem in the Linux kernel before 5.2 has a use-after-free that can lead to arbitrary code execution in the kernel context and privilege escalation, aka CID-c3e2219216c9. This is related to blk_mq_free_rqs and blk_cleanup_queue.