Identification of application protocols in the web interface

This table shows how the web interface system identifies application protocols:

System identification of application protocols

Identification

Description

Application protocol name

The Cloud-Delivered Firewall Management Center lists the protocol name if it is:

  • Positively identified by the system

  • Identified using NetFlow data and a correlation exists in /etc/sf/services

  • Manually identified using the host input feature

  • Identified by Nmap or an active source

pending

The Cloud-Delivered Firewall Management Center identifies an application protocol as pending if the system can neither positively nor negatively identify the application.

The system usually needs to collect and analyze more connection data to identify a pending application.

In the Application Details and Servers tables and in the host profile, the pending status appears only where specific application protocol traffic is detected, not inferred from detected client or web application traffic.

unknown

The Cloud-Delivered Firewall Management Center identifies an application protocol as unknown if:

  • the application does not match any of the system's detectors.

  • the application protocol was identified using NetFlow data, but no port-application protocol correlation exists in /etc/sf/services.

  • Snort has closed the session, but the session still persists in the device. Here, the traffic is allowed to pass through the firewall, but the application is not detected.

blank

All available detected data has been examined, but no application protocol was identified. In the Application Details and Servers tables and in the host profile, the application protocol is left blank for generic client traffic without HTTP connections.