4.4. System Vulnerability Assessment
💡 First Principle: Every system is a composition of components, and each component introduces its own failure modes — effective vulnerability assessment requires understanding the specific attack surface of each system type rather than applying generic checklists.
Why this matters: A database vulnerability scan that finds zero issues provides false assurance if the scanner only checks for network-level exposures while the real risk is inference attacks through legitimate queries. Organizations that treat vulnerability assessment as a uniform process miss category-specific threats and waste resources scanning for risks that do not apply while ignoring risks that do.
⚠️ Common Misconception: Vulnerability assessment is not the same as penetration testing. Assessment identifies and classifies vulnerabilities; penetration testing exploits them to demonstrate impact. The exam distinguishes these clearly — assessment is broader, more systematic, and often automated, while penetration testing is targeted, manual, and requires explicit authorization.
