Webroot SecureAnywhere

Webroot SecureAnywhere

Perch integrates with Webroot SecureAnywhere to provide access to data for Endpoint Protection, DNS Protection, and Security Awareness Training subscription services. Perch uses the Webroot API to automatically ingest the log data into Perchybana for use.

Getting Started

To allow Perch to work with your Webroot configuration, we will need several key pieces of information:

  1. The Username and Password of a user that has access to the Webroot SecureAnywhere Console.
  2. A Client ID and Client Secret generated for Perch API Access.
  3. The Parent Keycode for the configured site.

All of these can be found or created by logging in to your Webroot Anywhere account.

Client ID and Secret

To access the Webroot API, Perch will need a Client ID and Secret Key that identifies Perch as a valid access point. You can generate this information from your Webroot Anywhere dashboard by going to Settings, and selecting API Access in the submenu.

Select API Access from Settings

To generate a new key pair,

  1. Click “New.”
  2. Enter a Name and Description (e.g. Perch Logging).
  3. Click “Create.”

Create new API Credentials

Once Webroot has created the key and secret for you, it will be displayed.


This is the only time you will be able to see your secret key, so be sure to copy it down somewhere safe. If you lose it, you will need to regenerate it and provide the new key to Perch to continue using your integration.

Display API Credentials

GSM Parent Keycode

The Parent Keycode can be found in Settings, under Account Information. You will need this code to configure your Perch Integration.

GSM Keycode

Input Credentials

From your Organizations settings page,

  1. Install Webroot SecureAnywhere integration.
  2. Input the “Client ID” and “Client Secret” to their respective input boxes.
  3. Input the Username and Password of the GSM console user.
  4. Input the GSM Parent Keycode.
  5. Click “Save and Test” to verify your credentials.

Perch Authentication

Configure Site

Once the credentials have been verified, configure and enable the log collection by selecting a site from the dropdown menu and toggling log collection on (the switch should be purple).

Configure Integration