A cloud operations team configures an automated logging mechanism to record high-privilege configuration changes across production servers. The system computes a Hash-based Message Authentication Code (HMAC) for each log entry using a single symmetric key shared among all system administrators. Following an unauthorized system modification, an administrator denies executing the change, claiming that any user with access to the shared key could have forged the log entry. Which of the following security goals failed to be established by this logging design?
- Non-repudiationAnswer
- BIntegrity
- CConfidentiality
- DAuthorization
Answer
Non-repudiation is the security goal that failed to be established because shared symmetric keys cannot uniquely trace an action to a specific individual.
Non-repudiation provides indisputable proof of the origin and integrity of data such that the sender/creator cannot deny having performed the action. When symmetric keys are shared among multiple users (such as in standard HMAC implementations), any holder of the key can generate valid message authentication codes. As a result, individual attribution is lost, preventing the establishment of non-repudiation. Digital signatures utilizing asymmetric cryptography (where each user holds a unique private key) are required to achieve non-repudiation.
Step-by-Step Solution
Key Concept
Non-Repudiation vs Integrity in Cryptographic Controls