spe cs getting_started_guide

Symantec™ Protection Enginefor Cloud Services GettingStarted Guide

Symantec™ Protection Engine for Cloud ServicesGetting Started Guide

The software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0

Legal NoticeCopyright © 2012 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in theU.S. and other countries. Other namesmaybe trademarksof 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 documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

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 messagingenvironment

■ 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 CloudServicesSymantec™ Protection Engine for Cloud Services replaces Symantec AntiVirus™for Caching, Symantec AntiVirus™ for Messaging, and Symantec™ Scan Engine.

Note: In this document, Symantec™ProtectionEngine forCloudServices is referredto as Symantec™ Protection Engine.

Symantec Protection Engine is a carrier-class content and URL scanning engine.Symantec Protection Engine provides content scanning and URL filtering

capabilities to any application on an IP network, regardless of its platform. Anyapplication can pass files or URLs to Symantec Protection Engine for scanning.

Symantec Protection Engine accepts scan requests from the client applicationsthat use any of the following protocols:

■ Symantec Protection Engine Native protocol (deprecated)

■ The Internet Content Adaptation Protocol (ICAP), version 1.0, as presented inRFC 3507 (April 2003)

■ A proprietary implementation of remote procedure call (RPC)

You can use the Symantec Protection Engine software development kit (SDK) orbuild your own connector to integrate Symantec Protection Engine with yourapplication. The SDK supports version 1.0 of ICAP, as presented inRFC3507 (April2003). Symantec also has developed connector code for some third-partyapplications to seamlessly integrate with Symantec Protection Engine.

The Symantec ProtectionEngine SoftwareDevelopersGuide provides informationabout how to create customized integrations with ICAP.

See “Components of Symantec Protection Engine” on page 10.

About the connector codeThe connector codehandles the communication between theSymantec ProtectionEngine and the messaging or caching solution. It sends the scanning requests tothe Protection Engine, and it interprets the scanning results.

The connector code is either developed by the software vendor of the messagingor caching solution or by Symantec. Depending on your messaging or cachingsolution, you might need to obtain the connector code from the software vendor.In some cases, the software vendor integrates the connector code into its productbefore distribution.

Formore information about the connector for yourmessaging or caching solution,see the appropriate documentation.

Why youneed virus protection forWebproxy/cachingTheHTTPgateway is anunderprotected area ofmost networks. Corporate securityefforts have heavily focused onmore traditional areas throughwhich viruses canenter. Enterprises typically have focused security around known viruses thatenter the network through more common means, such as CD-ROM or email, sohackers now exploit the Web as a means to enter corporate networks. Many newthreats target port 80, which is usually open on corporate firewalls so that userscan browse the Web.

Getting StartedWhy you need virus protection for Web proxy/caching

4

Dedicatedvirus scanning forWeb traffic is recommended for the following reasons:

■ Scanning Web traffic lets you catch and block threats at the gateway, ratherthan multiple times at each desktop. Users can potentially disable desktopprotection, which can leave your network vulnerable to attack.

■ Becausemanypeople nowuseWeb-based email, email-born viruses thatwouldotherwise be caught by antivirus scanning at the SMTP gateway can slipthrough to infect the network.

■ The industry trend has been to Web-enable many application environmentsto include the use of technologies like ActiveX, JavaScript, and Java applets toenhance the user experience.Manynew threats are associatedwith theseWebtechnologies. Malicious mobile code viruses, such as Nimda and Code Red,have entered networks as executables (for example, ActiveX, JavaScript, orVisual Basic Scripts) that appear to be part of safe Web content.

■ Once a threat has been cached, malicious code can potentially be passed toother users on the network, which can compromise additional computers anddata on the network.

■ Malicious code can result in lost, stolen, or corrupted files, which can resultin costly downtime to the enterprise.

How Symantec Protection Engine protects againstthreats in a messaging environment

Symantec Protection Engine can detect the following types of risks:

■ Threats (such as viruses, worms, and Trojan horses)

■ Security risks (such as adware and malware)

■ Denial-of-service attacks

