Skip to main content

Sophos Central Source


The Sophos Central Source provides a secure endpoint to receive authentication logs from the Sophos Central APIs. It securely stores the required authentication, scheduling, and state tracking information.


To link the endpoint data to the alert, you can map the alert.ManagedAgent.ID field from the alert response with the endpointID field from the endpoint response.


This source is available in all deployments, including the Fed deployment.

Data collected

Polling IntervalData
5 minAlerts, Endpoint data is consumed for alerts with a product value of type endpoint from the Sophos Endpoint API.
5 minEvents


Vendor configuration

You need to have a Sophos account to generated Client ID and Client Secret. Follow the below steps:

  1. From the Sophos Homepage navigate to My Account and log in.
  2. On the Sophos Central Partner Dashboard (depending on your account you may instead have an Organization dashboard).
  3. In the left-hand toolbar, navigate to Settings & Policies > API Credentials > Add Credential.
  4. Give the credential a name, and save the generated Client ID and Client Secret, these are used to configure the integration in Sumo Logic.

Source configuration

When you create a Sophos Central Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure a Sophos Central Source:

  1. In the main Sumo Logic menu, select Manage Data > Collection > Collection.
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Select Sophos Central.
  4. Enter a Name to display for the Source in the Sumo web application. The description is optional.
  5. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM.
  7. (Optional) Fields. Click the +Add Field link to define the fields you want to associate, each field needs a name (key) and value.
    • green check circle.png A green circle with a check mark is shown when the field exists in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema it is ignored, known as dropped.
  8. Client ID. Provide the Sophos Central Client ID you want to use to authenticate collection requests.
  9. Client Secret. Provide the Sophos Central Client Secret you want to use to authenticate collection requests.
  10. Supported APIs to collect. Select one or more of the available APIs, Alerts and Events.
  11. (Optional) The Polling Interval is set for 300 seconds by default, you can adjust it based on your needs. This sets how often the Source checks for new data.
  12. Processing Rules for Logs (Optional). Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
  13. When you are finished configuring the Source, click Submit.

Metadata fields

_siemVendorSophosSet when Forward To SIEM is checked.
_siemProductSophos CentralSet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventID<eventId>Populated by the alert category. This will be one of the following values: azure, adSync, applicationControl, appReputation, blockListed, connectivity, cwg, denc, downloadReputation, endpointFirewall, fenc, forensicSnapshot, general, iaas, iaasAzure, isolation, malware, mtr, mobiles, policy, protection, pua, runtimeDetections, security, smc, systemHealth, uav, uncategorized, updating, utm, virt, wireless, or xgEmail.

JSON schema

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

schemaRefJSON Object{"type":"Sophos Central"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
clientIdStringYesnullProvide the Sophos Client ID you want to use to authenticate collection requests.
clientSecret`StringYesnullProvide the Sophos Secrete you want to use to authenticate collection requests.
supported_apisArray of stringsYesnullDefine one or more of the available APIs to collect: Events, and Alerts.["Events","Alerts"]
pollingIntervalIntegerNo300This sets how often the Source checks for new data.

JSON example

"type":"Sophos Central"
"description":"East field",
"supported_apis": ["Events", "Alerts"],

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "sophos_central_source" {
collector_id =
schema_ref = {
type = "Sophos Central"
config = jsonencode({
"description":"East field",
"supported_apis": ["Events", "Alerts"],
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"

Download example



Click here for more information about Cloud-to-Cloud sources.

Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.