Symantec on Monday introduced new client-side security software for the enterprise that borrows some tools and techniques from the company’s consumer line.<\/p>\n
Client Security integrates firewall, anti-virus, and intrusion detection defenses for desktops and laptops, then puts all the protected clients under control from a single management console.<\/p>\n
Its target: systems that are beyond the enterprise perimeter, such as employee PCs, mobile workers’ notebooks, and branch office systems unguarded at the gateway.<\/p>\n
“If clients always stayed behind the perimeter, you wouldn’t need something like Client Security,” said Murray.<\/p>\n
“But they’re moving beyond the perimeter, and enterprises need to protect every aspect of the corporate environment.”<\/p>\n
Among the new features in version 2.0 are several which made their debut in the consumer-level Symantec Internet Security, said Murray.<\/p>\n
Client Security now includes a Web ad blocker, as well as an adware\/spyware detector, all tools that have been part of the Internet Security for consumers.<\/p>\n
Client Security also boasts several new features expressly for enterprises, including a virtual private network (VPN) compliance checker that verifies an outside system meets set policies before it’s allowed to connect with the network.<\/p>\n
Administrators can demand that remote machines accessing the network via a VPN tunnel, for instance, have up-to-date virus definitions and a properly configured and enabled firewall.<\/p>\n
http:\/\/www.techweb.com\/wire\/story\/TWB20040405S0001<\/p>\n","protected":false},"excerpt":{"rendered":"
Symantec on Monday introduced new client-side security software for the enterprise that borrows some tools and techniques from the company’s consumer line. Client Security integrates firewall, anti-virus, and intrusion detection defenses for desktops and laptops, then puts all the protected clients under control from a single management console. Its target:…<\/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-1300","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\/1300","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=1300"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1300\/revisions"}],"predecessor-version":[{"id":3787,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/1300\/revisions\/3787"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=1300"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=1300"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=1300"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}