<?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: Block rogue VPN in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262165#M74292</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/95864"&gt;@VincentPresogna&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here's an example on how blocking TOR (for example) :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRtCAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRtCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It explains by blocking certain applications :&lt;/P&gt;
&lt;P&gt;Create a security policy to block the following applications to the internet:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;tor&lt;/LI&gt;
&lt;LI&gt;tor2web&lt;/LI&gt;
&lt;LI&gt;ssh&lt;/LI&gt;
&lt;LI&gt;ssh-tunnel&lt;/LI&gt;
&lt;LI&gt;ike&lt;/LI&gt;
&lt;LI&gt;ipsec-esp&lt;/LI&gt;
&lt;LI&gt;http-proxy&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, you can also do it similar to the way you describe in your post by blocking service ports 4500 and 500 in the rulebase or in combination with the applications shown above.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
    <pubDate>Fri, 24 May 2019 06:31:23 GMT</pubDate>
    <dc:creator>kiwi</dc:creator>
    <dc:date>2019-05-24T06:31:23Z</dc:date>
    <item>
      <title>Block rogue VPN</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262120#M74287</link>
      <description>&lt;P&gt;I am seeing this in my system logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;IKE phase-1 negotiation is failed. Couldn't find configuration for IKE phase-1 request for peer IP 172.250.246.42[500].&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How can I block this? I been a Cisco guy for a longtime and new to Palo Alto. On my old cisco asa I could block an ip at the control plane like this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;access-list cp-outside deny udp host 172.250.246.42 any eq 4500&lt;/P&gt;&lt;P&gt;access-list cp-outside deny udp host 172.250.246.42 any eq 500&lt;/P&gt;&lt;P&gt;access-list cp-outside deny esp host 172.250.246.42 any&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What would be the equivelant for Palo Alto?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 21:44:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262120#M74287</guid>
      <dc:creator>VincentPresogna</dc:creator>
      <dc:date>2019-05-23T21:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: Block rogue VPN</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262165#M74292</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/95864"&gt;@VincentPresogna&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here's an example on how blocking TOR (for example) :&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRtCAK" target="_blank" rel="noopener"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClRtCAK&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It explains by blocking certain applications :&lt;/P&gt;
&lt;P&gt;Create a security policy to block the following applications to the internet:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;tor&lt;/LI&gt;
&lt;LI&gt;tor2web&lt;/LI&gt;
&lt;LI&gt;ssh&lt;/LI&gt;
&lt;LI&gt;ssh-tunnel&lt;/LI&gt;
&lt;LI&gt;ike&lt;/LI&gt;
&lt;LI&gt;ipsec-esp&lt;/LI&gt;
&lt;LI&gt;http-proxy&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, you can also do it similar to the way you describe in your post by blocking service ports 4500 and 500 in the rulebase or in combination with the applications shown above.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope this helps.&lt;/P&gt;
&lt;P&gt;-Kiwi&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 06:31:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262165#M74292</guid>
      <dc:creator>kiwi</dc:creator>
      <dc:date>2019-05-24T06:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: Block rogue VPN</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262187#M74300</link>
      <description>&lt;P&gt;A couple of ways you could do this. I personally would really look into the 3rd option, but the 1st and 2nd options are quick and easily configured.&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Specify any IP you wish to block in the policy allowing the traffic and utilize the 'negate-source' option. This will cause the specified source IPs to no-longer match the policy and it will hit the default interzone-default deny policy.&lt;/P&gt;&lt;P&gt;2) Create a Deny 'any' 'any' policy at the top of your rulebase&amp;nbsp;so you can easily block an address from your environment from one static location.&lt;/P&gt;&lt;P&gt;3) Utilize a tool like MineMeld to form a firewall readable External Dynamic List (EDL) and utilize the EDL in the deny policy mentioned above. This has an added benefit of being able to utilize the MineMeld API to programmatically add addresses into the list, which the firewall can pull on a schedule. This means you don't need to actually perform a commit to add an address into your deny policy.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 13:01:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262187#M74300</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-05-24T13:01:24Z</dc:date>
    </item>
    <item>
      <title>Re: Block rogue VPN</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262232#M74316</link>
      <description>&lt;P&gt;Thank for the inputs. I'll see what I can manage.&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 20:47:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/262232#M74316</guid>
      <dc:creator>VincentPresogna</dc:creator>
      <dc:date>2019-05-24T20:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Block rogue VPN</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/264586#M74419</link>
      <description>&lt;P&gt;Thank's to both of you. I was able to create a simple rule to block/drop that dang ip. I used Kiwi's idea for it. I made a drop rule for that ip with ipsec and ike as the service. BPry, thanks for the MineMeld idea. I was able to get that setup in a day and it's working also.&lt;/P&gt;</description>
      <pubDate>Fri, 31 May 2019 19:56:12 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/block-rogue-vpn/m-p/264586#M74419</guid>
      <dc:creator>VincentPresogna</dc:creator>
      <dc:date>2019-05-31T19:56:12Z</dc:date>
    </item>
  </channel>
</rss>

