East-west traffic coverage
NDR sees what crossed the wire between servers and segments. EDR sees endpoints; SIEM sees logs; NDR sees the network. Programs running EDR plus SIEM without NDR have a visibility gap.
OpenText • Security operations
Network Detection and Response covers east-west traffic, behavioral detection and packet capture, showing SOCs the network layer that EDR and SIEM cannot see, and its signal feeds investigations in Threat Detection and Response.
A Merito NDR engagement maps sensor placement across cloud and on-prem, tunes behavioral baselines against the customer's actual traffic patterns, and integrates the signal into TDR so east-west visibility joins the existing SOC operating model rather than running as a standalone telemetry feed.
What it is
Network Detection and Response is OpenText's network-layer product for the SOC. It analyzes east-west traffic (server-to-server inside the network), runs behavioral detection on traffic patterns, and captures packets for forensic-grade investigation. Where EDR sees what happens on the endpoint and SIEM sees what was logged, NDR sees what crossed the wire. Programs running EDR plus SIEM without NDR have a visibility gap that lateral-movement attacks exploit.
Behavioral detection is the load-bearing capability. Signature-only NDR is detection theater on modern threats; lateral movement, beaconing, and data exfiltration patterns rarely match a static signature. Behavioral detection looks at traffic shape (volume, periodicity, destination patterns, protocol anomalies, encrypted-traffic-pattern analysis) and flags deviations from baseline. Programs running NDR without behavioral detection miss the patterns NDR exists to catch.
Packet capture for forensics is the depth advantage. When the SOC investigates an incident, the question is usually what was actually transferred. Behavioral detection and flow data show patterns; packet capture shows content. Programs subject to regulated breach investigations or operating in environments where adversary attribution matters need packet-level forensic data, and NDR without packet capture is a partial answer.
Sensor placement decides whether NDR catches anything. The product needs network telemetry from the right places (north-south at the perimeter, east-west between segments, internal-to-internal across critical infrastructure) and programs that deploy sensors only at the perimeter miss the lateral-movement attacks NDR is supposed to catch. Merito's engagement maps the network for sensor placement before deploying anything, and validates the coverage against the lateral-movement scenarios the SOC is responsible for catching.
Ideal use cases
What it is best at
NDR sees what crossed the wire between servers and segments. EDR sees endpoints; SIEM sees logs; NDR sees the network. Programs running EDR plus SIEM without NDR have a visibility gap.
Traffic-shape analysis, protocol anomaly detection, and encrypted-traffic-pattern analysis. Signature-only NDR misses modern lateral movement.
Beyond flow data and behavior into packet content. Programs subject to regulated breach investigations need this depth.
TDR, Behavioral Signals and Threat Intelligence consume NDR signal natively, so network evidence sits next to log, UEBA and IOC context in one investigation.
Cloud, on-prem, and hybrid sensor architectures. Programs running mixed environments get one product across the network.
Core capabilities
What NDR actually does on the network layer.
Behavioral traffic analysis
Traffic-shape, periodicity, destination-pattern, and protocol-anomaly analysis. Catches lateral movement and beaconing patterns signatures miss.
Encrypted-traffic-pattern analysis
Behavioral detection on encrypted flows without decryption, surfacing C2 patterns inside TLS.
Protocol coverage
Standard protocols (HTTP, HTTPS, DNS, SSH, RDP, SMB) plus industrial and OT protocols where applicable.
Threat-intel enrichment
Native enrichment with OpenText Threat Intelligence for IOC matching on traffic.
Network depth for SOC investigation and IR.
Packet capture
Selective and continuous packet capture for forensic-grade investigation.
Flow records and metadata
Long-retention flow data and metadata for post-incident hunt and timeline reconstruction.
Investigation workflow
NDR detections open as cases in Threat Detection and Response, so one investigation holds network and log evidence.
Where NDR sees the traffic.
Cloud sensors
AWS VPC traffic mirroring, Azure vTAP, GCP Packet Mirroring. Cloud-native east-west visibility.
On-prem sensors
Span-port and TAP-based deployment in on-prem networks with high-throughput coverage.
Hybrid orchestration
Unified policy and visibility across cloud and on-prem sensors.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
OpenText NDR cloud sensors
Cloud-deployed sensors for AWS, Azure, and GCP east-west visibility.
Best for: Cloud-native programs with limited on-prem footprint.
OpenText NDR hybrid
Cloud plus on-prem sensors with unified management.
Best for: Programs running mixed cloud and on-prem environments.
OpenText NDR with packet capture
Includes continuous packet capture for forensic-grade investigation.
Best for: Programs with regulated breach-investigation requirements.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Sensor-placement design, deployment, behavioral-baseline tuning, TDR integration.
Explore serviceSOC program scoping for OpenText NDR alongside ExtraHop, Vectra, and Darktrace.
Explore serviceNamed engineer, priority SLAs, and release-time coverage for OpenText NDR.
Explore serviceLong-term run support including sensor-architecture maintenance, behavioral-baseline evolution, and integration upkeep.
Explore serviceSensor-placement workshops and behavioral-baseline tuning for SOC analysts, network security architects and IR teams.
Explore serviceNetwork security engineers who place sensors and tune baselines, working inside your SOC and IR teams.
Explore serviceOpenText NDR licensing
OpenText NDR pricing arrives with sensor-placement design, deployment, behavioral-baseline tuning, and TDR integration that turn NDR into east-west visibility the SOC actually uses rather than a perimeter-only feed.
Merito point of view
SOCs with rigorous EDR (CrowdStrike, SentinelOne) and SIEM (Splunk, Sentinel) can still miss every lateral-movement attack when nothing watches east-west traffic. EDR shows what happened on the endpoint, SIEM shows what was logged, and NDR shows what crossed the wire. Running EDR plus SIEM without NDR leaves a visibility gap that modern attackers exploit.
OpenText NDR suits programs already running OpenText Cybersecurity or moving onto Threat Detection and Response, where network-layer visibility is the gap and packet capture for forensic investigation matters. ExtraHop, Vectra and Darktrace offer specialist NDR breadth, and scoping includes them when breadth is the priority.
Sensor placement is the operational point of failure. Programs that deploy sensors only at the perimeter (north-south) and skip east-west see only what crosses the boundary, which is the easy half. Lateral-movement attacks live east-west and need east-west visibility. Sensor placement is therefore designed before any sensor is deployed, not left to defaults.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share your network architecture, current EDR and SIEM footprint, and east-west visibility goals. A Merito OpenText specialist follows up within one business day.
East-west visibility
Behavioral detection and packet capture across cloud and on-prem. Programs running EDR plus SIEM alone have a visibility gap.
Native SecOps integration
Network signal shared natively with TDR, UEBA scoring, threat intelligence and long-retention logging.
Next step
A Merito OpenText NDR engagement starts with sensor-placement design and behavioral-baseline tuning. Perimeter-only NDR misses the lateral-movement attacks NDR is supposed to catch.