Chapter 46 — Engineering capstone II | Engineering Identity and access management

Open, free learning for anyone who wants to protect people and technology. No account is required to read this text or its worked answers.

Chapter 46 — Engineering capstone II

Lesson map

Lesson 46 published. Map, example, EX136.

flowchart TD
  N0["Learning outcomes"]
  N1["46.1 Completing migrations"]
  N2["46.2 Measuring outcomes"]
  N3["46.3 Interim controls"]
  N4["46.4 Handover"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5
  N5 --> EX["Worked example"]
  EX --> Q["Exercise EX136"]

Logical drawing

flowchart LR
  N0["Learning outcomes"]
  N1["46.1 Completing migrations"]
  N2["46.2 Measuring outcomes"]
  N3["46.3 Interim controls"]
  N4["46.4 Handover"]
  N5["Synthesis"]
  N0 --> N1 --> N2 --> N3 --> N4 --> N5 --> Q["EX136"]

[Learning outcomes]
    |
    v
[46.1 Completing migrations]
    |
    v
[46.2 Measuring outcomes]
    |
    v
[46.3 Interim controls]
    |
    v
[46.4 Handover]
    |
    v
[Synthesis]
    |
    v
[Worked example] --> [Exercise EX136]

Learning outcomes

You will (1) complete capstone delivery; (2) verify and measure outcomes; (3) hand over remaining work.

46.1 Completing migrations

Sana completes the capstone migrations in small groups, each with report-only checks first, a defined rollback and verification afterwards. By the end, thirteen of the twenty applications are under the provider with automated leaver removal, one more than the target. Each migration's evidence includes test results, the configuration version and a sample of leaver removals measured after go-live. Staff for each application receive notices beforehand and a contact for problems, following the communication pattern from earlier rollouts. Each completion is confirmed with the owner.

46.2 Measuring outcomes

Sana measures outcomes for the capstone applications: median leaver removal time falls from about a week under the old manual process to under two hours; the number of accounts with no matching employee in these applications drops from 47 to 2, both explained by pending HR corrections; and password tickets for these applications fall noticeably. She reports results with baselines, sample sizes and limits, such as the short measurement period for the last applications migrated. Measurement continues after handover, now run by the identity team.

46.3 Interim controls

The seven applications not migrated have documented interim controls: scripted daily checks against HR, alerts on mismatches, monthly owner sign-off and a planned date for migration or retirement. Sana tests that the scripted checks actually detect a synthetic leaver and that alerts reach the identity team. Interim controls are recorded in the residual risk register with owners. This ensures that applications outside the main design are still governed rather than silently forgotten once the project's attention moves on. Each control is reviewed monthly by its owner.

46.4 Handover

Sana hands over the capstone to the identity team with updated documentation, runbooks for proxies and new connectors, the test suite and evidence. She walks through each migrated application with the team lead and agrees who owns the remaining interim applications. A short handover checklist confirms that monitoring, alerts and access reviews cover the new integrations. The council's acceptance of the handover is recorded, closing the capstone formally and providing a clear end point for the thesis. Open questions are listed with owners.

Worked example

Thirteen of twenty applications are migrated, one above target; median leaver removal falls from about a week to under two hours and ownerless accounts from 47 to 2; seven applications remain on tested interim controls.

Synthetic case. Applications, counts and times are synthetic.

Errors and limits

Declaring success at go-live without measuring leaver removal afterwards leaves the main requirement unverified.

Exercises

EX136 — Migrated count. How many applications were migrated in the capstone? Rubric: 3 = thirteen of twenty, one above target;; 2 = thirteen;; 1 = twelve;; 0 = none.
EX137 — Ownerless accounts change. How did ownerless accounts change in capstone applications? Rubric: 3 = 47 to 2, both pending HR corrections;; 2 = 47 to 2;; 1 = vague;; 0 = none.
EX138 — Interim test. How are interim scripted checks verified? Rubric: 3 = a synthetic leaver is detected and alerts reach the team;; 2 = synthetic test;; 1 = assumed;; 0 = none.

Synthesis

Careful migration, measured outcomes, tested interim controls and a formal handover complete the capstone.

Continue studying — chapter 46 of 50

← Chapter 45 (draft) · Course chapter index · Chapter 47 (draft) →