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
Security
Security Statistics and Reports
Modern protection without signatures – comparison test on real threats (Advanced In The Wild Malware Test)
Message
<blockquote data-quote="Andy Ful" data-source="post: 977666" data-attributes="member: 32260"><p>That can depend on the AV. Anyway, at Level 3 the AVs usually trigger the strongest features because the threat is going to be executed (even if the execution is delayed). Some AVs use only pre-execution features, others can use also post-execution features based on the telemetry of running processes. But, the strong pre-execution features can be triggered also at Levels 1 or 2, if the AV protection is closely integrated with the web browser. An example of such protection can be Defender's BAFS, which works best with Chromium browsers. It can sometimes trigger at Level 1 or 2, even stronger pre-execution protection than at Level 3.</p><p>Unfortunately, this test is prepared in a special way that forces Defender to use only Level 3, which mimics the scenario when the already infected system downloads/drops/execute payloads.</p><p>Among the non-signature features triggered at Level 3 are HIPS, Local ASR, Local AI, AMSI, Local behavior-based detections, Local sandboxing, and their cloud counterparts (including Deep learning). Some AVs can also trigger reputation-based features or provide Network protection for the executed processes.</p><p></p><p>Examples of behavior blocking (related to Defender but probably also common for other AVs):</p><ul> <li data-xf-list-type="ul">Credential dumping from LSASS</li> <li data-xf-list-type="ul">Cross-process injection</li> <li data-xf-list-type="ul">Process hollowing</li> <li data-xf-list-type="ul">User Account Control bypass</li> <li data-xf-list-type="ul">Tampering with antivirus (such as disabling it or adding the malware as exclusion)</li> <li data-xf-list-type="ul">Contacting Command and Control (C&C) to download payloads</li> <li data-xf-list-type="ul">Coin mining</li> <li data-xf-list-type="ul">Boot record modification</li> <li data-xf-list-type="ul">Pass-the-hash attacks</li> <li data-xf-list-type="ul">Installation of root certificate</li> <li data-xf-list-type="ul">Exploitation attempt for various vulnerabilities</li> </ul></blockquote><p></p>
[QUOTE="Andy Ful, post: 977666, member: 32260"] That can depend on the AV. Anyway, at Level 3 the AVs usually trigger the strongest features because the threat is going to be executed (even if the execution is delayed). Some AVs use only pre-execution features, others can use also post-execution features based on the telemetry of running processes. But, the strong pre-execution features can be triggered also at Levels 1 or 2, if the AV protection is closely integrated with the web browser. An example of such protection can be Defender's BAFS, which works best with Chromium browsers. It can sometimes trigger at Level 1 or 2, even stronger pre-execution protection than at Level 3. Unfortunately, this test is prepared in a special way that forces Defender to use only Level 3, which mimics the scenario when the already infected system downloads/drops/execute payloads. Among the non-signature features triggered at Level 3 are HIPS, Local ASR, Local AI, AMSI, Local behavior-based detections, Local sandboxing, and their cloud counterparts (including Deep learning). Some AVs can also trigger reputation-based features or provide Network protection for the executed processes. Examples of behavior blocking (related to Defender but probably also common for other AVs): [LIST] [*]Credential dumping from LSASS [*]Cross-process injection [*]Process hollowing [*]User Account Control bypass [*]Tampering with antivirus (such as disabling it or adding the malware as exclusion) [*]Contacting Command and Control (C&C) to download payloads [*]Coin mining [*]Boot record modification [*]Pass-the-hash attacks [*]Installation of root certificate [*]Exploitation attempt for various vulnerabilities [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Top
