Actions56
- Acquisition Actions
- Asset Actions
- Baseline Actions
- Case Actions
- InterACT Actions
- Organization Actions
- Repository Actions
- Task Actions
- Triage Rule Actions
- User Actions
InterACT → Create InterACT Session
AI-generatedOverview
This node operation creates an InterACT session for a specified asset within an organization, optionally associating it with a case. It is useful for initiating interactive shell sessions and command execution on devices managed within the Binalyze AIR platform. For example, a security analyst can use this node to start a remote session on an endpoint asset to investigate or remediate an incident.
Use Case Examples
- Create an InterACT session for a specific asset by selecting the organization, optionally linking it to a case, and specifying the asset ID or selecting from a list.
- Use the node to automate the creation of interactive sessions on assets during incident response workflows.
Properties
| Name | Meaning |
|---|---|
| Organization | The organization that the asset belongs to. This is required to scope the session creation to the correct organizational context. It supports selection by list, ID, or name. |
| Case | The case to associate with the InterACT session. This is optional and can be selected from a list or specified by ID. |
| Asset | The asset to create the InterACT session for. This is required and can be selected from a list or specified by ID. |
Output
JSON
sessionId- The unique identifier of the created InterACT session.status- The status of the session creation request.sessionUrl- The URL or endpoint to access the created InterACT session.
Dependencies
- Requires an API key credential for authentication with the Binalyze AIR platform.
Troubleshooting
- Ensure the organization ID or name is valid and accessible by the authenticated user.
- Verify the asset ID is correct and belongs to the specified organization.
- If associating a case, confirm the case ID is valid and linked to the organization.
- Common errors may include authentication failures, invalid resource identifiers, or network connectivity issues. Check API credentials and network settings.