The situation
The organization is a civic-tech-adjacent human-rights NGO that supports whistleblowers reporting corporate misconduct across 14 jurisdictions, operating with a lean staff of about 35 and a single part-time security engineer.
Your task
Design a defensible, hardened anonymous-intake architecture for the NGO and chart a realistic phased migration, grounded in an honest threat model of the system it replaces.
The brief
What you do
- Using the current-stack dossier and the CTO mandate brief, build a threat model of the existing intake using the LINDDUN privacy-threat framework (linkability, identifiability, non-repudiation, detectability, disclosure of information, unawareness of consequences, and non-compliance) as defined in the LINDDUN methodology source, and state each attacker's capabilities explicitly: a network observer, a compromise of the hosted server, a compromise of the source's own device, and a malicious or coerced recipient inside the NGO.
- Evaluate three alternatives against that same threat list — SecureDrop, a Briar-style peer-to-peer mesh, and OnionShare ephemeral links — citing the official documentation provided for each.
- Recommend a target architecture and a three-phase migration that respects the NGO's small operations team and the legal-review windows described in the CTO mandate brief.
- A successful proposal scores every option against the same threats, names the threats none of the candidates fully mitigate, and justifies its recommendation on fit, feasibility, and clarity rather than novelty.
What you will practice
- Apply the LINDDUN privacy-threat framework to a real anonymous-communication system with explicitly modeled attackers
- Compare anonymity-preserving architectures on equal footing using a shared threat list and primary documentation
- Distinguish threats that an architecture eliminates from those it only reduces, and communicate residual risk honestly
- Translate a security recommendation into a migration plan constrained by a small team's operational and legal realities
- Write security findings in plain language a non-technical board can act on
A suggested way in
- Use LINDDUN to structure threat elicitation and map each threat to one or more of the four named attacker capabilities
- Score alternatives with a consistent rubric (e.g., mitigates / partially mitigates / does not address) so the matrix is comparable across candidates
- Borrow risk-classification practice (likelihood × impact) to rank threats rather than treating them as a flat list
- Sequence the migration so the highest-risk, lowest-effort hardening lands first and legal review is never the blocking path
Skills you will practice
Anonymous communication, Threat modeling, Tor, Privacy engineering, Risk classification, Privacy budget
Where it leads
Security Engineer, Privacy Engineer, Security Architect
How it is assessed
- Threat-model rigor30%
All seven LINDDUN categories are applied to the current-stack dossier with each threat tied to one or more of the four explicitly defined attacker capabilities.
- Alternative comparison25%
SecureDrop, the Briar-style mesh, and OnionShare ephemeral links are each scored against the same threat list with citations to the provided official documentation.
- Recommendation honesty25%
The 6-page memo names the threats none of the candidates fully mitigate and proposes compensating controls rather than overstating protection.
- Migration realism20%
The 3-phase plan respects the staffing and legal-review windows stated in the CTO mandate brief and assigns owners and checkpoints.
Resources
- NotionTool
Structures the threat model, recommendation memo, and residual-risk register as linked, reviewable documents.
- MiroTool
Diagrams the current and proposed architectures and visualizes attacker reach across trust boundaries.
- Google SheetsTool
Builds the threat-by-candidate comparison matrix and the likelihood-impact risk scoring.
- JiraTool
Sequences the phased migration into owned, scheduled work items with legal-review gates.
Finish it. Earn this.
A verified certificate with your name. Anyone can check it.
Time to practice.
Solve this challengeMore like this.
- Software EngineerGreedy Delivery-Slot Assignment for a Munich Grocery Startup
- Software EngineerDesign a Verified UART Receiver and Loopback for an FPGA Sensor Hub
- Data ArchitectDesigning a Data Warehouse for a Renewable Energy Firm
- Database AdministratorCut a 42-Minute Trino Query to Under Five Minutes
-
Greedy Delivery-Slot Assignment for a Munich Grocery Startup Software Engineer Using the provided order history sample, rider roster, and manual dispatch baseline, design and implement a greedy slot-assignment algorithm in Python greedy algorithmsalgorithm analysispython Open challenge → -
Design a Verified UART Receiver and Loopback for an FPGA Sensor Hub Software Engineer Propose and deliver a UART receiver for Helax's sensor hub that meets the functional requirements in the requirements brief (the 'uart-requirements-br veriloguartfpga Open challenge → -
Designing a Data Warehouse for a Renewable Energy Firm Data Architect You are given sample data from three sources: energy production logs, weather data, and equipment maintenance records. Your task is to: (1) design a s data warehousingstar schemaetl Open challenge → -
Cut a 42-Minute Trino Query to Under Five Minutes Database Administrator Using the slow query, the EXPLAIN ANALYZE readout, the Iceberg table schemas, and the 30-day execution-metrics dataset provided, design an optimizatio trinosql optimizationiceberg Open challenge →