An Analysis of the Security Patterns Landscape

Heyman, Thomas; Yskout, Koen; Scandariato, Riccardo; Joosen, Wouter

doi:10.1109/sess.2007.4

Cited by 57 publications

(46 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We believe that such a framework not only helps ensure the integration of security patterns with best practices early in the development process, but also helps to resolve two issues noted in the security patterns literature. The first is the observation that 35 percent of the published patterns do not pass the soundness test for patterns and, therefore, are considered to be guidelines or principles rather than formal patterns [17]. For example, security patterns like Asset Valuation and Threat Assessment [13] don't conform to the formal definition of a security pattern [17,33].…”

Section: Discussionmentioning

confidence: 99%

“…The first is the observation that 35 percent of the published patterns do not pass the soundness test for patterns and, therefore, are considered to be guidelines or principles rather than formal patterns [17]. For example, security patterns like Asset Valuation and Threat Assessment [13] don't conform to the formal definition of a security pattern [17,33]. However, since the ISDF incorporates best practices to guide secure development, patterns such as those can be avoided.…”

Section: Discussionmentioning

confidence: 99%

“…Since then, many other security patterns have been published. Although many of the published security patterns are considered to be merely guidelines or principals [17], security patterns have proven to be effective methods of dealing with security problems in a software system. Nevertheless, significant effort and security expertise are needed to properly apply them to a real software development situation.…”

Section: Scopementioning

confidence: 99%

“…According to a recent survey [17] there are currently a little over two hundred published security patterns. Despite the fact that thirty-five percent of these (so-called) patterns are considered to be merely guidelines or principals [17], security patterns have been proven to be effective methods of dealing with security problems in a software system.…”

Section: Security Patternsmentioning

confidence: 99%

See 3 more Smart Citations

The ISDF Framework: Towards Secure Software Development

Alkussayer¹,

Allen²

2010

Journal of Information Processing Systems

View full text Add to dashboard Cite

Abstract-The rapid growth of communication and globalization has changed the software engineering process. Security has become a crucial component of any software system. However, software developers often lack the knowledge and skills needed to develop secure software. Clearly, the creation of secure software requires more than simply mandating the use of a secure software development lifecycle; the components produced by each stage of the lifecycle must be correctly implemented for the resulting system to achieve its intended goals. This study demonstrates that a more effective approach to the development of secure software can result from the integration of carefully selected security patterns into appropriate stages of the software development lifecycle to ensure that security designs are correctly implemented. The goal of this study is to provide developers with an Integrated Security Development Framework (ISDF) that can assist them in building more secure software.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Discussionmentioning

confidence: 99%

Section: Scopementioning

confidence: 99%

Section: Security Patternsmentioning

confidence: 99%

See 2 more Smart Citations

The ISDF Framework: Towards Secure Software Development

Alkussayer¹,

Allen²

2010

Journal of Information Processing Systems

View full text Add to dashboard Cite

show abstract

“…Firstly, the techniques employed are mostly on the deployment level. Most of the previous work focus on implementation levels, such as cryptography protocols and algorithms [25,23], design patterns for system design and implementation [12,11], and internal control mechanisms [7,9].…”

Section: Figure 6 Relations Between the Security Modelsmentioning

confidence: 99%