<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>risk thinking on Ben Sapiro&#39;s Draft Thoughts</title>
    <link>https://thoughts.sapiro.net/categories/risk-thinking/</link>
    <description>Recent content in risk thinking on Ben Sapiro&#39;s Draft Thoughts</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 03 Nov 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://thoughts.sapiro.net/categories/risk-thinking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Complexity Firewall</title>
      <link>https://thoughts.sapiro.net/post/complexity_firewall/</link>
      <pubDate>Wed, 03 Nov 2021 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/complexity_firewall/</guid>
      <description>&lt;p&gt;I periodically get asked “are we secure?” or “is this system secure?”. That’s not an unusual question for a CISO, or any one cyber security professional in a leadership role, to be asked. How can we answer that question? Can we answer that question in a genuine and complete matter? What if we’re wrong? What if our answers turns out to be wrong later?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Assume the enemy knows the system</title>
      <link>https://thoughts.sapiro.net/post/solarwinds_microsoft/</link>
      <pubDate>Fri, 01 Jan 2021 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/solarwinds_microsoft/</guid>
      <description>&lt;p&gt;One of my favourite memories from my consulting days is a developer that decided to modify the DES encryption algorithm because &amp;ldquo;it was too well known&amp;rdquo;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Downstream Exposure / Upstream Breach</title>
      <link>https://thoughts.sapiro.net/post/downstream_exposure/</link>
      <pubDate>Thu, 24 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/downstream_exposure/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve written before about &lt;a href=&#34;externalities_in_risk_models.md&#34;&gt;externalities&lt;/a&gt;. When an organizations actions cause harm to others. The recent SolarWinds breach has got me thinking about when someone causes harm to others via a third party. Are you the route into your customer&amp;rsquo;s organization?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Thoughts on the SolarWinds breach</title>
      <link>https://thoughts.sapiro.net/post/solarwinds_breach/</link>
      <pubDate>Sun, 20 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/solarwinds_breach/</guid>
      <description>&lt;p&gt;You’re likely not a target of the SolarWinds breach but you still need to secure your digital supply chain.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Externalities</title>
      <link>https://thoughts.sapiro.net/post/externalities_in_risk_models/</link>
      <pubDate>Mon, 03 Aug 2020 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/externalities_in_risk_models/</guid>
      <description>&lt;p&gt;We all take risks; but do we consider how those risks impact others? Should we include the cost to others when we make risk based decisions not to address certain information security issues?&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Acceptable Risk</title>
      <link>https://thoughts.sapiro.net/post/acceptable_risk/</link>
      <pubDate>Thu, 30 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/acceptable_risk/</guid>
      <description>&lt;p&gt;Every individual, company and society is willing to take risk. In everything we do there is risk, we use risk as leverage (in the financial sense) to achieve some benefit at lower cost. Figuring out where that bright red line of &lt;em&gt;too much&lt;/em&gt; risk is not easy. Figuring out where you are relative to that position requires effort.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Risk Models</title>
      <link>https://thoughts.sapiro.net/errata/risk_models/</link>
      <pubDate>Thu, 30 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://thoughts.sapiro.net/errata/risk_models/</guid>
      <description>&lt;p&gt;I had included a list of risk modelling techniques as part of the &lt;a href=&#34;https://thoughts.sapiro.net/post/acceptable_risk/&#34;&gt;Acceptable Risk&lt;/a&gt; posting. I extracted the list because the content wasn&amp;rsquo;t core to that article. Here&amp;rsquo;s the list if you&amp;rsquo;re interested.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>The One Risk Statement To Bind Them All</title>
      <link>https://thoughts.sapiro.net/post/the_one_risk/</link>
      <pubDate>Sun, 26 Jul 2020 08:57:45 -0400</pubDate>
      
      <guid>https://thoughts.sapiro.net/post/the_one_risk/</guid>
      <description>&lt;p&gt;How many risk statements do you need to describe the information security risks to Management? Probably just one.&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>
