Sign in and find your way around SignDex Read the article

Understanding AATL and Trusted Digital Signatures

What Is AATL?

The Adobe Approved Trust List (AATL) is a program run by Adobe that lists Certificate Authorities (CAs) and Trust Service Providers whose root certificates Adobe trusts for signing PDF documents.

Providers on the list must meet Adobe’s technical and policy requirements before their certificates are accepted. Adobe Acrobat and Acrobat Reader then download the list automatically, so every user benefits without any setup.

When a PDF is signed with a certificate that chains back to an AATL-listed provider, Acrobat and Reader recognise it as trusted out of the box.

Adobe Approved Trust List (AATL)

How AATL trust works · from Adobe’s list to a trusted signature

Acrobat follows the chain from the signer’s certificate up to its CA root. If that root is on Adobe’s list, the signature shows as trusted.

In short: AATL tells Adobe software whether the certificate behind a digital signature comes from a provider it can trust.

Without AATL, recipients may need to manually import and trust a certificate before the signature shows as valid. Most external recipients will not know how to do this, and should not have to.

Why Certificate Trust Matters

A digital signature is more than an image placed on a page. When a signed PDF is opened, the reader software checks:

  • whether the document was changed after signing
  • whether the signing certificate is valid and not revoked
  • whether the certificate chain leads to a trusted root
  • whether the signer details match the certificate
  • whether timestamps and validation data are present

 

aatl-image4

 

If the certificate chain does not lead to a root the reader trusts, Acrobat may show messages such as:

  • “Signature validity is unknown”
  • “Signer’s identity is unknown”
  • “At least one signature has problems”

These warnings do not necessarily mean the document was altered or the signature is invalid. Often, they simply mean the reader does not trust the certificate’s issuer by default.

For businesses, though, the effect is the same: confused recipients, support queries, delayed approvals and extra verification work.

What Recipients See with an AATL-Backed Signature

With an AATL-backed signature, the recipient simply opens the PDF. There is nothing to install or configure.

 

aatl-image1

 

Acrobat or Reader recognises the certificate chain and shows a clear signature status, including:

  • who signed the document
  • which provider issued the certificate
  • whether the certificate was valid at the time of signing
  • whether the document has changed since it was signed
  • when it was signed, if a trusted timestamp is included

For external recipients, this is the difference between a warning that raises doubts and a status that builds confidence.

AATL Is Not the Same as Legal Compliance

AATL is a technical trust program, not a legal or regulatory licence. It controls whether Adobe products recognise a certificate. It does not, on its own, decide whether a signature meets the requirements of a particular law.

Whether a signature is legally accepted can depend on the jurisdiction, the type of document, how the signer’s identity was verified, which certificate provider was used, and the applicable regulations.

AATL Legal / regulatory framework
Purpose Certificate trust inside Adobe software Legal recognition of the signature
What it governs Which certificate chains Acrobat and Reader trust Requirements for certificates, identity and providers
Who manages it Adobe Governments and regulators
Main benefit A smoother verification experience for recipients Legal and compliance assurance

The two complement each other. But they should not be treated as the same thing.

AATL and Long-Term Validation (LTV) Solve Different Problems

AATL is also often confused with long-term validation (LTV).

  • AATL answers: Does Adobe trust the certificate today?
  • LTV answers: Can this signature still be verified years from now?

Certificates expire, and the online services used to check them may not exist in ten years. Long-term validation (LTV) solves this by embedding the evidence needed to verify the signature, such as certificate chains, revocation data and timestamps, inside the PDF itself.

For documents that must be kept for many years, standards such as PAdES B-LT and PAdES B-LTA define how this evidence is preserved. PAdES B-LTA adds archive timestamps that can be renewed over time, keeping the signature verifiable for the full retention period.

A strong signing setup needs both: a trusted certificate today, and verifiable evidence for tomorrow.

When Should Businesses Use AATL-Backed Signing?

AATL-backed signing is most valuable when signed PDFs leave your organisation and are reviewed by people who do not use your signing platform. Consider it when:

  • you regularly send signed PDFs to customers, partners, banks or government agencies
  • your recipients use Adobe Acrobat or Acrobat Reader
  • auditors, legal or compliance teams need to review signatures independently
  • documents are shared with international counterparties
  • you want to reduce support queries caused by trust warnings

