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 3 of 5

SIEM correlation rules and email header analysis

1 min read

A SIEM correlation rule expresses relationships between events: things that happen together, in a certain order, or above a threshold inside a time window. What it cannot express on its own is whether the relationship is legitimate.

Example: a rule fires whenever an account signs in from two countries within 60 minutes, and it produces hundreds of alerts a day because staff traffic leaves through a cloud gateway abroad and phones use foreign carrier addresses.

The fix is context, such as excluding the organization's known egress ranges. Widening the window would make the rule match more pairs, not fewer.

Email headers test the same idea of trust. Each receiving mail server adds its own Received line at the top, so the newest hop is listed first.

Only the lines your own servers wrote, from the top down to your inbound gateway's hop, can be trusted. Every line below that hop, plus the From display name, the Reply-To address and any X- header, is text the sender chose and can forge.

To find the infrastructure that really delivered a phishing message and search for other recipients, pivot on the address recorded by your own inbound gateway. On the exam, an answer that trusts X-Originating-IP or Reply-To because it looks technical is the usual wrong choice.

Check yourself

1. An analyst writes a SIEM correlation rule: alert when one account authenticates successfully from two different countries within one hour. It now fires several hundred times a day, almost all on staff whose sessions egress through a cloud access gateway in another country and whose phones use foreign carrier addresses. What does this illustrate about correlation rules?

2. A credential-phishing message reached three mailboxes, and the analyst wants to identify the infrastructure that actually delivered it in order to search for other recipients. The message carries a From display name matching an executive, a Reply-To at a free mail provider, an X-Originating-IP header, and a Received chain of five hops. Which element is the most reliable pivot?

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 →