Building secure systems using a security engineering process and security building blocks

Andre Rein, Carsten Rudolph, Jose Fran Ruiz

Research output: Chapter in Book/Report/Conference proceedingConference PaperResearch


In today's software development process, security related design decisions are rarely made early in the overall process. Even if security is considered early, this means that in most cases a more-or-less encompassing security requirements analysis is made. Based on this analysis best-practices, ad-hoc design decisions or individual expertise is used to integrate security during the development process or after weaknesses are found after the deployment. This paper explains the SecFutur security engineering process with a focus on Security Building Block Models which are used to build security related components, namely Security Building Blocks. These Security Building Blocks represent concrete security solutions and can be accessed via SecFutur patterns on the level of domain-specific models for particular application domains. The goal of this approach is to provide already defined and tested security related software components, which can be used early in the overall development process, to support security-design-decision already while modeling the software-system. Security Building Blocks are discussed in the context of the SecFutur Security Engineering Process with its requirement analysis and definition of security properties.

Original languageEnglish
Title of host publicationSoftware Engineering 2013 - Workshopband (inkl. Doktorandensymposium)
Subtitle of host publicationFachtagung des GI-Fachbereichs Softwaretechnik, 26.02.–01.03.2013, in Aachen [proceedings]
EditorsStefan Wagner, Horst Lichter
Place of PublicationBonn
PublisherGesellschaft fur Informatik (GI)
Number of pages16
ISBN (Print)9783885796091
Publication statusPublished - 2013
Externally publishedYes
EventMulti-Conference on Software Engineering, SE 2013 - Aachen, Germany
Duration: 26 Feb 20131 Mar 2013


ConferenceMulti-Conference on Software Engineering, SE 2013

Cite this