The pieces are broken up into smaller parts (intro, broken abstractions, memory management), but the abstract and ILOs are still for the whole thing.

Currently it covers only the textbook literature. Adding an overview of current and motivating research will be good for an overview, e.g. modern types of attacks.

Add the OWASP top 10 and the material I made for the webappsec course.

Runnable examples are more convincing and easy to grasp. Hence the examples should be more complete, rather than the high-level principles which cannot be tested.

Show the simple principles by runnable examples, then the bigger examples are easier to grasp.

The people in Chalmers does interesting stuff on software security, specifically language related. Links to interesting material can be found here.

Look for software security examples using Python. Currently most examples are for C.

We should provide a Docker image for each lab. Then a lab computer only needs Docker and access to Docker Hub.

• Wheeler's Secure Programs
• Viega and McGraw's Building Secure Software: How to Avoid Security Problems the Right Way
• McGraw's Software Security: Building Security In

There is some work on how to achieve good software security in an organization, e.g.:

• BSIMM, overview in Computer 2016:1.

Other material on software security can be found here:

• Wheeler's Secure Programs
• Viega and McGraw's Building Secure Software: How to Avoid Security Problems the Right Way
• McGraw's Software Security: Building Security In

Based on some coverage of DLTs, add smart contract programming.

There are several options:

• Ethereum's Solidity language, there is also this material by Bonneau from the FOSAD summer school.
• Ethereum also has Vyper, which is a Python-like language for writing smart contracts.
• Dfinity might have something useful too. Or maybe it's still too early.