<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Veracode on Medium]]></title>
        <description><![CDATA[Stories by Veracode on Medium]]></description>
        <link>https://medium.com/@Veracode?source=rss-f7913a3ebd3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0brLo5Vv7nCquuBvQh5dbA.jpeg</url>
            <title>Stories by Veracode on Medium</title>
            <link>https://medium.com/@Veracode?source=rss-f7913a3ebd3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:04:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Veracode/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How We Worked with Our Development Team to Make Security a Differentiator]]></title>
            <link>https://medium.com/@Veracode/how-we-worked-with-our-development-team-to-make-security-a-differentiator-91f4f81b2c28?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/91f4f81b2c28</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Thu, 26 May 2016 17:50:15 GMT</pubDate>
            <atom:updated>2016-05-26T17:50:15.267Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/hailey-pobanz">Hailey Pobanz</a></p><p>Starting an application security program at our <a href="http://doubledutch.me/">mobile app company</a> was becoming an inevitability. Yet, there were still groups within the company that didn’t see the value or thought starting a full-scale program wasn’t worth the effort. My challenge — in addition to developing a strategy that reduced risk and didn’t slow down the development processes — was to make these adversaries into allies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*Oy1dwwn2CIQlHV79." /></figure><h4>Why we started an AppSec program</h4><p>With security questions coming in from clients purchasing our software, DoubleDutch needed someone to client facing who could speak to the security of our platform. The responsibility fell to me, and I quickly realized we couldn’t continue responding to one-off requests for security attestation. Doing so was significantly slowing down our sales cycle and putting us at a disadvantage with our competitors. We needed to have a way to demonstrate our security posture and the best way to do that was to create an application security program as part of our software development lifecycle and to use this approach to achieve a third-party seal of approval for our security.</p><p>I found a partner that could help us create a security program and that could provide this seal of approval in the form of the Veracode VerAfied seal. With a trusted partner in place to help develop our application security strategy, the next big hurdle was getting the internal teams impacted by the program on board with the strategy.</p><h4>Identifying the relevant teams</h4><p>While I work on security with almost every department at our company, the two teams I was most focused on was product management and engineering. Each of these teams would be directly impacted by any AppSec policies we created, so I needed them to be on board with what we had planned. I knew this would be a challenge as these teams typically see security as an inhibitor to their progress. Security initiatives slow them down as their timelines are already dedicated to deadlines around produce updates. They are focused on delivering a great product that fulfills the needs of our customers. My goal was to work with the team so that “secure” became part of the definition of “great product”.</p><h4>Turning adversaries into allies</h4><p>From my own experience, I know I am less likely to balk at change if I am part of the conversation on how the change should occur. I think that is just human nature. Realizing this, it only made sense to work with the developers and product management rather than dictate how we would go about integrating application security into our development processes. In doing so, I was able to first understand how our development processes worked, and how we came up with product requirements. With this understanding, I was able to work with the team to come up with realistic expectations around security.</p><h4>Working with other teams to make AppSec a differentiator</h4><p>Though the product management and development team buy-in were crucial to the program, there were other groups that needed to understand what the benefits of this program would bring to the company.</p><p>To start, the management team needed to see the value of the program not just from a security perspective, but also from a business perspective. To demonstrate that need to the management team we explained that many of our customers were asking about our security practices and this line of questioning was slowing down our processes. In Europe, for example, our customers were particularly concerned about the security of their third-party software because they are liable for any breaches, even if they happened due to a vulnerability in vendor software rather than their own. By <a href="https://www.veracode.com/directory">achieving a VerAfied status</a> from Veracode we’d be able to move beyond this objection.</p><p>Once this was understood, the marketing department was even able to use this as a differentiator for our software as our competitors did not have this seal.</p><h4>Conclusion</h4><p>Companies are becoming more aware of the threat vulnerabilities in the software they purchase pose. As a software vendor, this means we will continue fielding questions about our security processes and the posture of specific applications. I knew the best way to manage this challenge was to implement a full scale application security program which integrated with our development processes. By working with the development team rather than dictating what they needed to do, made it possible for us to create a full scale program and make security a differentiator for us rather than a sales hurdle.</p><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/cracking-the-code-application-security-buy-in-veracode.pdf">Learn How to Work With Teams in Your Organization to Make AppSec a Success</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/01/how-we-worked-our-development-team-make-security-differentiator"><em>https://veracode.com/blog/...</em></a><strong><em> on January 21, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91f4f81b2c28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A pragmatic approach to leveraging WAF and RASP]]></title>
            <link>https://medium.com/@Veracode/a-pragmatic-approach-to-leveraging-waf-and-rasp-d98980fd76a4?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d98980fd76a4</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Tue, 24 May 2016 19:57:07 GMT</pubDate>
            <atom:updated>2016-05-24T19:57:07.575Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/joe-pelletier">Joe Pelletier</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*3Bfy3JGZCTDyHxQm." /></figure><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/what-is-rasp.pdf">Runtime Application Self-Protection</a> (RASP) is a revolutionary technology that aims at improving application security. RASP integrates monitoring and protection as part of the deployment of web applications making it the first technology to provide protection in real-time.</p><p>RASP is a new technology with the promise of improving application security by enabling applications to self-protect in real-time against internal and external attacks. This promise has given way to some talk about RASP replacing WAFs entirely. While, there may be some use cases where RASP can fully replace a WAF, the reality is both technologies have their own strengths and weaknesses and should be looked at as important layers for defense-in-depth.</p><p>Many organizations have invested in WAF for quite some time. Large portions of the security budget may be devoted to supporting WAF implementations. However, are you finding that WAF is only useful in some — not all — of attack scenarios? There is a reason you are noticing this lag.</p><p>WAFs provide broad perimeter defenses (generally at the data center level) and mitigate threats at the edge of your network. At face value, this is an attractive value proposition, but the deficiencies of WAF are generally only seen during the post-implementation phase when it comes to operating and maintaining the solution.</p><p>However, most customers I’ve spoken with use WAF in monitoring mode. This means that while it’s in-line with their app, it’s not taking action on application-level attacks. Instead, its recording the attack requests and letting you know the type of attack, which endpoints it’s hitting, and from where. While that’s important information to know, it doesn’t exactly help you sleep better at night.</p><p>On the positive side, WAFs may also tell you that it has successfully defended traffic from known-malicious IPs, automated bots, as well as blocked Denial of Service attacks (if you’ve purchased that add-on). These use cases are actually well suited for WAFs since they are usually network-level attacks that, if not blocked, can cause problems like application availability.</p><p>Most often than not, customers are trying to make the best use of their WAF for mitigating application level threats like SQLi and XSS. They start off by trying to maintain the WAF configuration outside the development process by running DAST assessments and using this information to “virtually patch” the WAF. Unfortunately, the more patches applied the greater chance of a negative performance impact. At a theoretical level, “virtual patching” is an effective concept but ultimately fails for the following reasons:</p><p>On-going maintenance is impossible to keep up with — AppSec teams generally do not know when App Dev may be pushing a release. This is especially true for large AppSec programs supporting multiple teams.</p><ul><li>Development is not involved — App Dev is generally “hands off” with WAF configuration and tuning, meaning it becomes a solution for security teams to maintain. WAFs are a black box that App Dev does not want to own or have interfere with their crown jewel — the application!</li><li>The biggest fear for App Dev is false positives from WAF. A WAF FP is something that inadvertently terminates a valid end-user transaction or request. Imagine your customer trying to purchase something on a website you own, but their transaction fails because the WAF *thinks* it’s seen attack. This is not good for business, and as a result, WAFs end up being underutilized and become less effective at protecting applications.</li></ul><p>WAF suffers from this stigma, and consequently serves as an expensive “attack monitor” that only tells you bad news. It also lacks the context — that is, the understanding of how data from the web request is actually used in the application — to mitigate the threat. This is where RASP adds a tremendous amount of value without any “learning” or tuning required. It can respond in real-time, at the run-time, at high performance and with low overhead. Finally, RASP can be integrated back into the SDLC and tested as part of existing functionality &amp; quality tests. This helps ensure RASP does not negatively interfere with application functionality, yet still provide effective application security controls.</p><p>So what can RASP offer when combined with WAF? In short:</p><ul><li>Risk reduction: Improve you application risk posture without the manual overhead of maintaining WAF</li><li>Defense in depth: Ensure application threats are mitigated <em>in addition to</em> common network level attacks that WAF is well suited for. Leverage each technology where it’s best served to provide high performance risk reduction.</li><li>Speed to market: Integrate RASP downstream into the SDLC and show how it can improve security without adding overhead or “breaking the app”</li></ul><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/what-is-rasp.pdf">Learn more about RASP and how it works</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/02/pragmatic-approach-leveraging-waf-and-rasp"><em>https://veracode.com/blog/...</em></a><strong><em> on February 16, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d98980fd76a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why RASP is a Transformational Technology]]></title>
            <link>https://medium.com/@Veracode/why-rasp-is-a-transformational-technology-aa288748a9e9?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa288748a9e9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Tue, 24 May 2016 19:56:51 GMT</pubDate>
            <atom:updated>2016-05-24T19:56:51.712Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/joseph-feiman">Joseph Feiman</a></p><p>For the most part, new technology is evolutionary, it advances on the innovations of the past. An example of evolutionary technology in the security world would be next generation firewall. It advanced the technology already created to provide some new capabilities.</p><p>Every so often, we see a technology that is innovative, and even rarer a truly transformational technology, or an innovation that changes the way a problem is solved and from which new technology will spring. RASP (Runtime Application Self-Protection) is just such a technology, and will change the way we look at security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*OqZbJAd5VkQnqVnd." /></figure><p>Existing security technologies fail to protect and diagnose our production applications. There are several reasons why they fail:</p><ol><li>Today’s application protection is, primarily, perimeter protection conducted by firewalls of different kinds, including web application firewalls (WAF). These technologies are traffic and session inspectors; they can mainly see traffic in and out of the application; for them, an application is a black box; they do not see and understand business logic flow; they do not see data flow within an application, and they do not see an application’s composition. <strong><em>How can they protect what they cannot see and understand?</em></strong></li><li>The perimeter is dissipating because of our increased mobility and availability of mobile devices. Where is the firewall when we work in a café, or on a train, or while walking down the street with our smartphone in hand? Where is perimeter that should be protected? <strong><em>How can perimeter-based technologies protect what is vanishing?</em></strong></li><li>Perimeter-based security technologies are outward-facing. They watch for outsider attacks. Yet, over the past few years, we painfully learned that the most severe attacks are often launched by insiders: our own employees and consultants. <strong><em>How can perimeter-based technologies protect the frontier that they are not watching?</em></strong></li><li>And if we reach out for protection technologies that are not traffic analyzers; when we attempt to use technologies such as application shielding and obfuscation, we fail once again. These technologies transform applications code in a way that inhibits reverse engineering and tampering. They are mainly focused on deterring intellectual property theft, not on attack protection. And they are invasive: they make changes in the applications’ code. <strong><em>How would any developer or application owner willingly allow anyone to mess with business-logic code?</em></strong></li></ol><h4>RASP Will Succeed Where Others Have Failed</h4><p>RASP is a unique technology that solves all the deficiencies described above. RASP, typically, gets instrumented into application runtime engine: into a JVM, .Net CLR, Apache server, etc. It becomes an additional feature of such engine, capable of detecting attacks and protecting against them. Being an integral part of the runtime, it has a comprehensive view of the logic flow, data flow, and configuration. It can be instrumented in the engine whether it runs on-premise, in the cloud, or on a mobile device (the latter is a coming capability, but coming inevitably). Perimeter is irrelevant for RASP: It is equally vigilant against insiders and outsiders. And it does not make changes to application code.</p><p>And, just as we saw multiple technologies arise from the advancement of network packet inspections, (firewalls, UTMs, web gateways, etc.), as RASP technology continues to mature, we will see other technologies spin out of its capabilities. All that makes RASP a transformational paradigm and technology, which advances application protection to an unseen level of assurance.</p><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/what-is-rasp.pdf">Learn more about RASP and how it works</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/02/why-rasp-transformational-technology"><em>https://veracode.com/blog/...</em></a><strong><em> on February 12, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa288748a9e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How the Legal Department Can Improve Your Vendor Application Security Program]]></title>
            <link>https://medium.com/@Veracode/how-the-legal-department-can-improve-your-vendor-application-security-program-38ef0bba192d?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/38ef0bba192d</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Tue, 24 May 2016 19:55:10 GMT</pubDate>
            <atom:updated>2016-05-24T19:55:10.961Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/jessica-lavery">Jessica Lavery</a></p><p>In order to keep up with the need for applications, companies are purchasing software at an accelerated rate. And if you are like most companies, your processes for vetting the security of your software is probably not very sophisticated. Most companies rely on questionnaires or even just a wink and a nod from the vendor’s account manager.</p><p>Companies that recognize the risk introduced from vendor applications implement <a href="https://www.veracode.com/blog/2015/10/third-party-application-security-risks-modern-companies-sw">third-party application security programs</a>. But even though vendor application security testing programs can significantly reduce risk, they can bring with them their own set of logistical dilemmas. That’s why it is best to work with a trusted advisor who has processes for creating these types of programs.</p><h4>Getting legal on your team</h4><p>One thing your advisor will tell you is that working with your legal department in crafting your program is an absolute necessity. Your legal department will help you craft language to make sure your vendor contracts are consistent with the security policies you want to enact. They will also evaluate whether your security demands are reasonable and legal.</p><h4>Creating consistency</h4><p>Working with the legal department will ensure legal compliance and consistency exists among your various suppliers and partners as well as your internal teams. We all know that the days of a centralized IT buying center are long gone. The democratization of IT means that anyone, in any department and at any time can purchase software to make their job more efficient. However, if you make contract reviews by the legal team part of the procurement processes, or PO process, then the legal team becomes your ally in controlling the flow of insecure software that makes its way into your environment.</p><h4>A winning combination</h4><p>Unlike other teams in your organization, working with legal is rather straightforward, and poses few (if any) hurdles. Legal teams understand the concept of risk reduction and liability. They understand that if you are breached due to a third-party application, it is still the name of your company in the news. So, you won’t have to do much in the way of convincing your legal team that a vendor application security testing program is necessary.</p><p>What you will have to do is help them understand best practices for these types of programs, and then iterate your program design based on their feedback.</p><p>By working with the legal team, you are creating a winning combination for a strong program that is consistently applied across your organization. Find out more with our guide, <a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/cracking-the-code-application-security-buy-in-veracode.pdf"><em>Cracking the Code on Application Security Buy-In</em></a>.</p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/03/how-legal-department-can-improve-your-vendor-application-security-program"><em>https://veracode.com/blog/...</em></a><strong><em> on March 16, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38ef0bba192d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Need Your Boss’ Buy-In for Application Security]]></title>
            <link>https://medium.com/@Veracode/why-you-need-your-boss-buy-in-for-application-security-2fbd46a42aa9?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fbd46a42aa9</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Tue, 24 May 2016 19:55:07 GMT</pubDate>
            <atom:updated>2016-05-24T19:55:07.884Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/suzanne-ciccone">Suzanne Ciccone</a></p><p>Want your application security program to succeed? Get your boss on board. You need your CISO’s buy-in, and not just for scanning or pen testing a few business-critical apps — but for building a mature, robust program that secures every application the organization builds, buys or assembles. Here’s why:</p><h4>Reason 1: You need your boss to be a champion for your program with the C-team</h4><p>You need a C-level application security champion (such as your CISO) in order to get the entire executive team’s buy-in. This champion needs to understand why a mature AppSec program is critical and be able to talk intelligently about it to the rest of the C-team on their terms — meaning, less talk about static and dynamic analysis and more talk about the bottom line.</p><p>Beyond the technology or technical details of the program, make sure your boss understands, and can talk to his or her peers about:</p><ul><li>The benefits of a mature AppSec program to the organization.</li><li>How the assessment cycle will speed up development and reduce the cost of remediating vulnerabilities post-production.</li><li>The risk that vulnerabilities in the application layer pose to the organization, and how reducing this risk will ultimately save the company money and time.</li></ul><h4>Reason 2: With the C-suite on board, you’ll get the support you need from other departments</h4><p>If you have support for your application security program from the executive team, other departments in the organization will be compelled to participate and support the program as well. Application security is unique in that it affects the work routines of many different departments in your organization. If these departments don’t understand and embrace the changes brought about by your program, you’re stalled. For instance, the development team can be the biggest barrier to the success of the program, because if they do not follow the protocol set forth by the program plan, you won’t be able to demonstrate the value of the plan.</p><h4>Reason 3: C-suite support means you’ll be able to scale your program</h4><p>Ultimately, the more support the application security program has from the C-suite, the more likely the security team will be able to scale the program to cover the entire application layer over time. The end goal needs to be a mature, robust application security program that secures every application at your organization, regardless of origin. It’s not enough to secure only the applications you build or only the business-critical ones. Recent high-profile and costly breaches have stemmed from non business-critical third-party applications and open source components. Your organization isn’t truly secure unless your application security program can assess every application, with the ability to scale as your organization expands and changes.</p><h4>A Few Conversation-Starting Stats</h4><p><em>Bottom line</em>: Make sure you’ve got the right people on board to ensure your application security program has a chance. And start with your boss; here are a few stats to help get the conversation started:</p><ul><li>Compared to Q1 2015, Q2 2015 saw a 17.65% increase in distributed denial of service (DDoS) attacks targeting the application layer. — <a href="https://www.akamai.com/us/en/our-thinking/state-of-the-internet-report/">Akamai’S Q2 2015 <em>State of the Internet Security Report</em></a></li><li>In 2014 alone, there were eight major breaches through the application layer, resulting in more than 450 million personal or financial records stolen.</li><li>60% of a typical enterprise application portfolio comes from third parties, yet 90% of third-party code does not comply with enterprise security standards, such as the OWASP Top 10. — According to <a href="https://www.veracode.com/quocirca-outsourcing-problem-software-security">Quocirca</a> and <a href="https://info.veracode.com/vast-soss.html">Veracode’s <em>State of Software Security Report</em></a></li><li>Veracode’s analysis of more than 5,300 enterprise applications uploaded to its platform over a two-month period found that components introduce an average of 24 known vulnerabilities into each application. — <a href="https://www.veracode.com/open-source-and-third-party-components-embed-24-known-vulnerabilities-every-web-application-average">Veracode’s <em>State of Software Security Report</em></a></li></ul><p>For more details on getting buy-in for your application security program, check out our guide, <a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/cracking-the-code-application-security-buy-in-veracode.pdf"><em>Cracking the Code on Application Security Buy-In</em></a>.</p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/03/why-you-need-your-boss%E2%80%99-buy-application-security"><em>https://veracode.com/blog/...</em></a><strong><em> on March 14, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fbd46a42aa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Apple-FBI Security Lesson: Redundant Protections Are Essential]]></title>
            <link>https://medium.com/@Veracode/the-apple-fbi-security-lesson-redundant-protections-are-essential-18d8b34ca8b9?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/18d8b34ca8b9</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[apple]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Tue, 24 May 2016 19:55:04 GMT</pubDate>
            <atom:updated>2016-05-24T19:55:04.475Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/evan-schuman">Evan Schuman</a></p><p>If there’s one security lesson that can taken from this FBI versus Apple surrealistic encounter, it’s that security redundancy is truly important. We’re talking multi-layered security, where any one or two layers can completely fail and security is still maintained. Why? Let’s look at the latest in the FBI-Apple encryption dance. And if any of you bought into this “this Apple fight is over” rhetoric, you haven’t been paying attention.</p><p>The upshot of the battle: The most secure consumer-grade smartphone in the world — the iPhone from Apple — thwarted all FBI attempts to <em>easily </em>break into the phone, in an attempt to find out more about terrorist. Making the case even more interesting is the fact that the phone’s owner — which happened to be the county government where the terrorist worked — also wanted the contents opened. With all that going for the government, Apple stood its ground on security and refused to weaken the security for everyone to help with this case.</p><blockquote>You want to break in, go for it, but we’re not going to hurt everyone’s security solely to make it easier and cheaper for you to do so.</blockquote><h4>FBI’S GOAL: LOW-COST/LOW-EFFORT</h4><p>What the FBI wanted was a low-cost/low-effort method so that they could cost-effectively break into an unlimited number of phones in the future. Apple’s response was, in effect, “You want to break in, go for it, but we’re not going to hurt everyone’s security solely to make it easier and cheaper for you to do so.”</p><p>Once it became clear that Apple wasn’t going to budge and that the federal courts were unlikely to force them to budge, the FBI, <a href="http://www.nbcnews.com/nightly-news/video/source-israeli-firm-helped-fbi-hack-san-bernardino-terrorist-s-iphone-654582339974">according to NBC News</a>, simply turned to a well-known security firm in Israel, Cellebrite, which has been publicly breaking into iPhones for years. Cellebrite details <a href="http://www.cellebrite.com/Pages/ios-forensics-physical-extraction-decoding-and-analysis-from-ios-devices">its approach</a> on its Web site publicly, even including <a href="https://www.youtube.com/watch?v=NFRAy3PyRx4&amp;feature=youtu.be&amp;rel=0">a video to show how easy their extraction methods are</a> to use.</p><p>It has been argued by others — <a href="http://mobile.eweek.com/mobile/third-party-tech-help-resolves-fbi-apple-standoff-over-killers-iphone.html">including this wonderful narrative piece in eWEEK</a> — that if the FBI knew of this option (and few in the encryption space didn’t), why didn’t it go there initially? The truth is that it costs more and takes longer. The FBI is not solely concerned with their own budget and time, but those of other law enforcement operations, especially metro police departments that often begin these terrorism probes.</p><h4>THE VALUE OF YOUR DATA</h4><p>This brings us back to the security redundancy point. How valuable — to others — is the data you’re protecting? If the data pot of gold at the other end of the firewall rainbow is big enough, cyberthieves can justify pouring major resources and time into cracking your systems. No single security method — regardless of how high-end, how enterprise-grade it is labeled — is perfect.</p><p>The takeaway from the Apple incident is that true corporate security is less about perfection — which is unattainable — and more about making the cost to the attacker so high that it’s simply not worth it. Professional cyberthieves are business people and if your data is worth $100 million on the blackmarket, no professional is going to deploy $200 million worth of effort to get it.</p><p>When you’re calculating this ROI value number, don’t forget that costs to <em>your </em>company — repairing/replacing impacted systems, costs of alerting customers, regulatory paperwork, disruptions to operations, etc. — are not relevant to this calculation. Those are important factors in calculating your company’s exposure to a successful databreach, but to the thief, the only dollar-value at issue is how much the data can be sold for. (Just to infuriate you a little more, your team might be the victim and the prospective customer. That would be the case <a href="https://www.veracode.com/blog/2016/03/hospitals-are-securitys-biggest-nightmare">if the attacker holds your data for ransom</a>.)</p><h4>OUTRUN YOUR TIGER</h4><p>There’s a very old joke about two guys in the jungle who run into a hungry tiger. One of the men immediately starts running and his companion shouts, “You fool! You can never outrun a tiger” to which his friend replies “I don’t have to. I merely have to outrun you.” In corporate IT, you don’t necessarily have to outrun a cyberthief attack. All you have to do is be more resistant than your largest rivals. Cyberthieves, like tigers, have a fondness for easy prey.</p><p>For every layer of redundant security you add, you are exponentially increasing the cost and time needed to successfully break into your system while simultaneously giving your own systems more of a chance to detect and alert you to the attack.</p><p>A lot of enterprises put too much focus — and trust — on external security systems. Although firewalls and authentication systems are essential, never assume that they will always work. A strong application security strategy — one that assumes that at least some of the bad guys will get through, or sidestep, your outer defenses — is critical. Apple’s inner encryption defenses (rules that threatened to block any access attempts if too many unsuccessful attempts were made <em>or </em>if the attempts were spaced too closely) were what slowed down FBI attempts.</p><p>Never assume that any security software works. But that none of six redundant systems will work? That’s a chance worth taking — and one that no thief likely will.</p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/04/apple-fbi-security-lesson-redundant-protections-are-essential"><em>https://veracode.com/blog/...</em></a><strong><em> on April 7, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18d8b34ca8b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google’s Vendor Security Assessment Questionnaire]]></title>
            <link>https://medium.com/@Veracode/googles-vendor-security-assessment-questionnaire-ee4c7ea06d13?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee4c7ea06d13</guid>
            <category><![CDATA[google]]></category>
            <category><![CDATA[supply-chain]]></category>
            <category><![CDATA[web-app-security]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Mon, 02 May 2016 15:14:13 GMT</pubDate>
            <atom:updated>2016-05-02T15:14:13.677Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/anne-nielsen">Anne Nielsen</a></p><p>Software supply chain security has arrived with Google’s <a href="https://github.com/google/vsaq">Vendor Security Assessment Questionnaire</a> (VSAQ)! Or has it? The web-based application released under an open-source license on GitHub contains the actual questionnaire Google uses to review its own software vendors’ security practices before making a purchase.</p><p>I know what you’re thinking: “if it’s good enough for Google, it’s good enough for me!”</p><p>Let me count the ways this is just not true …. three. While a good first step in tackling software supply chain security, it is simply a starting point. You can and should do more if you are purchasing a software product.</p><p>First, VSAQ asks for information on a software vendor and the vendor’s development process, but only lightly touches on the actual software being purchased. This is concerning because, while a company could aspire to best practices on its web application development process, this does not guarantee that these practices were followed.</p><p>Second, a form-assessment such as VSAQ relies on self-attestation: that the vendor is entirely truthful and speaking to the development process of the particular software you want to buy, not just of the ideal process it “tries” to follow.</p><p>If you’re a company looking to purchase software, or software as a service, you should ask your vendor to show you the paperwork created during application security testing (static, dynamic, composition, etc.) that shows proof-positive the risk of that particular application. If your vendor can’t do this, ask it to let you test its software. Either way, get the <em>proof</em> you need, not <em>speculation</em>.</p><p>Finally, as software is assembled from existing components found in libraries such as GitHub, you should require a “bill of materials” from the software vendor so that if future vulnerabilities are found in those components leveraged by its product, you are aware of the risk as soon as possible.</p><p>Form-assessments such as VSAQ, or the SIG or AUP offered from Shared Assessments, are a good place to start. However, to really reduce software supply chain security risk, the software itself must be tested — an approach advocated by the financial services consortium FS-ISAC, in its <a href="https://info.veracode.com/whitepaper-appropriate-software-security-control-types.html">whitepaper</a> on this subject.</p><p>We can help. Our <a href="https://www.veracode.com/services/vendor-application-security-testing">VAST program</a> is designed specifically for this purpose.</p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/03/google%E2%80%99s-vendor-security-assessment-questionnaire"><em>https://veracode.com/blog/...</em></a><strong><em> on March 10, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee4c7ea06d13" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Gets Measured Gets Done: a Motto to Live by in Application Security]]></title>
            <link>https://medium.com/@Veracode/what-gets-measured-gets-done-a-motto-to-live-by-in-application-security-d6bf840f2981?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6bf840f2981</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Mon, 02 May 2016 15:13:42 GMT</pubDate>
            <atom:updated>2016-05-02T15:13:42.570Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/jessica-lavery">Jessica Lavery</a></p><blockquote>Back in December, the CISO <a href="https://www.veracode.com/blog/2015/12/case-anonymous-case-studies">of a financial services</a> company explained how he took his company’s <a href="https://www.veracode.com/blog/2015/12/how-we-took-our-application-security-program-0-60-12-months">application security program from 0–60 in 12 months</a>. Now, that same CISO explains why measurement was a critical component to the program’s success.</blockquote><p>As we developed our application security strategy, gaining buy-in from various stakeholders was an essential part of making it a success. But, we also knew that we’d need to standardize on a set of effectiveness measurement so that we could measure progress and demonstrate that we were reducing risk. Also, I live by the motto “what gets measured gets done”, meaning if we create numerical goals, we are more likely to work toward reaching the goal.</p><p>Once we determined with our stakeholders what our application security program goals were, we created a dashboard of AppSec measures. This quantified the effectiveness of each control we put into place. The highly visible dashboards held us all accountable for the changes we were making, and promoted adoption of new controls across all teams.</p><blockquote>flaws fixed is a positive metric — it reports on the improvements and progress the development team is making</blockquote><p>For example, one of our key initiatives was training our development team on secure coding practices. We knew that doing so would ultimately improve our overall security by reducing vulnerabilities before we even assessed applications. However, we also knew that this is a hurdle many application security programs don’t overcome. Developers are on tight deadlines to produce innovations. From the developer perspective, training programs simply get in the way of productivity and on-time releases. But, by setting up a dashboard measuring training sessions completed on time, we are communicating that training is a priority, not a luxury.</p><p>Many application security programs measure the number of vulnerabilities found. Though this can be a helpful metric for baselining risk, we felt creating a dashboard measuring flaws fixed within an agreed upon SLA was also a worthwhile endeavor. The flaws fixed metric is important because it shows progress toward reducing risk, but it also has a psychological and collaborative benefit. Measuring vulnerabilities found can cause developers to feel like they are being shamed or criticized. After all, you are basically finding all their mistakes and reporting on them. But flaws fixed is a positive metric — it reports on the improvements and progress the development team is making. As a result, our security team is able to have a more cordial relationship with the development team.</p><p>Of course, these are not the only two metrics we reported, we had 1–3 measures established for all of our secure SDLC controls. But they are good examples of how we used metrics to build, refine and iterate our program. Now that we have a solid program in place, we can use these and other metrics to demonstrate the value of the program and explain how expanding the program to cover more of our application portfolio can benefit the company.</p><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/using-metrics-to-manage-your-application-security-program-sans-veracode.pdf">SANS: Using Metrics to Manage Your AppSec Program</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/04/what-gets-measured-gets-done-motto-live-application-security"><em>https://veracode.com/blog/...</em></a><strong><em> on March 31, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6bf840f2981" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 AppSec Mistakes that are Poisoning Your Progress]]></title>
            <link>https://medium.com/@Veracode/9-appsec-mistakes-that-are-poisoning-your-progress-1ca62cdfdeb3?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ca62cdfdeb3</guid>
            <category><![CDATA[web-app-security]]></category>
            <category><![CDATA[ngwaf]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Mon, 02 May 2016 15:13:37 GMT</pubDate>
            <atom:updated>2016-05-02T15:13:37.919Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/julian-totzek-hallhuber">Julian Totzek-Hallhuber</a></p><p>Application security testing is an essential part of a global security strategy but if it is not done the right way it can poison your progress.</p><p>Below I’ll explain the mistakes to avoid in order to test all your applications, find and fix the flaws whilst still creating a global application security programme.</p><h4>1: Only testing the most critical apps</h4><p>In most cases companies believe that testing their most critical apps for vulnerabilities is the right way to go, but in fact most breaches occur because of a vulnerable legacy app that is dormant. There are many real life examples, like the JP Morgan Chase, where a breach occurred due to a vulnerable charity donation website. This website had not been used in a year, yet still access to the corporate database!</p><h4>2: Relying solely on Manual Penetration Testing (MPT)</h4><p>Yes, you are right, MPT may find the logical flaws in applications, but it is absolutely impossible to scale manual pentesting. This would only work for a few applications otherwise you need an army of pentesters to test all your applications all of which costs a lot of time and money. This forces companies to only test their most critical apps, leaving hundreds unassessed and thus vulnerable.</p><h4>3: Assuming software components are secure</h4><p>Software today is a composition of many different things. The biggest parts of applications today are <a href="https://www.veracode.com/blog/2015/02/using-third-party-applications-and-software-libraries-worth-risk">open source components or pre build libraries</a>. Do you know if they have known vulnerabilities? It should always be a priority to check third party components of your software. A very famous third party library for example is OpenSSL and I bet you remember the <a href="https://www.veracode.com/heartbleed-vulnerability">HeartBleed</a> and Freak vulnerabilities!</p><h4>4: Not looking at vendor applications</h4><p>Do you only test you own build code? Do you blindly trust your software vendors that they build secure code — all because they say they do? All software you buy should go through the same process your own goes through.</p><p>Once the software is breached it’s too late. Who will you blame it on? It’s your company’s data and reputation that’s already lost.</p><h4>5: No developer security training</h4><p>If companies won’t train their developers they will make the same mistakes again and again without even knowing it. Software development normally is driven by deadlines not by security, therefore a good security knowledge in the development team is essential to build secure applications at speed.</p><h4>6: No SDLC (Software Development Life Cycle) integration</h4><p>Whenever you consider testing your software for security it also is mandatory to find a way to integrate this process into your SDLC. Developers tend to work in their environments and don’t want to learn new tools in order to test their software. You need to catch the developer in their usual workspace and offer plugins for the tools they already use. Only in this case developers will efficiently integrate into this process and run necessary test as needed.</p><h4>7: Only on-premise solution</h4><p>On premise solutions are so 90ies! Compensate cloud-fear with an effective security approach like data encryption, access control, running applications in memory not on hard disk and several others. Do you really want to add more boxes to your network forcing your infrastructure team to manage even more hardware? Do you want your network security team to manage more outgoing connections in terms of updating? Are you sure the box can handle the amount of scans you are planning? A cloud based solution will not face a single question like this, as it just runs outside your network, automatically scales and no infrastructure or network security will ever be involved.</p><h4>8: No global AppSec programme</h4><p>Especially for large enterprises it should be a high priority to build a full, global application security programme. It doesn’t make sense to have dedicated silos in different countries or even in different development teams. Some developers using tool X, other using service Y and the rest maybe Z. Either management has to hire another overlaying team to manage all of these different types of solutions and services or they have to run results on their own. This means they’re spending an enormous amount of time getting the different data aligned. Why not rely on the same tool for everyone and having an application security programme management service attached to it that helps keep the programme running and delivers the right statistics and reports?</p><h4>9: Think you are secure</h4><p>The biggest problem in application security and the one slowing down the progress is the false sense of being secure. You never will be secure, even if you implemented all above, you always need to adjust from time to time to fit new requirements, new attack vectors will be discovered over time or new programming languages are introduced. So only by living the above and continuously evolving will get you the most out of your applications security efforts.</p><p>Always ask the question — did I do everything I could to secure my applications?</p><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/proving-appsec-performance-using-metrics.pdf">Free eBook: Using Metrics to Build a Case for Application Security</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/03/9-appsec-mistakes-are-poisoning-your-progress"><em>https://veracode.com/blog/...</em></a><strong><em> on March 29, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ca62cdfdeb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is real-time security and why it is needed]]></title>
            <link>https://medium.com/@Veracode/what-is-real-time-security-and-why-it-is-needed-3fd8d94050df?source=rss-f7913a3ebd3------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fd8d94050df</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[web-app-security]]></category>
            <dc:creator><![CDATA[Veracode]]></dc:creator>
            <pubDate>Wed, 27 Apr 2016 14:51:36 GMT</pubDate>
            <atom:updated>2016-04-27T14:51:36.619Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://www.veracode.com/blog/author/joseph-feiman">Joseph Feiman</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*FpsJs8-3L5K3s9WR." /></figure><p>Application security has emerged, evolved, matured and adopted at the programming and testing phases of application lifecycle, not at its operation phase. Technologies for application protection at the operation phase have been adopted at lesser degree and even then they are only adopted with some stipulation.</p><p>This can be explained. Adopting application assessment/vulnerability detection technologies is less risky than adopting application protection technologies.</p><p>Technologies such as static application security testing (SAST), dynamic application security testing (DAST), and software composition analysis (SCA) serve as a good example of assessment technologies. They analyze application source, byte, or binary during the time of assessment or they analyze the presence of 3rd party components in the application. Based on that analysis, application development and security specialists can take remediation actions, such as fixing vulnerabilities in the application code. These actions only impact non-production applications, thus typically posing little to no risk to the usability of the applications.</p><p>Adopting protection technologies that act during the production phase is a much riskier proposition, as doing so can break production applications’ execution, causing an outage or malfunction. Thus, adoption of those technologies has lagged behind detection/testing technologies, and market has tolerated it until recently, when the situation in security has changed.</p><p>Over the last several years, the vector and nature of attacks have transformed. The application layer has increasingly become the main target of attacks. Recent attacks seek to exploit weaknesses in applications to gain unauthorized access to money, data, and possibly control over (such as power grid or water supply systems). These attacks have also become more targeted, and are often supported by governments or terrorist organizations.</p><p><strong>The change of the situation rings alarm, and causes demand for real-time, zero-latency technologies capable of detecting attacks that target running applications and protecting against those attacks.</strong></p><p>For many years, the IT industry substituted a specialized application protection technology with network-based security technologies, mainly with web application firewalls (WAFs). Yet, they have not been broadly adopted, nor are they effective at protecting against application attacks. Those technologies, are network traffic analyzers and as such see applications as black boxes. They do not have insight into applications’ logic flows, database access, data processing or configurations. Due to these deficiencies, they cannot distinguish (with the necessary degree of assurance) between an attack and legitimate access, making them ineffective for true real-time protection. Relying solely upon them is often too risky.</p><p>The deficiencies in network-based protection technologies cannot be overcome. A new approach, a new technology is required. That technology — runtime application self-protection (RASP) — has just emerged.</p><p>Only RASP is <strong>designed </strong>to work at the production phase, with an in-production application. RASP becomes an integral part of the runtime environment, therefore it offers a uniquely deep insight into application logic as well as data flow and thus, with unique accuracy, can detect attacks and protect against them. With this new technology we will see a transformation in the way enterprises protect their applications.</p><p><a href="https://www.veracode.com/sites/default/files/Resources/Whitepapers/what-is-rasp.pdf">Download the What is RASP Infosheet</a></p><p><strong><em>This story was originally published at:<br></em></strong><em> </em><a href="https://www.veracode.com/blog/2016/01/what-real-time-security-and-why-it-needed"><em>https://veracode.com/blog/...</em></a><strong><em> on January 29, 2016.</em></strong><em></em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fd8d94050df" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>