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
The node enables management of security policies within the Binalyze AIR platform. Specifically, the "Create Policy" operation allows users to define and add new security policies by specifying details such as the policy name, description, priority, enabled status, associated organization, and custom rules.
This node is beneficial in scenarios where automated or programmatic control over security policies is required, such as integrating policy creation into a larger security orchestration workflow or dynamically adjusting policies based on external triggers.
Practical examples include:
- Automatically creating new policies when onboarding new organizational units.
- Defining policies with specific priorities and rules as part of compliance automation.
- Enabling or disabling policies based on real-time security posture assessments.
Properties
| Name | Meaning |
|---|---|
| Policy Name | The name assigned to 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. |
| Enabled | Boolean flag indicating whether the policy is active (enabled) or inactive (disabled). |
| Organization | Specifies the organization the policy applies to. Can be selected from a list, specified by ID, or by name. Use "0" to apply to all organizations. |
| Rules | JSON array defining the detailed rules of the policy. |
Output
The node outputs JSON data representing the created policy object as returned by the Binalyze AIR API. This typically includes fields such as the policy's unique identifier, name, description, priority, enabled status, associated organization, and the rules defined.
No binary data output is produced by this node.
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 setup.
Troubleshooting
- Invalid JSON in Rules: If the "Rules" field contains malformed JSON, the API call will fail. Ensure that the rules are valid JSON arrays.
- Organization ID Validation: When specifying the organization by ID, it must be a positive number or zero. Invalid IDs will cause validation errors.
- Missing Required Fields: Omitting required properties like Policy Name, Description, or Priority will result in errors.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to create policies.
- Network Issues: Connectivity problems with the Binalyze AIR API endpoint can cause execution failures.
Links and References
- Binalyze AIR API Documentation (for detailed API schema and policy management)
- n8n Documentation (for general node usage and credential setup)