the PDF Signing Slide slide howto guidance
- 1. PDF Signing
- 2. What is PDF Signing • PDF includes support for signatures to be embedded in the document itself, rather than managed as separate data or added on to an existing document format. • When a PDF is signed, the signer’s certificate is embedded in the PDF file the relationship between the digital ID stored on the user’s hardware device and the signature value embedded in the PDF document. • The signature value may also include additional information such as a signature graphic, a time stamp, and other data that may be specific to the user, system, or application.
- 3. Digital Signatures in a PDF • Digital signatures are represented in a PDF document and what signature-related features the PDF language supports. Adobe Reader and Acrobat have implemented all of PDF’s features and therefore provide comprehensive support for the authentication of digital data based on public key infrastructure (PKI) technologies. • For these reasons, the PDF language provides mechanisms for two broad categories of tasks: • Fully trusting an electronic document by enabling verification that the signed document has not been altered and that it was signed by someone the recipient trusts. • Creating and controlling feature-rich and secure digital signature workflows.
- 4. Digitally Sign and Secure PDF Documents • Moving from paper-based to electronic document workflows increases productivity and reduces costs, but can also increase the risk of document forgery or tampering. • Organizations need a solution that offers their electronic documents the same assurance of origin and integrity as a wet ink signature provides a physical document. • Using PDF Signing to certify and add approval signatures to the document is the electronic equivalent of adding a notarized, wet ink signature. • A certified document assures the recipient that the document is authentic, comes from a verified source, and has not been tampered with. • Approval signatures expedite an organization's approval procedure by capturing the electronic approvals made by individuals or departments and embedding them within the actual PDF.
- 5. Public key infrastructure in PDF PDF’s digital signature capabilities are designed for compatibility with all the standards associated with mainstream public key infrastructures (PKI) deployed in enterprise and government settings. A PKI is the set of people, policies, procedures, hardware, and software used in creating, distributing, managing, and revoking, and using the digital IDs that contain the public/private key pairs used when signing a PDF. In the context of PDF signature workflows, “PKI” generally refers to the digital ID issuers, users, administrators, and any hardware or software used in those workflows. PDF viewers that implement and conform to the PDF language specification are able to interact with all of these components in a seamless and robust way.
- 6. Representing a Signature in a PDF file • In a PDF, signature information is contained in a signature dictionary. • The entries in these dictionaries determine the nature and features of the signature, and by extension, what data can be available to any PDF viewer designed to process the signature data. • While other viewers may vary in their support of PDF language features, The Acrobat family of products supports all of those features. • At a high level, these features can be grouped into these categories: • Adding a digital signature to a document. • Checking that signature for validity. • Permissions and restrictions that control the signature workflow.
- 7. Requirement Options • The Adobe AATL Certificate Policy requires certificates to be stored on FIPS-compliant hardware, such as a PKI token or Hardware Security Module (HSM). • Token-based - Ideal for individuals and organizations who need to digitally sign a moderate amount of PDF documents (under 5,000/year) or do not use an automated PDF generation solution. • Server-based - Ideal for organizations using automated PDF generation software, such as Adobe LiveCycle, Ascertia DSS, Eldos Secure Black Box, or iText Java/C Sharp, to generate and manage large volumes of documents.
- 8. Adobe Sign
- 9. what is Adobe Sign? • Adobe Sign is a Document Cloud solution that helps your organization delivery end-to-end document experiences with trusted, legal electronic signature. • easily initiate, sign, track, manage, and archive digital documents from web or mobile apps. • complies with many reginal regulations and industry standards and is accessible anywhere on any device.
- 10. Adobe Sign Digital Signature • Adobe sign support e-signature and digital signature. • E-signature are a way to indicate consent or approval on digital document and form are legally valid and enforceable in many industrial nations around the world. • A digital signature, by contrast, is a specific implementation of an e-signature that uses a certificate-based digital ID to verify signer on smart card, USB Tokens, and cloud-based hardware security modules (HSM). It supports open, standards-based signing with digital IDs across desktop, web, and mobile using the Cloud Signature Consortium specification.
- 11. Architecture • Designed to scale and handle large volumes of transactions without performance degradation. • To provide a high level of availability and scalability, all Adobe Sign transactional data is stored in multiple distributed redundant database clusters with automatic failover and recovery.
- 12. Identity Management • Uses a role-based model that handle authentication, authorization, and access control throughout Adobe Sign system. • Defines general user roles for • Sender – Licensed user granted specify permissions by administrator to create document signing workflow and send document for signature, approval, or viewing. • Signer – Verified user provided access by sender to sign a specific document. By default, Adobe Sign sends an email to signer that includes a unique URL to the document to be signed that is comprised of exclusive identifiers that are specific to the transaction. • Approver – Verified user provided access by Sender to approve a document. • Other – Verified user provided specific access by sender to view a document or audit trail.
- 13. User Authentication • Adobe Sign ID – A verified email address and password combination that is use by licensed user to securely log in to an adobe Sign Account. • Adobe ID – An adobe ID may be used to access all licensed Adobe services, including Adobe Sign. Adobe continually monitors all Adobe ID accounts for unusual or anomalous actively mitigate potential security threats. • Google ID – User identification authenticated by Google, such as Gmail or G Suite. • Single sign-on (SSO) - Enterprises seeking a tighter access control mechanism can enable Security Assertion Markup Language (SAML) SSO to manage users through their corporate identity system.
- 14. Document Certification • Maintain a secure checksum of the document to help ensure both document integrity and confidentiality. • Use Public Key infrastructure (PKI) to clarify final signed PDF document with a digital signature before distributing to all participants. • The digital signature is created with a hashing algorithm that takes unique information in final signed PDF to output a fixed-length, cryptographically sound, hex-encoded string of numbers and letters. • Displayed graphically as the blue banner and certification badge at the top of the final signed PDF, the digital signature verifies document integrity and provides assurance that the document has not been tampered with since the certificate was applied. • The final certified PDF can also be further secured with a password as needed. • Use specific certificate issued by trusted Certificate Authorities (Cas) and TimeStamp Authorities (TSAs)
- 15. Security • Employs industry standard security practices for identity management, data confidentiality, and document Integrity to help protect your documents, data, and personal Information. • Network security architecture • External-facing servers • Virtualized cloud networks • Client access
- 16. Comparing Signature Types in Adobe Sign
- 17. Adobe Approved Trust List Members The Adobe Approved Trust List (AATL) is a program that enables millions of people around the world to digitally sign documents in Adobe Document Cloud solutions using the world’s most trusted digital IDs. The certificate authorities (CAs) and trust service providers (TSPs) on this list issue certificate-based digital IDs and timestamp services that are used to comply with the most stringent legal and regulatory requirements in the world, such as the EU electronic identification and trust services for electronic transactions regulation (eIDAS) and the SAFE- BioPharma standard. Adobe digital signature solutions also work with every accredited provider offering qualified trust services listed in the European Union Trust List (EUTL). Get your certificate-based digital ID or timestamp service from one of the providers below, and start signing documents securely with Adobe Acrobat Reader DC, Acrobat DC, or Adobe Sign.
- 23. Comparing Signature Types in Adobe Sign https://www.digicert.com/order/order-1.php