Subscriber Acknowledgement of Receipt of Private Keys, v1.0

Addresses the requirement for subscriber acknowledgement of delivery of private keys.
NOTE: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
Subscriber Acknowledgement of Receipt of Private Keys (SubscriberAcknowledgementofReceiptofPrivateKeys)
When Private keys are delivered, does the Subscriber acknowledge receipt of the private key(s)?
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
When Private keys are delivered electronically, the Subscriber shall acknowledge receipt of the private key(s). When Private keys are delivered on a hardware cryptographic module, the Subscriber shall acknowledge receipt of the private key(s).
Citation
FBCA-CP
Section 6.1.2.