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 →
← Architecture & Log Sources

Chapter 1 · Lesson 2 of 5

Time synchronization and log normalization

1 min read

A timeline built from several sources is only as good as the clocks behind it. If one server's time drifts after NTP fails, its events can appear to happen before the request that caused them, which reverses cause and effect.

The correct response is never to throw that source away. Measure the offset, apply it as a correction, rebuild the timeline against one reference clock, and fix the synchronization so the drift stops.

  • Ingest time is not event time: forwarding and queuing delays differ by source, so arrival order at the SIEM can be wrong.
  • Converting skewed values into another time zone moves them all equally and leaves the skew in place.
  • A local timestamp with no recorded offset is ambiguous, and when clocks fall back for daylight saving one local hour happens twice.

The fix for mixed time zones is to normalize every entry to UTC at ingestion while keeping the original string. Normalization has a cost the exam likes to test: a parser keeps only the fields it maps.

If it drops the client source port, you can no longer separate the many hosts that share one address behind a NAT gateway. The raw record, usually still held by the collector, is where you recover it.

Check yourself

1. Two plants write their application logs in local wall-clock time with no offset recorded in the entry. One plant observes daylight saving time; the other does not. An analyst must order events from both plants across the night the clocks changed. What is the correct assessment?

2. An analyst correlates a firewall log, a web server log and a domain controller log for the same intrusion. NTP failed on the domain controller three weeks ago and its clock now runs seven minutes ahead of the other two sources. What should the analyst do about the timeline?

Facts checked 2026-11-15 · Sources: CompTIA CySA+ (CS0-004) certification page and exam objectives, NIST SP 800-92, Guide to Computer Security Log Management

CompTIA CySA+ cheat sheet: every key fact on one page →