CSE Roadmap

Core tier · about 3 hours · 7 parts

Part 1 of 7 · 1 min read

Why this page comes first

In this module you will

  • Separate protection (the mechanism that limits access) from security (the wider job of defending against attack).
  • Define a protection domain, and say which domain a Linux process runs in.
  • Read an access matrix, and derive access control lists and capability lists from it.
  • Compare ACLs and capabilities by storage, checking and revocation.
  • Explain the principle of least privilege with one example.

Levels 0 to 9 built the working parts of an OS: processes, memory, files and devices. Each of them can be misused by a program that should not touch it. Level 0 introduced user mode and kernel mode as the first wall. This level adds the rest of the walls. This page gives the model that all later pages fill in: subjects, objects and rights. Page 2 shows how Unix stores that model in file permission bits.

About this example About this example

Real: The C program in section 3 was compiled with gcc -Wall -Wextra and run on a Linux test machine (2 processors, kernel 6.18). The id and /proc/self/status lines in section 2 were read on the same machine, where the commands run as root and, with setpriv, as the user nobody.

Scripted: The four users, four objects and their rights in section 3, and the 1,000 users and 1,000,000 objects of section 4, are made up to show the idea.

Not real: The matrix in the program is a fixed table in memory. A real kernel checks rights when a system call opens or uses an object, and it keeps the lists inside the objects (for files, the inode of Level 9) or inside the process.