A healthcare analytics platform receives automated diagnostic telemetry from remote clinics. To comply with regulatory standards, the platform must verify that incoming data is unaltered during transit and ensure that sending clinics cannot deny originating a record. An engineer proposes applying a keyed-Hash Message Authentication Code (HMAC) using a symmetric key shared exclusively between each clinic and the platform. Which of the following security goals is compromised under this implementation when presenting log evidence to an independent third-party auditor?
- Non-repudiation, because symmetric key shared possession allows either the sender or the recipient to generate valid authentication tags.Answer
- BData integrity, because cryptographic hashing mechanisms only protect against accidental transmission errors rather than intentional tampering.
- CConfidentiality, because computing a message digest exposes plaintext payload data during network transit.
- DMutual authentication, because pre-shared keys are incapable of verifying endpoint identity during connection establishment.
Answer
Non-repudiation is compromised because symmetric key shared possession allows either the sender or the recipient to generate valid authentication tags.
Non-repudiation mandates that a sender cannot deny creating or transmitting a message. Because an HMAC relies on a shared symmetric secret key possessed by both parties, either the sender or the receiver can calculate a valid hash digest. Consequently, an independent third-party auditor cannot determine which party generated the payload, making symmetric HMAC insufficient for non-repudiation. Digital signatures using asymmetric private keys are required for non-repudiation.
Step-by-Step Solution
Key Concept
Distinction between symmetric HMAC (integrity and symmetric authentication) and asymmetric digital signatures (non-repudiation)