<?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 Creating security zones in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/creating-security-zones/m-p/3095117#M988040</link>
    <description>In current configuration, there are no security zones configures as of now.</description>
    <pubDate>Tue, 12 Mar 2019 13:29:21 GMT</pubDate>
    <dc:creator>kabilan.s81</dc:creator>
    <dc:date>2019-03-12T13:29:21Z</dc:date>
    <item>
      <title>Creating security zones</title>
      <link>https://community.cisco.com/t5/network-security/creating-security-zones/m-p/3095117#M988040</link>
      <description>Hi,

Currently we are having 1 access policy with 1 intrusion policy applied to our IPS. Our requirement is to segregate the traffic now zone wise where all internet related traffic will contain signatures with block action and for other traffic, signatures will be in monitoring only. Kindly let me know how to proceed with it.</description>
      <pubDate>Tue, 12 Mar 2019 13:29:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-security-zones/m-p/3095117#M988040</guid>
      <dc:creator>kabilan.s81</dc:creator>
      <dc:date>2019-03-12T13:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: Creating security zones</title>
      <link>https://community.cisco.com/t5/network-security/creating-security-zones/m-p/3175550#M988046</link>
      <description>&lt;P&gt;What exactly is your question?&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2017 20:52:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/creating-security-zones/m-p/3175550#M988046</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2017-08-24T20:52:39Z</dc:date>
    </item>
  </channel>
</rss>

