CCSI Officer course · Module 10 of 10
Capstone: secure design review
Apply the whole course to one scenario: review a confidential multi-party analytics and inference service, find the gaps, and produce the design review an officer would sign.
Learning objectives
- Run a structured design review of a confidential computing system
- Identify trust-boundary, attestation, key-release and operational gaps
- Write findings with severity, evidence and remediation
- Prepare for the proctored CCSI Officer assessment
Lessons
Lesson 10.1 · 10 min
The scenario
Two organisations want to pool data for fraud detection without revealing raw records to each other or to the operator.
Lesson 10.2 · 16 min
Reference design review
The findings an officer should raise, with severity and remediation.
Lesson 10.3 · 9 min
Officer checklist and the proctored assessment
A reusable review checklist, and how official certification works.
Check your understanding
Module 10 quiz
5 questions · pass mark 80%
1.In the scenario, why does using a confidential VM and GPU provide no protection from the operator as designed?
2.In a two-party design, who should control each dataset key?
3.Training logs containing sample rows are shipped to the operator. Which principle does this violate?
4.Where should a design review usually start?
5.What does completing this course's practice exam give you?
Glossary
- Design review
- A structured assessment of a system design against its security goals, producing findings and remediations.
- Finding
- A documented gap with severity, evidence and recommended remediation.
- Data clean room
- An environment where several parties combine data for agreed computations without seeing each other's raw data.