Symantec Protection Engine protects your mail system from messages andattachments that overload the system and cause denial-of-service. This includescontainer files that are overly large, that contain large numbers of embeddedcompressed files, or that are designed to maliciously use resources and degradeperformance. You can specify the maximum amount of time that the ProtectionEngine devotes to decompose a file and its contents, the maximum file size forcontainer files, and the maximum number of nested levels to be decomposed forscanning.

Symantec Protection Engine for Messaging uses the following technologies toprotect your messaging environment from threats:

5Getting StartedHow Symantec Protection Engine protects against threats in a messaging environment

Symantec engineers track reported outbreaks of risks (suchas viruses, Trojan horses, worms, adware, and spyware) toidentify new risks. After a risk is identified, informationabout the risk (a signature) is stored in a definition file. Thevirus definitions file contains the necessary information todetect and eliminate the virus.

Definitions

Symantec Protection Engine uses Symantec Bloodhound™heuristics technology to scan for threats forwhichnoknowndefinitions exist. Bloodhound heuristics technology scansfor unusual behaviors (such as self-replication) to targetpotentially infected documents. Bloodhound technology iscapable of detecting as much as 80 percent of new andunknown executable file threats. Bloodhound-Macrotechnology detects and repairs over 90 percent of new andunknown macro viruses. Bloodhound requires minimaloverhead since it examines only programs and thedocuments thatmeet stringent prerequisites. Inmost cases,Bloodhound can determine in microseconds whether a fileor document is likely to be infected. If it determines that afile is not likely to be infected, it moves to the next file.

Heuristics

Symantec Protection Engine contains a decomposer thatextracts container files so that they canbe scanned for risks.The decomposer continues to extract container files untilit reaches the maximum that you specify.

Container file decomposer

SymantecLiveUpdate technologyensures that yournetworkis not at risk of infection from newly discovered viruses.The updates are handled automatically without having therestart services or redeploy software. This ensures nointerruption in scanning services during the updates.

You can also update risk definitions using Rapid Release orIntelligent Updater.

Automatic product andvirusdefinitions updates

What's new in Symantec Protection EngineTable 1-1 describes the new features in Symantec Protection Engine.

Getting StartedWhat's new in Symantec Protection Engine

6

Table 1-1 New features

DescriptionFeature

Previously, Symantec Scan Engine exposed a limited set of staticnon-viral categories like Adware, Spyware, andOther Risks. Also,viral threats did not have any categories associated with them.Fromversion7.0onwards, SymantecProtectionEnginecategorizesviral and non-viral threats more accurately. Hence, previouslyunknown or new non-viral threats that were reported under thegeneric 'Other Risks' category, would now be categorized moreaccurately.

Enhancedcategorization ofthreats

You cannowaccess theSymantecProtectionEngine console usingthe following two types of authentication modes:

■ Symantec Protection Engine-based authentication mode

This legacy authenticationmethod requires users to enter theSymantec ProtectionEngine administrator password to accessthe console.

■ Windows Active Directory-based authentication mode

Only users from the authorized Windows Active Directorysecurity group can access the Symantec Protection Engineconsole using their Active Directory credentials.

Note: For non-Windows platforms, users only have the SymantecProtection Engine-based authentication mode for accessingconsole.

Windows ActiveDirectory-basedAuthentication mode

The Administrator can now create multiple user accounts formanaging Symantec Protection Engine. This feature is availableonly in Symantec Protection Engine-based authentication mode.

Manage user accounts

Customers who use Symantec LiveUpdate™ Administrator (LUA)to download definitions to their local LiveUpdate server fordistribution, must update their product catalog in the LUA. Todownload new definitions, you must add "Symantec ProtectionEngine 7.0" to the product catalog in the LUA.

New Product Catalogfor SymantecProtection Engine

Symantec Protection Engine now provides granular policies tohandle unscannable files (malformed and encrypted containers),along with statistical reports.

Better handling ofUnscannable files

You can now exclude files from scanning that exceed theconfigured file size threshold value.

Scan exclusion policybased on file size

7Getting StartedWhat's new in Symantec Protection Engine

Table 1-1 New features (continued)

DescriptionFeature

