Actions99
- InterACT Actions
- Notification Actions
- Organization Actions
- Task Actions
- Policy Actions
- Repository Actions
- Setting Actions
- Triage Rule Actions
- User Actions
- Acquisition Actions
- API Token Actions
- Asset Actions
- Auto Asset Tag Actions
- Baseline Actions
- Case Actions
- Evidence Actions
Overview
This node allows you to manage security policies within the Binalyze AIR platform. Specifically, the "Update Policy" operation lets you modify an existing policy's details such as its name, description, priority, enabled status, associated organization, and rules.
Use cases include:
- Updating a policy's priority to change its precedence.
- Modifying the description or name for clarity or compliance.
- Enabling or disabling a policy without deleting it.
- Adjusting the JSON rules that define the policy's behavior.
- Assigning the policy to a specific organization or making it global.
Practical example: You have a security policy that enforces endpoint scanning frequency. You want to update its priority to ensure it runs before other policies and add new rules to cover additional threat vectors.
Properties
| Name | Meaning |
|---|---|
| Policy | The target policy to update. Can be selected from a list of existing policies or specified by ID. |
| Policy Name | The new or updated name of the policy. |
| Policy Description | A textual description explaining the purpose or details of the policy. |
| Priority | Numeric priority of the policy; higher numbers indicate higher priority in evaluation order. |
| Enabled | Boolean flag indicating whether the policy is active (true) or inactive (false). |
| Additional Fields | Collection of optional fields: - Organization: The organization this policy applies to (select from list, by ID, or by name). Use "0" for all organizations. - Rules: JSON array string defining the policy rules. |
Output
The node outputs JSON data representing the updated policy object as returned by the Binalyze AIR API. This typically includes fields such as the policy's ID, name, description, priority, enabled status, organization association, and rules.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR platform.
- The node depends on the Binalyze AIR API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Invalid Policy ID: If specifying the policy by ID, ensure it only contains letters, numbers, hyphens, and underscores. Errors will occur if invalid characters are used.
- Malformed Rules JSON: The "Rules" field must be a valid JSON array string. Invalid JSON will cause the update to fail.
- Permission Issues: Ensure the API key has sufficient permissions to update policies.
- Organization ID Errors: When specifying an organization, use a positive number or "0" for default/global. Invalid IDs will cause errors.
- API Connectivity: Network issues or incorrect API credentials will prevent successful updates.
Links and References
- Binalyze AIR API Documentation
- JSON Syntax Guide (for formatting the rules field)