In short
- Definition: The protection of a system and its data against unauthorized access, use, change or destruction, both digital and physical.
- Goal: Preserve the confidentiality, integrity and availability of information.
- Example S.M.A.R.T. requirement: Zero critical vulnerabilities at release, 100% of users protected by multi-factor authentication, and an annual penetration test passed.
1. Definition
As a non-functional requirement, security describes the protection of a system and its data against unauthorized access, use, change or destruction, whether digital or physical [1].
Security is not a feature you add at the end. It is a property you design for and keep verifying.Key takeaway
In ISO/IEC 25010:2023, security includes confidentiality, integrity, non-repudiation, accountability, authenticity and resistance to attacks. In practice, security is often summarized by the CIA triad: confidentiality, integrity and availability [2].
Security requirements are best taken from recognized catalogs rather than invented: the OWASP Application Security Verification Standard (ASVS) for applications, the NIST Cybersecurity Framework 2.0 or ISO/IEC 27001 for the organization [3], [4], [5].
2. Goal
The goal is to preserve the confidentiality, integrity and availability of information, and to detect and respond to attacks.
Security failures lead to data breaches, fraud, ransom, regulatory fines and lasting loss of trust.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Critical vulnerabilities at release | Count | 0 | Security scanning and penetration test |
| Users protected by multi-factor authentication | % | 100% of users with access to sensitive data | Identity provider reports |
| ASVS verification level | Level met | Level 2 for most business applications | Security assessment against ASVS |
| Time to patch critical vulnerabilities | Days | < 7 | Patch management records |
| Security incidents | Count and severity | Decreasing; 0 major | Incident records |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Application: “The application shall meet OWASP ASVS level 2, verified by an independent assessment before go-live and every year after.”
- Identity: “100% of users with access to customer data shall use multi-factor authentication.”
- Release gate: “No release shall go to production with a known critical vulnerability; critical vulnerabilities found in production shall be fixed within 7 days.”
5. Questions to Ask Stakeholders
- What data and functions must be protected, and from whom?
- Which regulations and standards apply?
- Who may access what, and how is access granted and removed?
- How will security be tested before and after release?
- How will attacks be detected and incidents handled?
- Which third-party components and suppliers affect security?
6. Common Pitfalls
- Security as the last step. Late fixes are expensive. Include threat modeling and security requirements from the start.
- Inventing requirements. Use catalogs like OWASP ASVS so nothing obvious is missed.
- Forgetting operations. Patching, monitoring and incident response are part of security.
7. Related NFRs
- Privacy — protects personal data and people’s rights.
- Exploitability — how easily weaknesses can be used by attackers.
- Auditability and Control — records actions for investigations.
- Data Integrity — protects data against unauthorized change.
- Compliance — many rules require security controls.
8. FAQ
Confidentiality, integrity and availability: the three core goals of information security.
An open standard listing application security requirements and verification levels.
No. It is a snapshot. Combine it with secure design, code analysis, dependency scanning and monitoring.
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. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [6] |
| NIST | National Institute of Standards and Technology | United States government agency that publishes widely used standards and guides, notably in cybersecurity. | [7] |
| OWASP | Open Worldwide Application Security Project | Non-profit foundation that publishes free guidance on web application security, such as the OWASP Top 10. | [8] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [9] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ASVS | Application Security Verification Standard | OWASP checklist of security requirements for testing web applications. | [3] |
| CIA | Confidentiality, integrity, availability | The “CIA triad”: three core goals of information security. | [10] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [11] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [12] |
| 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. | [13] |
| Framework | Reusable foundation of code and conventions on which applications are built. | [14] |
| Incident | Unplanned interruption or degradation of a service. | [15] |
| Multi-factor authentication | Sign-in that requires two or more proofs of identity, such as a password and a phone code. | [16] |
| Patch | Update that fixes bugs or security holes. | [17] |
| Penetration test | Authorized simulated attack to find security weaknesses. | [18] |
| Personal data | Any information that relates to an identifiable person. | [19] |
| Production environment | The live system that real users use, as opposed to test environments. | [20] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [21] |
| Vulnerability | Weakness in software that an attacker could exploit. | [22] |
10. Sources and Further Reading
- [1] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [2] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [3] “OWASP Application Security Verification Standard (ASVS).” OWASP. https://owasp.org/www-project-application-security-verification-standard (accessed Nov. 18, 2026).
- [4] “The NIST Cybersecurity Framework (CSF) 2.0.” NIST. https://www.nist.gov/publications/nist-cybersecurity-framework-csf-20 (accessed Nov. 18, 2026).
- [5] “ISO/IEC 27001:2022 Information security management systems.” ISO. https://www.iso.org/standard/27001 (accessed Nov. 18, 2026).
- [6] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [7] “National Institute of Standards and Technology.” Wikipedia. https://en.wikipedia.org/wiki/National_Institute_of_Standards_and_Technology (accessed Nov. 19, 2026).
- [8] “OWASP.” Wikipedia. https://en.wikipedia.org/wiki/OWASP (accessed Nov. 19, 2026).
- [9] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [10] “Information security.” Wikipedia. https://en.wikipedia.org/wiki/Information_security (accessed Nov. 19, 2026).
- [11] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [12] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [13] “Authentication.” Wikipedia. https://en.wikipedia.org/wiki/Authentication (accessed Nov. 19, 2026).
- [14] “Software framework.” Wikipedia. https://en.wikipedia.org/wiki/Software_framework (accessed Nov. 19, 2026).
- [15] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [16] “Multi-factor authentication.” Wikipedia. https://en.wikipedia.org/wiki/Multi-factor_authentication (accessed Nov. 19, 2026).
- [17] “Patch (computing).” Wikipedia. https://en.wikipedia.org/wiki/Patch_(computing) (accessed Nov. 19, 2026).
- [18] “Penetration test.” Wikipedia. https://en.wikipedia.org/wiki/Penetration_test (accessed Nov. 19, 2026).
- [19] “Personal data.” Wikipedia. https://en.wikipedia.org/wiki/Personal_data (accessed Nov. 19, 2026).
- [20] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (accessed Nov. 19, 2026).
- [21] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [22] “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 @dizzydizz; inline photo by @mbacloud, both on Unsplash.




