RSA NetWitness Platform Known Issues

Document created by RSA Link Admin Employee on Feb 27, 2019Last modified by Sudha Ashok on Jan 7, 2021
Version 195Show Document
  • View in full screen mode

To find out if any known issue is fixed, refer to the Fixed Issues section in the Release Notes for the appropriate release.

You can sort this list by clicking on the column headings.




ComponentsTitle, Problem and WorkaroundFound In / Exists InFixed VersionTracking Number

Title: After upgrading from to 11.5.1, unable to log in to NetWitness Platform.

After you upgrade from version to 11.5.1 and reboot NetWitness Platform, NetWitness login fails with Admin server not reachable error.


To resolve the issue, do the following steps.

   1. Stop rsa-nw-admin-server service.
       systemctl stop rsa-nw-admin-server.service
   2. Log in to nw-shell.
   3. Run the bellow command.
       offline » reconstruct-keystore --service admin-server

       The output looks like below.
       Added service alias for admin-server chain from /etc/pki/nw/service/rsa-nw-admin-       

       server.chain file
       Key entry with alias netwitness ca is not found in the admin-server keystore
       Adding key entry for alias nw-saml in the new keystore
       Saving the keystore - [OK]
       Successfully reconstructed keystore. New file is located at: /etc/netwitness/admin-     

   4. Exit from nw-shell.
   5. Change the directory to admin-server.
       cd /etc/netwitness/admin-server
   6. Backup the existing keystore file.
       mv keystore.p12 keystore.p12.backup
   7. Replace keystore.p12 with successfully

       reconstructed keystore at

       cp keystore.p12
   8. Set permissions to keystore.p12.
       chmod 640 keystore.p12
       chown netwitness:netwitness keystore.p12
  9. Start rsa-nw-admin-server service.
      systemctl start rsa-nw-admin-server.service
 10. Restart the web application server service jetty.
       systemctl restart jetty



Title: UEBA Azure AD Logs events cannot be queried.

Problem: The device.type = 'microsoft_azure_signin_events' cannot be queried as it is not supported.

Workaround: None


NW Server

Title: Unable to push feeds with a feed definition XML file in 11.5

Problem: Custom feed deployment fails when an XML Feed File is used. The same XML file used to work in the previous versions.




Title: Cursor No Longer Shows On Login Page

Problem: When the log in page loaded, there is no cursor in any fields while some of the previous versions have the username field in focus.

11.4.x, 11.5.x

Packet Decoder

Title: Verification of packetdb compression that we aren't observing working

Problem: Packetdb compression does not work for pcapng format. This is expected behavior as compression only works with the native NetWitness databse format. A warning will be added to 11.5.2 to indicate that compression is not supported with pcapng format.

11.4.x, 11.5.x


Title: UI Text Does Not Make Sense For PKI Certificates

Problem: On the Admin > Security > PKI Settings tab, below the PKI Authentication Based Status window, the following text appears:
"Before you enable PKI Authentication, you must add the configure Server CA Certificate in the trust store. At least one external authentication system/method must be enabled with an external group and mapped to an Administrator role."
To avoid the confusion, the text will be changed as

"Please Note: Before you enable PKI Authentication, you must have at least one Trusted CA configured. At least one external authentication system/method must also be enabled with an external group and mapped to an Administrator role."

11.4.x, 11.5.x





Title: As of, exporting meta from Investigate includes all fields instead of limiting to selected meta group

Problem: Exporting meta from Investigate includes all meta fields while it should only export the meta data for the currently selected meta group.

11.4.x, 11.5.x




Packet Decoder

Title: TLS decryption to support RFC 7627 (extended master secret)

Problem: Decrypting sessions with a private key which uses TLS_RSA_WITH_AES_256_CBC_SHA, returns "Encountered bad padding while decoding record."

11.4.x, 11.5.x11.5.2




Title: Customer is seeing performance issues on new broker will hang during investigation.

Problem: The UI hangs when trying to run a query under Investigate and sometimes it fails to load meta keys. The issue goes away for a while when the broker service is restarted.








New Health and Wellness

Title: New Health and Wellness dashboard view is not displayed when you log in to NetWitness Platform as an Active Directory (AD) user.

If an AD group is configured with an Administrator role in NetWitness Platform and you log in as an AD user (associated with the AD group), the New Health and Wellness dashboard is not displayed when you pivot to Dashboards.

Workaround: None 



Title: Legacy Events View does not process event time.

Legacy Events View uses collection time and not the event time. Now, when the user preference for Query Time is set to Event Time and the user issues a text search, if the link in the body of the page or the table footer is used for a refined search in Legacy Events View then the Start Time and End Time passed to Legacy Events View will be for the event time. The search might not display the desired results as Legacy Events View does not use the event time.

Workaround: It is recommended that you modify the time to the desired time range in order to see the expected results.



Title: The User Profile view displays data for inactive users.

If a user is not active for the past 30 days, no new data is displayed in the Modeled Behavior tab. However, the last days older data is not deleted and is displayed for the inactive user.

Workaround: None



Title: Update status stays in “In Queue for Update” state and does not change.

While upgrading the NetWitness Platform hosts, for one or more hosts the update status remains in “In Queue for Update” state and does not change.


To resolve the issue, do the following steps.

  1. SSH to NW Admin Server.
  2. Run the following command on the NW Admin Server for the host that is in “In Queue for Update” state for long time.
    upgrade-cli-client --upgrade --host-addr <host-ip> --version <version number>

    <host ip>: IP address of the host displayed in the NetWitness Platform user interface for the host that is in “In Queue for Update”.

    <version number>: Version to which you want to upgrade. If you are upgrading to version, the version number will be

11.4.x, 11.5,

Investigator - Thick Client

Title: SSL Packet Decryption not working on Investigator Thick Client v11.4


Investigator Thick Client 11.4 fails to decrypt SSL packets as 1024 bit private keys are not supported.





Title: Events not displayed when using query prefix

Problem: Events are not displayed when using a query prefix. The issue in only noticed when investigating into a broker.

Packet Decoder

Title: cert.thumbprint and ja3 not always computed

Problem: The meta keys Ja3/Ja3s and cert.thumbprint are not getting generated for TLS sessions after enabling SSL fingerprint by adding HTTPS="cert.sha1=true ja3=true ja3s=true" to the parser options.





Title: warm standby - nwsetup-tui failed and does not set the IP address configured

Problem: nwsetup-tui script on warm/standby server fails to run, and does not set the IP address configured.

11.3.x, 11.4.x11.5



Log Decoder

Title: Invalid EPOC Timestamp with a year outside of range 1400-9999 breaks Msearch

Problem: Msearch breaks and returns "Year is out of valid range: 1400..9999" when the raw log has incorrected formatted EPOC timestamp.

11.3.x, 11.4.x11.5SACE-13572
Context hub

Title: Converting Feed to ContextHub List failed

Problem: Deploying a custom feed using a csv fails with an error "Converting Feed to ContextHub List". Workaround: disable mongo authentication in /etc/mongod.conf and set the flag " failIndexKeyTooLong" to false, restart the mongo service and then deploy the feed. Contact RSA Support. A custom hot fix may be required.





Log Collector

Title: 11.3 LC has significant TCP Syslog performance problems compared to 10.6.6 LD using the same source

Problem: 11.3 Log Collector shows around one quarter of syslog collection rate compare to 10.6 Log Collector.

11.3.x, 11.4.x, 11.5




Title: Problem in the UEBA backup-restore script

Problem: UEBA backup script fails due to the elasticsearch dump file being temporaily created in /etc/elasticsearch/backup causing the / partition to be 100% full.

11.3.2, 11.4.x11.5





Title: NW 11.4.0 - Admin server rabbitmq serviec runs out of file descriptors

Problem: The RSA NetWitness appliance's RabbitMQ service appears not to be processing even though the service is still running. When performing a netstat on the server there are a large number of connections, possibly in the thousands, associated with RabbitMQ (beam.smp) process.

Refer to 000038886 - RabbitMQ file descriptor limit reached in RSA NetWitness Platform 11.4.x 





Log Decoder

Title: Issues doing full search text in investigation

Problem: Log Decoder service crashes while running msearch query on raw logs

11.4, 11.5



Endpoint Agent

Title: 11.4.1 Advanced Agent causing Windows Pseudo Console apps to hang

Problem: After Endpoint agent is running for a few minutes, any appplications that use  the Windows Pseudo Console, CONpty, stop working unless they are run as an administrator. Restarting the deviceep service, uninstall the Endpoint agent, or rebooting the host fix the issue for a short whileuntil the issue recurs.,, 11.5.1



NW Server

Title: Login Banner not working after upgrade to 11.4

Problem: After upgrading to 11.4, the configured login banner does not pop up.

11.4.x, 11.5




Packet Decoder

Title: Query on the content of mail returns an error.

Problem: Email content msearch query fails with "ERROR Message: An error occurred searching service: Connection to service is closed …"

11.4.x11.4.1.2HF, 11.5.1



ESA Correlation Service

Title: Esper behavior with helper functions isOneOfIgnoreCase / isNotOneOfIgnoreCase

