uniquely linked to the signatory;
capable of identifying the signatory;
created using means that the signatory can maintain under their sole control; and
linked to the data to which it relates in such a manner that any subsequent change of the data is detectable.
SigningHub implements such signatures using standard PKI cryptography. Each user has a unique PKI signing key and associated digital certificate. The certificate acts as the person’s “digital identity” and is embedded in each signature they create – thereby securely binding the signer’s identity to their signed documents. The signing key which is used to create the signature is private and remains under the sole control of the owner, only accessible after appropriate authentication and authorisation checks.
Within SigningHub a signature consist of two layers. The blue layer is the e-signature appearance, a visible stamp on the document, containing the user’s hand-signature image, company logo and other text. Behind the scene there is cryptographic digital signature created using the unique key of the owner under their sole control (illustrated in green). The digital signature provides all of the security: who signed, when they signed and whether or not the document has changed since signing.
Within SigningHub a signature consist of two layers. The blue layer is the e-signature appearance, a visible stamp on the document, containing the user’s hand-signature image, company logo and other text. Behind the scene there is cryptographic digital signature created using the unique key of the owner under their sole control (illustrated in green). The digital signature provides all of the security: who signed, when they signed and whether or not the document has changed since signing.
For signed PDF documents you can easily determine if an AES was used by opening the document in Adobe® Reader as shown below. You can see who signed from the blue bar, or by simply clicking on the e-signature appearance to see the pop-up details highlighted below. You should see the name of the real person who created this signature if AES are being used, if instead you see the service provider’s name here then only basic e-signatures are being used and not AES!
SigningHub can obtain Adobe-approved AATL certificates automatically in real-time from our partner CAs in the remote signing use case
Set-up your own enterprise-branded CAs inside SigningHub to issue certificates to your users
Use any CA within your organisation, industry or country e.g. your national eID CAs