Establishing Digital Trust at Scale: Identity Verification and Security with Acrobat Sign

Transcript

Good morning and good evening everyone. Welcome to this Adobe webinar. We’re very excited to have you all here today. We see you’ve coming into the audience, which is great. Today we’re here to talk about establishing digital trusted scale, identity verification, and security with Adobe Acrobat Sign.

If we could go to the next slide, please.

Great. Let’s introduce you to who you’ll be talking to today. On the right, my name is Dave Stromfeld. I am a Principal Product Manager on Acrobat Sign. I’ve been at Adobe for over 20 years and I manage a breadth of areas with Acrobat Sign. Today I’ll be your moderator. With me today is our Principal Speaker who’s Andrea Valle. Andrea, you want to introduce yourself? Yeah. Thanks, David. Hi, everyone. I’m Andrea Valle, Principal Product Manager. I lead all the digital identity, security for Adobe Acrobat Sign.

Fantastic. Then there are some additional Adobe folks who are going to be managing the Q&A pod and helping us answer questions. You’ll see their names over in the Q&A pod. Speaking of the Q&A pod, Andrea, if you want to go to the next slide.

Let’s talk about the agenda first. The agenda really quickly today is we’re going to give you a very quick overview of Sign’s product vision and strategy, and how identity and trust and digital signatures play into that strategy. Then we’ll be spending the bulk of our time on three topics. Number 1, trusted digital signatures, and how trusted digital signatures give you the benefits of integrity, non-repudiation, and long-term validity. We’re going to be talking about global digital identity and how you can use that to verify and allow your signers to authenticate. Then we’re going to be talking about high assurance regulation, ready signing, and all the industry standards and new regulations that play into that. Then we’ll be leaving time at the end for questions and answers.

Great. Speaking of the Q&A pod and some housekeeping and how you’ll be interacting with us during this webinar. Number 1, as I mentioned, their Q&A pod is open. You can access that through the icon in the top of your toolbar, and then you can go ahead and ask questions, and you can upvote questions.

As you upvote questions, then that will help us know which questions are the most popular. Then during the course of the webinar, there’ll be some people that will be answering those questions, and then we’ll be leaving time at the end to answer any questions live that we didn’t get a chance to answer through the Q&A pod. We highly encourage you to use that Q&A pod during the webinar, ask all your questions, and folks will be answering those, and then we’ll try to get to as many of those as we can. Secondly, we’ll be doing polling.

During the course of the webinar, we’ll be bringing up polls to get your reactions to different parts of the webinar. In the spirit of that, Andrea, why don’t you go to the next slide? Let me go ahead and launch our first poll, which is, where are you joining us from? Hopefully, now everyone can see a poll on their screen. If you guys can all just go ahead and make a selection, this gives us a great opportunity to understand where you guys are all and I see results coming in for that, which is great.

Looks like a lot in North America, a lot in Europe, some folks from Africa, from Asia, from all over the place. Wonderful to have you all with us today.

I will go ahead and when you’re done taking that poll, you can just obviously click the X and dismiss it.

Now, I think we can go to the next slide, Andrea.

I will hand it off to you, Andrea, to take it from here.

Yeah. Thank you, David.

And hi again, everyone. Thanks for joining. Today, we will start talking about a few topics that you can also see in this picture. This picture is more about all the capabilities that Acrobat Sign has. Acrobat Sign, for those who are not familiar with all the features, holds the capability to create agreements and automate workflow around that, and also allow multiple users to sign in filling forms and do a lot of other things.

But today, we are going to focus in particular on these topics, which are essentially the clear core of e-signature. So, trustworthiness of e-signature and how to get confidence in our document, how we route those documents and essentially get compliance done and how we get a secure result. So, as part of this presentation, as you have seen in the agenda, we have three sections. And the first section I’m going to start is focusing on one key principle. So, e-signature legality is a complex matter. So, it’s easy to get confused. It’s easy to use simple terms that are essentially very generic.

But in effect, when we talk about electronic signature, not all the signatures are equal.

And in particular, today we will cover some aspects of the signature, which is technology, which is functional capabilities, but also legality and compliance.

