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 →
← Prioritization, Mitigation & Controls

Chapter 7 · Lesson 4 of 5

Compensating controls, exceptions, acceptance and transfer

1 min read

A compensating control is an alternative measure used when the primary fix cannot be applied yet: a proxy or web application firewall rule that filters the exploit request, tight access lists in front of an unsupported appliance, or a segment that admits only one imaging workstation and logs everything else.

These buy time by narrowing who can reach the flaw. They do not repair it, an attacker who finds a request shape the rule misses is back at the original defect, and the one permitted workstation is itself a route in if it is compromised.

So the finding stays open, the control is documented, and the patch or replacement stays on plan.

  • Exception: when a fix conflicts with business needs or an internal standard, the decision goes to the risk owner, with justification, compensating controls, an expiry date and a review.
  • Acceptance: a documented risk-owner decision to take no action, with a review date. An analyst cannot accept risk alone in a ticket comment.
  • Transfer: a contract or insurance moves who pays, not the vulnerability, so a third-party finding stays tracked with the provider's fix commitment.
  • Compliance scope: when an obligation applies, such as one inherited through a payment card contract, the control, its approval, scope and review date must be recorded as evidence.

Check yourself

1. An unsupported medical imaging controller carries a serious finding that cannot be patched. The team moves it to a segment that permits only the imaging workstation's traffic and logs every other attempt. A manager asks whether the risk is now resolved. Which answer is accurate?

2. A web application flaw cannot be patched for six weeks, so the team writes a blocking rule on the filtering layer in front of the application and confirms the rule stops the known attack request. The vulnerability manager asks what has actually changed. Which statement is accurate?

Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, FIRST: CVSS v4.0 Specification Document, FIRST: CVSS v4.0 User Guide, CISA: Known Exploited Vulnerabilities Catalog

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