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
Software Assurance: Time to Raise the Bar on Static Analysis
Newest First  |  Oldest First  |  Threaded View
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
10/7/2014 | 10:09:36 AM
Re: complementary sweet spots
@Sara -- from my experience organizations typically use one tool -- the concept of best of breed has died and people have bought into the concept of UTM (Unified Threat Management).  We've seen this on the network side of the shop with Cisco, Juniper, and Fortinet... The same has happened with the AppSec/SwA tools -- all in one.  But that locks organizations into that proprietary solution.  The feedback I got from organizations is that it takes too much time to triage mutiple reports from tools -- or it takes resources to bring in a new tool.  So that becomes a barrier to introducing additional tools into the workflow.  The SWAMP eliminates that barrier and enable the developer to focus on those weaknesses that matters the most. The bigger shops or more mature organizations tend to use multiple tools, but have to glue results from various tools.  I'm sharing witht the community, we have solved that problem and are able to leverage the context from various tools to help dive deeper into weaknesses in code. 
Sara Peters
100%
0%
Sara Peters,
User Rank: Author
10/6/2014 | 4:10:28 PM
complementary sweet spots
As you mention, Kevin, it's better to use multiple tools, instead of just one, because different tools excel at different things. In your experience, do most organizations and developers combine tools like this, or do they too often pick just one?
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/2/2014 | 1:43:31 PM
Re: Tool Compilation
Thanks, Kevin. We'll be looking forward to you sharing the insight you get from SWAMP as the project evolves. 
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
10/1/2014 | 12:09:19 PM
Re: Tool Compilation
@Marilyn -- we have not determined that yet.  However, there is some data to suggest which tools may work well together depending on language and the program structure of code.  For open-source tools, we can definitely share some insight on that, but commercial tools you are restricted from sharing information based on the EULA --

The SWAMP opened in Feb of 2014, and we are stil buidling the analytics around this notion.  
Marilyn Cohodas
50%
50%
Marilyn Cohodas,
User Rank: Strategist
10/1/2014 | 8:59:37 AM
Re: Tool Compilation
Following on Ryan's comment, Kevin: Have you determined through SWAMP (thus far) what is the most popular or most effective tool combo for SA? 
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
9/30/2014 | 2:46:24 PM
Re: Tool Compilation
I'll take a look thanks! Just a quick question, do you specialize in one genre of tool or do you group tools by genres to subscribe to more users? (NetSec tools, InfoSec tools, etc)
KevGreene_Cyber
50%
50%
KevGreene_Cyber,
User Rank: Author
9/30/2014 | 1:16:03 PM
Re: Tool Compilation
@Ryan... Thanks for your comment.  CodeDx bundles open-source tools and allow you to bring in others as well (commerical and open-source) in one GUI.  The goal is to provide a cost-effective solution to help formalize aspects of software assurance in organizations.  You should give it a eval and let us know what you think.  Also, create an account in SWAMP let us know what you think.  
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
9/30/2014 | 1:08:47 PM
Tool Compilation
Good article. It definitely seems to be more often than not the case that a tool alone yields not as verbose data results as tools used in correlation. It takes time and effort to find the precise tools needed and each endeavor requires different data so its hard to foresee what tools are needed.

For tools that are open source, why not have them combined in a GUI or command line fashion in one distribution. Allow functionality to add upon those packages for data correlation and your analysis efficiency should increase ten fold. 


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
How Enterprises Are Assessing Cybersecurity Risk in Today's Environment
The adoption of cloud services spurred by the COVID-19 pandemic has resulted in pressure on cyber-risk professionals to focus on vulnerabilities and new exposures that stem from pandemic-driven changes. Many cybersecurity pros expect fundamental, long-term changes to their organization's computing and data security due to the shift to more remote work and accelerated cloud adoption. Download this report from Dark Reading to learn more about their challenges and concerns.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-0261
PUBLISHED: 2022-01-18
Heap-based Buffer Overflow in GitHub repository vim/vim prior to 8.2.
CVE-2022-0262
PUBLISHED: 2022-01-18
Cross-site Scripting (XSS) - Stored in Packagist pimcore/pimcore prior to 10.2.7.
CVE-2022-0263
PUBLISHED: 2022-01-18
Unrestricted Upload of File with Dangerous Type in Packagist pimcore/pimcore prior to 10.2.7.
CVE-2022-23302
PUBLISHED: 2022-01-18
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configurat...
CVE-2022-23305
PUBLISHED: 2022-01-18
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into...