OpenText EnCase Endpoint Security

Version: 1.1
Updated: Jul 03, 2023
Collect evidence, create events and investigations, and issue containment actions with EnCase Endpoint Security.
Actions
- Collect Data (Enrichment) - Collect data from an endpoint as evidence during an investigation.
- Collect Memory (Enrichment) - Collect memory from an endpoint as evidence during an investigation.
- Collect Timeline (Enrichment) - Collect a timeline of events from an endpoint as evidence during an investigation.
- Find Items of Interest (Enrichment) - Search for items of interest to an investigation.
- List Investigations (Enrichment) -Gather a list of all investigations.
- Create Event (Notification) - Create a new event.
- Create Investigation (Notification) - Create a new investigation.
- Create Snapshot (Containment) - Create a new snapshot.
- Ban Hash (Containment) - Ban a file.
- Quarantine (Containment) - Quarantine a host.
Configure OpenText EnCase Endpoint Security in Automation Service and Cloud SOAR
Before you can use this automation integration, you must configure its authentication settings so that the product you're integrating with can communicate with Sumo Logic. For general guidance, see Configure Authentication for Automation Integrations.
How to open the integration's configuration dialog
- Access App Central and install the integration. (You can configure at installation, or after installation with the following steps.)
- Go to the Integrations page.
Classic UI. In the main Sumo Logic menu, select Automation and then select Integrations in the left nav bar.
New UI. In the main Sumo Logic menu, select Automation > Integrations. You can also click the Go To... menu at the top of the screen and select Integrations. - Select the installed integration.
- Hover over the resource name and click the Edit button that appears.
In the configuration dialog, enter information from the product you're integrating with. When done, click TEST to test the configuration, and click SAVE to save the configuration:
-
Label. Enter the name you want to use for the resource.
-
Protocol. Select HTTP or HTTPS for the protocol to use.
-
IP/Hostname. Enter your OpenText EnCase host address.
-
Port. Enter your OpenText EnCase port.
-
API Key. Enter an OpenText EnCase API key.
-
Connection Timeout (s). Set the maximum amount of time the integration will wait for a server's response before terminating the connection. Enter the connection timeout time in seconds (for example,
180
). -
Verify Server Certificate. Select to validate the server’s SSL certificate.
-
Automation Engine. Select Cloud execution for this certified integration. Select a bridge option only for a custom integration. See Cloud or Bridge execution.
-
Proxy Options. Select whether to use a proxy. (Applies only if the automation engine uses a bridge instead of cloud execution.)
- Use no proxy. Communication runs on the bridge and does not use a proxy.
- Use default proxy. Use the default proxy for the bridge set up as described in Using a proxy.
- Use different proxy. Use your own proxy service. Provide the proxy URL and port number.

For information about OpenText EnCase Endpoint Security, see the OpenText documentation.
Change Log
- October 3, 2019 - First upload
- July 3, 2023 (v1.1) - Updated the integration with Environmental Variables