Encrypt video traffic to desktop
AnsweredHi.
Thank you for nx's support.
We are a partner of network optix, and while testing the product, a question arose.
The operating environment is:
Version: 5.1.4.38659
OS: Windows 11 Pro
A few days ago, I asked about video traffic encryption, and I received an answer, but there is still a question.
System Management> Security> Encrypt Video Traffic to Desktop Client
I still find it difficult to see that this function works.
TLSV1.2 is displayed in the Wire Shark, whether or not this function is activated or not.
The image below is a capture of TLSV1.2 between the server and the client while the above function is inactive.
The image below was extracted from the NX Witness FAQ.
DATA: Always Encrypted (https)
-> Always communicate with TLSV1.2 between clients-server. Is that correct?
Video: Not Encrypted by Default, But Optional Tls Encryption Can be Enabled.
-> "System Management> Security> Encrypt Video Traffic to Desktop Client" enables TLS encryption. Is that correct?
When the function was activated or disabled, no difference was found in the wire shak. How can I confirm that video traffic is encrypted between server-clients?
-
Hi cgjeon,
When the RTSP stream isn't encrypted, it's theoretically possible for someone to intercept the traffic between the camera and the server. If this data is captured, they could filter the capture for RTP packets from a specific RTSP stream and then use a tool to reassemble these packets. After reassembly, another tool can extract key frames and save them in JPEG format.
While the packet content might already appear unreadable to the human eye, it can still be reused in this state.
Encrypting the communication ensures that the data cannot be reassembled, and the key frames cannot be extracted anymore. This provides an additional layer of security.
This community is not the best place to publish how exactly to reassembly, and extract that data. I hope you understand.0 -
Hi, Norman.
I understood.
Thank you for reply.
0
Post is closed for comments.
Comments
2 comments