How to check not detected open or allowed ports in service rule policy

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

How to check not detected open or allowed ports in service rule policy

L0 Member

NGFW Hi, Any idea if there is a tool to trace in PA5220 to check the un-detected open or allowed ports in rule policy. 

For example from a source IP 192.168.x.x.x. to a destination public IP (web server) . In the service I only specify port 443 but upon checking there are a lot of open ports that were allowed. This poses a security vulnerability in my network.

 

Any help would be much greatly appreciated. A thousand thank you in advance 🙂

Giovani Zapanta
1 accepted solution

Accepted Solutions

L4 Transporter

Hello,

 

First thought would be its either hitting a different rule or the service object is incorrect. If you look at the service object is the destination set to 443. Heres and example of the pre-defined one:

Claw4609_0-1709147005751.png

 

Otherwise it may be hitting a different rule. You can test example traffic and see which rule it would hit. If you for to Policies>Security at the bottom there is a test policy match where you can enter information and see what rule it would hit.

 

Claw4609_1-1709147089157.png

 

View solution in original post

2 REPLIES 2

L4 Transporter

Hello,

 

First thought would be its either hitting a different rule or the service object is incorrect. If you look at the service object is the destination set to 443. Heres and example of the pre-defined one:

Claw4609_0-1709147005751.png

 

Otherwise it may be hitting a different rule. You can test example traffic and see which rule it would hit. If you for to Policies>Security at the bottom there is a test policy match where you can enter information and see what rule it would hit.

 

Claw4609_1-1709147089157.png

 

A thousand thank you @Claw4609 . Done specifying the 443 part the only thing I have not tried is testing the policy match, seems I can do this temporarily but there is another platform that can detect that is capable of collecting, searching and analyzing the open/allowed ports that were not detected on the Palo fw.

Giovani Zapanta
  • 1 accepted solution
  • 466 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!