Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/54 ▾
  1. 1.Architecture & Log Sources0/5
    1. What each log source can and cannot prove
    2. Time synchronization and log normalization
    3. Sensor placement, logging levels and retention
    4. Cloud, containers, serverless and virtual machines
    5. Identity, directory and federation logs
  2. 2.Indicators of Malicious Activity0/5
    1. Network indicators: DNS abuse, odd protocols and unusual volume
    2. Host indicators: process lineage, masquerading and built-in tools
    3. Persistence and anti-forensics on hosts
    4. Identity and application indicators
    5. Cloud indicators: stolen keys and disabled audit trails
  3. 3.Investigation Tools & Threat Hunting0/5
    1. Packet capture, flow data and network monitoring sensors
    2. Endpoint telemetry, file reputation and sandboxes
    3. SIEM correlation rules and email header analysis
    4. Judging and sharing threat intelligence
    5. Running a threat hunt from hypothesis to detection
  4. 4.Process Improvement, Automation & AI0/5
    1. Choosing what to automate in the SOC
    2. Standard processes: playbooks, runbooks and the case record
    3. Integrations, alert tuning and measuring improvement
    4. AI in security operations: good uses and main risks
    5. AI governance: accountability, audit trails and validation
  5. 5.Vulnerability Scanning Methods0/5
    1. Asset inventory, discovery scans and scan scope
    2. Credentialed, non-credentialed and agent-based scanning
    3. Scanner placement: internal, external and what sits in between
    4. Passive scanning, fragile devices and scan scheduling
    5. Web applications, containers, infrastructure-as-code and baselines
  6. 6.Analyzing Scan Output0/5
    1. Validating findings and spotting false positives
    2. False negatives, failed credentials and stale plugin feeds
    3. Present, reachable, mitigated or already compromised
    4. Reading the kind of finding: patch, configuration, end of life or shared source
    5. Consolidating and deduplicating findings
  7. 7.Prioritization, Mitigation & Controls0/5
    1. Severity scores versus risk, and how CVSS v4.0 is organized
    2. Risk-based prioritization: exploitation, exposure and business context
    3. Remediation paths, change control and verifying the fix
    4. Compensating controls, exceptions, acceptance and transfer
    5. Classifying controls by type and by function
  8. 8.Attack Frameworks & the Response Process0/5
    1. Three attack frameworks, three different questions
    2. Using MITRE ATT&CK: tactics, techniques and procedures
    3. The Cyber Kill Chain: stages and where to break them
    4. The incident response lifecycle, old and new framing
    5. Containment, eradication, recovery and post-incident activity
  9. 9.Incident Response Techniques0/5
    1. Triage and scoping an incident
    2. Collecting evidence: order of volatility and safe access
    3. Integrity, chain of custody and legal hold
    4. Containment techniques that keep the evidence
    5. Eradication, recovery and root cause
  10. 10.Vulnerability Reporting & Communication0/5
    1. From raw scan export to an actionable finding
    2. Matching the report to the audience
    3. Metrics that show direction: trends, aging, recurrence and coverage
    4. Risk acceptance, exceptions, action plans and escalation
    5. Credibility: honest severity, controlled disclosure and AI-drafted reports
  11. 11.Incident Reporting & Metrics0/4
    1. Writing a defensible incident record
    2. Communicating while the incident is live
    3. After-action reports, root cause and lessons learned
    4. Response metrics and how they mislead
Saved in this browser. Move it to another device →
← Investigation Tools & Threat Hunting

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 dataWhat it keepsTypical use
Full packet captureEvery byte, including payloadReassemble a stream in a protocol analyzer to read exactly what was sent
Flow recordsAddresses, ports, times, duration, direction, byte countsProve a conversation happened months later
Network security monitoring sensorOne metadata log per connection, with fields such as the TLS server nameSearchable history of protocol details without storing payload
Signature-based IDSOnly traffic that matched a ruleAlert 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 →