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

Preserve AWS and SQL Server forensic evidence for handoff

Track acquisition time and hashes while separating originals from working copies. Correlate cloud audit and SQL Server records in the same incident.

What you will learn

Correlate cloud audit and SQL Server records in the same incident.

Prerequisite

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

Record the chain of custody

Preserve relevant logs in an authorized boundary. Distinguish event time from acquisition time and work from verified copies.

From acquisition to investigation
From acquisition to investigation1: Acquire — Record custody — Keep. 2: Keep — Compare integrity — Copy. 3: Copy — Log access — Analyze123AcquireKeepCopyAnalyzeFrom acquisition to investigation1: Acquire — Record custody — Keep. 2: Keep — Compare integrity — Copy. 3: Copy — Log access — Analyze123AcquireKeepCopyAnalyze
  1. Acquire → KeepRecord custody
  2. Keep → CopyCompare integrity
  3. Copy → AnalyzeLog access
Acquire
Record collector and time
Keep
Restrict and retain the original
Copy
Verify SHA-256
Analyze
Align event timelines

A synthetic time-zone discrepancy

An AWS audit event precedes review of a database change. SQL Server records use Japan time, and the cloud audit uses UTC.
SourceTime or resultUse
AWS audit01:04 UTCEvent time
SQL Server audit10:04 JSTThe same minute
Collection02:00 UTCAcquisition time
Working copyMatching hashRecord analysis and handoff

Keep the original zones and acquisition time alongside any normalized timestamps.

Evidence for the decision

Protect the original Record scope, purpose, storage, readers and the accountable collector.

Verify integrity Match hashes at acquisition and transfer, then use a restricted working copy.

Align clocks Record the original zone, converted time and any uncertainty.

Check your decision

Choose an option to see the result and explanation.

What is the relationship between 01:04 UTC and 10:04 JST?
Read the answer and reason

Answer: They are the same minute, so compare identifiers next · JST is UTC+9.

Does a matching hash prove provenance by itself?
Read the answer and reason

Answer: Keep source, time and handoff records too · Bytes and provenance have separate evidence.

Where do you analyze evidence?
Read the answer and reason

Answer: Restricted and verified working copy · Keep the original unchanged.

Check, then explain in your own words

  1. Protect the original.
  2. Verify the copy.
  3. Reconcile normalized times and IDs.
Check your understanding: Does the same minute establish a single caller?

Compare run and session IDs, resources and precise time.

Time alone cannot establish cause.

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.