liveBook · Manning

Defense in depth

As explained in Build Financial Software with Generative AI (From Scratch)

Defense in depth is a security strategy that uses multiple independent layers of protection across physical, network, application, data, and access controls.

Defense in depth, also called security in layers, protects an organization through multiple security practices rather than relying on one control. For developers, the layers include application security, data protection, and access management alongside physical and network security. section 3.5

In containerized applications, practical layers include:

  • Run containers as read-only where possible to limit malicious changes after compromise. section 3.5
  • Constrain memory and CPU so one container cannot consume resources needed by the wider system. section 3.5
  • Use no-new-privileges to prevent applications from gaining additional privileges or root access. section 3.5
  • Encrypt and mask sensitive data, then authenticate and authorize users. section 3.5

How Build Financial Software with Generative AI (From Scratch) covers it

How deep it goes
Explains the principle and demonstrates container controls, while stopping short of a full security architecture.
Examples
Uses read-only containers, resource limits, no-new-privileges, encryption, data masking, authentication, and authorization.
What you can do after
Apply layered container controls and identify complementary application, data, and access protections.
How it connects
Connects least privilege with container security, data security, authentication, authorization, and access management.

Also explained in

Compare how 7 books explain defense in depth →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build Financial Software with Generative AI (From Scratch). The section links point to the parts of the book it draws on.