A clinic downloads an installer and the file's hash no longer matches the hash the vendor published. The server is up, and the installer was never a secret. Which security goal failed?
Select an answer to reveal the explanation.
Short Explanation
The box arrived torn open and retaped. You can still see it and the shelf is not empty, but you cannot trust the contents, and that loss of trust is integrity. A hash is not a secrecy stamp, a down server, or a reliability statistic.
Full Explanation
Integrity is the goal that data has not been altered by an unauthorized change. A hash mismatch means the installer the clinic downloaded is not the file the vendor published, so integrity failed. The stem says the server is up and the installer was not a secret, which takes the other two goals off the table. Confidentiality fails when data is disclosed to someone who should not have it. A changed hash does not mean the file was secret or that it was leaked. Availability fails when the service cannot be used. The server is up, so this symptom is not an outage. Mean time between failures is an average runtime between hardware failures. A hash is not that statistic. Exam caveat: a mismatch can also mean a corrupt download rather than an attacker. You still do not install the file until the hash matches a fresh copy. Operational check: download the installer again, recompute the hash, and install only when it matches the vendor's published value. Recompute the hash on a fresh download before anyone installs the file.