Application detection
Application detection is a system capability that
-
analyzes IP traffic to identify commonly used applications on your network,
-
provides application awareness crucial for application control, and
-
identifies applications according to characteristics specified in detectors.
Application detection types and sources
The system detects three types of applications:
-
application protocols such as HTTP and SSH, representing communications between hosts
-
clients such as web browsers and email clients, representing software running on the host
-
web applications such as MPEG video and Facebook, representing the content or requested URL for HTTP traffic
The system identifies applications in network traffic according to the characteristics specified in the detector. For example, applications may be identified using ASCII patterns in packet headers. SSL protocol detectors use session information to identify the applications.
Application detectors come from two sources:
-
System-provided detectors detect web applications, clients, and application protocols based on system software version and VDB. Professional Services can import individual detectors. Release notes provide information on updated detectors.
-
Custom application protocol detectors are user-created to detect web applications, clients, and application protocols.
Implied application protocol detection, infers the existence of an application protocol based on client detection.
You can identify applications only if they originate from monitored network hosts as defined in your network discovery policy. If an internal host accesses an FTP server at an unmonitored remote site, the system does not identify the application protocol as FTP. However, if a remote or internal host accesses an FTP server on a monitored host, the system can identify the application protocol.
If the system identifies the client used by a monitored host to connect to a non-monitored server, it identifies the client's application protocol. However, it does not add this protocol to the network map. Client sessions must include a response from the server to occur for application detection.
The system characterizes each application that it detects; see Application rule conditions. The system uses these characteristics to create groups of applications, called application filters. Application filters are used to perform access control and to constrain search results and data used in reports and dashboard widgets.
You can also supplement application detector data using exported NetFlow records, Nmap active scans, and the host input feature.