<?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 My first sentence should in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985196#M43438</link>
    <description>&lt;P&gt;My first sentence should answer your question. A host in your network connects to a malicious Server in the Internet... A host that is not directly reachable from the Internet due to firewall rules and/or NAT can still be attacked if it opens up a session to an attacker, which can use this session to attack said client.&lt;/P&gt;</description>
    <pubDate>Tue, 15 Nov 2016 07:43:21 GMT</pubDate>
    <dc:creator>Oliver Kaiser</dc:creator>
    <dc:date>2016-11-15T07:43:21Z</dc:date>
    <item>
      <title>IPS reports</title>
      <link>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985193#M43434</link>
      <description>&lt;P&gt;IPS report shows victim IP address on which the attack was launched, how is external attacker able to attack specific private IP addresses in a huge infrastructure?&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 13:43:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985193#M43434</guid>
      <dc:creator>Reshma Raje</dc:creator>
      <dc:date>2019-03-10T13:43:00Z</dc:date>
    </item>
    <item>
      <title>The connection could be</title>
      <link>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985194#M43435</link>
      <description>&lt;P&gt;The connection could be established from the infected client to a C&amp;amp;C server. If the attack is initiated from the WAN to a server on-site you might see the private ip address because NAT is done before traffic is sent to the sfr module on Cisco ASA (or NAT is done on a router before your ips sensor).&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Let me know if this answers your question.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2016 17:48:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985194#M43435</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2016-11-14T17:48:27Z</dc:date>
    </item>
    <item>
      <title>Thank you for your reply but</title>
      <link>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985195#M43437</link>
      <description>&lt;P&gt;Thank you for your reply but my query is, attack from external IP on internal IP where the IPS report publishes internal IP on which there was an attack tried by the external IP...&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2016 04:14:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985195#M43437</guid>
      <dc:creator>Reshma Raje</dc:creator>
      <dc:date>2016-11-15T04:14:25Z</dc:date>
    </item>
    <item>
      <title>My first sentence should</title>
      <link>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985196#M43438</link>
      <description>&lt;P&gt;My first sentence should answer your question. A host in your network connects to a malicious Server in the Internet... A host that is not directly reachable from the Internet due to firewall rules and/or NAT can still be attacked if it opens up a session to an attacker, which can use this session to attack said client.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Nov 2016 07:43:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ips-reports/m-p/2985196#M43438</guid>
      <dc:creator>Oliver Kaiser</dc:creator>
      <dc:date>2016-11-15T07:43:21Z</dc:date>
    </item>
  </channel>
</rss>

