By the end, you’ll be able to…
- Separate assets, threats and controls.
- Identify residual risk after a control is added.
Three questions to carry into this lesson.
Name what needs protection
A custody design protects more than a balance. It may also protect privacy, access to operating funds, continuity after illness and the ability to explain decisions. List the asset, authorized people and consequence of failure. Avoid starting with a favorite device and inventing reasons it solves every problem.
Model distinct failures
Theft, accidental deletion, coercion, unavailable signers, misleading interfaces and a provider outage require different responses. A control can reduce one threat while increasing another. For example, a demanding approval threshold may resist one compromised signer but make urgent recovery harder. Geographic separation can reduce a shared physical failure while complicating access and maintenance.
Make assumptions testable
For a fictional community treasury, write who can prepare, authorize, reconcile and pause operations. Record the evidence a second person needs to reproduce the result. A tabletop exercise should include a missing device, an unavailable provider and an unexplained payment request. No real secrets or transfers are needed. The useful outcome is a list of unresolved dependencies, not a declaration that the system is institution grade because it uses several tools.
Practice on paper
A team introduces a second approval but both approvers share one laptop and one recovery account. What risk remains?
I’ve tried it — show the worked answer
A compromise or loss of that shared environment can affect both approvals. The nominal number of people does not establish independent control. Review the shared device, credentials, recovery route and ability to refuse separately.
Want to explore with buttons and instant feedback? Try the practice lab ↗
Make a choice. Discover why.
Choose an answer and check the explanation. You can retry as often as you like. These are practice questions, not a test of mastery; answers are not saved or sent.
One idea to take with you
Start with failure stories, then choose controls with explicit limits.
Your learning, at your pace
Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.
Continue with your next unfinished lesson →
Remove the saved completion marks for this course on this browser? Other courses will stay unchanged.
Saved only in this browser for this website address. Clearing storage, changing device or using a different gateway may lose these marks. No sync, grading or credential; nothing is sent to us. The export is a record for you, not a file this site can import.