A cloud compliance team is configuring an automated log aggregation vault to collect audit trails from independent third-party SaaS vendors. The organization mandates two primary security requirements for all ingested logs: first, the vault must be able to prove that a log file was not modified after creation; second, the log file must provide non-repudiation, ensuring that an untrusted vault administrator who possesses read access cannot forge a valid log entry on behalf of any vendor. Which of the following cryptographic techniques should each vendor apply to the log files prior to transmission to meet all audit requirements?
- ACompute a SHA-256 cryptographic hash digest of the log file and append the resulting hash to the header of the log prior to transmission.
- Sign the log file using the vendor's private key to generate an asymmetric digital signature appended to the payload.Answer
- CGenerate a Hash-based Message Authentication Code (HMAC-SHA256) tag using a pre-shared secret key shared between the vendor and the vault administrator.
- DEncrypt the log file using the central vault's public RSA key prior to sending the payload over the network.
Answer
The correct technique is signing the log file using the vendor's private key to generate an asymmetric digital signature.
Generating an asymmetric digital signature by hashing the log file and encrypting the hash digest with the vendor's private key guarantees both integrity and non-repudiation. Anyone can verify the signature using the vendor's public key, but no one—including the untrusted vault administrator—can forge a valid signature without access to the vendor's private key.
Step-by-Step Solution
Key Concept
Digital Signatures and Non-Repudiation