Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="509322" data-source="post: 770846"><p>To avoid the file extraction just select the x64 version, procexp64.exe on x64 Windows. The extraction to User Space directory (C:\Users\User_Name\Appdata\Local\Temp) happens when the x86 (procexp.exe) of Process Explorer is used.</p><p></p><p>Autoruns scans the system startup locations - both file system and registry - and then the whitelisting is done by file path.</p><p></p><p>Whitelist by hash is a policy that contains or specifies a hash, and that hash is defined in the policy such that the program is allowed to launch only if it matches the calculated hash number.</p><p></p><p>Basically... So, File = hash 123. Policy states File can launch if and only if File = has 123. File = hash 987 attempts to launch, and policy blocks it from executing.</p><p></p><p>In the same manner, you can blacklist by hash number.</p><p></p><p>Understand ?</p></blockquote><p></p>
[QUOTE="509322, post: 770846"] To avoid the file extraction just select the x64 version, procexp64.exe on x64 Windows. The extraction to User Space directory (C:\Users\User_Name\Appdata\Local\Temp) happens when the x86 (procexp.exe) of Process Explorer is used. Autoruns scans the system startup locations - both file system and registry - and then the whitelisting is done by file path. Whitelist by hash is a policy that contains or specifies a hash, and that hash is defined in the policy such that the program is allowed to launch only if it matches the calculated hash number. Basically... So, File = hash 123. Policy states File can launch if and only if File = has 123. File = hash 987 attempts to launch, and policy blocks it from executing. In the same manner, you can blacklist by hash number. Understand ? [/QUOTE]
Insert quotes…
Verification
Post reply
Top
