Security is much cheaper to design in than to bolt on later. A software architect decides where trust boundaries sit, how users and services prove who they are, and how a system keeps working when one of its protections fails. This module covers the ideas you need to make those decisions.
You'll start with Zero Trust, the model built on never trusting and always verifying. Then you'll look at OAuth 2.0 and OpenID Connect for authentication and authorization, threat modeling with STRIDE for finding risks early, and defense in depth for layering independent controls so that no single failure becomes a breach.
Next up is Scalability & Resilience, where you'll look at how to keep these systems fast and available as demand grows and things go wrong.
How the Zero Trust model works, why it assumes breach, and how it limits lateral movement inside a network.
The difference between authorization and authentication, and how OAuth 2.0 and OpenID Connect fit together.
A framework for finding security threats in a design by grouping them into six categories, from spoofing to elevation of privilege.
Why a layered set of independent security controls protects a system better than relying on any single barrier.