<p>In this tutorial we're going to cover how to properly segment your internet usage. This is the most common opsec practice that you should always use. We're going to base ourselves off from the pyramid of internet use that we have seen <ahref="../opsec4levels/index.html">previously</a>, to be able to replicate each of the 4 OPSEC levels into our current setup:</p>
<imgsrc="../opsec4levels/0.3.png"class="imgRz">
</div>
</div><!-- /row -->
</div><!-- /container -->
</div><!-- /grey -->
<!-- +++++ Second Post +++++ -->
<divid="anon3">
<divclass="container">
<divclass="row">
<divclass="col-lg-8 col-lg-offset-2">
<h2><b>Different Internet Usage </b></h2>
<p>The most common OPSEC mistake out there is the lack of internet usage segmentation. Most people don't have this reflex when they first discover Anonymity and Privacy online. Thing is, <b>it is not possible to be fully anonymous for everything that you do online</b>, there will always be some service that is vital to you, which you will need to access with your real world identity (for example, to access your bank account, or some insurance website, etc). However it is definitely possible to implement proper internet usage segmentation:</p>
<p>In this case we're going to differentiate 4 types of Internet usage:</p>
<imgsrc="2.png"class="imgRz">
<p><u>Internet Uses:</u></p>
<ol>
<li><p><u>Public use</u>: What you do is public knowledge</p></li>
<li><p><u>Private use</u>: What you do is not meant to be known (private)</p></li>
<li><p><u>Anonymous use</u>: What you do is meant to be done without revealing your identity</p></li>
<li><p><u>Sensitive use</u>: What you do is meant to remain secret at all cost, only to be known by you</p></li>
</ol>
<p>With each different Internet usage, we have different requirements:</p>
<imgsrc="3.png"class="imgRz">
<p><u>Requirements:</u></p>
<ol>
<li><p><u>Public use</u>: No requirement ; you can use closed source software (meaning it's all public)</p></li>
<li><p><u>Private use</u>: only open source software, + you use a pseudonym, to practice privacy</p></li>
<li><p><u>Anonymous use</u>: open source, using a false identity to practice anonymity, not sensitive</p></li>
<li><p><u>Sensitive use</u>: open source, using an other false identity and must be plausibly deniable</p></li>
</ol>
<p>Now with this we identified the 4 most typical internet use cases, and their requirements.</p>
</div>
</div><!-- /row -->
</div><!-- /container -->
</div><!-- /white -->
<divid="anon2">
<divclass="container">
<divclass="row">
<divclass="col-lg-8 col-lg-offset-2">
<h2><b>Identity Management</b></h2></br></br>
<p>As we said previously, segmentation is required for each internet use. This extends to the Identity you use online. For example you cannot use your real name when trying to use the internet anonymously. So you need a different identity for each use case: </p>
<imgsrc="4.png"class="imgRz">
<p><u>Different Identities:</u></p>
<ol>
<li><p><u>Public Identity</u>: <b>Linus Torvalds</b> (used on websites that ask for your identity) </p></li>
<li><p><u>Private Identity</u>: <b>Nihilist</b> (used on websites that may KYC, but pseudonym is preferred)</p></li>
<li><p><u>Anonymous Identity</u>: <b>ZacharyJr</b> (used on anonymous websites, non-sensitive use)</p></li>
<p>The important thing here is that you must make sure that each identity have nothing in common, <b>it must always remain impossible for and adversary to be able to link those identities together. </b></p>
<p>To help you implement your internet usage segmentation, you can use VMs to make sure the segmentation is present inside the system:</p>
<imgsrc="5.png"class="imgRz">
<p><u>Virtual Machines:</u></p>
<ol>
<li><p><u>Public use</u>: No requirement ; you can use a windows VM for all closed source software and KYC use</p></li>
<li><p><u>Private use</u>: you can use a Debian VM, with only open source software (ex:matrix and element)</p></li>
<li><p><u>Anonymous use</u>: you can use Whonix VMs, (can also have a with a Tor -> VPN setup) </p></li>
<li><p><u>Sensitive use</u>: You can use Whonix VMs, but they need to be inside a <ahref="../anonymity/index.html">veracrypt hidden volume</a></p></li>
<p><u>Sidenote:</u><ahref="https://www.qubes-os.org/">QubesOS</a> is based off the same segmentation principle, that every use must remain isolated (or compartmentalized) into VMs, for specific uses. It also uses Linux and Whonix VMs, while using the Xen hypervisor instead of libvirtd QEMU/KVM, but the concept remains the same. </p>
<p>Now with this setup, one can segment their Internet use with a system implementation (VMs) along with the associated Identities for each usecase.</p>
<imgsrc="6.png"class="imgRz">
<p>For further details on how to dissect your OPSEC, check out this tutorial <ahref="../opsec/index.html">here</a>, because using the right technologies is only the first half of the work, you also need to have the correct behavior while using them.</p>
Until there is Nothing left.</p></br></br><p>Creative Commons Zero: <ahref="../../../../opsec/runtheblog/index.html">No Rights Reserved</a></br><imgsrc="\CC0.png">
