In short
- Definition: The ease with which a weakness in a system could be used by an attacker to cause harm; a good system has low exploitability.
- Goal: Make vulnerabilities hard to exploit and limit the damage when one exists.
- Example S.M.A.R.T. requirement: Zero critical or high CVSS findings open for more than 15 days, confirmed by penetration testing.
1. Definition
As a non-functional requirement, exploitability describes how easily a weakness in a system could be used by an attacker to cause harm [1]. A well-protected system has low exploitability [2].
Every system has bugs. The requirement is that they are hard to exploit and quickly fixed.Key takeaway
In vulnerability scoring, exploitability is a key factor of severity. The Common Vulnerability Scoring System (CVSS), maintained by FIRST, rates how a vulnerability can be reached and triggered (network or local access, complexity, privileges and user interaction required) together with its impact [3].
Lowering exploitability means reducing the attack surface, requiring authentication and least privilege, validating inputs, keeping components patched, and adding layers so that one flaw is not enough [4].
2. Goal
The goal is to make vulnerabilities hard to exploit and to limit the damage when one is found.
Highly exploitable systems are attacked automatically within hours of a flaw becoming public; the cost is data theft, ransom or service disruption.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Open critical or high vulnerabilities | Count older than the remediation deadline | 0 older than 15 days | Vulnerability scanner and tracker (CVSS-rated) |
| Penetration test findings | Critical/high findings | 0 open at release | Independent penetration test |
| Attack surface | Exposed endpoints and ports | Only those documented and required | External scan compared with inventory |
| Patch latency | Days to patch known exploited vulnerabilities | < 7 days | Patch management records |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Web application: “No vulnerability rated critical or high with CVSS shall remain open for more than 15 days, as confirmed by the monthly scan report.”
- Release gate: “Each major release shall pass an independent penetration test with no open critical or high finding.”
- Exposure: “Only the documented public endpoints shall be reachable from the internet, verified by a quarterly external scan.”
5. Questions to Ask Stakeholders
- Which parts of the system are exposed to the internet or to partners?
- What data or functions would an attacker want?
- What remediation deadlines apply by severity?
- How will vulnerabilities in third-party components be tracked?
- Who performs penetration tests, and how often?
- How are fixes deployed in an emergency?
6. Common Pitfalls
- Scoring without context. A base CVSS score ignores your environment. Adjust priority to exposure and data.
- Fixing only what scanners find. Design flaws and logic errors need threat modeling and manual testing.
- Slow patching. Known exploited flaws are attacked fast. Keep an emergency patch path.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Security — exploitability is one dimension of the overall security posture.
- Robustness — robust input handling closes many attack paths.
- Dependency on Other Parties — many exploitable flaws come from third-party components.
- Deployment — fast, safe deployment lets fixes reach production quickly.
8. FAQ
The Common Vulnerability Scoring System, an open framework maintained by FIRST to communicate the characteristics and severity of software vulnerabilities.
The set of points where an attacker could try to enter or extract data: endpoints, ports, interfaces, user inputs.
It lists the most critical web application security risks and is a common baseline for reducing exploitable weaknesses.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FIRST | Forum of Incident Response and Security Teams | Global association of computer security incident response teams; it maintains CVSS. | [5] |
| OWASP | Open Worldwide Application Security Project | Non-profit foundation that publishes free guidance on web application security, such as the OWASP Top 10. | [6] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [7] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| CVSS | Common Vulnerability Scoring System | Standard for rating the severity of security vulnerabilities from 0 to 10. | [8] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [9] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [1] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Authentication | Checking that a user or system is who it claims to be. | [10] |
| Deployment | Installing a new version of software in the environment where people use it. | [11] |
| Framework | Reusable foundation of code and conventions on which applications are built. | [12] |
| Latency | Delay between a request and the start of the response. | [13] |
| Least privilege | Giving each user or program only the access it strictly needs. | [14] |
| Patch | Update that fixes bugs or security holes. | [15] |
| Penetration test | Authorized simulated attack to find security weaknesses. | [16] |
| Production environment | The live system that real users use, as opposed to test environments. | [17] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [18] |
| Vulnerability | Weakness in software that an attacker could exploit. | [19] |
10. Sources and Further Reading
- [1] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [2] “OWASP Top 10:2025.” OWASP. https://owasp.org/Top10/2025/0x00_2025-Introduction/ (accessed Nov. 18, 2026).
- [3] “Common Vulnerability Scoring System v4.0, Specification Document.” FIRST. https://www.first.org/cvss/specification-document (accessed Nov. 18, 2026).
- [4] “Attack surface.” Wikipedia. https://en.wikipedia.org/wiki/Attack_surface (accessed Nov. 18, 2026).
- [5] “Forum of Incident Response and Security Teams.” Wikipedia. https://en.wikipedia.org/wiki/Forum_of_Incident_Response_and_Security_Teams (accessed Nov. 19, 2026).
- [6] “OWASP.” Wikipedia. https://en.wikipedia.org/wiki/OWASP (accessed Nov. 19, 2026).
- [7] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [8] “Common Vulnerability Scoring System.” Wikipedia. https://en.wikipedia.org/wiki/Common_Vulnerability_Scoring_System (accessed Nov. 19, 2026).
- [9] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [10] “Authentication.” Wikipedia. https://en.wikipedia.org/wiki/Authentication (accessed Nov. 19, 2026).
- [11] “Software deployment.” Wikipedia. https://en.wikipedia.org/wiki/Software_deployment (accessed Nov. 19, 2026).
- [12] “Software framework.” Wikipedia. https://en.wikipedia.org/wiki/Software_framework (accessed Nov. 19, 2026).
- [13] “Latency (engineering).” Wikipedia. https://en.wikipedia.org/wiki/Latency_(engineering) (accessed Nov. 19, 2026).
- [14] “Principle of least privilege.” Wikipedia. https://en.wikipedia.org/wiki/Principle_of_least_privilege (accessed Nov. 19, 2026).
- [15] “Patch (computing).” Wikipedia. https://en.wikipedia.org/wiki/Patch_(computing) (accessed Nov. 19, 2026).
- [16] “Penetration test.” Wikipedia. https://en.wikipedia.org/wiki/Penetration_test (accessed Nov. 19, 2026).
- [17] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [18] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [19] “Vulnerability (computer security).” Wikipedia. https://en.wikipedia.org/wiki/Vulnerability_(computer_security) (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @hocza; inline photo by @annaazart, both on Unsplash.








