WEBVTT

00:00:00.400 --> 00:00:05.288
This lesson builds a reviewable migration plan without executing changes.

00:00:05.568 --> 00:00:06.404
Step one.

00:00:06.684 --> 00:00:08.112
Open Dependencies.

00:00:08.392 --> 00:00:13.848
Inspect observed, user-confirmed and inferred relationship labels and confidence.

00:00:14.128 --> 00:00:19.968
The graph displays supplied edges; it is not measured discovery and may be incomplete.

00:00:21.067 --> 00:00:21.926
Step two.

00:00:22.206 --> 00:00:23.356
Open Migration.

00:00:23.636 --> 00:00:30.567
Select the synthetic signing HSM and choose ML-DSA as an illustrative signature planning target.

00:00:30.847 --> 00:00:37.569
ML-KEM is for key establishment, not signatures; AES is a symmetric cipher.

00:00:37.849 --> 00:00:41.669
A menu choice is not proof of vendor compatibility.

00:00:42.800 --> 00:00:43.729
Step three.

00:00:44.009 --> 00:00:46.540
Select Generate planning package.

00:00:46.820 --> 00:00:53.890
Read affected services, prerequisites, evidence gaps, validation, rollback and residual risk.

00:00:54.170 --> 00:00:56.237
Execution remains false.

00:00:56.517 --> 00:01:03.436
The model is a dependency-based planning aid, not a measured digital simulation or change authorization.

00:01:04.533 --> 00:01:05.473
Step four.

00:01:05.753 --> 00:01:09.933
Open a finding and select Create remediation package.

00:01:10.213 --> 00:01:15.403
The package keeps the finding's rationale and evidence with a proposed target state.

00:01:15.683 --> 00:01:22.742
This action creates a review record only; no key, HSM or application is changed.

00:01:23.867 --> 00:01:24.877
Step five.

00:01:25.157 --> 00:01:27.827
Return to Migration and load packages.

00:01:28.107 --> 00:01:32.449
Assign the responsible team, select In review and save.

00:01:32.729 --> 00:01:34.575
Analysts cannot approve.

00:01:34.855 --> 00:01:44.840
An administrator may select Approved only after reviewing the package; this approval covers the plan, not
operational execution or risk acceptance.

00:01:45.933 --> 00:01:47.024
Step six.

00:01:47.304 --> 00:01:50.857
Confirm the stored Approved state for this synthetic example.

00:01:51.137 --> 00:02:00.669
Before real change work, obtain separate change authority, exact-version documentation, compatibility tests and
operator-owned rollback.

00:02:00.949 --> 00:02:03.631
Sentinel does not perform those changes.

00:02:04.733 --> 00:02:05.685
Step seven.

00:02:05.965 --> 00:02:12.432
With two comparable snapshots loaded, choose a baseline and select Compare snapshot drift.

00:02:12.712 --> 00:02:16.590
Inspect added, removed and changed metadata fields.

00:02:16.870 --> 00:02:19.435
This example changes a synthetic owner.

00:02:19.715 --> 00:02:24.731
Differences are between supplied snapshots, not observed live-device drift.