Upgraded to v5 recently and noticed that D+ is allowing some applications to run without alerting me to their execution (no trusted rules previously set in security policy). I initially thought that this had something to do with the new cloud search features which I disabled along with “trust files from trusted installers” just in case, but D+ still didn’t trigger any alerts.
The applications in question are:
C:\Windows\system32\vmnetdhcp.exe (VMware VMnet DHCP service)
C:\Windows\system32\AUDIODG.EXE (Windows Audio Device Graph Isolation)
Note that both are services executed by services.exe which is set to the default rule created at install.
I’m basically looking to enable old defense functionality of alerting me to any type of executable trying to lunch regardless of its trusted state in the cloud or the trusted vendor list. Can this still be achieved somehow?
for the record I didn’t not try removing the listings in the trusted vendor list, as I am unsure if I can restore it easily. Could this be what im looking for?
Also, did anyone notice that ever since v5 it takes defense a greater length if time to intercept an application?
My settings:
D+ is set to paranoid
Image execution control enabled with only “Do heuristic…” and “Detect shellcode…” enabled.
Sandbox enabled with automatically detect and trust disabled. (have it on for the manual sanboxing via right click menu)
“Trusted Files” and “Unrecognized Files” lists empty.
Nope, AUDIODG.EXE starts randomly whenever I run anything that has to do with sound and vmnetdhcp.exe I started via a batch file or manually through mmc → services.
It is set to “Windows System Application” if remember correctly I changed this app policy manually from the custom rule which is created on install which.
So basically, what your saying is that when a trusted application lunches another application (who doesn’t have a policy applied) will inherit the parent application policy? this doesn’t seem right to me.
I’ve been reading older posts and it appears that theres an additional hidden trusted vendor list withing comdo which is invisible to the user and might be the reason why some applications don’t trigger an alert even after setting to paranoid, disabling cloud, disabling sandbox and purging the trusted vendor list.
Is there really no way to get v4 behavior back? I don’t like the fact that some programs run without having a policy set by me.
Can anyone else using windows 7 and/or Vmware workstation verify that the executables I mentioned are getting past their D+?
Oh and another question, can anyone explain how some executables which are digitally signed by the same vendor are triggering alerts and some do not?