Home Similarity Diff BR Diff CS Diff EVG Diff SMIME Diff TLS

Home Show similarity Differences BR (in/out) Differences CS (in/out) Differences EVG (in/out) Differences SMIME (in/out) Differences TLS (in/out)

BR

CS

EVG

SMIME

TLS

EVG

#### 7.1.4.3 Additional Technical Requirements for EV Certificates All provisions of the Baseline Requirements concerning Minimum Cryptographic Algorithms, Key Sizes, and Certificate Extensions apply to EV Certificates with the following exceptions: 1. If a Subordinate CA Certificates is issued to a Subordinate CA not controlled by the entity that controls the Root CA, the policy identifiers in the `certificatePolicies` extension MUST include the CA's Extended Validation policy identifier. Otherwise, it MAY contain the anyPolicy identifier. 2. The following fields MUST be present if the Subordinate CA is not controlled by the entity that controls the Root CA. * `certificatePolicies:policyQualifiers:policyQualifierId` `id-qt 1` [RFC 5280] * `certificatePolicies:policyQualifiers:qualifier:cPSuri` HTTP URL for the Root CA's Certification Practice Statement 3. The `certificatePolicies` extension in EV Certificates issued to Subscribers MUST include the following: * `certificatePolicies:policyIdentifier` (Required) The Issuer's EV policy identifier * `certificatePolicies:policyQualifiers:policyQualifierId` (Required) `id-qt 1` [RFC 5280] * `certificatePolicies:policyQualifiers:qualifier:cPSuri` (Required) HTTP URL for the Subordinate CA's Certification Practice Statement 4. The `cRLDistributionPoints` extension MUST be present in Subscriber Certificates if the certificate does not specify OCSP responder locations in an `authorityInformationAccess` extension.

SMIME

#### 7.1.4.3 Subject information - root certificates and subordinate CA certificates By issuing a Subordinate CA Certificate, the CA represents that it followed the procedure set forth in its CP and/or CPS to verify that, as of the Certificate's issuance date, all of the Subject Information was accurate.

TLS

#### 7.1.4.3 Subscriber Certificate Common Name Attribute If present, this attribute MUST contain exactly one entry that is one of the values contained in the Certificate's `subjectAltName` extension (see [Section 7.1.2.7.12](#712712-subscriber-certificate-subject-alternative-name)). The value of the field MUST be encoded as follows: * If the value is an IPv4 address, then the value MUST be encoded as an IPv4Address as specified in RFC 3986, Section 3.2.2. * If the value is an IPv6 address, then the value MUST be encoded in the text representation specified in RFC 5952, Section 4. * If the value is a Fully-Qualified Domain Name or Wildcard Domain Name, then the value MUST be encoded as a character-for-character copy of the `dNSName` entry value from the `subjectAltName` extension. Specifically, all Domain Labels of the Fully-Qualified Domain Name or FQDN portion of the Wildcard Domain Name must be encoded as LDH Labels, and P-Labels MUST NOT be converted to their Unicode representation.

SMIME

##### 7.1.4.3.1 Subject distinguished name fields a. __Certificate Field:__ `subject:commonName` (OID 2.5.4.3) __Required/Optional:__ SHALL be present __Contents:__ This field SHOULD contain an identifier for the Certificate such that the Certificate's Name is unique across all Certificates issued by the Issuing CA. b. __Certificate Field:__ `subject:organizationName` (OID 2.5.4.10) __Required/Optional:__ SHALL be present __Contents:__ This field SHALL contain either the Subject CA's name or DBA as verified under [Section 3.2.3.2.2](#32322-verification-of-assumed-name) The CA MAY include information in this field that differs slightly from the verified name, such as common variations or abbreviations, provided that the CA documents the difference and any abbreviations used are locally accepted abbreviations; e.g., if the official record shows "Company Name Incorporated", the CA MAY use "Company Name Inc." or "Company Name". c. __Certificate Field:__ `subject:countryName` (OID: 2.5.4.6) __Required/Optional:__ SHALL be present __Contents:__ This field SHALL contain the two‐letter ISO 3166‐1 country code for the country in which the CA's place of business is located. d. Other Subject Attributes Other attributes MAY be present within the subject field. If present, other attributes SHALL contain information that has been verified by the CA.