Proceedings of the 2006 International Workshop on Software Engineering for Secure Systems 2006
DOI: 10.1145/1137627.1137634
|View full text |Cite
|
Sign up to set email alerts
|

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 … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
46
0
1

Year Published

2007
2007
2022
2022

Publication Types

Select...
5
3
2

Relationship

0
10

Authors

Journals

citations
Cited by 91 publications
(50 citation statements)
references
References 19 publications
0
46
0
1
Order By: Relevance
“…requirements) have received a great deal of attention from researchers over the last ten years. Security requirements identification, reasoning and evaluation have also been extensively researched [40][41][42][43][44]. Yet, very little has been done to evaluate the adherence of the design stage to the intended security requirement, in particular evaluating the software architecture.…”
Section: Discussionmentioning
confidence: 99%
“…requirements) have received a great deal of attention from researchers over the last ten years. Security requirements identification, reasoning and evaluation have also been extensively researched [40][41][42][43][44]. Yet, very little has been done to evaluate the adherence of the design stage to the intended security requirement, in particular evaluating the software architecture.…”
Section: Discussionmentioning
confidence: 99%
“…. constraints on functional requirements to protect the assets from threats" [26]. For example, the webpage sent by the web server must be identical to the webpage received by the client (i.e., integrity).…”
Section: Kirin Security Rulesmentioning
confidence: 99%
“…In the realm of security software engineering, Haley et al [10,9] present a framework for representing security requirements in an application context and for both formal and informal argumentation about whether a system satisfies them. The proposed argumentation process specifies several iterative steps for the problem part of the Twin Peaks.…”
Section: Related Workmentioning
confidence: 99%