Common use of Secure Clock Clause in Contracts

Secure Clock. The Content Protection System shall implement a secure clock. The secure clock must be protected against modification or tampering and detect any changes made thereto. If any unauthorized changes or tampering are detected, the Content Protection System must revoke the licenses associated with all content employing time limited license or viewing periods. The clock is protected by login only allowed by authorized personnel and content playback continues on with the new time. Playback continues on current rules by stopping at end of file with limitations set on guests availability to rewind/fast forward/pause such as 3 minutes prior to the end of the movie the guest can no longer rewind. Conditional Access LodgeNet’s D2R uses utilizes secure conditional access to allow one addressable device to access the content stream per user transaction. Licensee utilizes secure conditional access to allow one addressable device to access the content stream per user transaction. Accessible content delivered to individual end user devices shall be incapable of being transferred between such devices. The Content Protection System shall not import or protect content from untrusted sources. Protection Against Hacking. Playback licenses, revocation certificates, and security-critical data shall be cryptographically protected against tampering, forging, and spoofing. The Content Protection System shall employ industry accepted tamper-resistant technology on hardware and software components (e.g., technology to prevent such hacks as a clock rollback, spoofing, use of common debugging tools, and intercepting unencrypted content in memory buffers). Examples of techniques included in tamper-resistant technology are: The conditional access and Pro:Idiom robustness rules ensure the transmitting and receiving devices are indeed part of the system (authorized). Code and data obfuscation: The executable binary dynamically encrypts and decrypts itself in memory so that the algorithm is not unnecessarily exposed to disassembly or reverse engineering.

Appears in 2 contracts

Samples: wikileaks.org, wikileaks.org

AutoNDA by SimpleDocs

Secure Clock. The Content Protection System shall implement a secure clock. The secure clock must be protected against modification or tampering and detect any changes made thereto. If any unauthorized changes or tampering are detected, the Content Protection System must revoke the licenses associated with all content employing time limited license or viewing periods. The clock is protected by login only allowed by authorized personnel and content playback continues on with the new time. Playback continues on current rules by stopping at end of file with limitations set on guests availability to rewind/fast forward/pause such as 3 minutes prior to the end of the movie the guest can no longer rewind. Conditional Access LodgeNet’s D2R uses utilizes secure conditional access to allow one addressable device to access the content stream per user transaction. Licensee utilizes secure conditional access to allow one addressable device to access the content stream per user transaction. Accessible content delivered to individual end user devices shall be incapable of being transferred between such devices. The Content Protection System shall not import or protect content from untrusted sources. Protection Against Hacking. Playback licenses, revocation certificates, and security-critical data shall be cryptographically protected against tampering, forging, and spoofing. The Content Protection System shall employ industry accepted tamper-resistant technology on hardware and software components (e.g., technology to prevent such hacks as a clock rollback, spoofing, use of common debugging tools, and intercepting unencrypted content in memory buffers). Examples of techniques included in tamper-resistant technology are: The conditional access and Pro:Idiom robustness rules ensure the transmitting and receiving devices are indeed part of the system (authorized). Code and data obfuscation: The executable binary dynamically encrypts and decrypts itself in memory so that the algorithm is not unnecessarily exposed to disassembly or reverse engineering.

Appears in 2 contracts

Samples: wikileaks.org, wikileaks.org

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.