@techreport{SchmidtJuerjens2011, author = {Schmidt, Holger and J{\"u}rjens, Jan}, title = {UMLsec4UML2 - Adopting UMLsec to Support UML2}, series = {LS 14 Software Engineering mit dem Schwerpunkt Entwicklung evolutionsf{\"a}higer Software und Systeme}, journal = {LS 14 Software Engineering mit dem Schwerpunkt Entwicklung evolutionsf{\"a}higer Software und Systeme}, publisher = {Technische Hochschule Dortmund}, address = {Dortmund}, doi = {10.17877/DE290R-990}, pages = {17}, year = {2011}, abstract = {In this paper, we present an approach to adopt UMLsec, which is defined for UML 1.5, to support the current UML version 2.3. The new profile UMLsec4UML2 is technically constructed as a UML profile diagram, which is equipped with a number of integrity conditions expressed using OCL. Consequently, the UMLsec4UML2-profile can be loaded in any Eclipse-based EMF- and MDT-compatible UML editing tool to develop and analyze different kinds of security models. The OCL constraints replace the static checks of the tool support for the old UMLsec defined for UML 1.5. Thus, the UMLsec4UML2-profile not only provides the whole expresiveness of UML2.3 for security modeling, it also brings considerably more freedom in selecting a basic UML editing tool, and it integrates modeling and analyzing security models. Since UML2.3 comprises new diagram types, as well as new model elements and new semantics of diagram types already contained in UML1.5, we consider a number of these changes in detail. More specifically, we consider composite structure and sequence diagrams with respect to modeling security properties according to the original version of UMLsec. The goal is to use UMLsec4UML2 to specify architectural security patterns.}, language = {en} } @inproceedings{JuerjensOchoaSchmidtetal.2011, author = {J{\"u}rjens, Jan and Ochoa, Mart{\´i}n and Schmidt, Holger and Marchal, Lo{\"i}c and Houmb, Siv Hilde and Islam, Shareeful}, title = {Modelling Secure Systems Evolution: Abstract and Concrete Change Specifications}, series = {Formal Methods for Eternal Networked Software Systems: 11th International School on Formal Methods for the Design of Computer, Communication and Software Systems, SFM 2011, Bertinoro, Italy, June 13-18, 2011. Advanced Lectures}, volume = {LNCS, 6659}, booktitle = {Formal Methods for Eternal Networked Software Systems: 11th International School on Formal Methods for the Design of Computer, Communication and Software Systems, SFM 2011, Bertinoro, Italy, June 13-18, 2011. Advanced Lectures}, editor = {Bernardo, Marco and Issarny, Val{\´e}rie}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-21455-4}, doi = {10.1007/978-3-642-21455-4_15}, pages = {504 -- 526}, year = {2011}, abstract = {Developing security-critical systems is difficult, and there are many well-known examples of vulnerabilities exploited in practice. In fact, there has recently been a lot of work on methods, techniques, and tools to improve this situation already at the system specification and design. However, security-critical systems are increasingly long-living and undergo evolution throughout their lifetime. Therefore, a secure software development approach that supports maintaining the needed levels of security even through later software evolution is highly desirable. In this chapter, we recall the UMLsec approach to model-based security and discuss on tools and techniques to model and verify evolution of UMLsec models.}, language = {en} }