Network monitoring: what it sees that the endpoint cannot

NetFlow, NDR, and traffic analysis. Why you need network visibility alongside endpoint protection, and where to start if you have no dedicated tool for it.

Topic
IT security
Author
ARLITECH expert team
Published
Updated

Endpoint protection sees what happens on a machine. Network monitoring sees what happens between machines. Neither replaces the other, and a significant part of an attack shows up on only one of them.

What the network sees that the endpoint does not

Unmanaged devices. A printer, an IP camera, a building automation controller, a laptop a supplier brings on site. None of them runs an agent, so as far as endpoint protection is concerned, they do not exist.

The command-and-control channel. An outbound connection to an unknown destination often shows up in the traffic even when everything on the machine is quiet.

Data exfiltration. Unusually large outbound data volumes are easy to measure at the network level.

Lateral movement. Unusual connections between machines: a workstation that suddenly starts connecting to the administrative ports of other workstations.

The OT environment. You cannot install an agent on industrial devices, so there the network is the only source of visibility. We covered this in our article on ICS/SCADA.

Where to start if you have no dedicated tool

You do not need to buy an NDR product right away. Your existing infrastructure can already give you a lot.

1. NetFlow from network devices. Most managed switches and routers can export flow data: who talked to whom, when, and how much. It does not carry the content, only the connection pattern, and for most detections that is enough.

2. Firewall logs. You already have a log of allowed and blocked traffic; it is just usually not analyzed. The pattern of blocked outbound traffic is often the first sign.

3. DNS logging. An underrated source, even though a command-and-control channel almost always starts with name resolution, and unusual domain names show up here first.

4. Proxy logs. Outbound web traffic, with data volumes. Discovering shadow IT also starts here.

These four sources usually exist already; they are just not being collected. In our article on logging we covered in detail what is worth sending from them to a SIEM.

Network monitoring needs a baseline first. Until you know what normal operation looks like, you cannot tell what counts as an anomaly. That is why it pays to start by mapping the communication matrix, which is also the basis for segmentation.

What to watch for

  • A new connection between two devices that have not communicated before
  • Unusual timing: sudden night-time activity on systems that follow a daily rhythm
  • Many failed connection attempts in a short time: a sign of reconnaissance
  • An unknown device appearing on the network
  • Encrypted traffic on unusual ports or to unusual destinations

Where projects get stuck

Encrypted traffic. Most traffic today is TLS, so the content is not visible. The metadata (who talks to whom, how much, at what rhythm) is. TLS traffic can be decrypted, but that has privacy and performance consequences.

Choosing where to monitor. Most network traffic never crosses the perimeter: east-west traffic between machines stays inside. If you only watch the perimeter, you will not see lateral movement.

Data volume. Capturing all traffic is expensive and rarely worth it. Flow data combined with selective capture (only for suspicious connections) strikes a better balance.

In OT environments

Here network monitoring is the primary tool. Industrial traffic is highly predictable: the same devices talk to the same peers at the same rhythm. That is why anomaly detection works much better here than in IT environments.

The method is passive: traffic is mirrored from a SPAN port or a network TAP, without sending a single packet.

Both our IT security services and our OT services cover building network visibility.

Contact

Ready to secure your critical systems?

Our experts will assess where your security stands and build a roadmap that fits your organization.

ARLITECH's office in Gödöllő

Visit us

You are welcome to visit our Gödöllő office in person.

Address
Centrum Office Building, 2100 Gödöllő, Dózsa György út 13, 3rd floor, office 309
Office hours
Mon–Fri, 9 a.m. to 5 p.m.
Get directions (opens in a new tab)