Security
Security Architecture
Future Impact Lab is designed to host sensitive strategic foresight cases — including institutional, defense-adjacent, and ministry-level scenarios. Our security architecture reflects that responsibility.
Core principles
Compromise of infrastructure must not imply compromise of knowledge
Even if the server is breached, the database is dumped, or backups are stolen — an attacker should obtain ciphertext and metadata, not readable case content. Sensitive knowledge is protected independently of infrastructure security.
Keys belong to policy roles, not administrators
No single person holds unilateral access to sensitive case content. Access is policy-mediated, role-based, auditable, and revocable. Custody roles — not admin accounts — govern decryption.
Per-case compartmentalization
Each case operates under its own encryption context and custody policy. Compromise of one case does not compromise others.
Security tiers
Tier A — FIL Managed
Public · CommunityFIL-managed encryption at rest. Audited access. Invisible to participants — standard sign-in and contribution flow.
Tier B — Shared Custody
Institutional PrivateKey custody split between FIL and the participating institution. Neither party can decrypt unilaterally. Dual authorization required for sensitive decryptions. Full audit trail. Default for institutional private cases.
Tier C — Quorum Unlock
Restricted · SealedField-level encryption with quorum unlock (multiple custodians required). Designed for defense, ministry-level, and highly sensitive cases. Cryptographic deletion supported. Tamper-evident audit.
Audit and accountability
All access to case content, key operations, and custody events is recorded in an append-only audit log. For Tier C cases, the audit log is cryptographically chained — entries cannot be modified or removed without detection.
Institutions participating in private cases receive access to their case audit trail on request.
Implementation status
The security architecture is designed and documented. Tier A implementation is planned for the next infrastructure sprint. Tier B and Tier C will be implemented as institutional clients engage. The architecture is designed to be upgraded without disrupting existing cases or participants.
Institutional Programs