Security Requirements Engineering for Cloud Computing: The Secure Tropos Approach

In this paper, the author aim to present a threat and risk-driven methodology to security requirements engineering. The chosen approach has a strong focus on gathering, modeling, and analyzing the environment in which a secure ICT-system to be built is located. The knowledge about the environment comprises threat and risk models. As presented in the paper, this security-relevant knowledge is used to assess the adequacy of security mechanisms, which are then selected to establish security requirements.

Download Full-text

A Security Requirements Engineering Tool for Domain Engineering in Software Product Lines

Non-Functional Properties in Service Oriented Architecture ◽

10.4018/978-1-60566-794-2.ch004 ◽

2011 ◽

pp. 73-92

Author(s):

Jesús Rodríguez ◽

Eduardo Fernández-Medina ◽

Mario Piattini ◽

Daniel Mellado

Keyword(s):

Requirements Engineering ◽

Software Product Lines ◽

Product Line ◽

Security Requirements ◽

Engineering Process ◽

Product Lines ◽

Requirements Engineering Process ◽

Security Requirements Engineering ◽

Software Product ◽

Automated Support

The concepts of Service-Oriented Architectures and Software Product Lines are currently being paid a considerable amount of attention, both in research and in practice. Both disciplines promise to make the development of flexible, cost-effective software systems possible and to support high levels of reuse, and may sometimes be complementary to each other. In both paradigms, security is a critical issue, although most of the existing product line practices do not comprise all the security requirements engineering activities or provide automated support through which to perform these activities, despite the fact that it is widely accepted that the application of any requirements engineering process or methodology is much more difficult without a CARE (Computer-Aided Requirements Engineering) tool, since it must be performed manually. Therefore, this chapter shall present a tool denominated as SREPPLineTool, which provides automated support through which to facilitate the application of the security quality requirements engineering process for software product lines, SREPPLine. SREPPLineTool simplifies the management of security requirements in product lines by providing us with a guided, systematic and intuitive manner in which to deal with them from the early stages of product line development, thus simplifying the management and the visualization of artefact variability and traceability links and the integration of security standards, along with the management of the security reference model proposed by SREPPLine.

Download Full-text

Identifying Security Requirements Using the Security Quality Requirements Engineering (SQUARE) Method

Integrating Security and Software Engineering ◽

10.4018/978-1-59904-147-6.ch003 ◽

2007 ◽

pp. 43-69 ◽

Cited By ~ 8

Author(s):

N. R. Mead

Keyword(s):

Requirements Engineering ◽

Systematic Approach ◽

Promising Method ◽

Security Requirements ◽

Software Systems ◽

Quality Requirements ◽

Student Teams ◽

Security Requirements Engineering ◽

Engineering Institute

In this chapter, we describe general issues in developing security requirements, meth-ods that have been useful, and a method (SQUARE) that can be used for eliciting, analyzing, and documenting security requirements for software systems. SQUARE, which was developed by the CERT Program at Carnegie Mellon University’s Soft-ware Engineering Institute, provides a systematic approach to security requirements engineering. SQUARE has been used on a number of client projects by Carnegie Mellon student teams, prototype tools have been developed, and research is ongoing to improve this promising method.

Download Full-text

Identifying Security Requirements Using the Security Quality Requirements Engineering (SQUARE) Method

Information Security and Ethics ◽

10.4018/978-1-59904-937-3.ch065 ◽

2008 ◽

pp. 943-963

Author(s):

N. R. Mead

Keyword(s):

Requirements Engineering ◽

Systematic Approach ◽

Promising Method ◽

Security Requirements ◽

Software Systems ◽

Quality Requirements ◽

Student Teams ◽

Security Requirements Engineering ◽

Engineering Institute

In this chapter, we describe general issues in developing security requirements, methods that have been useful, and a method (SQUARE) that can be used for eliciting, analyzing, and documenting security requirements for software systems. SQUARE, which was developed by the CERT Program at Carnegie Mellon University’s Soft-ware Engineering Institute, provides a systematic approach to security requirements engineering. SQUARE has been used on a number of client projects by Carnegie Mellon student teams, prototype tools have been developed, and research is ongoing to improve this promising method.

Download Full-text

Novel Methods of Incorporating Security Requirements Engineering into Software Engineering Courses and Curricula

Software Engineering ◽

10.4018/978-1-60566-102-5.ch006 ◽

2009 ◽

pp. 98-113 ◽

Cited By ~ 1

Author(s):

Nancy R. Mead ◽

Dan Shoemaker

Keyword(s):

Software Engineering ◽

Case Studies ◽

Requirements Engineering ◽

Security Requirements ◽

Course Materials ◽

Body Of Knowledge ◽

Security Requirements Engineering ◽

Relationship Of ◽

The Relationship ◽

Future Plans

This chapter describes methods of incorporating security requirements engineering into software engineering courses and curricula. The chapter discusses the importance of security requirements engineering and the relationship of security knowledge to general computing knowledge by comparing a security body of knowledge to standard computing curricula. Then security requirements is related to standard computing curricula and educational initiatives in security requirements engineering are described, with their results. An expanded discussion of the SQUARE method in security requirements engineering case studies is included, as well as future plans in the area. Future plans include the development and teaching of academic course materials in security requirements engineering, which will then be made available to educators. The authors hope that more educators will be motivated to teach security requirements engineering in their software engineering courses and to incorporate it in their curricula.

Download Full-text