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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
‘Re-innovating’ Static Analysis: 4 Steps
Threaded  |  Newest First  |  Oldest First
Poissonpraveen
Poissonpraveen,
 User Rank: Apprentice
12/11/2015 | 8:03:51 AM
nice post
nice post and good peice of information and keep it bro...
KevGreene_Cyber
KevGreene_Cyber,
 User Rank: Author
12/14/2015 | 1:13:09 PM
Re: nice post
Thanks for the support.  Much appreciated.. 
planetlevel
planetlevel,
 User Rank: Author
12/15/2015 | 12:26:30 PM
The *term* static analysis should die
Hi Kevin - nice article.  Just wanted to check if you thought it was me suggesting static analysis is dead -- which I don't.  I have written that the *term* static analysis should die.  At least for security.  I think I've been clear that I use and trust static analysis for many types of code quality analysis.

http://www.contrastsecurity.com/blog/why-its-time-for-the-terms-static-analysis-and-dynamic-analysis-to-die

The basic idea is that it's the information -- the context -- available to the tool that matters, not the fact that it happens to be static, dynamic, interactive, runtime, or whatever.  We should be talking about whether a tool has access to accurate data flow, backend connections, http requests/responses, libraries/frameworks, etc...  That's what tools need to start getting accurate.

And I want to be clear. This isn't about correlating the results of single-approach tools. My experience is that it's very difficult to accurately correlate.  And even if you do, you lose the "sweet spots" that were only found by one tool and so didn't correlate with anything.  I'm talking about merging the analysis techniques themselves into a single tool - so that the analysis engine itself can use a broad range of contextual information when identifying vulnerabilities.

Static analysis is a key security technology. But in my view needs the information from other security analysis approaches closely integrated during analysis.  I look forward to seeing the results of the STAMP.

 

 

 
KevGreene_Cyber
KevGreene_Cyber,
 User Rank: Author
12/15/2015 | 2:33:16 PM
Re: The *term* static analysis should die
Jeff... that's not the case.  I think there are ways (we have been exploring) to correlate and bring disparate results together; as well as the context of various security testing activiites -- see ASTAM.  So.. we have already explored new ways to bring results together.. I think we are moving in the right direction.  Lots of exciting things to come... Thanks for reading...


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
Everything You Need to Know About DNS Attacks
It's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask. Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted. Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2023-33196
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences. Cross site scripting (XSS) can be triggered by review volumes. This issue has been fixed in version 4.4.7.
CVE-2023-33185
PUBLISHED: 2023-05-26
Django-SES is a drop-in mail backend for Django. The django_ses library implements a mail backend for Django using AWS Simple Email Service. The library exports the `SESEventWebhookView class` intended to receive signed requests from AWS to handle email bounces, subscriptions, etc. These requests ar...
CVE-2023-33187
PUBLISHED: 2023-05-26
Highlight is an open source, full-stack monitoring platform. Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `ty...
CVE-2023-33194
PUBLISHED: 2023-05-26
Craft is a CMS for creating custom digital experiences on the web.The platform does not filter input and encode output in Quick Post validation error message, which can deliver an XSS payload. Old CVE fixed the XSS in label HTML but didn’t fix it when clicking save. This issue was...
CVE-2023-2879
PUBLISHED: 2023-05-26
GDSDB infinite loop in Wireshark 4.0.0 to 4.0.5 and 3.6.0 to 3.6.13 allows denial of service via packet injection or crafted capture file