Forum Discussion
Jason Childs
Sep 11, 2016Copper Contributor
Best Practice for secure HyperV configuration
Our design and deployment teams were having a debate on the most secure way to deploy HyperV, particularly with respect to Ransomware attacks and protecting from encryption. There seems to be two...
Adam Haynes
Sep 13, 2016Copper Contributor
I agree with everyone so far and just to add a few more things to consider. Managing non domain joined machines, if not done correctly, can be less secure over all since you don't have a secure channel by default to work through. If you have not denied access to domain admins to everything in your enterprise except the domain controllers, you should start there. If you have not looked at LAPS, you should consider deploying and using that and removing all but a select few domain users and groups from local admin. No admins is preferred. Deploy your Hyper-V host configurations with PowerShell DSC and access them over PowerShell constrained endpoints using Just Enough Administration (JEA). If no one ever logs in interactively, admin or user, then the potential for malware execution is greatly reduced. In short how you configure and manage your servers is just as and sometime more important than the configuration itself.