<?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 Rich on Medium]]></title>
        <description><![CDATA[Stories by Rich on Medium]]></description>
        <link>https://medium.com/@rich-76605?source=rss-33d1529835c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*OSGlTPutBKLZvhpX.jpg</url>
            <title>Stories by Rich on Medium</title>
            <link>https://medium.com/@rich-76605?source=rss-33d1529835c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:38:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rich-76605/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[A CISO’s Intro To The Risk Operations Center (ROC)]]></title>
            <link>https://rich-76605.medium.com/a-cisos-intro-to-the-risk-operations-center-roc-1c8ff7f85e1c?source=rss-33d1529835c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c8ff7f85e1c</guid>
            <dc:creator><![CDATA[Rich]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 16:49:14 GMT</pubDate>
            <atom:updated>2025-01-30T17:53:22.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--NXpHz0ilLXskFjtChULA.png" /></figure><p><strong>WHAT’S IN A NAME?</strong></p><p>When CISOs hear the phrase “Risk Operations Center” they invariably ask, <em>“How is a ROC different from a SOC?”</em> Let’s begin answering this question with a concise definition: <em>A ROC orchestrates risk elimination.</em></p><p>I can hear risk purists objecting,<em> “You can never eliminate risk — only control it!”</em> I have two responses. First, I was being purposefully terse as a means of easing readers into a fuller definition. Second, I suspect objections stem from not completely aligning on terms. Let’s fix that by defining what <em>I mean</em> by <strong>risk</strong> and <strong>elimination</strong>.</p><p><strong>What’s Risk?</strong></p><p>For the definition of risk I will turn to our book How To Measure Anything In Cybersecurity Risk. <em>“Risk is a state of uncertainty where some of the possibilities could lead to loss, catastrophe, or some other undesirable outcome.”</em> Here is a thought experiment: If you completely remove your uncertainty — have you eliminated risk?</p><p>Imagine I am driving an SUV. I’ve just been told there is a small tunnel ahead. I don’t know what small means in this context. I just know I’m driving a high occupancy vehicle full of children and my spouse. I’m now uncertain if my vehicle will fit. As I approach the tunnel I see a sign overhead that says the tunnel is twenty feet by twenty feet — and I can also clearly see that my SUV will fit. Using “measurement” I just eliminated my state of uncertainty about possible future “<em>loss, catastrophe or some other undesirable outcome.”</em></p><p><strong>Risk measurement moderates our uncertainty. </strong>We define risk measurement in our book as, <em>“A quantitatively expressed reduction of uncertainty based on one or more observations.” </em>In the case of tunnel vs SUV my state of uncertainty was reduced 100%. Unfortunately, not all risks are this cut and dry. This is why we need to clarify what elimination means.</p><p><strong>What’s Elimination?</strong></p><p>For elimination I’m using its “risk oriented” word origin.<strong> </strong>In Latin, elimination is “ex limine.”<em> </em>The “ex” means “<em>off</em> or <em>out</em>.” And “<em>limine</em>” is limit or boundary. In short, to eliminate risk is to set a boundary or limit that should not be exceeded. This ties nicely with the concept of a cyber insurance limit and risk tolerance. Indeed, a limit is a mathematically unambiguous and contractually binding expression of business risk tolerance.</p><p>With our terms defined I can expand my overly pithy ROC definition to something acceptable even by the most ardent of risk purists: <em>“A ROC continuously orchestrates the remediation, mitigation and or transfer of cybersecurity risk that may exceed business tolerance.”</em></p><p>That’s a mouthful. Hopefully it’s clear that a ROC — at least in theory — is no SOC. To further distinguish the differences let’s turn our attention to platforming.</p><p><strong>WHAT’S A ROC PLATFORM</strong></p><p>I have the unique pleasure of engaging with CISOs and their teams around the globe on all things cybersecurity risk management. And a growing majority of fortune level CISO’s are attempting to stand up DIY ROCs. Perhaps you are one of these CISOs. How might you know?</p><p><strong>Are you aggregating comprehensive “Risk Data” into a data lake? </strong>More specifically, are doing one or more of the following:</p><p>● De-duplicating Assets</p><p>● Consume Full-Stack Vulnerability Data</p><p>● Rationalizing Disparate Scores</p><p>● Integrating Threat Intelligence</p><p>● Correlating Compensating Controls</p><p>● Trigger Auto-Mitigation / Remediation</p><p>● Prioritize Work Using Value-at-Risk?</p><p>● Others…</p><p>If you answered yes — even in part — then you are likely embarking on the ROC journey. It’s a non-trivial DIY proposition. Consider that the average fortune level firm has at a minimum dozens of security products. Hitting all the bullets above with each investment would most likely be out of reach — even for those with outsized budgets.</p><p><strong>Did you see the “Risk Data” distinction above? </strong>It was purposeful. I am distinguishing it from threat oriented “event data” that materializes in your SOC. Event data consists of streams of arrival time stamps with light weight meta-data. Due to its volume and millisecond velocity it’s invariably light on context. Event data is best persistent and modeled via time series data structures and related analysis. This is similar to what is used in realtime trading and network analysis.</p><p>“Risk Data” is the other end of the spectrum when it comes to context. Consider all the rich content and context coming from the bulleted list above. Analysis and reporting is usually done in some form of OLAP structure enriched with high context graph connected data. Indeed, graph comprehension is a must as cloud native data and other ephemeral “assets” aren’t always IP addressable. (Note: <em>The days of first and third party assets always being tied to a machine — and its IP — are fading. It would seem that the only thing the industry can agree on when it comes to assets is that they are probably nouns.</em>)</p><p>You can still do time series analysis with ROC data. You would do this to baseline metrics and do other forms of change analysis. The event grain for ROC data is not meant to duplicate log aggregation and or observability solutions that back-end SOC systems.</p><p><strong>What’s In A Picture</strong></p><p>The purpose of the infographic is to make clear a ROC’s strategic placement. As you can see, the ROC does not exclusively sit within the attack surface domain. (But the SOC does.) The ROC actually sits at the nexus of value and loss exposure.</p><p>Consider that a successful business is in the business of exposing more value, to more people, through more channels with higher velocities — to make more revenue and more profits. You can also call that “digital and ai transformation.” In this sense, successful businesses are risk exposure machines.</p><p>The ROC is in the center of risk flowing into and out of your “risk surface.” The large arrows show where value flows in and losses flow out. The ROC controls the “loss exposure” portion of that flow. It does that using both sentient and or artificially intelligent means of risk analysis. That analysis in turn automates actions (or enables workflows) for remediation, mitigation and risk transfer. Remediation and mitigation are represented by the green “control” objects within the attack surface domain. Transfer (also green) is within the broader risk surface domain. The green areas are where you take action as a defender and invest in capabilities for controlling loss.</p><p><strong>In Summary</strong></p><p>The ROC is not your SOC. They work together but at different levels of your overarching risk surface. The SOC exclusively operates on event data within the attack surface domain. And the ROC? <em>It</em> <em>continuously orchestrates the remediation, mitigation and or transfer of cybersecurity risk that may exceed business tolerance.</em></p><p>The interesting news is that you may already have a ROC — a nascent and partial one. The bad news, a complete ROC is likely out of reach for most DIY efforts no matter your budgets. The very good news is that vendors like Qualys (shameless plug for my current employer) — with our thousand or more developers, hundreds of researchers, and peta-byte scale data lakes — are deploying ROCs. It’s a natural evolution for us. We are turning what would otherwise be DIY death marches into achievable and affordable ROCs for our customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c8ff7f85e1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IANS Metrics Training: Course 1]]></title>
            <link>https://rich-76605.medium.com/ians-metrics-training-course-1-7ccb97020047?source=rss-33d1529835c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/7ccb97020047</guid>
            <dc:creator><![CDATA[Rich]]></dc:creator>
            <pubDate>Sat, 09 Oct 2021 19:13:34 GMT</pubDate>
            <atom:updated>2021-10-09T19:13:34.404Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/355b12b2c5c52570b8d3b8508d3bf233/href">https://medium.com/media/355b12b2c5c52570b8d3b8508d3bf233/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ccb97020047" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Code For Security Budgets At Risk]]></title>
            <link>https://rich-76605.medium.com/code-for-security-budgets-at-risk-ca8ca80585b5?source=rss-33d1529835c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca8ca80585b5</guid>
            <dc:creator><![CDATA[Rich]]></dc:creator>
            <pubDate>Sun, 07 Jun 2020 22:31:06 GMT</pubDate>
            <atom:updated>2021-05-30T05:04:59.389Z</atom:updated>
            <content:encoded><![CDATA[<p>This supports a blog post that can be found here: <a href="https://get.soluble.cloud/posts/2020/06/three-steps-to-better-security-roi-when-fast-times-clash-with-lean-reality/">https://get.soluble.cloud/posts/2020/06/three-steps-to-better-security-roi-when-fast-times-clash-with-lean-reality/</a></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/714f51c8604b593f2aadcb7c5c79501f/href">https://medium.com/media/714f51c8604b593f2aadcb7c5c79501f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca8ca80585b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>