Secure and Dependable Systems

• Course: Secure and Dependable Systems (CO-566)
• Semester: Spring 2023
• Prerequisites: Operating Systems (CO-562)
• Instructor: Jürgen Schönwälder
• Office Hours: Monday, 11:15-12:30, R.1-87
• TA: Nikolozi Bodaveli
• Class: Tuesday, 15:45-17:00, RLH-172 Conrad Naber Lecture Hall
• Class: Thursday, 15:45-17:00, RLH-172 Conrad Naber Lecture Hall
• 1st Module Exam: 2023-05-23 18:00-20:00, ICC East Wing
• 2nd Module Exam: 2023-08-29 14:00-16:00, Research I, Lecture Hall

This module introduces students to the fundamentals of computer security and techniques used to build and analyze dependable systems. This is an important topic given that computer systems are increasingly embedded in everyday objects (such as light bulbs) and taking over important control functions (such as driving cars). Furthermore, computer systems control complex communication systems that form critical infrastructure of the modern globalized world. Proper protection of information requires an applied understanding of cryptography and how cryptographic primitives are used to secure data and information exchanges. The aim of this module is to make students aware of what types of security vulnerabilities may arise in computing systems and how to prevent, identify, and fix them.

By the end of this module, students will be able to

• recall dependability terminology and concepts;
• explain control flow attacks and injection attacks and defense mechanisms;
• describe network data plane and control plane attacks and defense mechanisms;
• understand symmetric and asymmetric cryptographic algorithms;
• explain how digital signatures and public key infrastructures work;
• analyze key exchange protocols for weaknesses;
• describe secure network protocols (e.g., PGP, TLS, and SSH);
• recall anonymity terminology and concepts;
• discuss information hiding mechanisms (e.g., steganography, and watermarking);
• illustrate anonymization techniques (mixes, onion routing);

• Slides
• Lecture Notes
• Source Code

• Bruce Schneier: Applied Cryptography, 20th Anniversary Edition, Wiley, 2015
• Wm.Arthur Conklin, Gregory White: Principles of Computer Security, 5th Edition, McGraw-Hill, 2018
• Simon Singh: The Code Book: Science of Secrecy from Ancient Egypt to Quantum Cryptography, Anchor Books, 2000
• Dan Boneh and Victor Shoup: A Graduate Course in Applied Cryptography, 2023

The final grade is determined by a final exam (100%). There will be weekly marked homework assignments, each worth 10 points. Regular submission of good solutions for homework assignments can lead to bonus points. Bonus points can improve the final grade but they cannot turn a failing grade into a passing grade and they are limited to a maximum of 10 percent of the grade (see the undergraduate education policies). The usual rules for (medical) excuses apply.

The bonus b is derived from the points p earned in the homeworks as follows. For p in [0..50) points, the bonus is 0. For p in [50..100] points, the bonus b = p / 10. For p > 100, the b = 10. Bonus points can improve the final grade but they can't turn a failing grade into a passing grade and they are limited to a maximum of 10 percent of the grade (see the undergraduate education policies). The usual rules for (medical) excuses apply.

Electronic submission is the preferred way to hand in homework solutions. Please submit documents (plain ASCII/UTF-8 text or PDF, no Word) and your source code (packed into a tar or zip archive after removing all binaries and temporary files) via the online submission system. If you have problems, please contact one of the TAs.

Late submissions will not be accepted. Homeworks may need to be defended in an oral interview. In case you are ill, you have to follow the procedures defined in the university policies to obtain an official excuse. If you obtain an excuse, the new deadline will be calculated as follows:

1. Determine the number of days you were excused until the deadline day, not counting excused weekend days.
2. Determine the day of the end of your excuse and add the number of day you obtained in first step. This gives you the initial new deadline.
3. If the period between the end of your excuse and the new deadline calculated in the second step includes weekend days, add them as well to the new deadline. (Iterate this step if necessary.)

For any questions stated on assignment sheets, quiz sheets, exam sheets or during makeups, we by default expect a reasoning for the answer given, unless explicitly stated otherwise.

Students must submit solutions individually. If you copy material verbatim from the Internet (or other sources), you have to provide a proper reference. If we find your solution text on the Internet without a proper reference, you risk to lose your points. Any cheating cases will be reported to the registrar. In addition, you will lose the points (of course). These rules also apply to any generative AI tool, such as ChatGPT.

1. You are discouraged from using AI tools UNLESS under direct instruction from your instructor to do so. Please contact your instructor if you are unsure or have questions BEFORE using AI for any assignment.
2. If AI is permitted to be used, you must clearly state how AI was used in completing the assignments. No more than 25% of an assignment should be created with AI if the instructor gives permission for its use. If you are not sure whether a certain usage of AI is permitted for doing your assignments, contact the course instructor.
3. Note that the material generated by these programs may be inaccurate, incomplete, or otherwise problematic. Their use may also stifle your own independent thinking and creativity. Accordingly, reduction in the grade is likely when using AI. Rather use your own brain.

Any programs, which have to be written, will be evaluated based on the following criteria:

• correctness including proper handling of error conditions
• proper use of programming language constructs
• clarity of the program organization and design
• readability of the source code and any output produced

Source code must be accompanied by a README file providing an overview of the source files and giving instructions how to build the programs. A suitable Makefile is required if the build process involves more than a single source file.

If any part of these rules are confusing or uncertain, please reach out to your instructor for a conversation before submitting your work.

If you are unhappy with the grading, please report immediately (within one week) to the TAs. If you can't resolve things, contact the instructor. Problem reports which come late, that is after the one-week period, are not considered anymore.