Problem: The helper function, 'isOneOfIgnoreCase' or 'isNotOneOfIgnoreCase', for array meta key 'email_src' cause the rule deployment to fail using the rule builder. Advanced EPL rule can be deployed but causes some false positives.

11.3.x, 11.4.x11.5.1



Log Decoder

Title: Log Decoder service is core-dumping at restart. 

Problem: Some parsers or app rules(e.g. for log forwarding) cause the log decoder service to crash during a service restart.

11.3.x, 11.4.x11.4.1.3, 11.5



Health and Wellness

Title: Historical graph not showing graph yet showing numbers when you hover the mouse

Problem: Selecting other than 'Current Day' from a Historical Graph in Health & Wellness->System Stats Browser does not draw graph although hovering the mouse in this white space displays the expected numbers.




ESA Correlation Service

Title: Test Rule does not generate alert for the event.

When testing a Rule in the New Advanced EPL panel, does not generate alert for the event.

Cause: If you are testing any Rule that has meta key defined as type 'short', the Test Rule will not generate alert for the event.

Workaround: None

11.5,, 11.5.1, 11.5.2ASOC-103061
Event Stream Analysis

Title: After upgrading to version 11.5, the ESA correlation server does not aggregate events from the configured data sources.

To resolve the issue, do the following steps.
In the NetWitness Platform user interface,

  1. Go to Configure > ESA Rules.
    ESA Rules panel is displayed with Rules tab open.
  2. In the Rules tab options panel, under Deployments, select a deployment.
  3. In the Data Sources section, select the data source and click the edit icon in the toolbar.
  4. In the Edit Service dialog, type the password for that data source.
  5. Click the Test Connection button to make sure that it can communicate with the ESA service and then click OK.
    Note: Do the above procedure for all the configured data sources.
  6. After you finish making changes to the deployment, click Deploy Now to redeploy the ESA rule deployment.
11.511.5.0.1, 11.5.1ASOC-103097
UEBATitle: When performing a rerun, UEBA deployments with the TLS schema will not trigger alerts for two weeks.
Problem: When your UEBA deployment contains the TLS schema and you add any other schema to it or if you add the TLS schema to your UEBA deployment, a UEBA rerun is required. During the UEBA rerun, no alerts are generated for any data sources. For UEBA deployments with TLS, the historical data processed is limited to 14 days and thus the data collected in these two weeks (14 days) becomes a part of the learning period and will be used to build the baseline for the models.
For example, if you are processing data for a period of time, and then decide to add another schema such as authentication and your deployment contains TLS, a UEBA rerun is required. The rerun is performed on all existing schemas along with the newly added schema and so during these two weeks of rerun, no alerts are triggered.
Workaround: None
Context Hub

Title: Context Hub service goes offline when multiple users load the Investigate > Navigate view
Problem: If multiple users try to load the Investigate > Navigate view, the Context Hub service goes offline. This is because RabbitMQ queues Context Hub messages resulting in the service to go offline.
Workaround: You must check the contexthub-server logs (/var/log/netwitness/contexthub-server/contexthub-server.log) and do any one of the following:

  • If there is an Out of Memory issue:
       - Increase the RAM of the Context Hub service Java process to 16 GB by editing the -Xmx option available in /etc/netwitness/contexthub-server/contexthub-server.conf
    In JAVA_OPTS, search for the -Xmx option.”For example, edit the entry as follows:
    Where 16G represents 16GB space.
       - Restart the Context Hub service.
  • If there is no Out of Memory issue, you must restart the Context Hub service.
Event Stream Analysis / UpgradeTitle: Position tracking does not get migrated for data sources with a deployment name that contains @ or _ characters at the end of the deployment name.
Problem: If you have an ESA rule deployment that is sessions behind and the deployment name contains @ or _ characters at the end of the name, during the migration to 11.5.0, position tracking gets lost and the sessions that were behind do not get analyzed.
Workarounds: If the sessions in your ESA rule deployment are up to date, you can remove @ or _ from the end of the deployment name, redeploy the deployment, and then upgrade to 11.5.0.
If the sessions in your ESA rule deployment are always behind and you cannot change the deployment name, wait until this position tracking issue is fixed before you upgrade.

Title: The Classic user interface fails to start if the NW Server is rebooted after performing an upgrade init command.

Problem: After performing the upgrade init command on the NW Server and rebooting the NW Server, the Classic user interface does not start up.

Solution: Perform the upgrade on the NW Server again using the command line instructions described in "Appendix A. Offline Upgrade Using CLI" in the "Upgrade Guide for RSA NetWitness Platform 11.5". Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents.

UEBATitle: After upgrading UEBA from 11.3 to 11.5, the saved filters in the UI do not work.
Problem: After you upgrade, the entities that were saved as filters in NetWitness Platform Version 11.3 are displayed in version 11.5 (User > Entities), but the data cannot be retrieved and the user interface does not respond when clicked.
Workaround: To solve this issue, you must delete the old filters and create them again, if needed.
UEBATitle: After upgrade from 11.2 or 11.3 to 11.5, adapter logs are not written.
Problem: After you upgrade from NetWitness Platform Version 11.2 or 11.3 to 11.5, flume uses an incorrect library to write logs. The logs are written to slf4j-log4j12-1.7.25.jar instead of logback-classic-1.2.3.jar due to which the adaptor logs are not written.
Workaround: To solve this issue, you must delete the slf4j-log4j12-1.7.25.jar libraries from the flume library directory available on the UEBA machine using the following commands:
rm /var/netwitness/presidio/flume/plugins.d/PresidioStreamingSource/libext/slf4j-log4j12-1.7.25.jar and rm /var/netwitness/presidio/flume/lib/slf4j-log4j12-1.7.25.jar
Threat IntelligenceTitle: Post failover recurring custom feeds are failing.
Problem: On failover, recurring custom feeds that were created before the failover are failing and are not getting pushed to the core.
Workaround: Edit and save the failed recurring feeds.
New Health and Wellness

Title: Logging out from the New Health and Wellness dashboard logs you out from the NetWitness UI.
Problem: If you log out from the New Health and Wellness dashboard, it also logs you out from the NetWitness Platform UI.

Workaround: None. Log in to NetWitness Platform again.


Title: Continuous scans fail if the host name is used for the source host.

Problem: If the continuous scan configuration uses the host name for the source host instead of the host's IP address, the Malware continuous scan fails.

Workaround: Change the source host name to the IP address in the Source Host field on the Malware Analysis configuration page on the General tab in Continuous Scan Configuration. For more information, see the "Malware Analysis Configuration Guide".

Core Services

Title: Issue with logging UUID's or obsolete IP addresses in core services system log files.

Problem: A core service (for example, a Broker or Concentrator service) that has been configured to aggregate or connect to another NetWitness Platform component host may not reflect the latest IP address or hostname of the remote host in the service's system logs. This can occur after configuring an aggregation connection to a newly installed NetWitness Platform component host, or after updating the IP address or hostname of an existing NetWitness Platform component host.
Workaround: Restart the affected core service hosts which have an aggregation connection to either the newly-installed host or the host whose IP address or hostname has changed.
After a core service IP changes, it may be necessary to restart the ESA Correlation service or redeploy the ESA rule deployments for the logs to reflect the correct IP.

Event Stream ManagementTitle: On upgrade from 11.3 to 11.5, there is inaccurate data on ESM manage page.
Problem: When you upgrade from 11.3 to 11.5, the last update time gets updated internally, but changes are not propagated to the ESM Manage page. This can cause event count to be inaccurate, which can also impact any alarms that are set.
Workaround: Restart the collectd service.

Title: Filter Events Panel Shows Unexpected Results for Query Containing an Unwrapped OR

Problem: When you use OR in a query in the Events view and then drill into the result using a left-click option from the Events Filter panel, the new filter is added with an AND, without adding parentheses around the existing filters that use a logical OR. This gives different results than expected when compared to Navigate view and Legacy Events view results.

Workaround: When adding to a query in the Events panel, whether via left or right click in the Filter Events panel or linking from outside Events, the existing filter must be enclosed in parentheses if there is a top-level, unwrapped OR, either as its own operator or inside a complex filter. For example, service = 80 OR service = 443 AND sourcefile = 'email.pcap' will not return expected results. Edit the filter to enclose the logical OR statement in parentheses as follows: (service = 80 OR service = 443) AND sourcefile = 'email.pcap'. If the filter is service = 80,25 AND filename = ‘invoice’, enclose it in parentheses as follows: (service 80,25) AND filename =‘invoice’.

To enclose the logical OR expression in an additional set of parentheses; select the two filters in the query bar, right-click one of them, and select Wrap in parentheses in the drop-down menu.

