D
Deleted member 65228
@Sunshine-boy It is because of x64 limitations for kernel-mode interception and ethical requirements. If an AV vendor patches the kernel and it all goes pear shaped, that is on them - they lose customers because of crashes and maybe even have to spend trouble dealing with law-suits if the data-loss was really bad.
Some vendors use the hyper-visor for isolation, like Comodo (for their sandbox). When utilising the hyper-visor you can add support for kernel-mode patching without getting into trouble with PatchGuard - hooking techniques such as MSR (Model Specific Registers) or EPT (Extended Page Table) patching.
Intel have Extended Page Table (EPT) and AMD have Rapid Virtualization Indexing (RVI). You can block kernel-mode operations on 64-bit systems using the above mentioned techniques through virtualisation - you could even use the techniques to actually monitor how PatchGuard itself works - but it is a bit overkill and can be extraordinarily unpredictable in terms of stability in new and creative ways unless the developer doing this line of work has experience.
Some vendors use the hyper-visor for isolation, like Comodo (for their sandbox). When utilising the hyper-visor you can add support for kernel-mode patching without getting into trouble with PatchGuard - hooking techniques such as MSR (Model Specific Registers) or EPT (Extended Page Table) patching.
Intel have Extended Page Table (EPT) and AMD have Rapid Virtualization Indexing (RVI). You can block kernel-mode operations on 64-bit systems using the above mentioned techniques through virtualisation - you could even use the techniques to actually monitor how PatchGuard itself works - but it is a bit overkill and can be extraordinarily unpredictable in terms of stability in new and creative ways unless the developer doing this line of work has experience.