diff --git a/book/prereqs/threat-modeling.html b/book/prereqs/threat-modeling.html index 51dfd59..0390f4d 100644 --- a/book/prereqs/threat-modeling.html +++ b/book/prereqs/threat-modeling.html @@ -176,7 +176,7 @@
To select the right Hush Line deployment, consider the potential risks and consequences you or your tipsters might face:
-These scenarios typically involve situations where the primary risk is non-targeted threats or generic cyber threats. The fallout from a security breach is minimal.
We recommend using a VPS and deploying Hush Line as a public domain to a URL like this: tips.acme.com
.
Here, the risks escalate. They include targeted threats but might not require advanced defense measures.
We recommend using a VPS and deploying Hush Line as a public domain to a URL like this: tips.acme.com
. When sharing your Hush Line address, include the onion address for people that require higher levels of anonymity.
These are scenarios where targeted threats are likely, and consequences can be severe, like endangering someone's physical safety.
Depending on risks to your physical location, we recommend either using a VPS or local device like a Raspberry Pi and choosing an onion-only deployment. This will provide the greatest protection for your community and your tip line.
To select the right Hush Line deployment, consider the potential risks and consequences you or your tipsters might face:
-These scenarios typically involve situations where the primary risk is non-targeted threats or generic cyber threats. The fallout from a security breach is minimal.
We recommend using a VPS and deploying Hush Line as a public domain to a URL like this: tips.acme.com
.
Here, the risks escalate. They include targeted threats but might not require advanced defense measures.
We recommend using a VPS and deploying Hush Line as a public domain to a URL like this: tips.acme.com
. When sharing your Hush Line address, include the onion address for people that require higher levels of anonymity.
These are scenarios where targeted threats are likely, and consequences can be severe, like endangering someone's physical safety.
Depending on risks to your physical location, we recommend either using a VPS or local device like a Raspberry Pi and choosing an onion-only deployment. This will provide the greatest protection for your community and your tip line.