You can now choose to scan files in-place that are less than theconfigured file size threshold value. This feature is only availableover RPC protocol.

In-place scan policybased on file size

From version 7.0, Symantec Protection Engine is capable ofretaining cumulative scan data since installation in addition toretaining data since last restart.

View cumulative scandata on home page

From version 7.0 onwards, the data from the Resources page cannow be saved in log files for futher analysis.

Resource consumptionlogging

Symantec Protection Engine 7.0 is equipped with strong ciphersupport.

Stronger ciphers forpassword

While previously Symantec Scan Engine used to block access toinfectedMSOffice files, Symantec Protection Engine 7.0 can nowrepair and delete threats. Thus, you will be able to retrieve yourclean Office files.

Enhanced scanning forMS Office documents

You can configureSymantecProtectionEngine todisplay a customsecuritynotice that contains commonsecurity-related informationto all users before they log in to the Symantec Protection Engineconsole.

Security notice

You can integrate SymantecProtectionEngine eventswithSystemCenter Operations Manager (SCOM).System Center OperationsManager is a central repository that can receive critical events,errors, warnings, and other information from your SymantecProtection Engine servers.

Support for SystemCenter OperationsManager 2007(SCOM)Pack

Symantec Protection Engine 7.0 supports the following newplatforms:

■ Windows Server 2008 Japanese (32-bit and 64-bit)

■ Windows Server 2008 R2 Japanese (64-bit)

■ Windows Server 2012 (64-bit)

New platform support

Symantec Protection Engine 7.0 now supports JRE 7.0Java™ 2SE RuntimeEnvironment (JRE) 7.0

Getting StartedWhat's new in Symantec Protection Engine

8

About supported protocols for Symantec ProtectionEngine

Table 1-2 lists the supported protocols that client applications can use to sendscan requests to Symantec Protection Engine.

Table 1-2 Supported protocols

DescriptionProtocol

Symantec Protection Engine implements a TCP/IP protocol toprovide scanning functionality to client applications. Thisprotocol is text-based, like HTTP or SMTP. It uses ASCIIcommands and responses to communicate between the clientand the server.

To scan a file, a client connects to the default IP port. It sendsthe file to be scanned and then reads the results of the scan.After the client receives the scan results, the client and serverdisconnect and must initiate a new connection to scan eachsubsequent file.

Native protocol

(Deprecated)

ICAP is a lightweight protocol for executing a remote procedurecall on HTTPmessages. ICAP is part of an architecture that letscorporations, carriers, and ISPs dynamically scan, change, andaugment Web content as it flows through ICAP servers. Theprotocol lets ICAP clients pass HTTP messages to ICAP serversfor adaptation. Adaptation might include some sort oftransformation or other processing, such as scanning or contentfiltering. The server executes its transformation service on themessages and responds to the client, usually with modifiedmessages. The adaptedmessagesmight be eitherHTTP requestsor HTTP responses.

Internet ContentAdaptation Protocol(ICAP)

Remote procedure call (RPC) is a client/server infrastructurethat increases the interoperability and portability of anapplication. RPC lets the application be distributed overmultipleplatforms. The use of RPC frees the developer from having tobe familiar with various operating systems and networkinterfaces.

Symantec Protection Engine uses a proprietary scanningprotocol with the MS-RPC protocol to interface with clientapplications. This protocol is supported only on Windows 2003Server/Windows 2008 Server/Windows 2012 Server. Anyappropriate client can use RPC to communicate with SymantecProtection Engine to request the scanning and repairing of files.

A proprietary remoteprocedure call (RPC)protocol

9Getting StartedAbout supported protocols for Symantec Protection Engine

For more details on the supported protocols, see Symantec Protection EngineImplementation Guide.

Components of Symantec Protection EngineTable 1-3 lists the components that are included on the product CD.

Table 1-3 Product components

Folder nameDescriptionComponent

Symantec_Protection_Engine\The software that youinstall to protect yournetwork fromthreats (suchas viruses), security risks(such as adware andspyware), and unwantedcontent.

Symantec ProtectionEngine

Symantec_Protection_Engine\Silent_Install\

