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 Security Hub findings and verify resolution

Group related findings without losing their original identifiers. Draw the boundary between workflow status and evidence that the underlying issue was fixed.

What you will learn

Draw the boundary between workflow status and evidence that the underlying issue was fixed.

Prerequisite

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

Manage findings after aggregation

Security Hub CSPM workflow status captures investigation progress. Compare resource, source, control and time before assigning work.

From separate findings to verified remediation
From separate findings to verified remediation1: Intake — Match evidence — Group. 2: Group — Assess impact — Assign. 3: Assign — Update status — Verify123IntakeGroupAssignVerifyFrom separate findings to verified remediation1: Intake — Match evidence — Group. 2: Group — Assess impact — Assign. 3: Assign — Update status — Verify123IntakeGroupAssignVerify
  1. Intake → GroupMatch evidence
  2. Group → AssignAssess impact
  3. Assign → VerifyUpdate status
Intake
Record source and IDs
Group
Compare targets and rules
Assign
Name owner and deadline
Verify
Exercise the original requirement

Classify three synthetic findings

Resource a has F1 and F2. Resource b has F3.
RecordInformationDecision
F1Retention on resource aAssign owner A
F2Same resource and requirement from another sourceLink to F1
F3Public exposure check on resource bAssign separately
After remediationFunctional test and new evaluationEvidence for changing status

Retain original finding IDs so a reviewer can reconcile follow-up evaluations.

Evidence for the decision

Read the status meaning Keep the workflow phase distinct from evidence collected after remediation.

Document grouping criteria Match the resource and requirement, then preserve each record ID.

Monitor recurrence Compare conditions before and after remediation and recheck the original control.

Check your decision

Choose an option to see the result and explanation.

Can F1 and F2 always be grouped when they share a resource?
Read the answer and reason

Answer: Compare sources, requirements and resources · Their requirements must match as well.

What if you only change the status to resolved?
Read the answer and reason

Answer: Verify the changed configuration and evaluation · The correction still needs evidence.

Why assign F3 separately?
Read the answer and reason

Answer: A different resource and control · It describes a distinct issue.

Check, then explain in your own words

  1. Match resources and rules.
  2. Link related findings.
  3. Verify the correction before updating status.
Check your understanding: Does grouping findings replace the original evidence?

Retain the mappings to source IDs.

They are needed to verify the correction and investigate recurrence.

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.