<?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 RiskRecon on Medium]]></title>
        <description><![CDATA[Stories by RiskRecon on Medium]]></description>
        <link>https://medium.com/@riskrecon?source=rss-c8ebf4291123------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*9wEqzxPeerXz8sTi.jpg</url>
            <title>Stories by RiskRecon on Medium</title>
            <link>https://medium.com/@riskrecon?source=rss-c8ebf4291123------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:04:12 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@riskrecon/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[Part 1: Are Your Vendors Walking the Walk?]]></title>
            <link>https://medium.com/@riskrecon/part-1-are-your-vendors-walking-the-walk-64dac0096d17?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/64dac0096d17</guid>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[vendor-management]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Sat, 08 Jul 2017 01:05:04 GMT</pubDate>
            <atom:updated>2017-07-08T01:05:04.176Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1: Are Your Vendors Walking the Walk? Confronting Risk Realities: Your Measurements Are Incomplete</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*WKh5fiUoVCHS7PIE." /></figure><p><em>You just received an updated security attestation from your third-party provider, but the hair on your arms stands straight up when news of the latest hack appears on your screen. Your vendors may talk the talk, but you anxiously wonder if they’re walking the walk. Checklist compliance is not good enough. It’s time to confront your risk reality. In part one of this two-part blog series, we look at risk measurement.</em></p><p>Today’s enterprise IT environment is a complex, growing ecosystem of internal systems and processes integrated with third-party providers and partners that host your sensitive data. You depend on these vendors to successfully operate your business and drive growth. But this interdependent ecosystem has created a large attack surface and set of potential vulnerabilities outside of your direct control. Moreover, your current IT governance, measurement and control procedures are not adequately designed to measure and manage these third-party risks.</p><p>What is the Reality of Your Risk Measurements?</p><p>As you already recognize, it’s up to you to effectively and objectively assess the quality of third-party providers’ security. Vetting new vendors is standard operating procedure. Like most companies, your files are stuffed with the typical partner attestations, collected questionnaires, security documentation and information security certifications that are intended to reflect a company’s security effectiveness. For the highest risk vendors, you may even conduct on-site assessments.</p><p><em>Do these security attestations provide the transparency and accountability necessary to ensure your risk interests are properly protected?</em></p><p>Probably not — for the same reasons that we don’t ask students to grade their own report cards, or give employees raises based solely on self-assessments. It’s hard for vendors to be objective about their own security performance and both parties are eager to complete contracts and achieve business objectives. Whether due to blind spots from shadow IT, poor adherence to their own documented practices, or over-reliance on checklist compliance measures, vendor attestation is not sufficient. Why settle only for point-in-time vendor self-assessments when there’s so much at stake?</p><p>Assessing your vendor risk reality requires objective, frequent measurements to compliment and verify the vendor survey and attestation results. With objective measurements you can more easily:</p><ul><li>Make it <strong>easy to see if your vendors’ security performance</strong> is getting better or worse. Quantitative scores are clear indicators of good, better and best performance.</li><li><strong>Pinpoint potential exposures</strong> and root causes for a wide range of security criteria. Verifiable, objective data allows you to develop trust and discuss specific areas for further investigation.</li><li><strong>Benchmark</strong> your vendors against industry best practices while tracking <strong>historical trends</strong> for your overall portfolio and each individual provider.</li></ul><p>Obtaining assessments of any organization’s security practices quickly enables you to measure and control third party risk by confirming that vendors are adhering to their own documented practices.</p><p>Measurement is a critical component of your risk management practices. Accurate and verifiable scores allow you to establish a baseline and document progress, ensuring more comprehensive third-party risk management to support your business objectives.</p><p><em>RiskRecon’s SaaS solution enables organizations to bring greater transparency and accountability to their risk management programs by providing actionable, objective and continuous information on the security posture of their vendors. We do the heavy lifting, providing you actionable, detailed security analysis of each partner in your portfolio, all with push-button ease. Clients trust us to measure security program quality, improve productivity, and ensure accountability among all stakeholders.</em></p><p>Ready to confirm your vendors walk their talk? Contact us today! Or to read part two on Confronting Risk Reality, <a href="http://blog.riskrecon.com/are-your-vendors-walking-the-walk-confronting-third-party-risk-realities-process">click here.</a></p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/are-your-vendors-walking-the-walk-confronting-third-party-risk-realities-measurement"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64dac0096d17" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles for Fair and Accurate Security Ratings]]></title>
            <link>https://medium.com/@riskrecon/principles-for-fair-and-accurate-security-ratings-ae1072ada547?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae1072ada547</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[security-ratings]]></category>
            <category><![CDATA[third-party]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Wed, 21 Jun 2017 13:30:42 GMT</pubDate>
            <atom:updated>2017-06-21T13:30:42.638Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/684/1*8JGFc6Pf9z90leqSDrefag.jpeg" /></figure><p>The U.S. Chamber of Commerce just issued <a href="https://www.uschamber.com/above-the-fold/why-we-need-fair-and-accurate-cybersecurity-ratings">“Principles for Fair and Accurate Security Ratings.” </a>These ratings are the first-of-its-kind guidelines for an emerging class of solutions that provide objective assessments of third-party security practices. These solutions complement traditional third-party risk management data gathering processes of vendor security questionnaires, attestation document reviews, and on-site assessments.</p><p>The principles are the result of a collaborative effort between large American financial and non-financial companies and the leading vendor security assessment companies such as RiskRecon. We at RiskRecon wish to thank the Chamber and these institutions for taking the lead in bringing key stakeholders together to establish practical guidelines.</p><p><strong>What Is the Purpose?<br></strong>The <a href="https://www.uschamber.com/above-the-fold/why-we-need-fair-and-accurate-cybersecurity-ratings">Chamber document</a> itself states: “As security ratings continue to mature, more organizations in the public and private sectors leverage them in making business and risk decisions. As a key piece of a robust security evaluation program, security ratings based on accurate and relevant information are useful tools in evaluating cyber risk and facilitating collaborative, risk-based conversations between organizations.”</p><p>At RiskRecon, we share these same goals of producing useful insights to complement and dramatically improve any organization’s existing third-party risk management program.</p><p><strong>What Are the Principles?<br></strong>The collaborative process has produced six core principles:</p><ol><li>Transparency</li><li>Dispute, Correction and Appeal</li><li>Accuracy and Validation</li><li>Model Governance</li><li>Independence</li><li>Confidentiality</li></ol><p>The full description of each principle is available on the Chamber’s <a href="https://www.uschamber.com/above-the-fold/why-we-need-fair-and-accurate-cybersecurity-ratings">website</a>.</p><p><strong>RiskRecon’s Perspective<br></strong>We’re pleased to see a growing recognition that third-party ratings and security assessment solutions should be “a key piece of a robust security evaluation program.” And we appreciate being just one of the few service providers asked to participate in this process.</p><p>We were active contributors to the process and believe principles like these are vital to ensuring appropriate buy-in and trust among the stakeholders involved in any third-party (and fourth-party) risk assessment program.</p><p>From our founding, we have adhered to the spirit of all six principles. And we also fundamentally believe that solutions must provide a high level of accuracy and “actionability” to ensure organizations can scale their program to address the changing IT landscape.</p><p>The Chamber’s principles align closely with how we at RiskRecon describe our solution capabilities:</p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/principles-for-fair-and-accurate-security-ratings"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae1072ada547" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2017 Outlook: Vendor Risk Continues as a Top Challenge Faced by CISOs]]></title>
            <link>https://medium.com/@riskrecon/2017-outlook-vendor-risk-continues-as-a-top-challenge-faced-by-cisos-800554f01b29?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/800554f01b29</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[third-party]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[ciso]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Mon, 12 Jun 2017 14:29:08 GMT</pubDate>
            <atom:updated>2017-06-12T14:29:08.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/682/1*T1sw7AnwYFYraj-76xRLeQ.jpeg" /></figure><p><em>CISOs know that security risks abound. But objectively measuring risk and balancing it against the needs of the business is essential. Third-party risk provides a perfect case in point and spotlights one of the top challenges facing CISOs today.</em></p><p>Take the shift to cloud infrastructure as an example. It makes obvious business sense to allow your company to reduce its operational footprint to reduce costs to deploy, maintain and support critical IT functions. Local or decentralized IT and line of business areas are now often able to procure SaaS solutions on their own, entirely bypassing the formal IT governance process. From a security perspective, this introduces a larger external footprint and leaves your organization exposed to hard-to-measure inherent risks and controls.</p><p>At the same time, the methods for assessing and mitigating vendor risk aren’t working. They don’t scale to meet the rapid growth in the volume of protected data, systems and vendors. And, there is growing pressure from regulators, boards and institutional investors to shift to more frequent and comprehensive third party risk monitoring</p><p><strong>Third Party Risk Realities</strong></p><p>We all need to face a new reality. Assessing and mitigating risk associated with third parties cannot be solved in solely a manual fashion anymore. This combination of a larger external footprint and a need for scalable continuous monitoring means it’s just not possible to hire the volume of sufficiently trained people needed, or to pen test every one of your vendors. Spreadsheets and surveys simply don’t scale or provide sufficient objective information.</p><p>Certain elements of the scalability problem are being addressed by streamlining current methods, but these are just Band-Aids that don’t address the fundamental changes in the nature and scope of third party risks.</p><p>With current spreadsheets and surveys:</p><ul><li>Do you know whether a third party’s performance improves or degrades over time?</li><li>Do you have an aggregated view of how all your third parties together impact your overall security posture?</li><li>Can you identify and be alerted at moment when there is material change in third party’s attack surface area?</li></ul><p>We need smarter, more objective ways to manage this risk continuously and at scale.</p><p><strong>Why Change?</strong></p><p>The methods currently being employed to assess and mitigate third party risk are no longer working, for several reasons:</p><ul><li>Increased use of third party vendors pivots the decisions made by security practitioners from “what do we fix first?” to “who do we assess first and what is the appropriate level of assessment?”</li><li>Time is an extremely limited resource. Having more insights into your risk enables you to decide what you can accept, so that you can prioritize your focus on what is most important.</li><li>Throwing more people at the problem is not a fix; the problem isn’t the number of assessments being performed, it’s fundamentally about the tools and methods being employed to assess and prioritize risk.</li></ul><p>There is a need for automation and continuity in information gathered for risk assessment.</p><p><strong>Modern Monitoring and Mitigation</strong></p><p>All vendors are not equal when it comes to security practices and risk. Yet security practitioners treat most vendors the same until an issue is reported. Organizations need to establish a repeatable process to prioritize vender risk and manage appropriately, while still maintaining a common threshold of continuous risk monitoring. Then, automate risk monitoring to alert you when significant change occurs.</p><p>By analyzing trends, you can determine the vendors with whom you have a strong level of trust, and which need to be watched more closely. And, automation provides the measurement precision and direct evidence required to produce actionable results.</p><p>The answer to modernizing your 3rd party risk management is to implement a comprehensive risk program that blends attestation, assessments and automation that scales to continuously assess, measure, and monitor your extended risk surface.</p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/2017-outlook-vendor-risk-continues-as-a-top-challenge-faced-by-cisos"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=800554f01b29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 2: Incorporating Continuous Monitoring into Your Third-Party Risk Management Program: The…]]></title>
            <link>https://medium.com/@riskrecon/part-2-incorporating-continuous-monitoring-into-your-third-party-risk-management-program-the-4c67d569fd4?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c67d569fd4</guid>
            <category><![CDATA[third-party]]></category>
            <category><![CDATA[vendor-risk]]></category>
            <category><![CDATA[continuous-monitoring]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Fri, 09 Jun 2017 19:46:58 GMT</pubDate>
            <atom:updated>2017-06-09T19:49:05.901Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 2: Incorporating Continuous Monitoring into Your Third-Party Risk Management Program: The Pilot is Complete — Now What?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/689/1*fWLDtP7m6vDr8l0LTK0Cvw.jpeg" /></figure><p><em>One of the most common questions we’re asked is how to incorporate continuous monitoring into a third-party risk management program. In </em><a href="http://blog.riskrecon.com/incorporating-continuous-monitoring-into-your-third-party-risk-management"><em>part one</em></a><em> of this two-part blog, we discussed beginning with the end state in mind to establish goals for your continuous monitoring program and suggested you jumpstart your program with a pilot. So once the pilot is complete, now what?</em></p><h3>Making Your Risk Management Software Work For You</h3><p>The wheels are in motion. You’ve developed a reasonably good understanding of how to incorporate your new continuous risk assessment solution into your process, and have portfolio-level understanding of your vendor risks. Now, you want to take what you learned from the pilot and expand and mature your risk-adjusted vendor management model. And, you want to begin tracking suppliers and 4th parties that are currently unmanaged.</p><p>Your next step is to roll out the continuous risk assessment process and monitoring solution to your remaining managed vendors. Begin by engaging these vendors as their annual assessments occur, and establish thresholds in your monitoring program that alert you if a vendor deviates materially in between assessment periods. Over time, this historical monitoring information will help you establish a baseline of trust for each vendor. In addition, you should continue to add unmanaged suppliers and 4th parties to your continuous monitoring process.</p><p>Meanwhile, if you have not already done so, begin leveraging the objective, third-party data reports into your RFP process. You now have a rapid and actionable way to assess vendors during the proposal process (before they are contracted with) to help in the selection and to identify potential risks.</p><p>Your assessment provider’s continuous monitoring and alerting capabilities should be integrated into your incident response process so that you can easily identify material changes that occur in between the standard assessment process. And when ‘celebrity vulnerabilities’ emerge, leverage the capabilities of your continuous monitoring provider to identify the specific third parties and systems exposed to this new threat. You will likely need to partner with your security and vulnerability management peers who may own or assist with investigation and response.</p><h3>Continuous Improvement is Essential in Vendor Risk Management</h3><p>With the passage of time, you will accumulate historical data on all managed vendors. And with the help of your assessment provider, you should also accumulate risk assessments for your unmanaged vendors and fourth parties. These assessments give you the necessary information to prioritize, in terms of size and scope, the inherent risk and historical quality of each vendor’s security practices.</p><p>As our clients accumulate sufficient historical evidence, they typically find many ways to develop more productivity and control in their process.</p><ul><li>Receiving actionable information allows each analyst to cover more vendors as they spend less time preparing for assessments and can quickly pinpoint where to focus their efforts.</li><li>Using historical risk and objective data already known about each vendor permits risk-adjusted frequency of the survey and attestation process.</li><li>Similarly, clients can tailor the number of steps and overall assessment scope with the information provided by their continuous monitoring program.</li></ul><p>The journey from kick-off to full implementation of your continuous monitoring program typically takes place over a year or more. As a result of that implementation period, you will have a risk-adjusted program informed by verifiable and objective risk assessment information. You will also be able to leverage historical trending information, consistent scoring and actionable security alerts. This information and these capabilities will allow you to better scale your program, increase vendor coverage, and improve your control effectiveness.</p><p>We’d love to share more insights into how to successfully incorporate continuous monitoring into your risk management program. Give us a call today<strong> (781–784–2054).</strong></p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/part-2-incorporating-continuous-monitoring-into-your-third-party-risk-management-program-the-pilot-is-complete-now-what"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c67d569fd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Part 1: Incorporating Continuous Monitoring into Your Third Party Risk Program: Begin with the End…]]></title>
            <link>https://medium.com/@riskrecon/part-1-incorporating-continuous-monitoring-into-your-third-party-risk-program-begin-with-the-end-e57ac271d3d1?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/e57ac271d3d1</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[third-party]]></category>
            <category><![CDATA[risk-management]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Thu, 08 Jun 2017 14:03:56 GMT</pubDate>
            <atom:updated>2017-06-08T14:03:56.695Z</atom:updated>
            <content:encoded><![CDATA[<h3>Part 1: Incorporating Continuous Monitoring into Your Third Party Risk Program: Begin with the End State in Mind</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*RQBFdHz34uK1dn6b3M8FFg.jpeg" /></figure><p><em>Like many organizations today, you have existing processes, tools and people laser-focused on analyzing periodic vendor security questionnaires, documentation, and on-site reviews. Moving to a continuous monitoring program can be daunting. Our advice: Don’t focus on where to start…think about where you want to end up. Begin with the end state in mind.</em></p><p>Is today the day you say, “I’m ready”? Has the growing inherent risk associated with the number of vendors accessing your sensitive data finally convinced you of the need to do more than annual vendor surveys and assessments? Fantastic. The next question is, “where do I start?”</p><p>Many clients ask us how to get started. And I always respond by asking them about their desired end states. Meaning, what do they want their deliverables, metrics and processes to look like in the future? And, can they articulate the most significant gaps in their current programs that they want to address and rectify?</p><p>Before you take that first step, let’s review some things to help you determine your end goals. It’s these end goals that will guide you as you incorporate continuous monitoring into your third-party risk management program.</p><h3>When Thinking About Third Party Cyber Security, Keep Your End Goals in Mind</h3><p>Generally speaking, organizations aim to move from a manual, one-size-fits-all vendor risk process to one that is scalable and risk-adjusted. Today, your vendor survey and risk process doesn’t scale to effectively cover all third parties (and fourth parties) and doesn’t obtain sufficiently frequent and actionable security performance metrics. Ultimately, you want a process that incorporates all vendors and suppliers and allows you to align assessment scope and frequency with your organization’s residual risk tolerance and resources.</p><p>Determining what a risk-adjusted vendor risk management process means to your organization depends on risk appetite, potential exposure, budget constraints, system constraints, and other resource considerations. Therefore, when getting started, envision a risk-adjusted program that will answer these basic questions:</p><ul><li><strong>Who?</strong> Which categories of vendors, suppliers, and 4th parties require coverage or more frequent coverage?</li><li><strong>What?</strong> Do you need separate processes for managed vendors, unmanaged suppliers, 4th parties or vendors during the proposal process?</li><li><strong>When?</strong> How frequently do you require updated information for each category?</li><li><strong>Where?</strong> Into which steps in your process is it best to incorporate this new vendor risk data? Where do you want to remove, enhance or streamline steps?</li><li><strong>Why?</strong> Do your defined metrics capture and assess the reasons behind this change? For example, have you established measurements to capture the number of additional vendors under coverage, increased frequency of coverage, and analyst productivity improvements?</li></ul><h3>Getting Started with Your Online Risk Assessment</h3><p>Jumpstart your program by conducting a 90 to 180-day pilot with a set of vendors already scheduled for their annual assessment during the pilot period. During the pilot, build out your process according to the end goals you established:</p><ul><li>Obtain executive support to build an ad hoc team including security, sourcing, and third-party risk personnel. It’s this team that will meet regularly, agree on key objectives and metrics, and help to evangelize the new continuous monitoring program throughout the rest of the organization.</li><li>Establish the key pilot objectives and metrics, including impact on risk data quality and analyst productivity, remediation effectiveness, and third-party feedback.</li><li>Select a third-party risk management provider that can provide continuous monitoring of all your third parties.</li><li>Train your analysts on the new continuous risk scoring data, documenting how to build this data into your vendor engagement model. Shadow your analysts to determine what worked, or didn’t work, during this initial phase and capture that feedback as well as any feedback from the vendors assessed.</li><li>Meanwhile, gather an authoritative list of additional vendors not currently under review by your security team. Have your third-party risk management solution begin building portfolio and vendor-level risk assessments to prioritize which vendors to engage in phase 2 of your continuous monitoring project.</li></ul><p>Be sure to check out our next blog where we will discuss how to go from this pilot phase to your scalable, risk-adjusted program of the future.</p><p>If you’d like to explore how RiskRecon can help you kick-off your continuous monitoring program, give us a call today<strong> (781–784–2054).</strong></p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/incorporating-continuous-monitoring-into-your-third-party-risk-management"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e57ac271d3d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Threat Intelligence to Manage Third Party Risk: The Boy Who Cried Wolf]]></title>
            <link>https://medium.com/@riskrecon/using-threat-intelligence-to-manage-third-party-risk-the-boy-who-cried-wolf-89cf96b30d2a?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/89cf96b30d2a</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Mon, 05 Jun 2017 19:27:36 GMT</pubDate>
            <atom:updated>2017-06-05T19:27:36.174Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/467/0*m0yMQNCim6YZBAoh." /></figure><p><em>More and more enterprises are increasing their budgets for threat intelligence in order to stay on top of the latest security risks. The dramatic increase in third party cyber security risk seems to make it another area where threat intelligence can be applied. But is threat intelligence actually a good fit for your third-party risk management program?</em></p><p><strong>Are You Using Risk Management Software the Right Way?</strong></p><p>According to ESG, 72% of enterprise organizations plan to increase spending on their threat intelligence programs over the next 12 to 18 months.<a href="http://blog.riskrecon.com/using-threat-intelligence-to-manage-third-party-risk#_edn1">[i]</a> This represents considerable resources focused on threat intelligence.</p><h3>A Few Flaws in Only Using a Threat Intelligence Approach</h3><p>While there is no doubt that threat intelligence plays an important role in identifying and assessing your organization’s vulnerabilities, experience has shown that using the data provided by threat intelligence to manage third party risk has a few flaws:</p><ul><li><strong>It doesn’t scale<br></strong>Using threat intelligence to measure your organization’s vulnerabilities requires experienced people who can separate the signal from the noise. Someone must evaluate each alert and identify the false positives, as false positives can account for 5 to 10 times the number of legitimate vulnerabilities identified. While this approach may be manageable when looking at your own attack surface area, it doesn’t scale when trying to identify risk across hundreds, thousands, or tens of thousands of vendors. By its nature, threat intel is not accurate enough to build automated and actionable risk assessments that allow you to confidently engage third parties with a reasonable level of resources.</li><li><strong>It’s only a secondary measure <br></strong>How about those alerts that may be accurate (not false positives)? Well, even if they are accurate, they may not be meaningful. Threat intelligence often measures potential threats (leaked credentials, dark web chatter, etc.) rather than actionable gaps. And, you cannot directly manage every detail in the security programs of every vendor.</li><li><strong>It’s often helpful only for larger vendors <br></strong>One of your large vendors is likely a target of bad actors. What about the 80% of your vendors that are small or medium-sized and generally not targeted? Does this mean if they score well on threat intelligence that they have strong security practices, or just that no one has tried breaching them yet?</li></ul><p>It’s easy to see that incorporating threat intelligence into your third party risk management program could create a “boy who cried wolf” scenario, throwing up alerts on threats that aren’t real and consuming significant resources — yours and your suppliers. What’s the alternative?</p><h3>Call Out Real Third Party Cyber Security Risks: Directly Measure Attack Surface Area</h3><p>Threat intelligence certainly has a place in third party risk management if implemented appropriately. If your vendor frequently experiences data loss events or privacy breaches, that is a legitimate concern. However, we recommend implementing primary measures that look directly at the attack surface areas of the vendor: its internet-accessible assets.</p><p>Why this approach?</p><ul><li><strong>It scales <br></strong>Sophisticated tools now exist to accurately determine software patching levels, encryption methods, application email and DNS security, and so on. Using them, you can continuously monitor actual security performance and provide real, actionable information to your vendors to effectively manage your shared cyber risk.</li><li><strong>It’s a primary measure <br></strong>These measures capture the current vulnerabilities within your vendors’ infrastructure that are most likely to be targeted by bad actors. Soft targets may not be the subject of chatter, but they certainly will be found by cybercriminals.</li><li><strong>It’s consistent with your existing practices <br></strong>Many measurements of attack surface area — for example, patching, web, app, and email security, etc. — map directly to your existing assessment questionnaire. Accordingly, these measures are straightforward enough for analysts to understand and incorporate into their existing work product.</li><li><strong>It’s beneficial for vendors of any size<br></strong>While all vendors are not showing up as targets today in the dark web, they all have infrastructure on the internet that can be evaluated for good security practices. With the increasing number of targeted small and medium businesses, it’s important to know if they have strong security practices in place.</li></ul><p>Managing third party risk requires continuous monitoring; however, threat intelligence typically isn’t accurate enough to be built cost-effectively into your third party risk management process. Several Fortune 500 companies control their third party risk with continuous monitoring by RiskRecon.</p><p>Learn more by giving us a call today<strong> (781–784–2054).</strong></p><p><a href="http://blog.riskrecon.com/using-threat-intelligence-to-manage-third-party-risk#_ednref1">[i]</a> <a href="http://i.crn.com/custom/ESG_WP_Keys_to_Operationalizing_Threat_Intelligence_LG_Sep%202016_Final.pdf">http://i.crn.com/custom/ESG_WP_Keys_to_Operationalizing_Threat_Intelligence_LG_Sep%202016_Final.pdf</a></p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/using-threat-intelligence-to-manage-third-party-risk"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=89cf96b30d2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Extending GRC with Continuous Vendor Security Monitoring]]></title>
            <link>https://medium.com/@riskrecon/extending-grc-with-continuous-vendor-security-monitoring-685d03c34f7e?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/685d03c34f7e</guid>
            <category><![CDATA[third-party-risk]]></category>
            <category><![CDATA[fintech]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[grc]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Wed, 31 May 2017 20:01:32 GMT</pubDate>
            <atom:updated>2017-05-31T20:04:46.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*F8dtFYdI4njaShxQbhEVKg.jpeg" /></figure><p><em>We speak with many clients that already have some form of governance, risk management, and compliance (GRC) program in place to assist with managing their enterprise programs. And some have software solutions to help them manage the process. This is not surprising when the market for GRC solutions is expected to grow to </em><a href="http://www.marketsandmarkets.com/Market-Reports/enterprise-governance-risk-compliance-market-1310.html"><em>$38 billion by 2021</em></a><em>.</em></p><p><em>Most companies are seeking ways to obtain more value from their GRC system — often by extending their coverage to their third-party risk management programs. Using the new class of continuous vendor security monitoring solutions is one of the best ways to add immediate value to GRC. This pairing offers a number of benefits, such as speed to identify and manage risk, valuable insight for prioritization of response, visibility into an accurate and complete vendor IT footprint, and critical transparency of exposure and actionable information on inherited vulnerabilities.</em></p><p><strong>Fast Response</strong></p><p>Risk needs to be identified and managed quickly — and this is possible with RiskRecon’s continuous vendor security monitoring. For example, when the recent Apache Struts2 vulnerability emerged,we took less than 24 hours to help pinpoint which vendors were potentially vulnerable. Clients could then generate follow-up vendor information requests from their GRC solution, track status, and log remediation steps. Read our previous blog on Struts2 <a href="http://blog.riskrecon.com/when-apache-struts2-hits-the-fan-respond-with-data-and-collaboration">here</a>.</p><p><strong>Valuable Insight</strong></p><p>Information not only needs to be delivered quickly, it needs to be accurate. Many clients today gather vendor security performance primarily through vendor surveys and attestation. That information can be stored within GRC systems and remediation steps identified to resolve known issues. But how confident are you in the accuracy of the information?</p><p>After all, your GRC program is only as good as the underlying data it contains. Many clients increasingly question using attestations alone when vendors typically all appear above average in their security performance. This just doesn’t make sense.</p><p>Our clients find new insights and better prioritize follow-up inquiries when integrating independently-produced security assessments side-by-side with the vendor attestations. Shining light on the “risk reality” of how vendors actually perform rather than their documented intent to perform is critical.</p><p><strong>Visibility</strong></p><p>Why are complementary solutions required for GRC in order to meet the new vendor “risk reality”? One key step for any good GRC program is to have an appropriate inventory of processes and metrics. Implicit in having a complete inventory is building “asset maps” of your organization’s and vendors’ IT systems.</p><p>But historically, building an “asset map” is difficult, particularly for your third-party suppliers. For example, how confident are you with the following scenarios?</p><ul><li>We have good visibility into each critical supplier’s IT footprint, including that of the critical providers and fourth parties they use to deliver their service.</li><li>We can quickly gather detailed risk assessments of each vendor’s exposure to new “celebrity vulnerabilities” as they emerge.</li></ul><p>If you can’t answer “yes” to both scenarios, then you are relying on incomplete data provided mainly through the vendor attestation and survey process.</p><p><strong>Transparency</strong></p><p>As SaaS adoption continues to grow, your organization is exposed to much larger, often unseen fourth-party risks. By using continuous vendor monitoring solutions, clients quickly identify the security gaps not only at their vendors but also at their vendors’ suppliers. For example, wouldn’t it be useful to know in advance which vendors rely on Dyn, Amazon Web Services (AWS), and GoDaddy to provide services to your organization?</p><p>With proper integration into your GRC program and systems, continuous vendor monitoring solutions bring the needed level of transparency and granular details to highlight performance gaps. These solutions enable you to tailor the scope and frequency of each vendor’s assessment program rather than rely on a one-size-fits-all solution. You therefore obtain better information but can also better align your scarce human resources to focus on the most pressing items rather than routine questionnaires.</p><p>And when those urgent new threats emerge, you can quickly pinpoint where to focus rather than spend days or weeks trying to get every vendor to respond to your initial request.</p><p><strong>About RiskRecon’s Continuous Vendor Security Monitoring</strong></p><p>RiskRecon’s SaaS solution delivers transparent security measurements, analytics, and analyst-level insight directly into your GRC system. This enables you to better pinpoint risks and direct your resources to the most critical threats in your supply chain. Set up a demo today to <a href="http://www.riskrecon.com/contact-us.html">learn more</a>.</p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/extending-grc-with-continuous-vendor-security-monitoring"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=685d03c34f7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Apache Struts2 Hits the Fan, Respond with Data and Collaboration]]></title>
            <link>https://medium.com/@riskrecon/when-apache-struts2-hits-the-fan-respond-with-data-and-collaboration-53503dcd5395?source=rss-c8ebf4291123------2</link>
            <guid isPermaLink="false">https://medium.com/p/53503dcd5395</guid>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[cyber-risk-management]]></category>
            <category><![CDATA[risk-management]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[third-party-risk]]></category>
            <dc:creator><![CDATA[RiskRecon]]></dc:creator>
            <pubDate>Wed, 31 May 2017 19:59:08 GMT</pubDate>
            <atom:updated>2017-05-31T20:05:27.284Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*ged1TWCgpx0Gi8jLu_7m_A.jpeg" /></figure><p><em>Mitigating your third-party exposure to Apache Struts2 requires accurate, actionable data — and fast. If you can apply automated techniques to rapidly identify which of your vendors are most likely exposed to the exploit, you can quickly prioritize your risk resources and engage constructively with impacted vendors.</em></p><p><strong>Gain Third-Party Exposure Visibility</strong></p><p>Creating a comprehensive view of your third-party potential exposure to threats such as Struts2 may seem an insurmountable task. The default approach is to send a questionnaire to each of your hundreds of vendors when an incident occurs, asking them to attest to their exposure and remediation.</p><p>Using innovative techniques developed by RiskRecon, you can maintain objective awareness of your third-party exposure that does not require vulnerability scanning or other invasive techniques. For example, systems running a Java Application Server are potentially exposed to the Struts2 vulnerability exploit. This information can be gathered automatically through passive interaction with each of the vendor’s web applications. Sources of relevant information include:</p><ul><li>HTTP Set Cookie Header will reveal use of Java where JSESSIONID is present</li><li>HTTP X-Powered-By Headers reveal the presence of Java through values such as Servlet 2.4, JSP 2.0, GlassFish, or JBoss</li><li>URL file extensions indicative use of Java include “action,” “.do,” and “.jsp”</li></ul><p>Thus, if you have the means to rapidly map your vendors’ IT footprints and passively observe these software configurations, you can combine this knowledge with robust analytics to rapidly identify potential security exposure.</p><p><strong>Prioritize Remediation</strong></p><p>With good data, you can quickly prioritize your risk mitigation efforts towards those potentially exposed vendors running Java Application Servers. While other vendors should not be ignored, vendors with known potential exposure should be given high priority.</p><p>Based on RiskRecon’s measurements, approximately 36% of the high-risk vendors serving the Fortune 500 are potentially exposed to Apache Struts2 on the internet, running at least one publicly-accessible Java Application Server.</p><p><strong>Conduct Vendor Validation</strong></p><p>Structured correctly, vendor responses to your questionnaire can be validated against objective data to determine which potentially exposed vendors are correctly mitigating the risk. Consider the following question set:</p><p><em>Question 1)</em> How many systems in your environment are running Java Application Servers on Apache that are potentially exposed to the Struts2 exploit? Please describe the process of identification.</p><p><em>Question 2) </em>If potentially vulnerable systems were identified, how many of the identified systems were vulnerable to Struts2 exploit? Please describe the process of vulnerability testing.</p><p><em>Question 3) </em>Of the vulnerable systems identified, how many have been patched?</p><p>Now you can compare each vendor’s questionnaire answers with the data gathered by passively interacting with their Internet systems. For example, if a vendor responds to Question 1 stating they have no potential exposure but your assessment shows their running numerous internet-based with Java Application Servers, you can initiate escalation procedures with them.</p><p>Similarly, if a vendor’s response indicates they have identified 10 potentially exposed systems and your data identified five potentially exposed systems then you can have high confidence that they are properly managing the situation.</p><p><strong>Collaborate</strong></p><p>Even better results can be obtained by building a relationship with your vendors through which you can share your threat intelligence. In the process, you may provide the vendor knowledge of potential exposures they overlooked. Perhaps more importantly, the vendor will know you are in the fight together. After all, who better to share intelligence with than those vendors with whom you’ve entrusted with your assets?</p><p><strong>The Right Results</strong></p><p>Absent good, verifiable data on your vendors’ potential risk exposure, you are left to blindly approach each of your partners with the same attestation request and you are unable to proactively help your vendors protect your assets.</p><p>On the other hand, good data on your vendors’ potential risk exposure shared in a constructive relationship allows you to prioritize your risk mitigation resources and assist your vendors in the fight. It also serves as fuel to build stronger security relationships with your vendors that will be mutually beneficial. Rather than fostering an environment of suspicion, assessing and sharing information about the environment’s realities will foster trust. Trust, but verify. And collaborate.</p><p><a href="http://www.riskrecon.com/"><strong>About RiskRecon</strong></a></p><p>RiskRecon enables enterprises to see beyond the limitations of periodic questionnaires to their third-party risk reality. RiskRecon brings to bear deep, accurate security transparency and actionable measurements for every enterprise, enabling organizations to continuously manage their third-party risk reality at scale.</p><p>Within hours of the Apache Struts exposure, RiskRecon accelerated their customers threat response by providing actionable intelligence about their potential exposure in their own enterprise and third-party IT assets. Let’s discuss how you can strengthen your third-party relationships with our innovative assessment and collaboration solutions.</p><p><em>Originally published at </em><a href="http://blog.riskrecon.com/when-apache-struts2-hits-the-fan-respond-with-data-and-collaboration"><em>blog.riskrecon.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=53503dcd5395" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>