NW ServerTitle: NetWitness Platform User Interface Disconnects During Host Discovery
Problem: During host discovery and when services are updating, the UI disconnects briefly. This is caused by nginx restarting.
Workaround: Wait for a few minutes for the UI to reconnect when nginx is restarted.
11.4.x, 11.5ASOC-100247
Core ServicesTitle: Customizing the index level to IndexNone for keys that are part of entities can result in errors during index lookup.
Problem: Customizing the index level from IndexValues to IndexNone for meta keys that are part of entities requires that those meta keys be excluded from the entities. Failing to exclude the meta keys results in errors during index search operations (for example, msearch).
Workaround: For example, if the context meta key index level is changed from IndexValues to IndexNone, then exclude the context meta key from the corresponding entities (for example, context.all). Since context is a default meta key, you would override the context.all entity in the index-concentrator-custom.xml file and exclude the context meta key from the entity.
After this update, the context meta key and the context.all entity would be displayed as shown in the following example in the index-concentrator-custom.xml file.
<key description="Context" name="context" format="Text" level="IndexNone" defaultAction="Closed"/>
<entity description="All Context Keys" name="context.all"><keyref name="context.src"/><keyref name="context.dst"/></entity>
11.3.x, 11.4.x, 11.5SACE-13570/
AdministrationTitle: RabbitMQ Erlang Process and Memory SpikeProblem: RabbitMQ memory, connections, and Erlang process leaks occur if one or more component hosts are offline or shut down, or if federation links were not deleted on the RabbitMQ server for component hosts that were removed from the UI.
  1. Remove federation links corresponding to component hosts that are offline, shutdown or deleted:
    a. Log into https:<IP of NW Server>:15671 and go to Admin > Federation Upstreams.
    b. Select the upstream name corresponding to the component host that is either removed from the UI or that was taken offline or shutdown, and select Delete this Upstream.
   2. Restart RabbitMQ server on NW Server: systemctl restart rabbitmq-server
   3. When the offline hosts are brought back online or powered on, log in to NW     
       Server and refresh the component hosts that were brought online using nw-
       manage: nw-manage --refresh-host --host-key <Component Host
11.4.x.x, 11.5ASOC-93699
Log DecoderTitle: Log parse rule highlighting is not working for Analysts and Data Privacy Officers
Problem: Analysts and Data Privacy Officers role users don't have the parsers.manage permission and as a result are restricted from viewing log highlighting and getting log device types from the log decoder.
Workaround: To be able to view log parse rule highlighting in the Log Parser Rules view, grant the parsers.manage permission on all Log Decoders to all users who require this ability.
To be able to add, deploy, update, and delete parsers in the Log Parser Rules view, users must be granted the parsers.manage permission on all Log Decoders.
Use Admin > Log Decoder service > View > Security Users and Roles to manage privileges.
Event Stream AnalysisTitle: Multiple Users Can Edit an ESA Rule Deployment at the Same Time and Overwrite Changes
Problem: If two users modify the same ESA rule deployment by adding or removing rules, whoever clicks Deploy Now first overwrites the changes of the other user.
Workaround: Ensure that only one user at a time is making changes to an ESA rule deployment.
11.4.x and earlier versions11.5SACE-12736

Title: Permissions to manage meta groups and column groups in Investigate do not apply in Investigate.
Problem: The investigate-server.metagroup.manage and investigate-server.columngroup.manage permissions should control the ability of a user role to add, delete, edit, and clone meta groups and column groups. However, users are not prevented from adding, deleting, editing, and cloning meta groups and column groups in Investigate.

Workaround: None.

