NGFW Online Help

Home
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
Defining Situation elements
Situation elements contain the context information that defines the pattern that the NGFW Engine looks for in the inspected traffic. Situation elements also define the patterns that match events in the traffic.
Examples of custom Situation elements
These examples illustrate some common uses for Situations and the general steps on how each example is configured.

About this Help
Introduction to the Forcepoint Next Generation Firewall solution
Before setting up Forcepoint Next Generation Firewall (Forcepoint NGFW), it is useful to know what the different components do and what engine roles are available.
Deployment
Before you can set up the system and start configuring elements, you must consider how the different SMC components should be positioned and deployed.
Setting up
After deploying the SMC components, you are ready to start using the Management Client and carrying out some of the first configuration tasks.
Monitoring
You can use the SMC to monitor system components and third-party devices. You can also view and filter logs, and create Reports from them.
Controlling engines
You can command and set options for engines through the Management Client or on the engine command line. You can also stop traffic manually.
SMC configuration
Security Management Center (SMC) configuration allows you to customize how the SMC components work.
Engine element configuration
You can create and modify Firewalls, IPS engines, Layer 2 Firewalls, Master NGFW Engines and Virtual NGFW Engines. You can configure the engine properties, activate optional features, and configure advanced engine settings.
Routing
Use the Management Client to configure static or dynamic routing, and use a Multi-Link configuration to manage and distribute inbound and outbound connections.
Traffic inspection policies
Policies are key elements that contain rules for allowing or blocking network traffic and inspecting the content of traffic.
- Creating and managing policy elements
  Policy elements are containers for the rules that determine how NGFW Engines, Master NGFW Engines, and Virtual NGFW Engines examine traffic. The policy elements for the engines include Template Policies, Policies, and Sub-Policies.
- Ethernet rules
- Access rules
  Access rules are lists of matching criteria and actions that define how the engine treats different types of network traffic. They are your main configuration tool for defining which traffic is stopped and which traffic is allowed.
- NAT rules
- Inspection Policy elements
  Inspection Policy elements define how the engines look for patterns in traffic allowed through the Access rules and what happens when a certain type of pattern is found.
- Editing policies
  The rules in Firewall, IPS, Layer 2 Firewall, and Layer 2 Interface Policies allow you to control how the engines inspect and filter network traffic, and how NAT (network address translation) is applied on Firewalls, Master NGFW Engines, and Virtual Firewalls.
- Defining IP addresses
  When you define IP addresses as elements, you can use the same definitions in multiple configurations for multiple components.
- Working with Service elements
  Service elements match traffic based on protocol or port and set options for advanced inspection of traffic. Service elements are used in Firewall Policies, IPS Policies, Layer 2 Firewall Policies, and Layer 2 Interface Policies.
- Defining Situation elements
  Situation elements contain the context information that defines the pattern that the NGFW Engine looks for in the inspected traffic. Situation elements also define the patterns that match events in the traffic.
  - Getting started with Situation elements
    Situation elements define a pattern in traffic that the engine looks for.
  - Situations configuration overview
    Configuring Situation elements involves several main steps.
  - Create custom Situation elements
    You can create custom Situation elements in addition to using the predefined ones.
  - Context options for Situation elements
    Adding a Context to a Situation allows you to define what kinds of patterns you want to look for in the traffic.
  - Defining Context Options for Correlation Situation elements
    Correlation Contexts define the patterns for matching groups of related events in traffic.
  - Anti-Malware Contexts for Situation elements
    Anti-Malware Contexts are used to detect malware in HTTP, HTTPS, IMAP, POP3, and SMTP protocol traffic.
  - DoS Detection Contexts for Situation elements
    The DoS detection Contexts provide parameters for detecting DoS (Denial of Service) events in network traffic.
  - Scan Detection Contexts for Situation elements
    The Scan detection Contexts provide parameters for detecting attempts to scan which IP addresses are in use or which ports are open in your systems.
  - Protocol-specific Contexts for Situation elements
    The protocol-specific Contexts are used to detect a particular characteristic in the network traffic.
  - File Contexts for Situation elements
    The File Contexts are used to detect malicious or suspicious content in transferred files regardless of the transport protocol used.
  - System Contexts for Situation elements
    The System Contexts are used for errors and other system events.
  - Default elements for Situation elements
    There are many predefined Contexts, Situations, Tags, and Vulnerabilities.
  - Using Tags with Situation elements
    Tag elements collect together several Situations that have something in common.
  - Vulnerability elements and how they work
    Vulnerability elements provide a short description of the event that has matched and a reference to external vulnerability information (CVE/BID/MS/TA).
  - Using Situation elements
    You use Situation elements to define what you want to detect with the Inspection Policy.
  - Examples of custom Situation elements
    These examples illustrate some common uses for Situations and the general steps on how each example is configured.
    - Example: detecting the use of forbidden software
      Engine-specific examples of using custom Situations to detect traffic patterns associated with specific software.
    - Example: counting events to reduce number of repeated queries to a server
      An example of using the Count context in a Correlation Situation.
    - Example: preventing access to forbidden websites
      An example of using Situations to block access to specific websites.
