Skip to content
Looking for the Security Operations help?

NDR appliance modes

The mode controls which detection engines the NDR appliance uses and how it receives and handles network traffic. You set the mode in Sophos Fusion.

There are two detection engine families:

  • NDR machine-learning (ML) and anomaly engines: These engines look for unusual behavior in network traffic.
  • IDS/IPS engine: This engine matches traffic against Snort IDS/IPS signatures. Depending on the mode, it detects matching traffic or blocks traffic. This requires the IDS/IPS license.

The appliance can receive and handle network traffic in two ways:

  • Sniffer: The appliance operates out of band and inspects a copy of the traffic from a SPAN or mirror port or network TAP. It can't block traffic.
  • Inline: The appliance operates inline, with network traffic passing through it:

    • Inline passive modes inspect the traffic without blocking it.
    • Inline active modes can block traffic.

All capture ports on a physical appliance use the same mode. You can't configure some capture ports for sniffer mode and others for inline mode.

Compare modes

Use the following table to compare the available modes:

Mode Deployment ML and anomaly engines IDS/IPS engine Blocks traffic IDS/IPS license
NDR Sniffer Yes No No Not required
NDR+IDS Sniffer Yes Yes No Required
IDS Sniffer No Yes No Required
NDR+IPS Passive Inline Yes Yes No Required
NDR+IPS Active Inline Yes Yes Yes Required
IPS Passive Inline No Yes No Required
IPS Active Inline No Yes Yes Required

Note

Physical appliances support all modes. Virtual appliances support only NDR, NDR+IDS, and IDS modes.

NDR

What it does: NDR mode uses the ML and anomaly engines to inspect a copy of network traffic. It detects and reports unusual network behavior but can't block traffic.

Wiring: The appliance operates in a sniffer deployment. Connect one or more capture interfaces to a SPAN or mirror port or network TAP. The capture interfaces receive traffic but don't forward it. Because the appliance isn't in the network traffic path, an appliance failure doesn't interrupt network traffic.

Sophos Fusion configuration: Set the mode to NDR.

Behavior: The ML and anomaly engines generate events in Sophos Fusion.

Licensing: The IDS/IPS license isn't required.

Limitations: NDR mode doesn't provide signature detection or blocking. Traffic visibility depends on the traffic sent to the appliance. Configure your SPAN, mirror port, or TAP to provide both directions of the traffic you want to inspect.

NDR+IDS

What it does: NDR+IDS mode uses both the ML and anomaly engines and the IDS engine. The ML and anomaly engines detect unusual network behavior, while the IDS engine detects traffic that matches configured signatures. The appliance can't block traffic.

Wiring: The appliance operates in a sniffer deployment. Connect the capture interfaces to a SPAN or mirror port or network TAP.

On a physical appliance:

  • Copper modules support up to eight capture interfaces.
  • Fiber modules support up to four capture interfaces.

Configure the traffic source to provide both directions of the traffic you want to inspect.

Sophos Fusion configuration: Set the mode to NDR+IDS. Select a rule set and configure the home net, external net, and HTTP ports settings. For out-of-band deployments, we recommend setting external net to any.

Behavior: The IDS engine generates detections and the ML and anomaly engines generate events in Sophos Fusion. Because the appliance isn't in the network traffic path, it can't affect network traffic.

Licensing: The IDS/IPS license is required.

Limitations: NDR+IDS mode can't block traffic. Changing a physical appliance from NDR+IDS to an inline mode requires re-cabling the capture interfaces.

IDS

What it does: IDS mode uses only the IDS engine to inspect a copy of network traffic and detect traffic that matches configured signatures. The ML and anomaly engines aren't used, and the appliance can't block traffic.

Wiring: The appliance operates in a sniffer deployment. Connect the capture interfaces to a SPAN or mirror port or network TAP.

On a physical appliance:

  • Copper modules support up to eight capture interfaces.
  • Fiber modules support up to four capture interfaces.

Sophos Fusion configuration: Set the mode to IDS. Select a rule set and configure the home net, external net, and HTTP ports settings.

Behavior: The IDS engine generates detections in Sophos Fusion. Because the appliance isn't in the network traffic path, it can't affect network traffic.

Licensing: The IDS/IPS license is required.

Limitations: IDS mode doesn't provide ML or anomaly detection and can't block traffic. Changing a physical appliance from IDS to an inline mode requires re-cabling the capture interfaces.

NDR+IPS Passive

What it does: NDR+IPS Passive mode uses both the ML and anomaly engines and the IPS engine. The appliance inspects traffic inline but doesn't block traffic. IPS detections indicate traffic that would be blocked in NDR+IPS Active mode.

Wiring: The appliance operates inline. Connect the capture interfaces in bridge pairs so that traffic enters one interface and leaves through its paired interface.

