Skip to main content

Hubspot logs to chronicle

  • Nov 24, 2023 1:37 PM UTC
  • 5 replies
  • 161 views

Hi,

Is there a way to ingest Hubspot CRM audit logs to collect to Chronicle? I think we can collect them to GCP by Integration Connector. Is there any same method like API ingestion? I saw just non-API and Cloud Storage methods for Hubspot on Chronicle Add Feed page.

5 replies

Forum|alt.badge.img
  • New Member
  • Nov 26, 2023 2:14 PM UTC

Chronicle does not currently provide a direct API ingestion method for HubSpot CRM audit logs. The available methods for ingesting HubSpot logs into Chronicle are non-API and Cloud Storage methods, as mentioned on the Chronicle Add Feed page.

However, it is worth noting that Chronicle supports ingesting logs from Cloud Storage. So, if you can find or develop an Integration Connector that can export the HubSpot CRM audit logs to a supported format (such as JSON or CSV) and store them in a Cloud Storage bucket, you can then configure Chronicle to ingest the logs from that Cloud Storage bucket.

 


Krish_p
Forum|alt.badge.img+3
  • New Member
  • Sep 11, 2026 8:52 AM UTC

hi ​@Robina , is there any guide or document or any reference link how to integrate hubspot with secops?


Krish_p
Forum|alt.badge.img+3
  • New Member
  • Sep 11, 2026 9:03 AM UTC

Hi Team,

could you please suggest the best approach to integrate Hubspot logs with Google SecOps.
 


Bernier Advise
Forum|alt.badge.img

Hi Krish,

To ingest HubSpot logs into Google SecOps (Chronicle SIEM), there is currently no direct standard out-of-the-box connector, so you'll need to set up an API-driven ingestion pipeline.

Here is the standard 3-step architecture for this integration:

1. HubSpot Audit Log Extraction

Leverage the HubSpot Audit Logs API (⁠/settings/v3/audit-logs/⁠) to fetch security events, user activity, login attempts, and permission changes.

Authenticate using a Private App Token or OAuth 2.0 with the ⁠account-info.settings.read⁠ scope.

2. Middleware & Ingestion Pipeline

Choose one of the following methods to ship logs to SecOps:

Google Cloud Native (Serverless): Set up a scheduled Cloud Run job or Cloud Function to query the HubSpot API periodically, write state/checkpoints (to avoid duplicate ingestion), and send payloads directly to the Google SecOps Ingestion API (UDM format).

Chronicle Feed Manager / SecOps Forwarder: Deploy the Google SecOps Forwarder on an internal VM, or configure a webhook server/custom script to fetch HubSpot logs and forward them via syslog or HTTPS webhook endpoints.

3. Parsing and UDM Normalization

Map incoming JSON log fields from HubSpot to Google SecOps Unified Data Model (UDM) fields (e.g., mapping user IDs to ⁠principal.user.userid⁠, actions to ⁠target.resource.name⁠, and IP addresses to ⁠principal.ip⁠).

If using the SecOps Ingestion API, configure a custom parser rule in SecOps if standard parsing isn't automatically applied.


Krish_p
Forum|alt.badge.img+3
  • New Member
  • Sep 11, 2026 9:30 AM UTC

Hi ​@Bernier Advise ,

Thanks for replying, really appreciate it! If you have any reference links or documentation, could you please share them here? It would make it a bit easier for us to understand and proceed.