Domain-Specific Security Case Studies
Stub. How generic security engineering principles play out in specific high-stakes verticals: banking and bookkeeping (double-entry accounting as a security control), nuclear command and control (extreme, physically-enforced multi-party authorization), electronic and information warfare and cyberwar, telecom system security, healthcare security/privacy, and the harder-to-formalize terror/justice/freedom tradeoffs.
Security requirements and threat models aren’t generic — they’re shaped by the specific stakes and adversary of a domain, and this note is a survey of how differently that plays out across verticals. Banking treats double-entry bookkeeping itself as a centuries-old security control (an error or fraud has to violate the ledger’s own internal consistency to go undetected). Nuclear command and control is the extreme case of multi-party authorization enforced physically (permissive action links) rather than just procedurally. Electronic/information warfare and cyberwar extend the adversary model to nation-states operating below the threshold of open conflict; telecom system security and healthcare security/privacy are regulated critical-infrastructure domains with their own compliance regimes; and terror/justice/freedom covers the genuinely political tradeoffs (surveillance powers, encryption backdoors) that don’t reduce to a clean technical answer. See incentives-and-information-security for the economic-incentive lens on why these domains’ security so often fails for non-technical reasons.
Outline (TODO — flesh out each)
- Banking and bookkeeping
- Nuclear command and control
- Electronic and information warfare; cyberwar
- Telecom system security
- Healthcare security and privacy
- Terror, justice, and freedom — the policy tradeoffs