How can an organization verify that its database backups have not been tampered with?

• A. By checking file sizes
• B. By validating backup hashes
• C. By conducting manual reviews
• D. By using third-party software

Answer: (B)

Validating backup hashes is an effective way for an organization to verify that its database backups have not been tampered with. When a backup is created, a hash value is generated based on the data in the backup. This hash acts as a unique fingerprint for that specific set of data.

After the backup is created, the organization can store this hash securely. When they need to verify the integrity of the backup, they can calculate the hash of the backup file again and compare it to the original hash. If the two hash values match, it indicates that the backup has not been altered or corrupted since it was created. This method is highly reliable because even a small change in the data would result in a completely different hash value, signaling to the organization that tampering has occurred.

Other methods, such as checking file sizes or conducting manual reviews, can provide some level of assurance, but they are not as definitive as hash validation. File sizes may be the same even if the contents have changed, and manual reviews are subject to human error. Using third-party software may enhance backup processes but does not inherently address the verification of tampering unless that software specifically incorporates hash validation or similar integrity checks. Therefore, validating backup hashes is the most robust and reliable method