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.

Risk

11/25/2009
10:00 AM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Stay On Top of Source Code Security Flaws

Fortify's 360 Server helps developers track flaws and fixes in applications.

Source code analysis, a fundamental part of a complete application security process, helps IT find flaws and vulnerabilities in application code that could be exploited by attackers. A critical component of source code analysis is tracking and remediating the flaws and vulnerabilities uncovered.

Fortify's 360 Server is a repository for all the results and remediation activities that accompany an analysis of source code. While 360 Server doesn't itself perform source code analysis, it does accept uploads from other Fortify products in the 360 suite that do. Organizations can also take advantage of the product's service-oriented architecture to integrate with third-party code analysis software.

A common starting point in Server 360 is a new project, such as one or more applications being assessed. Once a project is created, security and compliance staff use the project area to view actual source code issues through a mock integrated development environment to understand exactly what issues are outstanding. Reviewers can mark issues as an exemption, a false positive, exploitable, or one of several other options.

DIG DEEPER
Special Report: Forensic Files
The latest enterprise incident response and digital forensic tools let organizations perform investigations in-house--and then work with authorities to catch the bad guys. PLUS: A guide to calling in the law.
Surprisingly, there isn't a method to mark an issue as resolved and provide supporting documentation or a link to an updated analysis report. A "comments" section is available for staff members, and this could be used to note that an issue has been resolved, but an explicit mechanism would be more useful. Once project requirements are signed off, the project is closed. There is no formal method of closing the project, but the status of the project is automatically updated to show all requirements have been accepted. From this point on, the project resides online. Because all activities within the project are tracked and logged, a full audit trail exists if needed for future reviews.

The Fortify 360 Server is the next logical step for organizations that have implemented application security code review, have structured remediation processes in place, and are looking to increase the efficiency of the process. It's particularly useful for those with other Fortify products in-house.

Adam Ely is an information security consultant.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
US Turning Up the Heat on North Korea's Cyber Threat Operations
Jai Vijayan, Contributing Writer,  9/16/2019
MITRE Releases 2019 List of Top 25 Software Weaknesses
Kelly Sheridan, Staff Editor, Dark Reading,  9/17/2019
Preventing PTSD and Burnout for Cybersecurity Professionals
Craig Hinkley, CEO, WhiteHat Security,  9/16/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-9717
PUBLISHED: 2019-09-19
In Libav 12.3, a denial of service in the subtitle decoder allows attackers to hog the CPU via a crafted video file in Matroska format, because srt_to_ass in libavcodec/srtdec.c has a complex format argument to sscanf.
CVE-2019-9719
PUBLISHED: 2019-09-19
A stack-based buffer overflow in the subtitle decoder in Libav 12.3 allows attackers to corrupt the stack via a crafted video file in Matroska format, because srt_to_ass in libavcodec/srtdec.c misuses snprintf.
CVE-2019-9720
PUBLISHED: 2019-09-19
A stack-based buffer overflow in the subtitle decoder in Libav 12.3 allows attackers to corrupt the stack via a crafted video file in Matroska format, because srt_to_ass in libavcodec/srtdec.c misuses snprintf.
CVE-2019-16525
PUBLISHED: 2019-09-19
An XSS issue was discovered in the checklist plugin before 1.1.9 for WordPress. The fill parameter is not correctly filtered in the checklist-icon.php file, and it is possible to inject JavaScript code.
CVE-2019-9619
PUBLISHED: 2019-09-19
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.