<?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: IPS configuration? in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-configuration/m-p/695926#M88083</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You're right. Almost all IPS signatures are set to trigger log or alarm only, except for some critical signatures that by default, drop/deny the traffic in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normal practise is to monitor your IPS log for at least 1 or 2 days. Review the log for type of violations/misuse. Check for false positive sign as well, as some might not be a real threats.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once confirmed, you may now start to change the actions for the relevant signatures to either drop/reset. Reset is effective for TCP sessions (between attacker &amp;amp; victim host) only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bear in mind, you need to constantly monitor the IPS log for new/missing violations. Frequent review of logs and security postures are highly recommended by Cisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read the SAFE Blueprint for details:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns128/networking_solutions_white_paper09186a00801bc111.shtml" target="_blank"&gt;http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns128/networking_solutions_white_paper09186a00801bc111.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using ACL is good as it can work in tandem with IPS where you only allow certain/known source addresses/services to come in. IPS, in turn, will provide deep packet inspection to ensure no malicious content is flowing into your network/servers from that permitted external/source addresses&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00803eb031.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00803eb031.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Dec 2006 01:39:23 GMT</pubDate>
    <dc:creator>a.kiprawih</dc:creator>
    <dc:date>2006-12-13T01:39:23Z</dc:date>
    <item>
      <title>IPS configuration?</title>
      <link>https://community.cisco.com/t5/network-security/ips-configuration/m-p/695925#M88082</link>
      <description>&lt;P&gt;Recently I installed the latest IPS update &amp;amp; noticed all signatures show alarm action only. I thought sdf "action" were pre set by Cisco.&lt;/P&gt;&lt;P&gt;Should any sigs be changed to reset or drop? &lt;/P&gt;&lt;P&gt;How do you determine which sigs to change? &lt;/P&gt;&lt;P&gt;Should an ACL be used with IPS?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:22:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-configuration/m-p/695925#M88082</guid>
      <dc:creator>ms4561</dc:creator>
      <dc:date>2019-03-10T10:22:13Z</dc:date>
    </item>
    <item>
      <title>Re: IPS configuration?</title>
      <link>https://community.cisco.com/t5/network-security/ips-configuration/m-p/695926#M88083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You're right. Almost all IPS signatures are set to trigger log or alarm only, except for some critical signatures that by default, drop/deny the traffic in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Normal practise is to monitor your IPS log for at least 1 or 2 days. Review the log for type of violations/misuse. Check for false positive sign as well, as some might not be a real threats.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once confirmed, you may now start to change the actions for the relevant signatures to either drop/reset. Reset is effective for TCP sessions (between attacker &amp;amp; victim host) only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Bear in mind, you need to constantly monitor the IPS log for new/missing violations. Frequent review of logs and security postures are highly recommended by Cisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read the SAFE Blueprint for details:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns128/networking_solutions_white_paper09186a00801bc111.shtml" target="_blank"&gt;http://www.cisco.com/en/US/netsol/ns340/ns394/ns171/ns128/networking_solutions_white_paper09186a00801bc111.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using ACL is good as it can work in tandem with IPS where you only allow certain/known source addresses/services to come in. IPS, in turn, will provide deep packet inspection to ensure no malicious content is flowing into your network/servers from that permitted external/source addresses&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00803eb031.html" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/products_configuration_guide_chapter09186a00803eb031.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;AK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Dec 2006 01:39:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-configuration/m-p/695926#M88083</guid>
      <dc:creator>a.kiprawih</dc:creator>
      <dc:date>2006-12-13T01:39:23Z</dc:date>
    </item>
  </channel>
</rss>

