Add users with the required permissions to investigate incidents and alerts in NetWitness Respond. Users with access to the Respond view need both Incidents and Respond-server permissions. Users with access to configure incident email notification settings need additional Integration-server permissions.
The following pre-configured roles have permissions in the Respond view:
- Analysts: The Security Operations Center (SOC) Analysts have access to Alerting, NetWitness Respond, Investigate, and Reporting, but not system configurations.
- Malware Analysts: Malware Analysts have access to investigations and malware events.
- Operators: Operators have access to configurations, but not Investigate, ESA, Alerting, Reporting and NetWitness Respond.
- SOC_Managers: The SOC Managers have the same access as Analysts plus additional permissions to handle incidents and configure NetWitness Respond.
- Data_Privacy_Officers: Data Privacy Officers (DPOs) are like Administrators with additional focus on configuration options that manage obfuscation and viewing of sensitive data within the system. See the Data Privacy Management Guide for additional information. Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents.
- Respond_Administrator: The Respond Administrator has full access to NetWitness Respond.
- Administrators: The Administrator has full system access to NetWitness Platform and has all permissions by default.
The NetWitness Respond default permissions are shown in the following tables. You need to assign user permissions from both the Incidents and Respond-server tabs, which are the Permissions tab names in the Admin > Security view Add or Edit Roles dialogs. You may want to add additional user permissions for Alerting, Context Hub, Investigate, Investigate-server, and Reports.
Users who configure incident email notification settings also need permissions in the Integration-server tab.
* Data Privacy Officers and Respond Administrators have the respond-server.* permission, which gives them all of the Respond-server permissions.
The Respond Administrator has all of the Respond-server and Incidents permissions.
Users who configure incident email notification settings also need Integration-server permissions. The following table lists the incident notification permissions in the Integration-server tab assigned to each role.
Users who view Event Analysis in Respond also need Investigate-server permissions. The following table lists the Respond Event Analysis permissions required in the Investigate-server tab and the permissions assigned to each role.
Incident Email Notification Settings Permissions
The following permissions are required for Respond Administrators, Data Privacy Officers, and SOC Managers to access incident email notification settings (Configure > Incident Notifications).
- Configure Incident Management Integration
Respond Event Analysis Permissions
The Event Analysis panel in the Respond view shows the Event Analysis view from Investigate for specific indicator events. The following permissions are required to view Event Analysis in the Respond view. These permissions are provided by default for users with the Analysts role.
- Access Administration Module
Respond Role Permission Examples
The following figure shows Respond-server permissions for the default Respond Administrator role. The Respond Administrator role contains all of the NetWitness Respond permissions.
The following figure shows the Incidents permissions for the default Analysts role:
For more information, see "Role Permissions" and "Manage Users with Roles and Permissions" in the System Security and User Management Guide. Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents.
Restrict Access to Incidents
By default, analysts can view all of the incidents, alerts, and tasks in the Respond view. If you have sensitive or restricted information that should not be shared, you can restrict what analysts and other users can see in the Respond view.
If you restrict access to incidents:
- Analysts can only see incidents assigned to them as well as the alerts and tasks associated with those incidents. Likewise, they can only change the status of and add journal entries (notes) to their own incidents.
- Analysts cannot see the Alerts and Tasks tabs in the Respond view (Respond > Tasks and Respond > Alerts are hidden), so they cannot view all alerts and tasks.
- Analysts cannot see the Assignee button or change the assignee of an incident.
- Analysts cannot see the Related Indicators (alerts) panel (Incident Details view > Find Related tab in the left-side panel).
- When adding events to incidents from the Investigate views, users can only add events to incidents to which they have access. The list of incidents to which users can add events only shows incidents that the user can access.
- When creating incidents from the Investigate views, users must have access to those incidents to view them in the Respond view. For example, when creating incidents from the Investigate view, Analysts must assign the incidents to themselves to view them in the Respond view.
To restrict access to incidents:
- Go to Admin > Security and click the Settings tab.
- In the Restrict Access to Incidents section, select Restrict access to incidents for all users, except for users with the roles listed below.
- In the list, add the user roles whose access to incidents should not be restricted.
- Click Apply.
Changes take effect on the next log in to NetWitness Platform.