Why networking comes before security tools
Security tools show you network traffic, open ports and connection logs. Without networking basics, that output is just numbers. With them, a scan result or an alert immediately tells a story: which machine talked to which, on what service, and whether that makes sense.
You do not need to become a network engineer. A clear understanding of a handful of concepts, plus the habit of checking them on a real machine, is enough to start.
The core concepts to learn first
Learn what each one is and why an attacker or defender would care about it.
IP addresses and subnets
Every device on a network has an address. Know private versus public ranges and how a subnet such as 192.168.1.0/24 groups machines together.
Ports and services
A port is a numbered door to a service on a machine: 22 for SSH, 53 for DNS, 80 and 443 for web traffic, 3389 for Remote Desktop. Unexpected open ports are a common finding.
TCP and UDP
TCP sets up a connection with a three-way handshake and confirms delivery; UDP just sends. Knowing the difference explains how scans, streaming and DNS behave.
DNS
DNS turns names into IP addresses. Attackers abuse it for phishing domains and hidden communication, so defenders watch it closely.
HTTP and HTTPS
The language of the web. Learn requests, responses, status codes and headers, and what TLS encryption in HTTPS does and does not protect.
Firewalls and NAT
Firewalls allow or block traffic by rules; NAT lets many private machines share one public address. Both decide what can reach what.
The OSI and TCP/IP models, in one line each
Interviewers often ask about the layers. Know what lives where:
- Physical and data link – cables, Wi-Fi and MAC addresses on the local network.
- Network – IP addresses and routing between networks.
- Transport – TCP and UDP, ports and connections.
- Application – DNS, HTTP, SSH, email and the other services people actually use.
How to practise networking safely
Use your own machines and lab networks only, never systems you do not have permission to test.
Inspect your own machine
Find your IP address, gateway and DNS server with ipconfig on Windows or ip a on Linux.
Watch real traffic
Open Wireshark on your own computer, visit a website and find the DNS query, the TCP handshake and the TLS connection.
List open ports
Run ss -tulpn on Linux or netstat -ano on Windows to see which services are listening on your machine.
Build a small lab
Create two virtual machines on a private virtual network and practise connecting, blocking with a firewall rule and checking the result.
Explain it back
Write a short note on what happens when you type a website address into a browser, from DNS to the page loading. It is a classic interview question.
Quick answers about networking for cyber security
Short answers to the questions beginners search for most.
Is networking necessary for cyber security?
Yes. Networking is the foundation for understanding attacks, alerts, scans and firewall rules. Most cyber security roles expect comfortable knowledge of IP addressing, ports, protocols and DNS.
Should I do CCNA before cyber security?
It is not required. CCNA-level knowledge helps, but most beginners can learn the networking needed for security alongside their security studies and practise it in labs.
Which ports should a cyber security beginner remember?
Start with 20 and 21 (FTP), 22 (SSH), 25 (SMTP), 53 (DNS), 80 (HTTP), 443 (HTTPS), 445 (SMB) and 3389 (RDP). These appear constantly in scans and alerts.
What is the difference between TCP and UDP?
TCP creates a connection and guarantees ordered delivery, which suits web pages and file transfers. UDP sends without a connection or guarantee, which suits DNS lookups, voice and video.
What tool should I use to learn networking?
Wireshark is the best single tool for learning, because it shows every packet your own machine sends and receives, layer by layer.
Go further with networking and security basics
See where networking sits in the syllabus, or read the guides that build on it.
Capture your own traffic today
Open Wireshark, load one website and find the DNS lookup, the TCP handshake and the HTTPS connection. Seeing the packets you created yourself turns networking theory into something you can explain in an interview.

