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 →
← Indicators of Malicious Activity

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.

PatternMost likely meaning
Thousands of long, high-entropy subdomains of one domain, similar-size TXT answers, no connection to the resolved addressDNS tunneling for command and control or data
Hundreds of never-seen names, nearly all NXDOMAIN, then one resolves and a session opens to itDomain generation algorithm malware
Port 443 sessions whose first bytes are an SSH banner and no TLS ClientHelloProtocol tunneled over an allowed port
Tens of gigabytes leaving a host whose role never sends data outData 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 →