A production team wants to distribute proprietary files among stakeholders so the sender cannot disclaim authorship. Which approach is BEST at verifying accountability?
Attaching a cryptographic signature to each file
A process that retains server logs of distribution timestamps
Attaching a cryptographic signature to each file creates a secure, verifiable binding between the content and its origin. Password protection or archived files may offer confidentiality but do not affirm the exact sender. Logs with timestamps or verbal confirmations similarly lack tamper-resistant proof of who authored and transmitted the documents. Cryptographic signatures preserve a traceable, validated link to the sender, supporting the goal of preventing disclaimers.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a cryptographic signature?
Open an interactive chat with Bash
How does a cryptographic signature prevent tampering?
Open an interactive chat with Bash
What are the limitations of other methods like server logs or password protection in verifying accountability?