sophos-central

Automate Sophos Central API operations for endpoints, alerts, SIEM events, XDR queries, and firewalls.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill sophos-central-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sophos-central
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/skills/sophos-central
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill sophos-central-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve? Working with the Sophos Central API requires juggling OAuth2 token flows, regional host resolution, partner/tenant header conventions, and inconsistent pagination styles across endpoints. This Skill encodes that entire workflow so you can query and manage your Sophos estate without re-reading API documentation each time. ## Core Features & Use Cases - Endpoint management: List and filter endpoints by health, isolate or de-isolate devices, trigger scans, and manage tamper protection via the Endpoint API. - Alert triage and SIEM export: Search and act on alerts through the Common API, and pull rolling event/alert feeds through the SIEM API for Splunk or Sentinel ingestion. - Threat hunting: Run XDR Data Lake SQL queries for historical hunts or Live Discover osquery against live devices, plus manage Central-registered firewalls and firmware. - Use Case: During incident response, ask to isolate all endpoints matching a hostname pattern — the Skill resolves the tenant region, finds the device IDs, shows you the target list, and bulk-isolates them with a ticket reference comment. ## Quick Start Ask the assistant to list all Sophos endpoints with bad or suspicious health status using your SOPHOS_CLIENT_ID and SOPHOS_CLIENT_SECRET environment variables.

Frequently Asked Questions about sophos-central

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate with the Sophos Central API?

Authenticate by POSTing client credentials to https://id.sophos.com/api/v2/oauth2/token with grant_type=client_credentials, then call /whoami/v1 to get your tenant ID and regional API host. The included sophos_client.py script handles this flow automatically using SOPHOS_CLIENT_ID and SOPHOS_CLIENT_SECRET environment variables.

How do I isolate endpoints using the Sophos Central API?

Isolate endpoints by POSTing to /endpoint/v1/endpoints/isolation with enabled=true, a comment, and a list of up to 50 endpoint IDs. Resolve hostnames to IDs first using hostnameContains or search filters, and confirm the target list before isolating since it affects production devices.

What is the difference between Sophos SIEM API, XDR Query, and Live Discover?

The SIEM API exports a rolling 24-hour event feed for tools like Splunk or Sentinel. XDR Query runs SQL against the Data Lake for up to 30 days of historical telemetry. Live Discover runs osquery directly on online endpoints for real-time investigation of processes, files, and registry.

Why does the Sophos Central API return 401 or 403 errors?

A 401 on the token endpoint means wrong client ID or secret, while 401 on tenant APIs usually means a missing X-Tenant-ID header or wrong regional host. A 403 indicates the credential role is too weak, such as a ReadOnly role attempting POST actions.

Can partner credentials manage multiple Sophos tenants?

Yes, partner and organization credentials enumerate tenants via /partner/v1/tenants or /organization/v1/tenants on the global host, then call each tenant's own apiHost with X-Tenant-ID. Throttle requests when iterating many tenants to avoid partner-level 429 rate limits.

What are the limitations of the Sophos SIEM event export?

The SIEM API only exposes a 24-hour data availability window, so you must poll at least every few hours and persist the next_cursor between calls. For history beyond 24 hours, use the XDR Data Lake or Common API alerts instead.