Configuring SSL between Symantec Endpoint Protection Manager and the clients

Article:HOWTO81056  |  Created: 2012-10-24  |  Updated: 2014-07-10  |  Article URL http://www.symantec.com/docs/HOWTO55351
Article Type
How To

Product(s)

Subject


Configuring SSL between Symantec Endpoint Protection Manager and the clients

Symantec Endpoint Protection Manager uses an Apache Web site to communicate with clients and provide reporting services. The Web site uses HTTP for all communications. HTTP is an unencrypted protocol and does not provide for the confidentiality or integrity of the communications over it. You can configure the Symantec Endpoint Protection Manager Apache Web site to use a Secure Sockets Layer (SSL) certificate to sign and encrypt data using an HTTPS connection.

Table: Configuring SSL communication to the client

Step

Action

Description

1

Check that the default SSL port is available

In some networks, port 443 may already be bound to another application or service. Before you enable SSL communication, you must check to see if the default port (443) is available.

See Verifying port availability.

2

Change the default SSL port as needed

If port 443 is not available, choose an unused port from the high port range (49152-65535). Adjust the server configuration to use the new port.

See Changing the SSL port assignment.

3

Enable SSL communication to the client

Edit the Apache httpd.config file to allow SSL communication to the client. By default, SSL traffic uses port 433. You may need to change the default port if it is already used.

See Enabling SSL communication between the management server and the client.

See Supported and unsupported migration paths to Symantec Endpoint Protection.

See Migrating from Symantec AntiVirus or Symantec Client Security to Symantec Endpoint Protection 12.1 or later.



Legacy ID



v57069738_v81626096


Article URL http://www.symantec.com/docs/HOWTO55351


Terms of use for this information are found in Legal Notices