Encryption of data in transit and at rest

The Wavestore secures your data in a variety of ways.  Most are automatic, especially between the WaveView client and the Wavestore server, but when setting up connections to external devices it is important to select the correct level of security.

Encryption between application components (Wavestore - camera)

  • Data can be encrypted using HTTPS/TLS/SSL if the "SSL" option is selected.  This might need some configuration on the camera as well, and will depend on the camera.

User connection to the application

  • Connections to the Wavestore from the clients using Protocol 5 use standard TLS encryption, just like HTTPS.
  • Connections to the Wavestore from the clients using the old Protocol 4 encryption equivalent to HTTPS for validation of login and for sensitive commands such as configuration changes and password setting.  Commands sent over the network are encrypted using RSA public key encryption for negotiation and then AES128 for content encryption, and this too is transparent to the user. It is similar to using HTTPS to access your web server. Video can also be encrypted using end-to-end encryption for additional security (see below).

Interfaces/connections to other applications

  • See above for HTTPS and Wavestore API.
  • If you enable DHCP, DNS, or NTP, then those protocols are used.

In-transit data (including passwords)

  • See above for HTTPS and Wavestore API.handling.

Is the integrity of application data during transmission ensured?

  • Application data is sent over TCP which has checksums, retransmission and validation.  Encryption also has validation.  Application-specific checks are also performed.

How is configuration data loaded from files validated?

  • Configuration editors enforce format before writing back.
  • On reading from a file, validation is performed when the data is processed, for example numeric fields are forced to be numeric.
  • Configuration data is not mixed with commands, so injection attacks are not possible.

Password protection at rest

  • A one-way work-factor hash with 10,000 iterations is used to protect passwords stored on the Wavestore

These are largely distinct methods of encryption. The one-way password encryption is performed using a secure one-way hash function and is transparent to the user. C

End-to-end encryption of video data

  • The Wavestore offers very secure end-to-end video data encryption which can be enabled in the Setup > Server > Encryption page.  This remains encrypted at rest and on transmission and can only be decoded by a key on the client at the time of playback.

Video and Audio can be encrypted at the point of recording. It remains encrypted on disk, when sent over the network, and when backed up to a backup device. It is decrypted only at the point of viewing on the WaveView client, such that it can only be viewed by users that hold a special ‘private key’.

The configuration steps required to enable this functionality are as follows:
• Generate a key pair - creating a public key and a private key
• Load the public key onto the Wavestore server (menu path View -> Setup -> Server -> Encryption).
• Enable Signature Stream Recording.
• Enable encryption for each individual channel that you wish to encrypt.
• Distribute the private key to any WaveView client that is required to access the video and audio.

When WaveView client (running either on the server itself, or a client PC) first detects encrypted footage, the operator is prompted to load the private encryption key. If this key is valid, the video will be displayed (or audio played). Otherwise, it will not be possible to view/listen to the encrypted footage.