Robust Implementation Sample Clauses
Robust Implementation. 31.2.1. Implementations of Content Protection Systems on General Purpose Computer Platforms shall use hardware-enforced security mechanisms, including secure boot and trusted execution environments, where possible.
31.2.2. Implementation of Content Protection Systems on General Purpose Computer Platforms shall, in all cases, use state of the art obfuscation mechanisms for the security sensitive parts of the software implementing the Content Protection System.
31.2.3. All General Purpose Computer Platforms (devices) deployed by Licensee after end December 31st, 2013, SHALL support hardware-enforced security mechanisms, including trusted execution environments and secure boot.
31.2.4. All implementations of Content Protection Systems on General Purpose Computer Platforms deployed by Licensee (e.g. in the form of an application) after end December 31st, 2013, SHALL use hardware-enforced security mechanisms (including trusted execution environments) where supported, and SHALL NOT allow the display of HD content where the General Purpose Computer Platforms on which the implementation resides does not support hardware-enforced security mechanisms.
Robust Implementation. 1.4.1.1. Implementation of Approved Protection Systems on Software Devices shall, in all cases, use state of the art obfuscation mechanisms or trusted execution environments for the security sensitive parts of the software implementing the Content Protection System.
1.4.1.2. All Software Devices deployed by Licensee after end December 31st, 2013, SHALL support trusted execution environments. For the avoidance of doubt, this requirement applies to actual, physical devices which are deployed to Subscribers by Licensee only and does not apply to software Playback Clients or Applications distributed by Licensee.
Robust Implementation. 38.2.1. Implementations of Content Protection Systems on General Purpose Computer Platforms shall use hardware-enforced security mechanisms, including secure boot and trusted execution environments, where possible.
38.2.2. Implementation of Content Protection Systems on General Purpose Computer Platforms shall, in all cases, use state of the art Agreement (16JUN10) maa-SMSS-SPT CLOUDY 3D CLOUDY_MONSTER HOUSE Letter Agreement (17JUN10) maa.doc obfuscation mechanisms for the security sensitive parts of the software implementing the Content Protection System.
38.2.3. All General Purpose Computer Platforms (devices) deployed by Licensee after end December 31st, 2013, SHALL support hardware- enforced security mechanisms, including trusted execution environments and secure boot.
38.2.4. All implementations of Content Protection Systems on General Purpose Computer Platforms deployed by Licensee (e.g. in the form of an application) after end December 31st, 2013, SHALL use hardware-enforced security mechanisms (including trusted execution environments) where supported, and SHALL NOT allow the display of HD content where the General Purpose Computer Platforms on which the implementation resides does not support hardware- enforced security mechanisms.
Robust Implementation. 4.1. Implementations of Content Protection Systems shall use hardware-enforced security mechanisms, including secure boot, secure key storage and a trusted execution environment.
4.2. Implementation of Content Protection Systems shall additionally be protected from the reverse engineering of the security sensitive parts of the software implementing the Content Protection System. The protection from reverse engineerings shall be different between different versions of the Content Protection System. By way of example, if the software obfuscation is used the form of the obfuscation has to be different between versions.
Robust Implementation