Onboarding from Web.Cloud to Web Security Service

book

Article ID: 171196

calendar_today

Updated On:

Products

Web Security Service - WSS

Issue/Introduction

Customers moving from the Symantec Web.Cloud to Symantec Web Security Service (WSS) can refer to this article as a step-by-step on how to configure their Threatpulse Portal. 

Resolution

  1. Register your Threatpulse Portal Account
    1. The first step in configuring your Threatpulse Portal is to register your Primary Administrator user. 
    2. Following the document below, you'll be provided with steps to register your initial user for your Threatpulse account: 
      1. https://support.symantec.com/en_US/article.TECH249536.html
  2. Import Policy
    1. Once you've registered your Primary Administrator, you'll be brought to the configuration page. 
    2. Should you choose to do so, you will be allowed the option to Import your policy into WSS right away. 
    3. Following the documentation below, you'll be provided with steps to import your existing policy, either During Registration or Post-Registration:
      1. http://portal.threatpulse.com/docs/sol/AccessMethods/deploy/webcloud/webcloud_landing.htm
  3. Setup User Accounts
    1. Once you have move beyond the initial configuration page, you now have access to the rest of your Threatpulse Portal. 
    2. A common next step is to configure additional users to access and/or administer your Threatpulse account. 
    3. Utilizing the documentation below, you can add users to any of the following roles: Administrator, Report User or Reviewer: 
      1. http://portal.threatpulse.com/docs/sol/Solutions/Admin/UserMgmt/adm_addadmin_ta.htm
  4. Setup Network Locations
    1. During the import of your Web.Cloud Policy, you are given the option to migrate static addresses for web routes.
    2. In WSS these are labeled as Locations. 
    3. You have the ability to configure multiple varieties of Locations within Threatpulse.
    4. The documentation below provides a walkthrough on the configuration and deployment of these Location types: 
      1. Firewall/VPN: https://portal.threatpulse.com/docs/am/AccessMethods/deploy/onpremise/firewallvpn/fwvpn_select.htm
      2. Proxy Forwarding: https://portal.threatpulse.com/docs/am/AccessMethods/deploy/onpremise/proxy/prxy_select_ta.htm
      3. Explicit Proxy: https://portal.threatpulse.com/docs/am/AccessMethods/deploy/explicit/explicit_select.htm
  5. Setup User Authentication
    1. Once your policy is imported, you may want to add the functionality of user and group based authentication. 
    2. The documentation below provides a matrix for selecting the proper Authentication Method (based on Access Method), and how to configure each Auth Method: 
      1. https://portal.threatpulse.com/docs/am/AccessMethods/Concepts/AuthDetail/about_authentication_co.htm
  6. Configuring SSL Interception
    1. Once your locations, policy and authentication are setup, the next logical (and major) configuration will be for SSL Interception. 
    2. Enabling SSL Interception allows WSS to perform policy checks, examine contents and to decrypt HTTPS connections. 
    3. The following documentation provides information on how SSL Interception works, how to configure and enable interception, and includes ways to troubleshoot the service: 
      1. https://portal.threatpulse.com/docs/am/Solutions/ManagePolicy/SSL/about_ssl_co.htm

 

Once you've completed these tasks, you should have a fully functioning, policy enforcing environment.  

In the event that you have questions about any of the individual tasks above, please contact Symantec Network Protection Support.