The files that you can useto perform a silentinstallation or upgrade.Also includes responsefiles for Red Hat andSolaris.

Silent installation

Command_Line_Scanner\The software that acts asa client to SymantecProtectionEngine throughthe Symantec ProtectionEngine applicationprogramming interface(API). The command-linescanner lets you send filesto Symantec ProtectionEngine to be scanned.

Command-line scanner

Symantec_Protection_Engine_SDK\The tools anddocumentation that youcan use to create thecustomized integrationsthat use ICAP.

Symantec ProtectionEngine softwaredeveloper's kit

Getting StartedComponents of Symantec Protection Engine

10

Table 1-3 Product components (continued)


Tools\Central_Quarantine\The tool that you use toquarantine infected filesthat cannot be repairedwhen you use the ICAPprotocol or RPC protocol.Symantec CentralQuarantine server lets youisolate unrepairable filesso that threats cannotspread.

Symantec CentralQuarantine server

Tools\LiveUpdate_Admin\The utility that you use toconfigure one or moreintranet FTP, HTTP, orLAN servers to act asinternal LiveUpdateservers. LiveUpdate letsSymantec productsdownload program anddefinition file updateseither directly fromSymantec or from aLiveUpdate server.

For more information, seethe LiveUpdateAdministrator's Guide onthe product CD.

LiveUpdate™Administration Utility

11Getting StartedComponents of Symantec Protection Engine

Table 1-3 Product components (continued)


Tools\SCOM\Management_PackYou can integrateSymantec ProtectionEngine eventswithSystemCenter OperationsManager (SCOM).SystemCenter OperationsManager is a centralrepository that can receivecritical events, errors,warnings, and otherinformation from yourSymantec ProtectionEngine servers.

Preconfigured rules areautomatically createdwhen you import themanagementpack. SystemCenterOperationManagerAgent monitors WindowsEvent log for SymantecProtection Engine eventsbased on criteriamentioned in rules ofManagement pack. Whena rule is triggered, theOperations Manager 2007Agent collects data aboutthe event and forwards itto the System CenterOperations Manager.

For more information, seethe Symantec™ ProtectionEngine Management PackIntegration Guide on theSymantec ProtectionEngine product CD.

SystemCenterOperationsManager 2007(SCOM)Pack

Adobe Acrobat Reader is required to view the reports that are generated in .pdfformat. You can download Adobe Acrobat Reader from http://www.adobe.com/.

Getting StartedComponents of Symantec Protection Engine

12

http://www.adobe.com/

About implementing Symantec Protection Engine forCloud Services

Implementation of Symantec Protection Engine for Cloud Services involves thefollowing process:

■ Ensure that your messaging or caching solution is properly installed andconfigured.For more information about the hardware and system requirements for yourmessaging or caching solution, see your product documentation.

■ If applicable, install the connector code or plug-in for your messaging orcaching solution. You must install the connector on the computer on whichthe messaging or caching solution is installed.For more information about installing and configuring the connector, see thedocumentation for your connector.

■ Install Symantec Protection Engine on a separate computer.Symantec Protection Engine is included on the Symantec Protection Enginefor Cloud Services 7.0 CD.Formore information about installing and configuring the Protection Engine,see the Symantec Protection Engine Implementation Guide on the CD.

■ Configure Symantec Protection Engine.Youmust configure theProtectionEngine before you configure themessagingor caching solution to send files to the Protection Engine.For more information about integrating your messaging or caching solutionwith the Protection Engine, see the appropriate configuration guide.

■ Configure the messaging or caching solution to send files to the ProtectionEngine.For more information about integrating your messaging or caching solutionwith the Protection Engine, see the appropriate configuration guide.

Before you install Symantec Protection EngineInstall Symantec Protection Engine on a computer that meets the systemrequirements. Before you install SymantecProtectionEngine, install and configurethe operating system software and applicable updates for your server. Also ensurethat your operating system software and server work correctly. For moreinformation, see the documentation for your server.

See “System requirements” on page 15.

Before you install Symantec Protection Engine, take the following steps:

