<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Autonomic Networking on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/autonomic-networking/</link>
    <description>Recent content in Autonomic Networking on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 13 Apr 2017 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/autonomic-networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Autonomic Network Part 3: Vulnerabilities</title>
      <link>https://insinuator.net/2017/04/autonomic-network-part-3-vulnerabilities/</link>
      <pubDate>Thu, 13 Apr 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/04/autonomic-network-part-3-vulnerabilities/</guid>
      <description>&lt;p&gt;This is the 3rd post in the series of Autonomic Network (AN), it will dedicated for discussing the vulnerabilities. I recommend reading the first 2 parts (&lt;a href=&#34;https://insinuator.net/2017/03/autonomic-network-overview/&#34;&gt;part one&lt;/a&gt;, &lt;a href=&#34;https://insinuator.net/2017/03/autonomic-network-analysis/&#34;&gt;part two&lt;/a&gt;) to be familiar with the technology and how the proprietary protocol is constructed.&lt;/p&gt;&#xA;&lt;p&gt;Initially we will discuss 2 of the reported CVEs, but later there is more CVEs to come 😉&lt;/p&gt;&#xA;&lt;p&gt;Here is a quick overview on how our network looks like for 2 CVEs&lt;/p&gt;</description>
    </item>
    <item>
      <title>Autonomic Networking – Part 2: Analysis</title>
      <link>https://insinuator.net/2017/03/autonomic-networking-part-2-analysis/</link>
      <pubDate>Mon, 20 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/03/autonomic-networking-part-2-analysis/</guid>
      <description>&lt;p&gt;This is the second part in the Autonomic Network series. We have introduced previously in our &lt;a href=&#34;https://insinuator.net/2017/03/autonomic-network-overview/&#34;&gt;first part&lt;/a&gt; the Autonomic Network (AN), took a look about the needed configuration to run it on Cisco gear and what is the expected communication flow. In this post, we will dive deeper to have a closer look on the packets and how they are composed. Cisco’s AN protocol is a proprietary one and as far as I know, the analysis provided here for the protocol is the first of its kind.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Autonomic Networking – Part 1: Overview</title>
      <link>https://insinuator.net/2017/03/autonomic-networking-part-1-overview/</link>
      <pubDate>Sun, 19 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/03/autonomic-networking-part-1-overview/</guid>
      <description>&lt;p&gt;This is a 3-part series which introduces and analyzes Cisco’s implementation for Autonomic Network. In the 1st part, the technology is introduced and we have an overview about communication flow. In the &lt;a href=&#34;https://insinuator.net/2017/03/autonomic-network-analysis/&#34;&gt;2nd part&lt;/a&gt;, Cisco’s proprietary protocol is reverse engineered ? then finally in the &lt;a href=&#34;https://insinuator.net/2017/04/autonomic-network-vulnerabilities/&#34;&gt;3rd part&lt;/a&gt;, multiple vulnerabilities will be disclosed for the first time. If you’re aware of the technology, you can skip directly to part 2 where the action begins! &lt;/p&gt;</description>
    </item>
  </channel>
</rss>
