Topic lessonTopic: AWS authorization, encryption, audit and response
Threat-model AWS deployment approval and SQL Server restore boundaries
Identify what must be protected and who makes each decision. Turn safeguards from GitHub change approval to AWS deployment and database restoration into acceptance checks.
Turn safeguards from GitHub change approval to AWS deployment and database restoration into acceptance checks.
This exercise uses fictional evidence and makes no changes in a live environment.
Draw trust boundaries before choosing safeguards
A threat model records assets and boundaries, identifies possible failures and prioritizes mitigations.
- Change → DeployApprove changes
- Deploy → RetainLimit the action
- Retain → RestoreRetain evidence
- Change
- Review and approve
- Deploy
- Temporary role and approval
- Retain
- Backup location and access
- Restore
- Isolated validation environment
A fictional billing database
| Boundary | Requirement | Check |
|---|---|---|
| Change to deployment | Only approved changes proceed | Unapproved attempts fail |
| Deployment to AWS | Scope updates to intended resources | Unrelated changes fail |
| Backup to storage | Restrict object readers | Exercise a synthetic object |
| Restore to verification | Keep the source isolated from writes | Use a segregated synthetic database |
Set the expected success, expected denial and evidence for each safeguard.
Evidence for the decision
Draw the boundaries Associate data, actors, processing and control owners.
Turn controls into checks Define expected success, expected denial, reviewer and evidence.
Repeat when relevant assumptions change Revisit boundaries for new destinations or restoration options.
Check your decision
Choose an option to see the result and explanation.
Check, then explain in your own words
- Record assets and owners.
- Define a test for each mitigation.
- Revisit boundaries after changes.
Check your understanding: Does completing the diagram finish acceptance?
Collect evidence from representative allowed and denied operations.
A diagram organizes claims that still need testing.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
Scope and conditionsIdentifying boundaries and prioritizing mitigations.
Used in this lessonDraw trust boundaries before choosing safeguards A fictional billing database Evidence for the decision