The DOI matches its Crossref record; 53 of the 53 references it cites were found in a registry or an index.
Security Requirements Engineering: A Framework for Representation and Analysis
Abstract
This paper presents a framework for security requirements elicitation and analysis. The framework is based on constructing a context for the system, representing security requirements as constraints, and developing satisfaction arguments for the security requirements. The system context is described using a problem-oriented notation, then is validated against the security requirements through construction of a satisfaction argument. The satisfaction argument consists of 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. We evaluate the framework by applying it to a security requirements analysis within an air traffic control technology evaluation project.
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
Cites
Toulmin, S. E. (2003) · doi:10.1017/cbo9780511840005 · Cited by 7,101
Role-based access control models
Sandhu, R. S., Coyne, E. J., Feinstein, H. L., & Youman, C. E. (1996) · Computer · doi:10.1109/2.485845 · Cited by 5,892
Basic concepts and taxonomy of dependable and secure computing
Avizienis, A., Laprie, J.-C., Randell, B., & Landwehr, C. (2004) · IEEE Transactions on Dependable and Secure Computing · doi:10.1109/tdsc.2004.2 · Cited by 5,223
On Non-Functional Requirements in Software Engineering
Chung, L., & do Prado Leite, J. C. S. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-02463-4_19 · Cited by 2,247
Goal-oriented requirements engineering: a guided tour
van Lamsweerde, A. (2002) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/isre.2001.948567 · Cited by 1,723
Non-Functional Requirements in Software Engineering
Chung, L., Nixon, B. A., Yu, E., & Mylopoulos, J. (2000) · Springer eBooks · doi:10.1007/978-1-4615-5269-7 · Cited by 1,690
Requirements Engineering: Processes and Techniques
Kotonya, G., & Sommerville, I. (1998) · Lancaster EPrints (Lancaster University) · Cited by 1,688
A Comparison of Commercial and Military Computer Security Policies
Clark, D. D., & Wilson, D. R. (1987) · 1987 IEEE Symposium on Security and Privacy · doi:10.1109/sp.1987.10001 · Cited by 1,137
Representing and using nonfunctional requirements: a process-oriented approach
Mylopoulos, J., Chung, L., & Nixon, B. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.142871 · Cited by 1,018
Toulmin, S. E., Rieke, R. D., & Janik, A. S. (1979) · Cited by 923
The Chinese Wall security policy
Brewer, D. F. C., & Nash, M. J. (2003) · Proceedings. 1989 IEEE Symposium on Security and Privacy · doi:10.1109/secpri.1989.36295 · Cited by 882
Pfleeger, C. P. (1988) · Cited by 808
Telos: representing knowledge about information systems
Mylopoulos, J., Borgida, A., Jarke, M., & Koubarakis, M. (1990) · ACM Transactions on Information Systems · doi:10.1145/102675.102676 · Cited by 786
Thompson, K. (1984) · Communications of the ACM · doi:10.1145/358198.358210 · Cited by 666
Handling obstacles in goal-oriented requirements engineering
van Lamsweerde, A., & Letier, E. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.879820 · Cited by 648
Weaving together requirements and architectures
Nuseibeh, B. (2001) · Computer · doi:10.1109/2.910904 · Cited by 517
Self-citationSoftware safety: why, what, and how
Leveson, N. G. (1986) · ACM Computing Surveys · doi:10.1145/7474.7528 · Cited by 471
Visualizing Argumentation: Software Tools for Collaborative and Educational Sense-Making
Kirschner, P. A., Shum, S. B., & Carr, C. S. (2012) · Cited by 442
Building Secure Software: How to Avoid Security Problems the Right Way
Viega, J., & McGraw, G. E. (2001) · Cited by 440
Software engineering for security: a roadmap
Devanbu, P. T., & Stubblebine, S. (2000) · Proceedings of the Conference on The Future of Software Engineering · doi:10.1145/336512.336559 · Cited by 418
Using abuse case models for security requirements analysis
McDermott, J. P., & Fox, C. (2003) · Annual Computer Security Applications Conference · doi:10.1109/csac.1999.816013 · Cited by 398
The internet worm program: an analysis
Spafford, E. H. (1989) · ACM SIGCOMM Computer Communication Review · doi:10.1145/66093.66095 · Cited by 397
Security and privacy requirements analysis within a social setting
Liu, L., Yu, E., & Mylopoulos, J. (2004) · Journal of Lightwave Technology · doi:10.1109/icre.2003.1232746 · Cited by 393
Johnson, F., & Philosophy Documentation Center (1980) · Teaching Philosophy · doi:10.5840/teachphil19803321 · Cited by 374
Elaborating Security Requirements by Construction of Intentional Anti-Models
van Lamsweerde, A., & Engineering, P. 2. I. C. O. S. (2004) · Cited by 351
Lee, J., & Lai, K.-Y. (2020) · Design Rationale · doi:10.1201/9781003064053-3 · Cited by 348
Security Engineering: A Guide to Building Dependable Distributed Systems
Anderson, R. (2020) · doi:10.1002/9781119644682 · Cited by 345
Eliciting security requirements by misuse cases
Sindre, G., & Opdahl, A. L. (2002) · doi:10.1109/tools.2000.891363 · Cited by 328
Security quality requirements engineering (SQUARE) methodology
Mead, N. R., & Stehney, T. (2005) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/1082983.1083214 · Cited by 317
Recording the reasons for design decisions
Potts, C., & Bruns, G. (2003) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse.1988.93722 · Cited by 308
Supporting systems development by capturing deliberations during requirements engineering
Ramesh, B., & Dhar, V. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.142872 · Cited by 284
Breaux, T. D., Vail, M. W., & Anton, A. I. (2006) · 14th IEEE International Requirements Engineering Conference (RE'06) · doi:10.1109/re.2006.68 · Cited by 273
Recording the reasons for design decisions
Potts, C., & Bruns, G. (1988) · doi:10.5555/55823.55863 · Cited by 271
Elaborating security requirements by construction of intentional anti-models
van Lamsweerde, A. (2004) · Proceedings/Proceedings - International Conference on Software Engineering · doi:10.1109/icse.2004.1317437 · Cited by 234
Specifying Reusable Security Requirements.
Firesmith, D. (2004) · The Journal of Object Technology · doi:10.5381/jot.2004.3.1.c6 · Cited by 214
A framework for security requirements engineering
Haley, C. B., Moffett, J. D., Laney, R., & Nuseibeh, B. (2006) · Proceedings of the 2006 international workshop on Software engineering for secure systems · doi:10.1145/1137627.1137634 · Cited by 162
Self-citationCommon Concepts Underlying Safety Security and Survivability Engineering
Firesmith, D. G. (2003) · Defense Technical Information Center (DTIC) · doi:10.21236/ada421683 · Cited by 155
Keyboard acoustic emanations revisited
Li, Z., Zhou, F., & Tygar, J. D. (2005) · ACM SIGSAC Conference on Computer and Communications Security (CCS) · doi:10.1145/1102120.1102169 · Cited by 150
Dialog Mapping: Reflections on an Industrial Strength Case Study
Conklin, J. (2003) · Computer supported cooperative work · doi:10.1007/978-1-4471-0037-9_6 · Cited by 140
Common Concepts Underlying Safety, Security, and Survivability Engineering
Firesmith, D. G. (2003) · KiltHub Repository · doi:10.1184/r1/6572621.v1 · Cited by 131
Security quality requirements engineering (SQUARE) methodology
Mead, N. R., & Stehney, T. (2005) · doi:10.1145/1083200.1083214 · Cited by 127
The Roots of Computer Supported Argument Visualization
Shum, S. B. (2003) · Computer supported cooperative work · doi:10.1007/978-1-4471-0037-9_1 · Cited by 114
Dealing with security requirements during the development of information systems
Chung, L. (1993) · Notes on numerical fluid mechanics and multidisciplinary design · doi:10.1007/3-540-56777-1_13 · Cited by 94
Design rationale: Concepts, techniques, and use
Ullman, D. G. (1997) · Design Studies · doi:10.1016/s0142-694x(97)89853-5 · Cited by 84
Rethinking the Notion of Non-Functional Requirements
Glinz, M. (2005) · Cited by 75
Strategies for Developing Policies and Requirements for Secure Electronic Commerce Systems
Antón, A. I., & Earp, J. B. (2000) · NCSU Libraries Repository (North Carolina State University Libraries) · Cited by 66
Pushing Toulmin Too Far: Learning From an Argument Representation Scheme
Newman, S. E., & Marshall, C. (1998) · Cited by 63
Arguing security: validating security requirements using structured argumentation
Haley, C. B., Moffett, J., Laney, R., et al. (2005) · Open Research Online - ORO (The Open University) · Cited by 54
Self-citationUsing trust assumptions with security requirements
Haley, C. B., Laney, R., Moffett, J., et al. (2005) · Requirements Engineering · doi:10.1007/s00766-005-0023-4 · Cited by 44
Self-citationE-Commerce Security and Privacy
Ghosh, A. K. (2001) · Advances in information security · doi:10.1007/978-1-4615-1467-1 · Cited by 41
SafSec: Commonalities Between Safety and Security Assurance
Lautieri, S., Cooper, D. E., & Jackson, D. (2007) · Springer eBooks · doi:10.1007/1-84628-130-x_5 · Cited by 38
The role of policy and stakeholder privacy values in requirements engineering
Antón, A. I., Earp, J. B., Potts, C., et al. (2002) · IEEE International Symposium on Requirements Engineering (RE) · doi:10.1109/isre.2001.948553 · Cited by 36
Strategies for Developing Policies and Requirements for Secure and Private Electronic Commerce
Antón, A. I., & Earp, J. B. (2001) · Advances in information security · doi:10.1007/978-1-4615-1467-1_5 · Cited by 24
Cited by
A survey of emerging threats in cybersecurity
Jang-Jaccard, J., & Nepal, S. (2014) · Journal of Computer and System Sciences · doi:10.1016/j.jcss.2014.02.005 · Cited by 892
On the Security of the Automatic Dependent Surveillance-Broadcast Protocol
Strohmeier, M., Lenders, V., & Martinovic, I. (2015) · IEEE Communications Surveys & Tutorials · doi:10.1109/comst.2014.2365951 · Cited by 298
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
Towards a Unified Secure Cloud Service Development and Deployment Life-Cycle
Hudic, A., Flittner, M., Lorunser, T., Radl, P. M., & Bless, R. (2016) · 2016 11th International Conference on Availability, Reliability and Security (ARES) · doi:10.1109/ares.2016.73 · Cited by 5
Metadata
- Authors
- Haley, C. B., Laney, R., Moffett, J. D., & Nuseibeh, B.
- Venue
- IEEE Transactions on Software Engineering
- Published
- 2008-01
- Volume
- 34
- Issue
- 1
- Pages
- 133-153
- ISSN
- 0098-5589 (ISSN-L)
- OpenAlex
- W2131730994
- Cited by
- 462
- References
- 53
- FWCI
- 135.34
- Type
- journal article
- 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
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.