{"id":616,"date":"2013-02-27T04:38:05","date_gmt":"2013-02-27T04:38:05","guid":{"rendered":"http:\/\/e-olio.com\/cknow\/cms\/?p=616"},"modified":"2013-05-08T15:42:58","modified_gmt":"2013-05-08T22:42:58","slug":"interception","status":"publish","type":"post","link":"https:\/\/www.cknow.com\/cms\/vtutor\/interception.html","title":{"rendered":"Interception"},"content":{"rendered":"

Monitoring for system-level routines that perform destructive acts can help, but such monitoring is fairly easily bypassed. Do not depend on it alone.<\/strong><\/p>\n<\/div>Interceptors (also known as resident monitors) are particularly useful for deflecting logic bombs<\/a> and Trojans<\/a>. The interceptor monitors operating system requests that write to disk or do other things that the program considers threatening (such as installing itself as a resident program). If it finds such a request, the interceptor generally pops up and asks you if you want to allow the request to continue. There is, however, no reliable way to intercept direct branches into low level code or to intercept direct input and output instructions done by the virus itself. Some viruses even manage to disable the monitoring program itself. Indeed, for one widely-distributed anti-virus program several years back it only took eight bytes of code to turn its monitoring functions off.<\/p>\n

It is important to realize that monitoring and interception is a risky technique. Some products that use this technique are so annoying to use (due to their frequent messages popping up) that some users consider the cure worse than the disease!<\/p>\n

Summary<\/h4>\n