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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

� Any incident preventing a CA from issuing a CRL within 24 hours of the time specified in<br />

the next update field of its currently valid CRL.<br />

The ROA shall reestablish operational capabilities as quickly as possible in accordance with<br />

procedures set forth in the respective CPS.<br />

When <strong>Raytheon</strong> has detected an incident or compromise of the RRCA and/or <strong>Raytheon</strong> signing<br />

CA, and upon approval by the <strong>Raytheon</strong> CISO, the <strong>Raytheon</strong> PMA shall notify the CertiPath<br />

PMA.<br />

The above measures will allow member entities to protect their interests as Relying Parties.<br />

5.7.2 Computing Resources, Software, and/or Data are Corrupted<br />

The CA shall maintain backup copies of system, databases, and private keys in order to rebuild<br />

the CA capability in case of software and/or data corruption.<br />

If a CA or CSA equipment is damaged or rendered inoperative, but the signature keys are not<br />

destroyed; the operation shall be reestablished as quickly as possible, giving priority to the<br />

ability to generate certificate status information. If a CA cannot issue a CRL prior to the time<br />

specified in the next update field of its currently valid CRL, then all CAs that have been issued<br />

certificates by the CA shall be securely 6 notified immediately. This will allow other CAs to<br />

protect their subscribers' interests as Relying Parties.<br />

The CA shall reestablish revocation capabilities as quickly as possible in accordance with<br />

procedures set forth in the respective CPS. If revocation capability cannot be established in a<br />

reasonable time-frame, the CA shall determine whether to request revocation of its certificate(s).<br />

If the CA is a Root CA, the CA shall determine whether to notify all subscribers that use the CA<br />

as a trust anchor to delete the trust anchor.<br />

5.7.3 Private <strong>Key</strong> Compromise Procedures<br />

If a CA signature keys are compromised, lost, or suspected to be compromised:<br />

1. All cross certified CAs shall be securely notified at the earliest feasible time (so that<br />

entities may issue CRLs revoking any cross-certificates issued to the CA);<br />

2. A CA key pair shall be generated by the CA in accordance with procedures set forth in<br />

the applicable CPS;<br />

3. New CA certificates shall be requested in accordance with the initial registration process<br />

as described in section 3.2.;<br />

4. All Subscribers shall be notified and requested to register in accordance with the initial<br />

registration process as described in section 3.2; and<br />

5. If the CA is the Root CA, it shall provide the Subscribers the new trust anchor using<br />

secure means.<br />

The ROA shall also investigate what caused the compromise or loss, and what measures must<br />

be taken to preclude recurrence.<br />

If a CSA key is compromised, all certificates issued to the CSA shall be revoked, if applicable.<br />

The CSA shall generate a new key pair and request new certificate(s), if applicable. If the CSA<br />

is a trust anchor, the relying parties shall be provided the new trust anchor in a secure manner<br />

(so that the trust anchor integrity is maintained) to replace the compromised trust anchor.<br />

6 With confidentiality, source authentication, and integrity security services applied.<br />

56 7/25/2011

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

Saved successfully!

Ooh no, something went wrong!