Fundamentals

T1040, T1046

Network Security Basics

A foundational guide to network security for SOC analysts — firewall types, ACLs, security zones, egress filtering, and network segmentation. Covers the concepts analysts need to interpret firewall logs and assess network controls.

View on Graph

What Network Security Controls Are and Why Analysts Need to Understand Them

  • Network security controls are the gatekeepers between users, systems, and the internet. They enforce what traffic is allowed, what is blocked, what is logged, and what is inspected.
  • Every SOC analyst reads firewall logs, triages IDS alerts, and interprets network telemetry daily. Understanding the control that generated the log is the difference between “the firewall blocked something” and “the firewall blocked a C2 callback on a port that should not be open.”
  • This article covers the core network security concepts every analyst needs: firewalls (stateful vs stateless), ACLs (standard vs extended), security zones (trusted vs untrusted), egress filtering, and network segmentation strategies.

Firewall Types — Stateful vs Stateless vs Next-Gen

Stateless (Packet Filter) Firewalls

The simplest type. Inspects each packet in isolation — no knowledge of connection state.

CharacteristicDetail
What it checksSource IP, destination IP, source port, destination port, protocol, TCP flags
State awarenessNone — each packet is assessed independently
PerformanceVery fast — no state table to maintain
SecurityLow — cannot detect state-based attacks (e.g., SYN floods that complete the handshake abnormally)
ExamplesStandard IPtables rules, early Cisco ACLs, basic router filters
Best forSimple permit/deny rules at network edges

Stateful Firewalls

Tracks the state of active connections. If a packet is part of an established connection, it is automatically allowed without re-evaluating rules.

CharacteristicDetail
What it checksSame as stateless + connection state (NEW, ESTABLISHED, RELATED, INVALID)
State awarenessFull — maintains a state table per connection
PerformanceModerate — maintained flow table is bounded (can be DoS target)
SecurityHigh — drops packets that arrive without matching state (e.g., unsolicited SYN-ACK)
ExamplesIPtables conntrack, Windows Firewall, pfSense, Cisco ASA, Palo Alto
Best forMost internal and perimeter deployments

Next-Generation Firewalls (NGFW)

Stateful inspection plus application-layer awareness — inspects packet payloads, not just headers.

CharacteristicDetail
What it checksEverything stateful checks + application protocol, file type, SSL/TLS decryption, user identity, threat intelligence feeds
State awarenessFull + application state
PerformanceSlower — deep packet inspection is CPU-intensive
SecurityHighest — can identify and block specific applications, malware downloads, and C2 protocols even on non-standard ports
ExamplesPalo Alto, Fortinet FortiGate, Check Point, Cisco Firepower
Best forPerimeter defense, data center east-west traffic, cloud egress

ACLs — Access Control Lists

ACLs are ordered lists of permit/deny rules applied to network interfaces. Every packet is evaluated against the rule list top-to-bottom until a match is found.

Standard vs Extended ACLs

FeatureStandard ACLExtended ACL
Match source onlyYes (source IP)No
Match source + destination + portNoYes
Exampleaccess-list 10 permit 192.168.1.0 0.0.0.255access-list 100 permit tcp 10.0.0.0 0.255.255.255 any eq 443
PlacementClose to the destination (because it doesn’t filter by destination)Close to the source (early filtering)
Wildcard maskRequiredRequired

ACL Wildcard Masks vs Subnet Masks

Do not confuse wildcard masks with subnet masks. Wildcard masks are inverted subnet masks:

SubnetSubnet MaskWildcard MaskWhat It Matches
/24255.255.255.00.0.0.255192.168.1.0-255
/16255.255.0.00.0.255.255192.168.0.0-255.255
Single host255.255.255.2550.0.0.0That exact IP only
Any0.0.0.0255.255.255.255Everything (any)

The implicit deny rule: Every ACL ends with an implicit deny all — even if not explicitly configured. If traffic does not match any rule, it is dropped. This is the most common reason analysts see blocked traffic that appears to match no rule.


Security Zones — Trusted, Untrusted, and DMZ

Network segmentation starts with security zones — logical groupings of systems with similar trust levels.

