WEBVTT

00:00:00.030 --> 00:00:04.605 position:50% align:center size:88%
Let’s connect control evidence, framework
coverage and a recorded fix.

00:00:04.655 --> 00:00:07.155 position:50% align:center size:88%
We’ll keep the dates and scope of each
check visible.

00:00:07.635 --> 00:00:11.685 position:50% align:center size:88%
This is the change from the paired fix and
rollback demonstration.

00:00:11.760 --> 00:00:15.810 position:50% align:center size:88%
Its history records the forward action and
its verification.

00:00:15.860 --> 00:00:19.785 position:50% align:center size:88%
The controlled rollback is recorded
separately on the same change.

00:00:19.835 --> 00:00:23.435 position:50% align:center size:88%
We are reviewing that evidence, not
running another fix.

00:00:23.510 --> 00:00:26.857 position:50% align:center size:88%
Open the linked incident to follow its
control context.

00:00:28.760 --> 00:00:32.635 position:50% align:center size:88%
The incident is linked to control E S T
zero three.

00:00:32.685 --> 00:00:36.985 position:50% align:center size:88%
The control detected an open remote-access
rule on the trial group.

00:00:37.060 --> 00:00:41.135 position:50% align:center size:88%
Changes that triggered this check links
the original cloud write.

00:00:41.210 --> 00:00:44.435 position:50% align:center size:88%
Open that recorded event to inspect the
connection.

00:00:44.510 --> 00:00:48.515 position:50% align:center size:88%
A matched change prompted the probe; the
probe established failure.

00:00:50.200 --> 00:00:53.425 position:50% align:center size:88%
This event was captured from the cloud
audit log.

00:00:53.500 --> 00:00:57.575 position:50% align:center size:88%
Its linked control result records what the
targeted probe found.

00:00:57.675 --> 00:01:01.425 position:50% align:center size:88%
Supported change rules recheck the
affected platform control.

00:01:01.475 --> 00:01:04.300 position:50% align:center size:88%
They do not run every framework
requirement.

00:01:04.400 --> 00:01:08.312 position:50% align:center size:88%
Now open Audit and coverage to compare
that narrower evidence.

00:01:10.120 --> 00:01:12.670 position:50% align:center size:88%
Switch between the two framework
catalogues.

00:01:12.720 --> 00:01:16.845 position:50% align:center size:88%
The page distinguishes automated checks
from human attestations.

00:01:16.945 --> 00:01:19.520 position:50% align:center size:88%
Unknown evidence remains unknown.

00:01:19.595 --> 00:01:23.820 position:50% align:center size:88%
These mappings are an interpretation for
review by the security team.

00:01:23.895 --> 00:01:26.760 position:50% align:center size:88%
A passing scan is not a compliance
certificate.

00:01:28.640 --> 00:01:31.790 position:50% align:center size:88%
Open the saved scan from September
twenty-eighth.

00:01:31.865 --> 00:01:34.815 position:50% align:center size:88%
Then open the network security control
result.

00:01:34.915 --> 00:01:37.840 position:50% align:center size:88%
This is the evidence from that original
scan.

00:01:37.915 --> 00:01:41.290 position:50% align:center size:88%
A later targeted check has its own date
and scope.

00:01:41.365 --> 00:01:44.533 position:50% align:center size:88%
Do not present the saved scan as a fresh
full assessment.

00:01:46.360 --> 00:01:49.160 position:50% align:center size:88%
Read the card for checks triggered by a
change.

00:01:49.235 --> 00:01:53.785 position:50% align:center size:88%
It distinguishes matched writes, repeated
probes and opened incidents.

00:01:53.860 --> 00:01:57.335 position:50% align:center size:88%
The fix followed the change hub in the
paired demonstration.

00:01:57.410 --> 00:02:01.460 position:50% align:center size:88%
That action and its verification stay in
their own recorded history.

00:02:01.585 --> 00:02:05.901 position:50% align:center size:88%
Scanner clearance, platform checks and
framework coverage are distinct.