On a physical appliance:

  • Copper modules support up to four bridge pairs using eight interfaces.
  • Fiber modules support up to two bridge pairs using four interfaces.

Sophos Fusion configuration: Set the mode to NDR+IPS Passive. Select a rule set and configure the home net, external net, and HTTP ports settings.

Behavior: The ML and anomaly engines generate events, and the IPS engine generates detections for traffic that matches the selected rule set. The IPS engine doesn't block traffic. The selected rule set determines which detections are identified as traffic that would have been blocked in NDR+IPS Active mode.

You can use NDR+IPS Passive mode to evaluate and tune the IDS/IPS configuration before switching to NDR+IPS Active. Switching between these modes doesn't require re-cabling the appliance.

Licensing: The IDS/IPS license is required.

Limitations: The appliance is in the network traffic path. If the appliance fails or restarts, the appliance switches to bypass. Changing the appliance from NDR+IPS Passive to a sniffer mode requires re-cabling the capture interfaces.

NDR+IPS Active

What it does: NDR+IPS Active mode uses both the ML and anomaly engines and the IPS engine. The ML and anomaly engines generate events but don't block traffic. The IPS engine blocks matching traffic when the selected rule specifies a blocking action.

Wiring: The appliance operates inline. Connect the capture interfaces in bridge pairs so that traffic enters one interface and leaves through its paired interface.

On a physical appliance:

  • Copper modules support up to four bridge pairs using eight interfaces.
  • Fiber modules support up to two bridge pairs using four interfaces.

You can, for example, deploy the appliance between the LAN interface of a Sophos Firewall and a core switch.

Sophos Fusion configuration: Set the mode to NDR+IPS Active. Select a rule set and configure the home net, external net, and HTTP ports settings.

Behavior: When traffic matches a blocking signature, the appliance blocks the traffic and generates a detection in Sophos Fusion. The ML and anomaly engines generate events but don't block traffic.

You can use block and allow rules for specific hosts or ports. Bypass rules exclude matching traffic from inspection.

Licensing: The IDS/IPS license is required.

Limitations: The appliance is in the network traffic path. If the appliance fails or restarts, the appliance switches to bypass. Changing the appliance from NDR+IPS Active to a sniffer mode requires re-cabling the capture interfaces.

IPS Passive

What it does: IPS Passive mode uses only the IPS engine. The appliance inspects traffic inline but doesn't block traffic. IPS detections indicate traffic that would be blocked in IPS Active mode.

Wiring: The appliance operates inline using the same bridge-pair configuration as IPS Active.

On a physical appliance:

  • Copper modules support up to four bridge pairs using eight interfaces.
  • Fiber modules support up to two bridge pairs using four interfaces.

Sophos Fusion configuration: Set the mode to IPS Passive. Select a rule set and configure the home net, external net, and HTTP ports settings.

Behavior: The IPS engine doesn't block traffic in this mode. The selected rule set determines which detections are identified as traffic that would have been blocked in IPS Active mode.

You can use IPS Passive mode to evaluate and tune the IDS/IPS configuration before switching to IPS Active. Switching between these modes doesn't require re-cabling the appliance.

Licensing: The IDS/IPS license is required.

Limitations: IPS Passive mode doesn't provide ML or anomaly detection. The appliance is in the network traffic path. If the appliance fails or restarts, the appliance switches to bypass. Changing the appliance from IPS Passive to a sniffer mode requires re-cabling the capture interfaces.

IPS Active

What it does: IPS Active mode uses only the IPS engine. It blocks traffic that matches blocking signatures in the selected rule set. The ML and anomaly engines aren't used.

Wiring: The appliance operates inline using bridge pairs.

On a physical appliance:

  • Copper modules support up to four bridge pairs using eight interfaces.
  • Fiber modules support up to two bridge pairs using four interfaces.

Sophos Fusion configuration: Set the mode to IPS Active. Select a rule set and configure the home net, external net, and HTTP ports settings.

Behavior: When traffic matches a blocking signature, the appliance blocks the traffic and generates a detection in Sophos Fusion. If the IPS engine incorrectly blocks known-good traffic, you can add an allow rule for that traffic.

Licensing: The IDS/IPS license is required.

Limitations: IPS Active mode doesn't provide ML or anomaly detection. The appliance is in the network traffic path. If the appliance fails or restarts, the appliance switches to bypass. Changing the appliance from IPS Active to a sniffer mode requires re-cabling the capture interfaces.

Change modes

Changing between sniffer modes doesn't require changes to the physical appliance cabling. Changing between passive and active versions of the same inline mode also doesn't require cabling changes.

Changing a physical appliance between sniffer and inline modes requires you to re-cable the capture interfaces because the appliance's position in the network traffic path changes.

For port wiring examples, see Port wiring.