<?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 Configuring a whitelist via in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081844#M18543</link>
    <description>&lt;P&gt;Configuring a whitelist via the whitelist tab within the correlation section.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 03:40:55 GMT</pubDate>
    <dc:creator>evan.chadwick1</dc:creator>
    <dc:date>2017-06-01T03:40:55Z</dc:date>
    <item>
      <title>whitelist violation change from priority 1</title>
      <link>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081842#M18523</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;is it possible to change whitelist violation severity? I believe by default they are priority 1 events. I'd like to test whitelist violations without causing incident tickets which are generated on P1 events.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 00:01:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081842#M18523</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2017-06-01T00:01:51Z</dc:date>
    </item>
    <item>
      <title>You mean a correlation</title>
      <link>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081843#M18536</link>
      <description>&lt;P&gt;You mean a correlation whitelist? &amp;nbsp;In your correlation policy when you add a rule you select the priority which can be None or 1-5. &amp;nbsp;This will set the priority of the resulting correlation event.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 03:08:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081843#M18536</guid>
      <dc:creator>atatistc</dc:creator>
      <dc:date>2017-06-01T03:08:12Z</dc:date>
    </item>
    <item>
      <title>Configuring a whitelist via</title>
      <link>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081844#M18543</link>
      <description>&lt;P&gt;Configuring a whitelist via the whitelist tab within the correlation section.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 03:40:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081844#M18543</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2017-06-01T03:40:55Z</dc:date>
    </item>
    <item>
      <title>I'm not sure if that was a</title>
      <link>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081845#M18552</link>
      <description>&lt;P&gt;I'm not sure if that was a follow-up question? &amp;nbsp;If you configure a white list via the White List tab under Correlation it's akin to creating a correlation rule. &amp;nbsp;It doesn't do anything by itself. &amp;nbsp;To have the White List evaluated against the target hosts and generate correlation events you need to create a correlation policy and add the White List to it, then activate the policy. &amp;nbsp;So, back to my original answer. &amp;nbsp;You set the priority in the correlation policy.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2017 01:52:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/whitelist-violation-change-from-priority-1/m-p/3081845#M18552</guid>
      <dc:creator>atatistc</dc:creator>
      <dc:date>2017-06-02T01:52:33Z</dc:date>
    </item>
  </channel>
</rss>

