If you're interested in really locking down your system. I'd look at stig viewer specifications. These are typical of the US government STIG Viewer | Unified Compliance Framework® and Link Removed This one is a US military site 
📎 AI Summary:
The thread discusses the lengthy and often stuck installation process of Windows Insider builds, specifically build 17666.1000, with users sharing experiences ranging from several hours to over six hours for the update to complete. Despite troubleshooting efforts, some users report being stuck at 100% preparing to install, highlighting variability likely influenced by hardware and internet speed. Overall, the sentiment emphasizes patience during extended update times, with some noting improvements in subsequent builds.
The thread discusses the lengthy and often stuck installation process of Windows Insider builds, specifically build 17666.1000, with users sharing experiences ranging from several hours to over six hours for the update to complete. Despite troubleshooting efforts, some users report being stuck at 100% preparing to install, highlighting variability likely influenced by hardware and internet speed. Overall, the sentiment emphasizes patience during extended update times, with some noting improvements in subsequent builds.
Yeah I'm going to check out a lot of this stuff. This is all stuff a network administrator should know right? We all know that some outfit is getting hacked and losing people's info. I guess if they were more up on this stuff they could probably stop more of that crap from happening.
Once I got word from Gawker that they had been hacked and somebody had my password. They suggested I really needed to not be using the same password everywhere. Of course at that time I was using one of two very simple passwords all the time. Now I have different passwords all over the place.
It looks like the new Insider O/S that I'm using might have some of that stuff in place already.
Once I got word from Gawker that they had been hacked and somebody had my password. They suggested I really needed to not be using the same password everywhere. Of course at that time I was using one of two very simple passwords all the time. Now I have different passwords all over the place.
It looks like the new Insider O/S that I'm using might have some of that stuff in place already.
Last edited by a moderator:
There is also the virtual TPM which in Windows is called Credential Guard and Device guard. These rely on the Hyper-V hypervisor to protect data such as credentials from tampering or dumping. With credential guard properly configured you will see a number or processes running on your system such as
'Secure System'
'LsaIso'
They run in a special virtual execution rings which can't even be accessed directly from the kernel nor from drivers that typically have direct memroy access. This is achieved via the hyper-v layer running below the kernel.
'Secure System'
'LsaIso'
They run in a special virtual execution rings which can't even be accessed directly from the kernel nor from drivers that typically have direct memroy access. This is achieved via the hyper-v layer running below the kernel.
