<?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: ASA email alerting in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402065#M683777</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not possible. These will be dropped by the firewall. You can see these in the asp drop captures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cap capasp type asp-drop all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh cap capasp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is configured to be alllowed - will send syslogs if tried to be accessed by some IP that is not allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is not even configured when tried to be accessed - the firewall just drops these packets and not log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 10 Apr 2010 03:59:25 GMT</pubDate>
    <dc:creator>Kureli Sankar</dc:creator>
    <dc:date>2010-04-10T03:59:25Z</dc:date>
    <item>
      <title>ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402059#M683771</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have been asked to provide a method of being emailed should a persistant public IP be trying to access out external IP of our ASA, are their anyways of doig this?&amp;nbsp; I don't want to get an email if one or 2 hits form the same IP are "seen" but if there are 40-50 from the same suggesting some sort of penetration activity?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've got some of the alerts going to my syslog server (solarwinds) but it can't do anything clever.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:30:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402059#M683771</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2019-03-11T17:30:47Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402060#M683772</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Unfortunately not a supported feature on ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA can only send email notifications for syslog messages on specific syslog severity.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 08:59:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402060#M683772</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-04-09T08:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402061#M683773</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looks like my syslog viewer can do some sort of email alerting, I can see message type "ASA-1-710003" appear and I now get an email, but I need to suppress it somehow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I don't understand is I get syslog alerts for denied access to our ASA, but we have other devices with public IP's that are NAT'd to their private addresses that I don't get denies from, it this down tot he device behind the NAT or shoudl the firewall also pickup these denies?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 09:26:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402061#M683773</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-09T09:26:16Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402062#M683774</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I assume the deny access would be syslog from access-list on interfaces.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 09:47:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402062#M683774</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2010-04-09T09:47:53Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402063#M683775</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 09:57:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402063#M683775</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-09T09:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402064#M683776</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For example we have a few public IP addresses going to web servers behind the firewall, I need a deny message to be sent our syslog server should the attempt be anything other that port 80.  How can I achieve this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is strange also  if I try and telnet to our ASA over the internet on port 80 or 23 I get a deny message sent to the syslog server but if I telnet on any other random port I don't get a deny log, it gets blocked but that's it I need to record this and for the other servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Apr 2010 12:07:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402064#M683776</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-09T12:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402065#M683777</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not possible. These will be dropped by the firewall. You can see these in the asp drop captures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cap capasp type asp-drop all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sh cap capasp&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is configured to be alllowed - will send syslogs if tried to be accessed by some IP that is not allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is not even configured when tried to be accessed - the firewall just drops these packets and not log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Apr 2010 03:59:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402065#M683777</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-10T03:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402066#M683778</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, how can I tell if we are being targeted from an external IP on the outside interface lots of the time?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I run your capture command will it show all drops from all interfaces or just the outside interface?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Apr 2010 06:58:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402066#M683778</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-10T06:58:29Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402067#M683780</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That is correct. ASP drop will show all drops - all interfaces.&lt;/P&gt;&lt;P&gt;for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have asdm/443, telnet and ssh allowed on my firewall. I tried a telnet to port 556 from the outside and the asp drop captures shows below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA# sh cap capasp | i 556&lt;BR /&gt;&amp;nbsp;&amp;nbsp; 2: 23:16:44.371425 802.1Q vlan#10 P0 10.117.14.69.58538 &amp;gt; 172.18.254.34.556: S 3707472990:3707472990(0) win 65535 &lt;MSS 1260=""&gt; Drop-reason: (acl-drop) Flow is denied by configured rule&lt;BR /&gt;&amp;nbsp; 21: 23:16:54.769003 802.1Q vlan#10 P0 10.117.14.69.58543 &amp;gt; 172.18.254.34.556: S 185959746:185959746(0) win 65535 &lt;MSS 1260=""&gt; Drop-reason: (acl-drop) Flow is denied by configured rule&lt;BR /&gt;&amp;nbsp; 23: 23:16:55.677500 802.1Q vlan#10 P0 10.117.14.69.58543 &amp;gt; 172.18.254.34.556: S 185959746:185959746(0) win 65535 &lt;MSS 1260=""&gt; Drop-reason: (acl-drop) Flow is denied by configured rule&lt;BR /&gt;&amp;nbsp; 26: 23:16:56.680323 802.1Q vlan#10 P0 10.117.14.69.58543 &amp;gt; 172.18.254.34.556: S 185959746:185959746(0) win 65535 &lt;MSS 1260=""&gt;&lt;/MSS&gt;&lt;/MSS&gt;&lt;/MSS&gt;&lt;/MSS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All SYNs from my outside client are dropped.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Apr 2010 12:27:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402067#M683780</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-10T12:27:29Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402068#M683781</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyway this can be outputted to a syslog server?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How would a company know if they are being hacked, I know the firewall is dropping the packets, but somebody could be trying for weeks and I wouldn't even know?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Apr 2010 07:01:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402068#M683781</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-11T07:01:54Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402069#M683783</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;No. ASP drops cannot be sent to syslog server.&amp;nbsp; Unfortunately not.&amp;nbsp; Threat Detection feature will help you: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_threat.html#wp1088111"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/conns_threat.html#wp1088111&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Besides this you need an IPS/IDS device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Apr 2010 13:09:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402069#M683783</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-11T13:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402070#M683786</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.  I do have the IPS module installed but again I think it only logs on allowed traffic passing through the firewall.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Apr 2010 15:56:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402070#M683786</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-11T15:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402071#M683789</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;NO. You can do a few things with an IPS/IDS device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; a. Deny Attacker Inline - Create an ACL that denies all traffic from the suspected source IP address&lt;/P&gt;&lt;P&gt;&amp;nbsp; b. Deny connection Inline - Send resets to terminate the TCP flow&lt;/P&gt;&lt;P&gt;&amp;nbsp; c. Deny packet Inline - Do not transmit the packet (inline only)&lt;/P&gt;&lt;P&gt;&amp;nbsp; d. Produce Alert - Generate an alarm message&lt;/P&gt;&lt;P&gt;&amp;nbsp; e. Reset TCP connection - Drop the packet and all future packets from the TCP flow&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Read about it here: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ips.html"&gt;http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ips.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;A href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/ips.html#wp1090830" onclick=""&gt;Figure 59-1&lt;/A&gt; shows the traffic flow when running the AIP SSM/SSC in inline mode. In this example, the AIP SSM/SSC automatically blocks traffic that it identified as an attack. All other traffic is forwarded through the adaptive security appliance. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-KS&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 11 Apr 2010 21:11:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402071#M683789</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2010-04-11T21:11:35Z</dc:date>
    </item>
    <item>
      <title>Re: ASA email alerting</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402072#M683798</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is what we have configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;policy-map global_policy&lt;BR /&gt; class myipsclass&lt;BR /&gt;&amp;nbsp; ips inline fail-open sensor vs0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I asked TAC about the report and they also say I can't do it.&amp;nbsp; Is this do to me using "ips inline fail-open" and not one of the other options you mentioned?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Apr 2010 09:30:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-alerting/m-p/1402072#M683798</guid>
      <dc:creator>Andy White</dc:creator>
      <dc:date>2010-04-12T09:30:43Z</dc:date>
    </item>
  </channel>
</rss>

