What is a digital signature in cryptography?

A mathematical scheme where the signer hashes a message and signs that hash with a private key, producing a value any holder of the corresponding public key can verify. Verification proves the message has not changed and the signature was made by the private key's holder — integrity, authentication, and non-repudiation from one construction.

What is the difference between a hash and a signature?

A hash is a fixed-length fingerprint of the message — anyone can compute it, and it proves nothing by itself. A signature is that hash transformed with the signer's private key — only the key holder can produce it, and anyone with the public key can verify it. The hash gives integrity checking; the private-key operation turns it into attributable proof.

Can a digital signature be forged mathematically?

Not by any practical means against modern algorithms and key lengths — forging means solving the underlying hard problem (factoring for RSA, discrete logarithms for ECDSA). Real-world "forgeries" attack the system around the math: stolen or exported private keys, weak identity vetting at certificate issuance, or a genuine signature replayed onto a different document (which the hash check catches).

Does a digital signature need a certificate to work?

The mathematics works without one — a self-signed key pair signs and verifies fine. What the certificate adds is identity: a trusted third party vouching for who holds the key. For documents that travel outside your organization, verification without that vouching proves the key, not the person — which is why production signing uses CA-issued certificates.

Digital Signatures in Cryptography: A US Guide

In cryptography, a digital signature is a mathematical scheme for proving a message's authenticity: the signer computes a hash of the message and signs that hash with their private key, producing a value that anyone holding the corresponding public key can verify. If the message changes by one byte, verification fails; if the signature verifies, only the private key's holder could have produced it. Three properties come out of that construction — integrity, authentication, and non-repudiation — and they are the foundation of everything from certificate-backed document signing to software distribution.

The Mechanism, Step by Step

A digital signature scheme has three operations, and the security of the whole system reduces to their correct implementation:

Key generation — a key pair is created: a private key, kept secret by the signer, and a mathematically linked public key, shared with the world. Modern document signing typically uses RSA or elliptic-curve (ECDSA) pairs.
Signing — the signer hashes the message (SHA-256 is the current standard), then applies the private key to that hash. The output is the signature: a value bound to both the exact message bytes and the private key.
Verification — any verifier recomputes the message hash, applies the public key to the signature, and checks that the two match. A match proves the signature was made by the private key's holder over this exact message.

The hash step is what makes the scheme practical: signing a fixed-length digest instead of an arbitrary-length document keeps the operation fast and the signature compact, while any change to the document produces a different digest and breaks verification. The algorithm-level detail is in Digital Signature Algorithm: How Signing Math Works.

The Three Properties the Construction Buys

Property	What it means	How the math provides it
Integrity	Message unchanged since signing	Hash mismatch on any edit
Authentication	Signer is the key holder	Only the private key signs
Non-repudiation	Signer cannot deny the act	Only they could have signed

The third property comes with a real-world caveat: non-repudiation holds only as strongly as the private key is controlled. A key exported to a shared drive, left on an unlocked machine, or held by a platform with weak access controls signs for whoever touches it — the mathematics cannot tell the difference between the key's owner and the key's possessor. This is why key custody is the security question, not the algorithm choice.

Where the Public Key's Trust Comes From

Verification proves "the holder of the private key signed this" — it says nothing about who that holder is. Binding the public key to a real-world identity is a separate problem, and the standard solution is the certificate: a certificate authority vets an identity and signs a certificate binding that identity to the public key, creating a chain of trust verifiers can follow back to a root they already trust. Without that layer, a digital signature is mathematically valid and evidentially anonymous — the self-signed certificate problem. The certificate layer is in X.509 Digital Certificates: What They Prove, and the infrastructure in PKI Signatures: Certificates, Trust Chains, Verification.

What Cryptography Does Not Prove

The scheme is powerful and its limits are precise:

Not intent — the math cannot show the key holder meant to sign this specific document or saw what they were signing. Intent lives in the signing session's record.
Not authority — the signature proves the key acted, not that the key holder was authorized to act for an organization.
Not timeliness — a signature alone proves nothing about when it was made; a trusted timestamp from an independent authority is what fixes the timeline and keeps signatures verifiable after certificates expire.
Not context — the consent, the presentation, and the circumstances of the act all live outside the cryptography.

This is why document-signing platforms treat the cryptographic layer as one component inside a larger evidentiary system rather than as the system itself. The workflow view is in How Digital Signatures Work in Business Workflows, and the security checklist in Secure Digital Signatures: Certificate and Identity Checks.

Checklist Before You Rely on a Cryptographic Signature

Key custody is controlled: the private key is not exported, shared, or casually accessible.
Identity is bound: a recognized CA has vetted and certified the key's holder.
Timestamp is trusted: an independent TSA stamps the signature at signing time.
Session evidence exists: intent, consent, and authority are logged alongside the math.
Verification is portable: the package — document, signature, chain, timestamp — verifies offline.

Cryptography Enterprises Don't Have to Run: Nota Sign

Nobody on your team should need to understand anything in this article to produce a court-ready signature — that is the actual product Nota Sign sells. The hashing, the key custody, the certificate chains, the timestamping: all of it runs as managed infrastructure behind a signing screen your counsel never has to think about, while the evidentiary layer the math cannot supply — intent, consent, authority, session data — is captured automatically per envelope and exported with the signed document as one offline-verifiable package.

The legal reach matches the technical one. More than 100 countries and regions run in a single envelope flow: ESIGN and UETA cover your US signers, eIDAS (SES, AES, QES) covers European ones, and APAC depth — iAM Smart, Singpass, regional data residency — covers the rest, all on SOC 2 Type II-audited infrastructure with standard electronic signatures and X.509-backed digital signatures available per document class. For documents moving between China and overseas counterparties, one envelope carries both executions — PRC rules on their side, ESIGN on yours — and the chain-bound evidence verifies for each.

Commercially, Nota Sign removes the last excuse for doing this on the cheap: no per-seat fees, so strong cryptography stays open to the whole team instead of being rationed by license count the way per-seat platforms like DocuSign ration it. Small teams start on a low-cost package; mid-market and enterprise buyers negotiate tailored plans sized to document volume and integration patterns. Nota Sign is built by FaDaDa, China's leading e-signature vendor.

If you want to see the full stack — hash, key, chain, timestamp, and session evidence — on one of your documents, contact sales and we will produce it and verify it offline with you.