Getting Started with Custom Threat Prevention

This section provides a step-by-step workflow on how to configure Custom Threat Prevention with the default Optimized profile.

Limitations

Configuration

You can configure Threat Prevention to give the exact level of protection that you need, or you can decide to use the out-of-the-box configuration.

  1. Enable Custom Threat Prevention Software Blades in the Security Gateway / Cluster object.

  2. Optional: Create your Custom Threat Prevention profiles based on the default Custom Threat Prevention profiles.

    See Threat Prevention Profiles.

  3. Optional: Configure advanced Threat Prevention settings:

    • Security Gateway / Cluster object - Settings for Threat Prevention Software Blades and features.

    • Security Policies view > Threat Prevention > Exceptions

    • Security Policies view > Threat Prevention > click Custom Policy > refer to the Custom Policy Tools section

    • Security Policies view > HTTPS Inspection

    • Manage & Settings view > Blades > Threat Prevention > Advanced Settings

    • Security Gateway / each Cluster Member command line - Configuration commands and files (for example, for SSH Deep Inspection)

  4. Configure the Custom Threat Prevention policy.

  5. Install the Custom Threat Prevention policy.

  6. Monitor and Tune

    Use the Logs & Events view in to show logs related to Threat Prevention traffic. Use the logs and events data to better understand the use of these Software Blades in your environment and create an effective Rule Base. You can update the Rule Base directly from the Logs & Events view. You can add more exceptions that prevent or detect specific protections or have different tracking settings. For more information, see the R82.20 Logging and Monitoring Administration Guide.

  7. Notes: