- Jun 22, 2014
- 899
Only takes one careless moment, right?
Right.
Like letting a white listed app install a compromised update through your default deny set up as in the Ccleaner debacle.
Regards Eck
Last edited:
Only takes one careless moment, right?
Is that the profile "WIndows_10_MT_Windows_Security_hardening.hdc" in the latest (beta) version 4.1.1.1?Windows 10 is really great. With Windows Defender on highest settings (use Configure Defender) and Software Restriction Policies (use Hard_Configurator with profile Windows_Security) only blocking file formats with hidden code (no executables, that is why you need to se WD on highest protection settings) you can runs as admin without any functional loss and have great protection. You really don't need third party AV or any other additional protection.
I put it on all family members PC when they ask me to help setup their PC's. I also tell them to use Edge and add Windows Defender Exploit protection setting called Code Integrity Guard for current Edge (processes MicrosoftEdge.exe and MicrosoftEdgeCP.exe) and future Chromiun based Edge (process msedge.exe). This makes current (old) Edge and future (new) Edge-chromium the safest browsers around (even safer than Chrome). The other benefit of using Edge is that Microsoft cheats and pre-loads Edge at system start (you can check that it cold-starts much faster than Chrome or Firefox).
So unless Windows Defender slows your PC down to a crawl (even on my tablet with a weak intel Atom Z3740 Windows Defender is the 'fastest' less CPU hungry AV), you really don't need to disable AV and risk shoot-in-the-foot errors. Even on the Intel Atom running without antivirus only reduces program start of Chrome with 0.2 seconds. So why bother?
Is that the profile "WIndows_10_MT_Windows_Security_hardening.hdc" in the latest (beta) version 4.1.1.1?
Is that the profile "WIndows_10_MT_Windows_Security_hardening.hdc" in the latest (beta) version 4.1.1.1?
Is that the profile "WIndows_10_MT_Windows_Security_hardening.hdc" in the latest (beta) version 4.1.1.1?
Yes.And is it suitable for use on SUA?
...
Technically, this feature is independent of WD. It can be very useful for people who like to use Edge as a safe browser for banking. But there can be problems with using it for daily work.@Andy Ful
Question: when people use configure defender, would it be possible to add Exploit Protection (allow only Microsoft signed DLL's) for old and new Edge?
I enabled Code Integrity Guard for MicrosoftEdge.exe, MicrosoftEdgeCP.exe, msedge.exe and (as test) for OUTLOOK.EXE.Windows 10 is really great. With Windows Defender on highest settings (use Configure Defender) and Software Restriction Policies (use Hard_Configurator with profile Windows_Security) only blocking file formats with hidden code (no executables, that is why you need to se WD on highest protection settings) you can runs as admin without any functional loss and have great protection. You really don't need third party AV or any other additional protection.
I put it on all family members PC when they ask me to help setup their PC's. I also tell them to use Edge and add Windows Defender Exploit protection setting called Code Integrity Guard for current Edge (processes MicrosoftEdge.exe and MicrosoftEdgeCP.exe) and future Chromiun based Edge (process msedge.exe). This makes current (old) Edge and future (new) Edge-chromium the safest browsers around (even safer than Chrome). The other benefit of using Edge is that Microsoft cheats and pre-loads Edge at system start (you can check that it cold-starts much faster than Chrome or Firefox).
So unless Windows Defender slows your PC down to a crawl (even on my tablet with a weak intel Atom Z3740 Windows Defender is the 'fastest' less CPU hungry AV), you really don't need to disable AV and risk shoot-in-the-foot errors. Even on the Intel Atom running without antivirus only reduces program start of Chrome with 0.2 seconds. So why bother?
Install MBAE and add outlook and edge to the protected programs. It should fail to inject MBAE.dllI enabled Code Integrity Guard for MicrosoftEdge.exe, MicrosoftEdgeCP.exe, msedge.exe and (as test) for OUTLOOK.EXE.
Is there a way to verify of this working correctly?
Do you also recommend flags like appcontainer for chromium based edge or should this be enough?
But there can be problems with using it for daily work.
For now, I am not sure about adding it to H_C. But, this can change in the future.![]()
When people use a third party antivirus this settings blocks the DLL the AV might inject in the browser.
It's a marketing stunt.On top of that Google does not like third-party software injecting DLL's in Chrome
It is never going to stop the main vendors.On top of that Google does not like third-party software injecting DLL's in Chrome, so your only speeding up things (fair chance that in a year or two Chrome protects its broker against DLL injection)
They can install a driver like MemPortect which safe guards chrome.exe. I did not post that they implemented the broker protection in the broker running medium integrity levelIt is never going to stop the main vendors.
Google resorted to the dirty warning tactic to scare people because they know they have absolutely no idea how to actually prevent AVs from injecting code.
Google are punching above their weight and they know it.
Google Chrome runs with a CPL of 3. Google Chrome will never run with a CPL of 0 or -1 (guest CPL 0).
You cannot block someone running at a higher privilege level at you, and enforcing anything to those running at the same privilege level as you is cat and mouse games.
CIG will prevent Edge from loading images (usually DLLs) which are not from Microsoft Store or not Microsoft-signed. It is more restrictive than just preventing DLL injections to Edge browser by external applications.I would NOT add it to H_C. When people use a third party antivirus this settings blocks the DLL the AV might inject in the browser. That is why I asked to add it to Configure Defender. Chances are very low that someone uses CD when they don't use Windows Defender. For people using Windows Defender this only 'allow MS signed' has advantages without any downside. On top of that Google does not like third-party software injecting DLL's in Chrome, so your only speeding up things (fair chance that in a year or two Chrome protects its broker against DLL injection)
No, that will not stop them.They can install a driver like MemPortect which safe guards chrome.exe. I did not post that they implemented the broker protection in the broker running medium integrity level![]()
MemProtect cannot "stop" DLL injection. MemProtect can prevent handle creation and duplication (or threads) of the processes it is "protecting".Memprotect can stop DLL injection, Protected processes can stop DLL-injection, Windows integrity guard can stop DLL-injection.