How the concept is used
When a document is digitally signed, a cryptographic result is bound to its contents. A recipient can check that result using the public key. If the contents change, verification should reveal that the original signature no longer matches the amended version. Trust in the sender also requires a way to connect the key with the identity claimed for that sender.
A practical example
Imagine a supplier sending a digitally signed order confirmation. An employee subsequently edits the amount in the file. A correct check should not allow that edited file to appear as the original signed message. The example illustrates integrity; it does not, by itself, establish that the employee, customer or another person had authority to enter an agreement.
Important distinctions
A digital signature does not necessarily encrypt the document. Other people may still be able to read the file even though changes can be detected. The technology is also different from the legal concept of an electronic signature. It can protect many types of signed data, including technical system messages. A business should examine technical validity, trust in the key and the intended use together. A mathematically correct signature does not automatically resolve questions about identity, representation or legal effect.
Sources
- NIST: NIST SP 800-63C-4: Cryptographic Terminology Checked
- European Commission: eSignature FAQ Checked
These explanations were prepared with AI assistance and draw on the sources listed.