0%

Book Description

Many organizations now run applications in cloud native environments, using containers and orchestration to facilitate scalability and resilience. But how do you know whether your deployment is secure? To fully grasp the security implications of containers and their operation, you’ll need an understanding of what they are and how they work. In this excerpt from her forthcoming book Container Security, author Liz Rice takes you through the mechanisms that isolate and protect your applications within each container.

This book as a whole looks at the building blocks and security boundaries commonly used in container-based systems and how they’re constructed in the Linux operating system. In the featured chapter, "Container Isolation," you’ll learn how namespaces limit the set of files and directories that particular container processes can see, functionally isolating them from other operations.

  • Learn how a container is actually a Linux process with a restricted view of the machine it’s running on
  • Explore the different namespaces typically used to create Linux containers
  • Examine how containerized processes are isolated from the host and other containerized processes

Table of Contents

  1. Preface
    1. Examples
  2. 1. Control Groups
    1. Cgroup hierarchies
    2. Creating cgroups
    3. Setting resource limits
    4. Assigning a process to a cgroup
    5. Docker using cgroups
    6. Cgroups v2
  3. 2. Container Isolation
    1. Linux namespaces
    2. Isolating the hostname
    3. Isolating process IDs
    4. Changing the root directory
    5. Combine namespaces and changing the root
    6. Mount namespace
    7. Network namespace
    8. User namespace
      1. User namespace restrictions
    9. Inter-process communications namespace
    10. Cgroup namespace
    11. Container processes from the host perspective
    12. Conclusions
  4. 3. Virtual machines
    1. Booting up a machine
    2. Enter the VMM
      1. Type 1 VMM, or Hypervisors
      2. Type 2 VMM
      3. Kernel-based Virtual Machines
    3. Trap-and-emulate
    4. Handling non-virtualizable instructions
    5. Process isolation
    6. Disadvantages of virtual machines
    7. Container isolation compared to VM isolation
  5. Index
18.119.133.228