AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve a specific list related to Defender TVM (Threat and Vulnerability Management). It is designed to fetch data filtered by a tenant identifier, which allows users to obtain targeted security or vulnerability information for a particular tenant environment. This node is beneficial in scenarios where organizations manage multiple tenants or environments and need to programmatically access security lists or reports for each.

Practical examples include:

  • Automating the retrieval of vulnerability lists for different tenants in a multi-tenant security platform.
  • Integrating Defender TVM data into dashboards or workflows for continuous monitoring.
  • Triggering alerts or further processing based on the retrieved list data.

Properties

Name Meaning
Tenantfilter A required string used as a query parameter to filter the list by a specific tenant ID.

Output

The node outputs JSON data representing the retrieved list from the Defender TVM service. The structure corresponds to the API response for the requested tenant-filtered list. This typically includes details about vulnerabilities, assets, or other relevant security information associated with the specified tenant.

If the API supports binary data output, it is not indicated here; thus, the output is expected to be purely JSON.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the resource API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties and handling OpenAPI specifications.
  • The node uses a bundled OpenAPI specification (openapi.json) to define its operations and parameters.

Troubleshooting

  • Missing or invalid Tenantfilter: Since the tenant filter is required, omitting it or providing an incorrect value will likely cause the API call to fail or return no data. Ensure the tenant ID is correct and properly formatted.
  • Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the API key credential is correctly set up.
  • Network or API endpoint issues: Problems connecting to the configured base URL or API server downtime can cause failures. Check network connectivity and API availability.
  • Unexpected API responses: If the API changes or returns unexpected data, the node might not handle it correctly. Review API documentation and update the node if necessary.

Links and References

Discussion