Implied application protocol detection from client detection

Implied application protocol detection is a process that

  • occurs when the system can identify the client used by a monitored host to access a non-monitored server,

  • allows the Cloud-Delivered Firewall Management Center to infer that the connection uses the application protocol that corresponds with the client, and

  • provides application protocol information for connections where monitored hosts access non-monitored servers.

Consequences of implied application protocol detection

This process has these consequences:

  • The system does not generate a New TCP Port or New UDP Port event for these servers, preventing their appearance in the Servers table. Additionally, the detection of these application protocols cannot trigger discovery event alerts or correlation rules.

  • The application protocol is not associated with a host. Its details cannot be viewed in host profiles, its server identity is not set, and its information is not used in host profile qualifications for traffic profiles or correlation rules. In addition, the system does not associate vulnerabilities with hosts based on this type of detection.

You can trigger correlation events when application protocol information is present in a connection. You can also use the application protocol information in connection logs to create connection trackers and traffic profiles.