Skip to main content

DD2460 Software Safety and Security 7.5 credits

The course covers several fundamental techniques for the analysis of programs, with a focus on safety and security. The techniques are based on types and logics for programs, and allow to discover certain types of illicit behaviour or deduce the absence of such behaviour. We consider several successful tools implementing such techniques.

Choose semester and course offering

Choose semester and course offering to see current information and more about the course, such as course syllabus, study period, and application information.


For course offering

Autumn 2024 sss24 programme students

Application code


Headings with content from the Course syllabus DD2460 (Autumn 2024–) are denoted with an asterisk ( )

Content and learning outcomes

Course contents

  • Part I. Introduction to safety and security.
  • Part II. Temporal logics, modeling, model checking, formal specification. Tool: NuSMV.
  • Part III. System modeling with Event-B. Tool: Rodin.
  • Part IV. Concurrency, network programming. Tool: Java Pathfinder.
  • Part V. Memory safety, fuzzing Tools: memory checker, fuzzer.

Intended learning outcomes

After passing the course, the student should be able to:

  • explain safety and security aspects for systems,
  • construct models of systems,
  • specify and analyse safety and security properties,
  • apply analytical tools on software systems,
  • evaluate and compare different approaches to verification and validation of software systems,

in order to

  • as citizen and expert be able to discuss software safety and security,
  • in professional life and/or research projects be able to formally express safety and security related properties,
  • be able to use and adapt various tools and technologies to verify such properties.

Literature and preparations

Specific prerequisites

Knowledge in computer security, 6 credits, corresponding to completed course DD2395/DD2391.

Active participation in a course offering where the final examination is not yet reported in Ladok is considered equivalent to completion of the course.
Registering for a course is counted as active participation.
The term 'final examination' encompasses both the regular examination and the first re-examination.

Recommended prerequisites

Good knowledge and skills in programming, programming languages, and program semantics. Knowledge of first-order logic and finite automata.


No information inserted


No information inserted

Examination and completion

If the course is discontinued, students may request to be examined during the following two academic years.

Grading scale

A, B, C, D, E, FX, F


  • LAB2 - Laboratory work, 5.0 credits, grading scale: A, B, C, D, E, FX, F
  • TEN2 - Examination, 1.0 credits, grading scale: A, B, C, D, E, FX, F
  • ÖVN2 - Group presentation and report, 1.5 credits, grading scale: A, B, C, D, E, FX, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

Opportunity to complete the requirements via supplementary examination

No information inserted

Opportunity to raise an approved grade via renewed examination

No information inserted


Ethical approach

  • All members of a group are responsible for the group's work.
  • In any assessment, every student shall honestly disclose any help received and sources used.
  • In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

Further information

Course room in Canvas

Registered students find further information about the implementation of the course in the course room in Canvas. A link to the course room can be found under the tab Studies in the Personal menu at the start of the course.

Offered by

Main field of study

Computer Science and Engineering

Education cycle

Second cycle

Add-on studies

No information inserted


Cyrille Artho (

Transitional regulations

The earlier module EXA2 has been replaced by TEN2.

Supplementary information

In this course, the EECS code of honor applies, see:

Additional regulations

This course contains group projects and labs. Course registration after the official registration period is not possible, since we need to create the groups in the beginning of the course.