Skip to content

Commit 2621872

Browse files
authored
Update media-services-content-protection-overview.md
1 parent e724bf8 commit 2621872

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/media-services/previous/media-services-content-protection-overview.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,9 @@ Customers often wonder whether they should use AES encryption or a DRM system. T
4949

5050
PlayReady, Widevine, and FairPlay all provide a higher level of encryption compared to AES-128 clear key encryption. The content key is transmitted in an encrypted format. Additionally, decryption is handled in a secure environment at the operating system level, where it's more difficult for a malicious user to attack. DRM is recommended for use cases where the viewer might not be a trusted party and you require the highest level of security.
5151

52+
> [!NOTE]
53+
> If content is encrypted with a clear key and it is sent over HTTPS, the content is not in clear until it reaches the client.
54+
5255
## Storage encryption
5356
You can use storage encryption to encrypt your clear content locally by using AES 256-bit encryption. You then can upload it to Azure Storage, where it's stored encrypted at rest. Assets protected with storage encryption are automatically unencrypted and placed in an encrypted file system prior to encoding. The assets are optionally re-encrypted prior to uploading back as a new output asset. The primary use case for storage encryption is when you want to secure your high-quality input media files with strong encryption at rest on disk.
5457

0 commit comments

Comments
 (0)