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.
Plan containment, evidence preservation and acceptance for restored deployment.
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.
- Intake → EvidenceIdentify the target
- Evidence → ContainPreserve and contain
- 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
| Stage | Decision | Evidence |
|---|---|---|
| Intake | Confirm owner and scope | Run ID |
| Initial response | Owner decides whether to hold affected deployment | Decision time |
| Review | Check issued sessions and operations | Audit events |
| Recovery | Exercise a constrained synthetic job | Success 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.
Check, then explain in your own words
- Confirm target and owner.
- Preserve observations and timing.
- 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.
- Incident responseChecked:
Scope and conditionsInvestigation, containment, eradication and recovery.
Used in this lessonRecord observations and changes separately A fictional credential handling incident Evidence for the decision