Configure Webroot for Arctic Wolf monitoring
You can configure Webroot® to send the necessary logs to Arctic Wolf® for security monitoring.
These resources are required:
- A Webroot GSM console account with Super Administrator permissions
Identify your console type
Arctic Wolf retrieves security information from the Webroot API, which is only accessible through the Managed Service Provider (MSP) console. You must identify if you are using the GSM or MSP console to determine next steps.
Convert your GSM console to an MSP console
If necessary, convert your GSM console to an MSP console to access the Webroot API.
- Sign in to the Webroot admin console with GSM Super Administrator permissions.
- In the navigation menu, click .
- In the Advanced Settings section, click Convert.
- In the dialog, select the checkbox, and then click Convert Console.
- Optional: You can complete or skip the MSP console tutorial.
Create Webroot API client credentials
Retrieve the Webroot site keycode
- Sign in to the Webroot admin console.
- In the navigation menu, click Sites.
- For each site that you want Arctic Wolf to monitor, complete these steps:
Retrieve the Webroot GSM keycode
The GSM keycode, also known as the parent keycode, and site keycode are similar but not the same. Both values are required for Arctic Wolf to monitor the site.
- Sign in to the Webroot admin console.
- In the navigation menu, click .
- Copy the Parent Keycode, and then save it in a safe, encrypted location to provide to Arctic Wolf later.
Create a new administrator for the Arctic Wolf Sensor
Provide Webroot credentials to Arctic Wolf
Time-based events are polled with a delay to make sure that data is available. For new deployments, Arctic Wolf begins polling and reviewing activity from approximately one hour prior to configuration success. If API credentials fail, for example due to expired credentials, Arctic Wolf notifies you and requests a new set of credentials. After receiving refreshed credentials, Arctic Wolf can only retrieve data from the previous 12 hours. Provide refreshed credentials within 12 hours of expiry to enable complete data polling and coverage.