18.11.2012 Views

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Any CA may unilaterally revoke another CA certificate it has issued. However, the ROA for a<br />

<strong>Raytheon</strong> CA shall revoke a Subject CA certificate only in the case of an emergency.<br />

Generally, the certificate shall be revoked based on the subject request, authorized<br />

representative of subject request, or RPMA request.<br />

Upon receipt of a revocation request, a CA shall authenticate the request and then revoke the<br />

certificate. In the case of a CA certificate issued by a <strong>Raytheon</strong> CA, the ROA shall seek<br />

guidance from the RPMA before revocation of the certificate except when the RPMA is not<br />

available and there is an emergency situation such as:<br />

� Request from the Signing CA for reason of key compromise;<br />

� Determination by the <strong>Raytheon</strong> Operational Authority that a Subject CA key is<br />

compromised; or<br />

� Determination by the <strong>Raytheon</strong> Operational Authority that a Subject CA is in violation<br />

of the CP or CPS to a degree that threatens the integrity of the <strong>Raytheon</strong> <strong>PKI</strong>.<br />

At the medium-hardware, medium-CBP-hardware, and high-hardware assurance levels, a<br />

Subscriber ceasing its relationship with an organization that sponsored the certificate shall, prior<br />

to departure, surrender to the organization (through any accountable mechanism) all<br />

cryptographic hardware tokens that were issued by or on behalf of the sponsoring organization.<br />

The token shall be zeroized or destroyed promptly upon surrender and shall be protected from<br />

malicious use between surrender and zeroization or destruction.<br />

If a Subscriber leaves an organization and the hardware tokens cannot be obtained from the<br />

Subscriber, then all Subscriber certificates associated with the unretrieved tokens shall be<br />

immediately revoked for the reason of key compromise.<br />

4.9.4 Revocation Request Grace Period<br />

There is no revocation grace period. Responsible parties must request revocation as soon as<br />

they identify the need for revocation.<br />

4.9.5 Time within which CA must Process the Revocation Request<br />

RRCA shall process all revocation requests within six hours of receipt of request.<br />

For Signing CAs, revocation request processing time shall be as specified below:<br />

Assurance Level Processing Time for Revocation Requests<br />

Medium Software and<br />

Medium CBP Software<br />

Medium Hardware and<br />

Medium CBP Hardware<br />

Within 18 hours of receipt of request<br />

Within 18 hours of receipt of request<br />

High Hardware Within six hours of receipt of request<br />

4.9.6 Revocation Checking Requirements for Relying Parties<br />

Use of revoked certificates could have damaging or catastrophic consequences in certain<br />

applications. The matter of how often new revocation data should be obtained is a<br />

determination to be made by the Relying Party and the system accreditor. If it is temporarily<br />

infeasible to obtain revocation information, then the Relying Party must either reject use of the<br />

37 7/25/2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!