So, we will answer these three questions that you see on screen.

So, first of all, it’s important to understand that depending on your use case and also your regulatory framework, you don’t have just one type of e-signature. You can have a basic signature. You can have a signature with an identity verified, and you can have digital signature, where cryptography plays an important role. And as you will see, the stronger the signature assurance becomes, and also it carries additional effort, additional cost, but also additional trust. So, one important point to highlight for Acrobat Sign is the fact that we support all this type of signature, because not all the signatures are good for every use case, for every requirement. So, it’s not good to use a very secure signature with a high cost, with high user friction, if you have a simple task to achieve. Maybe for an internal approval, you don’t need to meet any compliance requirement. On the contrary, when you need to meet this compliance requirement, you cannot just use a basic signature, because, for example, they may be refused in court, or you may not need a specific requirement. So, if you submit, for example, a document for a tender, this may be rejected and you lose a business opportunity. So, in particular, Acrobat Sign offers different types of user identification and authentication. So, you will hear a lot about these terms, because these are the characteristics that make this different type of signature basic, or verified, or digital signature. So, on the left side, you can see that essentially a basic signature can be as simple as using just an email address as a way to identify the signature, or a second factor of authentication, like an email, OTP, or phone authentication, or password to obtain a stronger level of authentication. But still, there’s no identity verified. So, identification or identity verification is definitely something more. It’s something that says, hey, when Andrea signs, you can be sure that it’s me and not someone else who tries to impersonate me or someone who is just stealing my identity. And of course, this identification can be done in different methods. So, Acrobat Sign has been built with a very flexible architecture. You will see in a moment the different kind of solution that we support, and you will see that we can have different capabilities that meet not only functional requirements, but also the level of assurance of the identity of the user. At the right side, you see digital signatures, which are based on digital certificates, which contain verified identity information issued by a trusted service provider. So, in this case, we have the previous level of verified identity combined with cryptography that makes this identity unbreakable. And essentially, when a digital signature is applied, you cannot forge it in any way. In the right bottom box, you can also see some logos that may be familiar to you. These are the trusted service providers that we will talk about a lot in a moment, which are those that issue this digital certificate and provide identity verification when you’re using digital signatures. So, in Acrobat Sign, we support two different options for digital signatures.

So, the first one is what we call cloud signature, which are digital signatures where the certificate is hosted as a service by a trusted service provider. So, the user has the flexibility to not have to configure or connect a physical device to a computer because the certificate is issued and hosted as a service. This is great, for example, for mobile users because they normally don’t have even a way to plug into a physical device. But still, a lot of legacy devices like smart cards or USB stick exist. And that’s why we also offer an option that we can consider more a legacy capability to sign with the code and sign with Acrobat. So, in this case, we can leverage the capability of Adobe Acrobat to support this legacy of physical devices hosting the certificate, holding the certificate. And therefore, sign allows, in this case, the user to maintain the capability to sign with their existing certificates. So, now let me move to deep dive a little bit on the cloud signature concept.

So, as I say, the cloud signatures are essentially digital signatures where the signer’s certificate is stored remotely in the cloud. In fact, an alternative name for cloud signature is remote electronic signature. So, this is something which Adobe has invested a lot and also one of the first providers to implement this kind of solution. Even before Acrobat Sign was born, Acrobat desktop had this capability to connect to external services for doing digital signature.

In Acrobat Sign, the cloud signature solution has been facilitated by the standardization that has been achieved through the cloud signature consortium. So, you may have seen the small logo you see in the center of the screen. This is an industry consortium that Adobe has contributed to fund 10 years ago, which has given us the possibility to define a standardized integration layer to connect to the high number of certificate providers you have seen in the previous screen. So, let’s now see how the cloud signature experience works. Well, first of all, in Acrobat Sign, we have close to 60 different service providers available. And on the left side, you can see the typical administrator user interface where the administrator can define which certificate providers should be enabled and available for their users. After this configuration is done, the signer can create an agreement or import document and place fields. In this case, digital signature fields will be the placeholder to allow signer to click on the field and start the digital signature experience. Now, that is what the signer will do when receiving a document for signing. The user clicks on this field on screen and will select the provider of their choice or the provider that the sender has specified to be a possible choice for them during the signature. This is important because not all the TSP providers provide the same kind of solution. As I said before, different providers can provide different certificates with different identity verification and also with different compliance. For example, in Europe or in other countries, there is this concept of qualified electronic signatures where the qualified is determined by specific characteristics of the certificate that only certain certified providers can provide.

