Secrecy Required and Integrity Required Sample Clauses

Secrecy Required and Integrity Required. In addition to those items listed as Secrecy Required on the table below, intermediate data items that are derived from such Secrecy Required items shall also be treated as Secrecy Required. Examples include but are not limited to Kvu, also known as the Volume Unique Key and which is derived from the Media Key and the Volume ID as defined in the Specifications, and the random/pseudorandom number generator constants k and S, as defined in the Specifications. Secrecy Required* Device Keys Sequence Keys Drive Private Key Host Private Key Media Keys Media Key Variant Title Keys Cmfg Data Key Bus Key MCS Private Key PVAS Private Key Algorithms described in specifications marked Confidential, including “HD-DVD and DVD Pre-recorded Book Confidential Part for CE System” and “HD-DVD and DVD Pre-recorded Book Confidential Part for PC-based System” Integrity Required** AACS LA Public Key AACS LA Content Cert Public Key MCS Public Key PVAS Public Key Device Binding Nonce Pre-recorded Media Serial Number Prepared Video Serial Number DRL or individual components thereof, when being stored in non-volatile storage by a Licensed Product as required in the Specifications CRL, or individual segments thereof, when being stored in non-volatile storage by a Licensed Product as required in the Specifications MKB when being stored in non-volatile storage by a Licensed Product as required in the Specifications Partial MKB, or individual components thereof, when being stored in non-volatile storage by a Licensed Product as required in the Specifications * Note: KCD is not Secrecy Required, but is subject to the robustness requirements of the Adopter Agreement, Exhibit E, Part 2, Section 7.11. ** Note: Volume ID, Media ID, and Binding Nonce are not Integrity Required but are subject to the robustness requirements of the Adopter Agreement, Exhibit E, Part 2, Section 7.10. Appendix 2
Sample 1See All (4)
AutoNDA by SimpleDocs
Secrecy Required and Integrity Required. In addition to those items listed as Secrecy Required on the table below, intermediate data items that are derived from such Secrecy Required items shall also be treated as Secrecy Required. Examples include but are not limited to Kvu, also known as the Volume Unique Key and which is derived from the Media Key and the Volume ID as defined in the Specifications, and the random/pseudorandom number generator constants k and S, as defined in the Specifications. Secrecy Required* Device Keys Sequence Keys Drive Private Key Host Private Key Media Keys Title Keys Algorithms described in specifications marked Confidential, including “HD-DVD and DVD Pre-recorded Book Confidential Part for CE System” and “HD-DVD and DVD Pre-recorded Book Confidential Part for PC-based System” Integrity Required** AACS LA Public Key AACS LA Content Cert Public Key Pre-recorded Media Serial Number DRL or individual components thereof, when being stored in non-volatile storage by a Licensed Product as required in the technical specifications CRL, or individual segments thereof, when being stored in non-volatile storage by a Licensed Product as required in the technical specifications MKB when being stored in non-volatile storage by a Licensed Product as required in the technical specifications Partial MKB, or individual components thereof, when being stored in non-volatile storage by a Licensed Product as required in the technical specifications * Note: KCD is not Secrecy Required but is subject to the robustness requirements of Part 2, Section 3.6.9.
Sample 1

Related to Secrecy Required and Integrity Required

  • Security Requirements 11.1 The Supplier shall comply, and shall procure the compliance of the Suppliers Personnel, with the Security Policy and the Security Plan and the Supplier shall ensure that the Security Plan produced by the Supplier fully complies with the Security Policy.

  • Data Security Requirements A. Data Transport. When transporting Confidential Information electronically, including via email, the data will be protected by:

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

  • Facility Requirements 1. Maintain wheelchair accessibility to program activities according to governing law, including the Americans With Disabilities Act (ADA), as applicable.

  • E-Verify Requirements To the extent applicable under ARIZ. REV. STAT. § 41- 4401, the Contractor and its subcontractors warrant compliance with all federal immigration laws and regulations that relate to their employees and their compliance with the E-verify requirements under ARIZ. REV. STAT. § 23-214(A). Contractor’s or its subcontractor’s failure to comply with such warranty shall be deemed a material breach of this Agreement and may result in the termination of this Agreement by the City.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:

  • Safety Requirements 18.1.1 The Concessionaire shall comply with the provisions of this Agreement, Applicable Laws and Applicable Permits and conform to Good Industry Practice for securing the safety of the Users. In particular, the Concessionaire shall develop, implement and administer a surveillance and safety program for providing a safe environment on or about the Project, and shall comply with the safety requirements set forth in Schedule-L (the “Safety Requirements”).

  • City Requirements Design, construction, materials, sizing, other specifications, permitting, inspections, testing, documentation and furnishing of as-built drawings, and acceptance of completed infrastructure shall be in accordance with City Requirements. Design and construction shall be by professionals licensed in the state of North Carolina to do the relevant work. City approval of the design of the Improvements shall be required prior to construction, as set forth in City Requirements. If Developer is connecting to the County sewer system, the City may require Developer to furnish the contract providing for such connection.

  • Health and Safety Requirements The Contractor and his subcontractors ensure at all times compliance with safety regulations imposed by any Act of Parliament, ordinance or any regulation or by¬law of any local or statutory authority. Occupational Health and Safety Act (Act of 1993-Section 37) The Contractor shall comply with:  The Occupational Health and Safety Xxx, 0000, and all Regulations made there under;  All Eskom Safety and Operating Procedures listed in this Works Information. The Contractor acknowledges that it is fully aware of the requirements of all the above and undertakes to employ only people who have been duly authorised in terms thereof and who have received sufficient training to ensure that they can comply therewith. The Contractor undertakes not to do, or not to allow anything to be done which will contravene any of the provisions of the Act, Regulations or Safety and Operating Procedures. The Contractor shall appoint a person who will liaise with the Eskom Safety Officer responsible for the premises relevant to this contract. The person so appointed shall, on request:  Supply the Eskom Safety Officer with copies of minutes of all Health and Safety Committee meetings, whenever he is required to do so;  Supply the Eskom Safety Officer with copies of all appointments in respect of employees employed on this contract, in terms of the Act and Regulations and shall advise the Eskom Safety Officer of any changes thereto. Eskom may, at any stage during the currency of this agreement, be entitled to:  Do safety audits at the Contractor’s premises, its work-places and on its employees;  Refuse any employee, sub-contractor or agent of the Contractor access to its premises if such person has been found to commit any unlawful act or any unsafe working practice or is found to be not authorised or qualified in terms of the Act;

  • Expenditure on Safety Requirements All costs and expenses arising out of or relating to Safety Requirements shall be borne by the Concessionaire to the extent such costs and expenses form part of the works and services included in the Scope of the Project, and works and services, if any, not forming part of the Scope of the Project shall be undertaken in accordance with the provisions of Article 16. Costs and expenses on works and services not covered hitherto before and arising out of Safety Requirements shall, subject to the provisions of Clause 16.3.2, be borne from out of a dedicated safety fund (the “Safety Fund”) to be funded, owned and operated by the Authority or a substitute thereof.

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