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
ESET
ESET 13.1.16.0
Message
<blockquote data-quote="Parsh" data-source="post: 875479" data-attributes="member: 58090"><p>Exactly what I meant earlier <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite109" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> Looked more like it was a result of code analysis (of system calls for expected behavior) rather than flagging actual behavior.</p><p>Though the tooltip info of DBI says that it monitors the activities of <em>all running programs. S</em>uspicious characteristics of code being executed like suspicious API call behavior could have led to the flagging.</p><p></p><p><u>Edit</u>: Just had a look into their <a href="https://www.eset.com/int/about/newsroom/press-releases/research/eset-deep-behavioral-inspection-enables-deeper-monitoring-of-unknown-suspicious-processes/" target="_blank">new whitepaper</a> that says</p><p></p><p>[SPOILER="Process monitoring"]</p><p>[ATTACH=full]237903[/ATTACH]</p><p>[/SPOILER]</p><p>Turns out that it's indeed the <em>system API calls</em> being checked. Not in the binary, but <em>dynamically</em>. DBI monitors the behavior of unknown processes in real-time by hooking into them to monitor the message traffic - and analyze the API calls before they're executed on the system. If it cannot give a verdict, it may pass on to HIPS.</p></blockquote><p></p>
[QUOTE="Parsh, post: 875479, member: 58090"] Exactly what I meant earlier :) Looked more like it was a result of code analysis (of system calls for expected behavior) rather than flagging actual behavior. Though the tooltip info of DBI says that it monitors the activities of [I]all running programs. S[/I]uspicious characteristics of code being executed like suspicious API call behavior could have led to the flagging. [U]Edit[/U]: Just had a look into their [URL='https://www.eset.com/int/about/newsroom/press-releases/research/eset-deep-behavioral-inspection-enables-deeper-monitoring-of-unknown-suspicious-processes/']new whitepaper[/URL] that says [SPOILER="Process monitoring"] [ATTACH type="full" alt="csm_dbi_in_hips_whitepaper_1c8b311659.png"]237903[/ATTACH] [/SPOILER] Turns out that it's indeed the [I]system API calls[/I] being checked. Not in the binary, but [I]dynamically[/I]. DBI monitors the behavior of unknown processes in real-time by hooking into them to monitor the message traffic - and analyze the API calls before they're executed on the system. If it cannot give a verdict, it may pass on to HIPS. [/QUOTE]
Insert quotes…
Verification
Post reply
Top