Integrations

Cloud integrations

Services that LogPulse reads itself, over their own API. No agent, no forwarder: a read-only credential is enough.

In short
Add a service under Configure → Sources → Cloud with a read-only credential. LogPulse fetches new events every five minutes by default. Each log gets an index for its kind of data, the product as source and a sourcetype of its own. There are 29 integrations, each with its own guide below.

Cloud platforms

Identity and access

Endpoint and EDR

Email and collaboration

Network and web security

Code and DevOps

Frequently asked questions

How does LogPulse collect cloud logs without an agent?
LogPulse signs in to the service with a read-only credential you create there and fetches new events itself, every five minutes by default. Nothing is installed on your side.
Which cloud services can LogPulse read?
29 services: Sophos Central, Cisco Duo, Slack, Thinkst Canary, Wiz, SailPoint Identity Security Cloud, Proofpoint TAP, Netskope, Cisco Meraki, Mimecast, Google Workspace, Google Cloud, Jira and Confluence, GitLab, Cisco Umbrella and Secure Access, Microsoft Defender XDR, CrowdStrike Falcon, SentinelOne, AWS logs in S3, Azure logs via Event Hub, Okta, CyberArk Endpoint Privilege Manager, Microsoft Entra ID, Microsoft 365, AWS CloudTrail, GitHub, Azure DevOps, Railway, Cloudflare.
Where does cloud data land in LogPulse?
In an index for the kind of data (iam, audit, endpoint, email, web, network, firewall, dns, vulnerabilities, cicd), with the product as source and a sourcetype per log. Fields are mapped to data models such as Authentication, Change and Alert.
My service is not on the list. Can I still send its logs?
Yes. Logs from other services can come in through the LogPulse agent, syslog, OTLP or the HTTP API.