5 Cross-Cutting Requirements

The Cross-cutting requirements described in this section are an extension of the cross-cutting requirements defined in the architecture specification document.

5.1 Hardware Security Module Compliance (REQUIRED)

HSM must be compliant to a minimum of FIPS 140-2 Level 3. This guarantees the protection of private keys. HSM/Key Management application shall not print any information about the end-use details. Keys should be created only within the HSM. This may apply to all other Building Blocks when dealing with cryptographic keys.

5.2 Audit (REQUIRED)

All audit logs shall be integrity-protected against tampering. The eSignature Building Block shall follow the data policy and audit logging requirements as laid out in the GovStack architecture.

5.3 Privacy (REQUIRED)

Signing using a single key can compromise the user's privacy in the long run. For example, a single key used to sign the consent of health form and agreement of the medical insurance could reveal that the consent and the agreement are from the same person. Generally available signed documents could be used to perform 360-degree profiling. This violates the Generic Architectural Privacy recommendation. Privacy-preserving techniques can be used in signature schemes, document storage, or reducing the key's lifespan to protect the user's privacy.

5.4 Logging

• The system shall provide traceability across services using trace ID or similar design patterns. (REQUIRED)

• The system shall provide logs to help debug the problems. (REQUIRED)

• The system shall not print sensitive information. (REQUIRED)

  • Private Key

  • User details

  • Authentication Token

  • Payment Token

  • Signature of the document

  • Full Certificate (Thumbprint is allowed to be printed)

  • User PIN

  • OTP

• In case a user/mobile app is involved, then logging shall provide traceability from the app to the server. (REQUIRED)