Thanks. Can you explain what win32k lockdown mitigation is when you have a chance?
It allows a process to restrict access to User and GDI system calls[1]. These are often used by exploits because their design and implementation have been (easily) abused by exploits. This mitigation is the only way to reduce the kernel attack surface on Windows (which is why I think it's pretty neat that they're using it now). It is similar to seccomp on Linux, although unlike on Linux where you can specify which system calls you want to use/disable there is no such configuration on Windows, it's just a switch.
You can enable it by adding the following to your Chrome shortcut as launch options:
Code:
--force-fieldtrials="EnableWin32kLockDownMimeTypes/Default/*EnableAppContainer/Enabled/" --enable-win32k-lockdown-mimetypes=* --enable-appcontainer --enable-win32k-renderer-lockdown
You have to force the field trial to default otherwise regardless of what you specify the field trial can disable it (I think this is unintuitive but it's supposedly for testing their rolling out of the feature). Also I added the appcontainer flag as well which may actually get enabled by default at this point (I'm not sure). These features also exist in the chrome://flag page although the field trial settings will still have to be added to the launch options.
I prefer using the launch options since I can just consolidate them in a batch file (although editing a shortcut works too) and sometimes you can't be sure with chrome://flags on whether the flag will stay there (or if it'll even get a flag).
You can also disable some background processes and background networking with the following additional launch options which may aid with privacy:
Code:
--disable-background-networking --dns-prefetch-disable --disable-component-extensions-with-background-pages
This also stops some of the additional processes from getting launched when you start Chrome.
Generic disclaimer that any of these options could break something. Also they may require that you be running the beta or dev versions of the browser. If stability is a concern then you should be safe with the beta version. I also recommend in addition to these options and good browsing habbits to take a look at running uBlock Origin in (what its Wiki calls) medium mode[2] since I think it has a very low barrier to entry and vastly improves your security/privacy over what filter lists can do.
You can use the latest version of Process Hacker to view the security features enabled for the various Chrome processes. Just right click a running process and go to Properties -> General tab -> hit Details on the mitigation policies (win32k will show up if enabled). You can use the command line to see whether the process is a plugin or renderer process. You can use the Token tab under properties to see whether it has an AppContainer SID and if it does it means it's using an AppContainer for that process. Another way to tell if the win32k lockdown mitigation is being used is by opening the Chrome task manager, right clicking in the white space and enabling GDI and USER handle counts. They will be 0 for both for processes where the flag is enabled and being used.
Edit: Added some info about checking whether these features are being used and a little something about uBlock Origin.
[1]
https://msdn.microsoft.com/en-us/library/windows/desktop/hh871472(v=vs.85).aspx (doesn't really explain anything)
[2]
https://github.com/gorhill/uBlock/wiki/Blocking-mode:-medium-mode