AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation deletes a specific Application Baseline Rule by its unique identifier. It is useful in scenarios where you need to programmatically remove outdated or incorrect baseline rules from your security or monitoring system to maintain accurate application behavior profiles.

For example, if an application baseline rule is no longer valid due to changes in the application or environment, this node can be used to delete that rule automatically as part of a workflow.

Properties

Name Meaning
X USER ID User Id (string) - identifies the user making the request; sent as a header X-USER-ID. This is required.
Id id (number) - the unique identifier of the Application Baseline Rule to delete. This is required.

Output

The output JSON typically contains the response from the API after attempting to delete the specified Application Baseline Rule. This may include confirmation of deletion or error details if the operation failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard ConnectSecure service.
  • The node uses the base URL and headers configured in the credentials.
  • The operation depends on the external AvantGuard ConnectSecure API endpoint for deleting application baseline rules.

Troubleshooting

  • Missing or invalid X USER ID header: The API requires a valid user ID header; ensure it is provided and correctly formatted.
  • Invalid or non-existent id: If the rule ID does not exist, the API will likely return an error indicating the resource was not found.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • Network or connectivity issues: Verify network access to the API endpoint.

Common error messages might include:

  • Unauthorized or forbidden errors due to missing/invalid credentials.
  • Not found errors if the specified rule ID does not exist.
  • Bad request errors if required parameters are missing or malformed.

Resolving these usually involves verifying input parameters, credentials, and network connectivity.

Links and References

Discussion