<?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: IDS module setup, what traffic to capture in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491254#M66993</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it all depends on what traffic is going through your network.&lt;/P&gt;&lt;P&gt;If you have apps different than email, http and https that you want to be IDS protected then you would need to expand the VACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use Netflow to see what applications are running through the network.&lt;/P&gt;&lt;P&gt;Then you can decide which ones you don't trust and want the IDS to monitor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Jul 2010 21:19:52 GMT</pubDate>
    <dc:creator>Panos Kampanakis</dc:creator>
    <dc:date>2010-07-08T21:19:52Z</dc:date>
    <item>
      <title>IDS module setup, what traffic to capture</title>
      <link>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491253#M66992</link>
      <description>&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-family: Times New Roman; color: #000000; font-size: 12pt;"&gt;I have a WS-SVC-IDSM-2 that I have been tasked to setup. Currently the focus is around our pair of ASA’s that are used for internet access but the scope could increase. I am getting some conflicting information on how to setup the packet capture to the IDS module. I am leaning towards VACLS but I keep wondering if I do that will I miss traffic somewhere? As an example if I setup the VACL to capture TCP port 80,443, and 25 I am afraid I may miss some type of traffic on that VLAN. How do I determine what traffic I should send to the IDS module? &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 12:03:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491253#M66992</guid>
      <dc:creator>Bill19795_2</dc:creator>
      <dc:date>2019-03-10T12:03:16Z</dc:date>
    </item>
    <item>
      <title>Re: IDS module setup, what traffic to capture</title>
      <link>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491254#M66993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it all depends on what traffic is going through your network.&lt;/P&gt;&lt;P&gt;If you have apps different than email, http and https that you want to be IDS protected then you would need to expand the VACL.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can use Netflow to see what applications are running through the network.&lt;/P&gt;&lt;P&gt;Then you can decide which ones you don't trust and want the IDS to monitor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jul 2010 21:19:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491254#M66993</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-07-08T21:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: IDS module setup, what traffic to capture</title>
      <link>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491255#M66994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to Panos' recommendations on methods for determining traffic to inspect with the IDSM-2, also keep in mind that the IDSM-2 is rated to inspect ~500 Mbps of traffic.&amp;nbsp; If the traffic you will be sending to the IDSM-2 exceeds that amount, it will most likely not be inspected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That you mention having ASAs in your environment, have you considered deploying Cisco's AIP-SSM within the ASA?&amp;nbsp; There are multiple models for different traffic requirements, and they can inspect traffic that is flowing through the ASA.&amp;nbsp; You can find out more about the AIP-SSM here:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/go/aipssm"&gt;http://www.cisco.com/go/aipssm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Jul 2010 10:42:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491255#M66994</guid>
      <dc:creator>Scott Fringer</dc:creator>
      <dc:date>2010-07-09T10:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: IDS module setup, what traffic to capture</title>
      <link>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491256#M66995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using a VACL to capture traffic on a 6500 I want to capture several types of traffic on my internal LAN. I have the VACL to do this. I also want to make sure I capture everything destined for and sourced from my ASA. Can I use a MAC ACL to capture the traffic? If I capture the traffic with a MAC ACL and apply that to the VACL will the IPS device process it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jul 2010 23:43:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ids-module-setup-what-traffic-to-capture/m-p/1491256#M66995</guid>
      <dc:creator>Bill19795_2</dc:creator>
      <dc:date>2010-07-12T23:43:06Z</dc:date>
    </item>
  </channel>
</rss>

