<?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: Unauthorized SSH access through port 22 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12013#M8810</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would definitely open a support case so that we can review the logs and configuration. I had a similar case recently, and the cause was a couple of configuration items (using applications listed as tcp/dynamic and setting tcp-reject-non-syn to no).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Nov 2013 13:22:10 GMT</pubDate>
    <dc:creator>cstancill</dc:creator>
    <dc:date>2013-11-15T13:22:10Z</dc:date>
    <item>
      <title>Unauthorized SSH access through port 22</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12012#M8809</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a rule that permit traffic from "untrust" to some servers in "DMZ" but only for applicacions FTP, SSL and web-browsing, the problem is someone has gained access through SSH using the tcp 22. Shouldn't the PaloAlto has block this kind of traffic? Anyone knows a solution for this problem or know how to block some ip address?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gonzalo Arroyo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2013 13:04:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12012#M8809</guid>
      <dc:creator>SOC_CSG</dc:creator>
      <dc:date>2013-11-15T13:04:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unauthorized SSH access through port 22</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12013#M8810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would definitely open a support case so that we can review the logs and configuration. I had a similar case recently, and the cause was a couple of configuration items (using applications listed as tcp/dynamic and setting tcp-reject-non-syn to no).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Nov 2013 13:22:10 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12013#M8810</guid>
      <dc:creator>cstancill</dc:creator>
      <dc:date>2013-11-15T13:22:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unauthorized SSH access through port 22</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12014#M8811</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My suggestion is after allowing the required apps (&lt;SPAN style="color: #3b3b3b; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt; FTP, SSL and web-browsing&lt;/SPAN&gt; ) what was the service set as ? If it is "Application-Default" indicating that only those ports will be opened which are used by the allowed apps as informed earlier.&lt;/P&gt;&lt;P&gt;By doing so no other port can be opened to pass through that security rule.&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, 15 Nov 2013 16:29:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/unauthorized-ssh-access-through-port-22/m-p/12014#M8811</guid>
      <dc:creator>Phoenix</dc:creator>
      <dc:date>2013-11-15T16:29:30Z</dc:date>
    </item>
  </channel>
</rss>

