Skip to content
Find out how we support MDR.

Skyhigh Security Secure Web Gateway

Log collector

You must have the Network integrations license pack to use this feature.

You can integrate Skyhigh Security Secure Web Gateway (formerly McAfee Web Gateway) with Sophos Central so that it sends data about web access requests to Sophos.

This integration uses a log collector hosted on a virtual machine (VM). Together they're called an appliance. The appliance receives third-party data and sends it to the Sophos Data Lake.

Note

You can add multiple Secure Web Gateways to the same appliance.

To do this, set up your Skyhigh Security Secure Web Gateway integration in Sophos Central, then configure one gateway to send logs to it. Then configure your other Secure Web Gateways to send logs to the same Sophos appliance.

You don't have to repeat the Sophos Central part of the setup.

The key steps are as follows:

  • Configure an integration for this product. This configures an image to use on a VM.
  • Download and deploy the image on your VM. This becomes your appliance.
  • Configure Secure Web Gateway to send data to the appliance.

Requirements

Appliances have system and network access requirements. To check that you meet them, see Appliance requirements.

Configure an integration

To configure the integration, do as follows:

  1. In Sophos Central, go to Threat Analysis Center > Integrations > Marketplace.
  2. Click Skyhigh Security Secure Web Gateway.

    The Skyhigh Security Secure Web Gateway page opens. You can configure integrations here and see a list of any you've already configured.

  3. In Data Ingest (Security Alerts), click Add Configuration.

    Note

    If this is the first integration you've added, we'll ask for details about your internal domains and IPs. See My domains and IPs.

    Integration setup steps appears.

Configure the VM

In Integration setup steps you configure your VM as an appliance to receive data from Secure Web Gateway. You can use an existing VM, or create a new one.

To configure the VM, do as follows:

  1. Enter an integration name and description.
  2. Enter a name and description for the appliance.

    If you've already set up a Sophos appliance, you can choose it from a list.

  3. Select the virtual platform. Currently we support VMware ESXi 6.7 Update 3 or later and Microsoft Hyper-V 6.0.6001.18016 (Windows Server 2016) or later.

  4. Specify the IP settings for the Internet-facing network ports. This sets up the management interface for the VM.

    • Select DHCP to assign the IP address automatically.

      Note

      If you select DHCP, you must reserve the IP address.

    • Select Manual to specify network settings.

  5. Select the Syslog IP version and enter the Syslog IP address.

    You'll need this syslog IP address later, when you configure Secure Web Gateway to send data to your appliance.

  6. Select a Protocol. For SonicOS integration, this must be TCP.

    You must use the same protocol when you configure Secure Web Gateway to send data to your appliance.

  7. Click Save.

    We create the integration and it appears in your list.

    In the integration details, you can see the port number for the appliance. You'll need this later when you configure Secure Web Gateway to send data to it.

    It might take a few minutes for the VM image to be ready.

Deploy the VM

Restriction

If you're using ESXi, the OVA file is verified with Sophos Central, so it can only be used once. If you have to deploy another VM, you must create an OVA file again in Sophos Central.

Use the VM image to deploy the VM. To do this, do as follows:

  1. In the list of integrations, in Actions, click the download action for your platform, for example Download OVA for ESXi.
  2. When the image download finishes, deploy it on your VM. See Deploy a VM for integrations.

Configure Secure Web Gateway

You now configure Secure Web Gateway to send data from its access log to us, using syslog forwarding.

To configure Secure Web Gateway, do as follows:

  1. In Secure Web Gateway, add a rule that makes access log data available to the syslog daemon.
  2. Adapt the rsylog.conf system file to let the daemon send data to a syslog server.

You must do this on every Secure Web Gateway you want to send access log data. You can also send other log data.

The data includes the date and time of a web access request, the user who sent the request, the requested URL, and other information.

You must send the data in TCP protocol and CEF format.

See About Sending access log data to a syslog server.