<?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: Mars Rules in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402349#M923797</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Thanks ganesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There
are plenty of rules in MARS to trigger the incident,If i deactivate
those i wont get any incident from that rule,but what are the most
typical one's which are always kept active in view of attack's and
service unavailability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not worked on MARS ,i will be going to install soon,making things clear before implementation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Hi Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out the below link hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044"&gt;http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ganesh.H&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 05 Mar 2010 15:00:23 GMT</pubDate>
    <dc:creator>Ganesh Hariharan</dc:creator>
    <dc:date>2010-03-05T15:00:23Z</dc:date>
    <item>
      <title>Mars Rules</title>
      <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402346#M923792</link>
      <description>&lt;P&gt;Hello Dear's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are many unwanted incidents generating in my MARS, how can i customized to important's only and to avoid unwanted ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:53:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402346#M923792</guid>
      <dc:creator>thomasandy32</dc:creator>
      <dc:date>2020-02-21T11:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: Mars Rules</title>
      <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402347#M923793</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hello Dear's&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are many unwanted incidents generating in my MARS, how can i customized to important's only and to avoid unwanted ones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check ou the below link on MARS rule configuration hope that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044"&gt;http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember to rate the helpful post&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ganesh.H&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 11:51:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402347#M923793</guid>
      <dc:creator>Ganesh Hariharan</dc:creator>
      <dc:date>2010-03-02T11:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: Mars Rules</title>
      <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402348#M923795</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks ganesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are plenty of rules in MARS to trigger the incident,If i deactivate those i wont get any incident from that rule,but what are the most typical one's which are always kept active in view of attack's and service unavailability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not worked on MARS ,i will be going to install soon,making things clear before implementation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 12:41:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402348#M923795</guid>
      <dc:creator>thomasandy32</dc:creator>
      <dc:date>2010-03-02T12:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: Mars Rules</title>
      <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402349#M923797</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Thanks ganesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There
are plenty of rules in MARS to trigger the incident,If i deactivate
those i wont get any incident from that rule,but what are the most
typical one's which are always kept active in view of attack's and
service unavailability.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have not worked on MARS ,i will be going to install soon,making things clear before implementation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;Hi Thomas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out the below link hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044"&gt;http://www.sans.org/reading_room/whitepapers/logging/configuring_and_tuning_cisco_csmars_2044&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ganesh.H&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Mar 2010 15:00:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402349#M923797</guid>
      <dc:creator>Ganesh Hariharan</dc:creator>
      <dc:date>2010-03-05T15:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: Mars Rules</title>
      <link>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402350#M923798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There's a "False Positive Tuning" link to the right of each incident.&amp;nbsp; You will need to review the data provided in the incident to decide if the information is relative to an attack.&amp;nbsp; The false positives, based on your discretion, can be logged but not alerted, or completely dropped.&amp;nbsp; You can configure false positives based on port information, IP, time/date, reporting device, etc.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Mar 2010 16:31:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mars-rules/m-p/1402350#M923798</guid>
      <dc:creator>chris.cumbaa</dc:creator>
      <dc:date>2010-03-15T16:31:22Z</dc:date>
    </item>
  </channel>
</rss>

