CND (312-38) Network Defense Simulation

In this simulation, you will analyze firewall logs and TCP/UDP port behaviors. Understanding the standardized categories of network ports is a foundational skill for traffic analysis, firewall rule creation, and identifying rogue services.

Network Scenario

A network security analyst is reviewing outbound firewall logs during a routine threat hunt. A newly provisioned application server in the DMZ is initiating outbound connections to external IP addresses. The analyst must verify if the destination ports align with approved enterprise applications, and if the network behavior matches normal client-server communication standards.

Traffic & Logs

[FW-CORE-01] SRC: 10.50.2.15:52341 DST: 198.51.100.44:3389 ACT: PERMIT (RDP) [FW-CORE-01] SRC: 10.50.2.15:52342 DST: 203.0.113.88:8080 ACT: PERMIT (HTTP-ALT) [FW-CORE-01] SRC: 10.50.2.15:52343 DST: 192.0.2.15:1433 ACT: PERMIT (MSSQL) [IDS-NIDS-01] ALERT: Suspicious outbound connection pattern. Destination ports 3389, 8080, and 1433 are non-standard for this server profile.

* Note: The server's operating system dynamically assigned the source ports (52341-52343), but the destination ports belong to a specific IANA-defined category used by commercial and vendor applications.

Question

What is the range for registered ports?
Defensive Hint: Ports 0-1023 are "Well-Known" (like HTTP 80, HTTPS 443). Ports 49152-65535 are "Ephemeral/Dynamic" used for client source ports. Which range is left for vendor applications like RDP (3389) or SQL (1433)?

Expert Analysis

1. What is happening in the network

The DMZ server is initiating connections where the source ports are ephemeral (52341+), and the destination ports fall into the registered category (3389, 8080, 1433). This indicates the server is acting as a client to these external services, which is highly unusual and potentially dangerous for a DMZ asset.

2. Identify attack or behavior

Attackers frequently use registered ports (like 8080 or 8443) for Command and Control (C2) infrastructure to blend in with legitimate alternative web traffic. Additionally, outbound RDP (3389) and MSSQL (1433) could indicate data exfiltration or lateral movement to external actor-controlled infrastructure.

3. Why correct answer is correct

A. 1024 through 49151: The Internet Assigned Numbers Authority (IANA) defines this range as Registered Ports. They are used by specific applications and vendors (e.g., Microsoft RDP on 3389, MySQL on 3306) and typically run under normal user privileges, unlike well-known ports.

4. Why others are wrong

5. Defensive action

Implement a Default-Deny egress filtering policy on the firewall. The DMZ server should not be allowed to initiate outbound connections on registered application ports (like RDP or SQL) to the internet. If external access is required, restrict it strictly by Destination IP and utilize an Application-Layer (Layer 7) firewall to ensure the traffic inside the port actually matches the expected protocol.

MINI LESSON: Port Analysis in Traffic

  • Traffic Pattern Recognition: Normal client-server traffic has a source port in the Ephemeral range (49152-65535) and a destination port in the Well-Known (0-1023) or Registered (1024-49151) range.
  • Protocol Behavior: Because registered ports do not require root/admin rights to bind, malware frequently uses them to set up listening services on compromised endpoints.
  • Detection vs Prevention: Filtering by port number alone is easily bypassed. Modern network defense relies on Deep Packet Inspection (DPI) to identify the true application layer protocol, regardless of the port used.

Ready for the real exam?

Sharpen your Blue Team skills with more realistic network scenarios.

Explore more CND simulations