<?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 IPS and CSM FlexConfig in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085269#M54444</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see. If using CSM, you should create different shared policies for DMZs and all other IPS in general. Another common practices is to configured different virtual sensors or simply different signature policies for these exceptions. Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 18 Nov 2012 23:23:59 GMT</pubDate>
    <dc:creator>alphaccie</dc:creator>
    <dc:date>2012-11-18T23:23:59Z</dc:date>
    <item>
      <title>IPS and CSM FlexConfig</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085266#M54430</link>
      <description>&lt;P&gt;Can we Flex signatures tuning using CSM?&amp;nbsp; I posted the question 3 days ago on the CSM forum, however, no one has answered it yet?&lt;/P&gt;&lt;P&gt;Thanks. &lt;/P&gt;&lt;P&gt;Cath.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:49:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085266#M54430</guid>
      <dc:creator>cpaquet</dc:creator>
      <dc:date>2019-03-10T12:49:00Z</dc:date>
    </item>
    <item>
      <title>IPS and CSM FlexConfig</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085267#M54435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not supported. But I wonder why you need to use Flexconfigs for IPS Signature tuning when it is supported natively?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2012 22:22:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085267#M54435</guid>
      <dc:creator>alphaccie</dc:creator>
      <dc:date>2012-11-16T22:22:20Z</dc:date>
    </item>
    <item>
      <title>IPS and CSM FlexConfig</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085268#M54442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If we have many IPS sensors and are using CSM to push new signatures and common configurations, however, IPS on DMZ1 and DMZ2 are a few signatures that need tweaking differently from each other, I was wondering if FlexConfig could have been used to push the signature customizations.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cath.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 Nov 2012 14:49:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085268#M54442</guid>
      <dc:creator>cpaquet</dc:creator>
      <dc:date>2012-11-18T14:49:00Z</dc:date>
    </item>
    <item>
      <title>IPS and CSM FlexConfig</title>
      <link>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085269#M54444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I see. If using CSM, you should create different shared policies for DMZs and all other IPS in general. Another common practices is to configured different virtual sensors or simply different signature policies for these exceptions. Hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 18 Nov 2012 23:23:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-and-csm-flexconfig/m-p/2085269#M54444</guid>
      <dc:creator>alphaccie</dc:creator>
      <dc:date>2012-11-18T23:23:59Z</dc:date>
    </item>
  </channel>
</rss>

