Ewance
← All challenges Security Engineer

Threat-Model and Hardening Proposal for a Whistleblower Intake

Duration
2 weeks
Level
Advanced
Type
Design
Team
1 to 5 people

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

  1. 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.
  2. 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.
  3. 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.
  4. 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

  1. Use LINDDUN to structure threat elicitation and map each threat to one or more of the four named attacker capabilities
  2. Score alternatives with a consistent rubric (e.g., mitigates / partially mitigates / does not address) so the matrix is comparable across candidates
  3. Borrow risk-classification practice (likelihood × impact) to rank threats rather than treating them as a flat list
  4. 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.

Sample Ewance certificate of completion, verified by LearnCoin
Sample certificate
Your proof

Finish it. Earn this.

A verified certificate with your name. Anyone can check it.

Time to practice.

Solve this challenge
Related challenges

More like this.