DOC

ROBUSTNESS RULES

By Dennis Mason,2014-04-19 05:40
10 views 0
ROBUSTNESS RULES

    ROBUSTNESS RULES

    FOR WINDOWS MEDIA FORMAT 9.5 SDK APPLICATIONS

    0. DEFINITIONS

    The following terms have the meanings set forth below. Other initially capitalized terms

    not defined in these Compliance Rules have the meanings ascribed to them in the License

    Agreement or the Microsoft Implementation.

    0.1 Application” means software applications running on the Windows

    Media Format SDK and making use of WMDRM functionality.

    0.2 Application Secrets” means, collectively, the WMDRM stub library

    provided to the Company and secrets such as symmetric keys and private

    keys that reside in the Application binary and/or in the process space of

    the Application.

    0.3 Certificate” means a unique WMDRM object used to assess trust,

    including whether or not a device or application has been revoked.

    0.4 Certificate Revocation List” means a list of Certificates that have been

    revoked.

    0.5 Certified Output Protection Protocol” or “COPP” enables a robust

    signaling and content delivery mechanism between the Application and

    video device drivers.

    0.6 Circumvention Device” means a hardware, software or hybrid entity

    whose primary purpose is the circumvention of Security Functions.

    0.7 Collaborative Play-enabled Licensed Products” means Licensed Products

    that implement Collaborative Play as prescribed by the Compliance

    Rules.

    0.8 Collaborative Session Secrets” means secrets pertaining to the execution

    of Collaborative Play as prescribed by the Compliance Rules, including

    without limitation recompressed content encryption keys or assets used

    by the Licensed Product to secure the exchange of these keys.

    0.9 Companymeans an entity licensed under a License Agreement to

    develop Licensed Products.

    0.10 “Compliance Rules” means the Compliance Rules for the licensed

    WMDRM Technology, as such Compliance Rules may be amended from

    time to time.

     Robustness Rules for WMF 9.5 SDK

    Microsoft Confidential -1- 4-30-06

0.11 Compliant Product” refers to a Licensed Product that is in compliance

    with all applicable Robustness and Compliance Rules.

    0.12 Content Key” means a symmetric key used to decrypt WMDRM Content. 0.13 COPP Session Assets” means the sequence numbers and protection

    settings for a given COPP session, as described in the Technical

    Documentation.

    0.14 COPP Session Key” means the data integrity key for a given COPP

    Session as described in the Technical Documentation.

    0.15 Debugging Aids” means software/hardware components supporting

    debugging and profiling tools and/or technologies, including without

    limitation debugging symbols in software.

    0.16 Source ID” means a WMDRM Policy contained in the WMDRM License.

    0.17 DTCP Source Content” shall mean content where the WMDRM license

    includes a Source ID of 258, indicating it was received from Digital

    Transmission Content Protection.

    0.18 Effective Resolution” means an image having a visual equivalence not

    more than the total number of pixels per frame specified. For the

    avoidance of doubt, an image of Effective Resolution may be Passed

    using video processing techniques such as line doubling, scaling, or

    sharpening.

    0.19 License Agreement” means the agreement under which Microsoft

    licenses entities to develop and distribute products that include and use

    the WMDRM components contained in the Windows Media Format

    SDK redistributable components.

    0.20 Licensed Product” means a software application (or other software

    component, which may be a separately identifiable subset of a software

    application or operating system) that (i) implements WMDRM subject to

    a license from Microsoft, (ii) may be capable of passing WMDRM

    Content and (iii) may make use of WMDRM functionality.

    0.21 Licensed Technology means the WMF SDK.

    0.22 Microsoft Implementation of WMDRM-ND means the implementation

    of WMDRM-ND functionality provided as source code, binaries,

    technical documentation, tools and/or sample files as provided to

    Company under the License Agreement.

    0.23 “Public Cryptography Constants” means all applicable public keys in the

    public key cryptography sense that are used to validate certificates and/or

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -2- 4-30-06

    signatures as prescribed in the Compliance Rules, except those used to

    execute the COPP protocol. Public Cryptography Constants include,

    without limitation, the root public key used to authenticate the WMF

    SDK API at run time.

    0.24 Robustness Rules” means the rules and requirements set out in this

    document, as they may be amended from time to time by Microsoft.

    0.25 Security Functions” means functions related to protection of content as

    prescribed by the Technical Documentation and the Compliance Rules

    except those related to COPP execution, including without limitation

    transfer of WMDRM Content to WMDRM-ND Receivers, Collaborative

    Play including without limitation enforcement of maximum number of

    Collaborative Players concurrently receiving content from a given

    Collaborative Player, and WMDRM-ND transmission including without

    limitation enforcement of maximum number of WMDRM-ND Receivers

    concurrently receiving WMDRM Content, as prescribed by the

    Technical Documentation.

    0.26 Technical Documentation” means, collectively, the WMF SDK

    Technical Documentation and the Microsoft Implementation of

    WMDRM-ND.

    0.27 Unprotected WMDRM Content” means audio and/or video content that

    is governed by WMDRM Policy in a form that is inconsistent with such

    WMDRM Policy, as described by the Microsoft Implementation and the

    Compliance Rules.

    0.28 WMDRM” means Windows Media Digital Rights Management

    technology.

    0.29 WMDRM Contentmeans audio and/or video content that has been

    encrypted and recorded using WMDRM, and whose usage is governed

    by a WMDRM License.

    0.30 WMDRM License” means a data structure that contains, but is not

    limited to, WMDRM Policy and an encrypted Content Key associated

    with specific WMDRM Content.

    0.31 WMDRM Policy” means the description of the actions permitted and/or

    required for or with WMDRM Content and restrictions on those actions

    as described in the WMDRM License associated with the WMDRM

    Content.

    0.32 WMDRM Technology” means the methods for local decryption and

    renewability developed by Microsoft for use with Windows Media

    Digital Rights Management.

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -3- 4-30-06

