<?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 An update to this, I have a in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898018#M1037816</link>
    <description>&lt;P&gt;An update to this, I have a tac case raised. I've tried creating correlation rules to stop email alerting and this has not worked either. SHould hear back from Tac today who are labbing and testing also.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jun 2016 21:15:52 GMT</pubDate>
    <dc:creator>evan.chadwick1</dc:creator>
    <dc:date>2016-06-30T21:15:52Z</dc:date>
    <item>
      <title>How to create email alerting for some networks but not others</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898013#M1037762</link>
      <description>&lt;P&gt;Hi, I have email alerting working but want to only receive emails for my Corporate Subnets and not my Free Wifi Subnets.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;How can I achieve this?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 13:01:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898013#M1037762</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2019-03-12T13:01:29Z</dc:date>
    </item>
    <item>
      <title>Also can you configure</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898014#M1037775</link>
      <description>&lt;P&gt;Also can you configure different HTTP responses based on different subnets behind a managed device?&lt;/P&gt;</description>
      <pubDate>Wed, 25 May 2016 00:33:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898014#M1037775</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-05-25T00:33:49Z</dc:date>
    </item>
    <item>
      <title>An update to this. I"ve tried</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898015#M1037790</link>
      <description>&lt;P&gt;An update to this. I"ve tried adding a supression rule in my IPS policy. I chose the ever so popular event id of 28039, which makes sourcefire generate an event when a person performs a dns request to a .pw domain.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I added a supression rule source subnet of my Free Wifi. However I still receive email alerts when an ip in this range browses to a .pw domain.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&amp;lt;update: I had not deployed the policy, once I did this the supression worked. Still in the hunt for a global solution rather than entering supression rules all the time, furthermore which&amp;nbsp;can not take advantage of an Object group&amp;gt;&lt;/P&gt;</description>
      <pubDate>Sun, 29 May 2016 22:30:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898015#M1037790</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-05-29T22:30:59Z</dc:date>
    </item>
    <item>
      <title>Hi Evan,</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898016#M1037803</link>
      <description>&lt;P&gt;Hi Evan,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;After adding suppression, you have to commit the policy and then deploy it again.&lt;/P&gt;
&lt;P&gt;For the HTTP response issue, unfortunately there is no such option of different http response&lt;/P&gt;
&lt;P&gt;as this is a global setting under Policy-&amp;gt;advanced.&lt;/P&gt;
&lt;P&gt;Rate if it helps.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Ankita&lt;/P&gt;</description>
      <pubDate>Mon, 30 May 2016 06:16:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898016#M1037803</guid>
      <dc:creator>ankojha</dc:creator>
      <dc:date>2016-05-30T06:16:55Z</dc:date>
    </item>
    <item>
      <title>I still don't feel that</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898017#M1037810</link>
      <description>&lt;P&gt;I still don't feel that adding supression rules is the way forward. Especially since supression rules can not deal with objects. I'm wondering if this is a feature request. As correlation rules don't seem to handle objects either.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The significance of this means that if I have a large amount of /22 sites to supress for I have to enter each one individually. Also rather than have to create supression rules for each ID that gets triggered, why not enable a feature to globally create Alert Ignores for?&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2016 21:06:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898017#M1037810</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-06-02T21:06:00Z</dc:date>
    </item>
    <item>
      <title>An update to this, I have a</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898018#M1037816</link>
      <description>&lt;P&gt;An update to this, I have a tac case raised. I've tried creating correlation rules to stop email alerting and this has not worked either. SHould hear back from Tac today who are labbing and testing also.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2016 21:15:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898018#M1037816</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-06-30T21:15:52Z</dc:date>
    </item>
    <item>
      <title>Update:</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898019#M1037818</link>
      <description>&lt;P&gt;Update:&lt;/P&gt;
&lt;P&gt;A feature request has been raised. My workaround:&lt;/P&gt;
&lt;P&gt;Turn off all email alerting, via Policy&amp;gt;Alerts&lt;/P&gt;
&lt;P&gt;Then apply a correlation rule:&lt;/P&gt;
&lt;P&gt;if "intrusion event takes place"&lt;/P&gt;
&lt;P&gt;and source ip 'is not in' x.x.x.x/22 (network i want to protect and never hear about)&lt;/P&gt;
&lt;P&gt;and source ip 'is not in' x.x.x.x/22&amp;nbsp;&lt;SPAN&gt;(network i want to protect and never hear about)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;etc&amp;nbsp;&lt;/P&gt;
&lt;P&gt;etc&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2016 00:39:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/2898019#M1037818</guid>
      <dc:creator>evan.chadwick1</dc:creator>
      <dc:date>2016-08-04T00:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: Update:</title>
      <link>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/3371350#M1037823</link>
      <description>&lt;P&gt;I know the thread is a couple years old. I have the same need and wondering what is the best way to accomplish. If need be I can open a case with TAC. Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 18:29:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/how-to-create-email-alerting-for-some-networks-but-not-others/m-p/3371350#M1037823</guid>
      <dc:creator>8pcallahan</dc:creator>
      <dc:date>2018-04-23T18:29:08Z</dc:date>
    </item>
  </channel>
</rss>

