Webbrowsing on non-standard http ports....

[smccall]

What is the best way for me to implement a rule that allows http traffic over non standard ports?

Our security standards require that we use a feature similar to what is available in Checkpoint that allows us to lock the port down based on protocol. Ex: port 55000 is open and allowed assuming the traffic is http or https.

Any help would be appreciated.

[sjamaluddin]

When creating security rules, in the Application section configure: Web Browsing but in the Service section refer to the ports you are interested in allowing.

You may have to create a custom service and allow these non standard ports and then call that custom service in the security rule (where it says service). That way when traffic is checked against the security rule, you'd have web browsing AND the port (allowed via service) and only if the two web browsing on that non standard port match, will the traffic be allowed

So e.g.  your service would look like

Where service-http goes to 80 and 8080

and the security policy would be:

[sraghunandan · Accepted solution]

I would suggest you to set the application as any and service port as the non-standard port that you use. Once the traffic traverses the firewall the application would show up and then you can modify the rule to incorporate it.

[smccall]

I goofed around a bit and figured this was the way to do it, but thank you very much for the response.

Nice to have someone confirm my thoughts.