Symantec released a free beta of its integrated security suite that for the first time includes a full-featured anti-spyware component, a move by the Cupertino, Calif.-based company to fend off both its long-time rivals in the security space as well as smaller firms that specialize in spyware defenses.<\/p>\n","protected":false},"excerpt":{"rendered":"
Norton Internet Security 2005 Anti-Spyware Edition is, as the name implies, a version of Symantec’s all-in-one consumer and small business security suite. “Customers want an all-in-one solution,” said Kraig Lane, the group product manager for the suite line.<\/p>\n
The anti-spyware technology included in Norton Internet Security (NIS) uses Symantec’s already-announced Risk Impact Model, a system the company will use to analyze adware and spyware, score it against a set of predefined criteria, then toss it in a “delete” bin or ask the user what he\/she wants to do with it. The new model, which Symantec has said moves away from the black-and-white malicious code approach of detecting and deleting viruses and worms to a more flexible technique that lets users make some decisions about what to keep and what to throw away, is also a way to fend off spyware and adware makers’ threats. <\/p>\n
Other advantages of Symantec’s anti-spyware addition to NIS, said Lane, is that it uses the same scanning engine as Norton Anti-Virus, which is also part of the suite’s bundle.<\/p>\n
http:\/\/www.techweb.com\/wire\/security\/160902145<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1402","post","type-post","status-publish","format-standard","hentry","category-product"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1402","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=1402"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1402\/revisions"}],"predecessor-version":[{"id":3889,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1402\/revisions\/3889"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1402"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1402"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1402"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}