← Back to CoursesCyber Security: PhD Level

Neuroanatomy Explorer

Drag to rotate · scroll to zoom · click regions to explore

View
Loading 3D model…

Click a region
to explore it

Memory Deck

Flip each card and rate whether you knew it. Your score is saved.

Term
Definition

Deck complete — score saved.

Match the Pairs

Match each term to its definition. Finish the board to earn your score.

All matched — score saved.

Concept Constellation

Every key idea in this course, mapped as an explorable 3D constellation. Drag to rotate, scroll to zoom, click a node.

Click a node to read its definition.

Secure Operating Systems, Isolation, and Trusted Computing

Manual: General · Subject: Cyber Security

Analyze how kernels, enclaves, virtualization, and memory safety shape the security of modern compute platforms.

Operating System Security as an Enforcement Problem

The OS as reference monitor and attack surface

The operating system mediates access to memory, storage, devices, and processes, so it is both a security boundary and a large attack surface. Research questions include how to build complete mediation, minimize TCB size, and preserve isolation despite complex drivers, system calls, and shared resources.

Isolation mechanisms

Process isolation

  • Relies on virtual memory and kernel enforcement.
  • Fine-grained but vulnerable to kernel compromise.

Virtualization

  • Adds a hypervisor layer for separation.
  • Useful for consolidation and sandboxing.

What is the primary security benefit of virtualization?

Why is the kernel typically considered part of the trusted computing base?

Memory Safety and Exploit Mitigation

From buffer overflows to control-flow hijacking

Memory corruption remains one of the most consequential classes of vulnerabilities because it can lead to code execution, privilege escalation, and sandbox escape. Research and engineering responses include address space layout randomization, control-flow integrity, sandboxing, hardware-assisted memory tagging, and safer languages.

Typical mitigation stack

  1. 1

    Step 1: Prevent bugs using memory-safe languages where feasible.

  2. 2

    Step 2: Contain failures with sandboxing and least privilege.

  3. 3

    Step 3: Detect exploitation through monitoring and anomaly detection.

  4. 4

    Step 4: Harden control flow and sensitive interfaces.

  5. 5

    Step 5: Reduce exploit value using secrets isolation and rapid patching.

What does control-flow integrity primarily aim to prevent?

Name one limitation of relying only on sandboxing.

Trusted Execution and Attestation

Hardware roots of trust

Trusted execution environments and attestation aim to convince a remote verifier that code runs in a particular protected environment. However, they introduce questions about supply-chain trust, microarchitectural leakage, rollback resistance, and whether attestation meaningfully captures the security properties a user actually needs.

What is attestation used for?

Why are enclaves not a complete solution to system security?