Configure Endpoint Alerts via Message Bus

Document created by RSA Information Design and Development on Sep 15, 2017Last modified by RSA Information Design and Development on Nov 16, 2017
Version 10Show Document
  • View in full screen mode
  

This procedure is required to integrate NetWitness Endpoint with NetWitness Suite so that the NetWitness Endpoint alerts are picked up by the Respond component of NetWitness Suite and displayed in the RESPOND > Alerts view.

Note: RSA supports NetWitness Endpoint versions 4.3.0.4, 4.3.0.5, or 4.4 for NetWitness Respond integration. For more information, see the "RSA NetWitness Suite Integration" topic in the NetWitness Endpoint User Guide.

The diagram below represents the flow of NetWitness Endpoint alerts to the Respond Incident List view of NetWitness Suite and its display in the RESPOND > Alerts view.

Endpoint Alerts via Message bus

Prerequisites

Ensure that you have the following:

  • The Respond service is installed and running on NetWitness Suite 11.0.
  • NetWitness Endpoint 4.3.0.4, 4.3.0.5, or 4.4 is installed and running.

Configure NetWitness Endpoint to Forward NetWitness Endpoint Alerts

To configure NetWitness Endpoint to send alerts over the message bus to the NetWitness Suite user interface:

  1. In the NetWitness Endpoint user interface, click Configure > Monitoring and External Components.

    The External Components Configuration dialog is displayed.
    NetWitness Endpoint - External Components Configuration dialog

    1. From the components listed, select Incident Message Broker and click + to add a new IM broker.
  2. Enter the following fields:

    1. Instance Name: Enter a unique name to identify the IM broker.
    2. Server Hostname/IP address: Enter the Host DNS or IP address of the IM broker (NetWitness Server).
    3. Port number: The default port is 5671.
  3. Click Save.
  4. Navigate to the ConsoleServer.exe.config file in C:\Program Files\RSA\ECAT\Server.
  5. Modify the virtual host configurations in the file as follows:
    <add key="IMVirtualHost" value="/rsa/system" />

  6. Note: In NetWitness Suite11.0, the virtual host is “/rsa/system”. For version 10.6.x and below, the virtual host is “/rsa/sa”.

  7. Restart the API Server and Console Server.

  8. To set up SSL for Respond Alerts, perform the following steps on the NetWitness Endpoint primary console server to set the SSL communications:

    1. Export the NetWitness Endpoint CA certificate to .CER format (Base-64 encoded X.509) from the personal certificate store of the local computer (without selecting the private key).
    2. Generate a client certificate for NetWitness Endpoint using the NetWitness Endpoint CA certificate. (You MUST set the CN name to ecat.)

      makecert -pe -n "CN=ecat" -len 2048 -ss my -sr LocalMachine -a sha1 -sky exchange -eku 1.3.6.1.5.5.7.3.2 -in "NweCA" -is MY -ir LocalMachine -sp "Microsoft RSA SChannel Cryptographic Provider" -cy end -sy 12 client.cer

      Note: In the above code sample, if you upgraded to Endpoint version 4.3 from a previous version and did not generate new certificates, you should substitute "EcatCA" for "NweCA".

    3. Make a note of the thumbprint of the client certificate generated in step b. Enter the thumbprint value of the client certificate in the IMBrokerClientCertificateThumbprint section of the ConsoleServer.Exe.Config file as shown.

      <add key="IMBrokerClientCertificateThumbprint" value="896df0efacf0c976d955d5300ba0073383c83abc"/>

  9. On the NetWitness Server, copy the NetWitness Endpoint CA certificate file in .CER format into the import folder:
    /etc/pki/nw/trust/import

  10. Issue the following command to initiate the necessary Chef run:
    orchestration-cli-client --update-admin-node
    This appends all of those certificates into the truststore.

  11. Restart the RabbitMQ server:
    systemctl restart rabbitmq-server
    The NetWitness Endpoint account should automatically be available on RabbitMQ.

  12. Import the /etc/pki/nw/ca/nwca-cert.pem and /etc/pki/nw/ca/ssca-cert.pem files from the NetWitness Server and add them to the Trusted Root Certification stores in the Endpoint Server.

Troubleshooting

This section suggests how to resolve problems you may encounter when you configure NetWitness Endpoint alerts via Message Bus.

             
Known IssuesSolutions
Orchestration fails on admin node.You must copy and paste the content of EcatCA certificate in /etc/rabbitmq/ssl/truststore.pem and restart the Rabbitmq service.
You are here
Table of Contents > Configure Endpoint Alerts via Message Bus

Attachments

    Outcomes