How SignDex Supports AATL-Backed Signing

SignDex supports AATL-backed digital signing through its integration with Namirial, an AATL-listed Trust Service Provider. Documents signed this way carry a Namirial certificate that Adobe Acrobat and Reader recognise automatically.

Local recognition and Adobe trust, on one platform. SignDex also integrates with Malaysia’s MCMC-licensed Certification Authorities, Pos Digicert and MSC Trustgate. Malaysian businesses often face a choice: sign with a local licensed CA, or with a certificate Adobe trusts for recipients overseas. With SignDex, you don’t need separate tools for each. You choose the right option for every document.

To protect the integrity of each signature, SignDex combines certificate trust with identity assurance:

  1. Prepare the document in SignDex and choose AATL-backed signing.
  2. Verify identity. If the signer has not yet completed identity verification, SignDex asks them to do so first.
  3. Confirm with SMS OTP. The signer confirms the signing action with a one-time password sent to their mobile phone.
  4. Sign. The document is signed with a Namirial certificate.
  5. Verify. The recipient opens the PDF in Acrobat or Reader and sees a trusted signature status, with no manual setup.

aatl-image3

AATL-backed signing in SignDex · 5 steps

SignDex confirms who the signer is before signing; the Namirial certificate and AATL make the result trusted in Adobe.

Choosing the Right Trust Model in SignDex

AATL-backed signing is one of several signing options in SignDex. Not every document needs the same level of assurance, so organisations can match the signing method to each workflow.

Signing option Certificate provider Best suited for
Standard digital signing SignDex Everyday internal and commercial agreements
Malaysian licensed CA signing MCMC-licensed CAs: Pos Digicert and MSC Trustgate Workflows that require a digital signature under Malaysia’s Digital Signature Act 1997
AATL-backed signing Namirial (AATL-listed) Documents sent to external or international recipients who verify in Adobe Acrobat or Reader

This lets you apply stronger assurance where it matters, without adding unnecessary steps to every document.

AATL as Part of a Broader Digital Trust Strategy

AATL covers one part of trusted signing: certificate recognition. A complete strategy considers six questions together.

Area The question it answers How SignDex helps
Identity verification Do we know who the signer is? Identity verification before signing, plus SMS OTP confirmation
Document integrity Can we detect changes after signing? Cryptographic signatures that flag any later modification
Certificate trust Will the recipient’s software recognise the certificate? AATL-backed signing via Namirial, and Malaysian licensed CAs
Long-term validation (LTV) Can the signature be verified years from now? PAdES B-LT and PAdES B-LTA signatures
Audit evidence Who signed, when, and what happened in the workflow? A full audit trail for every document
Regulatory requirements Does the method meet the law for this document? A choice of signing options to match each requirement

Frequently Asked Questions

What does AATL stand for?
AATL stands for Adobe Approved Trust List. It is Adobe’s list of Certificate Authorities and Trust Service Providers whose certificates Acrobat and Reader trust for PDF signatures.

Why does my signed PDF say “Signature validity is unknown”?
Usually because the reader does not recognise the certificate’s issuer. The document may be unchanged and the signature valid. Signing with an AATL-backed certificate prevents this warning in Adobe products.

Does the recipient need to install anything?
No. Acrobat and Reader update the AATL list automatically, so the recipient only needs to open the PDF.

Is an AATL-backed signature legally binding?
AATL does not determine legal validity. That depends on the laws of the relevant jurisdiction and the type of document. AATL improves how the signature is recognised in Adobe software.

Does AATL work outside Adobe Acrobat?
AATL is specific to Adobe products. Other PDF readers and validators use their own trust lists, so trust status may differ in non-Adobe software.

Is every SignDex signature AATL-backed?
No. AATL-backed signing through Namirial is one option. SignDex also offers standard signing and signing with Malaysian licensed Certification Authorities.

Conclusion

A signature is only as useful as the recipient’s ability to trust it. The Adobe Approved Trust List helps by letting Acrobat and Reader recognise trusted certificates automatically, removing the warnings that confuse recipients and slow down approvals.

AATL does not replace legal requirements, identity verification or long-term validation (LTV). It adds a layer of trust on top of them.
With its Namirial integration, SignDex combines AATL-backed certificates with identity verification and SMS OTP confirmation, giving your recipients a signature they can trust the moment they open it.

Was this article helpful?

0
0