Domain Trust Architecture

You will be able to

• Define domain trust generically, and name its four surfaces
• Draw the dependency graph and say what each control leaves open
• Sequence a programme, and identify what genuinely cannot be parallelised
• Run a repeatable estate assessment and capture the evidence for each finding
• State the limits of any scoring scheme, including your own
• Rank work by impact against effort without pretending either is precise
• Make the case to a budget holder without scare tactics, and handle a no

Syllabus

1. 1. What Domain Trust Means

   A definition that does not depend on any product, and the four surfaces it covers.

   1. A definition worth using10 min
   2. The four surfaces11 min

2. 2. The Controls as One System

   Where each control sits, what it leaves open, and what depends on what.

   1. Where each control sits12 min
   2. The dependency graph11 min
   3. What each one leaves open11 min

3. 3. Order of Operations

   What has to come first, what can run in parallel, and what to do with no budget.

   1. What must come first12 min
   2. What to do with no budget11 min

4. 4. Assessing an Estate

   A method you can run by hand, the evidence to capture, and what a score cannot say.

   1. A method you can run by hand13 min
   2. Evidence per finding10 min
   3. What a score cannot say11 min

5. 5. Prioritising

   Impact against effort honestly, the nearly-free controls, and the ones worth skipping.

   1. Impact against effort, honestly11 min
   2. The ones worth skipping10 min

6. 6. Sustaining It

   What decays and how fast, handover that survives, and making the case for the work.

   1. What decays, and how fast11 min
   2. Handover that survives10 min
   3. Making the case11 min

7. 7. Final assessment

   15 scenario questions · 80% to pass · unlimited retakes

   What the assessment covers