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
General Security Discussions
What Behavior Blocker is, and what it is not.
Message
<blockquote data-quote="davisd" data-source="post: 824900" data-attributes="member: 77647"><p>You didn't read Opcode's reply did you. He stated that HIPS and sandboxing are both forms of behavior blocking and that <strong>dynamic heuristics</strong> <strong>could be included as a form of behavior blocking depending on how it functions</strong>. The differentiation is commonly provided with the difference in feature names: HIPS; sandbox; dynamic heuristics.</p><p></p><p>He has already told you more than once in different threads that all of these features relay on the same technology internally, most of the time part. He went as far to specify when dynamic heuristics wouldn't count as "behavior blocking" for you. You ignored it and kept pushing your belief. Look at your own comodo reference. They have literaly used sandbox as the most important part of their "Behavior Blocker" named "Defense+".</p><p>You ask for references but your own references have generally been agreeing with him this entire time, so what are you trying to prove here?</p><p>All of this has to do with english language, if the feature name is based on genuine english words then it should make sense in english, no? The term "real-time protection" makes sense in the english when you compare to how it functions in traditional AV solutions whereas the name "firewall" isn't a word that was from the english language, it was made up, and such it has its own definition by whoever thought of the word and used it first or based on how it has been used in the industry by different vendors.</p><p></p><p>The language argument should obligatory be used because it is the only argument that can provide a clear definition of what "behavior blocker" or similar means due to how the different terms are thrown around differently by diferent vendors and how peoples personal interpretation of changes are when they use the different terms.</p><p></p><p>You are making this personal by talking about your 35 years of experience which means you have already lost few screws, you wouldn't need to tell this if you had a genuine argument to come up with. You have nothing to say other than reiterate numerous times how you have references (which I have read and most of them back up what Opcode has been saying about how features like HIPS, sandbox are forms of behavioral blocking and ocassionally dynamic heuristics too) and make comments about how you do not want to argue with people, yet you are doing exactly that, challenging with who has the better understanding and proofs what is "Behaviour Blocking" in your self made dictionary, ignoring the english language. The G Data reference basically explains watching for suspicious behavior and then blocking when it is found, that is literally a form of dynamic heuristics.</p><p></p><p>Avast Behavior Shield isn't HIPS based. It monitors for behavior but it can block the application before suspicious behavior is carried out once it thinks a threshold has been met, so it can also block behavior, it doesn't just let behavior happen and block after it has seen it if it's of interest to the component.</p><p></p><p>If your 35 years of experience isnt for the behavior blocking tech then it is completely irrelevant.</p></blockquote><p></p>
[QUOTE="davisd, post: 824900, member: 77647"] You didn't read Opcode's reply did you. He stated that HIPS and sandboxing are both forms of behavior blocking and that [B]dynamic heuristics[/B] [B]could be included as a form of behavior blocking depending on how it functions[/B]. The differentiation is commonly provided with the difference in feature names: HIPS; sandbox; dynamic heuristics. He has already told you more than once in different threads that all of these features relay on the same technology internally, most of the time part. He went as far to specify when dynamic heuristics wouldn't count as "behavior blocking" for you. You ignored it and kept pushing your belief. Look at your own comodo reference. They have literaly used sandbox as the most important part of their "Behavior Blocker" named "Defense+". You ask for references but your own references have generally been agreeing with him this entire time, so what are you trying to prove here? All of this has to do with english language, if the feature name is based on genuine english words then it should make sense in english, no? The term "real-time protection" makes sense in the english when you compare to how it functions in traditional AV solutions whereas the name "firewall" isn't a word that was from the english language, it was made up, and such it has its own definition by whoever thought of the word and used it first or based on how it has been used in the industry by different vendors. The language argument should obligatory be used because it is the only argument that can provide a clear definition of what "behavior blocker" or similar means due to how the different terms are thrown around differently by diferent vendors and how peoples personal interpretation of changes are when they use the different terms. You are making this personal by talking about your 35 years of experience which means you have already lost few screws, you wouldn't need to tell this if you had a genuine argument to come up with. You have nothing to say other than reiterate numerous times how you have references (which I have read and most of them back up what Opcode has been saying about how features like HIPS, sandbox are forms of behavioral blocking and ocassionally dynamic heuristics too) and make comments about how you do not want to argue with people, yet you are doing exactly that, challenging with who has the better understanding and proofs what is "Behaviour Blocking" in your self made dictionary, ignoring the english language. The G Data reference basically explains watching for suspicious behavior and then blocking when it is found, that is literally a form of dynamic heuristics. Avast Behavior Shield isn't HIPS based. It monitors for behavior but it can block the application before suspicious behavior is carried out once it thinks a threshold has been met, so it can also block behavior, it doesn't just let behavior happen and block after it has seen it if it's of interest to the component. If your 35 years of experience isnt for the behavior blocking tech then it is completely irrelevant. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
