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

AWS Config evaluations and remediation|Handle stale findings

Identify which conditions justify a change to the current resource. Use a stale report to distinguish compliance evaluation from execution.

What you will learn

Use a stale report to distinguish compliance evaluation from execution.

Prerequisite

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

Detect a stale snapshot

Config remediation works from evaluation data, which may lag current state. Consider a current-state check and idempotent remediation.

Reconcile evaluation, action and result
Reconcile evaluation, action and result1: Record — Find the delta — Reread. 2: Reread — Confirm authority — Repair. 3: Repair — Inspect outcome — Reevaluate123RecordRereadRepairReevaluateReconcile evaluation, action and result1: Record — Find the delta — Reread. 2: Reread — Confirm authority — Repair. 3: Repair — Inspect outcome — Reevaluate123RecordRereadRepairReevaluate
  1. Record → RereadFind the delta
  2. Reread → RepairConfirm authority
  3. Repair → ReevaluateInspect outcome
Record
Preserve evaluation time
Reread
Get the current value
Repair
Check scope and preconditions
Reevaluate
Verify compliance and behavior

A violation at 10:00 and a newer state

A fictional resource has inadequate retention. Another authorized operator applies the change first.
TimeObservationDecision
10:007 days is noncompliantRecord initial evaluation
10:03Updated to 30 daysApproved change by another operator
10:05Remediation scheduledVerify target and current value
10:0630 days and functionalNo change required

A change took place after evaluation, so use current state before remediating.

Evidence for the decision

Record both clocks Keep the evaluation and operation times in the record.

Check execution preconditions Verify the target is in authorized scope and still needs remediation.

Prepare for repeats Receiving the same request twice should preserve a compliant value and expected function.

Check your decision

Choose an option to see the result and explanation.

The last evaluation was at 10:00 and it is now 10:05. What first?
Read the answer and reason

Answer: Read the current target value · The resource could have changed afterward.

Remediation reports success. What follows?
Read the answer and reason

Answer: Obtain a new evaluation and test function · Verify both function and compliance.

The value is already 30 days. What next?
Read the answer and reason

Answer: Record that no change is required · The purpose is to reach and preserve compliance.

Check, then explain in your own words

  1. Compare current state with the finding.
  2. Verify execution preconditions.
  3. Check the updated evaluation and behavior.
Check your understanding: Should every finding trigger the same remediation immediately?

Check scope, current state, authority and side effects first.

Compliance assessment and changes have different preconditions.

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.