PKI Private keys Not In Plain Text Outside Cryptographic Module Boundary, v1.0

Addresses requirements for protection of PKI private keys during transfer.
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
PKI Private keys Not In Plain Text Outside Cryptographic Module Boundary (PKIPrivatekeysNotInPlainTextOutsideCryptographicModuleBoundary)
Does the organization ensure that PKI private keys are never in plaintext form outside the cryptographic module boundary?
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
Private keys must never exist in plaintext form outside the cryptographic module boundary.
Citation
FBCA-CP
Section 6.2.6.