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.

Vulnerabilities / Threats

DevSecOps An Effective Fix for Software Flaws

Organizations seeking to fix flaws faster should look to automation and related methodologies for success, says a new report.

Knowing a vulnerability's severity might not tell you anything about how quickly that vulnerability will be fixed. But knowing what kind of development model the company is using could tell you a lot. Those are some of the conclusions of a new study that looks at how many vulnerabilities appear in enterprise software and how long they hang around once they're discovered.

The ninth edition of Veracode's "State Of Software Security" report concludes that the greatest indicator of how quickly an organization will fix the vulnerabilities it finds correlates to how many times each year developers scan their code for issues. It's a marker that Chris Eng, vice president of research at Veracode, says he sees as a stand-in for the type of development discipline the company uses.

"We used scan frequency as kind of a proxy for DevOps because if you're scanning really often — daily or or more often — it indicates that you're doing a lot with automation," Eng says. "We can surmise from that that you're probably a DevOps shop." He contrasts organizations that scan their code hundreds of times a year with those that run one or two scans a year, and says the differences are borne out in what Veracode sees in code defects and remediation.

Veracode judges the duration of a flaw based on how many times the same issue shows up in a scan after its initial discovery, Eng says. "If the flaw shows up three, four, five times, we can see that this was discovered in January, and you scanned it every month, and it's still there in May—then in June it goes away. So you assume that to mean that they closed it after four months," he explains.

Eng's use of "months" as the time scale for remediation is not arbitrary. According to the Veracode research, more than 70% of all flaws were still present a month after initial discovery, and nearly 55% had not been remediated after three months. In fact, while roughly a quarter of all code flaws were dealt with inside 21 days, another quarter were still open issues after a year.

The length of time from discovery to fix varied according to the flaw's severity — but not very much, Eng says. Based on a scale that rates the most severe issues a 5 and the least severe a 1, he explains, "We expected the fives to be fixed the fastest and then the fours, threes, twos, but it wasn't like that." While the flaws rated 5 were repaired fastest, 3s were fixed faster than 4s — and 5s weren't fixed all that quickly, either.

It takes 14 days to get 25% of the 5s fixed, 64 days to get to the 50% mark on repairs, and 206 days before 75% have been corrected, Eng says. The great variation in time to repair is how often the code is scanned for flaws, he says.

In the population that scans their code 300 times a year or more, Eng says, "They're fixing a quarter of the flaws that we detect within three days, half within five days, and 75% within seven days." Just as important, Eng says, those high-frequency companies eventually remediate 100% of the flaws found.

"Compare that to the ones that are scanning one to three times a year," he says. "Even to get to the 50% mark it's almost a year, and to get to the 75% mark it's almost four years."

This report surprised Eng in several ways, but ultimately, he says, "We feel like we have good evidence that the DevSecOps thing actually does work. We see that in the 'fix velocity' chart, and that was that was a huge, huge takeaway for us."

Related Content:

 

Black Hat Europe returns to London Dec 3-6 2018  with hands-on technical Trainings, cutting-edge Briefings, Arsenal open-source tool demonstrations, top-tier security solutions and service providers in the Business Hall. Click for information on the conference and to register.

Curtis Franklin Jr. is Senior Editor at Dark Reading. In this role he focuses on product and technology coverage for the publication. In addition he works on audio and video programming for Dark Reading and contributes to activities at Interop ITX, Black Hat, INsecurity, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-12420
PUBLISHED: 2019-12-12
In Apache SpamAssassin before 3.4.3, a message can be crafted in a way to use excessive resources. Upgrading to SA 3.4.3 as soon as possible is the recommended fix but details will not be shared publicly.
CVE-2019-16774
PUBLISHED: 2019-12-12
In phpfastcache before 5.1.3, there is a possible object injection vulnerability in cookie driver.
CVE-2018-11805
PUBLISHED: 2019-12-12
In Apache SpamAssassin before 3.4.3, nefarious CF files can be configured to run system commands without any output or errors. With this, exploits can be injected in a number of scenarios. In addition to upgrading to SA 3.4.3, we recommend that users should only use update channels or 3rd party .cf ...
CVE-2019-5061
PUBLISHED: 2019-12-12
An exploitable denial-of-service vulnerability exists in the hostapd 2.6, where an attacker could trigger AP to send IAPP location updates for stations, before the required authentication process has completed. This could lead to different denial of service scenarios, either by causing CAM table att...
CVE-2019-5062
PUBLISHED: 2019-12-12
An exploitable denial-of-service vulnerability exists in the 802.11w security state handling for hostapd 2.6 connected clients with valid 802.11w sessions. By simulating an incomplete new association, an attacker can trigger a deauthentication against stations using 802.11w, resulting in a denial of...