evelin.

Networking for defenders: read alerts, flows and IP connections

Learn how basic networking helps you read alerts, flows and suspicious connections in context, so you can act like a real security analyst.

Why networking knowledge matters for defenders

As a junior analyst you spend your day inside tools that show IPs, ports, protocols and strange looking network paths. Without basic networking, all of that feels like random numbers. With it, you can quickly see what is normal and what is suspicious. You recognise internal addresses, internet ranges and risky services like exposed RDP. This reduces noise, guides your questions and makes your investigation notes clearer. Strong networking basics also give you confidence in interviews, because you can explain alerts in plain language. You do not need deep engineering skills. You need just enough to read the picture of how systems talk to each other.

How networking helps defenders
🧭
Gives direction
Focus on risky connections first
🧩
Adds context
Turn raw IPs into real systems
✂️
Cuts noise
Ignore harmless background traffic

Reading IP addresses and subnets in security alerts

Most alerts show at least a source IP, a destination IP and sometimes a subnet or CIDR value. You should quickly see if an address is internal, external or special use. For example, 10.x, 172.16 to 172.31 and 192.168.x are private ranges that stay inside a network. Public IPs are reachable over the internet and deserve more attention. Subnets like /24 or /16 tell you how large an internal segment is. This matters when an alert hits many hosts at once. Practice by taking random IPs from sample logs and deciding where they likely sit in a company network.

Private vs public IP focus
Private IP ranges
  • •10.0.0.0/8
  • •172.16.0.0/12
  • •192.168.0.0/16
  • •Stay inside local networks
Public IP space
  • ✓Reachable from internet
  • ✓Often external services
  • ✓Higher attack surface
  • ✓More triage priority
VS

Using ports and protocols to judge how risky traffic is

Ports and protocols tell you what kind of conversation is happening. TCP 80 and 443 usually mean web traffic. TCP 3389 means remote desktop. UDP 53 is DNS. As a defender you map these details to risk. Unexpected RDP from internet to a server is worrying. DNS to random external IPs might hint at tunneling or malware. Start by learning a shortlist of common ports and what they are used for. When an alert pops up, ask which side started the connection, what service the port suggests and whether that story fits the asset. Over time you will spot odd patterns faster.

Understanding flows so you can see the bigger picture

Network flows summarise who talked to whom, on which port, how often and for how long. They do not always show full packet content, but they show patterns. As a defender this helps you answer fast questions. Is this a single failed login or thousands from one IP. Is data leaving the network over an unusual port. Did that internal host suddenly start talking to many countries. When you view flows, group them by source, destination or port and look for repeats. Short, one off connections to known services might be fine. Long lived or spreading flows often deserve a deeper look.

Quick flow review steps
  1. 👤1
    Group by source
    Who is doing the talking
  2. 🚪2
    Check ports
    What service is implied
  3. ⏱️3
    Scan time range
    Burst or long lived
  4. 🔍4
    Note patterns
    Repetition or spread

Typical beginner mistakes when reading network alerts

New analysts often chase every single alert without checking context, which leads to fatigue. A common mistake is to ignore direction. For example, blocked inbound scans from the internet matter less than successful outbound connections from a server to a rare country. Another mistake is to focus only on the IP reputation score and skip basic checks like asset owner or usual business use. Avoid guessing. If you do not understand a protocol, quickly look it up and note what you learned. Over time you will build a mental list of common benign patterns and free your attention for true threats.

Practical ways to build networking skills for defense

You can train with only a laptop and free tools. Install Wireshark and capture traffic from your own web browsing. Practice spotting your local IP, the external server IPs and the ports used. Use basic commands like ipconfig or ifconfig and netstat to see active connections. Many labs and Capture the Flag platforms give network logs or PCAPs to analyse. Focus on explaining in words what you see, for example, internal host connects to external IP over TCP 443 for 10 minutes. This translation skill is what hiring managers look for in junior defenders.

Simple daily networking practice
  1. 💻1
    Run basic commands
    Check IP and active connections
  2. 📡2
    Capture small PCAPs
    Record short traffic samples
  3. ✏️3
    Write one sentence
    Describe what the traffic shows

Real-world examples

  • • You see an alert for multiple connections from 192.168.1.15 to a public IP on TCP port 3389. Because you know this is RDP going out to the internet, you treat it as a high priority event and check if that host should ever use remote desktop externally.
  • • Your SIEM shows thousands of denied inbound hits from many foreign IPs to TCP port 80 on a web server. Networking knowledge tells you this is likely a common internet scan, so you document it quickly and focus more on successful logins and outbound traffic.
  • • During a home lab, you capture PCAPs while streaming video. You learn to recognise long lived TCP connections on port 443 and see how they differ from short one off DNS lookups on UDP port 53.

Useful links

Keep learning

Related courses

More programs on evelin that fit this path. Each one adapts to you after a two minute quiz.

Guides from related courses

All courses on evelin →

Turn reading into real progress

A short quiz builds your personal learning path for How to Become a Remote Cybersecurity Analyst. Lessons adapt to you from day one.

Start the quiz

Created with AI assistance and reviewed before publishing.