topic Re: Custom Signature to allow LDAPS as SSL port 636 in Custom Signatures

Custom Signature to allow LDAPS as SSL port 636

palmanza — Tue, 11 Feb 2020 16:56:39 GMT

Hello Everyone,

Has anyone created a custom signature to create a custom APP-ID to allow SSL over port 636? I have read that decryption needs to be implemented for the Palo to identify the traffic to the right application but if decryption can not be completed how can this be done.

Thanks in advance.

Re: Custom Signature to allow LDAPS as SSL port 636

JoergSchuetter — Wed, 12 Feb 2020 17:25:21 GMT

Hello @palmanza

Is it mandatory to have a signature, or would application override suffice for your need?

I simply created a new application (copied over the things from ldap, named it ldaps), and created the override policy. The policies where ldap was listed as application were extended by ldaps.

Re: Custom Signature to allow LDAPS as SSL port 636

palmanza — Thu, 13 Feb 2020 14:34:12 GMT

I am enforcing APP-ID and wanted to do it at the application lever but your suggestion should be good. The insteresting part is that the Palo is showing hits to the rule with the custom rule but when I review the traffic it does not show anything with that rule. Any ideas on that?

Update on my own question.

Looks like I needed to create the APP override which is something I have not done before but was able to do it properly and now the rule it is showing the traffic properly.

Thanks