Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 2 · Lesson 1 of 5
Network indicators: DNS abuse, odd protocols and unusual volume
1 min read
Network questions usually hinge on the shape of the traffic rather than one packet. Learn the shapes below and the innocent look-alikes the distractors offer.
| Pattern | Most likely meaning |
|---|---|
| Thousands of long, high-entropy subdomains of one domain, similar-size TXT answers, no connection to the resolved address | DNS tunneling for command and control or data |
| Hundreds of never-seen names, nearly all NXDOMAIN, then one resolves and a session opens to it | Domain generation algorithm malware |
| Port 443 sessions whose first bytes are an SSH banner and no TLS ClientHello | Protocol tunneled over an allowed port |
| Tens of gigabytes leaving a host whose role never sends data out | Data exfiltration |
Two principles sit behind the table. First, a port only says where traffic is going, while the first bytes show what protocol is really in use. Second, volume is judged against the host's role and against benign explanations the evidence can rule out, such as a backup job that already finished to an internal target on a different port.
Scanning is the reverse case: enumeration from a host in the asset inventory, using its own service account inside the published maintenance window, is authorized assessment. Verify the source and timing, then close it.
Check yourself
1. Over five minutes a workstation asks the internal resolver for 600 names it has never queried before, such as qvbnlxzrt.com and mwdkphjsg.net, and 597 return NXDOMAIN. The 598th resolves, and the workstation immediately opens a TLS session to that address. What does this sequence indicate?
2. Between 02:00 and 02:40, host 10.20.5.9 sent SYN packets to 1,000 ports on each of 240 internal hosts, then authenticated to each host with the account svc_scan. The address is listed in the asset inventory as the credentialed assessment host, and the window matches the published maintenance calendar. What is the correct reading?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, AWS CloudTrail User Guide: Logging data events
CompTIA CySA+ cheat sheet: every key fact on one page →