I will not spend too much on this feature, but you can see also a link to the help guide at the bottom of the screen that you can look at. I just want to conclude this section with a couple of news that we have recently added for those who are already familiar with digital signature capabilities in Acrobat Sign. First of all, in the last release, we have added the ability to enforce digital signature at recipient level. This means that while previously a digital signature could just be triggered by adding a digital signature field, now the sender can select this checkbox in the recipient settings which will enforce the presence of a digital signature field in the document. This way, if a digital signature is requested, the sender can enforce that the document will always have a digital signature field.

This feature also works with identity check which enforces the identity of the signer with the capability to match the email contained in the digital certificate or the name of the signer itself. We will see more about this in the next section.

And also, this is another enhancement that is very useful, especially for recurring signers who may have to just use the same certificate every time. Instead of going through repeating the activity to select their certificate and authenticate with their provider, they can set the certificate they are using as default. This will essentially allow the user to skip this repeated authentication and selection activity every time. Very useful for recurring users.

Last slide for this section is to also speak about electronic seals.

Electronic seals are more a legal definition, more than a technical definition because they rely on the same technology for digital signatures. But the concept of seal is essentially more or less the equivalent of a legal entity applying a signature rather than a natural person, so an individual person. So, Acrobat Sign supports the ability to apply electronic seal in an automated way which allows also to streamline processes where a business document needs to be signed by the company, not by an individual. And we have again capabilities for the administrators to define a seal and also to define the appearance of the seal in the document and also to allow the sender to define where to place the seal in the document but also at which level of the signing workflow. It can be at the beginning, it can be at the end of the workflow or anytime in the middle. And of course, the audit report will also provide information on the seal with specific verbiage in the audit report.

Okay, now I’m finished with the first section, so I’m heading back to David for a quick poll.

Great, thank you Andrea. Let me bring up our first poll in the conclusion of Andrea’s section. And while I bring that up, there was a great question asked that I forgot to remind people at the beginning of the webinar which is yes, you will get a copy of the recording, we will email that to you. You will also in that email get links to some of the key URLs, websites that Andrea is sharing during his presentation. So no need to take screenshots or notes, you will get all this in a follow-up email. I apologize for not mentioning that earlier.

But in the meantime, let me bring up our second polling question here.

Let me find it, there we go. And this is a three-parter, it should show up on your screen now, which is basically what types of electronic signatures are you using today in Acrobat Sign? And then if you are using digital signatures, a couple of questions about how you are using digital signatures. So you can see the next arrow down at the bottom of the poll, you can answer those three questions. We will give everyone a few seconds to answer those.

I’m seeing results come in.

A good breath of usage of both Simple E signatures and digital signatures.

Some good usage of cloud-based digital signatures. So this is really great feedback from all of you. So thank you for sharing this. So great, you can go ahead and close that poll when you are done. And Andrea, let’s go on to the next section. We are doing great on time, we are right on time. So let’s move on to the next section, Andrea.

Great, thank you. So the next section focuses a lot on digital identity. As you have seen, digital identity is also important for digital signature, but we also support in Acrobat Sign digital identity combined with simple signature. And the reason for that, as I said, is that digital signatures carry also additional complexity and additional friction for the user because of the presence of cryptography and digital certificate. So Acrobat Sign offers the flexibility to use different methods for authenticating your recipient using alternative methods than digital signatures. In fact, as we have seen in the initial slides, we support just a simple signature with email address, which of course carries a very weak level of identity verification. But we have other systems that add both authentication and identity verification. So for example, password can be a shared password that allows the sender and the signer to just have the same password shared, which will allow the user to enter the password. And if the password is correct, then the user is authenticated. But we have the ability to have real identity verification, which use third party services for ensuring a real verification of the identity. For example, knowledge base authentication is very popular in the US or government ID verification, which is using photo ID documents with biometric check to match a live selfie with a picture. All these solutions are perfect to identify users who are maybe new to a platform like Acrobat Sign as external signers and have no footprint for their identity in the system. You will see later that we have a solution called the Digital Identity Gateway, which is our newest solution for identity verification. But now I just wanted to show you something that we have recently added to our platform, which is WhatsApp authentication. So WhatsApp authentication is very similar to phone authentication. But while phone authentication relies on SMS messages, WhatsApp authentication still relies on phone numbers.

