X9 PKI is intended for non-browser TLS authentication scenarios. The main use case at the outset is mutual TLS (mTLS) among financial institutions and between them and their partners and customers. It is these applications that typically require the client authentication function that Google recently announced it will distrust soon.

Other applications beyond financial services can benefit from using X9 PKI rather than Web PKI certificates. The intention is to expand the offering based on customer needs.

X9 PKI offers a standards-based infrastructure designed to meet the rigorous security and interoperability needs of regulated industries. Here are four key benefits: 

• Independence from Browser-Controlled Trust Models 

• Interoperability Across Ecosystems 

• Support for Classical and Post-Quantum Cryptography (PQC) 

• Scalability with Cross-Certification Capabilities 

• Ability to tailor certificate management to the requirements of policy and regulatory compliance 

If your application has no need for communications outside of your networks, an internal PKI (private CA) may be the best solution. Even such applications often require public trust, as in the case of an API gateway accessible to partners.

Yes, they are. For more information and descriptions of other possible use cases, we encourage you to download X9 PKI Use Case Document from the ASC X9 website.