Home > Research Groups > Software Engineering > Teaching > Secure Software Engineering SS2019

Secure Software Engineering SS2019


On 18.06.19, Jürgen Schmidt from Heise Security will be giving a guest lecture (in German):

Title: Sicherheitslücken:Warum uns Geheimhaltung nicht weiter bringt?

Speaker: Jürgen Schmidt ist Chefredakteur von heise Security und als Ressortleiter beim Computermagazin c't zuständig für alles was mit Sicherheit zu tun hat.

Abstract: Details zu einem akuten Sicherheitsproblem in die Welt hinauszuposaunen, klingt zunächst nach einer schlechten Idee. Schließlich profitieren potentielle Einbrecher ja von diesen Informationen. Der Vortrag zeichnet den schmerzhaften Weg zum heutigen Verständnis vom richtigen Umgang mit Sicherheitslücken nach und erklärt dabei unter anderem, was es mit den Spielarten Full, Responsible und Coordinated Disclosure auf sich hat. Und was Sicherheitsforscher und auch Anbieter von Diensten, Soft- oder Hardware beachten sollten, um dabei nicht unter die Räder zu geraten.


Also, on 21.05.19, Tobias Harmes from the company MindSquare will be talking about security pitfalls in the area of SAP systems.

Course Abstract

What does it take to engineer software systems securely? This is the key question we wish to address in this course. Answering it requires to develop an understanding of the following key areas of secure software engineering: threat modeling, secure design, secure coding, security validation, secure deployment and maintenance. In this course we will be covering those areas in an example-driven style, discussing current techniques applicable to those areas and lessons learned from concrete real-world security breaches.


Participants are expected to have completed or nearly completed the first section of the Bachelor degree, in particular the Softwaretechnikpraktikum or Softwarepraktikum. On top of that there are no special prerequisites for this course. However, for the BiBiFi contest, Learning Java before the course is highly recommended.

Course Material

The slides and exercise sheets will be uploaded after each lecture on the course's PANDA Page


The teaching language will be English. Questions in German will be permitted.

The programming language for the BiBiFi contest will be Java. Learning Java before the course is highly recommended. 

  • Lectures: 

          Tue 11:00-14:00 (c.t.) Room: A4

          A preliminary lecture schedule is available here.

  • Exercise classes:

          1. Wed 09:00-11:00 (c.t.)

          2. Wed 11:00-13:00 (c.t.)

          A preliminary class schedule is available here. 

Registration & Questions

To attend the course, you have to register in the PAUL system as a participant.

Final Exam

There will be two written exam dates.

Date / Time / Room:

  • 1. Exam: TBA
  • 2. Exam: TBA

Further Information:

  • The exam will be given in English. Answers in German will be permitted.
  • The use of a English-Deutsch dictionary is permitted.

Learning Outcomes

After having attended this course, participants will have developed a solid understanding of the most important aspects of secure software engineering, both in theory and practice. This includes the ability to identify and model threats to software systems, to avoid the most common classes of vulnerabilities, and to identify and apply techniques and tools to avoid or identify the introduction of security vulnerabilities.


The course will be comprising different theoretical and practical parts:

  • The main lecture will cover background information about all relevant aspects of a secure software-engineering lifecycle. We will be motivating and explaining the core ideas with real-world examples. An integral part of every lecture will be the discussion of one or two vulnerabilities of the day: inspired by past real-world vulnerabilities and attacks, we will discuss common vulnerability categories and attack patterns. Where possible, the vulnerabilities will directly relate to this day's remaining content of the lecture.
  • In addition, we will be conducting a practical contest called Build It, Break It, Fix It. The course is meant to help students experience a secure development lifecycle first hand. In the "Build It" phase, students will be asked to gather in teams and develop small software projects based on a formal specification, also including security requirements. In the "Break It" phase, the developed software will be exchanged between development teams to break the implementation, i.e., find and exploit security vulnerabilities in code of other teams. Lastly, in the "Fix It" phase, teams will get the chance to fix found vulnerabilities and, hence, render their software product more secure. This contest will be conducted using an automated online infrastructure.
    During this one hour on Thursday, we will be describing the contest in some weeks, and give students free time to work on the contest in other weeks.
    We used to run this as a separate MSc course, see here for this previous edition.
  • The exercise classes are meant to reinforce the student's understanding of the main lecture's content. With practical, sometimes interactive exercises students will be able to learn important skills that can also support their work in the Build It, Break It, Fix It contest.

The main lecture will discuss crucial elements of a Secure Software Development Lifecycle, including:

  • Threat modeling
  • Risk analysis
  • Architectural security
  • Secure coding
  • Applied Cryptography
  • Secure configuration and deployment
  • Updates and maintenance

Recommended Reading Material

We will not be able to provide a script for this course.
However, a lot of the topics are also covered in the book:

Gary McGraw. Software Security: Building Security In which you can access within the university network.

Regarding the contest, we recommend this publication:

Andrew Ruef, Michael Hicks, James Parker, Dave Levin, Michelle L. Mazurek, and Piotr Mardziel. 2016. Build It, Break It, Fix It: Contesting Secure Development. In Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security (CCS '16). ACM, New York, NY, USA, 690-703. DOI: doi.org/10.1145/2976749.2978382