<?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 Yes. On your Access Control in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/need-help-whitelisting-vm-scanning/m-p/2915321#M43827</link>
    <description>&lt;P&gt;Yes. On your Access Control Policy, create a rule to "Trust" that traffic Source and/or destination.&amp;nbsp; Make sure you enable logging so that can search or validate has been Trust (do not inspect).&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2016 20:29:15 GMT</pubDate>
    <dc:creator>Ed Padilla Jr</dc:creator>
    <dc:date>2016-06-30T20:29:15Z</dc:date>
    <item>
      <title>Need Help Whitelisting VM Scanning</title>
      <link>https://community.cisco.com/t5/network-security/need-help-whitelisting-vm-scanning/m-p/2915320#M43826</link>
      <description>&lt;P&gt;I have internal Qualys vulnerability scans which target systems inside my web DMZ.&amp;nbsp; Once my AMP 8150 IPS devices see the traffic it appears to be coming from a&amp;nbsp;x-forwarded IP&amp;nbsp;address on&amp;nbsp;our load balancers.&amp;nbsp; Two things I can see when I analyze the packets on the IPS are:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;1. You can see the 'X-Forwarded-For' IP address is in fact the IP address of the Qualys scanner.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. We append the text into the packets: 'Qualys-Scan: VM'&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What are my options for not generating intrusion events for this traffic?&amp;nbsp; My hope was to look at the 'X-Forwarded-For' address and whitelist based on that, but it seems like that may not be possible on the Sourcefire platform(?).&amp;nbsp; Any ideas?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:38:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/need-help-whitelisting-vm-scanning/m-p/2915320#M43826</guid>
      <dc:creator>kyle.brearley</dc:creator>
      <dc:date>2019-03-10T13:38:11Z</dc:date>
    </item>
    <item>
      <title>Yes. On your Access Control</title>
      <link>https://community.cisco.com/t5/network-security/need-help-whitelisting-vm-scanning/m-p/2915321#M43827</link>
      <description>&lt;P&gt;Yes. On your Access Control Policy, create a rule to "Trust" that traffic Source and/or destination.&amp;nbsp; Make sure you enable logging so that can search or validate has been Trust (do not inspect).&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2016 20:29:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/need-help-whitelisting-vm-scanning/m-p/2915321#M43827</guid>
      <dc:creator>Ed Padilla Jr</dc:creator>
      <dc:date>2016-06-30T20:29:15Z</dc:date>
    </item>
  </channel>
</rss>

