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
Battlefield
Software Comparison
Planned: Real-world Test of Trend Micro, ZoneAlarm, Eset and Webroot
Message
<blockquote data-quote="Andy Ful" data-source="post: 1098835" data-attributes="member: 32260"><p>I do not know if "dead" is the best choice, I used it as the opposite of the term "alive" = present on the attacker servers or malicious domains used in the attack. Many samples can be "alive" in the wild for a short time (several minutes up to a few hours, and disappear). The short "alive" time causes a low prevalence of the sample (some AVs are impacted by the sample in the wild, and some are not). The behavior of the sample is often different at the time when it is "alive" in the wild and at the test time when it is "dead". During the test time, some AVs detect the sample by a signature created on the basis of the "alive" behavior. Other AVs will try to detect the sample on the basis of the "dead" behavior. To avoid this, one must test the malware as soon as possible. Any delay increases the error, so more samples must be tested to keep that error sufficiently low.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 1098835, member: 32260"] I do not know if "dead" is the best choice, I used it as the opposite of the term "alive" = present on the attacker servers or malicious domains used in the attack. Many samples can be "alive" in the wild for a short time (several minutes up to a few hours, and disappear). The short "alive" time causes a low prevalence of the sample (some AVs are impacted by the sample in the wild, and some are not). The behavior of the sample is often different at the time when it is "alive" in the wild and at the test time when it is "dead". During the test time, some AVs detect the sample by a signature created on the basis of the "alive" behavior. Other AVs will try to detect the sample on the basis of the "dead" behavior. To avoid this, one must test the malware as soon as possible. Any delay increases the error, so more samples must be tested to keep that error sufficiently low. [/QUOTE]
Insert quotes…
Verification
Post reply
Top