liveBook · Manning

Security boundary

As explained in Microservices Patterns, Second Edition

A security boundary is a controlled interface across which access to protected resources is mediated and restricted.

A service API can act as a security boundary around sensitive data: callers access that data only through the API. Isolating sensitive-data subdomains reduces the attack surface; network controls can restrict access further. section 7.4.5

Use layered controls to limit access:

  • Isolate sensitive data, such as PII, in its own service and mediate access through its API. section 7.4.5
  • Restrict access further with firewall rules, service mesh rules, or private subnets. section 7.4.5

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines the service API as the access gate and names network controls, without detailing their configuration.
Examples
Isolates Personally Identifiable Information in its own service and exposes it only through that service’s API.
What you can do after
Apply it by isolating sensitive data in a service and limiting access through its API and network controls.
How it connects
Connects service APIs with firewalls, service mesh rules, and private subnets.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.