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 5 · Lesson 5 of 5
Web applications, containers, infrastructure-as-code and baselines
1 min read
Each of these targets needs a scan designed for it, placed where the evidence lives. A host or network policy aimed at the wrong layer returns a clean result that proves nothing.
| Target | What the scan needs | What it misses otherwise |
|---|---|---|
| Web application | A maintained session: credentials, a recorded login sequence and the logout link excluded | Everything behind the login, such as accounts, payments and administration |
| Container | Image scanning in the build pipeline and the registry | Libraries inside image layers, which a host scan of the node never reads |
| Infrastructure-as-code | Template scanning before apply plus assessment of the deployed cloud state | Drift, such as a setting changed by hand in the provider console |
| Hardening baseline | A credentialed configuration audit policy run against the adopted benchmark | Per-setting compliance evidence that a vulnerability policy never produces |
Watch for the tell in the question. An eight-minute scan of a large customer portal that only reports public pages means the crawler never held a session.
A clean host scan of a container node says nothing about the images running on it, and a library inside a running container is still reachable through the service it exposes. A pipeline that blocks insecure templates cannot see a database someone opened later in the console.
Check yourself
1. A web application scan of a customer portal finishes in eight minutes and reports findings only on the marketing pages, the login page and the password-reset form. Account management, payments and administration all sit behind the login. What does the scan configuration need?
2. A pipeline scans infrastructure-as-code templates before apply and blocks any definition that grants public access. Three months later an audit finds a production database reachable from the internet, and no template declares that setting. What does this reveal about the scan's scope?
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 →