The Snare Central Server uses Ubuntu as a base operating system, and is compatible with instructions provided by most certificate issuing agencies for Ubuntu (or Debian), to generate your certificate signing request and install the resulting certificates.
This link provides general documentation on the use of self-signed, and third-party certificates on Ubuntu server appliances, and can be useful background reading if you wish to implement a non-standard configuration: https://help.ubuntu.com/community/OpenSSL#SSL Certificates.
The file /etc/apache2/sites-enabled/000-default-ssl, on the Snare Server, contains SSL/TLS related configuration items. Various options will need to be enabled and you will have to copy the updated certificates to the server after signing etc.
How To Create your own Certificate Signing Request (CSR) Certificate to get signed by an organisational, or 3rd party Certificate Authority
Using putty or ssh, connect to your Snare Central Server as the 'snare' user, attain administrator-level privileges by running the command: "sudo -s" (and enter your snare user password), then enter following commands:
It will then request C/CN details. The "C" field should be a two-letter country code. The CN should be the DNS name of the Snare Server; the same address that you will put into your web browser to connect to the server. Other fields, as appropriate based on your geographic location and organisational details.
Once the command completes, a snare.csr will be created. You will need to transfer it to your CA to sign (generally by copy/pasting the contents into a web form).
Please ensure that the certificate provided by your CA is exported in base64/PEM format. The certificate you get back from your CA needs to replace the contents of the apache.pem file.
Please transfer the certificate to the Snare Server, and copy it to
Note: you will need to transfer the files to either /tmp or /home/snare as you can only use SFTP/scp for non root accounts. Once you copy the files to the Snare Central server, log in to the CLI, sudo to root-level user access as highlighted above, then move the files to the correct locations.
To reload the web server with the new keys execute:
Snare Central TLS Listener
TLS and strict validation are available from Snare Agents to Snare Central. Standard TLS is supported with a self-signed certificate. Strict validation of the client/server can be provided with a certificate signed by a trusted (internal or third party) CA.
Logs can be received by the Snare Central server over a TLS connection, on tcp port 6163, or port 6514 (encrypted syslog). By default, the Snare collection system in v8.4 will generate a new dynamic self-signed certificate every time the service restarts. If a valid certificate is found in /data/SnareConfig, it will be used by 8.4 and prior. The reflector can work with either a single PEM file that contains both public and private keys, or will be use with two separate PEM files containing private and public keys respectively. The public key is signed (self, or CA). The agent encrypts content using the public key. The private key is used to decrypt the encrypted data. The private key is generally kept secure on the server and not shared. New keys can be generated in the same fashion as described above for the Apache web server but just stored in this separate location.
Installing certificate in Reflector v3.x.x on Snare Central
The Snare Reflector/Collector can receive events using secure TLS on port 6163. Snare TLS+Authentication is also support on port 6164.
By default, the Collector uses a self-signed certificate for this purpose. It is possible however, to install custom certificates. In order to accomplish this, the user needs to upload both public and private keys to the Snare Central server, place the certificates in the right directory with the right permissions/ownership.
Please note that the certificates are used exclusively for the TLS reception port(s) and are not used to access the UI nor as an encryption certificate for any destination.
The Collector can be configured to support separate files for private/public keys, or can use a single container file (pem) that includes both keys. Depending on user needs the procedure is very similar:
Stop Collector with the following command:
$ sudo /etc/init.d/snare stop
Upload and copy certificate files into the correct directory, with the correct filename. Assuming the source private and public keys are in separate files and the names are MyTLSCert-Public.pem and MyTLSCert-Private.pem: