P. 1
SPE CS Getting Started Guide

SPE CS Getting Started Guide

|Views: 3|Likes:
Published by Upender Thatishetti
ok
ok

More info:

Categories:Types, Brochures
Published by: Upender Thatishetti on Jan 28, 2014
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

01/28/2014

pdf

text

original

Symantec™ Protection Engine for Cloud Services Getting Started Guide

Symantec™ Protection Engine for Cloud Services Getting Started Guide
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version: 7.0

Legal Notice
Copyright © 2012 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Symantec Protection Engine provides content scanning and URL filtering . and Symantec™ Scan Engine.Getting Started This document includes the following topics: ■ ■ ■ About Symantec Protection Engine for Cloud Services Why you need virus protection for Web proxy/caching How Symantec Protection Engine protects against threats in a messaging environment What's new in Symantec Protection Engine About supported protocols for Symantec Protection Engine Components of Symantec Protection Engine About implementing Symantec Protection Engine for Cloud Services Before you install Symantec Protection Engine System requirements Where to get more information ■ ■ ■ ■ ■ ■ ■ About Symantec Protection Engine for Cloud Services Symantec™ Protection Engine for Cloud Services replaces Symantec AntiVirus™ for Caching. Symantec™ Protection Engine for Cloud Services is referred to as Symantec™ Protection Engine. Note: In this document. Symantec AntiVirus™ for Messaging. Symantec Protection Engine is a carrier-class content and URL scanning engine.

The SDK supports version 1. regardless of its platform. such as CD-ROM or email. .0.4 Getting Started Why you need virus protection for Web proxy/caching capabilities to any application on an IP network. Corporate security efforts have heavily focused on more traditional areas through which viruses can enter. Symantec Protection Engine accepts scan requests from the client applications that use any of the following protocols: ■ ■ Symantec Protection Engine Native protocol (deprecated) The Internet Content Adaptation Protocol (ICAP). For more information about the connector for your messaging or caching solution. In some cases.0 of ICAP. Depending on your messaging or caching solution. Many new threats target port 80. Symantec also has developed connector code for some third-party applications to seamlessly integrate with Symantec Protection Engine. so hackers now exploit the Web as a means to enter corporate networks. Enterprises typically have focused security around known viruses that enter the network through more common means. It sends the scanning requests to the Protection Engine. The Symantec Protection Engine Software Developers Guide provides information about how to create customized integrations with ICAP. version 1. the software vendor integrates the connector code into its product before distribution. About the connector code The connector code handles the communication between the Symantec Protection Engine and the messaging or caching solution. which is usually open on corporate firewalls so that users can browse the Web. The connector code is either developed by the software vendor of the messaging or caching solution or by Symantec. Any application can pass files or URLs to Symantec Protection Engine for scanning. Why you need virus protection for Web proxy/caching The HTTP gateway is an underprotected area of most networks. See “Components of Symantec Protection Engine” on page 10. you might need to obtain the connector code from the software vendor. as presented in RFC 3507 (April 2003) A proprietary implementation of remote procedure call (RPC) ■ You can use the Symantec Protection Engine software development kit (SDK) or build your own connector to integrate Symantec Protection Engine with your application. and it interprets the scanning results. see the appropriate documentation. as presented in RFC3507 (April 2003).

The industry trend has been to Web-enable many application environments to include the use of technologies like ActiveX.Getting Started How Symantec Protection Engine protects against threats in a messaging environment 5 Dedicated virus scanning for Web traffic is recommended for the following reasons: ■ Scanning Web traffic lets you catch and block threats at the gateway. ■ ■ ■ ■ How Symantec Protection Engine protects against threats in a messaging environment Symantec Protection Engine can detect the following types of risks: ■ ■ ■ Threats (such as viruses. and Java applets to enhance the user experience. which can compromise additional computers and data on the network. ActiveX. Symantec Protection Engine for Messaging uses the following technologies to protect your messaging environment from threats: . stolen. This includes container files that are overly large. JavaScript. or that are designed to maliciously use resources and degrade performance. and the maximum number of nested levels to be decomposed for scanning. JavaScript. such as Nimda and Code Red. Because many people now use Web-based email. Once a threat has been cached. or Visual Basic Scripts) that appear to be part of safe Web content. malicious code can potentially be passed to other users on the network. Many new threats are associated with these Web technologies. which can result in costly downtime to the enterprise. email-born viruses that would otherwise be caught by antivirus scanning at the SMTP gateway can slip through to infect the network. or corrupted files. the maximum file size for container files. which can leave your network vulnerable to attack. worms. Users can potentially disable desktop protection. have entered networks as executables (for example. and Trojan horses) Security risks (such as adware and malware) Denial-of-service attacks Symantec Protection Engine protects your mail system from messages and attachments that overload the system and cause denial-of-service. You can specify the maximum amount of time that the Protection Engine devotes to decompose a file and its contents. Malicious code can result in lost. that contain large numbers of embedded compressed files. Malicious mobile code viruses. rather than multiple times at each desktop.

Bloodhound-Macro technology detects and repairs over 90 percent of new and unknown macro viruses. Heuristics Container file decomposer Automatic product and virus Symantec LiveUpdate technology ensures that your network definitions updates is not at risk of infection from newly discovered viruses. This ensures no interruption in scanning services during the updates. Symantec Protection Engine contains a decomposer that extracts container files so that they can be scanned for risks. Trojan horses. and spyware) to identify new risks. information about the risk (a signature) is stored in a definition file. Bloodhound technology is capable of detecting as much as 80 percent of new and unknown executable file threats. Bloodhound requires minimal overhead since it examines only programs and the documents that meet stringent prerequisites. . The virus definitions file contains the necessary information to detect and eliminate the virus. What's new in Symantec Protection Engine Table 1-1 describes the new features in Symantec Protection Engine. Symantec Protection Engine uses Symantec Bloodhound™ heuristics technology to scan for threats for which no known definitions exist. adware. it moves to the next file. worms. In most cases.6 Getting Started What's new in Symantec Protection Engine Definitions Symantec engineers track reported outbreaks of risks (such as viruses. Bloodhound can determine in microseconds whether a file or document is likely to be infected. After a risk is identified. Bloodhound heuristics technology scans for unusual behaviors (such as self-replication) to target potentially infected documents. You can also update risk definitions using Rapid Release or Intelligent Updater. The updates are handled automatically without having the restart services or redeploy software. The decomposer continues to extract container files until it reaches the maximum that you specify. If it determines that a file is not likely to be infected.

From version 7. Spyware. previously unknown or new non-viral threats that were reported under the generic 'Other Risks' category. Symantec Protection Engine categorizes viral and non-viral threats more accurately. Symantec Protection Engine now provides granular policies to handle unscannable files (malformed and encrypted containers). To download new definitions. You can now exclude files from scanning that exceed the configured file size threshold value. would now be categorized more accurately. along with statistical reports. Symantec Scan Engine exposed a limited set of static non-viral categories like Adware. You can now access the Symantec Protection Engine console using the following two types of authentication modes: ■ Windows Active Directory-based Authentication mode Symantec Protection Engine-based authentication mode This legacy authentication method requires users to enter the Symantec Protection Engine administrator password to access the console. Hence.0 onwards. and Other Risks. This feature is available only in Symantec Protection Engine-based authentication mode. ■ Note: For non-Windows platforms. New Product Catalog for Symantec Protection Engine Customers who use Symantec LiveUpdate™ Administrator (LUA) to download definitions to their local LiveUpdate server for distribution. Manage user accounts The Administrator can now create multiple user accounts for managing Symantec Protection Engine. must update their product catalog in the LUA.Getting Started What's new in Symantec Protection Engine 7 Table 1-1 Feature Enhanced categorization of threats New features Description Previously. Windows Active Directory-based authentication mode Only users from the authorized Windows Active Directory security group can access the Symantec Protection Engine console using their Active Directory credentials. you must add "Symantec Protection Engine 7. Also. Better handling of Unscannable files Scan exclusion policy based on file size . viral threats did not have any categories associated with them. users only have the Symantec Protection Engine-based authentication mode for accessing console.0" to the product catalog in the LUA.

you will be able to retrieve your clean Office files. errors. the data from the Resources page can logging now be saved in log files for futher analysis. Security notice You can configure Symantec Protection Engine to display a custom security notice that contains common security-related information to all users before they log in to the Symantec Protection Engine console.0 .0 is equipped with strong cipher support. Symantec Protection Engine is capable of data on home page retaining cumulative scan data since installation in addition to retaining data since last restart. Thus. Stronger ciphers for password Symantec Protection Engine 7.8 Getting Started What's new in Symantec Protection Engine Table 1-1 Feature New features (continued) Description You can now choose to scan files in-place that are less than the configured file size threshold value. warnings.0 supports the following new platforms: ■ ■ ■ Windows Server 2008 Japanese (32-bit and 64-bit) Windows Server 2008 R2 Japanese (64-bit) Windows Server 2012 (64-bit) Java™ 2SE Runtime Symantec Protection Engine 7. and other information from your Symantec Protection Engine servers.0 Environment (JRE) 7. Support for System Center Operations Manager 2007(SCOM) Pack New platform support Symantec Protection Engine 7.0. Symantec Protection Engine 7.0 can now repair and delete threats. You can integrate Symantec Protection Engine events with System Center Operations Manager (SCOM). This feature is only available over RPC protocol. Enhanced scanning for While previously Symantec Scan Engine used to block access to MS Office documents infected MS Office files. Resource consumption From version 7.0 onwards. In-place scan policy based on file size View cumulative scan From version 7.System Center Operations Manager is a central repository that can receive critical events.0 now supports JRE 7.

and augment Web content as it flows through ICAP servers. It uses ASCII commands and responses to communicate between the client and the server. a client connects to the default IP port. To scan a file. A proprietary remote procedure call (RPC) protocol . The use of RPC frees the developer from having to be familiar with various operating systems and network interfaces. Adaptation might include some sort of transformation or other processing. the client and server disconnect and must initiate a new connection to scan each subsequent file. This protocol is text-based. It sends the file to be scanned and then reads the results of the scan. Table 1-2 Protocol Native protocol (Deprecated) Supported protocols Description Symantec Protection Engine implements a TCP/IP protocol to provide scanning functionality to client applications. ICAP is part of an architecture that lets corporations. usually with modified messages. such as scanning or content filtering. Remote procedure call (RPC) is a client/server infrastructure that increases the interoperability and portability of an application. like HTTP or SMTP. and ISPs dynamically scan. After the client receives the scan results. RPC lets the application be distributed over multiple platforms. Symantec Protection Engine uses a proprietary scanning protocol with the MS-RPC protocol to interface with client applications. The server executes its transformation service on the messages and responds to the client.Getting Started About supported protocols for Symantec Protection Engine 9 About supported protocols for Symantec Protection Engine Table 1-2 lists the supported protocols that client applications can use to send scan requests to Symantec Protection Engine. This protocol is supported only on Windows 2003 Server/Windows 2008 Server/Windows 2012 Server. The protocol lets ICAP clients pass HTTP messages to ICAP servers for adaptation. Internet Content Adaptation Protocol (ICAP) ICAP is a lightweight protocol for executing a remote procedure call on HTTP messages. carriers. The adapted messages might be either HTTP requests or HTTP responses. Any appropriate client can use RPC to communicate with Symantec Protection Engine to request the scanning and repairing of files. change.

The command-line scanner lets you send files to Symantec Protection Engine to be scanned. Components of Symantec Protection Engine Table 1-3 lists the components that are included on the product CD. see Symantec Protection Engine Implementation Guide. security risks (such as adware and spyware). Symantec_Protection_Engine\ Silent_Install\ Silent installation Command-line scanner The software that acts as Command_Line_Scanner\ a client to Symantec Protection Engine through the Symantec Protection Engine application programming interface (API). and unwanted content. Table 1-3 Component Symantec Protection Engine Product components Description Folder name The software that you Symantec_Protection_Engine\ install to protect your network from threats (such as viruses). Symantec_Protection_Engine_SDK\ Symantec Protection Engine software developer's kit . The files that you can use to perform a silent installation or upgrade. Also includes response files for Red Hat and Solaris.10 Getting Started Components of Symantec Protection Engine For more details on the supported protocols. The tools and documentation that you can use to create the customized integrations that use ICAP.

LiveUpdate lets Symantec products download program and definition file updates either directly from Symantec or from a LiveUpdate server.Getting Started Components of Symantec Protection Engine 11 Table 1-3 Component Symantec Central Quarantine server Product components (continued) Description Folder name The tool that you use to Tools\Central_Quarantine\ quarantine infected files that cannot be repaired when you use the ICAP protocol or RPC protocol. or LAN servers to act as internal LiveUpdate servers. Symantec Central Quarantine server lets you isolate unrepairable files so that threats cannot spread. LiveUpdate™ Administration Utility . HTTP. The utility that you use to Tools\LiveUpdate_Admin\ configure one or more intranet FTP. For more information. see the LiveUpdate Administrator's Guide on the product CD.

.12 Getting Started Components of Symantec Protection Engine Table 1-3 Component Product components (continued) Description Folder name System Center Operations You can integrate Tools\SCOM\Management_Pack Manager 2007(SCOM) Symantec Protection Pack Engine events with System Center Operations Manager (SCOM).System Center Operations Manager is a central repository that can receive critical events. the Operations Manager 2007 Agent collects data about the event and forwards it to the System Center Operations Manager. and other information from your Symantec Protection Engine servers. Adobe Acrobat Reader is required to view the reports that are generated in . When a rule is triggered. Preconfigured rules are automatically created when you import the management pack. warnings. System Center Operation Manager Agent monitors Windows Event log for Symantec Protection Engine events based on criteria mentioned in rules of Management pack. see the Symantec™ Protection Engine Management Pack Integration Guide on the Symantec Protection Engine product CD.adobe. errors.com/. For more information.pdf format. You can download Adobe Acrobat Reader from http://www.

0 CD. see your product documentation. If applicable. You must configure the Protection Engine before you configure the messaging or caching solution to send files to the Protection Engine. Symantec Protection Engine is included on the Symantec Protection Engine for Cloud Services 7. For more information about installing and configuring the connector. Before you install Symantec Protection Engine. For more information about integrating your messaging or caching solution with the Protection Engine. Before you install Symantec Protection Engine. For more information. see the appropriate configuration guide. For more information about integrating your messaging or caching solution with the Protection Engine. ■ ■ ■ ■ Before you install Symantec Protection Engine Install Symantec Protection Engine on a computer that meets the system requirements. take the following steps: . For more information about installing and configuring the Protection Engine. see the Symantec Protection Engine Implementation Guide on the CD. You must install the connector on the computer on which the messaging or caching solution is installed. Install Symantec Protection Engine on a separate computer. Configure the messaging or caching solution to send files to the Protection Engine. see the appropriate configuration guide. see the documentation for your connector. install the connector code or plug-in for your messaging or caching solution. Also ensure that your operating system software and server work correctly. see the documentation for your server. Configure Symantec Protection Engine.Getting Started About implementing Symantec Protection Engine for Cloud Services 13 About implementing Symantec Protection Engine for Cloud Services Implementation of Symantec Protection Engine for Cloud Services involves the following process: ■ Ensure that your messaging or caching solution is properly installed and configured. install and configure the operating system software and applicable updates for your server. See “System requirements” on page 15. For more information about the hardware and system requirements for your messaging or caching solution.

Migrating to version 7. To prevent scanning conflicts. perform the post-installation tasks.0 .0 (update 03 or later). JRE 6. or JRE 7. It is recommended to use JRE 7. see the Symantec Protection Engine Implementation Guide. You can turn on antivirus protection after installation is complete. The server (on which you plan to install Symantec Protection Engine) belongs to the same domain or has trust relationship with the Active Directory. Note: Symantec Protection Engine supports only 32-bit versions of Java Runtime Environment. Review the deployment considerations and recommendations.0 (update 13 or later). Symantec Protection Engine does not protect the computer on which it runs.14 Getting Started Before you install Symantec Protection Engine ■ On Windows operating system. Symantec Protection Engine cannot be installed with 64-bit JRE versions. Since Symantec Protection Engine processes the files that might contain threats. For post-installation tasks. ■ ■ After you complete the installation.0 While installing Symantec Protection Engine. Use an antivirus program to protect the server on which Symantec Protection Engine runs. if you want to use Windows Active Directory-based authentication method to access the Symantec Protection Engine console. Symantec Protection Engine scans the files that client applications pass to Symantec Protection Engine.0 (update 21 or later).0 (update 03 or later) on the server. configure the antivirus program not to scan the temporary directory that Symantec Protection Engine uses for scanning. These recommendations can enhance your overall performance. ■ ■ Install Java 2SE Runtime Environment (JRE) 5. you must ensure the following: ■ Create or identify an existing security group in the Active Directory that would be authorized to access the Symantec Protection Engine console. you can choose to upgrade from the previous version to version 7. the server on which it runs is vulnerable if it has no real-time protection. Disable any third-party antivirus products that are running on the server on which you plan to install Symantec Protection Engine. such as Symantec Endpoint Protection. that contains the security group authorized to access the Symantec Protection Engine console.

0. Symantec Protection Engine retains all of the settings and values that you have configured.1.1 You can install the upgrade over the existing installation. you can retain the custom security files. When you upgrade from version 5. and then upgrade the version 5. delete the keystore. Symantec Protection Engine automatically uses the existing files when you upgrade. Note: Symantec Protection Engine does not support upgrades from version 5.2x (which does support a direct upgrade from version 4. If you cancel the upgrade on Solaris after selecting the upgrade type. Symantec Protection Engine retains all of the settings and values that you have configured.2/5. 4.3x or earlier of the product are not supported. take the following actions: ■ If you use the default security files that Symantec Protection Engine generated. If you want to upgrade from version 5. When you upgrade from version 5. . 5. ■ System requirements Before you install Symantec Protection Engine. verify that your server meets the minimum system requirements.2.Getting Started System requirements 15 Table 1-4 describes the upgrades that Symantec Protection Engine supports.public and keystore. you must reinstall the previous version. You must stop the Symantec Protection Engine service before you upgrade the software.3x and earlier Upgrades from version 4.2 You can install the upgrade over the existing installation. you must first upgrade your installation to version 5.2x installation to version 7.1 and use security certificates. Table 1-4 Supported upgrades Previous version number Description 5.private before you perform the upgrade installation. If you want to upgrade a version 4.3x or earlier installation.0.3x). If you use custom security files.

See “System requirements to install Symantec Protection Engine on Solaris” on page 17.16 Getting Started System requirements See “System requirements to install Symantec Protection Engine on Windows” on page 16. System requirements to install Symantec Protection Engine on Windows The following are the minimum system requirements for installing Symantec Protection Engine on Windows: Operating system ■ ■ ■ ■ ■ ■ ■ ■ Windows Server 2003 (32-bit and 64-bit) Windows Server 2003 R2 (32-bit and 64-bit) Windows Server 2003 R2 Japanese (32-bit and 64-bit) Windows Server 2008 SP2 (32-bit and 64-bit) Windows Server 2008 R2 (64-bit) Windows Server 2008 Japanese (32-bit and 64-bit) Windows Server 2008 R2 Japanese (64-bit) Windows Server 2012 (64-bit) Ensure that your operating system has the latest service patches available. Processor Intel or AMD Server Grade Single Processor Quad Core systems or higher 4 GB of RAM or higher 5 GB of hard disk space 10 GB of hard disk space for using URL Filtering feature Hardware Network interface card (NIC) running TCP/IP with a static IP address ■ Internet connection to update definitions ■ ■ Memory Disk space 100 Mbps Ethernet link (1 Gbps recommended) . See “System requirements to install Symantec Protection Engine on Linux” on page 18.

0 (update 21 or later). JRE 6. Microsoft Visual C++ 2005 (SP1 or later) redistributable package (x86) ■ One of the following Web browsers to access the Symantec Protection Engine console: ■ Microsoft Internet Explorer 8 or later Use Microsoft Internet Explorer to access the Symantec Protection Engine console from a Windows client computer.0 (update 13 or later).0 (update 03 or later). Note: Symantec Protection Engine supports only 32-bit versions of Java Runtime Environment.0 (update 03 or later) It is recommended to use JRE 7. System requirements to install Symantec Protection Engine on Solaris The following are the minimum system requirements for installing Symantec Protection Engine on Solaris: Operating system Solaris 10 and 11 Ensure that your operating system has the latest service patches available. ■ The Web browser is only required for Web-based administration. ■ Mozilla Firefox 10 or later Use Mozilla Firefox to access the Symantec Protection Engine console from a Solaris or Linux client computer. or JRE 7. The computer must have access to the server on which Symantec Protection Engine runs.Getting Started System requirements 17 Software ■ J2SE Runtime Environment (JRE) 5. Symantec Protection Engine cannot be installed with 64-bit JRE versions. You must install the Web browser on a computer from which you want to access the Symantec Protection Engine console. Processor Memory Disk space UltraSPARC 4 GB of RAM or higher 5 GB of hard disk space 10 GB of hard disk space for using URL Filtering feature Hardware Network interface card (NIC) running TCP/IP with a static IP address ■ Internet connection to update definitions ■ ■ 100 Mbps Ethernet link (1 Gbps recommended) .

0 (update 21 or later). The Web browser is only required for Web-based administration.5 (32-bit and 64-bit) and later Red Hat Enterprise Linux Server 6 (32-bit and 64-bit) and later Red Hat Advanced Linux Server 6 (32-bit and 64-bit) and later SUSE Linux Enterprise Server 11 (32-bit and 64-bit) Ensure that your operating system has the latest service patches available. JRE 6. You must install the Web browser on a computer from which you want to access the Symantec Protection Engine console. or JRE 7. If you install the self-extracting JRE.0 (update 03 or later). ■ One of the following Web browsers to access the Symantec Protection Engine console: ■ Mozilla Firefox 10 or later Use Mozilla Firefox to access the Symantec Protection Engine console from a Solaris or Linux client computer.18 Getting Started System requirements Software ■ J2SE Runtime Environment (JRE) 5. ensure that you note the installation location. You must provide the location of the JRE if the installer is unable to detect it. Processor Intel or AMD Server Grade Single Processor Quad Core systems or higher 4 GB of RAM or higher 5 GB of hard disk space 10 GB of hard disk space for using URL Filtering feature Memory Disk space . ■ Microsoft Internet Explorer 8 or later Use Microsoft Internet Explorer to access the Symantec Protection Engine console from a Windows client computer. System requirements to install Symantec Protection Engine on Linux The following are the minimum system requirements for installing Symantec Protection Engine on Linux: Operating system ■ ■ ■ ■ ■ Red Hat Enterprise Linux Server 5.0 (update 03 or later) It is recommended to use JRE 7. Note: Symantec Protection Engine supports only 32-bit versions of Java Runtime Environment. The computer must have access to the server on which Symantec Protection Engine runs. Symantec Protection Engine cannot be installed with 64-bit JRE versions.0 (update 13 or later).5 (32-bit and 64-bit) and later Red Hat Advanced Linux Server 5.

2-6 or later ncompress-4.0 (update 03 or later) It is recommended to use JRE 7.0 (update 21 or later). ■ Microsoft Internet Explorer 8 or later Use Microsoft Internet Explorer to access the Symantec Protection Engine console from a Windows client computer.2. Symantec Protection Engine cannot be installed with 64-bit JRE versions. ■ 32 bit libstdc++ library package ■ ■ J2SE Runtime Environment (JRE) 5. ■ 32-bit GNU libuuid-2.6. You must provide the location of the JRE if the installer is unable to detect it. ■ One of the following Web browsers to access the Symantec Protection Engine console: ■ Mozilla Firefox 10 or later Use Mozilla Firefox to access the Symantec Protection Engine console from a Solaris or Linux client computer. ■ GNU C Library (glibc) ■ Software ■ Initscripts This package is required for Red Hat Linux only.0 (update 03 or later). Note: If any of the above package binary is already present on the computer and if the installer is still unable to find it. The computer must have access to the server on which Symantec Protection Engine runs.Getting Started System requirements 19 Hardware Network interface card (NIC) running TCP/IP with a static IP address ■ Internet connection to update definitions ■ ■ 100 Mbps Ethernet link (1 Gbps recommended) Ensure that the following packages are installed: ■ GNU sharutils-4.1-2 or later Use this package to expand the Rapid Release packages.17. or JRE 7. . You must install the Web browser on a computer from which you want to access the Symantec Protection Engine console. Install the JRE using Red Hat Package Manager (RPM). Note: Symantec Protection Engine supports only 32-bit versions of Java Runtime Environment.0 (update 13 or later).4-44 or later Use this package to expand the Rapid Release packages. you can add the path to the binary in LD_LIBRARY_PATH environment variable. JRE 6. The Web browser is only required for Web-based administration. ■ aaa_base package This package is required for SUSE only. Ensure that you note the installation location.

jsp . and enterprise/support/index. which contains information about all known threats.com/ groups.0 CD at the following locations: Symantec Protection Engine for Cloud Services Implementation Guide Symantec_Protection_Engine\Docs\ You can visit the Symantec Web site for more information about your product. information about hoaxes.com/ security_response/index.symantec. news http://www. downloads. The following online resources for Symantec Protection Engine and its supported caching and messaging devices are available: Latest supported caching and messaging devices documentation http://www.symantec. and access to white papers about threats http://enterprisesecurity.symantec.symantec.com/docs/HOWTO77303 Technical support Knowledge Base.20 Getting Started Where to get more information Where to get more information For more information about using this product. contact information. the following resources are available on the Symantec Protection Engine for Cloud Services 7.com/ http://www.jsp mailing list subscriptions Product news and updates Virus Encyclopedia.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->