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
AMSI .Net and reducing the attack surface
Message
<blockquote data-quote="MacDefender" data-source="post: 844614" data-attributes="member: 83059"><p>Most core Windows services are not .NET based and the ones that are rarely get updated to a new version of the .NET framework when it's not a major Windows release update. </p><p></p><p>AMSI's use case isn't really exploit blocking. It's for introspecting pseudo fileless and fileless threats. Even the article says so:</p><p></p><p></p><p>So it's similar to making it easier for Powershell scripts that use "eval" scan those contents, anything that's executed via eval() is passed via AMSI to scan. The .NET equivalent is calling Assembly.Load on an in memory buffer which isn't scannable by a traditional real-time file scanner. </p><p></p><p>They are not claiming this somehow makes your anti-malware part of the .NET JIT and able to introspect in real-time.</p></blockquote><p></p>
[QUOTE="MacDefender, post: 844614, member: 83059"] Most core Windows services are not .NET based and the ones that are rarely get updated to a new version of the .NET framework when it's not a major Windows release update. AMSI's use case isn't really exploit blocking. It's for introspecting pseudo fileless and fileless threats. Even the article says so: So it's similar to making it easier for Powershell scripts that use "eval" scan those contents, anything that's executed via eval() is passed via AMSI to scan. The .NET equivalent is calling Assembly.Load on an in memory buffer which isn't scannable by a traditional real-time file scanner. They are not claiming this somehow makes your anti-malware part of the .NET JIT and able to introspect in real-time. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
