It is targeted at two types of user:

1. OCAP application developers who prepare applications for delivery through a broadcast network.

2. Certificate authorities that support the Public Key Infrastructure (PKI) associated with the OCAP security framework.

Product Overview

1. An Application Developer who, primarily, needs to sign and deliver an application over the broadcast network.

2. An Other Application Developer whose application has generated files in persistent storage and needs to grant access to these files to another application.

3. A Certificate Authority who produces new certificates in response to requests from users (either Application Developers or other Certificate Authorities) and ensures that appropriate action is taken if any of the keys associated with these certificates is compromised.

4. A Root Certificate Authority who manages the self-signed keys that are the trusted source for all certificate chains. This role also includes the role of a Certificate Authority.

5. A Device Manufacturer who needs to sign and deliver an updated code image for their receiver implementation.

A single entity may perform more than one of these roles, for example, a Certificate Authority may also be an Application Developer.

Features for OCAP Application Developers

The OCAP Security File Generator provides facilities for the following steps that you need to take in order to sign applications:

1. Key generation - to produce a public/private key pair that you use to sign applications.

2. Certificate management - to manage all the certificates that are provided by the certificate authorities who generate your certificates.

3. Permission file generation - to create permission files that can include persistent file credentials provided to you by other application developers.

4. Application signing - to create the hash files, certificate files and signature files that are specified in the MHP security framework.

5. Persistent file credential generation - to create a persistent file credential and the associated certificate files that you can pass to other application developers who need access to the files that your application generates in persistent storage.

Product Features for Device Manufacturers

As an OCAP device manufacturer, your main security associated task is to apply a signature to a code image that will be downloaded to the receiver. The code download file is in PKCS#7 Signed Data format and is always signed by the Manufacturer's Code Validation Certificate. The PKCS#7 file may also contain Manufacturer Certificate Authority certificates, the CableLabs Code Validation Root CA certificate and the CableLabs Code Validation CA certificate. The PKCS#7 file may need to be dual signed by both the Manufacturer and by CableLabs in line with CableLabs security policy

The OCAP Security File Generator provides facilities for the following steps that you need to take in order to sign applications:

1. Key generation - to produce a public/private key pair that you use to sign code files.

2. Certificate management - to manage all the certificates that are provided by the certificate authorities that generate your certificates.

3. Code Download signing - to create the PKCS#7 Signed Data file containing the code image and the certificates specified in the OCAP security framework.

4. Code Download dual signing - to add a second (CableLabs) signature to the PKCS#7 Signed Data file already signed by the Device Manufacturer.

Product Features for Certificate Authorities

The OCAP Security File Generator provides facilities for the following functions that you need to provide to your users:

1. Key generation - to produce a public/private key pair that you use to sign applications.

2. Certificate management - to manage all the certificates that are provided by the certificate authorities who generate your certificates and those that you provide to your users.

3. Certificate generation - to produce certificates for application developers and subsidiary certificate authorities as and when requested.

4. CRL generation - to revoke certificates that you have issued and have since been compromised.

For Root Certificate Authorities

1. Root certificate generation - to create a self-signed certificate that provides a point of trust for the certificates that it signs.

2. RCMM generation - to produce RCMMs for distribution to OCAP receivers.

3. RCMM signing - to apply a signature to RCMMs that have been generated by other Root Certificate Authorities