- Apr 5, 2021
- 621
Thanks @Andy Ful , I missed running that last updater.exe command yesterday. Testing just now,. OSArmor blocks it the same as yours.
Please provide comments and solutions that are helpful to the author of this topic.
Actually, AutoPilot blocks this attack just fine. I am guessing that have your WLC set to "Allow Safe WhitelistCloud items when OFF or AutoPilot", which would allow this attack when VS is OFF or on AutoPilot.No block from VoodooShield (in auto pilot mode) and no block from Microsoft Defender hardened by ConfigureDefender and Simple Windows Hardening
You forgot to mention that "Allow Safe WhitelistCloud items when OFF or AutoPilot" is the default setting after a fresh VS install.Actually, AutoPilot blocks this attack just fine. I am guessing that have your WLC set to "Allow Safe WhitelistCloud items when OFF or AutoPilot", which would allow this attack when VS is OFF or on AutoPilot.
View attachment 256511
The default setting is Smart Mode.You forgot to mention that "Allow Safe WhitelistCloud items when OFF or AutoPilot" is the default setting after a fresh VS install.
I was simply pointing out that it was not AutoPilot that allowed this attack, it was the "Allow Safe WhitelistCloud items when OFF or AutoPilot" WLC setting. I can change the default, all I have to do is change a 1 to a 0.@danb you are correct, but if I want to use autopilot mode, I must change the default setting "Allow Safe WhitelistCloud items when OFF or AutoPilot" of switch off WhitelistCloud?
Yes, I understand that, but for the user (me) it feels like AutoPilot allowed the attack.I was simply pointing out that it was not AutoPilot that allowed this attack, it was the "Allow Safe WhitelistCloud items when OFF or AutoPilot" WLC setting. I can change the default, all I have to do is change a 1 to a 0.
AutoPilot should mainly be used as an additional layer of protection to complement an existing robust traditional or ngav security product, or it can be used as kind of a "Smart Training" mode for a few days.
If you close that window, VS defaults to Smart Mode. Having said that, we probably should mention in that window that Smart Mode is the default, although, we do mention it here...View attachment 256512
Since left side is not "smart mode" I guess I will say it's 50/50 (and I was half wrong with default)
And that is exactly why I wanted to make it absolutely clear that it was not AutoPilot that allowed the attack, so that you were aware of this, and so you can change the setting to your liking.Yes, I understand that, but for the user (me) it feels like AutoPilot allowed the attack.
I'm using VS as an additional layer of protection to compliment Microsoft Defender.
Just trying to look for the best balance between security and usability that I can also use for family and friends.
What would be the additional benefit of WhitelistCloud when you don't allow safe items?
AutoPilot will work either way, it all depends on how tight you want your config to be, and what other security products you are running.@danb you are correct, but if I want to use autopilot mode, I must change the default setting "Allow Safe WhitelistCloud items when OFF or AutoPilot" of switch off WhitelistCloud?
ok, with CFW the updater and amsi are copied to APPDATA, but nothing happens after pressing enter ! is it me, or is something supposed to happen?@wat0114, @porkpiehat
The below test:
Code:copy %windir%\System32\windowspowershell\v1.0\powershell.exe %APPDATA%\updater.exe copy %windir%\System32\amsi.dll %APPDATA%\amsi.dll %APPDATA%\updater.exe -Command exit
requires Command Prompt. PowerShell is not executed at all.
Simply open Command Prompt and paste/execute the code.
OSA blocks this in another way:
View attachment 256462
It is OK. The renamed PowerShell (updater.exe) is executed and immediately closed. Depending on the Comodo settings, the execution can be allowed, contained in the sandbox, or blocked. The alerts can be suppressed by your settings. If not, then the lack of alert means that Comodo allowed unrestricted execution.ok, with CFW the updater and amsi are copied to APPDATA, but nothing happens after pressing enter ! is it me, or is something supposed to happen?
aah, I have my settings to Block.... I just enabled HIPS, and an alert was given, so I can only assume that everything is hunky dory. cheers!It is OK. The renamed PowerShell (updater.exe) is executed and immediately closed. Depending on the Comodo settings, the execution can be allowed, contained in the sandbox, or blocked. The alerts can be suppressed by your settings. If not, then the lack of alert means that Comodo allowed unrestricted execution.