13Getting StartedAbout implementing Symantec Protection Engine for Cloud Services

■ On Windows operating system, if you want to use Windows ActiveDirectory-based authentication method to access the Symantec ProtectionEngine console, you must ensure the following:

■ Create or identify an existing security group in the Active Directory thatwould be authorized to access the Symantec Protection Engine console.

■ The server (on which you plan to install Symantec Protection Engine)belongs to the same domain or has trust relationship with the ActiveDirectory, that contains the security group authorized to access theSymantec Protection Engine console.

■ Install Java 2SE Runtime Environment (JRE) 5.0 (update 13 or later), JRE 6.0(update 21 or later), or JRE 7.0 (update 03 or later) on the server. It isrecommended to use JRE 7.0 (update 03 or later).

Note: Symantec Protection Engine supports only 32-bit versions of JavaRuntime Environment. Symantec Protection Engine cannot be installed with64-bit JRE versions.

■ Disable any third-party antivirus products that are running on the server onwhichyouplan to install SymantecProtectionEngine.Youcan turnonantivirusprotection after installation is complete.Symantec Protection Engine scans the files that client applications pass toSymantec Protection Engine. Symantec Protection Engine does not protectthe computer on which it runs. Since Symantec Protection Engine processesthe files that might contain threats, the server on which it runs is vulnerableif it has no real-time protection.Use an antivirus program to protect the server onwhich Symantec ProtectionEngine runs, such as Symantec Endpoint Protection. To prevent scanningconflicts, configure the antivirus programnot to scan the temporary directorythat Symantec Protection Engine uses for scanning.

■ Review the deployment considerations and recommendations. Theserecommendations can enhance your overall performance.

After you complete the installation, perform the post-installation tasks.

For post-installation tasks, see the Symantec Protection Engine ImplementationGuide.

Migrating to version 7.0While installing Symantec Protection Engine, you can choose to upgrade fromthe previous version to version 7.0

Getting StartedBefore you install Symantec Protection Engine

14

Table 1-4 describes the upgrades that Symantec Protection Engine supports.

Table 1-4 Supported upgrades

DescriptionPrevious version number

You can install the upgrade over the existing installation.

When you upgrade from version 5.2, Symantec ProtectionEngine retains all of the settings and values that you haveconfigured.

5.2

You can install the upgrade over the existing installation.

When you upgrade from version 5.1, Symantec ProtectionEngine retains all of the settings and values that you haveconfigured.

5.1

Upgrades fromversion 4.3x or earlier of the product are notsupported. If you want to upgrade a version 4.3x or earlierinstallation, you must first upgrade your installation toversion 5.2x (which does support a direct upgrade fromversion 4.3x), and thenupgrade the version 5.2x installationto version 7.0.

4.3x and earlier

Note: Symantec Protection Engine does not support upgrades from version 5.0.

You must stop the Symantec Protection Engine service before you upgrade thesoftware. If you cancel the upgrade on Solaris after selecting the upgrade type,you must reinstall the previous version.

If youwant to upgrade from version 5.2/5.1 and use security certificates, take thefollowing actions:

■ If youuse the default security files that Symantec ProtectionEngine generated,delete the keystore.public andkeystore.private before youperform theupgradeinstallation.

■ If you use custom security files, you can retain the custom security files.Symantec Protection Engine automatically uses the existing files when youupgrade.

System requirementsBefore you install Symantec Protection Engine, verify that your server meets theminimum system requirements.

15Getting StartedSystem requirements

See “System requirements to install Symantec Protection Engine on Windows”on page 16.

See “System requirements to install Symantec Protection Engine on Solaris”on page 17.

See “System requirements to install Symantec Protection Engine on Linux”on page 18.

System requirements to install Symantec Protection Engine onWindows

The following are the minimum system requirements for installing SymantecProtection Engine on Windows:

■ 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 patchesavailable.

Operating system

Intel or AMD Server Grade Single Processor Quad Core systems orhigher

Processor

4 GB of RAM or higherMemory

5 GB of hard disk space

10 GB of hard disk space for using URL Filtering feature

Disk space

■ Network interface card (NIC) running TCP/IP with a static IPaddress

