Skip to content

Commit 9928383

Browse files
authored
Update offline-widevine-for-android.md
1 parent 113ff17 commit 9928383

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/media-services/latest/offline-widevine-for-android.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -167,14 +167,12 @@ Depending on business logic of custom STS, different claims are issued in the JW
167167

168168
### Question
169169

170-
For Widevine security levels, in Googles [Widevine DRM Architecture Overview doc](https://storage.googleapis.com/wvdocs/Widevine_DRM_Architecture_Overview.pdf) documentation,
171-
it defines three different security levels. However, in [Azure Media Services documentation on Widevine license template](widevine-license-template-overview.md),
170+
For Widevine security levels, the Googles "Widevine DRM Architecture Overview" doc defines three different security levels. However, in [Azure Media Services documentation on Widevine license template](widevine-license-template-overview.md),
172171
five different security levels are outlined. What is the relationship or mapping between the two different sets of security levels?
173172

174173
### Answer
175174

176-
In Googles [Widevine DRM Architecture Overview](https://storage.googleapis.com/wvdocs/Widevine_DRM_Architecture_Overview.pdf),
177-
it defines the following three security levels:
175+
The Googles "Widevine DRM Architecture Review" doc, defines the following three security levels:
178176

179177
1. Security Level 1: All content processing, cryptography, and control are performed within the Trusted Execution Environment (TEE). In some implementation models, security processing may be performed in different chips.
180178
2. Security Level 2: Performs cryptography (but not video processing) within the TEE: decrypted buffers are returned to the application domain and processed through separate video hardware or software. At level 2, however, cryptographic information is still processed only within the TEE.

0 commit comments

Comments
 (0)