Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

10.9 Medium Assurance Code Signing Certificate
Field Value
Version V3 (2)
Serial Number Must be unique
Issuer Signature Algorithm sha-1WithRSAEncryption {1 2 840 113549 1 1 5} or
sha256 WithRSAEncryption {1 2 840 113549 1 1 11}
Issuer Distinguished Name ou=class3, o=CAs, dc=raytheon, dc=com
Validity Period No longer than 3 years from date of issue expressed in UTCTime until
2049
Subject Distinguished Name Unique X.500 subject DN within the namespace dc=raytheon, dc=com
as specified in Section 7.1.4 of the Raytheon CP
Subject Public Key
2048 bit RSA key modulus, rsaEncryption
Information
Issuer’s Signature sha-1WithRSAEncryption {1 2 840 113549 1 1 5} or
sha256 WithRSAEncryption {1 2 840 113549 1 1 11}
Extension Value
Authority Key Identifier c=no; Octet String (same as subject key identifier in MASCA certificate )
Subject Key Identifier c=no; Octet String (same as in PKCS#10 request or calculated by the
MASCA)
Key Usage c=yes; digitalSignature; nonRepudiation
Private Key Usage Period c=no; 2 years for 2048 bit keys
Extended key usage c=yes; { iso(1) identified-organization(3) dod(6) internet(1) security(5)
mechanisms(5) pkix(7) id-kp(3) id-kp-codesigning (3) }
Certificate Policies 22 c=no;
SHA1: {1.3.6.1.4.1.1569.10.1.2} or {1.3.6.1.4.1.1569.10.1.4} or
SHA256: {1.3.6.1.4.1.1569.10.1.12} or {1.3.6.1.4.1.1569.10.1.14}
Authority Information Access c=no; id-ad-caIssuers access method entry contains HTTP URL for .p7c
file containing certificates issued to MASCA or LDAP URL pointer to the
caCertificate attribute of the MASCA; id-ad-ocsp access method entry
contains HTTP URL for the MASCA OCSP Responder
Subject Alternative Name DN of the person controlling the code signing private key; RFC822 email
address of role (optional)
Subject Directory Attributes c=no; Entrust User Role= integer, where integer is a numeric role
identifier
CRL Distribution Points 23 c=no
22
Certificate Policies will be asserted such that all lower assurance policies will also be asserted. (For
example if 10.4 is asserted 10.5 will also be asserted).
23
The CRL distribution point extension shall only populate the distributionPoint field. The
distributionPoint field shall contain HTTP (i.e., of the form http://…) URI. The distributionPoint field may
contain LDAP (i.e., of the form ldap://…) URI. The reasons and cRLIssuer fields shall not be populated.
The CRL shall point to a full and complete CRL or a Distribution Point based partitioned CRL. The
Distribution Point field shall contain a full name (i.e, the Distribution Point field shall not contain
nameRelativetoCRLIssuer).
97 7/25/2011