Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

4.6.1 Circumstance for Certificate Renewal
Not applicable.
4.6.2 Who may Request Renewal
Not applicable.
4.6.3 Processing Certificate Renewal Requests
Not applicable.
4.6.4 Notification of New Certificate Issuance to Subscriber
Not applicable.
4.6.5 Conduct Constituting Acceptance of a Renewal Certificate
Not applicable.
4.6.6 Publication of the Renewal Certificate by the CA
Not applicable.
4.6.7 Notification of Certificate Issuance by the CA to Other Entities
Not applicable.
4.7 Certificate Re-Key
The longer and more often a key is used, the more susceptible it is to loss or discovery.
Therefore, it is important that a Subscriber periodically obtains new keys and reestablishes its
identity. Re-keying a certificate means that a new certificate is created that has the same
characteristics and level as the old one, except that the new certificate has a new, different
public key (corresponding to a new, different private key) and a different serial number, and it
may be assigned a different validity period.
4.7.1 Circumstance for Certificate Re-key
A CA may issue a new certificate to the Subject when the Subject has generated a new key pair
and is entitled to a certificate.
4.7.2 Who may Request Certification of a New Public Key
A Subject may request the re-key of its certificate.
A PKI Sponsor may request re-key of a component certificate.
4.7.3 Processing Certificate Re-keying Requests
A certificate re-key shall be achieved using one of the following processes:
� Initial registration process as described in Section 3.2; or
� Identification & Authentication for Re-key as described in Section 3.3.
For cross certificates issued by a Raytheon CA, certificate re-key also requires that a valid MOA
exists between Raytheon and the cross certified PKI, and the term of the MOA is beyond the
expiry period for the new certificate.
34 7/25/2011