Windows 10: Using virtualization as a measure of security

This morning I was setting up a couple of VMs and had this idea. I didn't implement it, just thought about.

With so many virus, hackers, ransoms, and other plagues out there maybe it could be done as a way to protect user and at the same time to guarantee a quick restore in case of problems. The idea is to keep a "bait barrier" that can be destroyed without causing any real damage.

My plan is:

1) Install a very light version of the OS in HD/SSD and add to it a VM app or enable Hyper-V.
2) Copy this partition with a backup/restore app like Macrium Reflect and keep it in a safe place.
3) Create a new guest with your real stuff (every day apps) and move it to a different drive (not C.

This way if for instances your main (physical) OS become hijacked by a ransomware or so you just shrugh because it is just a shell where you don't have nothing important. In this case you could quickly recover your environment in minutes doing it:

1) Format C drive.
2) Restore the partition from backup with Macrium (or whatever).
3) Point to the guest where you run your stuff.

I have used a similar setup for years and I find it very handy to quickly restore partition/system when my Windows crashes in a irreparable way or when it becomes crappy. So instead to pull my hair off or have all that boring task of installing everything from scrach I just restore it. It's an awesome solution also when you need to migrate your system to a larger disk or in case of your disk just die. In my case I still use my main OS as my work OS meaning that I don't run my everyday stuff in a VM but I am considering do this. However I have two VMs -- one with XP for very old apps and other with W7 where I keep my studio music stuff then I don't need to overload the main system with stuff I don't use all the time. By the way this is another great use for virtualization, that is, group applications in VMs to not bloat your system. *Wink

My question here is if such setup would cause a noticeable performance degradation... Personally I can't notice any difference between main OS (W10) and my VMs (7/XP). My system is a desktop i5 with 8GB with SSD. *Huh

What do you think?

:)

 

Corporate Security Solution

That made me so facepalm. Some people have absolutely no clue. I hope they don't take you for granted with all this you're doing for them.

SonicWall is a good security product, so Mindweaver's suggestion sounds like a good one and should make for a rather bigger baby step. Let's hope they take it.

 

About the security of Virtual Smart Cards

Hi Arachnide,

Thank you for writing to Microsoft Community Forums.

Windows 10 uses the TPM to protect the encryption keys for BitLocker Volumes, virtual smart cards, certificates, and the many other keys that TPM is used to generate. TPM is used to securely record and protect integrity-related measurements of select hardware.
The TPM can also be used to generate and store cryptographic keys.

You can refer to this thread in Microsoft TechNet forums on
Does Windows remember PIN of the Virtual Smart Card in memory? and check.

I'd suggest you to post your query in the
TechNet forums where we have a team of experts who are well equipped to answer your query. Queries regarding encryption and decryption are best addressed here.

Regards,

Naveen M

Microsoft Community - Moderator

 

Microsoft Edge TLS Security

After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.