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 Its Insane To Trust Static Analysis
Newest First  |  Oldest First  |  Threaded View
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
11/29/2015 | 4:11:11 PM
Re: SAST, DAST, and IAST all important testing technologies
I agree... SAST and DAST are too important to dismiss. We have to find a way to leverage the strength of each, at the same time work to continually evolve and raise the bar for these tools.  
johannacuriel
0%
100%
johannacuriel,
User Rank: Apprentice
10/1/2015 | 8:02:51 AM
OWASP Benchmark official review at OWASP
I did a review of this project as part of the Project review team at OWASP. It has never been my impression that the OWASP Benchmark project has been promoted within the OWASP community as a 'ready' to use tool but rather as a tool in development stage. It is clear to me that the tool still needs a lot of testing and even so, it will not be able to 'benchmark' all the features of a SAST tool for example, if the tool being benchmarked in not able to produce a complete XML output reports with all its results.

More details about OWASP Benchmark Project review:

https://drive.google.com/file/d/0B28S4R_cON7JZGtNZVRrMDl3NzQ/view?pli=1

https://groups.google.com/a/owasp.org/forum/?hl=en#!topic/projects-task-force/h1leFW8e8zE
planetlevel
100%
0%
planetlevel,
User Rank: Author
9/23/2015 | 12:34:36 PM
Re: What would a benchmark against Coverity show?
In reponse to a few private inquiries I want to make very clear that I think static analysis for many kinds of *quality* issues is fantastic.  FindBugs in particular has an excellent accuracy record for non-security bugs and it has helped me improve my code in the past.
planetlevel
100%
0%
planetlevel,
User Rank: Author
9/23/2015 | 12:14:57 AM
Re: What would a benchmark against Coverity show?
The OWASP Benchmark Project supports for many different commercial and open source tools, including: 
  • Findbugs
  • HP Fortify
  • PMD
  • IBM AppScan
  • Veracode
  • CheckMarx
  • Synopsys Coverity
  • Parasoft
  • SonarQube

The picture in the article is FindBugs (security) but that's just one example of (pretty poor) static analysis capability.  The Benchmark also looks at many dynamic scanning tools.  The results are fascinating.

And as I mentioned, easily reproduceable.  If you have Coverity, just clone the benchmark project and run Coverity on it.  Then feed the results into the Benchmark scoring tool and get a report on exactly what you want to see.

I appreciate your optimism, but it's amazing what you find out when you actually measure.
Charlie Babcock
50%
50%
Charlie Babcock,
User Rank: Ninja
9/22/2015 | 9:09:07 PM
What would a benchmark against Coverity show?
Author Jeff Williams uses OWASP benchmark results against FindBugs to disparage the effectiveness of static analsysis of code, and I haven't heard much about FindBugs. I'd be more interested in what a benchmark against Coverity or one of the other more prominent static analysis tools might show. I suspect static analysis has done too much good for too long for it to be dismissed as easily as Willaims does, with his confidence in the brilliance of Contrast Security's interactive application security testing. Might they each excel at different things?
cwysopal
67%
33%
cwysopal,
User Rank: Apprentice
9/22/2015 | 12:42:47 PM
SAST, DAST, and IAST all important testing technologies

IAST is a great testing technique that has some advantages that SAST and DAST do not have. But there are clearly strengths that SAST and DAST have that don't exist in IAST.  It's not time to throw away your SAST and DAST investment. A mature app sec program combines approaches to maximize strengths an minimize weaknesses.

SAST doesn't require a running system with test data and automated test suites.  This allows SAST to be used earlier in the dev cycle when it is least expensive to fix flaws.  DAST doesn't require modifying the production environment so you don't need find the server the app is running on, get the approval, schedule a change and contact an administrator to modify it. This allows DAST to be used more easily in production. Web apps can be scanned by just knowing the URL of the application. Finding the best way to combine techniqes will give you the best application security.

-Chris



Attackers Leave Stolen Credentials Searchable on Google
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2021
How to Better Secure Your Microsoft 365 Environment
Kelly Sheridan, Staff Editor, Dark Reading,  1/25/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We need more votes, check the obituaries.
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4815
PUBLISHED: 2021-01-27
IBM Cloud Pak for Security (CP4S) 1.4.0.0 could allow a remote user to obtain sensitive information from HTTP response headers that could be used in further attacks against the system.
CVE-2020-4816
PUBLISHED: 2021-01-27
IBM Cloud Pak for Security (CP4S) 1.4.0.0 could allow a remote attacker to obtain sensitive information, caused by the failure to properly enable HTTP Strict Transport Security. An attacker could exploit this vulnerability to obtain sensitive information using man in the middle techniques. IBM X-For...
CVE-2020-4820
PUBLISHED: 2021-01-27
IBM Cloud Pak for Security (CP4S) 1.4.0.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session.
CVE-2020-4967
PUBLISHED: 2021-01-27
IBM Cloud Pak for Security (CP4S) 1.3.0.1 could disclose sensitive information through HTTP headers which could be used in further attacks against the system. IBM X-Force ID: 192425.
CVE-2020-36012
PUBLISHED: 2021-01-27
Stored XSS vulnerability in BDTASK Multi-Store Inventory Management System 1.0 allows a local admin to inject arbitrary code via the Customer Name Field.