liveBook · Manning

Deny-by-default

As explained in Grokking Software Architecture

Deny by default is a security policy in which access is rejected unless it is explicitly permitted.

Deny by default rejects network access unless it is explicitly permitted. For a legacy system, enabling it all at once can break traffic the application depends on, so introduce it gradually. section 11.3.3

A service-mesh migration can build toward this policy in stages:

  • Audit Mode: Log existing traffic without blocking it. section 11.3.3
  • Baseline: Identify which services need to communicate. section 11.3.3
  • Identity: Issue cryptographic certificates to services. section 11.3.3
  • Policy: Permit baseline traffic through least-privilege rules, then gradually turn on deny-by-default policies. section 11.3.3

How Grokking Software Architecture covers it

How deep it goes
Defines the access policy and outlines migration stages, but does not show policy syntax.
Examples
Uses a legacy application's observed network traffic to establish which service connections to permit.
What it assumes
Assumes legacy network traffic to observe and introduces audit, baseline, identity, and policy stages.
What you can do after
Configure service-mesh policies gradually, moving from observed legacy traffic to explicitly permitted connections.
How it connects
Connects Zero Trust, service meshes, least privilege, and mutual TLS.

Also explained in

Compare how 2 books explain deny-by-default →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.