In the context of secure releases, what is the purpose of tamper-evident logs?

• A. To attract user data storage.
• B. To detect unauthorized changes to release artifacts and records.
• C. To increase UI performance.
• D. To encrypt all data.

Answer: (B)

Tamper-evident logs are built to preserve the integrity and traceability of release activities. In secure releases, every step—building artifacts, signing, packaging, and deploying—produces records that are protected so that any change becomes detectable. They use mechanisms like cryptographic hashes, chain hashing, and signatures to ensure that once a log entry or artifact record is created, tampering will be evident. This lets teams quickly spot unauthorized modifications to release artifacts and their records, supporting trust, accountability, and forensic investigation in the software supply chain. That’s why the purpose is to detect unauthorized changes to release artifacts and records. The other options don’t fit this role: attracting user data storage isn’t about integrity; improving UI performance isn’t related to security logs; and encrypting all data is a confidentiality measure, not the primary aim of tamper-evident logging.