The sender has to enter a phone number. But instead of receiving an SMS, the user will receive a WhatsApp message containing a one-time password. So as you can see in the first screen, when WhatsApp authentication is configured for the user, then the signer will receive this message informing how the authentication will be performed. And when they click on send code, they will receive on their mobile phone or other device with WhatsApp installed, this message from Adobe Acrobat Sign carrying the one-time password. And then in the next screen, they will enter the screen and click on the verify button. And if the code is correct, the user will be authenticated. So very straightforward and especially very good in certain jurisdictions where SMS are subject to blocks or restrictions for security reasons and WhatsApp is very popular, very familiar. Okay, now let’s move to this important topic, which is the Digital Identity Gateway.

So the Identity Gateway is an integration technology that we have created to have a high assurance of basic electronic signature with verified identities. And that’s also why in our terminology, we define the signature created through the Digital Identity Gateway providers verified signature because it’s an e-signature with a verified identity.

This Digital Identity Gateway is an integration technology based on a very popular standard called OpenID Connect, which allows Adobe Acrobat Sign to define an ecosystem of third-party providers that by supporting the OpenID Connect can be easily integrated into our platform and increase this number of providers that you see on screen.

The other interesting thing is that we also support private identity providers using OpenID Connect, but allowing enterprise customers to integrate their own identity and access management service to authenticate in terms of the users. This is very interesting, so please follow up with me if you are interested into this topic.

So let’s see again how the user experience works for the different personas supported in Acrobat Sign. So first of all, the administrator needs to configure the identity providers available under the Digital Identity Gateway that they wanted to offer to their users. So all these services are optional services, so they are not enabled out of the box. If you want to offer any of these services, you have essentially to buy a license from the provider, which will provide you the configuration data that you need to enter in this screen. So for example, if you want to configure Bank ID in Sweden, then you have to procure the license, and then you click on this icon, you will enter the configuration, and then the service will be immediately available to your senders. And for senders, when a service is enabled, you will see in the dropdown for each recipient, as much as you can do already with phone authentication, password, GovID, and so on. So whenever one of the identity providers will be enabled, a new section at the end of the dropdown will be available, and senders can just select to apply this authentication method to the signer. And of course, for the signers, they will see a similar screen to what we have seen before for WhatsApp, but just informing them that they will have to authenticate using this identity provider selected by the sender. And when they click, they will have this user experience that’s specific for the service they are using.

Okay, now let’s talk about identity check. I’ve mentioned it before, this is a very, very important characteristic. So sometimes when you send an agreement to someone for signing, you don’t just want this user to be authenticated, you want a specific user to be authenticated. So for example, if you send, let’s say, an insurance contract, to a family email address, the notification can be received by the husband or by the wife or another member of the family. So this document may accidentally be signed by the wrong person, just because this person is also able to complete the authentication required by the agreement. But of course, from a business point of view, this signature would not meet the business requirement to be signed by the exact person. So in that case, identity check allows the sender to enforce some of the attributes of the identity of the user, such that only the right user who has the right name or the right email or other attributes will match the intended values set by the signer. So for example, if someone is sending me an agreement to sign and expecting to be signed by Andrea Valle, then they can set name matching to Andrea Valle, such that only if I authenticate with an identity provider that proves I am Andrea Valle, the matching will occur and the signature will be valid. If that’s not the case, then the agreement will be refused. So very important for compliance requirement.

Another characteristic that can be enabled by the Digital Identity Gateway is verify the form fields. So as you know, Acrobat Sign allows to create forms with interactive fields.

