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 3 · Lesson 1 of 5
Packet capture, flow data and network monitoring sensors
1 min read
Network evidence comes at different depths, and each depth costs a different amount to store. The exam usually gives a retention period or a storage limit and asks what can still be proven.
| Tool or data | What it keeps | Typical use |
|---|---|---|
| Full packet capture | Every byte, including payload | Reassemble a stream in a protocol analyzer to read exactly what was sent |
| Flow records | Addresses, ports, times, duration, direction, byte counts | Prove a conversation happened months later |
| Network security monitoring sensor | One metadata log per connection, with fields such as the TLS server name | Searchable history of protocol details without storing payload |
| Signature-based IDS | Only traffic that matched a rule | Alert on known patterns |
Example: capture is kept for 5 days and flow for 9 months. For an event 3 weeks ago, you can prove when the hosts talked, for how long and how many bytes moved, but not what was carried.
To confirm whether a legacy application sends passwords in clear text over Telnet, only packet capture works: filter to TCP 23 and follow the stream. A missing IDS alert is not proof that the traffic is encrypted. When storage rules out a month of payload, a monitoring sensor that writes per-connection metadata is the usual compromise.
Check yourself
1. A security operations center retains 7 days of full packet capture and 12 months of flow records. An investigation opens into traffic from 30 days ago, when an internal workstation exchanged data with an external address later identified as a command-and-control host. What can the analyst still establish from the surviving data?
2. A hunt team needs, for every connection on a monitored segment over the last month, a record of protocol, duration, bytes and the server name requested in each TLS handshake. Storing payload for a month is not affordable. Which monitoring approach meets the requirement?
Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, MITRE ATT&CK knowledge base of adversary tactics and techniques
CompTIA CySA+ cheat sheet: every key fact on one page →