<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Geoffrey Hill - Tutamantic</title>
    <description>www.linkedin.com/in/geoffrey-hill-61b7bb￼</description>
    <link>https://speakerdeck.com/geoffreyhilltutamantic</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/geoffreyhilltutamantic.rss"/>
    <lastBuildDate>2018-09-12 11:45:17 -0400</lastBuildDate>
    <item>
      <title>Rapid Threat Model Prototyping Process</title>
      <description>Threat Modelling can be a laborious and time-consuming exercise, and is not a happy marriage with CI/DevOps methodologies. 

Introducing my Rapid Threat Model Prototyping paradigm, which I have been using at several sites. It enables automation with fast development cycles in today's IT environments.</description>
      <media:content url="https://files.speakerdeck.com/presentations/f76c255f705c454283cc3dd6029cc012/preview_slide_0.jpg?10750372" type="image/jpeg" medium="image"/>
      <content:encoded>Threat Modelling can be a laborious and time-consuming exercise, and is not a happy marriage with CI/DevOps methodologies. 

Introducing my Rapid Threat Model Prototyping paradigm, which I have been using at several sites. It enables automation with fast development cycles in today's IT environments.</content:encoded>
      <pubDate>Wed, 08 Aug 2018 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/geoffreyhilltutamantic/rapid-threat-model-prototyping-process</link>
      <guid>https://speakerdeck.com/geoffreyhilltutamantic/rapid-threat-model-prototyping-process</guid>
    </item>
  </channel>
</rss>