So the typical phase is to either import a document containing fields or creating fields using the authoring capabilities. But often these forms require user to enter data that, well, it’s repeated and annoying people because they have to enter data. Sometimes they go fast and they may type wrong and make mistakes that can be critical for sending those agreements. So verified forms allows to automatically pre-fill form fields with verified data coming from the identity provider upon a successful identification. So the way it works is that by designing the form fields, you can use naming conventions such that the value of these fields will automatically be bound to the response from the identity provider when the user authenticates. So for example, if I’m authenticating with ID NOW and ID NOW returns a birthdate, then the birthdate field can be automatically pre-filled with my birthdate coming as verified data from the identity provider instead of having to type this value and maybe type a wrong value. This is also important because the fields can also be read-only and in that case the user did not have a chance to modify the data. And in this case, the information will really be verified because the identity provider is a trusted source for identity information. Okay. Now it’s time again for a new poll to complete this section. David, back to you. Great. Thank you, Andrea. We are doing great on time, right on schedule. Also, again, I’ll remind people the Q&A pod is open. We’ve gotten some great questions in there. But if you have questions about anything you’re hearing or Acrobat Sign in general, please go ahead and use that Q&A pod. Let me go ahead and bring up our next polling question here. There we go. And this is, again, per what Andrea just presented, we’d love to get your feedback on what solutions you are currently using to authenticate your recipients. So go ahead and check the options that are currently being used by you and your organization.

I’m seeing results come in. Digital Signatures is quite high. Adobe Sign Authentication is quite high.

Some good usage of phone authentication. Digital Identity Gateway. Great. Really good information.

So go ahead and make your selections. Dismiss it when you’re done. And Andrea, I think we can move on to the next section.

Okay, great. Thank you, David. And thank you, everyone, for answering these polls. So the last section is about signature assurance and regulation impact. So we have already considered some of the rationale for using digital identity or trusted services beyond basic e-signature. But here you can see, in fact, the three key reasons for that. From customer conversation, we found that the reason they are using digital identity and trusted services beyond the basic signature fall in three main categories. First of all, legal outcomes. So this is when a customer needs to comply with country specific regulation or e-signature type. For example, EIDAS in the European Union or, I don’t know, ICP Brazil in Brazil. But other regions and country have their own version of this regulation. The second point is compliance outcome. This is when a customer needs to meet industry specific compliance requirement. Think of CFR Part 11 in the US for pharmaceutical and life science companies, or also in the EU, of course. Or in financial services, the know your customer or anti money laundering requirements. So Archimed Sign is able to meet those requirements. And this is very important to understand. Last but not least, and this is very generic, risk management and fraud reduction. So digital transformation has unfortunately brought a lot of digital frauds. And it’s important that by maintaining e-signature workflow, you don’t offer essentially an option to fraudster to impact your business. So any time the risk of fraud for an agreement is there and adding an additional layer of identity verification adds security protection from fraudsters.

As I say, the e-signature legality is not just a single piece of law or regulation. So globally, there are rules and regulations defining the legal validity of electronic signature.

And typically they are not even very similar. So in the world that we have typically two different categories of legal systems, the permissive and minimalist laws like in the common law countries. And the more prescriptive regulatory systems in those in the civil law, Roman law.

So to help organizations understand international legal consideration in impacts of signature legality, we have created some public guides that you can see referenced here in these links, which provide at country level the key information about the main signature regulation and how they have impact on your e-signature workflow. So it’s very, very important to have a look at these pages and understand the impact on your signing workflow. Of course, we will never say, oh, you need a qualified signature, you need an advanced signature or simple signature because we don’t provide the legal advice. But it’s important to understand the legal requirements and refer to your lawyers, to your legal counsel for getting the right determination on which solution you need for your business.

