2007
DOI: 10.1007/s10009-007-0048-8
|View full text |Cite
|
Sign up to set email alerts
|

Tools for secure systems development with UML

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
160
0

Year Published

2009
2009
2013
2013

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 131 publications
(160 citation statements)
references
References 22 publications
0
160
0
Order By: Relevance
“…For instance, misuse case [22] provide high level modeling constructs to capture threads to the system assets, but offer no special primitives for modeling nor reasoning about information integrity. In UMLsec [12], integrity was modeled as constraints that can restrict unwanted modification. SecureUML [3] was mainly developed to model access control policies, which can protect information integrity to a certain level.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
See 1 more Smart Citation
“…For instance, misuse case [22] provide high level modeling constructs to capture threads to the system assets, but offer no special primitives for modeling nor reasoning about information integrity. In UMLsec [12], integrity was modeled as constraints that can restrict unwanted modification. SecureUML [3] was mainly developed to model access control policies, which can protect information integrity to a certain level.…”
Section: Related Work and Conclusionmentioning
confidence: 99%
“…[22,12,3,13]). In this paper, we propose an extended version of i*/Tropos [23,7] modeling language to capture and analyze information integrity requirements starting from a socio-technical perspective.…”
Section: Introductionmentioning
confidence: 99%
“…This formalisation process relies on UML sequence diagrams that model a security protocol enabling the involved entities to apply security functions to the transferred data and, thus, protect it. To this end, we use the UML extension UMLsec, which offers a cryptographic notation for secure systems development [9].…”
Section: Securing the Recording And Storage Stagementioning
confidence: 99%
“…Due to space restriction, messages related to the TLS protocol are not presented. However, TLS formalisation can be found in [9].…”
Section: Messagesmentioning
confidence: 99%
“…Vulnerable actors take measures to mitigate perceived risks, by using locks on the doors, surveillance cameras, etc. Existing security requirements engineering frameworks focus on various aspects for eliciting security requirements, such as attacker behavior [29,31] and attacker goals [32], design of secure components [15], social aspects [18,11], and events that can cause system failure [1]. However, attacks and consequent security failures often take place because of the exploitation of weaknesses or backdoors within the system.…”
Section: Introductionmentioning
confidence: 99%