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
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
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
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
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-33085
PUBLISHED: 2022-06-30
ESPCMS P8 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the fetch_filename function at \espcms_public\espcms_templates\ESPCMS_Templates.
CVE-2022-33087
PUBLISHED: 2022-06-30
A stack overflow in the function DM_ In fillobjbystr() of TP-Link Archer C50&A5(US)_V5_200407 allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.
CVE-2022-31115
PUBLISHED: 2022-06-30
opensearch-ruby is a community-driven, open source fork of elasticsearch-ruby. In versions prior to 2.0.1 the ruby `YAML.load` function was used instead of `YAML.safe_load`. As a result opensearch-ruby 2.0.0 and prior can lead to unsafe deserialization using YAML.load if the response is of type YAML...
CVE-2022-33082
PUBLISHED: 2022-06-30
An issue in the AST parser (ast/compile.go) of Open Policy Agent v0.10.2 allows attackers to cause a Denial of Service (DoS) via a crafted input.
CVE-2013-5683
PUBLISHED: 2022-06-30
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2013. Notes: none.