Send Sophos Central logs to LogPulse

Sophos Central events and alerts through the SIEM API: malware and PUA detections, blocked web and applications, isolation, tamper protection and health.

In short
To send Sophos Central logs to LogPulse, add Sophos Central under Configure → Sources → Cloud. LogPulse reads the Sophos Central SIEM API itself, without an agent. Events land in the endpoint index with source sophos and fill the Malware data model.

Overview

How Sophos Central data reaches LogPulse
Vendor
Sophos Central SIEM API
Collect
Integration pollerreads new events, maps the fields
Store
index=endpoint
  1. Sophos Central SIEM API to Integration poller
  2. Integration poller to index=endpoint

LogPulse signs in to Sophos Central with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • A Sophos Central tenant (partner and enterprise accounts: create the credential inside each tenant)
  • An API credential with the Service Principal Read-Only role
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Sophos Central

Field in LogPulseWhere you find it
Client IDIn Sophos Central: Global Settings, API Credentials Management, Add Credential. Choose the role Service Principal Read-Only.
Client secretShown once when you create the credential. Stored encrypted and never shown again.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Sophos Central. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Eventsendpointsophossophos_eventsEvery endpoint and server event: detections, cleanups, web and application control, device and update state.
Alertsendpointsophossophos_alertsThe alerts Sophos raises, with severity, category, the device and the threat.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Sophos Central without changes.

Note: Sophos keeps events and alerts for 24 hours, so a pause of a few hours loses nothing.
Note: Partner and enterprise accounts: create the credential inside each tenant.

Fields and data models

Data modelWhat you get
MalwareDetections with the device, user, threat and what Sophos did.

Field names follow the CIM field names. These are the fields LogPulse sets on Sophos Central events; a field is left out when Sophos Central did not send a value.

  • action
  • alert_id
  • category
  • description
  • dest
  • dest_category
  • dest_id
  • file_hash
  • group
  • id
  • product
  • severity
  • signature
  • src_ip
  • tenant_id
  • threat_id
  • user
  • user_id
  • vendor_action

The original record of Sophos Central is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (endpoint) source IN (sophos)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
Sophos refused the client id and secret.Copy the client ID and secret again from Global Settings, API Credentials Management. The secret is shown only once; create a new credential when you no longer have it.
This is a partner (or organization) credential. Create the credential inside the tenant.Partner and enterprise credentials cannot read the SIEM API. Open the tenant itself and add the credential there.
The SIEM API returned 403. Give the credential the Service Principal Read-Only role.Edit the credential in Sophos Central and choose the role Service Principal Read-Only.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Sophos Central may also simply have had nothing new.

Frequently asked questions

How do I send Sophos Central logs to LogPulse?
Add the Sophos Central cloud integration under Configure, Sources, Cloud in LogPulse and fill in Client ID, Client secret. LogPulse reads the Sophos Central SIEM API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Sophos Central?
A Sophos Central tenant (partner and enterprise accounts: create the credential inside each tenant). An API credential with the Service Principal Read-Only role. Read access is enough for collecting logs.
Which index does Sophos Central data go to?
The index is the kind of data: endpoint. The source is the product: sophos. Each data source has its own sourcetype, listed on this page.
Which data models does Sophos Central fill?
Malware. Detection rules and dashboards written for a data model work on Sophos Central without changes.
Do I lose Sophos events when the integration is paused?
Not for a pause of a few hours: Sophos keeps events and alerts for 24 hours and LogPulse carries on where it stopped.