- Using Network Application elements
  Network Application elements collect combinations of identified characteristics and detected events in traffic to dynamically identify traffic related to the use of a particular network application.
- Defining User Response elements
  With the User Response element, you can send customized replies to users, instead of just closing an HTTP or HTTPS connection.
- Quality of Service
  The Quality of Service (QoS) features allow you to manage bandwidth and prioritize connections on the engines. QoS features are available on Firewalls, IPS engines, Layer 2 Firewalls, Master NGFW Engines, Virtual Firewalls, Virtual IPS engines, and Virtual Layer 2 Firewalls.
- File filtering
  Monitoring and restricting what data is sent out is an important part of data loss prevention (DLP). File filtering allows you to restrict the file types that are allowed in and out through the firewall, and to apply malware detection to files.
- Integrating Endpoint Context Agent
  If you have installed Forcepoint Endpoint Context Agent (ECA) clients on the endpoints in your network, you can collect information about endpoint clients, and use the information for access control in the SMC.
- Filtering URLs
  URL filtering allows you to filter URLs based on categories of content or lists of individual URLs.
- Anti-malware scanning
  An anti-malware scanner compares network traffic against an anti-malware database to search for malware. If malware is found, the traffic is stopped or content is stripped out.
- Protocol Agents on engines
  Protocol elements of the Protocol Agent type are special modules for some protocols and services that require advanced processing. Protocol Agents can enforce policies on the application layer.
- Sidewinder Proxies
  Sidewinder Proxies are software modules that provide network level proxies, protocol validation, and configurable application level protocol filtering and translation on Forcepoint Next Generation Firewall.
- Setting up TLS inspection
  The TLS inspection feature decrypts TLS connections so that they can be inspected for malicious traffic and then re-encrypts the traffic before sending it to its destination.
- Redirecting traffic to a proxy service for external inspection
  In addition to inspecting traffic on the NGFW Engine, you can transparently redirect traffic to a proxy service in the cloud or on premises. For example, you can redirect all HTTP and HTTPS traffic to the Forcepoint Web Security Cloud service.
- Blacklisting IP addresses
  Blacklisting is a way to temporarily block unwanted network traffic either manually or automatically with blacklist requests from an NGFW Engine or Log Server. Firewalls, IPS engines, Layer 2 Firewalls, and Virtual NGFW Engines can use a blacklist for blocking traffic.
Users and authentication
User accounts are stored in internal databases or external directory servers. You can use Forcepoint NGFW in the Firewall/VPN role or external authentication servers to authenticate users.
Virtual private networks
Forcepoint NGFW supports both policy-based and route-based VPNs (virtual private networks).
Maintenance and upgrades
Maintenance includes procedures that you do not typically need to do frequently.
Troubleshooting
Troubleshooting helps you resolve common problems in the Forcepoint NGFW and SMC.
Appendices

Examples of custom Situation elements

These examples illustrate some common uses for Situations and the general steps on how each example is configured.

Example: detecting the use of forbidden software
Engine-specific examples of using custom Situations to detect traffic patterns associated with specific software.
Example: counting events to reduce number of repeated queries to a server
An example of using the Count context in a Correlation Situation.
Example: preventing access to forbidden websites
An example of using Situations to block access to specific websites.

Copyright © 2018 Forcepoint LLC