added
Attack Path Analysis: List Attack Paths
4 months ago by Lance Duvall
A new endpoint has been added to the Tenable Attack Path Analysis API that enables users to retrieve a list of attack path vectors. The new endpoint is described in the following table:
Endpoint | Name | Description |
---|---|---|
GET /apa/api/discover/v1/vectors | List attack paths | Returns a list of attack path vectors. |
The new endpoint supports the following query parameters:
Parameter | Type | Description |
---|---|---|
page_number | Integer | For offset-based pagination, the result set page index to retrieve. If this parameter is omitted, Tenable Attack Path Analysis uses the default value 1 . For example, if the total number of results is 28 and the limit is set to 5, page 2 contains records 6-10. |
run_ai_summarization | Boolean | Indicates whether or not to run the AI summarization for missing paths. Generative AI enables users to better understand attack paths and their associated risk, and it provides additional insight into the assets affected by the attack paths. For more information about generative AI in Tenable Attack Path Analysis, see the Attack Path Analysis Generative AI Best Practices Guide. Note that enabling the AI summarization results in slower response times. |
filter | String | A JSON string filter condition in the following format:{"operator": "$valid_operator", "value": [{}, { "operator": "$valid_operator", "key": "$valid_key", "value": "$value" }]} . The following are valid operators: and , or , is equal to , does not equal , includes , excludes , contains , == , != , < , > , <= , and >= .The following are valid keys: asset_exposure , asset_id , blast_radius , critical_asset , data_source , finding_id , freetext , name , priority , steps , summary , technique , and weakness_id .For example, both of the following examples are valid filters:
|
limit | Integer | The number of records to retrieve. If this parameter is omitted, Tenable uses the default value of 25 . |
sort_field | String | The field to sort the results by. Supported fields for sorting are name and priority . |
sort_order | String | The order to sort the results by, either ascending (asc ) or descending (desc ). |