Skip to content

Commit

Permalink
Update threat-modeling.md
Browse files Browse the repository at this point in the history
  • Loading branch information
glenn-sorrentino committed Oct 1, 2023
1 parent bf6e0db commit fba6da1
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions src/prereqs/threat-modeling.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,22 +8,22 @@ If you need a tip line and it's a relatively low-risk scenario, we recommend mak

A real example is Investigative Data, whose official URL is investigativedata.io with Hush Line reachable at hello.investigativedata.org.

πŸ’Ό Small to medium businesses
🏫 Schoolhouses
πŸ’Ό Small to medium businesses<br>
🏫 Schoolhouses<br>
🎈 Conference organizers

## Medium Threats

Medium threats include higher priority scenarios but might not be at the level of requiring advanced censorship circumvention techniques. In this case, you might want to deploy to a public domain. Since every deployment includes an onion address, you'll always have the option for higher-risk scenarios like public companies or government contractors.

πŸ“ˆ Publicly traded businesses
🩺 Law or doctor's offices
πŸ“ˆ Publicly traded businesses<br>
🩺 Law or doctor's offices<br>
🚨 Domestic abuse hotlines

## High Threats

High threats are where someone's physical safety can be in danger. Consider a whistleblower leaking evidence of nation-state abuses or a journalist dedicated to reporting on corruption in authoritarian governments. For these cases, we recommend using a Tor-only deployment. Rather than a VPS, someone may wish to deploy to a physical device they possess, like a Raspberry Pi.

πŸ“° Journalists
πŸ†˜ Government whistleblowers
πŸ“° Journalists<br>
πŸ†˜ Government whistleblowers<br>
πŸš” Locations with internet censorship

0 comments on commit fba6da1

Please sign in to comment.