Unless I missed something, Emsisoft does not provide full anti-exploit capabilities at this time but it is in the works. When asked about anti-exploit protection last year and earlier this year, Fabian Wosar
Fabian Wosar, Post #6
The biggest issue with shipping exploit mitigation is the fact that we always tried to maintain compatibility to other AVs and as a consequence a lot of users use EAM alongside another AV. Implementing exploit mitigation will break compatibility to a lot of AVs that also include some kind of exploit mitigation. If you ever tried to run MBAE, EMET or HMPA alongside each other, you will know what I am talking about here. If we do decide to ship some form of exploit mitigation, it will only be after a head start to people have time to decide whether they want to stick to EAM or their existing AV.
Fabian Wosar, Post #2
...No, we do not provide anti-exploit capabilities. We do protect from the payload these exploits drop, but we do not attempt to mitigate the exploit itself.
Fabian Wosar, Post #4
The problem is that a significant portion of our users expect EAM to run alongside other AVs, which often already implement exploit mitigation features. Multiple exploit mitigations will ultimately clash in many cases. If you ever tried to run MBAE alongside EMET you know what I am talking about. So we will do it only if we can somehow maintain compatibility with other AVs.
Fabian Wosar, Post #4
The only thing of the things you listed we don't implement because of compatibility concerns is exploit mitigation. In general we have no plans of introducing another "edition" of our products. It will be extremely confusing to all our users and will have a huge detrimental impact on development speed as it means another 2 code bases that have to be kept in sync and maintained.
Fabian Wosar, Post #30
The answer to that is a bit complicated. Technically, yes...However, you will notice that we do not advertise it and there are also no options for it. It's not listed as a feature either, mostly because it is far from being finished yet. In general I believe holding off security improvements until an arbitrary release date just to somehow "beef up" the release announcement is kind of stupid and not really in the interest of our users. That is why we will roll them out gradually during the coming months and announce them officially once they are complete, the same way we rolled out the script protection in the last version 10 updates already but didn't officially announce them until the version 11 release.