So far, we have talked a lot about creating electronic signature because it’s easy to just focus on, OK, we need to create those signature. But in reality, verification is often more important than creation. And the reason for that is that the value of a digital signature will appear later during an audit, during a dispute or a regulatory review. When someone will need to answer three basic questions, who signed, has the document changed and can I trust the issuer of that signature? So the certificate, the presence of a certificate, for example, may not be enough if the issuer of this certificate, the certificate authority, is not trustworthy. And of course, we need to have this determination available even to the lay person. It should not be an expert determination. So that’s why essentially a reliable source of trust is an essential characteristic of electronic signature. So that’s why essentially you may have heard about the Adobe Approved Trust List or AATL. That’s essentially a trust program aimed at creating exactly the conditions to make e-signature trusted. It’s a global trust program that allows Acrobat and Acrobat Reader to verify whether a digital signature or an electronic seal is baked by a recognized, audited and trusted service provider. So when a certificate comes from an AATL member, Acrobat can automatically validate the signature for individuals signing documents or organization applying electronic seals without any custom configuration or prior relationship. In short, trusted digital signatures don’t scale without trusted source of trust and the AATL provides exactly this foundation, ensuring signature remains valid and defensible. For you, what that means? Well, essentially that when you are procuring certificates for your digital signature, look at those providing certificates under the AATL program, because they will ensure that your relying party will always see the green check.

That means your certificate are trustworthy.

In addition to the AATL, we have a special support for the European Union digital certificates. And the reason for that is very historical, but also due to the fact that in the European Union, the use of digital signature is very widespread. Over the years, certificate authorities have established in all the European Union countries, but only recently, let’s say 10 years ago, the European Commission has created this concept of EU trusted list.

Nowadays, the European Union trusted list contains about 1700 certificates.

That’s not individual certificates. That’s the number of certificates of all the different certificate authorities available in Europe. So it’s a massive number. And of course, you cannot expect to just maintain a list of the certificates on your own. And that’s why Adobe Acrobat supports the European trust list out of the box, such that you can essentially just simply ignore the problem of maintaining this huge list of certificates, because Acrobat does that for you. So what happens behind the scenes is when you have a qualified electronic signature or QES, Acrobat signing will automatically validate it and show this little trust mark. That’s essentially the symbol of EU qualified services and will essentially provide information that this is a qualified electronic signature according to the EIS regulation. So very important if you need to prove compliance and make sure that the signature that you create are trustworthy. So let’s now switch to the evolution of this EIDAS regulation that applies to the European Union. So the EIDAS regulation has been updated in 2024 and starting this year is now entering into force. So it’s very, very current topic. So what is EIDAS 2, the way it’s this update of the EIDAS regulation is commonly called? So it establishes a pan-European digital identity framework with some important news that were not existing in the previous version of EIDAS. In particular, the concept of European digital identity supported by the concept of identity wallets.

So identity wallets, similarly to the payment wallets that you’re familiar with, are essentially mobile app that allow to support digital identity in your pocket. So instead of using additional mobile application provided by single providers, the UDI wallet will be issued by the member states in the European Union as free government applications that will allow users to get not only digital identity, but also additional elements like attribute attestation. And this will allow to support this three key functionality. First of all, authentication. So instead of using, for example, phone authentication, users will be able to just prove their identity and authenticate it to websites or authenticated for an e-signature. And the second is the ability to store in the wallet the digital equivalent of identity documents like driver’s license or educational diplomas or medical prescription or vaccination certificates, whatever. The third key characteristics, given the support of identity is critical for signature, is exactly the ability to create legally binding electronic signatures with the wallet. And that’s exactly what we are going to focus on. So the key impact of the U digital identity wallet will also be the ability to support the signing workflows with digital identity hosted on the identity wallet. The EIDAS 2 regulation also introduces an interesting thing, which is free QES for individual citizens. This is still a work in progress in terms to understand what free means. But essentially it means that if an individual wants to sign a document for another individual, they can get a certificate, qualified certificate for signature in the wallet for free.

In addition, as I said, the attribute attestation is another important factor because it will add the trusted metadata in addition to the signature. So for example, it will allow to say, okay, I am not only an individual with a name as a name, but I am also a trusted CEO of the company. So I carry some power of attorney. So very, very important. And of course, some use cases will be absolutely taking advantage of this technology by essentially using the UDI wallet for cross border interactions or financial services, healthcare and government services.

Okay. Thank you very much. So I think I’ve also finished this section. So I’m going to have to go over to David for the last poll.

