<?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 Synopsys Software Integrity on Medium]]></title>
        <description><![CDATA[Stories by Synopsys Software Integrity on Medium]]></description>
        <link>https://medium.com/@SW_Integrity?source=rss-db4bc0f3950f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3a8t8t6VXp__mNEhIPK2xw.jpeg</url>
            <title>Stories by Synopsys Software Integrity on Medium</title>
            <link>https://medium.com/@SW_Integrity?source=rss-db4bc0f3950f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 01:18:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SW_Integrity/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[Synopsys Software Integrity February 2020 Webinars]]></title>
            <link>https://medium.com/@SW_Integrity/synopsys-software-integrity-february-2020-webinars-bdfedaf3d368?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdfedaf3d368</guid>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[webinar]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Thu, 23 Jan 2020 18:28:22 GMT</pubDate>
            <atom:updated>2020-01-30T16:07:25.612Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/416/1*WkkRde5MWaSGgXGj9ej5-w.jpeg" /></figure><p>Join <a href="https://www.synopsys.com/software-integrity.html">Synopsys Software Integrity</a> in one of our upcoming webinars. This month we’ll discuss modern <a href="https://www.synopsys.com/blogs/software-security/is-your-software-security-strategy-working/?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium">application security programs</a>, <a href="https://www.synopsys.com/software-integrity/security-testing/software-composition-analysis.html?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium">Black Duck</a> on the VMware Cloud Marketplace, and open source scanning. Click on the links below to get more information or to register!</p><p><strong>That’s Not How This Works | <br>Feb. 11 | 1:00 p.m. EDT |</strong><a href="https://www.brighttalk.com/webcast/13983/378727?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium"><strong>Register</strong></a></p><p><a href="https://www.brighttalk.com/webcast/13983/378727?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium">That&#39;s Not How This Works</a></p><p><strong>Synopsys Black Duck is now on the VMware Cloud Marketplace | <br>Feb. 18 | 1:00 p.m. EDT | </strong><a href="https://www.brighttalk.com/webcast/13983/383487?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium"><strong>Register</strong></a></p><p><a href="https://www.brighttalk.com/webcast/13983/383487?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium">Synopsys Black Duck is now on the VMware Cloud Marketplace</a></p><p><strong>Why All Open Source Scans Aren’t Created Equal | Feb. 20 | 12:00 p.m. EDT |</strong><a href="https://www.brighttalk.com/webcast/13983/383035?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium"><strong>Register</strong></a></p><p><a href="https://www.brighttalk.com/webcast/13983/383035?cmp=sm-sig&amp;utm_source=social&amp;utm_medium=medium">Why All Open Source Scans Aren&#39;t Created Equal</a></p><p>Learn more about Synopsys Software Integrity:<a href="https://www.synopsys.com/software-integrity.html">https://www.synopsys.com/software-integrity.html</a></p><p>Subscribe: <a href="https://www.youtube.com/channel/UC0I_hKR1E-Ty0roBUEQN4Ww">https://www.youtube.com/channel/UC0I_hKR1E-Ty0roBUEQN4Ww</a></p><p>Follow us on Twitter: <a href="https://twitter.com/sw_integrity">https://twitter.com/sw_integrity</a></p><p>Like Synopsys Software Integrity on Facebook:<a href="https://www.facebook.com/synopsyssoftwareintegrity">https://www.facebook.com/synopsyssoftwareintegrity</a></p><p>Join us on LinkedIn: <a href="https://www.linkedin.com/showcase/sw_integrity">https://www.linkedIn.com/showcase/sw_integrity</a></p><p>Read our Software Integrity blog:<a href="https://www.synopsys.com/blogs/software-security/">https://www.synopsys.com/blogs/software-security/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdfedaf3d368" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software quality: It can be a matter of life and death]]></title>
            <link>https://medium.com/@SW_Integrity/software-quality-it-can-be-a-matter-of-life-and-death-20b4b4b2fff7?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/20b4b4b2fff7</guid>
            <category><![CDATA[synopsys-software-quality]]></category>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 21:56:01 GMT</pubDate>
            <atom:updated>2020-01-10T21:56:01.190Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*_NTTKXdZ5lnrbPjLZiZg-Q.png" /></figure><p>Was there ever any doubt that defective software could kill people — lots of people? If there was, two catastrophic Boeing 737 MAX 8 jetliner crashes erased it. But so far, there is scant evidence that these tragedies have revolutionized software development. That’s a tragedy itself, given the availability of methods and tools to <a href="https://www.synopsys.com/blogs/software-security/safety-critical-software/">eliminate defects in safety-critical software</a>.</p><h3>How to build better safety-critical software</h3><p>The situation is a stark reminder that modern society is increasingly dependent on the quality and security of software. We look to software not only to provide convenience but also to protect our lives and ensure our safety.</p><p>Organizations can ensure the <a href="https://www.synopsys.com/blogs/software-security/code-quality-code-security/">quality and security</a> of safety-critical software in a variety of ways. But they’re all related to the concept of building software integrity in during development. Many organizations rely on the alternative: bolting or patching it on at the end. But in the long run, “shifting left” makes it cheaper and faster to build a superior product.</p><p>Shifting left requires the use of multiple testing and analysis tools throughout the SDLC. Another essential tool is software composition analysis, which helps developers uncover known bugs and vulnerabilities in open source components.</p><h3>Slow is fast in software development</h3><p>Numerous experts have warned that there is no such thing as software that is fast, cheap, and good. It’s a dangerous, potentially lethal, fantasy. The irony is that trying to go “fast and cheap” in the development of software yields the opposite results.</p><p>“The phrase ‘slow is fast’ is well known in engineering circles,” said Eric Elliott, an author and distributed systems expert, in <a href="https://medium.com/javascript-scene/why-cutting-costs-is-expensive-how-9-hour-software-engineers-cost-boeing-billions-b76dbe571957">a post on Medium</a>. “It has origins in the military phrase ‘slow is smooth and smooth is fast,’ and it’s a form of uncommon sense.” As in lifesaving common sense. <a href="https://www.synopsys.com/blogs/software-security/safety-critical-software/">Read more about safety-critical software.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20b4b4b2fff7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Synopsys Burlington Career & Networking Event — RSVP!]]></title>
            <link>https://medium.com/@SW_Integrity/synopsys-burlington-career-networking-event-rsvp-6e93ce7904cb?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e93ce7904cb</guid>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[software-career]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[synopsys-careers]]></category>
            <category><![CDATA[career-technology]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 19:14:24 GMT</pubDate>
            <atom:updated>2020-01-10T19:14:24.264Z</atom:updated>
            <content:encoded><![CDATA[<h3>Synopsys Burlington Career &amp; Networking Event — RSVP!</h3><figure><a href="https://www.eventbrite.com/e/burlington-career-and-network-event-tickets-86745495111&amp;cmp=sm-sig?utm_source=social&amp;utm_medium=medium"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iBFysJ2xj0ohYgihMssiAg.jpeg" /></a><figcaption>Register now!</figcaption></figure><p>Synopsys wants you to join our Software Integrity team! Join us on Tuesday, January 28, 2020 for an evening of guest speakers, prizes, networking, and food drink! <a href="https://www.eventbrite.com/e/burlington-career-and-network-event-tickets-86745495111&amp;cmp=sm-sig?utm_source=social&amp;utm_medium=medium"><strong>RSVP!</strong></a></p><p>Visit our careers page to learn more about the open positions within our Software Integrity Group: <a href="https://www.synopsys.com/company/synopsys-careers.html">https://www.synopsys.com/company/synopsys-careers.html</a></p><p>Learn more about Synopsys Software Integrity:<a href="https://www.synopsys.com/software-integrity.html">https://www.synopsys.com/software-integrity.html</a></p><p>Subscribe: <a href="https://www.youtube.com/channel/UC0I_hKR1E-Ty0roBUEQN4Ww">https://www.youtube.com/channel/UC0I_hKR1E-Ty0roBUEQN4Ww</a></p><p>Follow us on Twitter: <a href="https://twitter.com/sw_integrity">https://twitter.com/sw_integrity</a></p><p>Like Synopsys Software Integrity on Facebook:<a href="https://www.facebook.com/synopsyssoftwareintegrity">https://www.facebook.com/synopsyssoftwareintegrity</a></p><p>Join us on LinkedIn: <a href="https://www.linkedin.com/showcase/sw_integrity">https://www.linkedIn.com/showcase/sw_integrity</a></p><p>Read our Software Integrity blog:<a href="https://www.synopsys.com/blogs/software-security/">https://www.synopsys.com/blogs/software-security/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e93ce7904cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why your SAST tool needs to understand your web framework]]></title>
            <link>https://medium.com/@SW_Integrity/why-your-sast-tool-needs-to-understand-your-web-framework-e3a34e256501?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3a34e256501</guid>
            <category><![CDATA[sast]]></category>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-framework]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Fri, 10 Jan 2020 16:16:01 GMT</pubDate>
            <atom:updated>2020-01-10T16:16:01.264Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*J4AaZKBZqwkYjuzYzPV1hA.jpeg" /></figure><p>With so many web frameworks available, it’s no surprise that framework code often makes up most of the code in an application. But this also means framework code comes from a range of sources. How can you <a href="https://www.synopsys.com/blogs/software-security/web-framework-security-static-analysis/">ensure that web framework code doesn’t introduce security vulnerabilities</a> into your application?</p><p>Security tools must be able to understand framework code and how it interacts with the applications they scan. Static analysis is a leading security mechanism used to identify vulnerabilities in source code before deployment. It allows security to shift to the earliest phases of development, reducing the time and cost needed to resolve the vulnerabilities it identifies.</p><h3>Control flow analysis</h3><p>A substantial challenge in analyzing framework-based applications for vulnerabilities is understanding the flow of control between the framework code and application code. Traditionally, applications call into libraries as needed. Modern web frameworks invert this control model. Instead, the framework and its components become the main body of the application, transferring control into your application at specific points in specific contexts.</p><p>Control flow across subsystems can pass data, possibly tainted, from the web, into the framework, and onto the application. Tainted data coming in from untrusted sources is a potential source of injection attacks. Other security issues related to web framework code include buffer handling, certificate management, credential management, insecure connection settings, and path manipulation scenarios. Look for a static analysis tool that detects all of these, as well as issues with authorization, hard-coded passwords, certificate usage, insecure (non-SSL) communication, and issues relating to leakage of sensitive data.</p><p><a href="https://www.synopsys.com/blogs/software-security/web-framework-security-static-analysis/">Learn more about how to ensure web framework security using static analysis.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3a34e256501" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What to do after a cyber security acquisition]]></title>
            <link>https://medium.com/@SW_Integrity/what-to-do-after-a-cyber-security-acquisition-8217d818f8d9?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/8217d818f8d9</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[security-testing]]></category>
            <category><![CDATA[appsec-testing]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 20:06:01 GMT</pubDate>
            <atom:updated>2020-01-08T20:06:01.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*490gcaYF5t_PiHJQ61qaOw.jpeg" /></figure><p><em>A </em><a href="https://www.synopsys.com/blogs/software-security/cyber-security-acquisition/">cyber security acquisition</a><em> can be a great deal for investors, but what about users? Here’s what to do if your application security tool has been acquired.</em></p><p><strong>Review your contract. </strong>Have your legal team look at the contract to understand your options, including the ability to revisit the contract in an M&amp;A situation.</p><p><strong>Understand the drivers.</strong> Do some research to understand the drivers behind the acquisition. Sometimes companies acquire tools to shut them down and gain market share (e.g., <a href="https://www.theverge.com/2018/7/26/17619482/slack-hipchat-acquisition-stride-atlassian-partnership-microsoft-teams-competition">Slack’s acquisition of HipChat</a>). In such cases, you need to prepare for change.</p><p><strong>Know your standards and regulations.</strong> Some sectors, like government, have strict regulations for working with companies in particular countries. For example, Indian company <a href="https://www.hcltech.com/press-releases/press-releases-business/hcl-technologies-announces-close-acquisition-select-ibm">HCL’s acquisition of AppScan</a> may raise concerns for U.S. intelligence communities who share information only with select countries and may take issue with sensitive data being housed by companies outside that group.</p><p><strong>Assess the impact. </strong>Every merger or acquisition brings some changes. Assess the impact on your business. Were you waiting on any major product updates? Could product consolidations affect your existing integrations? Are you no longer able to fulfill certain regulation or compliance needs owing to the merger or acquisition of your vendor?</p><p><strong>Evaluate your options and make a decision. </strong>If you anticipate significant changes as a result of the merger or acquisition, this is your opportunity to move on to something better.</p><p><a href="https://www.synopsys.com/blogs/software-security/">Learn more about what to do if your cyber security tool or vendor has been acquired.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8217d818f8d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chain Heist and blockchain security at DEF CON 2019]]></title>
            <link>https://medium.com/@SW_Integrity/chain-heist-and-blockchain-security-at-def-con-2019-369b5703e36d?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/369b5703e36d</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[synopsys-at-defcon]]></category>
            <category><![CDATA[capture-the-flag]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 15:56:01 GMT</pubDate>
            <atom:updated>2020-01-08T15:56:01.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*4KaBH7BuQgiOCHNXSr1uLw.jpeg" /></figure><p>This year DEF CON introduced a variety of “villages,” which function as mini-conferences, focusing on areas like blockchain, cryptography, and digital currencies. A central component of these villages was hands-on learning experience in the form of workshops and competitions. The Synopsys <a href="https://www.synopsys.com/software-integrity/cybersecurity-research-center.html">Cybersecurity Research Center (CyRC)</a> coordinated one such event: the <a href="https://www.synopsys.com/blogs/software-security/chain-heist-blockchain-security/">Chain Heist blockchain capture-the-flag (CTF) challenge</a>.</p><h3>The Chain Heist blockchain CTF</h3><p>The Chain Heist award was 11 Ethereum (approximately $2,500 at the time of the competition) to the participant who could identify and exploit the most security vulnerabilities in a series of blockchain-based challenges. Our goal was to build a challenge containing real-world vulnerabilities from both public sources of famous blockchain hacks and our experience working with clients building enterprise blockchain applications. The result was a demanding set of 23 challenges that required participants to stretch their capabilities and encouraged them to discover these vulnerabilities for themselves.</p><h3>State of the art in blockchain security</h3><p>Blockchain is still a niche area with few experts. Those who are familiar with blockchain are speaking loudly about it, but it has been slow to pick up steam beyond the cryptocurrency craze. The low-hanging fruit lies just out of reach for people who have yet to dive into the technology.</p><p>The blockchain village at DEF CON gave a sneak peek into state-of-the-art <a href="https://www.synopsys.com/software-integrity/solutions/by-security-need/blockchain-security.html">blockchain application security</a>. While many blockchain projects are open source or freeware, they’re still very limited in application, and interpretation of results is critical. Even the developers of these tools admit that simply having the tool isn’t sufficient. What’s also necessary is a trained eye for detail and an understanding of the underlying technology.</p><p><a href="https://www.synopsys.com/blogs/software-security/chain-heist-blockchain-security/">Read more about our blockchain CTF at DEF CON.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=369b5703e36d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The different types of application security vulnerabilities]]></title>
            <link>https://medium.com/@SW_Integrity/the-different-types-of-application-security-vulnerabilities-11e68d2b945e?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/11e68d2b945e</guid>
            <category><![CDATA[synopsys-software]]></category>
            <category><![CDATA[web-application-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[appsec-testing]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 20:51:01 GMT</pubDate>
            <atom:updated>2020-01-07T20:51:01.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*gDn-WsT--6LkGFYCbI9NIQ.jpeg" /></figure><h3>What is an application security vulnerability?</h3><p>An application security vulnerability is a security bug, flaw, error, fault, hole, or weakness in software architecture, design, code, or implementation that can be exploited by attackers.</p><p>Security vulnerability lists like <a href="https://www.owasp.org/index.php/Category:OWASP_Top_Ten_Project">OWASP Top 10 Most Critical Web Application Security Risks</a> and the similar <a href="https://cwe.mitre.org/top25/">CWE/SANS Top 25 Most Dangerous Software Errors</a> are helpful for developers who want to learn how to secure their code. These lists lay out the most critical types of security vulnerabilities to keep in mind as you develop software.</p><p>But some application vulnerabilities warrant more scrutiny and mitigation efforts than others. So let’s<em> take a closer look at the </em><a href="https://www.synopsys.com/blogs/software-security/types-of-security-vulnerabilities/">different types of security vulnerabilities</a><em>.</em></p><h3>What are the different types of security vulnerabilities?</h3><p>OWASP is well known for its <a href="https://www.synopsys.com/blogs/software-security/owasp-top-10-application-security-risks/">top 10 list of web application security risks</a>. But the <a href="https://www.owasp.org/index.php/Category:Vulnerability">organization’s website</a> also lists dozens of entries grouped into 20 types of security vulnerabilities. Categories include <a href="https://www.owasp.org/index.php/Category:API_Abuse">API Abuse</a>, <a href="https://www.owasp.org/index.php/Category:Input_Validation_Vulnerability">Input Validation Vulnerability</a>, and <a href="https://www.owasp.org/index.php/Category:Session_Management_Vulnerability">Session Management Vulnerability</a>. OWASP’s application vulnerability descriptions talk about risk factors, give examples, and cross-link to related attacks, vulnerabilities, and controls.</p><p><a href="https://cwe.mitre.org/top25/">MITRE and the SANS Institute</a> put together the latest CWE/SANS Top 25 list in 2011. In that list, they categorize three main types of security vulnerabilities based their more extrinsic weaknesses: porous defenses, risky resource management, insecure interaction between components. <a href="https://www.synopsys.com/blogs/software-security/types-of-security-vulnerabilities/">Read more about these types of security vulnerabilities.</a></p><figure><a href="https://www.synopsys.com/software-integrity/resources/ebooks/application-security-weakness-anatomy.html?intcmp=sig-medium-weakness"><img alt="" src="https://cdn-images-1.medium.com/max/468/1*Rwdne8A2GqIkBmUhztrKkw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11e68d2b945e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top cloud migration security risks]]></title>
            <link>https://medium.com/@SW_Integrity/top-cloud-migration-security-risks-ec17b3227950?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec17b3227950</guid>
            <category><![CDATA[cloud-security-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Tue, 07 Jan 2020 15:51:01 GMT</pubDate>
            <atom:updated>2020-01-07T15:51:01.591Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*RoPivec7tgabQtRHCQBxHw.jpeg" /></figure><p>Organizations moving to the cloud are mindful of the security risks inherent in both cloud computing and the migration process. But there’s a lot of contradicting information about the top security risks of moving to the cloud.</p><p>If you’re planning to <a href="https://www.synopsys.com/blogs/software-security/cloud-migration-business/">migrate business operations to the cloud</a>, what should you be most concerned about? The security of the software, platform, and infrastructure offered by your cloud service provider? The security of your own applications and processes? What poses the greatest cloud migration security risk: data exposure, misconfiguration, <a href="https://www.synopsys.com/blogs/software-security/regulatory-compliance-challenges/">regulatory compliance</a>, policy and strategy, or something else entirely?</p><p>We’ve rounded up some expert opinions about the <a href="https://www.synopsys.com/blogs/software-security/top-cloud-migration-security-risks/">top security risks during cloud migration</a> that organizations should keep in mind.</p><h3>Focus on access, compliance, and monitoring</h3><p>I would say the top three are:</p><ul><li>Proper setup and protection of user identities while accessing the cloud</li><li>Ensuring your cloud computing is compliant with applicable regulations and policies</li><li>Establishing proper logging, monitoring, and analysis of security events in the cloud</li></ul><p><a href="https://twitter.com/chenxiwang?lang=en">— Chenxi Wang</a>, founder and general partner, Rain Capital</p><h3>Compliance and configuration are concerns</h3><p>While changes to applications and the underlying cloud services are introduced increasingly frequently, in most cases there are no controls that validate the security and compliance of cloud services configuration changes beyond day one. The manual, “day one” or “point in time” type of compliance and validation of cloud services configuration become increasingly insufficient for public cloud workloads, as was demonstrated by a slew of recent data breaches in financial institutions that were associated with cloud services misconfigurations.</p><p><a href="https://www.linkedin.com/in/talavren/">— Tatiana Lavrentieva</a>, cloud security and operations practice lead, Synopsys</p><p><a href="https://www.synopsys.com/blogs/software-security/top-cloud-migration-security-risks/">Read more about the top cloud migration security risks.</a></p><figure><a href="https://www.synopsys.com/software-integrity/resources/analyst-reports/security-in-the-cloud.html?intcmp=sig-medium-cloudreport"><img alt="" src="https://cdn-images-1.medium.com/max/468/1*cr6xUl-bYJ4VRiyeOpFNxQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec17b3227950" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What software security activities are in your security program?]]></title>
            <link>https://medium.com/@SW_Integrity/what-software-security-activities-are-in-your-security-program-93450aab3c3?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/93450aab3c3</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[bsimm]]></category>
            <category><![CDATA[software-security]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 20:41:01 GMT</pubDate>
            <atom:updated>2020-01-06T20:41:01.726Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/846/1*wpwdE3jfG6OIBL8TzefyfA.jpeg" /></figure><p>If you’ve heard of the BSIMM, you know it’s the best way to measure your software security initiative (SSI) year after year to see how it’s evolving and how your SSI compares to that of other firms in your industry. The latest version,<em> </em>BSIMM10, compiles a decade of research on <a href="https://www.synopsys.com/blogs/software-security/bsimm10-software-security-activities/">software security activities</a> in real-life firms into a guide for maturing your software security initiative. Here are three patterns that emerged in this year’s report:</p><h3>DevOps is changing software security</h3><p><a href="https://www.synopsys.com/blogs/software-security/agile-cicd-devops-difference/">Agile, CI/CD, and DevOps</a> are speeding up development and driving the use of automation. In response, firms are changing the way they approach the software security activities they perform. We’ve updated many of the BSIMM activity descriptions and added three new activities that demonstrate how firms are actively working to match the speed of software security to the speed of software delivery.</p><h3>Engineers are leading security efforts</h3><p>BSIMM10 is our first study to formally reflect changes in SSI culture. Governance-led cultures, where centralized software security groups lead software security efforts from the top down, were once dominant. Now we’re seeing more engineering-led cultures, where development and operations teams drive software security efforts from the bottom up. Just in the past few years, engineering-led security culture has established and grown meaningful software security efforts in some organizations.</p><h3>Software security initiatives evolve through 3 phases</h3><p>BSIMM10 shows that organizations can improve over time. Many mature to the point where they strive to expand existing software security activities rather than always adding new ones. BSIMM10 is the first BSIMM report to define three phases of <a href="https://www.synopsys.com/blogs/software-security/software-security-initiative-fundamentals/">software security initiative</a> maturity — emerging, maturing, and optimizing. BSIMM10 also demonstrates how both governance-led and new engineering-led cultures can progress through these phases. <a href="https://www.synopsys.com/blogs/software-security/bsimm10-software-security-activities/">Learn more about BSIMM10.</a></p><figure><a href="https://www.bsimm.com/download.html?intcmp=sig-medium-bsimm"><img alt="" src="https://cdn-images-1.medium.com/max/468/1*G2v9vRCmUSldRds9WHdz4g.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93450aab3c3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Questions about fuzz testing? We’ve got answers]]></title>
            <link>https://medium.com/@SW_Integrity/questions-about-fuzz-testing-weve-got-answers-237fd35aedae?source=rss-db4bc0f3950f------2</link>
            <guid isPermaLink="false">https://medium.com/p/237fd35aedae</guid>
            <category><![CDATA[fuzz-testing]]></category>
            <category><![CDATA[software-security]]></category>
            <dc:creator><![CDATA[Synopsys Software Integrity]]></dc:creator>
            <pubDate>Mon, 06 Jan 2020 14:38:37 GMT</pubDate>
            <atom:updated>2020-01-06T14:38:37.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*6BE5C3RQp68tPXcyeTC7pg.jpeg" /></figure><p>Do you have questions about fuzz testing? We’ve got answers, explanations, and recommendations from our last <a href="https://www.brighttalk.com/webcast/13983/365228">webinar on fuzzing</a> using agent instrumentation.</p><h3>How do you know when to stop fuzzing?</h3><p>It comes down to metrics. <a href="https://www.synopsys.com/software-integrity/security-testing/fuzz-testing.html">Fuzzing</a> has an infinite space issue in the sense that it’s negative testing. That means you can have an arbitrary number of test cases. For example, if you take one field in a packet and insert a single character, say ‘A,’ that’s a test case. Insert two A’s, and that’s a test case. Insert three, four, up to one billion A’s, and those are all test cases. It looks very fancy on marketing slides to have one billion test cases for this field. But it doesn’t make much sense to execute them all.</p><p>First, a good fuzzer should have high-quality anomalies. The normalization database should contain anomalies that are likely to trigger issues when inserted into various parts of the code.</p><p>Second, if you set up the instrumentation correctly, you’ll know whether and how a specific function crashes. Then you won’t have to execute more test cases to trigger that bug. For example, if you trigger an overflow on a field, you won’t waste your time executing a hundred more test cases on that field.</p><p>It’s also about coverage. The fuzzer should understand the protocol it’s testing against and create test cases that cover the entire breadth of the protocol. It should also go very deep to the protocol stage while executing test cases.</p><p><a href="https://www.synopsys.com/blogs/software-security/fuzz-testing-questions-answers-recommendations/">Read more fuzz testing questions and answers.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=237fd35aedae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>