Auditing Linkerd proxies for FIPS compliance

The BEL CLI includes a command to verify that all Linkerd proxies on your Kubernetes cluster are FIPS-compliant.

Prerequisites

• Buoyant Enterprise for Linkerd installed with FIPS enabled
• The BUOYANT_LICENSE environment variable set, with functioning BEL CLI

Audit Linkerd proxies for FIPS compliance

To audit all Linkerd proxies for FIPS compliance on your Kubernetes cluster, run the following command:

linkerd fips audit

If all Linkerd proxies on the cluser are FIPS-compliant, you will see output similair to this:

√ Found 24 proxies. All proxies are FIPS-compliant.

If some Linkerd proxies on the cluser are not FIPS-compliant, they will be listed:

× non FIPS-compliant proxy found: emoji-5b74dbfc6-998f2 (enterprise-2.15.5)
× 1 non FIPS-compliant proxy found

Learning more

For more information about using linkerd fips audit, see the BEL CLI reference page.