Security architecture vs security features
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
separate structural security decisions from individual controls.
Planned topics
- Features are controls added to one service (input validation, a login page); architecture decides where trust boundaries sit and how identity flows.
- Architecture decisions are costly to change later, so they need design attention early.
- Merging two organizations brings two identity systems, two trust models, and unknown assumptions.
- Start from assets and threats: what must be protected, from whom, and what happens if one component is breached.
Draft outline details
Demonstration
A diagram description: two organizations (Shop, FulfillCo) with their own user stores, services, and a partner path; circle the trust boundaries and mark where the two models meet.
Check your understanding
Why is security architecture decided early?
Show answer
It fixes boundaries and identity flows that are expensive to change later.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.