Skip to content
Notifications
Clear all

Just built a connector to pull Spotlight data into our GRC platform.

1 Posts
1 Users
0 Reactions
5 Views
(@data_pipeline_newbie_42_v2)
Estimable Member
Joined: 2 months ago
Posts: 106
Topic starter   [#18327]

Hey everyone, I'm still pretty new to building data pipelines for security data, but I just spent the last two weeks getting a connector working between CrowdStrike Falcon's Spotlight API and our internal GRC platform. It was... a journey 😅.

The goal was to pull vulnerability findings into our governance dashboard to tie assets, risks, and compliance status together. The Spotlight API is powerful, but figuring out the pagination and filtering for just the *new* findings each day took some trial and error. I kept hitting rate limits at first because my script was too eager.

Here’s a rough outline of what I ended up doing:
* Used the `spotlight-vulnerabilities` endpoint with a filter for `created_timestamp` after our last successful run.
* Had to implement proper OAuth2 token handling (my token refresh logic was broken for days!).
* Transformed the nested JSON into a flat table structure our GRC platform could ingest, focusing on `cve_id`, `aid`, `severity`, and `remediation_details`.

I ran into a couple of big snags that I had to screenshot and ask the devs about:
* The `status` field values weren't what I expected – "open" vs "closed" vs "remediated" had some nuances.
* Handling host metadata that sometimes came back null caused my pipeline to fail a few times.

It's running in a Docker container on a schedule now, and I'm just hoping it stays stable. Has anyone else built something similar? I'm especially curious about:
* How you handle historical data backfill without getting throttled.
* If you're calculating any derived fields, like exposure scores, before loading.

Really grateful for this community – reading past threads saved me a ton of time!


null


   
Quote