AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve firewall rules associated with a specific asset. It is designed to fetch detailed firewall rule data for an asset identified by user ID, optionally filtered or paginated using query parameters.

Common scenarios where this node is beneficial include:

  • Auditing or monitoring firewall rules applied to assets in a network.
  • Integrating firewall rule data into security dashboards or reports.
  • Automating compliance checks by retrieving current firewall configurations.

For example, a security analyst could use this node to programmatically pull all firewall rules for a given asset and then analyze them for unauthorized access patterns.

Properties

Name Meaning
X USER ID The User ID identifying the asset whose firewall rules are to be retrieved.
Additional Query Parameters Optional filters and controls for the query:
- Condition: Filter condition string.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data representing the firewall rules retrieved from the API for the specified asset. The structure typically includes details about each firewall rule such as source, destination, ports, protocols, and action (allow/deny).

If the API supports binary data (e.g., exporting rules as files), the node would handle it accordingly, but based on the provided code and properties, the output is primarily JSON-formatted firewall rule data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled within the node for request building.

Troubleshooting

  • Missing or invalid User ID: The node requires a valid "X USER ID" header; ensure this is provided and correct.
  • API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Query parameter issues: Incorrectly formatted or unsupported query parameters may cause API errors; double-check the values for "Condition", "Skip", "Limit", and "Order By".
  • Network or connectivity problems: Ensure the base URL is reachable and there are no firewall restrictions blocking the request.
  • Empty or unexpected responses: If no firewall rules are returned, confirm that the asset exists and has associated firewall rules.

Links and References

Discussion