AvantGuard - SentinelOne icon

AvantGuard - SentinelOne

AvantGuard - SentinelOne

Actions682

Overview

This node operation retrieves aggregated application risk data from the Application Management resource via a web API. It allows users to query and filter applications based on various criteria such as detection dates, vendors, severities, endpoint details, and more. This is useful for security analysts or IT administrators who want to monitor and assess application risks across their environment, enabling targeted risk management and remediation efforts. For example, a user can fetch applications detected within a specific date range that have critical severity or filter by vendor to focus on specific software providers.

Properties

Name Meaning
Additional Query Parameters A collection of optional filters and parameters to refine the API request. These include filters like countOnly (to return only the total count), detection date ranges, vendor names, application types, severities, endpoint identifiers, pagination controls (limit, skip, cursor), sorting options, and other risk-related attributes. Each parameter corresponds to a query parameter sent to the API to customize the data retrieval.

Output

JSON

  • applications - An array of aggregated application objects matching the query filters, each containing risk and detection details.
  • totalCount - The total number of applications matching the query, if requested.
  • cursor - Cursor string for pagination to retrieve the next set of results.

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

  • If the API returns authentication errors, verify that the API key credential is correctly configured and has necessary permissions.
  • If no data is returned, check the filter parameters for correctness and ensure that the query matches existing data.
  • Pagination parameters like 'cursor' and 'skip' must be used correctly to iterate over large datasets; misuse may result in missing data.
  • Invalid date formats in detection date filters can cause API errors; ensure timestamps are in ISO 8601 format.
  • Setting 'countOnly' to true will return only the total count without application details, which may be confusing if expecting full data.

Discussion