From: Paula Miner
To: Untitled Mail Group (DO NOT USE)
Date: Sunday, December 1, 2019 12:06 AM
Subject: Let's move on

We need to have a meeting about shifting our focus a little bit. We've reset VM 1 how many times now? For real, we've definitely collected as much data as we can from it at this point. We just need to work with what we have and try to increase the stability of our connection to VM2. We've obviously gotten spoiled by the ease of access that VM1 offers us, but it's just unrealistic for somеone in real life to bе granted a level of elevation even close to "Monitor Kernel Access". If we can't establish a stable connection to VM2, then how can we expect to get anywhere when the same scenario inevitably occurs to our own universe?

Anyway - thanks to Ro's work, we were able to acquire a few rudimentary logs. I have an idea on how to increase connection stability to VM2 while maintaining weak hypervisor access to everyone inside on an individual basis. Ironically, it has to do with something that they're building in their own VM. I'll go into detail in a more formal report, but some of the log files indicate attempts of theirs to pool together the access potential of multiple individuals into a single parallel unit. It sounds ridiculous, but if they actually get somewhere with it, then we might have a solid entry point that doesn't heavily intrude upon the VM.

I'm going to spin up a read-only hypervisor that we can use to test different ideas like this. The elevation level will be set to "Monitor Adjacent Runtime-Level Access". The VM will just be named "TEST VM" for now, although the parallel-access unit they're building in the VM seems to be called "Project Libitina", according to the few logs we have. We can change the name once we actually get a decent picture of it.

Paula Miner
Project Manager