ZoneTrust LevelWhat Lives ThereInbound PolicyOutbound Policy
Trusted (Internal)HighCorporate users, internal servers, Active DirectoryRestrict inbound from other zonesPermit outbound to internet (with inspection)
DMZ (Demilitarized)MediumWeb servers, mail relays, VPN gateways, application proxiesPermit specific ports from internet (80, 443, SMTP)Restrict outbound — only specific protocols to internal
Untrusted (Internet)NoneEverything outsideN/ADefault-deny inbound
ManagementHighestSSH/RDP jump hosts, monitoring servers, admin workstationsOnly from dedicated admin IPsMinimal — patching and logging only
Guest (BYOD)LowGuest WiFi, contractor laptopsNoneInternet only — no internal access

The cardinal rule of zone-based firewalls: Traffic between zones must be explicitly permitted. Nothing passes between zones by default — including traffic from Trusted to DMZ.


Egress Filtering — The Most Overlooked Security Control

Egress filtering controls outbound traffic from your network to the internet. Most organizations invest heavily in inbound filtering but leave outbound ports wide open — which is why C2 beacons on port 443 work so reliably.

Why Egress Filtering Matters

Attack PhaseWithout Egress FilteringWith Egress Filtering
C2 beaconingBeacon easily reaches the attacker’s server on any portBeacon is blocked unless it uses approved ports/protocols
Data exfiltrationLarge outbound data transfer to an unknown IPBlocked or flagged by security monitoring
DNS tunnelingDNS queries to exfiltrate data reach any DNS serverOnly approved DNS resolvers are allowed — DNS tunneling traffic is blocked
Reverse shellAttacker connects back to a listener on any portBlocked if the port/protocol is not permitted
Outbound PortProtocolServiceRationale
53TCP/UDPDNSResolve domain names — restrict to approved DNS servers only
80TCPHTTPWeb traffic — ideally proxy all HTTP through an inspection proxy
443TCPHTTPSWeb traffic — inspect with CAs and TLS interception
123UDPNTPTime synchronization
22TCPSSHOutbound SSH — restrict to known admin IPs
25TCPSMTPEmail — restrict to authorized mail servers only

Everything else should be blocked. If a business need exists, permit it with exceptions and log all matches.


Network Segmentation — Containment Through Architecture

Segmentation limits lateral movement by dividing the network into isolated segments. If an attacker compromises one segment, they cannot see or reach the others without traversing a firewall.

Common Segmentation Models

ModelDescriptionSecurity LevelComplexity
Flat networkAll hosts on the same subnet — any host can reach any otherLowMinimal
VLAN separationLayer 2 separation — hosts in different VLANs cannot communicate without a routerMediumModerate
Micro-segmentationEach workload or application has its own security policy — enforced at the hypervisor, container network interface, or cloud security groupHighSignificant
Zero Trust networkNo implicit trust based on network location — every request is authenticated, authorized, and encryptedHighestHigh

How Analysts Detect Segmentation Failures

SPL query — cross-segment traffic from user workstations to sensitive servers:

index=network sourcetype=firewall_log
| search src_ip=10.0.1.0/24 (users) AND dest_ip=10.0.100.0/24 (sensitive servers)
| stats count by src_ip, dest_ip, dest_port
| where count > 5
| eval alert = "Cross-segment traffic from user subnet to sensitive server — possible lateral movement"
| table _time, src_ip, dest_ip, dest_port, count, alert

SPL query — hosts sending traffic to unusual ports:

index=network sourcetype=firewall_log action=allowed
| search NOT dest_port IN (53, 80, 443, 123, 22, 3389)
| stats count by src_ip, dest_ip, dest_port
| where count > 20
| eval alert = "Outbound traffic on non-standard port"
| table _time, src_ip, dest_ip, dest_port, count, alert

Log Sources for Network Security Investigations

Log SourceWhat It RevealsKey Fields for Analysis
Firewall logsWhich traffic was allowed, denied, or droppedsrc_ip, dest_ip, src_port, dest_port, action, rule_name
VPC Flow LogsTraffic metadata in cloud environmentssrcaddr, dstaddr, dstport, protocol, action, bytes, packets
DNS query logsWhich domains are being resolved and by which hostquery_name, src_ip, response_ip, query_type
Proxy logsHTTP/HTTPS traffic details — including full URL pathsurl, method, status_code, user_agent, bytes, content_type
NetFlow/IPFIXSummary of network conversationssrc_ip:port, dest_ip:port, protocol, bytes, packets, duration

Sources