Chapters0/54 ▾
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 7 · Lesson 3 of 5
Remediation paths, change control and verifying the fix
1 min read
Remediation means the vulnerable code is fixed or gone. Applying the vendor patch is the familiar route, but removing vulnerable functionality is equally legitimate.
If an optional file-preview feature has a flaw, no business process uses it, and turning it off is a supported configuration change, switch it off now and patch when the vendor release lands. An enabled feature that nobody uses is still exploitable, so a permanent risk acceptance on the grounds that it is unused is the wrong answer.
Remediation carries its own risk, so it runs inside change control. An internal finding with no reported exploitation, whose kernel update needs a rolling restart and has a known storage-driver regression, belongs in the next approved window with a rollback plan, not in an emergency change at midnight.
Urgency is set by the threat context, not by the mere fact that a finding is open.
Closure is proven by the tool that found the problem. A management platform can report that a hardening change was pushed to every server while a service restart, a policy conflict or a rollback left it ineffective on some.
When the authenticated rescan still lists hosts as affected, reopen the finding and drive those hosts to a clean rescan; the deployment report is not verification.
Check yourself
1. A configuration hardening change was pushed to 300 servers by the endpoint management platform, which reported 300 successes, and the ticket closed automatically. The next authenticated scan still lists 46 of those servers as affected. What should the analyst conclude and do?
2. A finding concerns an optional file-preview feature in an internal document service. No business process uses the feature, the vendor's fix is two releases away, and switching the feature off is a supported configuration change. What is the appropriate action?
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 →