0.33 WMDRM-ND” means WMDRM for Networked Devices.

    0.34 WMDRM-ND Receiver” means a device, licensed by Microsoft, to

    connect to WMDRM-ND Transmitters and acquire WMDRM Licenses

    and WMDRM Content.

    0.35 WMDRM-ND Session Assets” means the bookkeeping assets

    maintained by the WMDRM-ND Transmitter to fulfill requirements of

    the Technical Documentation and the Compliance Rules; for example,

    without limitation, the number of devices being served at the current

    time.

    0.36 WMDRM-ND Transmitter” means a product licensed under the License

    Agreement for WMDRM-ND Platforms that complies with the

    applicable Compliance Rules and passes WMDRM Content and

    WMDRM Licenses to a WMDRM-ND Receiver.

    0.37 WMDRM-ND Transmitter-enabled Licensed Products” means Licensed

    Products that implement WMDRM-ND Transmitter functions, as

    prescribed by the Compliance Rules.

    0.38 WMF SDK” means Windows Media Format Software Development Kit.

    0.39 WMF SDK Technical Documentation” means documentation provided

    with the WMF SDK.

    1. CONSTRUCTION

    1.1 Generally. Licensed Products as shipped must meet the applicable

    Robustness and Compliance Rules and be designed and manufactured so

    as to resist attempts to modify such products so as to defeat the functions

    of the Technical Documentation, as more specifically described herein.

    1.2 Defeating Functions and Features. Licensed Products must not include

    control functions means, software switches, backdoors, bypasses, end-

    user selectable options, debuggers or Debugging Aids, or mechanisms

    for self-tampering or delayed loading by which the Security Functions

    may be defeated. Licensed Products must not use, incorporate, call or

    enable any software that modifies the behavior of the Licensed Product

    in a manner that causes it to violate the Compliance Rules. This Section

    1.2 does not prohibit Company from designing and implementing its

    products incorporating means used by Company or professionals to

    analyze or debug deployed products, or to design its products

    incorporating software protection techniques such as obfuscation or

    fragilization, provided, however, that such means do not provide a

    pretext for inducing consumers to defeat or circumvent mandatory

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -4- 4-30-06

    provisions of the Technical Documentation, Robustness Rules or

    Compliance Rules.

    1.3 Keep Secrets. Licensed Products must be designed and manufactured

    such that they resist attempts to each and all of the following:

    1.3.1 Use or replace without authority the Application Secrets. For this

    Section 1.3.1, „use without authority‚Äü refers to direct or indirect use

    or leverage of the Application Secrets by a software entity other

    than the Licensed Product, by which the Security Functions may

    be defeated;

    1.3.2 Replace without authority the Public Cryptographic Constants;

    1.3.3 For WMDRM-ND Transmitter-enabled Licensed Products, replace

    without authority the WMDRM-ND Session Assets;

    1.3.4 For Collaborative Play-enabled Licensed Products, discover, reveal,

    replace or use without authority the Collaborative Session Secrets. 2. ACCESSIBILITY OF CONTENT. Company must design and develop Licensed

    Products such that Unprotected WMDRM Content must not be available as output or via

    unrestricted application APIs, and must not travel or otherwise be placed outside the

    application process except as allowed by the Compliance Rules.

    3. METHODS OF MAKING FUNCTIONS ROBUST

    Licensed Products must use at least the following techniques to be designed to effectively

    frustrate efforts to circumvent or defeat all applicable Security Functions and protections

    specified in the Compliance and Robustness Rules:

    3.1 The Licensed Product must include all of the characteristics set forth in

    Sections 1 and 2 of these Robustness Rules. In addition, the Licensed

    Product must:

    3.1.1 Achieve compliance with Sections 1 and 2 of these Robustness

    Rules, to the extent required by Section 4, by reasonable and

    effective methods, which may include use of techniques of

    obfuscation to disguise and hamper attempts to discover the

    approaches used and/or secrets concealed within the software,

    and/or self-checking of integrity in such a manner as to result in a

    failure to execute Security Functions in the event of unauthorized

    modification.

    3.1.2 Be implemented such that the failure of a Security Function would

    cause the implementation to cease further processing and explicitly

    fail safely, as prescribed by the Technical Documentation.

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -5- 4-30-06

    4. REQUIRED LEVELS OF ROBUSTNESS

    4.1 The Security Functions and the characteristics set forth in Sections 1.3.1

    and 1.3.2 must be implemented so that it is reasonably certain that they:

    4.1.1 Cannot be defeated or circumvented using Widely Available Tools

    or Specialized Tools.

    4.2 The Security Functions and the characteristics set forth in Sections 1.3.3,

    and 1.3.4, wherever applicable, must be implemented so that it is

    reasonably certain that they:

    4.2.1 Cannot be defeated or circumvented using Widely Available Tools.

    4.2.2 Can only with difficulty be defeated or circumvented using

    Specialized Tools.

    4.3 Licensed Products shall be clearly designed such that when decrypted

    uncompressed video data from DTCP Source Content with a resolution

    greater than an Effective Resolution of 520000 pixels per frame is

    transmitted over User Accessible Bus, it is reasonably certain that such

    data:

    4.3.1 Are reasonably secure from unauthorized interception by using

    either Widely Available Tools or Specialized Tools, except with

    difficulty, other than Circumvention Devices. The level of

    difficulty applicable to Widely Available Tools is such that a

    typical consumer should not be able to use Widely Available Tools,

    with or without instructions, to intercept such data without risk of

    serious damage to the product or personal injury. 4.4 Widely Available Tools” means unrestricted application APIs and

    general-purpose tools or software that are widely available at a

    reasonable price, such as file readers, file editors, file comparison

    utilities and internet traffic analyzers, other than Circumvention Devices. 4.5 Specialized Tools” means specialized tools, equipment or software that

    are widely available at a reasonable price, such as page file scanners,

    kernel mode code, and memory readers and writers, other than

    Circumvention Devices.

    4.6 User Accessible Bus” means a data bus that is designed for end user

    upgrades or access, such as PCMCIA, device bay, IEEE 1394, PCI buses

    with user accessible sockets or Cardbus, but not graphics buses, memory

    buses, CPU buses, internal PCI buses or other point-to-point buses, and

    similar portions of a device's internal architecture. This Section 4.6 does

    not prohibit Company from designing and manufacturing its products

    incorporating means, such as test points, used by Company or

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -6- 4-30-06

    professionals to analyze or repair products, provided, however, that such

    means do not provide a pretext for inducing consumers to obtain ready

    and unobstructed access to internal connectors.

5. NEW CIRCUMSTANCES. If a Licensed Product when designed and shipped

    complies with the Robustness Rules set forth above, but at any time thereafter

    circumstances arise which, had they been existing at the time of design, would have

    caused such implementation to fail to comply with the Robustness Rules ("New

    Circumstances"), then upon becoming aware of such New Circumstances, Company shall promptly redesign the affected Licensed Product(s) or make available upgrades to its

    affected Licensed Product(s) to make such Licensed Products compliant with the

    Robustness Rules under the New Circumstances, and, as soon as reasonably practicable,

    consistent with ordinary product cycles and taking into account the level of threat to

    content under the New Circumstances, shall incorporate such redesign or replacement

    into its affected Licensed Product(s), or if such redesign or upgrades are not possible or

    practical, cease manufacturing such affected Licensed Product(s) and cease selling such

    affected Licensed Product(s).

     Robustness Rules for WMF 9 Series SDK

    Microsoft Confidential -7- 4-30-06

Report this document

For any questions or suggestions please email
cust-service@docsford.com