<?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: Expedition for Cisco ACLs in Expedition Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/228691#M431</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It depends, you can put a PaloAlto Networks device in serial with your ASA and let Expedition to suggest you rules based on the logs generated by our platform or you can migrate the ACLs, Consolidate them to reduce the number of rules and after apply those ACLs to our technology use again Expedition to learn the applications for all the Rules.&lt;/P&gt;</description>
    <pubDate>Wed, 29 Aug 2018 07:44:01 GMT</pubDate>
    <dc:creator>alestevez</dc:creator>
    <dc:date>2018-08-29T07:44:01Z</dc:date>
    <item>
      <title>Expedition for Cisco ACLs</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/228645#M430</link>
      <description>&lt;P&gt;&amp;nbsp;How is the tool at migrating ACLs ? A lot of those practices are not in line with newer security policies and next generation principles. Is it useful to migrate the ACLs or start from scratch ?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 22:55:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/228645#M430</guid>
      <dc:creator>jcardenosa</dc:creator>
      <dc:date>2018-08-28T22:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition for Cisco ACLs</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/228691#M431</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It depends, you can put a PaloAlto Networks device in serial with your ASA and let Expedition to suggest you rules based on the logs generated by our platform or you can migrate the ACLs, Consolidate them to reduce the number of rules and after apply those ACLs to our technology use again Expedition to learn the applications for all the Rules.&lt;/P&gt;</description>
      <pubDate>Wed, 29 Aug 2018 07:44:01 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/228691#M431</guid>
      <dc:creator>alestevez</dc:creator>
      <dc:date>2018-08-29T07:44:01Z</dc:date>
    </item>
    <item>
      <title>Re: Expedition for Cisco ACLs</title>
      <link>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/229085#M447</link>
      <description>&lt;P&gt;If you are doing a one-to-one migration then all the ACL's migrate just fine.&amp;nbsp; After that, Expedtion can use logs or machine learning to crate new layer 7 policies for you.&amp;nbsp; Expedition can definately help you migrate to L7 policies quicly and efficiently.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Sep 2018 01:12:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/expedition-discussions/expedition-for-cisco-acls/m-p/229085#M447</guid>
      <dc:creator>bagherib</dc:creator>
      <dc:date>2018-09-01T01:12:24Z</dc:date>
    </item>
  </channel>
</rss>

