Protocol Signatures

[Christian_Wagen]

What are the Protocol Signatures doing?

[HeikoAnkenbrand · Accepted solution]

Hi @Christian_Wagen,

In R80.xx and R81, the identification of most common protocols are done using Firewall services with protocol signature. 
Signatures are pieces of information taken from both "Client to Server" and "Server to Client" packets that eventually identify the protocol. During the Service matching process, signatures validate that the content of the connection is truly the configured protocol. Protocol Signatures are part of the matching process.

SecureXL packet flow:
After policy installation, all traffic matching the Service with Protocol Signature enabled, will use the Medium Patch of traffic flow (PXL, new name PSLXL).

To use matching by protocol signature and services:

- Add the matching service to the appropriate rule.
- Activate the Protocol Signature option.
- Enable Application Control and/or  URL Filtering Blades

[_Val_]

Please look here: https://community.checkpoint.com/t5/Security-Management/White-Paper-Protecting-IoT-Internet-of-Thing..., in the paper itself.

Protocol signature ensures the protocol is used according to RFC.

[valterj]

Hi All. 

Considering that Protocol Signature is a feature to provide more security and reliability to traffic inspection process, why is not enabled by default? Shouldn't this be the opposite, enabled by default and I disable if I need?

Regards. 

Valter Junior