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
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
Other security for Windows, Mac, Linux
LMT AntiMalware
Message
<blockquote data-quote="Lenny_Fox" data-source="post: 876500" data-attributes="member: 82776"><p>There was a famous soccer player in the Netherlands who used to talked in cryptic sentences, one of his quotes "every disadvantage has an advantage", meaning try to turn your weakness into a strength. Considering the time you have and the added value of yet another security application, let's think free and try to remove 'go to market' thresholds (I am a digital marketeer).</p><p></p><p>Position your application as the ideal antivirus companion focusing on user land threats. The rational behind it is that malware has limited operating room when it runs as an unelevated process. At the same time users are not warned when malware changes a HKCU autorun registry key (UAC does not protect those), so even while the operating system limits the damage an unelevated process can do, it still can do a lot of things average users don't want to happen: like a spyware application living in user folders surviving reboot by adding itself as an HKCU autorun entry.</p><p></p><p>Another advantage of changing your promise (only warning against ring 3 - user land intrusions) is that you don't need to protect against kernel based keyloggers (which has the advantage that your application is not considered to have a weakness or missing something).</p><p></p><p>So my suggestion would be: limit the intrusion detection to</p><p>1. Userland hook protection (e.g. keyloggers)</p><p>2. Userland registry protection (only HKCU)</p><p>3. Yara rules protection</p><p>4. Heuristics (explain what it involves???)</p><p></p><p>Newly created unelevated processes which are marked suspicious by one of the above detection mechanisms are checked at Virus Total</p><p></p><p>When you have moved the AI from server side to client side you can add that as an additional intrusion detection mechanism. This saves time so you can write a monitor which protects your processes from being terminiated.</p><p></p><p>Shortest GO2MARKET road I can think of. When protection module is ready launch your companion as a fremium program (1 year free then ask a yearly micro-fee, say 2.95 US dollar, that is less than the price of a big-mac).</p></blockquote><p></p>
[QUOTE="Lenny_Fox, post: 876500, member: 82776"] There was a famous soccer player in the Netherlands who used to talked in cryptic sentences, one of his quotes "every disadvantage has an advantage", meaning try to turn your weakness into a strength. Considering the time you have and the added value of yet another security application, let's think free and try to remove 'go to market' thresholds (I am a digital marketeer). Position your application as the ideal antivirus companion focusing on user land threats. The rational behind it is that malware has limited operating room when it runs as an unelevated process. At the same time users are not warned when malware changes a HKCU autorun registry key (UAC does not protect those), so even while the operating system limits the damage an unelevated process can do, it still can do a lot of things average users don't want to happen: like a spyware application living in user folders surviving reboot by adding itself as an HKCU autorun entry. Another advantage of changing your promise (only warning against ring 3 - user land intrusions) is that you don't need to protect against kernel based keyloggers (which has the advantage that your application is not considered to have a weakness or missing something). So my suggestion would be: limit the intrusion detection to 1. Userland hook protection (e.g. keyloggers) 2. Userland registry protection (only HKCU) 3. Yara rules protection 4. Heuristics (explain what it involves???) Newly created unelevated processes which are marked suspicious by one of the above detection mechanisms are checked at Virus Total When you have moved the AI from server side to client side you can add that as an additional intrusion detection mechanism. This saves time so you can write a monitor which protects your processes from being terminiated. Shortest GO2MARKET road I can think of. When protection module is ready launch your companion as a fremium program (1 year free then ask a yearly micro-fee, say 2.95 US dollar, that is less than the price of a big-mac). [/QUOTE]
Insert quotes…
Verification
Post reply
Top