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

Identity and application indicators

1 min read

Identity questions reward knowing the exact shape of each attack. Brute-force guessing is many attempts against one account from one source; spraying is one password tried thinly across many accounts to avoid lockout.

In Windows logs, 4625 is a failed logon, 4624 a successful one (logon type 10 means remote interactive), and 4672 shows special privileges assigned to the new session. Example: 900 failures on one admin account followed by a 4624 type 10 and a 4672 is a confirmed, privileged compromise.

  • Session hijacking: one session cookie used from two distant networks with different User-Agent strings and no new sign-in means a stolen token is being replayed, so invalidate the session on the server.
  • Illicit consent grant: a user approves an unverified, newly registered app asking for mail access plus offline_access. No password is involved, so revoke the grant and its tokens.
  • Short-lived elevation: an account added to an admin group (4728), used, then removed (4729) within minutes while its owner is on leave hides from current-state reviews.
  • Account enumeration: a reset page that answers differently for real and unknown addresses tells an attacker which accounts exist.

Check yourself

1. A domain controller records 1,412 failed logon events (4625) for the account svc_backup from 198.51.100.22 over twenty-two minutes, then one successful logon (4624) with logon type 10 from the same address, followed by a special privileges event (4672). What does this indicate?

2. An alert reports the same account authenticating from Denver at 08:02 and from Frankfurt at 08:09. The Frankfurt address belongs to the company's own cloud VPN egress range, both events carry the same device certificate, and the account's baseline shows that egress on every working day. How should this be read?

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 →