@@ -2113,61 +2113,28 @@ The validity of the cryptographic mechanisms used to encure those funtions is co
- REFERENCE: ACC-PKI-DM-03
- OBJECTIVE:
Determine whether the product maintains only the configuration data required to implement the PKC management functions applicable to the use case.
- PREPARATION:
- Product configuration documentation.
- List of implemented PKC management functions and associated configuration parameters.
- ACTIVITIES:
1. Review the applicable use case requirements.
2. Identify all PKC management functions implemented by the product.
3. Review all PKC-related configuration parameters.
4. Verify that each configuration item supports an identified PKC management function.
5. Verify that unnecessary PKC management functions and associated configuration data are not maintained.
- VERDICT:
- SUCCESS:
- All PKC configuration parameters support identified certificate management functions required by the applicable use case.
- No unnecessary PKC management functions or associated configuration data are maintained.
- FAIL:
- Configuration data are maintained for PKC functions not required by the applicable use case.
- Unnecessary PKC management capabilities are present.
- EVIDENCE:
- Use case analysis.
- Configuration documentation.
- Assessment records mapping configuration parameters to PKC functions.
- REFERENCE: ACC-PKI-SBDC-03
- OBJECTIVE:
- Determine whether the product only stores and processes user data required to perform certificate management functions.
- PREPARATION:
- Data flow diagrams.
- Database schemas and storage specifications.
- Descriptions of certificate management operations.
- Identify user data processed by the product.
- ACTIVITIES:
- Review the certificate management workflows.
- Identify all categories of user data collected, stored, processed, and transmitted.
- Verify that each category of user data is necessary to support certificate management functions.
- Verify that unnecessary user information is neither stored nor processed.
- Review logs and temporary storage mechanisms to ensure unnecessary user data are not retained.
- VERDICT:
- SUCCESS:
- All maintained and processed user data are necessary to perform certificate management functions.
- No unnecessary user data are collected, processed, or retained.
- FAIL:
- User data unrelated to certificate management are collected, processed, or retained.
- Excessive or unnecessary data are stored by the product.
- EVIDENCE:
- Data flow diagrams.
- Database schemas (if any).
- Data dictionaries.
- Configuration and logging documentation.
- Assessment records demonstrating data mapping.
- REFERENCE: ACC-PKI-SBDC-04
- REFERENCE: ACC-PKI-DM-04
- OBJECTIVE:
- Determine whether all key generation operations are performed exclusively by approved Secure Cryptographic Devices (SCDs) or remote Key Management Systems (KMSs) implementing cryptographic mechanisms conformant with Annex K.
- PREPARATION:
@@ -2181,69 +2148,19 @@ The validity of the cryptographic mechanisms used to encure those funtions is co
3. Verify that keys are generated only by approved SCDs or remote KMSs.
4. Verify that no software-based key generation mechanism exists outside the SCD or KMS.
5. Verify that the cryptographic mechanisms used by the SCD or KMS conform to Annex K requirements.
- VERDICT:
- SUCCESS:
- All key generation operations are delegated exclusively to approved SCDs or remote KMSs.
- The cryptographic mechanisms employed conform to Annex K requirements.
- FAIL:
- Keys can be generated outside an SCD or KMS.
- The SCD or KMS uses non-approved cryptographic mechanisms.
- EVIDENCE:
- Cryptographic architecture documentation.
- SCD/KMS specifications and certifications.
- Configuration files.
- Assessment records demonstrating key generation paths.
- REFERENCE: ACC-PKI-SBDC-05
- OBJECTIVE:
- Determine whether communications with the SCD or KMS are securely established and whether interfaces are correctly implemented and invoked.
- PREPARATION:
- Obtain interface specifications.
- Obtain communication protocol documentation.
- Obtain configuration information for SCD/KMS connections.
- Obtain error handling and operational procedures.
- ACTIVITIES:
1. Review the communication architecture between the product and the SCD or KMS.
2. Verify that communication channels are authenticated and protected.
3. Verify the use of secure protocols and cryptographic protections.
4. Verify that SCD/KMS interfaces are correctly invoked according to the interface specifications.
5. Verify handling of communication failures and abnormal conditions.
- VERDICT:
- SUCCESS:
- Communications with the SCD or KMS are securely established and maintained.
- Interfaces are implemented and invoked according to their specifications.
- Communication failures are securely handled.
- FAIL:
- Communication channels are not adequately protected.
