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 provides integration with Binalyze AIR, a digital forensics and incident response platform. Specifically, the "Acquisition" resource with the "Get" operation allows users to retrieve details about a specific acquisition profile. Acquisition profiles define configurations for remote data acquisitions from endpoints.
This node is useful in scenarios where automated workflows need to fetch acquisition profile information to trigger or manage forensic data collection remotely. For example, security analysts can use it to dynamically select an acquisition profile before starting a remote acquisition task on an endpoint.
Properties
| Name | Meaning |
|---|---|
| Acquisition Profile | The acquisition profile to operate on. Can be selected either from a searchable list of existing profiles or by entering a valid acquisition profile ID manually. |
- The "Acquisition Profile" property supports two modes:
- From List: Select from a searchable list of acquisition profiles fetched dynamically.
- By ID: Enter the acquisition profile's unique identifier (letters, numbers, hyphens, underscores only).
Output
The node outputs JSON data representing the acquisition profile details retrieved from Binalyze AIR. This typically includes all relevant fields describing the acquisition profile configuration such as name, settings, and identifiers.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Binalyze AIR API.
- The node depends on the Binalyze AIR service being accessible and the API token having permissions to read acquisition profiles.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
- Invalid Acquisition Profile ID: If the entered ID contains invalid characters, the node will reject it due to regex validation. Ensure IDs contain only letters, numbers, hyphens, and underscores.
- Profile Not Found: If the specified acquisition profile does not exist or the API token lacks permission, the node may return an error or empty result. Verify the profile ID and API credentials.
- API Authentication Errors: Common errors include invalid or expired API tokens. Re-authenticate or update credentials as needed.
- Network Issues: Connectivity problems to the Binalyze AIR API endpoint will cause failures. Check network access and firewall rules.
Links and References
- Binalyze AIR Official Website
- Binalyze AIR API Documentation (for detailed API usage and acquisition profile schema)