INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Turn safeguards from GitHub change approval to AWS deployment and database restoration into acceptance checks.

Prerequisite

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.

Deployment and data operations
Deployment and data operations1: Change — Approve changes — Deploy. 2: Deploy — Limit the action — Retain. 3: Retain — Retain evidence — Restore123ChangeDeployRetainRestoreDeployment and data operations1: Change — Approve changes — Deploy. 2: Deploy — Limit the action — Retain. 3: Retain — Retain evidence — Restore123ChangeDeployRetainRestore
  1. Change → DeployApprove changes
  2. Deploy → RetainLimit the action
  3. 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

Deployment and restoration have different owners. Audit continues during recovery.
BoundaryRequirementCheck
Change to deploymentOnly approved changes proceedUnapproved attempts fail
Deployment to AWSScope updates to intended resourcesUnrelated changes fail
Backup to storageRestrict object readersExercise a synthetic object
Restore to verificationKeep the source isolated from writesUse 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.

What should the diagram name first?
Read the answer and reason

Answer: Assets, principals and trust boundaries · Start with the intersection of operations and access.

What should happen to an unapproved release attempt?
Read the answer and reason

Answer: It is denied and recorded · Protect the deployment boundary.

What happens when you add a destination?
Read the answer and reason

Answer: Update the scope and related checks · Boundaries and responsibilities may change.

Check, then explain in your own words

  1. Record assets and owners.
  2. Define a test for each mitigation.
  3. 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.