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
What Drives A Developer To Use Security Tools -- Or Not
Newest First  |  Oldest First  |  Threaded View
Page 1 / 2   >   >>
Erik Klein
Erik Klein,
User Rank: Apprentice
9/24/2015 | 12:58:29 PM
What if the developer didn't need to USE a tool?
This article reports on the factors that influence a software developer to proactively stop the process of developing software, perform a context-switch, and execute a security tool ... steps that do not contribute to the functional deliverables of the SDLC.

Of course there would be pushback ... unless the developer is compensated for secure code.

But what if accurate application security vulnerabilities could be identified before code check-in without any of the steps mentioned above?  What if the applciation security vulnerabilities were identified simply from the FUNCTIONAL development and usage of the system?

As a former developer (and current AppSec tooling guy), I am always looking for ways to invisibly inject security into the SDLC ... ways that do NOT require a new line item in a project plan, an extra step in the coding / development process, or a self-imposed "wait state" in order to get application security results ... and, ideally, to have appication security vulnerabilities identified continuously and in real-time as an invisible and natural by-product of the process of building and testing software in an SDLC without regard for "Security Testing".

I have found that passive IAST products are capable of achieving this goal and not only enabling developers to identify and fix their vulnerabilities before the code leaves their desktop, but actually proactively reaching out to them to show the exact line of code that is vulnerable ... ALL WITHOUT A SCAN or extra step ... all in real-time from performing the very act that all developers do before checking in code ... FUNCTIONAL sanity/smoke testing.

Contrast Security provides such a solution.
Dr.T
Dr.T,
User Rank: Ninja
8/26/2015 | 4:07:40 PM
Re: Monkey see Monkey do
Comfortable medium is somewhere we keep the balance of CIA: Confidentiality, Integrity, Availability. If you push one side more than others it eventually causes other problems. Keep in mind that there will never be a "Secure" system.
Kelly Jackson Higgins
Kelly Jackson Higgins,
User Rank: Strategist
8/26/2015 | 4:07:25 PM
Re: Security makes it complex
Wow, @Dr. T. That's a shame. That says a lot about the problem. No one expects a dev to write perfect code--not possible--but if they had more support in writing more secure and better code, maybe they would find it challenging yet realistic.
Dr.T
Dr.T,
User Rank: Ninja
8/26/2015 | 4:05:12 PM
Re: Monkey see Monkey do
Psychological perspective security may not even really matter, we are all concern about privacy in most cases.
Dr.T
Dr.T,
User Rank: Ninja
8/26/2015 | 4:03:16 PM
Re: User-Experience
Agree. User experience may be important factor why some of our codes are not as secure as they could be.
Dr.T
Dr.T,
User Rank: Ninja
8/26/2015 | 4:01:57 PM
Re: Monkey see Monkey do
Money tests can really catch lost for security vulnerabilities that standard set of test action items.
Dr.T
Dr.T,
User Rank: Ninja
8/26/2015 | 3:59:46 PM
Security makes it complex

I know some of my developer friends stop doing development since they started thinking that it is getting harder and harder to write a code in secure way, so they just give up. :--))
RyanSepe
RyanSepe,
User Rank: Ninja
8/25/2015 | 11:47:22 AM
Re: Monkey see Monkey do
Very interesting. Looking at it from a psychological perspective it would seem that developers are hardcoded for functionality while security folk are hardwired towards safeguards. How do we reach a comfortable medium?
Kelly Jackson Higgins
Kelly Jackson Higgins,
User Rank: Strategist
8/25/2015 | 9:12:23 AM
Re: Monkey see Monkey do
I thought it was interesting to look at the issue from a psychological perspective. That may well be a key element in bridging the gap between the dev and security worlds.
RyanSepe
RyanSepe,
User Rank: Ninja
8/25/2015 | 9:08:00 AM
User-Experience
Also, user experience is another event that needs to be understood here. If the developer has a good experience with the tool they are more likely to use it in the future than if they had a bad experience. This principle is universal.
Page 1 / 2   >   >>


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
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-29376
PUBLISHED: 2022-05-23
Xampp for Windows v8.1.4 and below was discovered to contain insecure permissions for its install directory, allowing attackers to execute arbitrary code via overwriting binaries located in the directory.
CVE-2022-30015
PUBLISHED: 2022-05-23
In Simple Food Website 1.0, a moderation can put the Cross Site Scripting Payload in any of the fields on http://127.0.0.1:1234/food/admin/all_users.php like Full Username, etc .This causes stored xss.
CVE-2022-28999
PUBLISHED: 2022-05-23
Insecure permissions in the install directories and binaries of Dev-CPP v4.9.9.2 allows attackers to execute arbitrary code via overwriting the binary devcpp.exe.
CVE-2022-29002
PUBLISHED: 2022-05-23
A Cross-Site Request Forgery (CSRF) in XXL-Job v2.3.0 allows attackers to arbitrarily create administrator accounts via the component /gaia-job-admin/user/add.
CVE-2022-31489
PUBLISHED: 2022-05-23
Inout Blockchain AltExchanger 1.2.1 allows index.php/home/about inoutio_language cookie SQL injection.