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: 1032318" data-attributes="member: 32260"><p>Such a BlockList would be relatively long (over 60 entries):</p><p>AddInProcess, AddInProcess32, AddInUtil, Aspnet_Compiler, bash, bitsadmin, cdb, cmd, cmstp, csc, csi, dbghost, dbgsvd, dnx, finger, forfiles, fsi, FsiAnyCpu, hh, ieexec, iexplore, ilasm, InfDefaultInstall, InstallUtil, jsc, kd, kill, lxrun, Microsoft.Workflow.Compiler, msbuild, msdt, mshta, ntkd, ntsd, pnputil, powershell, PowerShellCustomHost, powershell_ise, PresentationHost, rcsi, reg, regasm, regini, regsvr32, RegSvcs, runas, rundll32, RunScriptHelper, sc, schtasks, SyncAppvPublishingServer, TextTransform, vbc, verclsid, VisualUiaVerifyNative, wfc, windbg, wmic, wsl, wslconfig, wslhost, xwizard.</p><p></p><p>The list is longer than for WDAC, because H_C does not block DLLs (but blocks the files that could contain the CmdLines to run DLLs via LOLBins). If you use a setup that does not prevent running CmdLines, then you must also add the LOLBins that can run DLLs.</p><p></p><p>I prefer the setup that can prevent access to CmdLine (as much as possible). This can be done via SRP in H_C and cannot be done via AppLocker or WDAC. That is why I included in enhanced settings only some popular LOLBins (probably unnecessary).</p><p>Anyway, I can put some info about the extended set of LOLBins in the H_C manual.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 1032318, member: 32260"] Such a BlockList would be relatively long (over 60 entries): AddInProcess, AddInProcess32, AddInUtil, Aspnet_Compiler, bash, bitsadmin, cdb, cmd, cmstp, csc, csi, dbghost, dbgsvd, dnx, finger, forfiles, fsi, FsiAnyCpu, hh, ieexec, iexplore, ilasm, InfDefaultInstall, InstallUtil, jsc, kd, kill, lxrun, Microsoft.Workflow.Compiler, msbuild, msdt, mshta, ntkd, ntsd, pnputil, powershell, PowerShellCustomHost, powershell_ise, PresentationHost, rcsi, reg, regasm, regini, regsvr32, RegSvcs, runas, rundll32, RunScriptHelper, sc, schtasks, SyncAppvPublishingServer, TextTransform, vbc, verclsid, VisualUiaVerifyNative, wfc, windbg, wmic, wsl, wslconfig, wslhost, xwizard. The list is longer than for WDAC, because H_C does not block DLLs (but blocks the files that could contain the CmdLines to run DLLs via LOLBins). If you use a setup that does not prevent running CmdLines, then you must also add the LOLBins that can run DLLs. I prefer the setup that can prevent access to CmdLine (as much as possible). This can be done via SRP in H_C and cannot be done via AppLocker or WDAC. That is why I included in enhanced settings only some popular LOLBins (probably unnecessary). Anyway, I can put some info about the extended set of LOLBins in the H_C manual. [/QUOTE]
Insert quotes…
Verification
Post reply
Top