A survey on security patterns
Open accessThe DOI matches its Crossref record; 30 of the 30 references it cites were found in a registry or an index.
Abstract
Security has become an important topic for many software systems.Security patterns are reusable solutions to security problems.Although many security patterns and techniques for using them have been proposed, it is still difficult to adapt security patterns to each phase of software development.This paper provides a survey of approaches to security patterns.As a result of classifying these approaches, a direction for the integration and future research topics is illustrated.
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
(1994) · Cited by 21,711
A framework for information systems architecture
Zachman, J. A. (1987) · IBM Systems Journal · doi:10.1147/sj.263.0276 · Cited by 3,228
Alexander, C. (1979) · Cited by 3,187
Tropos: An Agent-Oriented Software Development Methodology
Bresciani, P., Perini, A., Giorgini, P., Giunchiglia, F., & Mylopoulos, J. (2004) · Autonomous Agents and Multi-Agent Systems · doi:10.1023/b:agnt.0000018806.20944.ef · Cited by 1,747 · cited 1×
“Tropos [4] is a model for analysis of requirements among stakeholders.”
BackgroundLogical foundations of object-oriented and frame-based languages
Kifer, M., Lausen, G., & Wu, J. (1995) · Journal of the ACM · doi:10.1145/210332.210335 · Cited by 1,450 · cited 2×
“Using a symbolic ontology representation language F-Logic [48], this approach defines a knowledge base composed of a security ontology, mappings between security concepts and security pattern elements, and inference rules among patterns (such as pattern p1 requires another pattern p2 in its solution).”
MethodRefactoring object-oriented frameworks
Opdyke, W. F. (1992) · Illinois Digital Environment for Access to Learning and Scholarship (University of Illinois at Urbana-Champaign) · Cited by 1,126
Problem Frames: Analyzing and Structuring Software Development Problems
Jackson, M. (2000) · Medical Entomology and Zoology · Cited by 951
SecureUML: A UML-Based Modeling Language for Model-Driven Security
Lodderstedt, T., Basin, D., & Doser, J. (2002) · Lecture Notes in Computer Science · doi:10.1007/3-540-45800-x_33 · Cited by 763 · cited 1×
“For modeling security concerns, models such as UMLsec [67] and SecureUML [75] have been proposed, so we need to adapt such models to security patterns.”
MethodHoward, M., LeBlanc, D. J., & Valentine, B. (2001) · Cited by 551
Building Secure Software: How to Avoid Security Problems the Right Way
Viega, J., & McGraw, G. E. (2001) · Cited by 503
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 · cited 1×
“Devanbu et al. stated this as follows [1]: " Security concerns must inform every phase of software development, from requirements engineering to design, implementation, testing , and deployment.”
BackgroundKerievsky, J. (2004) · Lecture Notes in Computer Science · doi:10.1007/978-3-540-27777-4_54 · Cited by 406
Architectural Patterns for Enabling Application Security
Yoder, J. W., & Barcalow, J. (1998) · 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 · cited 1×
“This means that we do not consider general methods such as SQUARE [3], Tropos [4], UMLsec [5], and so forth.”
MethodIFIP—international federation for information processing
(1991) · Information Systems · doi:10.1016/0306-4379(91)90042-8 · Cited by 282
Steel, C., Nagappan, R., & Lai, R. (2005) · Cited by 204
Security Engineering with Patterns
Schumacher, M. (2003) · Lecture Notes in Computer Science · doi:10.1007/b11930 · Cited by 202
Viega, J., & McGraw, G. E. (2001) · Cited by 156
Secure Software Development by Example
Apvrille, A., & Pourzandi, M. (2005) · IEEE Security & Privacy · doi:10.1109/msp.2005.103 · Cited by 120 · cited 1×
“For example, these include aspect-oriented security design methodologies, in which the security aspects are modeled using patterns and weaved into functional models [65], [66]; a security engineering process based on problem frames [9] with security patterns [14]; and an approach using security patterns and UMLSec [67…”
MethodHafiz, M., Adamczyk, P., & Johnson, R. E. (2007) · IEEE Software · doi:10.1109/ms.2007.114 · Cited by 111 · cited 2×
“proposed several ways to classify and organize security patterns [52], such as a classification based on the CIA model [53], which describes three key aspects of security (confidentiality, integrity, and availability), a tabular classification based on patterns’ application contexts and the Zachman framework [54], and…”
BackgroundMethodAn aspect-based approach to modeling access control concerns
Ray, I., France, R. B., Li, N., & Georg, G. (2004) · Information and Software Technology · doi:10.1016/j.infsof.2003.10.007 · Cited by 100 · cited 1×
“For example, these include aspect-oriented security design methodologies, in which the security aspects are modeled using patterns and weaved into functional models [65], [66]; a security engineering process based on problem frames [9] with security patterns [14]; and an approach using security patterns and UMLSec [67…”
MethodSecure Programming for Linux and Unix HOWTO
Wheeler, D. A. (2003) · Cited by 89
Misuse and abuse cases: getting past the positive
Hope, P., McGraw, G. E., & Antón, A. I. (2004) · IEEE Security & Privacy · doi:10.1109/msp.2004.17 · Cited by 79 · cited 1×
“• Problem-Frame-based models: abuse frame [70], anti-requirements [71], malicious subject, etc • Tropos-based models: i*/Tropos, Secure Tropos [72], attacker agents, trust relations, etc • UML-based models: abuse case, misuse Case [73], misuse actions [74], etc”
BackgroundAn Analysis of the Security Patterns Landscape
Heyman, T., Yskout, K., Scandariato, R., & Joosen, W. (2007) · International Workshop on Software Engineering for Secure Systems (SESS) · doi:10.1109/sess.2007.4 · Cited by 72 · cited 5×
“For example, they found that the most well-represented objective of existing security patterns is access control [49].”
BackgroundMethodInfluentialPrivacy patterns for online interactions
Romanosky, S., Acquisti, A., Hong, J., Cranor, L. F., & Friedman, B. (2006) · Conference on Pattern Languages of Programs · doi:10.1145/1415472.1415486 · Cited by 68 · cited 2×
“Security patterns for privacy have also been proposed [26], [27].”
BackgroundA Pattern System for Security Requirements Engineering
Hatebur, D., Heisel, M., & Schmidt, H. (2007) · International Conference on Availability, Reliability and Security (ARES) · doi:10.1109/ares.2007.12 · Cited by 57
Requirements Engineering Meets Trust Management
Giorgini, P., Massacci, F., Mylopoulos, J., & Zannone, N. (2004) · Lecture notes in computer science · doi:10.1007/978-3-540-24747-0_14 · Cited by 51 · cited 4×
“We can use Secure Tropos to formally analyze from whom the permission to handle information should be obtained.”
BackgroundInfluentialSecurity Engineering Using Problem Frames
Hatebur, D., Heisel, M., & Schmidt, H. (2006) · Lecture notes in computer science · doi:10.1007/11766155_17 · Cited by 49 · cited 1×
“Hatebur et al. used the Security Problem Frame, based on the Problem Frame, to specify security patterns with security requirements [12]–[14].”
MethodModeling a Sensor Network by means of Clustering
Barali, E., Cerquitelli, T., & D’Elia, V. (2007) · International Workshop on Database and Expert Systems Applications (DEXA) · doi:10.1109/dexa.2007.23 · Cited by 41
Defining Security Requirements Through Misuse Actions
Fernández, E. B., VanHilst, M., Larrondo-Petrie, M. M., & Huang, S. (2006) · Springer eBooks · doi:10.1007/978-0-387-34831-5_10 · Cited by 31 · cited 1×
“• Problem-Frame-based models: abuse frame [70], anti-requirements [71], malicious subject, etc • Tropos-based models: i*/Tropos, Secure Tropos [72], attacker agents, trust relations, etc • UML-based models: abuse case, misuse Case [73], misuse actions [74], etc”
Background
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
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
“Selecting the right pattern is indeed not an easy task, especially when different pattern catalogs list similar patterns with different names [12], [14].”
BackgroundMethod
Metadata
- Authors
- YOSHIOKA, N., WASHIZAKI, H., & MARUYAMA, K.
- Venue
- Progress in Informatics
- Published
- 2008-03
- Issue
- 5
- Pages
- 35
- ISSN
- 1349-8606 (ISSN-L)
- 1349-8614
- OpenAlex
- W2079079970
- Cited by
- 173
- References
- 30
- FWCI
- 22.26
- Type
- journal article
- Language
- en
- Open access
- bronze
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.