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.

Comments
Why DevOps Fails At Application Security
Newest First  |  Oldest First  |  Threaded View
kwestrom
50%
50%
kwestrom,
User Rank: Apprentice
10/24/2015 | 3:24:21 PM
DevOps failing with Application Security
There were many good points raised with the article, and as pointed out, it's a mad rush to get the product with enough features out the door or to get it to market that security is often left out. Security should be built into the total time frame on an approximate 75% development total budgeted time, and around about 25% for the application security teams to look at it and root out the bugs in the code. As said, the developers are only looking at the code to put in features with seeing it only from a development standpoint/through development glasses, while the security team looks at it from the vulnerability viewpoint, and where the inherent weaknesses are hiding in the application. THe DevOps teams are too close to the application to see it from the vulnerability point of view to really do the job; however the bigger problem isn't with them, but the senior organizational management, such that until or unless the security of the produced products impacts the organizational financial bottomline, such as it is with the car/truck/vehicle makers, or the pharmaceutical industries, it won't happen.  THe software development application businesses have been enjoying a freedom from having to do thorough testing of their applications up through this point, but they need to be held accountable for the consequences by the exploited vulnerabilities when it occurs. Legislation/regulatory standards (with significant penalties for the weaknesses-vulnerabilities to be incurred upon hacks), so need to be put into place for the senior management to actually think about and plan for  the necessity of having secure applications when they are released into the market place for the public. Without something of that sort to be done, no organizational senior management, Board, or especially the stockholders to care about any application other than to get it out the door so that money can be made for profit on the product. 
TejGandhi1986
50%
50%
TejGandhi1986,
User Rank: Apprentice
10/15/2015 | 8:03:02 AM
Devops fail application security
Shipping the product to market has always been a priority.Considering security concerns increases the schedule and budget however it is critical.A mindset shift towards security can achieve this purpose.

 

Stakeholders ,devops need to ennsure proper time allotment and budget allotment toward security,the consequences must be revealed of not introducing secuity in the code.

When the impact is known it will immediately ensure that security has taken into consideration.

 

https://ca.linkedin.com/pub/tej-gandhi/2b/a88/a10
Dave787
100%
0%
Dave787,
User Rank: Apprentice
10/14/2015 | 4:06:09 PM
Secure code has never been easier with this DevOps tool
Hey Julien –

Great article!

It really captured exactly what's not being discussed enough in the cybersecurity space. True data-centric security starts with the developer and the application-level.

Disclaimer: I work for a company called Crypteron. At Crypteron, we are intimately aware of the new challenges and responsibilities facing developers nowadays. Secure coding has long been too difficult, complex, time-consuming - and not really "secure."

 

 


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-43056
PUBLISHED: 2021-10-28
An issue was discovered in the Linux kernel for powerpc before 5.14.15. It allows a malicious KVM guest to crash the host, when the host is running on Power8, due to an arch/powerpc/kvm/book3s_hv_rmhandlers.S implementation bug in the handling of the SRR1 register values.
CVE-2021-43057
PUBLISHED: 2021-10-28
An issue was discovered in the Linux kernel before 5.14.8. A use-after-free in selinux_ptrace_traceme (aka the SELinux handler for PTRACE_TRACEME) could be used by local attackers to cause memory corruption and escalate privileges, aka CID-a3727a8bac0a. This occurs because of an attempt to access th...
CVE-2021-3904
PUBLISHED: 2021-10-27
grav is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE-2021-3906
PUBLISHED: 2021-10-27
bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type
CVE-2021-3903
PUBLISHED: 2021-10-27
vim is vulnerable to Heap-based Buffer Overflow