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

Identity, directory and federation logs

1 min read

Identity infrastructure is the authoritative record of account state and authentication because it performs both operations. The directory service's security log records group membership changes, who made them, and the authentication events that name the requesting workstation.

If a question asks when an account was added to a privileged group and where it signed in from, the directory log answers both. Flow records carry no directory meaning, and a credential vault only knows about sessions that passed through the vault.

Single sign-on and federation split the evidence along the same line they split trust. The identity provider performs the authentication, so it owns the record of which factors were presented, which policy applied and whether multifactor authentication succeeded.

The application only receives an assertion, so its audit log records what the session then did inside the application. An investigation that asks both questions must collect from both sides.

Example: an account opened a federated payroll application at 23:30, and the on-premises domain controllers show no logon for it that night. In many designs that is expected, because the sign-in happened at the identity provider. Closing the alert as a false positive after searching the wrong system is a coverage mistake, not a finding.

Check yourself

1. Staff reach a hosted expense application through the corporate identity provider using single sign-on. An analyst must establish both whether the second factor was satisfied at sign-in and which expense reports the account opened afterwards. Where does that evidence live?

2. An analyst must establish when a compromised account was added to a privileged group and from which workstation that account authenticated during the same period. Which single source best answers both questions?

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 →