Microsoft Updates Guideline on Windows Driver Security (bleepingcomputer.com)
An anonymous reader shares a report: Microsoft has released an updated guide on driver security. This new guide offers advice that developers could use to ensure Windows drivers are secured against basic attacks and preventable flaws. The new guide -- also available as a one-document PDF -- is authored by Microsoft's Don Marshall and comes to replace an older help page. [...] While the driver security checklist is a must-read for any software developer and not just driver authors, the guide on assessing "threat modeling for drivers" is also something that software engineers should take a peek at.
Just drive your own damn car!
#DeleteFacebook
U...hu. I think I'll pass this boring document. The boring texts never end.
Here's the actual guidelines document: https://docs.microsoft.com/en-us/windows-hardware/drivers/driversecurity/
Why run Windows in a VM at all if you're not going to give it access to let you work on your critical files?
See definition of oxymoron.
Hmmm. You mean all these decades I could have had the entire multi-volume encyclopedia set in a multi-document PDF? Who knew? (It seems OP just learned what a PDF is: a single-document file-format; or is speaking to an audience 35 years ago who don't know what a PDF is.)
Windows in a VM allows for some very convenient 'undo' positions. Also virtual networking. The more the host machine is like a hypervisor the easier it is to secure it and maintain.