CISSP 9.19 - Essential Security Protection Mechanisms

This episode of the ISC2 Certified Information Systems Security Professional (CISSP) exam prep series digs into the Domain 3 mechanisms that keep a system trustworthy from the inside — the quiet foundation under everything else you build, from how a system decides what to trust to where its chain of trust actually begins.

Frequently Asked Questions

Why should you never simply trust software?

Any code written outside the operating system is, by default, unproven. Since third-party software comes from someone other than the operating-system maker, it might misbehave, so the system treats it as potentially harmful and isolates it — the principle of zero trust applied right down at the machine level. The time to build these protections is early, during design, because security added only after the fact almost always fails.

How does an operating system keep processes from stepping on each other?

Through process isolation. The operating system gives each process its own separate memory space and strictly enforces those boundaries, so one process cannot read or write another’s data, which blocks unauthorized access and protects the integrity of every process. Many systems deliver this by giving each process a virtual machine view, where it behaves as if it owns the entire computer.

What does hardware segmentation add that software cannot?

Hardware segmentation serves the same goal as process isolation, keeping one process away from another’s information, but it enforces the separation with physical hardware controls rather than software rules. That makes the boundary far harder to defeat, but also expensive and complex, so it tends to appear only where the stakes are extreme, such as national security systems.

Where does a system’s chain of trust actually begin?

At the root of trust, the anchor point from which every other security assurance flows and the foundation for verifying the integrity, authenticity, and confidentiality of what the system does. At its heart sits a trust anchor, a component that is inherently trusted and deliberately made tamper-resistant. The strongest form is a hardware root of trust, built into dedicated chips such as a trusted platform module or a hardware security module, which isolate cryptographic keys and operations from the general computing environment.

How does a security policy shape a system from the very start?

A system security policy guides the design, development, testing, and maintenance of one specific system, defining the rules and procedures for how it manages, protects, and distributes sensitive information. A policy that specifically prevents information from flowing down from higher security levels to lower ones is called a multilevel security policy. Security must be considered across the entire life of the project, applied to hardware, firmware, software, and how people use the system.

Reference: This article is based on concepts discussed in CISSP 9.19 - Essential Security Protection Mechanisms.