Great. Thank you, Andrea. I’m launching our last poll right now. If everyone could answer, this is a two parter. There’s a next button in the lower right.

So if everyone could go ahead and fill that in now.

And I’m seeing some answers come in. Mostly domestic, but a good mix of people using e-signatures across global markets.

And then some good feedback on which regulatory frameworks are you most interested in. So great. That’s really helpful. Go ahead and everyone can answer that and then dismiss that. Andrea, you want to go ahead and flip to the next slide, please? So we’re nearing the end of our webinar. Here’s our survey. So if folks can please go ahead and scan that QR code. I’m going to paste it in one moment into the Q&A area as well. We’d love to get your feedback on what you liked in this webinar, what you would like to see more of. We also have an opportunity for you to tell us what future webinars would you like to see from Acrobat Sign. So please, everyone, go ahead and fill out that survey and I’ll put the link in the Q&A pod right now as well.

And if we flip to the next slide, Andrea. Let’s go ahead and answer some questions. We’ve got about five minutes left. We’ve had a team that’s been busy, busy answering your questions in the Q&A pod. I don’t see any questions that did not get an answer in the Q&A pod. If you have any last questions, please enter them in the Q&A pod now. But Andrea, let me ask you a couple of things that came up. So first of all, kind of an easy basic question. But, you know, if you could cover again sort of what is the basic differences between digital signature and electronic signature? If I’m explaining to my team or my leadership in my company why we might want to move to a digital signature over a basic electronic signature, what’s a good sort of, you know, one minute response that I could give to my broader team at my company, Andrea? Sure. Yeah. Well, first of all, on the name, electronic signature is also used as the generic term. So when we say electronic signature, we mean any kind of the various options I mentioned. So basic, verified or digital signature. When we’re talking about digital signature, we are definitely talking about the highest level of signature assurance. So for both anti-tempering, identity proofing and compliance, you have definitely the highest level peace of mind for legality, compliance and security. So that if these terms are critical for you, definitely digital signature are your must have choice.

Great. Thank you. And Andrea, maybe could you also remind us again from a jurisdiction perspective, what jurisdictions are moving to digital signatures right now? Well, typically digital signature are the mandated or recommended signature in the prescriptive legal systems I mentioned before. So typically in the US, Canada, all the Commonwealth countries, which are essentially common law driven, they are less prescriptive. So digital signature may not be very popular. If not, due driven to essentially compliance or high risk requirements. So definitely digital signature are moving much faster in countries like Europe, Latin America, Southeast Asia and Africa. So yeah, pretty, pretty popular everywhere, but less in countries like the United States or the UK or other Australia and so on. For example, in the US, digital signature are the absolute standard in the federal space, for example, because the level of security and risk and assurance is very high. So in fact, Acrobat has been adopted in the federal space for ages now. Great. Thank you so much. And a good question from Carla came in. She in particular said that her organization is interested in complying with QES requirements in EU countries, in the Ukraine, in Egypt. How would you recommend a customer get started when they’re looking at how to comply with QES requirements in particular jurisdictions or countries? Yeah, as I said, first of all, look at our e-signature legality pages, because the concept of qualified signature is not absolutely the same, even if the term that is being used is the same. EU qualified signature are completely different from Egyptian or Ukrainian qualified signature. So first look at the legality page. You will also find information about which type of providers may support this solution. And also have a look at our page regarding digital signature, because you will find also important information about which providers support which kind of signature, which kind of certificate in different countries. And that’s also the reason why we have such a broad ecosystem of providers, because not all the providers can provide the same solution that meets your compliance requirements.

Great. Thank you so much. Well, we are at the top of the hour. I think we’re ready to wrap this up. I just wanted to thank everyone for attending. Again, Andre, if you wouldn’t mind, would you flip back to the survey slide if folks didn’t get a chance to scan that? I also put the URL in the Q&A pod. So if folks could please fill out the survey through the QR code or through the link in the chat pod, we’d love it. We look forward to hearing your ideas about the next webinars you’d like to see, and we will see you at the next one. Thank you, everyone, so much for joining, and have a great day.

Thank you, David.