Skip to content
Technische Universität Berlin Deutsch
Course catalog and module transfer system

Security Lab ProjectModule description #40805 / Version 2

← Module page Deutsche Fassung
This module description is not valid in the current semester (Winter semester 2026/27).
Module / Version#40805 / #2
ValiditySS 2019 – WS 2019/20
Available language(s)English
Credit points9
Person responsible for the moduleSeifert, Jean-Pierre
GradingGraded
Exam formatPortfolio examination
Language(s) of instructionEnglish

Affiliation

FacultyFakultät IV
InstituteInstitut für Softwaretechnik und Theoretische Informatik
Academic chair34355100 FG S-Professur Security in Telecommunications (SecT)

Contact

OfficeNot specified
Contact personBuhren, Robert
E-mail addresslehre@sect.tu-berlin.de
WebsiteNot specified

Learning outcomes

This module’s qualification aims are:

1. Understanding of security relevant interfaces (hard- and software) of (embedded) computer systems
2. Practical experience in identifying, exploiting, and fixing of vulnerabilities in hard- and software
3. Development of scenarios regarding embedded system security aspects based on the practical experience gained in the practical course.
4. Ability of working on a complex project task in a team.

Content

In this project students develop their own piece of software which highlights a recently discovered or older, highly relevant kind of security vulnerability of their choice. To gain the relevant practical knowledge and hands-on-experience they attend the Security Lab (PR) as first part of the module.

The Security Lab offers students the opportunity to learn how to analyze the system security of Linux-based systems with an emphasis on embedded platforms. It covers topics from hardware security and debug facilities and then moves on to software security issues in applications and finally the kernel. This course focuses on practically relevant details and hands-on experience instead of providing thorough theoretical background information.

Students will have to solve multiple challenges on an ARM development board (Raspberry Pi II), where a system has to be analyzed and then compromised. In the project part they will create challenges of this kind on their own.
Basic Linux and C programming knowledge is required for the practical course. The usage of other implementation languages during the project part is possible.

TOPICS:
• Serial interface
• ARM/MIPS introduction
• JTAG hardware debugging interface
• OpenOCD, BusPirate, BusBlaster
• Software debugging with GDB
• Linux security tools
• Public key cryptography, certificates and signatures
• Shellcode
• Memory corruption vulnerabilities
• NX/XD/XN, ASLR, stack canaries
• ELF binary format
• Heap structure
• Integer overflows
• Kernel security

Module components

Compulsory area

The following courses are mandatory for this module:

CoursesTypeNumberFrequencyLanguageHours per weekCourse catalog
Security LabInternship0434 L 972 Winter and summer semester–4 ISIS
Security LabProject0434 L 985 Winter semester–4 ISIS

Workload and credit points

Security Lab (Internship)

Workload descriptionMultiplierHoursTotal
Assignments425 h100 h
Presence hours102 h20 h
120 h

Security Lab (Project)

Workload descriptionMultiplierHoursTotal
Concept130 h30 h
Implementation180 h80 h
Meetings52 h10 h
preparation of final presentation110 h10 h
written report120 h20 h
150 h

The workload of the module adds up to 270 hours. The module therefore comprises 9 credit points.

Description of teaching and learning methods

The module consists of a project and a preparatory practical course.

Requirements for participation and examination

Desirable prerequisites for participation in the courses:

Prerequisites:
• knowledge equivalent to the "Software Security" lecture
• familiarity with Unix/Linux operating system primitives (e.g. using a command line)

Recommended additional skills:
• basic networking concepts and tools (DNS, DHCP, NAT, ...)
• low-level programming concepts (pointers, registers, stack vs. heap, ...)
• basic concepts of cryptography

In order to complete the assignments, each participant needs at least one computer with administrator privileges (i.e. being able to log into university computers is insufficient) preferrably running Linux. It is possible to complete the tasks while using Windows or MacOS as well, but the teaching staff cannot provide guidance on those operating systems.

Mandatory requirements for the module examination registration:

This module has no examination requirements.

Completion of the module

GradingGraded
Exam formatPortfolio examination
Type of portfolio examination100 points in total
LanguageEnglish

Test elements

NamePoints/WeightCategoryDuration/Extent
(deliverable assessment) 4 assignments40practical2 weeks per assignment
project: final presentation10oral30 minutes
project: implementation30practicalsecond semester
project: written report (solution + documentation)20writtenapprox. 10 pages

Exam description

• (Practical Course) 4 practical assignments
• (Project Course) concept, project meetings in the group and with the supervisors, implementation, written report, final presentation

Duration of the module

The following number of semesters is estimated for taking and completing the module: 2 semester(s).

This module can be started in the following semesters: Winter and summer semester.

Maximum number of participants

The maximum capacity of participants is 18.

Registration procedures

As there is a hard limit of 18 students for the project, please register beforehand by sending an email to seclab-project@sect.tu-berlin.de. The first 18 students will be accepted - reception timestamp counts. A separate registration for the practical course Security Lab is not necessary in this case.
Additional registration with the examination office (usually via QISPOS) is still mandatory.

Recommended reading, lecture notes

Lecture notes

unavailable

Electronic lecture notes

unavailable

Recommended literature

No recommended literature given

Assigned programs

This module is not used in any program.

Miscellaneous

Not specified