AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation allows users to patch (update partially) an existing Application Baseline Rule in the AvantGuard ConnectSecure system. It is useful when you want to modify specific fields of an application baseline rule without replacing the entire object. For example, you might update the list of denied applications or adjust tag inclusions/exclusions for a particular baseline rule.

Common scenarios include:

  • Updating security policies by modifying which applications are denied.
  • Adjusting company or tag filters that determine the scope of the baseline rule.
  • Changing whether the rule applies globally or to specific subsets.

Properties

Name Meaning
X USER ID The user identifier making the request. This is required and sent as a header X-USER-ID.
Additional Body Fields Optional fields to include in the PATCH request body:
- Data JSON object containing fields such as denied_applications, include_company, exclude_company, is_global, ignore_tags, and include_tags. These control the details of the baseline rule.
- Id Numeric identifier of the Application Baseline Rule to update.

The "Data" field expects a JSON string representing the partial data to update on the baseline rule. Example structure:

{
  "denied_applications": "[]",
  "include_company": "[]",
  "exclude_company": "[]",
  "is_global": false,
  "ignore_tags": "[]",
  "include_tags": "[]"
}

Output

The node outputs the response from the API after patching the Application Baseline Rule. The output is structured as JSON under the json property and typically contains the updated baseline rule details or confirmation of the update.

No binary data output is expected from this operation.

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 X-USER-ID header must be provided to identify the user performing the update.

Troubleshooting

  • Missing or invalid X-USER-ID header: The API requires this header; ensure it is set correctly.
  • Invalid JSON in "Data" field: The "Data" property must be valid JSON. Errors parsing this will cause the request to fail.
  • Incorrect or missing Id: The baseline rule ID must be specified and valid; otherwise, the API will not know which rule to update.
  • API authentication errors: Ensure the API key credential is valid and has permissions to update baseline rules.
  • Network or connectivity issues: Verify the base URL and network access to the AvantGuard API endpoint.

Links and References

Discussion