Obsidian Ridge

Integrations

We work with what you already have.

Most small and mid-market businesses already run a handful of security and IT tools. Obsidian Ridge does not ask you to rip and replace — we connect to your existing stack, ingest the signals, and have the SOC review them. Below is a complete picture of what we plug into today.

Endpoints & devices

Endpoints & devices

Where the Managed EDR agent runs. Light, signed, and deployable across mixed fleets.

Windows 10 / 11

Standard Huntress agent

GA

Windows Server 2016+

Includes Domain Controllers

GA

macOS 12+

Apple Silicon and Intel

GA

Linux (RHEL, Ubuntu, Debian, Amazon Linux)

Server workloads

GA

Microsoft Intune

Agent push via Intune policies

Supported

JAMF Pro

Agent push for managed Macs

Supported

Kandji

Agent push for Apple fleets

Supported

Addigy

Agent push for Apple fleets

Supported

Identity providers

Identity providers

Where Managed ITDR watches for the patterns that show up before account takeover.

Microsoft 365 / Entra ID

Full identity threat detection

GA

Google Workspace

Full identity threat detection

GA

Okta

Log forwarding and posture monitoring

Supported

JumpCloud

Available in Complete tier scope

Roadmap

Cloud platforms

Cloud platforms

Cloud workloads ingested into Managed SIEM for unified detection across your stack.

Microsoft Azure

Sentinel logs, Defender for Cloud

GA

Amazon Web Services (AWS)

CloudTrail, GuardDuty, S3 access logs

GA

Google Cloud Platform (GCP)

Cloud Audit Logs, SCC findings

Supported

Cloudflare

WAF events, Zero Trust logs

Supported

Network & perimeter

Network & perimeter

Firewall, DNS, and VPN telemetry feeding Managed SIEM correlation.

Fortinet FortiGate

Syslog ingestion

GA

Palo Alto Networks

Syslog and Cortex XDR

GA

SonicWall

Syslog ingestion

Supported

Cisco Meraki

Syslog and event API

Supported

Cisco Umbrella

DNS security telemetry

Supported

Cloudflare WARP / Zero Trust

Activity logs

Supported

Security tools you may already run

Security tools you may already run

We don't ask you to rip and replace. Existing security tools become signal sources for the SOC.

Microsoft Defender for Endpoint

Coexists with Huntress agent

GA

SentinelOne

Alert ingestion and correlation

Supported

CrowdStrike Falcon

Alert ingestion and correlation

Supported

Sophos / Sophos MDR

Alert ingestion and correlation

Supported

Productivity & SaaS

Productivity & SaaS

Audit-relevant SaaS log sources for compliance and threat detection.

Slack

Audit log forwarding

Supported

GitHub

Audit log and security event ingestion

Supported

Atlassian (Jira, Confluence)

Audit log forwarding

Supported

Salesforce

Available in Complete tier scope

Roadmap

Box, Dropbox, OneDrive

Activity log forwarding

Supported

FAQ

Questions about integrations

What does "GA" vs "Supported" vs "Roadmap" mean?

GA (generally available) means the integration is fully productized and works out of the box on the relevant tier. Supported means we can connect it during onboarding with light configuration work. Roadmap means we can scope it as a custom integration in the Complete tier — typically a one-time setup fee.

I don't see a tool I use. Can you still ingest it?

Probably yes. The Managed SIEM in the Complete tier accepts standard log formats (Syslog, JSON, Webhook, S3 bucket forwarding). If your tool has any kind of log export, we can usually wire it in. Tell us during the briefing.

Do you need admin access to all of these tools?

We need read-only or scoped admin access to ingest logs and see alerts. For most tools, that means a service account with audit-log read permissions — not a global admin. We document exactly what's needed before deployment.

Will adding integrations slow down our existing tools?

No. Most integrations are log-forwarding (one-way), not in-line traffic inspection. The Huntress endpoint agent itself is light — under 50 MB of memory, no kernel hooks, signed by Microsoft.

Don't see your tool?

Most things connect. Tell us what you run.

The Managed SIEM in the Complete tier accepts standard log formats (Syslog, JSON, Webhook, S3 forwarding). If your tool can export logs, we can usually ingest them.

Ask about your stack