AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation sends a POST request to the Datalake Inventory AI ML API endpoint to retrieve available actions with status for XDR assets. It allows users to filter and query asset data using a wide range of optional query parameters and body fields, enabling detailed and customized inventory analysis. This is useful for security analysts or IT teams who want to programmatically access and analyze asset statuses and available actions in their extended detection and response (XDR) environment.

Properties

Name Meaning
Additional Query Parameters Optional query parameters to filter the asset data returned by the API. These include filters on cloud provider details, regions, coverage status, tags, risk factors, asset status, environment, and many other asset attributes. Users can specify multiple filters to narrow down the results.
Additional Body Fields Optional body fields to further filter the request payload, including lists of inventory IDs to include or exclude.

Output

JSON

  • response - The JSON response from the API containing available actions with status for the filtered XDR assets.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard SentinelOne API.
  • Relies on the '@avantguardllc/n8n-openapi-node' package for OpenAPI integration.

Troubleshooting

  • Ensure the API credentials are correctly configured and have the necessary permissions to access the Datalake Inventory AI ML endpoints.
  • Verify that the query and body parameters are correctly formatted JSON arrays or strings as expected by the API.
  • If the API returns errors related to invalid filters, check that the filter keys and values conform to the API specification.
  • Network connectivity issues or incorrect base URL configuration can cause request failures; verify the baseURL credential parameter.
  • Large or complex queries may result in timeouts or performance issues; consider simplifying filters or paginating requests if supported.

Discussion