■ Internet connection to update definitions

■ 100 Mbps Ethernet link (1 Gbps recommended)

Hardware

Getting StartedSystem requirements

16

■ J2SE Runtime Environment (JRE) 5.0 (update 13 or later), JRE 6.0(update 21 or later), or JRE 7.0 (update 03 or later)

It is recommended to use JRE 7.0 (update 03 or later).

Note: Symantec Protection Engine supports only 32-bit versionsof JavaRuntimeEnvironment. Symantec ProtectionEngine cannotbe installed with 64-bit JRE versions.

■ Microsoft Visual C++ 2005 (SP1 or later) redistributable package(x86)

■ One of the following Web browsers to access the SymantecProtection Engine console:

■ Microsoft Internet Explorer 8 or later

Use Microsoft Internet Explorer to access the SymantecProtection Engine console from a Windows client computer.

■ Mozilla Firefox 10 or later

Use Mozilla Firefox to access the Symantec Protection Engineconsole from a Solaris or Linux client computer.

The Web browser is only required for Web-based administration.You must install the Web browser on a computer from which youwant to access the Symantec Protection Engine console. Thecomputer must have access to the server on which SymantecProtection Engine runs.

Software

System requirements to install Symantec Protection Engine on SolarisThe following are the minimum system requirements for installing SymantecProtection Engine on Solaris:

Solaris 10 and 11


Operating system

UltraSPARCProcessor




Disk space




Hardware




If you install the self-extracting JRE, ensure that you note theinstallation location. You must provide the location of the JRE ifthe installer is unable to detect it.








Software

System requirements to install Symantec Protection Engine on LinuxThe following are the minimum system requirements for installing SymantecProtection Engine on Linux:

■ Red Hat Enterprise Linux Server 5.5 (32-bit and 64-bit) and later

■ Red Hat Advanced Linux Server 5.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)


Operating system

Intel or AMD Server Grade Single Processor Quad Core systems orhigher

Processor




Disk space

Getting StartedSystem requirements

18




Hardware

■ Ensure that the following packages are installed:

■ GNU sharutils-4.6.1-2 or later

Use this package to expand the Rapid Release packages.

■ 32-bit GNU libuuid-2.17.2-6 or later

■ ncompress-4.2.4-44 or later

Use this package to expand the Rapid Release packages.

■ GNU C Library (glibc)

■ Initscripts

This package is required for Red Hat Linux only.

■ aaa_base package

This package is required for SUSE only.

■ 32 bit libstdc++ library package



Install the JREusingRedHat PackageManager (RPM). Ensure thatyou note the installation location. You must provide the locationof the JRE if the installer is unable to detect it.








Note: If any of the above package binary is already present on thecomputer and if the installer is still unable to find it, you can add thepath to the binary in LD_LIBRARY_PATH environment variable.

Software


Where to get more informationFor more information about using this product, the following resources areavailable on the Symantec Protection Engine for Cloud Services 7.0 CD at thefollowing locations:

Symantec_Protection_Engine\Docs\Symantec Protection Engine for CloudServices Implementation Guide

You can visit the Symantec Web site for more information about your product.

The following online resources for Symantec Protection Engine and its supportedcaching and messaging devices are available:

http://www.symantec.com/docs/HOWTO77303Latest supported caching and messagingdevices documentation

http://www.symantec.com/enterprise/support/index.jsp

Technical support Knowledge Base, newsgroups, contact information, downloads, andmailing list subscriptions

http://enterprisesecurity.symantec.com/Product news and updates

http://www.symantec.com/security_response/index.jsp

Virus Encyclopedia, which containsinformation about all known threats;information about hoaxes; and access towhite papers about threats

Getting StartedWhere to get more information

20

http://www.symantec.com/docs/HOWTO77303

http://www.symantec.com/�enterprise/support/index.jsp

http://www.symantec.com/�enterprise/support/index.jsp

http://enterprisesecurity.symantec.com/

http://www.symantec.com/�security_response/index.jsp

http://www.symantec.com/�security_response/index.jsp

spe cs getting_started_guide

Education