WEBVTT

00:00:00.030 --> 00:00:04.605 position:50% align:center size:88%
Let’s review an isolated AWS fix and its
later rollback.

00:00:04.655 --> 00:00:07.539 position:50% align:center size:88%
We’ll read the saved evidence without
changing the cloud.

00:00:08.019 --> 00:00:11.369 position:50% align:center size:88%
This trial change was executed on October
eighth.

00:00:11.444 --> 00:00:13.869 position:50% align:center size:88%
Its current status is rolled back.

00:00:13.944 --> 00:00:18.694 position:50% align:center size:88%
The target was a temporary security group
with no attached network interfaces.

00:00:18.744 --> 00:00:21.269 position:50% align:center size:88%
The original cleanup removed that group.

00:00:21.344 --> 00:00:23.785 position:50% align:center size:88%
This review follows the recorded evidence.

00:00:25.720 --> 00:00:28.045 position:50% align:center size:88%
Read the forward verification record.

00:00:28.095 --> 00:00:32.070 position:50% align:center size:88%
The execution receipt records removal of
one ingress rule.

00:00:32.120 --> 00:00:35.470 position:50% align:center size:88%
The control recheck then recorded a
cleared result.

00:00:35.545 --> 00:00:39.120 position:50% align:center size:88%
That check belongs to the forward fix,
before rollback.

00:00:39.195 --> 00:00:41.976 position:50% align:center size:88%
It is not a fresh assessment of a running
resource.

00:00:43.880 --> 00:00:47.180 position:50% align:center size:88%
Read What ran to inspect the approved
operation.

00:00:47.255 --> 00:00:51.705 position:50% align:center size:88%
It removed one remote-access ingress
permission from the trial group.

00:00:51.780 --> 00:00:55.580 position:50% align:center size:88%
The recorded connection and resource
identity are masked here.

00:00:55.630 --> 00:00:58.963 position:50% align:center size:88%
The approval and execution applied to that
specific change.

00:01:00.680 --> 00:01:03.805 position:50% align:center size:88%
Open the snapshot artifact from the Safety
net.

00:01:03.880 --> 00:01:07.055 position:50% align:center size:88%
It preserves the state captured before the
forward write.

00:01:07.130 --> 00:01:10.555 position:50% align:center size:88%
That permission was deliberately
introduced for the trial.

00:01:10.630 --> 00:01:15.405 position:50% align:center size:88%
A captured configuration is not
automatically a safe configuration.

00:01:15.480 --> 00:01:18.963 position:50% align:center size:88%
Return to the same change to read its
restoration result.

00:01:20.600 --> 00:01:24.900 position:50% align:center size:88%
The change retains the compiled rollback
and its restoration check.

00:01:24.975 --> 00:01:27.625 position:50% align:center size:88%
The recorded pre-change state was
restored.

00:01:27.700 --> 00:01:31.000 position:50% align:center size:88%
That restored permission was still the
trial exposure.

00:01:31.050 --> 00:01:35.800 position:50% align:center size:88%
The original cleanup then removed both the
rule and the unattached group.

00:01:35.875 --> 00:01:38.861 position:50% align:center size:88%
This review performs no new fix or
rollback.

00:01:40.760 --> 00:01:44.110 position:50% align:center size:88%
Open the linked incident and its
Validation section.

00:01:44.185 --> 00:01:46.835 position:50% align:center size:88%
Keep each verdict beside its check time.

00:01:46.910 --> 00:01:51.235 position:50% align:center size:88%
The recorded forward fix, rollback and
cleanup have separate meanings.

00:01:51.310 --> 00:01:54.960 position:50% align:center size:88%
An execution response alone is not proof
of recovery.

00:01:55.035 --> 00:01:58.360 position:50% align:center size:88%
The retained history lets an operator
review what happened.