<?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: vCenter Server Appliance Web user interface HTTPS Security Rule in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/vcenter-server-appliance-web-user-interface-https-security-rule/m-p/333954#M84290</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/135151"&gt;@ccarter&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Two things:&lt;/P&gt;&lt;P&gt;1) Have you enabled logging on the interzone-default security rulebase entry to actually get logs, or otherwise have a deny rule that would generate a log when this traffic isn't matching a security entry?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) You say that you created a custom application. Did you test that the custom application signature is properly catching the traffic and it isn't being matched to ssl?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I think is happening is that the custom application you created doesn't have a proper signature assigned and the traffic is being identified as ssl over tcp/5480, which wouldn't work if you have the service configured as application-default. Without having interzone-default set to log, or anything else that would capture and log traffic that doesn't match a security entry, you wouldn't have any logs to look at.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jun 2020 21:26:39 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2020-06-17T21:26:39Z</dc:date>
    <item>
      <title>vCenter Server Appliance Web user interface HTTPS Security Rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vcenter-server-appliance-web-user-interface-https-security-rule/m-p/333750#M84252</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Due to a number of system administrators working from home, I have been asked to allow&amp;nbsp;&lt;SPAN&gt;vCenter Server Appliance Web user interface HTTPS port 5480 through the firewall for administration over VPN (Global Protect).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Specifically port 5480. vCenter uses standard ports 80 and 443 and successfully navigates to the site.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I have been unable to trace the reason why the site cannot be reached and looking for suggestions as the palo is not showing any traffic in the logs (that i can find).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Steps I have done:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1. Created a new custom application object tcp\5480.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. Applied the new custom app to the relevant&amp;nbsp;security rule.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Wondering if anyone else has seen this behavior&amp;nbsp;before?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Cheers,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Chris&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2020 00:51:20 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vcenter-server-appliance-web-user-interface-https-security-rule/m-p/333750#M84252</guid>
      <dc:creator>ccarter</dc:creator>
      <dc:date>2020-06-17T00:51:20Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Server Appliance Web user interface HTTPS Security Rule</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/vcenter-server-appliance-web-user-interface-https-security-rule/m-p/333954#M84290</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/135151"&gt;@ccarter&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Two things:&lt;/P&gt;&lt;P&gt;1) Have you enabled logging on the interzone-default security rulebase entry to actually get logs, or otherwise have a deny rule that would generate a log when this traffic isn't matching a security entry?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2) You say that you created a custom application. Did you test that the custom application signature is properly catching the traffic and it isn't being matched to ssl?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What I think is happening is that the custom application you created doesn't have a proper signature assigned and the traffic is being identified as ssl over tcp/5480, which wouldn't work if you have the service configured as application-default. Without having interzone-default set to log, or anything else that would capture and log traffic that doesn't match a security entry, you wouldn't have any logs to look at.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2020 21:26:39 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/vcenter-server-appliance-web-user-interface-https-security-rule/m-p/333954#M84290</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-06-17T21:26:39Z</dc:date>
    </item>
  </channel>
</rss>

