Tenable Security Center connectivity from Power BI

Hi Rnaval 
Are you using Tenable Security Center (on-prem) or Tenable.io

In either case, wouldn't the relevant REST API be the better option

Hi Rnaval 

Tenable Security Center provides a REST API, so you do not have to continue exporting CSV files manually. API-key authentication is supported using the `x-apikey` request header:

`x-apikey: accesskey=ACCESS_KEY; secretkey=SECRET_KEY;`

For vulnerability data, the usual endpoint is:

`POST https://<your-tenable-server>/rest/analysis`

The request can use a vulnerability query such as `listvuln`, and the results can be paged using `startOffset` and `endOffset`.

A simplified Power Query example would look like this:

```powerquery
let
BaseUrl = "https://your-tenable-server",

RequestBody =
Json.FromValue(
[
type = "vuln",
sourceType = "cumulative",
startOffset = 0,
endOffset = 1000,
query = [
type = "vuln",
tool = "listvuln",
filters = {}
]
]
),

Response =
Json.Document(
Web.Contents(
BaseUrl,
[
RelativePath = "rest/analysis",
Headers = [
#"x-apikey" =
"accesskey=YOUR_ACCESS_KEY; secretkey=YOUR_SECRET_KEY;",
#"Content-Type" = "application/json"
],
Content = RequestBody
]
)
),

Results = Response[response][results],
Output = Table.FromRecords(Results)
in
Output
```

Because this is a POST request with a custom authentication header, configure the Power BI Web data source as **Anonymous**; the API authentication is supplied by the header. Power Query supports POST requests through `Web.Contents`, although POST requests can only use the Anonymous credential mode.

A few important considerations:

* Do not leave production API keys hard-coded inside a PBIX file.
* Add pagination, because one request will probably not return the complete vulnerability dataset.
* If Tenable Security Center is hosted inside your network, scheduled refresh in Power BI Service will require an on-premises data gateway with network access to the Tenable server.
* The gateway machine must trust the Tenable HTTPS certificate.
* For a large environment, the more reliable architecture is a scheduled API extraction into SQL, a lakehouse, or another staging layer, and then connect Power BI to that storage. Direct API access from Power BI is reasonable for a proof of concept, but it can become slow and difficult to maintain at scale.

Therefore, yes—the API is the alternative to CSV. I would first test `/rest/currentUser` to verify the API keys, then build the required `/rest/analysis` query and pagination.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.