A vulnerability is a weakness that a threat can exploit to disrupt an asset. The asset might be a building, network equipment, software, data, or a person. A weakness matters because it can leave something the organization relies on exposed to unauthorized access, disruption, damage, or theft. section 1.1.4 section 1.1.3
Weaknesses can arise in several ways:
- Software bugs, design flaws, or implementation errors. section 1.1.3 section 1.1.4
- Misconfigured security settings or poor security practices. section 1.1.4
- Human error or limited security awareness, such as sending sensitive data to the wrong person, clicking a malicious link, or using a weak password. section 1.1.4
A database without backups
A database without backups has a vulnerability: hardware failure could lead to data loss. The missing backup is the weakness; hardware failure is a threat that could act on it. An attack is different: it is an intentional exploitation of a vulnerability by a threat actor. section 1.1.4
To choose safeguards, identify the vulnerabilities affecting an asset, assess the associated risks, and apply controls that reduce the likelihood or impact of an incident. Controls may be physical, technical, or administrative; an asset often needs more than one. Consider whether a weakness could affect confidentiality, integrity, or availability, and weigh the asset’s value and exposure when choosing protection. section 1.1.5 section 1.4

















