The DOI matches its Crossref record.
A framework for security requirements engineering
Abstract
This paper presents a framework for security requirements elicitation and analysis, based upon the construction of a context for the system and satisfaction arguments for the security of the system. One starts with enumeration of security goals based on assets in the system. These goals are used to derive security requirements in the form of constraints. The system context is described using a problem-centered notation, then this context is validated against the security requirements through construction of a satisfaction argument. The satisfaction argument is in two parts: a formal argument that the system can meet its security requirements, and a structured informal argument supporting the assumptions expressed in the formal argument. The construction of the satisfaction argument may fail, revealing either that the security requirement cannot be satisfied in the context, or that the context does not contain sufficient information to develop the argument. In this case, designers and architects are asked to provide additional design information to resolve the problems.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cited by
On lightweight mobile phone application certification
Enck, W., Ongtang, M., & McDaniel, P. (2009) · Proceedings of the 16th ACM conference on Computer and communications security · doi:10.1145/1653662.1653691 · Cited by 921
Security Requirements Engineering: A Framework for Representation and Analysis
Haley, C. B., Laney, R., Moffett, J. D., & Nuseibeh, B. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2007.70754 · Cited by 462
Self-citationAddressing privacy requirements in system design: the PriS method
Kalloniatis, C., Kavakli, E., & Gritzalis, S. (2008) · Requirements Engineering · doi:10.1007/s00766-008-0067-3 · Cited by 269
A comparison of security requirements engineering methods
Fabian, B., Gürses, S., Heisel, M., Santen, T., & Schmidt, H. (2010) · Requirements Engineering · doi:10.1007/s00766-009-0092-x · Cited by 239
A scenario-based framework for the security evaluation of software architecture
Alkussayer, A., & Allen, W. H. (2010) · 2010 3rd International Conference on Computer Science and Information Technology · doi:10.1109/iccsit.2010.5564015 · Cited by 22
Metadata
- Authors
- Haley, C. B., Moffett, J. D., Laney, R., & Nuseibeh, B.
- Venue
- Proceedings of the 2006 international workshop on Software engineering for secure systems
- Publisher
- ACM
- Published
- 2006-05-20
- Pages
- 35-42
- OpenAlex
- W2163022780
- Cited by
- 162
- References
- 0
- FWCI
- 46.73
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: A framework for security requirements engineering. https://app.cochat.ai/papers/10.1145/1137627.1137634
- The paper
- Haley, C. B., Moffett, J. D., Laney, R., & Nuseibeh, B. (2006). A framework for security requirements engineering. Proceedings of the 2006 international workshop on Software engineering for secure systems. https://doi.org/10.1145/1137627.1137634
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.