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
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
Operating Systems
Windows 11
Windows 11 22H2 no longer supports Software Restriction Policies (SRP)
Message
<blockquote data-quote="Andy Ful" data-source="post: 1026631" data-attributes="member: 32260"><p>Blocking PowerShell is a most valuable restriction. I think that you have in mind also WDAC restrictions (Constrained Language Mode), but the attackers found some ways to bypass it.</p><p>A partial solution would be blocking powershell.exe and allowing powershell_ise.exe. In purpose to use powershell_ise.exe, one has to change the ExecutionPolicy to RemoteSigned (or Unrestricted).</p><p>Another useful restriction would be to block outbound connections for PowerShell.</p><p></p><p>If regedit.exe is not blocked, then Exploit Protection for any executable can be easily applied/removed by using a simple .reg file (so one does not have to use PowerShell for that).</p><p>For example:</p><p></p><p>[CODE]Windows Registry Editor Version 5.00</p><p></p><p>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\powershell.exe]</p><p>"MitigationOptions"=hex:00,00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00</p><p>"MitigationAuditOptions"=hex:00,00,00,20,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00</p><p>"EAFModules"=""[/CODE]</p><p></p><p>It is easy to create the reg file for other LOLBins by replacing powershell.exe with another LOLBin.</p><p></p><p>Post edited/corrected.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 1026631, member: 32260"] Blocking PowerShell is a most valuable restriction. I think that you have in mind also WDAC restrictions (Constrained Language Mode), but the attackers found some ways to bypass it. A partial solution would be blocking powershell.exe and allowing powershell_ise.exe. In purpose to use powershell_ise.exe, one has to change the ExecutionPolicy to RemoteSigned (or Unrestricted). Another useful restriction would be to block outbound connections for PowerShell. If regedit.exe is not blocked, then Exploit Protection for any executable can be easily applied/removed by using a simple .reg file (so one does not have to use PowerShell for that). For example: [CODE]Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\powershell.exe] "MitigationOptions"=hex:00,00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 "MitigationAuditOptions"=hex:00,00,00,20,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00 "EAFModules"=""[/CODE] It is easy to create the reg file for other LOLBins by replacing powershell.exe with another LOLBin. Post edited/corrected. [/QUOTE]
Insert quotes…
Verification
Post reply
Top