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="Andy Ful" data-source="post: 753533" data-attributes="member: 32260"><p>What this app does:</p><ol> <li data-xf-list-type="ol">It can check only already running programs, so the user has to run one program (at least) from every folder which contains executables.</li> <li data-xf-list-type="ol">It can check if the program path can be writable.</li> <li data-xf-list-type="ol">If the path is writable and the process is running as standard user, then it will be marked as yellow.</li> <li data-xf-list-type="ol">If the path is writable and the process managed to elevate on SUA, then it will be marked as red (vulnerable).</li> <li data-xf-list-type="ol">If the program from point 3 is executed via "Run as administrator" from Explorer context menu, then it will be also marked as red (vulnerable).</li> </ol><p>For the Hard_Configurator user (default-deny setup), this app can be useful to check the concrete application from Program Files or whitelisted paths. Sometimes, but rarely, applications can use some folders by changing their ACL privileges to writable (normally all subfolders in Program Files are not writable as standard user).<strong> Almost all folders whitelisted by the user in the Userspace are also writable (by default) if the user did not adopt ACL restrictions.</strong></p><p><span style="color: rgb(0, 0, 0)">Whitelisted folders area is the potential vulnerability, but it is very hard to make use of it in the home user environment (network protected by NAT router), with default-deny settings and forced SmartScreen. Even when something will be exploited, the malware will not know which folders are whitelisted, except the standard possibilities like OneDrive path. The OneDrive path is specially whitelisted in Hard_Configurator so if the malware with the random name will be copied there, then execution will be blocked.</span> For the paranoid type of security, the user can also whitelist executables by hash.</p><p>Another solution will be restrict whitelisted folders by ACL to <span style="color: rgb(41, 105, 176)"><strong>make them not executable with admin rights</strong></span> or<span style="color: rgb(0, 168, 133)"><strong> not writable</strong></span>. <span style="color: rgb(41, 105, 176)"><strong>The first possibility</strong></span> is OK, if executables located in the whitelisted folder do not elevate and update program from that folder does not require elevation, too (quite possible).</p><p><strong><span style="color: rgb(0, 168, 133)">The second possibility</span></strong> is OK, if the executable does not write anything essential in that folder.</p><p>Another (paranoid) possibility is using a special program (Fides, Secure Folders, Easy File Locker, etc) or WD Controlled Folder Access.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 753533, member: 32260"] What this app does: [LIST=1] [*]It can check only already running programs, so the user has to run one program (at least) from every folder which contains executables. [*]It can check if the program path can be writable. [*]If the path is writable and the process is running as standard user, then it will be marked as yellow. [*]If the path is writable and the process managed to elevate on SUA, then it will be marked as red (vulnerable). [*]If the program from point 3 is executed via "Run as administrator" from Explorer context menu, then it will be also marked as red (vulnerable). [/LIST] For the Hard_Configurator user (default-deny setup), this app can be useful to check the concrete application from Program Files or whitelisted paths. Sometimes, but rarely, applications can use some folders by changing their ACL privileges to writable (normally all subfolders in Program Files are not writable as standard user).[B] Almost all folders whitelisted by the user in the Userspace are also writable (by default) if the user did not adopt ACL restrictions.[/B] [COLOR=rgb(0, 0, 0)]Whitelisted folders area is the potential vulnerability, but it is very hard to make use of it in the home user environment (network protected by NAT router), with default-deny settings and forced SmartScreen. Even when something will be exploited, the malware will not know which folders are whitelisted, except the standard possibilities like OneDrive path. The OneDrive path is specially whitelisted in Hard_Configurator so if the malware with the random name will be copied there, then execution will be blocked.[/COLOR] For the paranoid type of security, the user can also whitelist executables by hash. Another solution will be restrict whitelisted folders by ACL to [COLOR=rgb(41, 105, 176)][B]make them not executable with admin rights[/B][/COLOR] or[COLOR=rgb(0, 168, 133)][B] not writable[/B][/COLOR]. [COLOR=rgb(41, 105, 176)][B]The first possibility[/B][/COLOR] is OK, if executables located in the whitelisted folder do not elevate and update program from that folder does not require elevation, too (quite possible). [B][COLOR=rgb(0, 168, 133)]The second possibility[/COLOR][/B] is OK, if the executable does not write anything essential in that folder. Another (paranoid) possibility is using a special program (Fides, Secure Folders, Easy File Locker, etc) or WD Controlled Folder Access. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
