Trend Micro Vision One - Isolate Device
Trend Micro Vision One - Isolate Device isolates an endpoint to prevent network communication and contain potential security threats for:
- Assets returned by the selected query or assets selected on the relevant asset page.
Note
The endpoint must be managed by Trend Micro Vision One and have an active agent to be isolated.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
Note
- Not all asset types are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Aggregated Security Findings.
- See Actions supported for Software.
Required Fields
These fields must be configured to run the Enforcement Action.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
- Use stored credentials from the Trend Micro Vision One adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
-
When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
-
Note
To use this option, you must successfully configure a Trend Micro Vision One adapter connection.
-
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.
Additional Fields
These fields are optional.
- Description - Enter an optional description for the isolation action. This description appears in the Trend Micro Vision One console to provide context for the isolation request.
Connection and CredentialsWhen Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
- Host Name or IP Address - The hostname or IP address of the Trend Micro Vision One server.
- Token - The API token for authentication.
Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
Gateway Name - Select the Gateway through which to connect to perform the action.
APIs
Axonius uses the Trend Micro Vision One Response API - POST /v3.0/response/endpoints/isolate
Required Ports
Axonius must be able to communicate via the following ports:
- TCP port 80/443
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:
The following permissions and requirements are needed:
- A valid Trend Micro Vision One API token with Response permissions
- Permission to isolate endpoints
Version Matrix
This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.
| Version | Supported | Notes |
|---|---|---|
| v3.0 | Yes | Tested with Trend Micro Vision One API v3.0 |
For more details about other enforcement actions available, see Action Library.
Updated about 2 hours ago
