Sophos Central
The Sophos integration brings security events from Sophos Central into UTMStack. Sophos Central provides secure APIs to retrieve event data, and UTMStack reads them with an API credential that you create in Sophos Central Admin. No agent or collector is needed.
How it works
UTMStack signs in to Sophos Central with the credential's Client ID and Client Secret, asks Sophos which tenant and data region the credential belongs to, and reads the Sophos Central SIEM events API every 5 minutes. It reads events, not the separate alerts API.
Events are stored with the data type
sophos-centraland parsed by the shipped pipelinesophos/sophos_central.yaml. UTMStack v12 ships 20 detection rules for this data type; see Sophos Central in the Rules tab.
Before you start
In Sophos Central Admin, you need permission to manage API credentials.
In UTMStack, you need the Administrator role (the
integrations.writepermission). Configuration is saved in the tenant you are working in.The UTMStack server must be able to reach Sophos Central over HTTPS (outbound port 443).
Step 1: Create an API credential in Sophos Central
- 1
- 2
Create a new credential
Click Add Credential. Enter a Name and a Description, select the appropriate Role, and click Add. The credential must be able to read events: a read-only role such as Service Principal Read-Only is enough.
Create the credential in Sophos Central Admin of the account (tenant) you want to monitor. UTMStack reads one tenant per credential; a credential created at partner or enterprise level in Sophos Central does not work here. To monitor several Sophos Central accounts, create one credential in each and add one config group per account.
- 3
Step 2: Connect Sophos Central in UTMStack
Each Sophos Central account connection is a config group. You can add more than one.
- 1
Open the integration
Go to Configure > Integrations, search for
Sophosand open the Sophos card (the one for Sophos Central, not Sophos Xg). The form is at the end of the setup guide, under Add Sophos Central credentials.The guide mentions alerts, but this integration reads only the Sophos Central events API; see How it works.
- 2
Fill in the form
Field What to enter Config group name A name for this connection, for example acme-prod. It cannot be changed later, and it becomes the data source name on the Data Sources page.Client ID The Client ID from Step 1. Client Secret / API Key The Client Secret from Step 1. - 3
Save
Click Add config group. You see "Config group created successfully."
UTMStack does not test Sophos Central credentials when you save them: a wrong Client ID or secret is saved without an error. After saving, check that events arrive (see below). If none arrive, check the Client ID, the secret and the credential's role in Sophos Central.
Check that events arrive
Because the save does not test the credentials, this check is the only proof that the connection works.
- 1
Make sure there is activity
Sophos Central only returns events that happened. In Sophos Central, open Logs & Reports > Events (the event log) and check that recent events exist, for example a scan, a policy change or a sign-in to an endpoint.
- 2
Open the logs in UTMStack
Wait at least 5 minutes, then open the Sophos card again and click View logs. Log Explorer opens with the
sophos-centraldata type for the last 24 hours. - 3
Check the data source
Go to Configure > Data Sources and open the Integrations tab. Your config group is listed by its name. The row is created when you save, and turns Live after the first events are counted, which can take up to 20 minutes. A row that stays Offline while Sophos Central shows recent events means UTMStack cannot read them.
Troubleshooting
Errors do not appear in the web interface, not even a wrong secret. They are written to the logs of the UTMStack event processor on the server, where the integration runs.
| Symptom | Likely cause | Fix |
|---|---|---|
No sophos-central events after 10 minutes | The Client ID or Client Secret is wrong, or the secret was copied incompletely. | Create a new credential in Sophos Central, then edit the config group and paste both values. |
| Still no events with a new credential | The credential was created at partner or enterprise level, or its role cannot read events. | Create it in Sophos Central Admin of the monitored account, with a role such as Service Principal Read-Only. |
| Events stopped after working | The credential was deleted or its secret was renewed in Sophos Central. | Edit the config group and paste the current secret. |
| You also need the full traffic and threat logs of a Sophos Firewall | This integration reads Sophos Central events, not the firewall's own syslog. | Send the firewall's syslog to a UTMStack Collector; see Sophos Firewall (XG). |
| The Integrations row shows Offline although events arrive | The data source's "last seen" time is updated from the ingestion counts, which can take up to about 20 minutes. | Wait 20 minutes and click Refresh. |
Manage config groups
Add more connections: save one config group per Sophos Central account.
Edit: click the pencil icon next to a config group. The name cannot be changed. The secret shows a masked value; leave it as it is to keep the stored secret. Click Update config group.
Delete: click the bin icon. The config group is deleted at once, without a confirmation, and collection stops. The data source it created stays on the Data Sources page; delete it there if you no longer need it.