Configure custom application detectors

Configure custom application detectors to identify specific applications and protocols not covered by the default detectors, enabling more accurate traffic analysis and control.

Configure basic or advanced custom application detectors.

Procedure


Step 1

Select Policies > + Show more > Advanced > Applications.

Step 2

Click Create Custom Detector, and enter a Name and a Description.

Step 3

Choose an Application Protocol from the application drop-down list.

You have these options:

  • If you are creating a detector for an existing application protocol (for example, if you want to detect a particular application protocol on a non-standard port), select the application protocol from the drop-down list.

  • If you are creating a detector for a user-defined application, follow the procedure outlined in Create a user-defined application.

Step 4

Click Detector Type as Basic or Advanced and click OK.

Step 5

Configure Detection Patterns or Detection Criteria or Encrypted Visibility Engine Process Assignments:

  • If you are configuring a basic detector, specify preset Detection Patterns as described in Specifying detection patterns in basic detectors.

  • If you are configuring an advanced detector, specify custom Detection Criteria as described in Specify detection criteria in advanced detectors.

  • If you are configuring an encrypted visibility engine (EVE) detector, specify custom EVE process assignments as described in Specifying EVE Process Assignments section in this chapter.

    Caution

    Advanced custom detectors are complex; ensure your knowledge of .lua files is adequate. Incorrect configuration can negatively impact performance or detection.

Step 6

Optionally, use Packet Captures to test the new detector as described in Testing a custom application protocol detector.

Step 7

Click Save.

Note

If you include the application in an access control rule, the detector is automatically activated and cannot be deactivated while it's in use.


The custom application detector is created and is ready for activation in access control rules and policies.

What to do next

Activate the detector as described in Activate and deactivate detectors.