<?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: Attack Pattern in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640996#M604339</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;We can check for &lt;SPAN style="color: #ff6600;"&gt;any attacks&lt;/SPAN&gt; using syslog messages, right???&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So an "Attack Pattern" would be a restricted defintion here: only packets that make to the ASA ruleset?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some firewall admins like to know who is knocking on their door even if the packets never make it to the device's ruleset.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 02 Mar 2011 04:16:06 GMT</pubDate>
    <dc:creator>lcaruso</dc:creator>
    <dc:date>2011-03-02T04:16:06Z</dc:date>
    <item>
      <title>Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640990#M604333</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am going to implement Syslog server in my environment.. how can we check any attack pattern in that logs???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One more doubt... do i need to configure in the severity-level???? which is the best??? is there any problem happen if i give debug in severity-level???&lt;/P&gt;&lt;P&gt;Please guide me... I need it so badly... Please reply ASAP...........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vipin&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:57:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640990#M604333</guid>
      <dc:creator>vipinrajrc</dc:creator>
      <dc:date>2019-03-11T19:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640991#M604334</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV class="jive-rendered-content"&gt;&lt;P&gt;Hello Vipin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;As such there is no harm in using level 7 logging(debugging) but please ensure you are not running on high CPU. Here is guide which talks about all the syslogging security levels and its description.&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/monitor_syslog.html#wp1082848"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/monitor_syslog.html#wp1082848&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using an ASA, you can mitigate SYN attacks, IP spoofing attacks and duplicate packets due to faulty NIC card in the network. Here is a nice document which talks about the same &amp;amp; syslog ids:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00809763ea.shtml"&gt;http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00809763ea.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is a document which can be refered to understand the syslog message using its id :&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/partner/docs/security/asa/asa80/system/message/logmsgs.html#wp4768722"&gt;http://www.cisco.com/en/US/partner/docs/security/asa/asa80/system/message/logmsgs.html#wp4768722&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All these documents will require login using your CCO id.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps. Please reply back if you need any further assistance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Chirag&lt;BR /&gt;&lt;SPAN style="font-size: 8pt;"&gt;P.S.: Please mark this thread as answered if you feel your query is answered. Do rate helpful posts.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN style="font-size: 8pt;"&gt;is thread as answered if you feel your query is answered. Do rate helpful posts.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Feb 2011 08:52:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640991#M604334</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-02-28T08:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640992#M604335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Chirag,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for you support.........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can check for any attacks using syslog messages, right???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vipin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Mar 2011 09:37:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640992#M604335</guid>
      <dc:creator>vipinrajrc</dc:creator>
      <dc:date>2011-03-01T09:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640993#M604336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Vipin,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, we can mitigate attacks by evaluating information in the syslogs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Chirag&lt;BR /&gt;&lt;SPAN style="font-size: 8pt;"&gt;P.S.: Please mark this thread as answered if you feel your query is answered. Do rate helpful posts.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 02:14:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640993#M604336</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-03-02T02:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640994#M604337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In reading these forums previously, I came to understand that not all drops are found in syslog entries. To see everything that is getting dropped, you must use a capture command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;cap alldrops type asp-drop all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh cap alldrops&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since some attacks or portions of them will be dropped, you cannot rely entirely upon syslog entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After coming from competing products, I was very disappointed to learn about this unexpected feature of the ASA platform.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 03:23:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640994#M604337</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-03-02T03:23:10Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640995#M604338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We were discussing here ways to backup the logs for future analysis and determine if there was a attack.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Chirag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 03:57:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640995#M604338</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-03-02T03:57:37Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640996#M604339</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;We can check for &lt;SPAN style="color: #ff6600;"&gt;any attacks&lt;/SPAN&gt; using syslog messages, right???&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So an "Attack Pattern" would be a restricted defintion here: only packets that make to the ASA ruleset?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some firewall admins like to know who is knocking on their door even if the packets never make it to the device's ruleset.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 04:16:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640996#M604339</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-03-02T04:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640997#M604340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA device is different from an IPS device. ASA syslogs are set pre-defined messages to report few aspects while in production. Logs suggest severity of the alert and can help in detecting only few kinds of attacks. For eg., ASA can detect IP spoof and SYN attacks but can't detect Day Zero attacks.&lt;/P&gt;&lt;P&gt;You are right, to see details of all packets hitting ASA, best is to use a packet capture. For detailed messages, you can also use capture in pcap format on the interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Chirag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 08:37:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640997#M604340</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-03-02T08:37:27Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640998#M604341</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;ASA device is different from an IPS device&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess the title of the ASA book (below) made me think it was an IPS, but maybe you mean it's not as complete as a dedicated IPS (I agree). The reason I noticed some drops not being in the syslog was I replaced a CheckPoint firewall with an ASA at my own site and wondered what happened to all of the probes I normally see. After reading these forums, I found the answer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There's nothing wrong with using a capture to see all drops and then looking at them with WireShark. It just means you have to realize the syslog doesn't have every single event that is seen on the outside interface. That was my original point.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 09:22:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640998#M604341</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-03-02T09:22:49Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640999#M604342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ASA book I mentioned (would not allow me to upload image in previous post)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Mar 2011 09:28:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1640999#M604342</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-03-02T09:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641000#M604343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Firstly this a very nice book to read if you are new to Cisco ASA. Yes, ASA is not an IPS device. We have IPS&amp;nbsp; available as an appliance, as a module and IOS based. The book talks about&amp;nbsp; the module available for ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Chirag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Mar 2011 01:41:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641000#M604343</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-03-03T01:41:52Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641001#M604344</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="laugh" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/laugh.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;3 Intrusion Detection / Prevention&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;3.1 ASA and Intrusion Prevention Systems&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;The Cisco ASA code allows for two ways to block malicious traffic. &lt;SPAN style="color: #ff0000;"&gt;All ASA models&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;&lt;SPAN style="color: #ff0000;"&gt;have a built-in rule set&lt;/SPAN&gt;, and various application inspection protocols. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;ASA models 5510 and &lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: small;"&gt;up, however, offer the option of installing and using &lt;SPAN style="color: #ff0000;"&gt;a separate intrusion prevention system &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: small;"&gt;(IPS) blade – the AIP-SSM module. The AIP-SSM works exactly like any other Cisco networkbased &lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: small;"&gt;IPS (NIPS), with the exception that, instead of requiring that SPAN ports be configured,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;or a device be placed in the physical path of the network, the AIP-SSM inspects traffic on the&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;backplane of the firewall while the traffic is still traversing it, giving faster response, and the&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;ability to filter traffic on all networks with a single device. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: 10pt;"&gt;Since tuning the IPS is beyond the &lt;/SPAN&gt;&lt;SPAN style="font-family: 'courier new', courier; font-size: small;"&gt;scope of this document, focus will remain on the application inspection &lt;SPAN style="color: #ff0000;"&gt;and smaller database &lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN style="color: #ff0000; font-family: 'courier new', courier; font-size: small;"&gt;of signature-based rules in the standard ASA code&lt;/SPAN&gt;&lt;/P&gt;&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Mar 2011 02:13:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641001#M604344</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-03-03T02:13:14Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641002#M604345</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yep, ASA has a feature called Theat Detection and we can also customize a few features by Modular Policy Framework(MPF) available on ASA.&lt;/P&gt;&lt;P&gt;Cisco ASA 8.2 or higher also supports BotNet&amp;nbsp; traffic detection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Chirag&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 02:16:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641002#M604345</guid>
      <dc:creator>csaxena</dc:creator>
      <dc:date>2011-03-04T02:16:28Z</dc:date>
    </item>
    <item>
      <title>Re: Attack Pattern</title>
      <link>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641003#M604346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it really depends on how you have setup your firewall, you can choose to try and make the most of a particular hardware but then it would just leed to eating up more memory and cpu&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can use features like threat detection and botnet but that will come with a price of increased memory usage and if your firewall is already running with good amount of mem utlization you might not want to enable everything, also we need to understand that fact that most of the modern day attacks are so clever that they look like perfect traffic at layer 3/4 and that is when we need some special devices meant for this purpose like IPS and some other solutions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now coming to how useful the syslogs are to detect data, well as you know syslogs are mainly for historical data, the affects of attack would be felt almost immediate in the form of increased amount of connections or traffic than usual, so you know the whole idea of learning about an attack becomes useless. And also the syslogs do show inconsistencies in connections but it is upto the network admin to look at them and differentiate between attack and normal behaviour which usually takes time and hence if you are looking for mitigating advanced attacks you should look at devices which are meant for this like IPS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 16:52:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/attack-pattern/m-p/1641003#M604346</guid>
      <dc:creator>Jitendriya Athavale</dc:creator>
      <dc:date>2011-03-04T16:52:17Z</dc:date>
    </item>
  </channel>
</rss>

