AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation retrieves identity asset data from the Datalake Inventory via a web API. It allows users to query and filter identity assets based on a wide range of optional parameters such as cloud provider details, Active Directory attributes, tags, regions, and more. This is useful for security analysts, IT administrators, or automation workflows that need to fetch detailed identity asset information for monitoring, auditing, or integration with other systems.

Properties

Name Meaning
Additional Query Parameters A collection of optional filters and query parameters to refine the search for identity assets. These include filters on cloud provider organization, object SID, forest, asset criticality, tags, region, resource type, user principal name, and many others. Users can specify values or lists of values to include or exclude (using 'contains', 'not in', 'exists', etc.) to tailor the query results.

Output

JSON

  • items - Array of identity asset objects matching the query filters.
  • totalCount - Total number of items matching the query (if countOnly is false and skipCount is false).
  • cursor - Cursor string for pagination to fetch next set of results if more than 1000 items exist.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard SentinelOne API.
  • Relies on the base URL configured in the node credentials to access the Datalake Inventory API.

Troubleshooting

  • If the node returns authentication errors, verify that the API key credential is correctly configured and has necessary permissions.
  • If no results are returned, check the query parameters for correctness and ensure that the filters are not too restrictive.
  • Pagination issues can occur if 'cursor' is not used properly when iterating over large datasets; use the cursor value returned to fetch subsequent pages.
  • The 'limit' parameter must be between 1 and 1000; setting it outside this range may cause errors.
  • If the API returns errors related to unknown query parameters, verify that the parameter names match those supported by the API.

Links

Discussion