|Applies To||RSA Product Set: NetWitness Endpoint (ECAT)|
RSA Product/Service Type: NetWitness Endpoint (ECAT)
RSA Version/Condition: 4.1.x.x, 4.2.x.x
Platform (Other): SQL 2014 Standard/Enterprise, SQL 2012 Standard/Enterprise, SQL 2008 Standard/Enterprise
|Issue||It is recommended that NetWitness Endpoint and Microsoft SQL Server be installed on the same physical server. However, this is not always feasible for various reasons. When NetWitness Endpoint is installed on a physically separate server from the SQL database, permissions become more complicated. The following details the permissions requirements for Windows/Active Directory and Microsoft SQL Server when NWE and SQL are on separate servers.|
|Tasks||There are 4 services accounts that must have appropriate permissions, 3 folders that require configuration and SQL privileges that must be correct if NetWitness Endpoint is to function correctly. You must also share both the QueuedData and Files directories to allow ConsoleServer, SQL Server and SQL Agent to access them remotely. The API Server service does not need access to these shares. In cases where Console Server and API Server services are running under the same account the additional permissions do not impact performance. Remote users of the UI will need access to the Files directory as well.|
|Resolution||Example of limiting ‘sysadmin’ privileges:|
For the purpose of installing, the user will need to be sysadmin. Let’s call him Adam. Adam will then be able to login to NetWitness Endpoint UI because he is sysadmin on the DB. Adam should create another user within “Users and Roles” in the NetWitness Endpoint UI - let’s call him Bob, and add the role of ECAT Admin to him. Then we can drop the sysadmin rights from Adam. Bob can create a new user from within the ECAT UI for Adam and give him the role of ECAT Admin. These two users will then be able to add users and change roles at will. Not a single human will have sysadmin.