RSA NetWitness

Version: 1.19
Updated: Feb 28, 2024
Query RSA NetWitness Incidents, Events.
Actions
- Get list Alerts NetWitness Daemon (Daemon) - Automatically get Alerts from NetWitness.
- Retrieve Alert Details (Enrichment) - Retrieve alert details for the specified NetWitness incident.
- Retrieve Incident Details (Enrichment) - Retrieve NetWitness incident details.
- Search Incidents (Enrichment) - Search NetWitness incidents.
Configure RSA Netwitness 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.
-
Host. Enter your NetWitness host.
-
Port. Enter your NetWitness port.
-
Username. Enter the username of a NetWitness admin user authorized to authenticate the integration.
-
Password. Enter the password for the admin user.
-
Incident ID. Enter a Netwitness incident ID.
-
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 Netwitness, see the NetWitness documentation.
Change Log
- November 21, 2018 - First upload
- July 23, 2021 - New action added
- September 7, 2021 - Actions updated
- July 13, 2023 (v1.18)
- Updated the integration with Environmental Variables
- Changed fields visibility
- Updated Daemon compatibility
- February 28, 2023 (v1.19) - Updated code for compatibility with Python 3.12