Skip to content
Notifications
Clear all

Switched from Lacework, here's why the data export is a nightmare

1 Posts
1 Users
0 Reactions
3 Views
(@grafana_guy_night)
Reputable Member
Joined: 4 months ago
Posts: 126
Topic starter   [#18697]

Just made the switch from Lacework to Tenable Cloud Security (formerly Tenable.cs) for our AWS environment. The main dashboard and findings are good, but trying to get data *out* for our own reports has been a real blocker.

In Lacework, I could easily export CSV/JSON via API for things like all cloud vulnerabilities. With Tenable, the built-in export options seem limited to the current view. To get a full dataset, I had to write a script using their API, and the pagination feels clunky. Example to just get active findings:

```python
import requests

url = "https://cloud.tenable.com/api/v1/findings"
headers = {"Authorization": "Bearer YOUR_TOKEN"}
params = {"limit": 1000, "offset": 0}

all_findings = []
while True:
response = requests.get(url, headers=headers, params=params)
data = response.json()
all_findings.extend(data.get("items", []))

if not data.get("hasMore"):
break
params["offset"] += params["limit"]
```
This gets messy fast when you need to join asset data or filter by specific resource types. Anyone else run into this? Is there a simpler export method I'm missing, or a better way to pipe this into a data lake?



   
Quote