Non-Null Subject Distinguished Name (DN) In End Entity Certificates, v1.0

Addresses requirements for certificates issued to end entities to include a non-NULL subject DN.
If an assessment step references organization-defined elements (E.g. <organization-defined personnel or roles>, <organization-defined frequency>, etc.), corresponding citations/excerpts must be provided to confirm that the organization has established and documented these values and that they apply as referenced in the conformance criteria.

Similarly, if a "Selection" among multiple options (e.g. [Selection (one or more): as needed; ]) is specified, evidence must be provided to establish that the option(s) implemented by the organization have been defined and documented.

The assessment step shall not be marked as satisfied without this evidence.

Assessment Step

1
Non-Null Subject Distinguished Name (DN) In End Entity Certificates (Non-NullSubjectDistinguishedNameDNInEndEntityCertificates)
For other than PKI certificates requiring a rudimentary level of assurance, does the organization only generate End Entity PKI certificates that contain a non-null subject Distinguished Name (DN)?
Artifact
A1
Provide evidence (e.g. organizational policies, procedures, compliance/assessment reports, etc.) that support the assessor's response to this assessment step.
If conformance criteria reference organization-defined elements (e.g. <organization-defined personnel or roles>, <organization-defined frequency>, etc.), these values must be defined and documented by the organization.

Similarly, if the criteria specify a "Selection" among multiple options (e.g. [Selection (one or more): as needed; ]), the option(s) implemented by the organization must also be defined and documented.

Conformance Criteria (1)

C1
All certificates issued to end entities, except those issued at the Rudimentary level of assurance, shall include a non-NULL subject DN.
Citation
FBCA-CP
Section 3.1.1.