Windows_Security
Level 24
Thread author
Verified
Honorary Member
Top Poster
Content Creator
Well-known
- Mar 13, 2016
- 1,298
Friends,
Really a great piece of free software which uses Windows internal mechanism and a great add-on to every security setup. @WildByDesign is sort of the intermediate between developer and security forums, so thanks to his feedback collection the developer implements user request (when he thinks they make sense).
Memprotect uses a Windows mechanism (protected processes), which was designed for DRM by Microsoft, but soon was also used to protect Security software from being attacked. MemProtect takes it a step further and uses the API of Microsoft to use this "protected processes" feature to mitigate memory based exploit attacks. Since it is a windows mechanism this feature will cost near zero CPU cycles.
I use it in default allow mode and apply container approach, meaning vulnarable software. MemProtect cages vulnarable processes, by blocking it to inject dll, start other process or access memory of other process. WIth my [defaultallow] approach I tell MemProtect to "cage"only a few vulnarable processes.
This "caging"approach is applied for Chrome, Office and Firefox. I installed Firefox in Mozilla so its Program Files folder is the same as AppData folders. The Home version/free version has a limitation that the ini file may only be 2KB. Using the same folder for installation as AppData simplifies the rules and uses less bytes in the ini file.
[LETHAL]
[#LOGGING]
[WHITELIST]
[DEFAULTALLOW]
!*\Google\*>*\Google\*
!*\Mozilla\*>*\Mozilla\*
!*\Microsoft Office????\*>*\Microsoft Office????\*
!C:\Program Files\*>*SumatraPDF.exe
!C:\Program Files\*>*PDFCreator.exe
!C:\Program Files\*>*splwow64.exe
!C:\Program Files\*>*Chrome.exe
[BLACKLIST]
*\Google\*>*
*\Mozilla\*>*
*\Microsoft Office????\*>*
EOF]
The blacklist entries tell MemProtect to deny *\Google\* to mess with any other process memory. The priortity rule whitelist (with !) overrules the blacklist and it basically tells MemProtect that Google (Chrome and update) is allowed to mess with itself.
I use this on Windows 7 and allow all caged programs to use PDFCreator (printer) and view PDF files (SumatraPDF) print to spool (splwow64.exe) and click on a link (chrome.exe). With this strong protection I don't worry about using WIndows 7 and Office 2007.
Really a great piece of free software which uses Windows internal mechanism and a great add-on to every security setup. @WildByDesign is sort of the intermediate between developer and security forums, so thanks to his feedback collection the developer implements user request (when he thinks they make sense).
Memprotect uses a Windows mechanism (protected processes), which was designed for DRM by Microsoft, but soon was also used to protect Security software from being attacked. MemProtect takes it a step further and uses the API of Microsoft to use this "protected processes" feature to mitigate memory based exploit attacks. Since it is a windows mechanism this feature will cost near zero CPU cycles.
I use it in default allow mode and apply container approach, meaning vulnarable software. MemProtect cages vulnarable processes, by blocking it to inject dll, start other process or access memory of other process. WIth my [defaultallow] approach I tell MemProtect to "cage"only a few vulnarable processes.
This "caging"approach is applied for Chrome, Office and Firefox. I installed Firefox in Mozilla so its Program Files folder is the same as AppData folders. The Home version/free version has a limitation that the ini file may only be 2KB. Using the same folder for installation as AppData simplifies the rules and uses less bytes in the ini file.
[LETHAL]
[#LOGGING]
[WHITELIST]
[DEFAULTALLOW]
!*\Google\*>*\Google\*
!*\Mozilla\*>*\Mozilla\*
!*\Microsoft Office????\*>*\Microsoft Office????\*
!C:\Program Files\*>*SumatraPDF.exe
!C:\Program Files\*>*PDFCreator.exe
!C:\Program Files\*>*splwow64.exe
!C:\Program Files\*>*Chrome.exe
[BLACKLIST]
*\Google\*>*
*\Mozilla\*>*
*\Microsoft Office????\*>*
EOF]
The blacklist entries tell MemProtect to deny *\Google\* to mess with any other process memory. The priortity rule whitelist (with !) overrules the blacklist and it basically tells MemProtect that Google (Chrome and update) is allowed to mess with itself.
I use this on Windows 7 and allow all caged programs to use PDFCreator (printer) and view PDF files (SumatraPDF) print to spool (splwow64.exe) and click on a link (chrome.exe). With this strong protection I don't worry about using WIndows 7 and Office 2007.
Last edited: