@@ -982,7 +982,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- APPLICABILITY: UC2, UC3, UC4 and UC5.
- REFERENCE: REQ-PKI-INT-03
- REQUIREMENT: The product shall periodically create an audit log signing event in which it computes a digital signature, keyed hash, or authentication code over the entries in the audit log. The digital signature, keyed hash, or authentication code shall be computed over, at least:
- REQUIREMENT: The product shall periodically create an audit log signing event in which it computes a digital signature, keyed hash, or authentication code over the entries in the audit log. For that it shall use state of the art cryptographic mechanisms as defined in Annex K.The digital signature, keyed hash, or authentication code shall be computed over, at least:
- every entry that has been added to the audit log since the previous audit log signing event;
- the digital signature, keyed hash, or authentication code from the previous audit log signed event. The digital signature, keyed hash, or authentication code from the audit log signing event shall be included in the audit log.
- RATIONALE: All entries of the audit log, and the order and exhaustivity of batches of entries should impact authenticity checks of the audit log. The audit record integrity ensure that all auditable events are traceable and misuse of the product functions can be traced.
@@ -991,7 +991,7 @@ This clause addresses the requirements in the CRA [\[i.1\]](#_ref_i.1) Annex 1 P
- REFERENCE: REQ-PKI-INT-04
- REQUIREMENT: The product shall ensure the integrity of audit logs.
- RATIONALE: Integrity protection of audit logs ensures that all auditable events are traceable and that product operations can be reliably tracked for accountability and security monitoring.
- RATIONALE: Integrity protection of audit logs ensures that all auditable events are traceable and that product operations can be reliably tracked for accountability and security monitoring. For that the product shall use state of the art cryptographic mechanisms as defined in Annex K.
- NOTE: Not all integrity protection mechanisms can be foreseen so for use cases with lower regulation of standardization constraints (UC1, UC2) other approaches can be valid and so not identified here. Acceptable mechanisms include: append-only log storage, file-system integrity monitoring, hash-chained log entries, or forwarding to a trusted external log management system. The choice should be proportionate to the risk profile.
