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 6 · Lesson 4 of 5
Reading the kind of finding: patch, configuration, end of life or shared source
1 min read
Scan output mixes several kinds of condition, and each one leads to a different fix. Naming the kind correctly is often the whole question.
| Kind of finding | Clue in the output | Where remediation belongs |
|---|---|---|
| Missing patch | Installed version is older than a fixed release | Apply the update, then rescan |
| Misconfiguration | Software is current but offers deprecated TLS versions or weak ciphers | Hardening change in the server's own configuration, then a verification rescan |
| End of life | Vendor support ended and no patch is listed | Upgrade or replace the platform, isolating it in the meantime |
| Shared source | Host built from a template, a container image or an infrastructure-as-code definition | Fix the source, rebuild, then scan everything built from it |
Shared sources produce the trickiest questions. A hardening gap on one server built from a single VM template is really a template defect, latent on every host built from it and on every future build. Patching a library inside a running container fails because the container is recreated from its image at the next deployment.
A template that opens a management port to 0.0.0.0/0 is a real finding even when someone tightened the live resource by hand, because the next build will reopen it. End-of-life findings are permanent until the platform changes, so never give them a deferred patch date that can never be met.
Check yourself
1. A scan flags a hardening setting missing on one newly built virtual server. The build team confirms that every server in that environment is deployed from a single virtual machine template. What does the single finding actually indicate?
2. A scan flags 'server supports deprecated TLS protocol versions and weak cipher suites' on an application host. The web server package itself is fully patched. What does this finding say, and where does remediation belong?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-115: Technical Guide to Information Security Testing and Assessment
CompTIA CySA+ cheat sheet: every key fact on one page →