Not All ACME Protocol Integrations Are Equal

Here is what makes AppViewX AVX ONE CLM different when integrating with ACME

What is the ACME Protocol?

ACME, or Automated Certificate Management Environment, is a communications protocol that automates interactions between Certificate Authorities (CAs) and server endpoints. To do this, it leverages an agent such as certbot to automate the process of CSR generation and certificate and key rotation.

The ACME protocol is primarily used by the popular public CA, Let’s Encrypt, as a part of its business model of issuing 90-day DomainValidated (DV) certificates and automating their renewals. Because Organizational Validation (OV) and Extended Validation (EV) certificates require more human supervision to issue, the ACME protocol is not a valid automation method, Additionally, Google with its 90-day TLS validity proposal is building on this idea as an industry standard laying the foundations for a Post-Quantum world of Cryptography.

Why do enterprises use ACME?

While originally only used by Let’s Encrypt to issue x.509 (SSL/TLS) certificates, various other CAs, PKI vendors, and browsers are now beginning to support ACME to work with other kinds of certificates such as S/MIME and code signing as well. However, to leverage them, the CA should be able to access the DNS/HTTPS token that is published. They should also be able to process custom attributes involved to identify the usage of the certificates across an organization’s enterprise infrastructure.

Because of this, the ACME protocol may be better suited to be an internal PKI issuance method for private trust use cases.

For Instance: An Internal application team requests a certificate issued by a known CA for their applications hosted on a Linux server and approved by their PKI team to secure access to it. The certificate always has custom attributes appended to it to help the PKI team identify the uniqueness of the usage of the certificate by the application teams. It is also required for billing, auditing and compliance purposes.

Problem with ACME and Existing Clients

The custom attributes are not a built-in functionality on the agents and are appended by the PKI team after certificate issuance. This leads to a lot of work usually done manually by the PKI teams, which renders the process slow and highly prone to errors. This can be detrimental to not only the speed and agility required by the internal applications teams, but also the billing and the audit teams.

AppViewX AVX ONE Certificate Lifecycle Management and ACME

With its AVX ONE Certificate Lifecycle Management (CLM) solution, AppViewX is the only CLM offering to have customized the agents, such as Certbot, to provide the extended functionality of custom attributes to be built-in for customers over the existing Certbot client to help meet various business and operational needs. The custom attributes will be sent as part of the payload in the finalized order call along with the CSR to the CA.

Certificate Lifecycle Management with Visibility, Control and Insights – All in One Place

The Agents are a single click Installation and interactive certificate lifecycle management operations can be seamlessly performed using AppViewX AVX ONE CLM. Additionally, AVX ONE CLM provides ready-to-use dashboards, actionable reports and certificate expiration alerts to PKI administrators and application teams.

The ability to parse custom attributes is a significant differentiator of the AppViewX AVX ONE CLM solution over other CLM products. Users can leverage it to customize the reports to help with the billing, auditing and compliance needs associated with internal PKI implementations.

With AppViewX AVX ONE CLM, certificates can be issued by any CA. If there is a need to change the issuing CA or need for an additional Issuing CA, only minimal configuration changes are required in the AVX ONE CLM solution . These changes are simple and quick to execute, making the process efficient and flexible.

For this internal PKI use case, AppViewX AVX ONE CLM supports the following Linux OS versions:he

  • Ubuntu 20.4
  • CentOS 7
  • Redhat 8.6
  • Debian 10
  • Devuan 3
  • OpenSUSE Tumbleweed

To learn more about the advantages of integrating the ACME protocol with the AppViewX AVX ONE CLM solution, we invite you to request a demo today.

Tags

  • ACME protocol
  • Certificate authority
  • code signing
  • PKI
  • SSL/TLS
  • x.509

About the Author

Shiva Kumar

Customer Success Architect

Enabling customers to resolve business challenges by designing solutions and facilitating a better understanding of the AppViewX platform.

More From the Author →

Related Articles

The Importance of Code Signing Best Practices in the Software Development Lifecycle

| 12 Min Read

Google Second-Gen Chromecast and Audio Devices Hit By A Major Outage—Expired Intermediate CA Certificate to Blame

| 5 Min Read

AppViewX AVX ONE Code Signing Integration with GitHub

| 4 Min Read