RMP supports encrypting video playback with Advanced Encryption Standard (AES) encryption using a 128-bit key, paired with a time-limited access token.
This page explains how AES-128 works in RMP, when it is a good fit, and what to expect for VOD and live content.
This protection is not applied automatically. To enable it, contact Ravnur.
In this article:
Concepts
The following terms cover the core vocabulary used on this page:
| Name | Description |
| AES-128 | Advanced Encryption Standard using a 128-bit key. Encrypts the media stream behind a video. |
| Access token | A time-limited credential required to play encrypted media. Its duration is configurable. It is issued and applied automatically, with no visible trace in the portal or the video page. |
How AES-128 works
Once enabled, AES-128 encryption is applied to all media uploaded to RMP automatically. All media is covered without additional setup.
Enabling AES-128 does not change the Media Portal or the video page a viewer sees. The switch to encrypted playback is seamless. No one on your team needs to change how they work - content is automatically protected from the moment transcoding is complete.
Limitation:
AES-128 does not apply to the live broadcast. Once the event ends, the recording becomes available with AES-128 encryption applied automatically.
Why use AES-128
Encrypting playback adds a layer of protection against unauthorized reuse of video content and can help meet security requirements for sensitive or premium content.
AES-128 encryption is a good fit when:
Relevant for healthcare, finance, or government content where encryption is a requirement, not just a preference.
The portal handles sensitive or premium content that benefits from restricting reuse.