RespondTitle: UEBA Sends Alerts to Respond After Decommissioning the UEBA Host
Problem: In NetWitness Platform 11.5, if a UEBA host is decommissioned (such as removed from (Admin > Hosts) but remains powered on, if UEBA alerts are generated they will continue to be forwarded to Respond.
Workaround: Administrators should power off the decommissioned UEBA host as soon as possible after decommissioning it from the user interface.
Raid Tool Script

Title: Raid Script Tool "" fails when encounters a bad drive.

Problem: Raid Script Tool "" fails when it encounters a drive is in a 'UBad' state.
Event Source Management

Title: Event Source Monitoring tracking wrongly after upgrading to

Problem: After upgrading to 11.4.1.x, false alarms are triggered for High threshold and no alarm is triggered for Low threshold.








Title: Endpoint agent not being assigned a policy when more than 3 IPs are assigned to same NIC on endpoint.

Problem: Endpoint agent is not being assigned a policy when more than 3 IP addresses are assigned to the same NIC on the endpoint agent host.






Title: Malware Analysis License appears to be expired on UI.

Problem: The license server fails to parse the Malware-Analyis entitlements as it expects a different feature name, and so the license appears to be expired on the Admin UI.








Title: REST API Results for Countdistinct are not complete on Broker.

Problem: On a 'passthrough' Broker ( a Broker connected to just one upstream device) the countdistinct aggregate function does not work correctly in when used in the SDK query API.






Title: Endpoint Server does not detect process at Z drive.

Problem: Scanning Endpoint hosts does not find processes that are run from the drive letter "Z".







Title:  Single Sign-On authentication Implementation Failure

Problem:  Single Sign-On authentication does not work although the Admin server is correctly configured.






Title: Endpoint Agent in Insights mode crashes on Red Hat/CentOS 8.x

Problem: Endpoint agent in Insights mode crashes when installed on Redhat/CentOS 8.1. When the agent is switched to Advanced mode, it starts to work normally.







Title: Packet Decoder's capture process stops with the 'packet pool depletion' alarm.

Problem: When HTTP2 header parsing is turned on, then Decoder would hang on HTTP2 parser causing packet capture to go down.








Title: Higher entitled usage for throughput licenses is noticed after upgrading to

Problem: Data filtered by App rules is still counted as captured bytes causing higher entitled usage for throughput licenses after upgrading to /decoder/stats/capture.appfilter.bytes does not increment.






Title: Investigate-HOSTS page does not show all IP addresses of Endpoint agent on Mac.

Problem: Investigate-HOSTS page does not display the IP address if its interface has MAC address, 00:00:00:00:00:00. This can occur when the Mac host is connected via VPN.



Log Decoder

Title: Index Language merge handler doesn't update entities from Index definition files on Log Hybrid Retention 

Problem: The language merge handler which exists for decoder during /index save () call doesn't merge entities which are loaded from Index definition files. Due to this problem, the changes made to index keys are reverted back to the old settings.

Workaround: Remove the index save scheduler entry and use automatic Index save using /index/config/save.session.count.





Custom Feeds

Title: The first line in a CSV file is removed when a custom feed is deployed as Non IP type.

Problem: When a custom feed is deployed as Non IP type, the first line in the source csv file is missing from the deployed csv file under /etc/netwitness/ng/upload/tempxxx.



Title: Feed Selection for Groups does not have previously pushed out groups check marked.

Problem: When you edit the feed, the previously selected and deployed device groups are not selected, making it difficult to understand which are deployed.

Title: Unable to add the "accessInvestigateUsers" to a role via the GUI.

Problem: When tried to add  "accessInvestigateUsers" permission to the user in  Admin>Security>Roles tab, the permission "accessInvestigateUsers" does not available.


Title: adding/Editing a recurring feed only validates the hostname in the URL path, not the filename or path when clicking Verify.

Problem: Custom feed verifies only the host name in the URL path and does not verify the filename or path.

Title: PAM Kerberos authentication fails after upgrading to

Problem: After upgrading to 11.4, unable to login to NetWitness Platform user interface using PAM authentication.


Title: NW - Not able to deploy recursive feed on Decoders group.

Problem: After upgrading to 11.4, unable to deploy the recursive feeds on the Decoder group.


Title: NW - credential mismatch - mixing users of different roles between admin and non-admin functions.

Problem: When the user logs in to NetWitness Platform, the permissions of the user who previously logged in is applied.

Title: UI is sometimes very slow.

Problem:The NetWitness Platform user interface response is very slow and takes up to 30-45 seconds to work.

Title: Rabbitmq service on Endpoint Hybrid fails to start in NetWitness 11.4.

Problem:After upgrading to 11.4, Rabbitmq service does not start.
Work Around: To resolve the issue, follow the below steps. 
1. On the UI of the NwAdmin, remove the failed Endpoint Log Hybrid from the hosts page
- Ensure that the UUID of the failed Endpoint Log Hybrid is no longer present in the output of the command orchestration-cli-client --list-hosts
2. Via ssh session on the failed Endpoint Log Hybrid
- Execute the command tar -zcvf /tmp/endpoint-ng-bkup.tar.gz /etc/netwitness/ng
- SCP this file to a safe location that is not on the failed Endpoint Log Hybrid
- Execute the command cat /proc/scsi/scsi and save the output
- Execute the command ls -ld /sys/block/sd*/device and save the output
- Execute the command pvscan and save the output
 -Execute the command lsblk and save the output
- Execute the command cat /etc/fstab and save the output
3. On the esxi/vcenter open the main information page for the failed Endpoint Log Hybrid
- Under the 'Hardware Configuration' window expand all the virtual hard drives and note the 'Controller' entry for each as well as the Capacity.
- We now need to compare the SSH commands we captured as well as the capacity and SCSI controller IDs so we know exactly which VMDKs need to be brought over. We do not need the VMDKs that contain the VGs 'netwitness_vg00*' or 'VolGroup00*'.
4. Politely Power off the failed Endpoint Log Hybrid
5. Create a new VM using OVA
6. Via console session execute the command nwsetup-tui and follow on screen prompts
- During this the user will be prompted for network information, at this point please enter the IP of the failed Endpoint Log Hybrid
7. After nwsetup-tui run is completed go to the UI of the NwAdmin and discover the service.
- After the service is discovered, install the new Endpoint Log Hybrid from the UI
8. Once the new Endpoint Log Hybrid is installed politely power off the device.
9. Copy/move the VMDKs from the failed Endpoint Log Hybrid to the new Endpoint Log Hybrid
- Should only be moving 10 VMDKs total
- A copy would be best here, but may not be possible because of capacity constraints. If this is the case a move is accetable.
10. Once the copy/move of the VMDKs to the new Endpoint Log Hybrid is completed we need to add these hard drives to the VM.
- On the vcenter/esxi going to 'edit settings' on the vm and selecting 'add hard disk' -> 'existing hard disk'
 - do this for all the available hard disks that were moved over, should be 10 total.
11. After the 10 VMDKs have been added to the new Endpoint Log Hybrid power it on and SSH to it
12. A pvscan should show the added VMDKs
13. Append the lines from the failed Endpoint Log Hybrid output of /etc/fstab that contain the additional drive information to the new Endpoint Log Hybrid /etc/fstab
- Test this configuration with mount -a to ensure no errors occur
14. Run the command df -hP and ensure all mount points are present and sizes are expected.
15. [Optional] Stop the concentrator and logdecoder services
systemctl stop nwconcentrator
systemctl stop nwappliance
systemctl stop nwlogdecoder
systemctl stop nwlogcollector
16. [Optional] From the earlier tar.gz file, extract whatever backup information the customer feels is important (NOTICE: DO NOT BRING ANY OLD CERTS/KEYS/PKI THINGS FROM OLD VM).
- They can bring over things like /etc/netwitness/ng/NwConcentrator.cfg if they would like. Up to them.
17. [Optional] Start the concentrator and logdecoder services
systemctl start nwconcentrator
systemctl start nwlogdecoder
systemctl start nwlogcollector
systemctl start nwappliance


Title: Backup script v 4.4 and 4.5 gives verify puppet cert validity on SA 10.6.6.
Problem: After running the backup script version 4.5 on a 10.6.6 system, an error "verify Puppet Certs validity on SA Server" is displayed.


Title: NW Recovery Tool ignore Custom Meta Group and Investigation Profiles.
Problem: When running the NetWitness Recovery Tool (NRT), the custom Meta Groups and Profiles are not imported as a part of the restoration process.

Title: Threatgrid and RSA Cloud connection not working post upgrade to NW
Problem: (Malware Analysis) After upgrading to, the Threatgrid module is not working and the RSA Cloud connection is not working via HTTP Proxy.

Title: On new install, the mongo sa.repo table does not show repo is downloaded.
Problem: After installing version, the mongo sa.repo table does not show that the repo is downloaded even though /var/netwitness/common/repo/ is available.

Title: Content issue possible customer is seeing HTTP 400 Errors.
Problem: Not able to extract file in the NetWitness Platform user interface, if the file is an attachment of a mail.

Title: Files not extracted from SMB Session.
Problem: Unable to extract files from an SMB2 session due to the recent changes in the SMB2 protocol.


Title: Packet Decoder with very low session rates and capturing at 9.6G.
Problem: Packet Decoder has very low session rates and capturing at 9.6G.
Log Decoder

Title: Log Decoder Forwarding Configuration Issue.
Problem: Syslog forwarder forwards only the logs that have meta attached to them and have the forward flag set in the Application Rule.


Title: Upgrade to is causing an impact when rebooting Series 6 packet Decoders and packet Hybrids.
Problem: Some times, when rebooting the Decoder or Decoder Hybrids, the Decoder service hangs during restart and becomes unresponsive.
Log Decoder

Title: issues with proofpoint collection since upgrade from 10.6 to 11.3.
Problem: After upgrading to 11.3 or later, Log Collector does not receive logs from the Proofpoint event source.
Log Decoder

Title: WinRM bookmarks returning 1 for a certain event channel stops collection across all channels.
Problem: WinRM channel bookmark is returning 1 as the PULL response and corrupts the bookmark file.
Log Decoder

Title: using ssl syslog for logstash event source , crashes the nwlogcollector on VLC.
Problem: When the syslog event source is changed to syslog over SSL from Logstash, Log Collection service crashes.

Event Stream Analysis

Title: Needed API improvements to obtain actual sessions.behind per node (conc/decoder) on ESAs.
Problem: Users are able to retrieve the actual number of sessions.behind per data source on an ESA using esa-client on version 10.6.x. But this feature is no longer available in 11.3.

Event Stream Analysis

Title: Enrichment utilizing context hub list does not remove values which no longer exist in the list.

A Context Hub enrichment in an ESA Rule creates alerts for the older values that are deleted.

This issue occurs when the list from which the Context Hub Enrichment is created is a recurring one with the Overwrite option. When the values are overwritten by new values, ESA alerts should not be triggered for the older values.

Title: Compressed payload not displayed in Respond for text recon.

Compressed payloads not displayed when using text reconstruction in Respond. In 11.3.2 and 11.4, you may encounter a scenario when using packet reconstruction within Respond for network sessions containing compressed (for example, gzip) payloads.


Title: Risk Score is not getting calculated as the event generated in Respond doesn't have a Checksumsha256.

Respond may stop processing alerts when Endpoint file alerts do not contain a SHA256 Checksum. In 11.3.2 and 11.4, you may encounter Respond stopping the processing of alerts when handling certain alerts containing Endpoint events not containing a SHA256 hash of the offending file. This results in a failure to calculate risk scores for alerts and, subsequently, errors when attempting to process subsequent alerts.

Warehouse Connector

Title: Warehouse Connector - Add SFTP Destination with SSH Key Passphrase.
Problem: Unable to connect to the destination when the Warehouse Connector uses SFTP passphrase.
Health and Wellness

Title: Incorrect PSU status on H&W when actually one PSU is failed on S5 Hybrid.
Problem: PSU shows incorrect status on the Health & Wellness view, when one PSU fails on the S5 Hybrid.
Health and Wellness

Title: - H&W alarm on Endpoint Loghybrid Logcollector - LogCollector Virtual System Resources Exhausted.
Problem: - H&W alarm on Endpoint Loghybrid Logcollector - LogCollector Virtual System Resources Exhausted.
Health and Wellness

Title: Fan/Temperature information doesn't display on H&W System Stats Browser using Series 6 hardware.
Problem: ADMIN > Health & Wellness > System Stats Browser tab, does not display Fan status and System Temperature.

Title: Brasil No longer follows Daylight Savings Time - Update Moment Timezone Libraries for investigation.
Problem: After Brazil stopped using Daylight Saving Time, there is a one-hour discrepancy between the configured Profile timezone (Americas/Sao Paulo GMT -3) and the timezone used to display time in the Investigate and Respond views (Americas/Sao Paulo GMT -2).

Title: Wrong closing xml tag when exporting logs from the UI.
Problem: When logs are exported in XML format from the Events view or the Legacy Events view, the logs have incorrect closing tags. The closing tag is <Logs/> instead of the correct closing tag, </Logs>.


Title: Issues investigating off of a archiver collection.
Problem: When investigating an offline Archiver collection, it does not display metadata with events but displays only the events count.


Title: Unable to export logs using a custom time frame from event view when a profile is in place.

Problem: Event export fails when investigating for a custom time frame and profile with no prequery.

Title: Cannot export logs by Japanese users.

Problem: Unable to export logs in the Investigate view, when the user language setting is not English or French.


Title: In NetWitness 11.4 it removes pivoting in to meta on legacy views.

Problem: After upgrading to 11.4 and reconstructing an event in the Legacy Events view, the metadata drill down options are missing under the View Meta option in the event reconstruction toolbar.

Title: Investigate Event, searching value with slash character don't work, need to add extra slash to get the correct result.

Problem: From UEBA, when you pivot on a meta value containing a slash, the Investigate > Events view, does not display any results.


Title: Pivoting into the investigation of an event reconstruction is querying the wrong ip.src in FTP system parser.


The event reconstruction for a filename in the Investigate > Events view is querying the wrong meta key (ip.src ) instead of ip.dst in the FTP system parser.

Malware Analysis

Title: "HTTP/1.1 500 Internal Server Error" from MA cloud.


AV tab in Admin > Services > Malware > Config, does not display AV Vendor results.

Context Hub

Title: Some STIX fields are not there when converted to CSV.

Problem: When STIX data is converted to CSV format, some of the STIX fields are not available in the CSV file.

Context Hub

Title: Password for Live Connect and File Reputation datasource gets saved empty on edit config.

Problem: Connection for Threat Insights (Live Connect) and File Reputation data source fails as the password gets saved as blank.

Context Hub

Title: Recurring feed producing 'Failed' status when 'Converting Feed to Context Hub List'.


When converting a recurring feed to a Context Hub list, it displays a failed status.

Title: Duplicate Hosts in Endpoint Log Hybrid.

Problem: In the Investigate > Hosts view, duplicate hosts are displayed for the same host name but with different agent IDs as the agent was installed multiple times.
Reporting Engine

Title: Reports on Alerts/Incidents from ESA alerts not generating.

Problem: When you edit an existing schedule of a report, you cannot select a data source if a data source was not previously selected.
Reporting Engine

Title: Discrepancy in Reporting Engine Alert Count.

ProblemWhen querying against a time range, it does not load any alerts and does not display all the alerts  when queried for the custom time range.

Title: UEBA UI unable to access after installation.

Problem: After upgrading, UEBA page shows the default user interface instead of the latest UEBA page.

Log Decoder

Title: Log Decoder service crashes if changes are done to the log forwarding configuration fields logs.forwarding.enabled and logs.forwarding.destination
Problem: In Log Decoder, when you made any changes to log forwarding configuration fields logs.forwarding.enabled and logs.forwarding.destination, the changes are not written to /etc/netwitness/ng/NwLogdecoder.cfg file. Also, the Log Decoder service crashes and the core files are dropped in /var/netwitness/logdecoder/metadb.
Workaround: To resolve the issue, follow the below steps.

  1. Stop the Log Decoder service.
  2. Manually edit the NwLogdecoder.cfg file in /etc/netwitness/ng/.
  3. Restart the Log Decoder service.,

Title: Test connection fails for Relay Server with Endpoint Log Hybrid.
Problem: Enhanced Version of openjdk for Relay Server prevents the communication to Endpoint Log Hybrid.
Workaround: To resolve the issue, follow the below steps.

  1. SSH to Relay Server.
  2. Run the following commands.
    rpm -e java-11-openjdk-
    rpm -e java-11-openjdk-headless-
  3. SSH to NW server (Node 0).
  4. From the /var/netwitness/common/repo/ location, copy the following file to the Relay Server.
  5. From the /var/netwitness/common/repo/ location, copy the following file to the Relay Server.
  6. SSH to Relay Server.
  7. Run the following commands to install the copied RPMs from the NW Server (Node 0).
    rpm -ivh java-11-openjdk-headless-
    rpm -ivh java-11-openjdk-
  8. Run the following command to verify the installation.
    rpm -qa | grep -i openjdk
  9. Restart the Relay Server.
UEBATitle: Incorrect object metadata is parsed in UEBA
Problem: The UEBA Object Name pivot link in the Investigate > Entities view is populated with an incorrect meta key. Due to this issue, no matching events are displayed when pivoting to the Events view because the query includes the meta key.
Workaround: Run the query without, group, and user source.
UEBATitle: Pivoting from the Entities view to the Events view with the event.time meta key results in a query with invalid event time.
Problem: When you query the event.time meta key on any UEBA pivot link in the Entities view, the query added to the query bar in the Events view has an invalid filter (marked by a red outline) for event.time expressing the time in EPOCH format, and the query cannot be submitted. A tooltip on the invalid query explains the problem, but the suggested solution does not work:
You entered '1585216020-1585216080'. Times must be quoted with single or double quotes.
Workaround: Copy the EPOCH time value and create a new free-form filter without quoting the EPOCH time. See "Add a Free-Form Filter" in the Investigate User Guide.

Title: Unable to upgrade the NW Server host to version using the Offline User Interface method.
Problem: When trying to upgrade the NW Server host by clicking Update Host in the NetWitness Platform User Interface, the packages are initialized but the upgrade fails with the message "Download error".

  1. In the Command Line Interface (CLI), SSH to the NW Server host.
  2. Run the following command:
    upgrade-cli-client –-upgrade --host-addr <IP of Netwitness Server> --version
  3. After the NW Server is successfully updated, log in to the NW Server host user interface and go to Admin > HOSTS, where you are prompted to reboot the host.
  4. Click Reboot Host from the toolbar.

You can update all the other hosts using the offline user interface method, following the instructions in "User Interface Method with No Connectivity to the Internet" in the Upgrade Guide for RSA NetWitness Platfrom 11.4.1.,

Title: Refocusing a value that contains the backslash (\) character in the Events view does not return results
Problem: From the Event meta panel or any other place in the Events view, no events are returned when you right-click and refocus a value that contains the backslash (\) character.
Workaround: Edit the query filters containing the backslash (\) character and apply the query.

Title: In the email reconstruction, the Download button for attachments is not enabled due to a filename mismatch
Problem: Clicking on attachments in the email reconstruction should enable the Download button, but there is sometimes a mismatch between the file hash in the user interface versus the database. In this case, the Download button is not enabled.
Workaround: Download the same file from file reconstruction.

Title: Paging through results while packets are rendered causes the new page to load fewer packets
Problem: In a packet reconstruction that includes the payload, paging through results while the page is loading causes the next page to show only partial results. For example, if an event has 3500 packets, page 3 will probably include packets 1001-1500. But if you paginate to page 3 from page 2 while page 2 is rendering data, page 3 may start from packet 1025 or even 1050.
Workaround: If you reload the page or page forward and come back to the page, everything will load fine.


Title: The Download menu in the Events view remains in the “Downloading…” state after a timeout during the download operation.

Problem: When downloading a large number of network events from the Events list, the Download menu remains in the Downloading state () and the jobs queue gives a status of Failed with the following error message:
Error retrieving PCAP from service: TransportException: Channel was instructed to close or stop waiting for a response, timeout error activated.

The user cannot download events in the Events view until the exception is cleared.

Workaround: To clear the exception and restore the Download menu, go to the Events view and refresh the browser window.

11.4.1,, 11.4,
Legacy Windows Collector

Title: WLC Cert renewal script does not run.

Problem: The WLC Cert Renewal Script, packaged as part of 11.4 and located at

/var/netwitness/root-ca- update/wlc/, should not be run. RSA plans to provide a fix in a future NetWitness Platform patch release.

Workaround: None, 11.4.1ASOC-87953/
Event Stream Analysis

Title: Some ESA Rule Deployments migrated from versions before 11.3 can cause ESA Rule Deployment issues during the 11.4 upgrade.

Problem: Unused ESA rule deployments left over from the migration from the 10.6 or 11.2 legacy Event Stream Analysis service, which do not contain an ESA Correlation service, cause ESA rule deployments to not deploy after upgrading to NetWitness Platform 11.4.

Workaround: Before you upgrade to 11.4, delete ESA rule deployments that do not contain an ESA Correlation service. The remaining ESA rule deployments should have been deployed at least once with the ESA Correlation service.

To delete an ESA rule deployment:

  1. Go to Configure > ESA Rules > Rules tab.
  2. In the options panel to the left under Deployments, select the deployment that you want to remove.
  3. Select (Deployment menu icon) > Delete.
  4. Click Yes to confirm the delete.
Event Stream Analysis

Title: When a rule is shared between multiple ESA deployments, there is a discrepancy with the Enabled and Disabled ESA rule statuses after an upgrade
Problem: If an ESA rule is used in multiple deployments, then after an upgrade it is possible that the Enabled or Disabled status of that rule in those deployments may not be as expected.
Workaround: Check the ESA rule deployments that contain the rule and change the rule status as needed.
To change the ESA rule status in a deployment:

  1. Go to Configure > ESA Rules > Services tab.
  2. In the options panel to the left under ESA Services, select an ESA Correlation service.
  3. Click the tab for the deployment that contains the rule and in the Deployed Rule Stats section, select the rule.
  4. Change the rule status in the Status column by selecting either Enable or Disable above the table.
11.4.x, 11.3.x,
Event Stream Analysis

Title: An ESA Rule Deployment name with a Colon (:) throws a failed to start stream error

Problem: If an ESA rule deployment name contains a colon (:), data aggregation fails to start during deployment.

Workaround: Edit the ESA rule deployment name to remove the colon (:) and then redeploy the deployment.

  1. Go to Configure > ESA Rules > Rules tab.
  2. In the options panel on the left, under Deployments, select a deployment.
    The Deployment view is displayed.
  3. Select (Deployment menu icon) > Edit.
    The deployment name is made available for editing.
  4. Remove the colon (:) from the deployment name.
  5. Click Deploy Now to redeploy the deployment.
    The changes take effect on ESA after the ESA rule deployment is redeployed.
Event Stream Analysis

Title: Esper metrics collection can impact performance in some environments with ESA rules that consume large amounts of memory.

Problem (11.4.0.x): Metric collection in Esper version 8.2.0 is different than the previous 7.1.0 version. For an ESA Correlation server with rules that consume a lot of memory, the gathering of metrics can consume significant CPU, leading to a drop in EPS when the metrics are being collected. To avoid the drop in EPS, the default interval to collect metrics in NetWitness Platform 11.4 is set to a very large value (999999 days). This prevents the Esper metrics from being collected.

Workaround (11.4.0.x): If you need metrics collected at a more frequent interval, you can update the background-metrics-frequency parameter on the ESA Correlation service. Do not set the metrics collection interval lower than 5 minutes.

  1. Go to Admin > Services, select the ESA Correlation service, and then select Actions (red gear) > View > Explore.
  2. In the Explore view node list on the left side, select correlation > esper.
  3. In the right panel, enter a new metrics collection interval value for background-metrics-frequency.
  4. Restart the ESA Correlation service.
    • From the UI, go to Admin > Services, select the ESA Correlation service, and then select Actions (red gear) > Restart.
    • From the command line, run: systemctl restart rsa-nw- correlation-server 

Problem (11.4.1): Metric collection in Esper version 8.2.0 is different than the previous 7.1.0 version. In a typical deployment, rule metrics calculation finishes very quickly, within seconds. If a rule uses a significant amount of memory, it may take a long time to calculate metrics. During this time, ESA Correlation does not analyze events and this will result in an overall EPS drop. ESA Correlation will attempt to calculate metrics for a maximum of 15 seconds (default) and if any rules have metrics which cannot be calculated in this time, an error will be shown in the logs and ESA Correlation will abort the calculation to avoid further EPS drop. This will result in a maximum of 15 seconds of analysis lost every 5 minutes (background-metrics-frequency).

Workaround (11.4.1): If you need metrics collected at a more frequent interval, you can update the background-metrics-frequency and metrics-timeout parameters on the ESA Correlation service.

For example, if you have a rule that is using a lot memory and it cannot be optimized, you can reduce the overall EPS drop by increasing the frequency and / or lowering the timeout.

  1. In NetWitness Platform, go to Admin > Services, select the ESA Correlation service, and then select Actions (red gear) > View > Explore.
  2. In the Explore view node list on the left side, select correlation > esper.
  3. In the right panel, you can change the background-metrics-frequency and /or the metrics-timeout parameter value.
  4. Restart the ESA Correlation service. 
    • From the UI, go to Admin > Services, select the ESA Correlation service, and then select Actions (red gear) > Restart.
    • From the command line, run: systemctl restart rsa-nw- correlation-server 



RSA KB #38369
Event Stream Analysis

Title: Recurring In-Memory Table enrichments are not updating.

Problem: Recurring In-Memory Table enrichments do not update when the .CSV file changes. If you use Ad Hoc In-Memory Tables, this is not an issue. 

Recurring In-Memory Table enrichments are no longer supported. It is preferable to use Context Hub List enrichment sources instead of In-Memory Table enrichment sources. You can share Context Hub List enrichment sources across the NetWitness Platform.

You can only use the In-Memory Table with ESA

 Workaround: Change your Recurring In- Memory Tables to Context Hub lists. For each Recurring In-Memory table, do the following:

  1. Delete your Recurring In-Memory Table.
  2. Create a Context Hub List with the same name so that you do not have to update the ESA rules.

For information on how to configure a Context Hub List as an enrichment source, see the Alerting with ESA Correlation Rules User Guide. Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents. 

11.4.x, 11.3.xWon't fixASOC-86887

Title: When the NOT operator is used in Free-Form Mode without parenthesis, as in NOT medium = 1 vs NOT(medium = 1), the free-form query will fail.

Problem: When the NOT operator is placed before an expression like (NOT service = 80), Free-Form Mode is transforming the expression by adding an open parentheses in front of the expression following the NOT; this imbalances the query and produces an error.

Workaround: Use this syntax when creating a query in Free-Form Mode: NOT (service = 80). Also, be sure to fix any pre-query or query prefix that has the NOT operator in this form: (NOT service = 80) so that pivoting from Navigate to Events view does not break the flow.

Title: Packets are not rendered properly and the expected data is not displayed in the Events view packet reconstruction.

Problem: Sometimes when reconstructing larger events with multi-page data in the packet reconstruction, the request or response field is blank and no data is loaded.

Workaround: Click the Web reconstruction icon above the packet reconstruction. After the web reconstruction opens in the Legacy Events view, switch back to the packet reconstruction.

Title: The packet reconstruction being viewed does not have data loaded after leaving the Events view for the Hosts, Files, or Entities view, and then returns to the Events view using the Events option in the Investigate submenu.

Problem: If the packet reconstruction is open and the user moves away from Events view by clicking on the Hosts view, Files view, or Entities view, and comes back to the Events view by clicking Events in the Investigate submenu, there is an issue with the reconstruction. The previous query is executed, but the reconstruction that was open does not load the packet reconstruction as expected.

Workaround: Refresh the browser page.

TitleAfter upgrading to Version 11.4, there may be issues in the Navigate view and Legacy Events view because the column groups, meta groups, or profile groups permission is disabled for custom user roles.

ProblemWhen the column groups, meta groups, or profile groups permission is disabled for a user, the Load Values button is not displayed in the Navigate view. When column groups permission is disabled, there is an additional issue in the Legacy Events view: Only the Detail view is visible and you cannot select different views and column groups.

The issue occurs most frequently after upgrading to 11.4 because new built-in permissions are not automatically applied to custom user roles.

WorkaroundAfter completing the upgrade, the administrator needs to enable the

required permissions as described in the System Security and User Management Guide. Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents. 

A quick workaround for analysts: To load values in the Navigate view, you can select a different time range to load meta values. There is no workaround for the issue with the Legacy Events view.

Title: Unable to query meta keys with values and meta values are truncated for some characters like ®.

Problem: When some meta values include special characters like ®, analysts cannot drill down using that meta key in the Navigate view. Meta values are also truncated in the Events view.

Workaround: Remove the special character if creating a feed, or encode it properly at the source of the feed.

11.4.1,, 11.411.5ASOC-85375

Title: When initiating a download, Investigate fails to connect to the browser job tray and the download spinner remains indefinitely.

Problem: The download job fails to connect to the browser job tray, but the download job does initiate and can be retrieved from the link shown in the flash message at the top of the screen.

Workaround: Retrieve the download from the job queue under <Your Name> > Profile

> Jobs.

11.4.1, 11.411.5ASOC-50412
Log Decoder

Title: Log Decoder may not start data aggregation after upgrade.

Problem: There can be two reasons that Log Decoder may not start data aggregation:

  • Log Decoder service crashes due to higher index usage that leads to disk input or output issue before an index rollover occurs. This causes the Concentrator to fail and stop data aggregation because it was unable to retrieve first session from the Log Decoder.
  • Concentrator has frequent meta overflow alerts for some meta keys.

Workaround: In Log Decoder configuration, the parameter save.session.count=0 or

save.session.count=600000000, which was set by default in previous releases, must be set to AUTO.

  1. Go to Admin > Services and select a Log Decoder.
  2. Click Actions (red gear icon), and then click View > Explore.
  3. Click index > config.
  4. Change save.session.count to auto.
  5. Follow these steps to reset the index:
    1. In the Explore view, in the left pane, right-click the decoder folder and select Properties.
    2. Go to the bottom of the center pane, under Properties, in the drop-down menu, click the down arrow, and select reset.
    3. In Parameters, type index=1 and click Send.
      The service restarts and rebuilds the index.
11.4.x, 11.3.x, 11.2, 11.1Won't fixSADOCS-1784, SACE-12300
Endpoint Server

Title: Endpoint server is often found in Unhealthy state after a day of deployment.

Problem: If you are running an Endpoint Server in an environment that does not contain a Context Hub server, the file status and file reputation features will not work, and the status of the Endpoint Server shows Unhealthy in Health and Wellness. Other Endpoint features will work without the Context Hub Server.

Workaround: None


Title: Built-in charts are not enabled by default for multi analyst UI.

Problem: When the Admin enables the built-in dashboards on any node, the dashboards and the corresponding charts are enabled only on the selected node. On the other nodes, the corresponding built-in charts are not enabled by default. The built-in dashboards are enabled with an error message, "No active execution details available for chart (chart name)" displayed on the UI.

Workaround: The user must login as an Admin on every node and manually enable the built-in charts.

11.4, 11.5ASOC-79538

Title: When there are 100+ events in an alert, the scroll bar does not display all the alert information in a clear format.

Problem: The scroll bar is only partially visible when there are over 100 events in the Incident Details view Events List.

Workaround:  You can continue scrolling to see all of the information.

11.4.x, 11.3.xWon't fixASOC-71935
Audit Logging

Title: logstash does not reconnect to RabbitMQ if RabbitMQ is reset. 

Problem: If RabbitMQ is reset for any reason, logstash does not connect to RabbitMQ for aggregating Audit logs.

Workaround: Restart logstash to reconnect to RabbitMQ.


Title: Updating "Effective Date" daily causes scan schedules to restart.

Problem: The default EDR policy does not specify an effective date. If a policy for an agent does not specify the effective date, then the current date is used instead. This causes the group policy document to be updated every day with the new effective date. Any agent using the default effective date setting will then receive an updated policy every day, causing it to restart its scan schedule everyday and resulting in the agent scanning every day regardless of what the actual policy is.

Workaround: Edit the default EDR policy and add an effective date.




Title: Cannot orchestrate an additional component host if the NW Server host was upgraded to without an intermediate upgrade to

Problem: If you are upgrading your hosts from 11.0, 11.1, or 11.2 directly to, and you want to add a new host after the NW Server Host has been upgraded, the new host cannot be orchestrated.
Workaround: Refer to the Knowledge Base article located here:



Event Stream Analysis

Title: Aggregation stops on some Concentrators because of too many open files.

Problem: Occasionally, ESA Correlation will encounter an error when aggregating from a Concentrator resulting in a connection leak. Over time, this may result in the 'too many open files' error which will stop aggregation.

Workaround: You must restart the ESA Correlation service from the NetWitness Platform user interface.

  1. Log on to NetWitness Platform as Admin.
  2. Go to ADMIN > Services.
  3. Select the ESA Correlation service and then select the Actions icon > Restart.


Core Services

Title: Log Collector event processor does not get started after Log Decoder appliance reboot.
Problem: When you reboot Log Decoder appliance, the Log Collector event processor does not get started.
Workaround: To resolve this issue, do the following:

  1. Go to ADMIN > Services.
  2. Select a Log Collection service.
  3. Select the Actions icon > View > Config to display the Log Collection configuration parameter tabs.
  4. Click the Event Destinations tab.
  5. Select Log Decoder and click the Start icon.

ASOC- 83767

Event Stream Analysis

Title: Cannot Access Custom Esper Java Libraries
Problem: In NetWitness Platform version 11.3.x and later, it is slightly more difficult to enable custom Esper Java libraries for those customers who have built their own EPL extensions in Java. For those customers, upgrading to 11.3.x or 11.4.x can create an issue with their alerts that previously used their custom EPL extensions. Without the extended rules (Esper + Java Libraries), customers do not have full visibility of some pattern detection which increases noise for their Analysts, decreasing their productivity.
Alternate Methods: For 11.3.x, see Knowledge Base article “000038138 - Cannot Access Custom Esper Java Libraries for RSA NetWitness Platform's Event Stream Analysis” at For 11.4 and later, see 
Knowledge Base article “000038371 - Cannot Access Custom Esper Java Libraries for RSA NetWitness Platform's Event Stream Analysis” at

11.4, 11.3.x,
See the KB articles.



Event Stream Analysis

Title: Sample Enrichment ESA rules are being disabled on due to src_ip meta key error

Problem: In, the migrated Whitelist and Blacklist SAMPLE ESA rules use the src_ip meta key, which is invalid for 

Workaround: Edit the Whitelist and Blacklist SAMPLE rules to use ip_src:

  1. Go to CONFIGURE > ESA Rules > Rules tab.
  2. Double-click the “SAMPLE - Blacklist -From inside countries that are not the US, Non SMTP Traffic on TCP Port 25 Containing Executable” rule to edit it.
    1. In the Conditions section, select the “Non SMTP Traffic on TCP Port 25 Containing Executable” statement and click  to edit the statement.
    2. In the Build a Statement dialog, change the ipv4 key value from src_ip to ip_ src and click Save.
    3. In the Enrichments section, for GeoIP output, change the ESA Event Stream Meta value from src_ip to ip_src.
    4. Click Save to save the rule.
  3. Double-click the “SAMPLE - Whitelist -From outside of Germany, P2P Software as Detected by an Intrusion Detection Device” rule to edit it.
    1. In the Enrichments section, for GeoIP output, change the ESA Event Stream Meta value from src_ip to ip_src.
    2. Click Save to save the rule.


Event Stream Analysis

Title: Sometimes the status of an ESA rule deployment is incorrect.

Problem: When you deploy ESA rules, sometimes an error occurs that shows that the rules are disabled in the user interface (CONFIGURE > ESA Rules> Rules tab Deployment panel) when the ESA rule deployment is actually successful. Check the Services tab to see the actual status of the deployment.

Note: This issue is fixed in NetWitness Platform

Workaround: None.




Title: Default SSH timeout period 

Problem: In 11.3.1, there is a new default, three-minute timeout period for an SSH session (from the Browser or Console).  This brief timeout period may be inadequate for your needs.

Workaround: The following procedures are two options for changing this setting.

Disable the SSH Timeout Setting and Default to the Auth Timeout Setting
If you disable the SSH timeout setting, NetWitness Platform uses the auth timeout setting. The default value for the auth timeout setting is 10 minutes.
1. SSH to the NW Server host or use the Console from the NetWitness Platform User Interface.
2. Submit the following command string.
/opt/rsa/saTools/bin/manage-stig-controls --host-all --disable-control-groups 2

Remove the Timeout Setting (No Timeout for SSH)
If you disable both the SSH and Auth timeout settings, SSH sessions will not time out.
1. SSH to the NW Server host or use the Console from the NetWitness Platform User Interface.
2. Submit the following command string.
/opt/rsa/saTools/bin/manage-stig-controls --host-all --disable-control-groups 2,4, 11.3.2ASOC-80695
UpgradeTitle: Linux policy is not updated in the user interface after upgrading agents from 11.2.0 to 11.3.1.
Problem: In the NetWitness Platform user interface, Agent mode is displayed as INSIGHT after upgrading from 11.2.0 to 11.3.1. After scanning, Agent mode is moving to ADVANCED.
Workaround: None.

TitleThe default CEF and human-readable format audit templates are not updated after upgrading to 11.3.1.

Problem: In 11.3.1, notification templates were updated with additional fields. The updated templates are "Default Audit Human-Readable Format" and "Default Audit CEF Template." If you are using these templates, you must perform the steps below after you update to 11.3.1 to reflect the changes.

Workaround: Delete the default templates, restart the Jetty service, and reconfigure Global Auditing:

  1. Go to ADMIN > System > Notification template. Delete the "Default Audit Human-Readable Format" and "Default Audit CEF Template" templates.
  2. Run systemctl to restart Jetty.
  3. Reconfigure Global Auditing.
Event Stream Analysis

Title: Unable to delete an endpoint bundle from an ESA rule deployment
Problem: When creating an ESA rule deployment, if you add an Endpoint Risk Scoring Rule Bundle and then you decide to remove it from the deployment, you see the following error: Rule of type `Endpoint` is an internal rule and cannot be modified
Likewise, if an ESA rule deployment with an Endpoint Risk Scoring Rule Bundle is deployed, you cannot reuse the deployment by deleting the bundle and adding other ESA rules.
Workaround: Delete the ESA rule deployment containing the Endpoint Risk Scoring Rule Bundle and create a new ESA rule deployment. Do not combine the Endpoint Risk Scoring Rule Bundle with other ESA rules in the same deployment.


Title: Broker timeline does not render if Concentrator is offline.
Problem: The Investigate time-line graph is not displayed when one of the aggregated devices defined in Broker Configuration is offline.
Workaround: None

11.3.1, 11.3SACE-11365
Global Notifications

Title: Syslog server config updates are making entries in config.
Problem: Duplicate entries in rsa-audit-server- output.conf log file. If multiple changes in Global Notifications are made in a short time frame, NetWitness Platform appends multiple duplicate entries to the rsa-audit-server-output.conf file.


  1. Delete the duplicate entries from the rsa-audit-server- output.conf file.
  2. Go to ADMIN > System > Global Notifications.
  3. Select a notification server and click the Edit icon.
  4. Click Save.
    It takes about five minutes for the workaround to take effect.
11.3.1, 11.x11.4ASOC-59607
Event Stream Analysis

Title: Meta keys marked as sensitive for Data Privacy are still included in notifications and alerts for some ESA rules.

Problem: In ESA rules that do not select every piece of metadata from the session (that is, using ‘select *’), you may see that data privacy (if enabled) and the Pivot to Investigate > Navigate link accessed from a context tooltip in Respond does not work.

Workaround: For 11.4, you can perform the steps that are documented in “Update any ESA Rule that Selects Only Certain Meta Keys from the Session to Include event_ source_id” in the Alerting with ESA Correlation Rules User Guide. Go to the Master Table of Contents to find all RSA NetWitness Platform 11.x documents. 

Event Stream Analysis

Title: The available data sources in an ESA rule deployment show details of a deleted host.

Problem: If a Concentrator is added to the available data sources for ESA rule deployments and then the host is removed from the NetWitness server, you can still see that host in the available data sources list.

Workaround: Remove the host from the available data sources for ESA rule deployments and then redeploy any existing ESA rule deployments that were using that host.

To remove the host from the available configured data sources:

  1. Go to CONFIGURE > ESA Rules Rules tab.
  2. In the options panel on the left, select an ESA rule deployment.
  3. In the Deployment panel Data Sources section, click the Plus Sign.
  4. In the Available Configured Data Sources dialog, select the host that was removed from the NetWitness Server. The host should show a white circle (stopped service) instead of a green circle (running service). 
  5. Click the Minus Sign and then click Save.,

Title: Commands issued after pressing the Tab key are not captured in Powershell for Windows 10 version 1809

Problem: In Windows 10 version 1809, when you execute a command in Powershell and press the Tab key, the Powershell console events that are captured contain only the characters entered before pressing Tab. Also, some of the Powershell console events that are captured may contain repeated characters.

Workaround: None


Title: In the Event Analysis view, the query console does not replace the information icon with an error icon when a service is offline.

Problem: When a queried service is offline, the information icon in the query console should change to an error icon (red triangle with an exclamation point). The border of the query console border turns red, but the information icon does not change to a error triangle.

Workaround: None


Title: When retrieval of events for a query is in progress in the Event Analysis view, events that are already displayed disappear if the query takes more than 5 minutes to finish

Problem: This can happen when querying a large set of data with a query that includes expensive operations. The query is auto-canceled after a 5-minute timeout, and an error message is displayed.

Workaround: To avoid the timeout, change the query parameters to filter a smaller data set and re-execute the query.


Title: Matching files are not displayed in the Files tab if the file name in the event does not match the global file name.

Problem: From the Nodal Graph, when you pivot to Investigate > Hosts or Files tab for analyzing a file, if the file name in the event does not match with the global file name, no result is displayed in the Files tab.

Workaround: You must pivot to Investigate > Hosts or Files using the file hash.

  1. Go to RESPOND > Incidents.
  2. Click the ID (incident ID) associated with the file name.
  3. Click the Events List and search for the file name you want to analyze.
  4. Hover over on the file hash and click Pivot to Investigate > Hosts/Files.
11.4.x, 11.3.x11.5ASOC-73173

Title: Respond stats reset after update.

Problem: After an update from NetWitness Platform 11.2 to 11.3, Respond statistics are reset in the Incident Rules view (CONFIGURE > Incident Rules). The rule counter for matched alerts and incidents resets to zero and the Last Matched, Matched Alerts, and Incidents columns show only 11.3 values.

Workaround: None.

Note: This is fixed for updates from 11.3 to 11.3.x or 11.4.x, but is still an issue for updates from 11.2.x to 11.3.x.

11.3.x, 11.2.x11.3.1.1ASOC-72759

Title: Show proper message for Event Analysis not loading in a mixed-mode environment.

Problem: In a mixed-mode environment, when the Event Analysis does not load from the Respond Incident Details view, customers receive the following message: “An unexpected error has occurred attempting to retrieve this data.” Instead they should receive a message that this is expected behavior. Event Analysis requires all core services to be on NetWitness 11.1 or greater.

Workaround: None.,,, 11.2.x.x11.3.1.1ASOC-60463

Title: Deleting an alert in Respond is not updating the High-Risk User List in Threat Aware Authentication

Problem: Applicable to customers who have enabled Threat Aware Authentication. When Alerts associated with an open incident are deleted from the Alerts view (Respond > Alerts), the email addresses associated with the deleted alerts are not removed automatically from the SecurID’s high-risk users list.

Workaround: None, but you can manually remove the user details from the high-risk users list.,,

Title: ESA Rules with severity as High or Low are not populated in the RSA Archer user interface.

Problem: When ESA alerts with severity High or Low are forwarded to RSA Archer, the Security Alert Priority field is not populated in the RSA Archer user interface.

Workaround: None

11.5, 11.4.x,11.3.x, 11.2.xARCHER-47100
Event Stream Analysis

Title: For ESA rules that use enrichment sources, the Ignore Case option does not work for first statement

Problem: When creating an ESA rule that uses any enrichment source, if the Ignore Case option is enabled on the first enrichment statement, no results are returned. Note that this issue does not apply to any statements after the first statement (that is, substatements).

Workaround: When creating a new rule, the Ignore Case option is now disabled. For existing rules that have the Ignore Case option enabled for an enrichment statement, the option is still enabled but users will be prompted to disable the option when opening the rule in ESA and then save the updated rule.

11.5, 11.4.x, 11.3.x, 11.2.xASOC-49906

Title: When a large PCAP is extracted from the Events view, if it times out after 5 minutes, the query time is displayed as 8 hours in the Jobs tray error message.

Problem: When exporting a PCAP with ~100000 sessions from the Events view using Export > Export All PCAP, the download may fail due to the 5-minute packets call timeout. If the call times out, the error message in the Jobs tray incorrectly displays the timeout as 8 hours (28800000 ms).

Workaround: None.


Title: Nginx rejects post requests exceeding request size 1 MB

Problem: The Nginx server is upgraded and the default payload size is set to 1 MB. This causes any data post request exceeding 1 MB to fail.

Workaround: Add the following setting to the Nginx configuration file (/etc/nginx/conf.d/nginx.conf) and restart the Nginx server:

client_max_body_size 100M

Event Source Management

Title: SMS Service crashes with Out of Memory Error

Problem: On systems with a large number of active event sources, when the system cannot keep up with the processing of log statistics messages, the SMS service can crash with a java.lang.OutOfMemoryError: Java heap space error.

Workaround: If you experience this issue, please contact RSA support for details on how to address the issue.
Event Stream Analysis

Title: ESA CH rules get disabled during upgrade or ESA host reboot

Problem: If the ESA host restarts and Context Hub rules are deployed on ESA, the Context Hub rules may be disabled. This happens as a result of a race condition between the Context hub and Event Stream Analysis services startup order on the ESA host.

Workaround: To resolve this issue, do one of the following:

  • Go to the CONFIGURE > ESA Rules > Services tab and enable the disabled rules that are dependent on Context Hub.
  • Restart the Event Stream Analysis service.
Event Stream Analysis

Title: Case-sensitive sorting is not working properly in the ESA All Rules grid

Problem: When rule names begin with lower and upper case letters, the sort does not work properly in the Rule Name column of ESA All Rules grid. For example, "Rule 1" is not followed by "rule 2" when you sort by name.

Workaround: None

11.3.1, 11.3, 11.2Won't fixSAENG-3605

Title: In the Event Analysis view, log and network events are not interleaved

Problem: Network and log events are interleaved and sorted in time order in the Events view, but in the Event Analysis view, events are sorted differently. In the Event Analysis view, the events are not interleaved as they should be; instead all log events sorted in time order are displayed before all network events sorted in time order.

Workaround: Use the Events view to see interleaved network and log events.


Title: Imported Investigate profiles are not displayed in the Profiles drop-down menu

Problem: When you import Profiles to the Navigate view or the Events view using the Manage Profiles dialog, the newly imported profiles are not added to the Profiles drop-down menu.

Workaround: Refresh the browser window to see the recently added profiles.


Title: If the URL for a drill point is very long and you use the query in the Event Analysis view, an error (414 Request error) is returned

Problem: Several situations create a very long query that the browser cannot handle, especially if you are using Internet Explorer, which has a much lower character limit than most browsers. Pivoting to Event Analysis from Reporting can result in a very long query, and a number of pivots in the Navigate view can create a very long query.

Workaround: Continue to work in the Navigate view or Events view when the URL becomes too long to render in the Event Analysis view.


Title: When all alerts are deleted for an alert rule, the filter for the rule is not properly removed

Problem: In the Alerts List view (Respond > Alerts), you can filter alerts by Alert Name and then delete all of the alerts that have that name. If you do not remove the alert name filter after deleting the alerts, the next time the Alerts List view loads, the filter will still be in place, but it will no longer be visible as a checkbox in the Filters panel because all alerts with that name have been deleted. You will continue to see zero results when visiting the Alerts List view.

Workaround: Before you refresh or reload the Alerts List view, you can remove the filter by clearing the checkbox by the alert name. If you already refreshed or reloaded the Alerts List view, the only way to remove the hidden filter is to press the Reset Filters button, which removes all filters, including the hidden alert name filter.


Title: When the proxy is configured, and NetWitness Platform is updated to 11.2, the license details do not get refreshed automatically.

Problem: When the proxy is configured, and NetWitness Platform is updated to 11.2, the license details do not get refreshed automatically or even after clicking the Refresh button in the License Details view. This is because the communication to the license server is not established.

Workaround: The administrator has to manually download the license details using the offline mode and upload latest license details through the RSA NetWitness Platform UI. For more information, see the Licensing Management Guide for RSA NetWitness Platform.





Title: STIX recurring feed fails on upgrade from 10.6.6 to 11.2

Problem: When you upgrade Security Analytics 10.6.6 to RSA NetWitness Platform 11.2, the STIX Recurring feed you created using HTTPS URL fails to work. This is because, in 10.6.x, by default, all the certificates are trusted. However, this is not the case in 11.2. In 11.2, the Trust All certificates option is provided and is disabled by default.

Workaround: Navigate to Configure > Custom Feeds and edit the failed feed. Either enable the Trust all option, or upload a valid SSL certificate to resolve the issue. In case of any further queries, contact the RSA Customer Support.


Title: After you upgrade to or, the logstash files are not updated in the logstash output configuration file

Problem: When you upgrade from 10.6.x.x to or, logstash files are not updated in the logstash output configuration file. This happens when you have a global audit setup.

Workaround: If global auditing is configured, you need to edit one of the syslog entries in the Global Notifications servers and click Save to apply the latest Audit log configuration.


Title: The investigation links are disabled for static charts during 10.6.x.x to 11.1 or 11.2 post-upgrade.

Problem: The investigation link is disabled for the static chart (the result of the report is in chart format) which has the datasource as RSA NetWitness Platform-Broker (This service is available by default).

Workaround: There are two workarounds for this issue:

  • The rules that have the result in static chart can be viewed in Tabular format and the investigation works as expected.
  • Or you can perform the following steps to fix the issue:
    1. Delete and add the RSA NetWitness Platform-Broker again as the datasource to Reporting Engine with the same name.
    2. If the reports with static chart are scheduled reports, then in the next run, the investigation link will work as expected.
    3. If the report is an Adhoc report then, then re-run the report for getting the investigation links.