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

Respond to a credential incident in GitHub Actions and AWS

Identify the affected delivery path and incident owner at intake. Plan containment, evidence preservation and acceptance for restored deployment.

What you will learn

Plan containment, evidence preservation and acceptance for restored deployment.

Prerequisite

This exercise uses fictional evidence and makes no changes in a live environment.

Record observations and changes separately

Incident response includes investigation, containment, eradication and recovery. Identify the affected deployment and decision makers before changing access.

Handle a synthetic incident
Handle a synthetic incident1: Intake — Identify the target — Evidence. 2: Evidence — Preserve and contain — Contain. 3: Contain — Verify recovery — Restore123IntakeEvidenceContainRestoreHandle a synthetic incident1: Intake — Identify the target — Evidence. 2: Evidence — Preserve and contain — Contain. 3: Contain — Verify recovery — Restore123IntakeEvidenceContainRestore
  1. Intake → EvidenceIdentify the target
  2. Evidence → ContainPreserve and contain
  3. Contain → RestoreVerify recovery
Intake
Identify the affected job
Evidence
Record run ID and audit time
Contain
Limit the intervention scope
Restore
Test a bounded path

A fictional credential handling incident

An output might have contained sensitive material. No secret values are inspected or retained.
StageDecisionEvidence
IntakeConfirm owner and scopeRun ID
Initial responseOwner decides whether to hold affected deploymentDecision time
ReviewCheck issued sessions and operationsAudit events
RecoveryExercise a constrained synthetic jobSuccess and denial

Keep identifiers and before-and-after state instead of copying secret values.

Evidence for the decision

Assign responsibility Name the decision makers for investigation, containment and recovery.

Avoid copying secret values Record only required identifiers and integrity information in a restricted evidence store.

Define a reopening gate Verify approved deployment, denied out-of-scope operations and no repeated anomaly.

Check your decision

Choose an option to see the result and explanation.

Should you send the logs externally first?
Read the answer and reason

Answer: Identify the owner, scope and run · Limit collected and shared information to what the investigation needs.

What do you investigate after holding deployment?
Read the answer and reason

Answer: Session and audit timeline · Check activity and already-issued authorization.

What establishes recovery?
Read the answer and reason

Answer: Approved deployment succeeds and prohibited actions fail · Verification still needs an authorization boundary.

Check, then explain in your own words

  1. Confirm target and owner.
  2. Preserve observations and timing.
  3. Test restricted recovery.
Check your understanding: Does stopping a workflow end all sessions already issued?

Investigate issued sessions, their expiration and approved containment options.

Workflow and credential lifecycle are distinct.

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.