This functionality is accessible by default for hardware level DRM implementation from all three different DRMs (for example, Widevine Modular Level1, Playready SL3000, and Fairplay DRMs (with OS 12+)). However, this security is primarily applicable on native app implementation types on mobile devices; browser-based viewing on Android devices is not necessarily subject to the same restrictions.
For instance, if an Android device is able to support widevine Level 1 implementation, then it offers security against screen recording during the playing of content using an Android application.
However, the same device cannot offer the same level of protection to the user when the content is being played on browsers (like chrome). The use of Firefox and other browsers is not an option because these browsers do not offer support for widevine DRMan anti-piracy tool when the content is being consumed on an android smartphone. However, if the service provider has a compelling use case to provide chrome browser-based playback on android mobile and they would also like to ensure protection against screen capturing, then they will need to invest in chrome-specific screen capture protection solutions such as this anti screen capture.
Protection of the output (HDCP/CGMS):
After being enabled with the appropriate parameters, digital rights management solutions (DRM) can provide the capability to safeguard against recording via digital output signals (such as HDCP) or analogue output signals (such as VGA, etc.).
When this is activated, it guarantees that the content being sent is of HD quality and that it will not be copied out by using HDMI or VGA types of digital or analogue output once it has been copied out. Devices that are able to support the hardware level of DRM implementation are the only ones that can make this feature available (e.g. Widevine Level 1 for android). This functionality cannot be provided for devices that simply have a software implementation (such as Widevine Level 3 on Android), which are the case for all other devices.
However, despite the fact that some devices offer support for DRM at the hardware level, it is not as simple to accomplish as it may appear because of the complicated nature of HDCP implementation at the device end. The following situations have the potential to cause complications.
During the process of encrypting the video file, the data will be jumbled up by an algorithm, which will render the file useless. Because of this, there is no chance that the data can be decoded. This is made possible with the assistance of a key, which, in conjunction with the algorithm, is used in order to encrypt and decode the digital information. This makes it possible for a third party to read the information that has been encrypted. Because of this, deciphering the information, even if it has been encrypted, is not impossible. Every single component of the video and the asset, including the audio, the video that was captured in standard definition (SD), and the video that was captured in high definition (HD), makes use of its very own unique special key. As a result of this, the process of encrypting or decrypting a video clip is classified as an operation that makes use of symmetric cryptography. This is because symmetric cryptography employs the same key to encrypt and decrypt the file.
