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

Triage GuardDuty findings using severity and independent evidence

Read the target, detection type and time before making a decision. Distinguish evidence for priority from evidence of impact or compromise.

What you will learn

Distinguish evidence for priority from evidence of impact or compromise.

Prerequisite

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

Evidence after a detection

GuardDuty identifies a resource and finding type. Use severity as a triage signal, then reconcile audit and operational records.

Narrow the investigation
Narrow the investigation1: Notification — Record observations — Audit. 2: Audit — Validate with other sources — Operations. 3: Operations — Record next steps — Decision123NotificationAuditOperationsDecisionNarrow the investigation1: Notification — Record observations — Audit. 2: Audit — Validate with other sources — Operations. 3: Operations — Record next steps — Decision123NotificationAuditOperationsDecision
  1. Notification → AuditRecord observations
  2. Audit → OperationsValidate with other sources
  3. Operations → DecisionRecord next steps
Notification
Read target and type
Audit
Find corresponding events
Operations
Check approval and times
Decision
Assign accountable owner

A detection during a planned deployment

Several actions occur under a sandbox role. A workflow run exists at the same time.
SourceEvidenceDecision
FindingHigh priorityTriage promptly
Audit logCaller establishedCorrelate the workflow run
Change recordOnly reads approvedAn observed update is unexplained
DecisionEscalate unexplained updateDetermine its scope

Separate matched activity from actions still requiring investigation.

Evidence for the decision

Fix the identifiers Record finding ID, account, region and time.

Reconcile sources Align the approval, execution and audit records to the same time window.

Keep an uncertainty record Distinguish observations, hypotheses and further checks.

Check your decision

Choose an option to see the result and explanation.

How do you use high severity?
Read the answer and reason

Answer: To order triage · It helps prioritize review.

Only reads were approved, but an update appears. What now?
Read the answer and reason

Answer: Trace the update's principal and affected resources · Investigate the unexplained difference.

What ties multiple sources together?
Read the answer and reason

Answer: Resource, time, principal and IDs · Point to an identifiable occurrence.

Check, then explain in your own words

  1. Read the finding target.
  2. Reconcile audit and change records.
  3. Investigate unexplained actions.
Check your understanding: Can you close the case when the times match?

Check whether the actual operations were approved.

Other actions can occur in the same interval.

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.