- Dec 29, 2014
- 1,716
If they open that's a start. Try closing and reopening the EMET GUI with cmd.exe open and then PowerShell. See if it show up green. Just checked and I think I recall now the refresh button doesn't work. Makes testing a little more difficult.
I have set Always On, Opt In, Opt In, Enabled. Can't remeber, the default for DEP might be Opt In. Think I turned it on full time, but I don't get any lag.
Now that I think about it, protecting cmd.exe and powershell using EMET is not so high on the list as it might be compared to protecting them with other security apps. The reason is that EMET protects the application itself from being exploited by malware (then causing damage to the system), rather than protecting the system from being directly exploited by the malicious application (like most security apps). So malware could like wait for a cmd line command to run on the system and then maybe there is a way to exploit that by injecting into the run. Not out of the question I would say, but seems not as likely as the browser or office apps being exploited for sure. Anyway, sure doesn't hurt to protect cmd/ps from being exploited. Javascript is protected by default, so I don't see why cmd/ps shouldn't be too.
Almost forgot. If you use Flash, you might want to add the Flash player executables to the list. I had them before, and I will be adding them. Processes are:
C:\Windows\System32\Macromed\Flash
C:\Windows\SysWow\Macromed\Flash
I have set Always On, Opt In, Opt In, Enabled. Can't remeber, the default for DEP might be Opt In. Think I turned it on full time, but I don't get any lag.
Now that I think about it, protecting cmd.exe and powershell using EMET is not so high on the list as it might be compared to protecting them with other security apps. The reason is that EMET protects the application itself from being exploited by malware (then causing damage to the system), rather than protecting the system from being directly exploited by the malicious application (like most security apps). So malware could like wait for a cmd line command to run on the system and then maybe there is a way to exploit that by injecting into the run. Not out of the question I would say, but seems not as likely as the browser or office apps being exploited for sure. Anyway, sure doesn't hurt to protect cmd/ps from being exploited. Javascript is protected by default, so I don't see why cmd/ps shouldn't be too.
Almost forgot. If you use Flash, you might want to add the Flash player executables to the list. I had them before, and I will be adding them. Processes are:
C:\Windows\System32\Macromed\Flash
C:\Windows\SysWow\Macromed\Flash
Last edited: