AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node performs a POST request to the Datalake Inventory Identity API endpoint to retrieve or query asset identity data based on complex filtering criteria. It is useful for security analysts or IT asset managers who need to fetch detailed identity information about assets, filtered by various attributes such as account IDs, group IDs, site IDs, resource types, and criticality. For example, it can be used to query all critical access control systems within specific sites or accounts, supporting pagination and sorting.

Properties

Name Meaning
Additional Query Parameters Optional query parameters to further filter the request, including lists of Account IDs, Group IDs, and Site IDs.
Filter A required JSON object defining detailed filtering criteria for the asset identities, including fields like cloud provider organization, object SIDs, resource types, asset criticality, pagination (limit, skip), sorting, and many other asset attributes.
Additional Body Fields Optional additional JSON fields to include in the request body, allowing for extended or custom data parameters.

Output

JSON

  • response - The JSON response from the API containing the filtered asset identity data, including metadata such as pagination cursors and the list of matching assets.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard SentinelOne API.
  • Depends on the '@avantguardllc/n8n-openapi-node' package for request handling.
  • Uses the base URL and headers configured in the node credentials.

Troubleshooting

  • If the API returns authentication errors, verify that the API key credential is correctly configured and has sufficient permissions.
  • Malformed JSON in the 'Filter' or 'Additional Body Fields' properties can cause request failures; ensure valid JSON syntax.
  • Pagination parameters like 'limit' and 'skip' must be set correctly to avoid empty or incomplete results.
  • Network or connectivity issues to the API endpoint can cause timeouts or errors; check network access and base URL configuration.
  • If the response is empty or missing expected data, review the filter criteria to ensure they match existing assets.

Discussion