@inproceedings{HeymanYskoutScandariatoetal.2011, author = {Heyman, Thomas and Yskout, Koen and Scandariato, Riccardo and Schmidt, Holger and Yu, Yijun}, title = {The Security Twin Peaks}, series = {Engineering Secure Software and Systems: Third International Symposium, ESSoS 2011, Madrid, Spain, February 9-10, 2011. Proceedings}, volume = {LNCS}, booktitle = {Engineering Secure Software and Systems: Third International Symposium, ESSoS 2011, Madrid, Spain, February 9-10, 2011. Proceedings}, number = {6542}, editor = {Erlingsson, {\´U}lfar and Wieringa, Roel and Zannone, Nicola}, publisher = {Springer}, address = {Berlin, Heidelberg}, isbn = {978-3-642-19124-4}, doi = {10.1007/978-3-642-19125-1_13}, pages = {167 -- 180}, year = {2011}, language = {en} } @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} } @article{Schmidt2011, author = {Schmidt, Holger}, title = {Threat and Risk-Driven Security Requirements Engineering}, series = {International Journal of Mobile Computing and Multimedia Communications}, volume = {3}, journal = {International Journal of Mobile Computing and Multimedia Communications}, number = {1}, publisher = {IGI Global}, issn = {1937-9412}, doi = {10.4018/jmcmc.2011010103}, pages = {35 -- 50}, year = {2011}, abstract = {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.}, 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} } @incollection{SchmidtHateburHeisel2011, author = {Schmidt, Holger and Hatebur, Denis and Heisel, Maritta}, title = {A Pattern-Based Method to Develop Secure Software}, series = {Software Engineering for Secure Systems: Industrial and Research Perspectives}, booktitle = {Software Engineering for Secure Systems: Industrial and Research Perspectives}, editor = {Mouratidis, Haralambos}, publisher = {IGI Global}, address = {Hershey}, isbn = {978-1-61520-837-1}, doi = {10.4018/978-1-61520-837-1.ch003}, pages = {32 -- 74}, year = {2011}, abstract = {The authors present a security engineering process based on security problem frames and concretized security problem frames. Both kinds of frames constitute patterns for analyzing security problems and associated solution approaches. They are arranged in a pattern system that makes dependencies between them explicit. The authors describe step-by-step how the pattern system can be used to analyze a given security problem and how solution approaches can be found. Afterwards, the security problems and the solution approaches are formally modeled in detail. The formal models serve to prove that the solution approaches are correct solutions to the security problems. Furthermore, the formal models of the solution approaches constitute a formal specification of the software to be developed. Then, the specification is implemented by generic security components and generic security architectures, which constitute architectural patterns. Finally, the generic security components and the generic security architecture that composes them are refined and the result is a secure software product built from existing and/or tailor-made security components.}, language = {en} } @misc{OPUS4-455, title = {282 - Fachbereichsordnung f{\"u}r den Fachbereich Medien der Fachhochschule D{\"u}sseldorf vom 28.11.2011}, address = {D{\"u}sseldorf}, organization = {Fachhochschule D{\"u}sseldorf}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:due62-opus-7077}, pages = {5}, year = {2011}, abstract = {Aufgrund des \S 26 Abs. 3 Satz 2 des Gesetzes {\"u}ber die Hochschulen des Landes Nordrhein-Westfalen (Hochschulgesetz-HG) in der Fassung vom 01.01.2007, der Grundordnung der Fachhochschule D{\"u}sseldorf vom 12.07.2010 ge{\"a}ndert durch Satzung vom 26.10.2011 hat der Fachbereichsrat des Fachbereichs Medien der Fachhochschule D{\"u}sseldorf folgende Fachbereichsordnung erlassen:}, language = {de} } @misc{OPUS4-454, title = {283 - Fachbereichsordnung f{\"u}r den Fachbereich Elektrotechnik der Fachhochschule D{\"u}sseldorf vom 01.12.2011}, address = {D{\"u}sseldorf}, organization = {Fachhochschule D{\"u}sseldorf}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:due62-opus-7061}, pages = {7}, year = {2011}, abstract = {Aufgrund \S 26 Abs. 3 des Gesetzes {\"u}ber die Hochschulen des Landes Nordrhein-Westfalen (Hochschulgesetz - HG) in der Fassung des Hochschulfreiheitsgesetzes vom 01. Januar 2007 (Hochschulfreiheitsgesetz - HFG) und der Grundordnung der Fachhochschule D{\"u}sseldorf (GO) vom 12.07.2010 ge{\"a}ndert durch Satzung vom 26.10.2011 hat der Fachbereich Elektrotechnik die folgende Fachbereichsordnung erlassen:}, language = {de} } @misc{OPUS4-453, title = {284 - Fachbereichsordnung f{\"u}r den Fachbereich Architektur der Peter Behrens School of Architecture der Fachhochschule D{\"u}sseldorf vom 01.12.2011}, address = {D{\"u}sseldorf}, organization = {Fachhochschule D{\"u}sseldorf}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:due62-opus-7055}, pages = {7}, year = {2011}, abstract = {Aufgrund des \S 26 Abs. 3 des Gesetzes {\"u}ber die Hochschulen des Landes Nordrhein-Westfalen (Hochschulgesetz -HG) in der Fassung des Hochschulfreiheitsgesetzes vom 01. Januar 2007 (Hochschulfreiheitsgesetz -HFG) und der Grundordnung der Fachhochschule D{\"u}sseldorf vom 12.07.2010 (Grundordnung -GO) ge{\"a}ndert durch Satzung vom 26.10.2011 hat der Fachbereichsrat des Fachbereichs Architektur folgende Fachbereichsordnung erlassen:}, language = {de} } @misc{OPUS4-452, title = {281 - Evaluationsordnung f{\"u}r den Fachbereich Design der Fachhochschule D{\"u}sseldorf; vom 17.11.2011}, address = {D{\"u}sseldorf}, organization = {Fachhochschule D{\"u}sseldorf}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:due62-opus-7040}, pages = {5}, year = {2011}, abstract = {Aufgrund des \S 7 Abs. 2 des Gesetzes {\"u}ber die Hochschulen im Lande Nordrhein-Westfalen (Hochschulgesetz - HG) in der Fassung vom 1. Januar 2007 (GV.NRW S 474) hat der Fachbereich Design der Fachhochschule D{\"u}sseldorf die folgende Evaluationsordnung erlassen:}, language = {de} } @misc{OPUS4-451, title = {280 - Erste Satzung zur {\"A}nderung der Fachbereichsordnung des Fachbereichs Design vom 14.11.2011}, address = {D{\"u}sseldorf}, organization = {Fachhochschule D{\"u}sseldorf}, url = {http://nbn-resolving.de/urn:nbn:de:hbz:due62-opus-7032}, pages = {2}, year = {2011}, abstract = {Aufgrund des \S 26 Absatz 3 des Gesetzes {\"u}ber die Hochschulen des Landes Nordrhein-Westfalen (Hochschulgesetz HG) in der Fassung vom 01.01.2007 (GV. NRW. S. 474) in Verbindung mit der Grundordnung der Fachhochschule D{\"u}sseldorf in der jeweils g{\"u}ltigen Fassung hat der Fachbereich Design die folgende Fachbereichsordnung erlassen:}, language = {de} }