liveBook · Manning

Security requirement

As explained in Microservices Patterns, Second Edition

A security requirement is a condition specifying how software, systems, or data must be protected against threats.

Security requirements specify how software, systems, or data must be protected against threats. They are one characteristic to consider when deciding whether to separate subdomains into services; such segregation can improve security. section 7.4.5

How Microservices Patterns, Second Edition covers it

How deep it goes
Names security requirements among subdomain characteristics but does not define them or detail security-specific separation.
What you can do after
Evaluate whether separating subdomains with differing characteristics could improve security.
How it connects
Connects security requirements to subdomains, service boundaries, and microservice architecture.

Also explained in

Compare how 2 books explain security requirement →

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.