Guide
What is network detection and response?
Network detection and response (NDR) analyzes network traffic to find suspicious activity and give investigators evidence they can follow: which systems communicated, how activity moved inside the network, and what happened before, and after a detection.
If you only read one thing.
NDR is only as useful as the visibility behind it. Check these first.
Coverage
Which segments and sites can the platform actually see?
Direction
Internal east-west traffic, internet-facing north-south traffic, or both?
Retention
Full packets, flows, protocol logs, detections, or only summaries?
Trail
Can an analyst move from a detection back to the sessions behind it?
01 · How NDR works
How NDR works.
NDR needs visibility into the traffic you care about. That can include north-south traffic entering or leaving the environment and east-west traffic moving between internal systems.
Collect the traffic
Network evidence can come from taps, SPAN ports, packet brokers, flow records, cloud network telemetry, or imported captures.
Turn it into usable evidence
Connections become records: source and destination, ports, protocols, timing, DNS activity, session details, data volume, and payload content when available.
Look for suspicious patterns
Rules, threat intelligence, behavioral analysis, baselines, and correlation can surface activity that deserves investigation.
Give the analyst a trail
The useful output is the evidence around the activity: systems involved, sessions, sequence, timing, and enough context to investigate what happened next.
The exact collection method and response capability vary by product. NDR cannot analyze traffic it never receives.
02 · What NDR looks at
What NDR actually looks at.
There is no single NDR data format. The depth of an investigation depends on what the platform can collect and retain. 1 2
- Packets and PCAP
- Full packet data can preserve protocol headers and, when visible, payload content for deeper forensic review.
- Flow and session records
- NetFlow, sFlow, and similar records show who communicated, over which ports and protocols, when, and how much data moved.
- Protocol metadata
- Zeek and similar telemetry turn DNS, HTTP, TLS, SMB, SSH, and other network activity into searchable records.
- Network security events
- Firewall, IDS/IPS, proxy, and other network controls add detections and context around the traffic being investigated.
- Cloud network telemetry
- Virtual network flow logs and mirrored traffic extend visibility into cloud workloads where physical taps do not exist.
03 · What it can surface
What network evidence can surface.
NDR is strongest when suspicious behavior leaves a pattern in network communications. These are common examples an analyst may be able to see or investigate.
- Lateral movement
- A host begins reaching internal systems or services it does not normally use, including new SMB, RDP, SSH, or administrative paths.
- Command and control
- Repeated outbound connections, unusual destinations, beacon-like timing, or other communication patterns can point to C2 activity.
- Reconnaissance and scanning
- Bursts of connections across many hosts, ports, or services can reveal internal discovery and network-service scanning.
- DNS and protocol abuse
- Long or unusual DNS queries, unexpected protocols, uncommon ports, or protocol behavior that breaks the normal pattern can warrant investigation.
- Possible data exfiltration
- Large or unusual outbound transfers, new destinations, and unexpected transfer methods can provide evidence of data leaving the environment.
- Unexpected access paths
- New third-party connections, remote access from unusual networks, or communication across a boundary that should be quiet can expose a path worth checking.
Network evidence shows the communication. Host, identity, cloud, or application evidence may still be needed to explain which process or account caused it.
04 · What makes it useful
NDR is only as useful as the visibility behind it.
Before judging any NDR platform, check the collection and investigation path first.
- Which network segments and sites can the platform actually see?
- Can it see internal east-west traffic, internet-facing north-south traffic, or both?
- What is retained: full packets, flows, protocol logs, detections, or only summaries?
- How much useful context remains when traffic is encrypted?
- Can an analyst move from a detection back to the sessions and evidence that support it?
- Who owns the investigation, and which response actions require human approval?
Collection also has to respect performance, reliability, and safety constraints. Passive network visibility is useful where active probing is inappropriate.
See what your network evidence can tell you.
Talk with our team about how AtlasCyber carries suspicious network activity into an investigated case.
05 · Where CrunchAtlas fits
Where CrunchAtlas fits.
CrunchAtlas ingests passive network evidence from CrunchSense, existing security tools, PCAP, NetFlow, and Zeek. Suspicious activity is investigated with the supporting evidence attached. Network monitoring stays passive, and consequential production changes remain under operator control.
The same case can continue into forensics, campaign correlation, and incident reporting without starting the investigation over.
06 · FAQ
NDR questions, answered.
What does NDR stand for?
Network detection and response: security technology that analyzes network traffic or network telemetry to detect suspicious activity and support investigation and response.
How is NDR different from IDS or IPS?
IDS and IPS focus on detecting suspicious network activity, and IPS can also block traffic inline. NDR usually adds broader traffic analytics, historical context, investigation workflows, and response capabilities. The exact boundary varies by product.
How do NDR and EDR work together?
They answer different parts of the same investigation. NDR sees network communications. EDR sees activity on the endpoint, such as processes, files, registry changes, and host behavior.
Can NDR still help when traffic is encrypted?
Yes, within limits. Even without payload visibility, metadata such as endpoints, ports, DNS activity, TLS characteristics, timing, session duration, and data volume can support detection and investigation. What is visible depends on the collection method and product.
Can NDR monitor OT networks?
Yes, when the deployment can safely observe the relevant OT segments and protocols. Passive collection monitors communication without actively probing operational devices. Coverage depends on placement, telemetry, protocol support, and operating constraints.
07 · Sources
Sources.
The network traffic, detection, and OT concepts on this page are grounded in MITRE ATT&CK, CISA, and NIST guidance. CrunchAtlas product descriptions are separate from agency guidance.
- MITRE ATT&CK, Network Traffic Content (DC0085)
- MITRE ATT&CK, Network Traffic Flow (DC0078)
- CISA, RITA: Network Traffic Analysis
- NIST, SP 800-82 Rev. 3, Guide to Operational Technology (OT) Security
This page is educational. NDR coverage and conclusions depend on network architecture, collection points, telemetry, retention, encryption, integrations, and approved scope.
Keep reading.
See what's moving inside your network.
Talk with our team about what AtlasCyber watches across IT and OT, and how it turns movement into cases.
Talk to our teamSign up for our newsletter
CrunchAtlas