{"id":3113,"date":"2011-06-01T11:38:29","date_gmt":"2011-06-01T10:38:29","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=3113"},"modified":"2015-09-09T19:37:12","modified_gmt":"2015-09-09T11:37:12","slug":"microsoft-enhanced-mitigation-evaluation-toolkit-emet","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2011\/06\/microsoft-enhanced-mitigation-evaluation-toolkit-emet\/","title":{"rendered":"Microsoft Enhanced Mitigation Evaluation Toolkit (EMET)"},"content":{"rendered":"

The enhanced Mitigation Experience Toolkit (EMET) is designed to help prevent hackers from gaining access to your system.<\/p>\n

Software vulnerabilities and exploits have become an everyday part of life. Virtually every product has to deal with them and consequently, users are faced with a stream of security updates. For users who get attacked before the latest updates have been applied or who get attacked before an update is even available, the results can be devastating: malware, loss of PII, etc.<\/p>\n

Security mitigation technologies are designed to make it more difficult for an attacker to exploit vulnerabilities in a given piece of software. EMET allows users to manage these technologies on their system and provides several unique benefits:<\/p>\n

1. No source code needed<\/strong>: Until now, several of the available mitigations (such as Data Execution Prevention) have required for an application to be manually opted in and recompiled. EMET changes this by allowing a user to opt in applications without recompilation. This is especially handy for deploying mitigations on software that was written before the mitigations were available and when source code is not available.<\/p>\n

2. Highly configurable:<\/strong> EMET provides a higher degree of granularity by allowing mitigations to be individually applied on a per process basis. There is no need to enable an entire product or suite of applications. This is helpful in situations where a process is not compatible with a particular mitigation technology. When that happens, a user can simply turn that mitigation off for that process.<\/p>\n