<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cisco and Meraki in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Cisco-and-Meraki/m-p/14927#M480</link>
    <description>&lt;P&gt;Meraki is geared towards small and medium business, with Cisco steering enterprise customers towards their Viptela solution.&amp;nbsp; Fundamentally, Meraki limitations arise from dependency on "proprietary protocols" and difficulties inter-operating with competitors, such as IOS, Palo, Checkpoint, zscaler, bluecoat, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They do a pretty good job of checking off the boxes when comparing features/price on paper.&amp;nbsp; Like any cloud offering, the feature list is wide, but not deep.&amp;nbsp; For example, they have a "firewall", but it is not competitive with enterprise solutions such as Palo Alto and Checkpoint.&amp;nbsp; Also, their VPN options (specifically surrounding NAT) are no where as flexible as IOS or Palo Alto.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Their cool health-based routing is geared towards inter-facility connections, where you control both ends and have an MX appliance on each end.&amp;nbsp; Extended migrations require a meet-me point to bridge old and new networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If an endpoint is "the Internet", long-term connections (e.g. webex) require client-initiated reestablishment if meraki decides to switch to a backup ISP.&amp;nbsp; This is because they NAT to the ISP-provided source IP address instead of using BGP peering.&amp;nbsp; Similarly, they do not do stateful-failover if you need to fail to a backup Meraki appliance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Their price advantage primarily comes from displacing backhaul of Internet-bound traffic.&amp;nbsp; If you already have "direct internet access" at your remote locations, the financial story is less compelling.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As with any subscription product, there are questions of contingency operation if the Meraki cloud were to fail, if&amp;nbsp;your model were to fall out of support&amp;nbsp;or if you were to fail to pay your bill.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We last looked at them somewhat more than a year ago, so YMMV.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Sep 2018 21:52:49 GMT</pubDate>
    <dc:creator>denbesten</dc:creator>
    <dc:date>2018-09-24T21:52:49Z</dc:date>
    <item>
      <title>Cisco and Meraki</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Cisco-and-Meraki/m-p/14901#M479</link>
      <description>&lt;P&gt;Anybody have any experience, good or bad with the CISCO Meraki suite of security "products"?&lt;/P&gt;&lt;P&gt;We have to upgrade our infrastructure and the CISCO reps are trying to sell out IT folks on replacing a lot of our current security tools with their "Meraki" solution. I am doing some independent research but wanted to hear your thoughts or experiences with it.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Sep 2018 14:44:32 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Cisco-and-Meraki/m-p/14901#M479</guid>
      <dc:creator>CISOScott</dc:creator>
      <dc:date>2018-09-24T14:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco and Meraki</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Cisco-and-Meraki/m-p/14927#M480</link>
      <description>&lt;P&gt;Meraki is geared towards small and medium business, with Cisco steering enterprise customers towards their Viptela solution.&amp;nbsp; Fundamentally, Meraki limitations arise from dependency on "proprietary protocols" and difficulties inter-operating with competitors, such as IOS, Palo, Checkpoint, zscaler, bluecoat, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They do a pretty good job of checking off the boxes when comparing features/price on paper.&amp;nbsp; Like any cloud offering, the feature list is wide, but not deep.&amp;nbsp; For example, they have a "firewall", but it is not competitive with enterprise solutions such as Palo Alto and Checkpoint.&amp;nbsp; Also, their VPN options (specifically surrounding NAT) are no where as flexible as IOS or Palo Alto.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Their cool health-based routing is geared towards inter-facility connections, where you control both ends and have an MX appliance on each end.&amp;nbsp; Extended migrations require a meet-me point to bridge old and new networks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If an endpoint is "the Internet", long-term connections (e.g. webex) require client-initiated reestablishment if meraki decides to switch to a backup ISP.&amp;nbsp; This is because they NAT to the ISP-provided source IP address instead of using BGP peering.&amp;nbsp; Similarly, they do not do stateful-failover if you need to fail to a backup Meraki appliance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Their price advantage primarily comes from displacing backhaul of Internet-bound traffic.&amp;nbsp; If you already have "direct internet access" at your remote locations, the financial story is less compelling.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As with any subscription product, there are questions of contingency operation if the Meraki cloud were to fail, if&amp;nbsp;your model were to fall out of support&amp;nbsp;or if you were to fail to pay your bill.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We last looked at them somewhat more than a year ago, so YMMV.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Sep 2018 21:52:49 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Cisco-and-Meraki/m-p/14927#M480</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2018-09-24T21:52:49Z</dc:date>
    </item>
  </channel>
</rss>

