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
Microsoft Defender
Windows Defender ATP: Latest Attack surface reduction rules for maximum impact
Message
<blockquote data-quote="Andy Ful" data-source="post: 799971" data-attributes="member: 32260"><p>This should be tested on all Windows versions that support ASR. I cannot do it, for now.</p><p>But the ASR rule "Block process creations originating from PSExec and WMI commands" (introduced in Windows ver. 1803), can be easily checked with the command in the PowerShell console: <span style="color: rgb(0, 168, 133)"><strong>([WMICLASS]"ROOT\CIMV2:win32_process").Create("cmd.exe")</strong></span></p><p></p><p><strong>WMI not blocked by ASR rule</strong> - WMI could read the ProcessId (in my case 4664).</p><p></p><p>__GENUS : 2</p><p>__CLASS : __PARAMETERS</p><p>__SUPERCLASS :</p><p>__DYNASTY : __PARAMETERS</p><p>__RELPATH :</p><p>__PROPERTY_COUNT : 2</p><p>__DERIVATION : {}</p><p>__SERVER :</p><p>__NAMESPACE :</p><p>__PATH :</p><p><strong><span style="color: rgb(184, 49, 47)">ProcessId : 4664</span></strong></p><p>ReturnValue : 0</p><p>PSComputerName :</p><p></p><p><strong>WMI blocked by ASR rule</strong> - WMI could not read the ProcessId.</p><p></p><p>__GENUS : 2</p><p>__CLASS : __PARAMETERS</p><p>__SUPERCLASS :</p><p>__DYNASTY : __PARAMETERS</p><p>__RELPATH :</p><p>__PROPERTY_COUNT : 2</p><p>__DERIVATION : {}</p><p>__SERVER :</p><p>__NAMESPACE :</p><p>__PATH :</p><p><span style="color: rgb(184, 49, 47)"><strong>ProcessId :</strong></span></p><p>ReturnValue : 2</p><p>PSComputerName :</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 799971, member: 32260"] This should be tested on all Windows versions that support ASR. I cannot do it, for now. But the ASR rule "Block process creations originating from PSExec and WMI commands" (introduced in Windows ver. 1803), can be easily checked with the command in the PowerShell console: [COLOR=rgb(0, 168, 133)][B]([WMICLASS]"ROOT\CIMV2:win32_process").Create("cmd.exe")[/B][/COLOR] [B]WMI not blocked by ASR rule[/B] - WMI could read the ProcessId (in my case 4664). __GENUS : 2 __CLASS : __PARAMETERS __SUPERCLASS : __DYNASTY : __PARAMETERS __RELPATH : __PROPERTY_COUNT : 2 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : [B][COLOR=rgb(184, 49, 47)]ProcessId : 4664[/COLOR][/B] ReturnValue : 0 PSComputerName : [B]WMI blocked by ASR rule[/B] - WMI could not read the ProcessId. __GENUS : 2 __CLASS : __PARAMETERS __SUPERCLASS : __DYNASTY : __PARAMETERS __RELPATH : __PROPERTY_COUNT : 2 __DERIVATION : {} __SERVER : __NAMESPACE : __PATH : [COLOR=rgb(184, 49, 47)][B]ProcessId :[/B][/COLOR] ReturnValue : 2 PSComputerName : [/QUOTE]
Insert quotes…
Verification
Post reply
Top