Dr. Dobb's Journal - October 2007 - (Page 20) Conversations by Deirdre Blake Rating Security Matt Moynahan CEO of Veracode DDJ: Why has application-level security suddenly moved into the forefront? MM: Application security has moved to the forefront largely because hacking into enterprises has become a criminal activity driven by monetary gain. Applications are the weakest asset—or should I say, the targetrichest environment for attackers. Enterprises have been largely successful in securing their networks, whereas they are just now realizing how difficult it is to secure applications. Evidence of this is that 90 percent of all new attacks occur at the application level, whereas still only 10 percent of IT security spending is at the application tier. DDJ: When it comes to software, security raises its head both pre- and post-release. Is one stage more important than the other? MM: Given the dynamic nature of the application security threat, security testing preand post-release is very important. That said, thorough testing pre-deployment has a much higher return on investment, given that you are likely to dramatically lower the probability of a successful attack against your application as well as reduce the operational cost burdens associated with constant security patching required for insecure software once it’s been deployed. DDJ: Veracode, your company, focuses on “on-demand” security. What is “on-demand” security? MM: On-demand application security is simply delivering code security testing as a service. Part of the difficulty in deploying application security tools are cultural and process issues arising from different development teams, locations, and coding methodologies. Choosing to analyze your applications with an outsourced service enables you to focus on your core competencies—running your business—and relying on security experts and lowering your overall operational burden. Using a service is much simpler and does not involve the deployment of hardware and software, or expenses such as training and licenses. DDJ: When it comes to security, what kind of metrics can be collected and what can developers do with that information? MM: We [recently] announced the Veracode Software Security Ratings Service, which is a way to determine the security level of a piece of software. The ratings provide a pragmatic way for enterprises and ISVs to measure, compare, and improve the security of software. We do this by identifying and ranking the severity and exploitability of software flaws. With a rating, enterprises now have insight into the security quality of software for the first time. It’s similar to the ratings provided by Moody’s, Standard and Poor’s, or Consumer Reports for other products. The developers of the application being rated receive a tailored report that clearly shows what the most serious flaws are and which ones are the most important to fix first, and a recommended remediation path, so the rating can go from a “B” to an “A” for example. 20 Dr. Dobb’s Journal l www.ddj.com l October 2007 DDJ: Binary-code analysis versus sourcecode analysis. What’s the advantage of one over the other? MM: The ratings would never have been possible if the founders of Veracode hadn’t solved the very hard problem of security analysis at the binary level. By looking for software flaws and vulnerabilities in binaries, [we are] able to assess 100 percent of the code in an application, including thirdparty libraries and components. These are portions you typically don’t have the source code for. In addition, by doing binary-code analysis, there isn’t the intellectual-property sensitivity there would be if you were analyzing the source code. What I mean by that is [that] source code is a company’s IP, like the secret formula for Coke or Pepsi. Those companies would never allow an off-site taste test if it required them to send their intellectual property, in this case, their special formula or recipe along with it. In this particular case, the software companies’ IP is the source code. So bottom line, binary analysis is a superset of source-code analysis, allowing you to review 100 percent of an application for security flaws, not just a portion of it. That makes [our] security reviews more complete and more accurate. Binary analysis also makes it possible for us to offer this analysis through an ondemand, outsourced service. For enterprises, that means an easier and more costeffective solution to software security reviews than doing it in house, which can be time consuming—requiring internal training, licenses, and hardware and software. And for companies that are purchasing software, this means they have a way of getting a third party, external, software-security rating for the first time. DDJ http://www.ddj.com
Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - October 2007 Cover Contents Hmmmm Alia Vox Developer Diaries Developer’s Notebook AI: It’s OK Again! Conversations Visual Cryptography and Bit-Plane Complexity Segmentation Inside the Windows Vista Disk Encryption Algorithm Memory-Aware Components Software and the Core Description Process Logging In C++ Effective Concurrency The Agile Edge Swaine’s Flames Dr. Dobb's Journal - October 2007 Dr. Dobb's Journal - October 2007 - Cover (Page Cover1) Dr. Dobb's Journal - October 2007 - Cover (Page Cover2) Dr. Dobb's Journal - October 2007 - Cover (Page 1) Dr. Dobb's Journal - October 2007 - Cover (Page 2) Dr. Dobb's Journal - October 2007 - Cover (Page 3) Dr. Dobb's Journal - October 2007 - Contents (Page 4) Dr. Dobb's Journal - October 2007 - Contents (Page 5) Dr. Dobb's Journal - October 2007 - Hmmmm (Page 6) Dr. Dobb's Journal - October 2007 - Hmmmm (Page 7) Dr. Dobb's Journal - October 2007 - Hmmmm (Page 8) Dr. Dobb's Journal - October 2007 - Hmmmm (Page 9) Dr. Dobb's Journal - October 2007 - Alia Vox (Page 10) Dr. Dobb's Journal - October 2007 - Alia Vox (Page 11) Dr. Dobb's Journal - October 2007 - Developer Diaries (Page 12) Dr. Dobb's Journal - October 2007 - Developer Diaries (Page 13) Dr. Dobb's Journal - October 2007 - Developer’s Notebook (Page 14) Dr. Dobb's Journal - October 2007 - Developer’s Notebook (Page 15) Dr. Dobb's Journal - October 2007 - AI: It’s OK Again! (Page 16) Dr. Dobb's Journal - October 2007 - AI: It’s OK Again! (Page 17) Dr. Dobb's Journal - October 2007 - AI: It’s OK Again! (Page 18) Dr. Dobb's Journal - October 2007 - AI: It’s OK Again! (Page 19) Dr. Dobb's Journal - October 2007 - Conversations (Page 20) Dr. Dobb's Journal - October 2007 - Conversations (Page 21) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 22) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 23) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 24) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 25) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 26) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 27) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 28) Dr. Dobb's Journal - October 2007 - Visual Cryptography and Bit-Plane Complexity Segmentation (Page 29) Dr. Dobb's Journal - October 2007 - Inside the Windows Vista Disk Encryption Algorithm (Page 30) Dr. Dobb's Journal - October 2007 - Inside the Windows Vista Disk Encryption Algorithm (Page 31) Dr. Dobb's Journal - October 2007 - Inside the Windows Vista Disk Encryption Algorithm (Page 32) Dr. Dobb's Journal - October 2007 - Inside the Windows Vista Disk Encryption Algorithm (Page 33) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 34) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 35) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 36) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 37) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 38) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 39) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 40) Dr. Dobb's Journal - October 2007 - Memory-Aware Components (Page 41) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 42) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 43) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 44) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 45) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 46) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 47) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 48) Dr. Dobb's Journal - October 2007 - Software and the Core Description Process (Page 49) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 50) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 51) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 52) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 53) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 54) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 55) Dr. Dobb's Journal - October 2007 - Logging In C++ (Page 56) Dr. Dobb's Journal - October 2007 - Effective Concurrency (Page 57) Dr. Dobb's Journal - October 2007 - Effective Concurrency (Page 58) Dr. Dobb's Journal - October 2007 - Effective Concurrency (Page 59) Dr. Dobb's Journal - October 2007 - The Agile Edge (Page 60) Dr. Dobb's Journal - October 2007 - The Agile Edge (Page 61) Dr. Dobb's Journal - October 2007 - The Agile Edge (Page 62) Dr. Dobb's Journal - October 2007 - The Agile Edge (Page 63) Dr. Dobb's Journal - October 2007 - Swaine’s Flames (Page 64) Dr. Dobb's Journal - October 2007 - Swaine’s Flames (Page Cover3) Dr. Dobb's Journal - October 2007 - Swaine’s Flames (Page Cover4)
For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.