FIPS 140-2 Compliant Plugins

This reference lists which Kong Gateway plugins are FIPS 140-2 compliant and provides additional details about how they maintain compliance.

PluginSubcomponent Compliance (if applicable)FIPS CompliantNotes
jwe-decryptN/AYesCompliant via BoringSSL
openid-connectAllYesCompliant via BoringSSL
jwt-signerAllYesCompliant via BoringSSL
key-auth-encN/AYesCompliant via BoringSSL
hmac-authN/AYesCompliant via BoringSSL
ldap-auth-advancedN/AYesCompliant via BoringSSL
proxy-cacheN/AYesCompliant via BoringSSL
proxy-cache-advancedN/AYesCompliant via BoringSSL
graphql-proxy-cache-advancedN/AYesCompliant via BoringSSL
mtls-authN/AYesCompliant via BoringSSL
oauth2N/AYesCompliant via BoringSSL
basic-authN/AYesCompliant via BoringSSL
samlN/AYesCompliant via BoringSSL
jwtN/AYesCompliant via BoringSSL
All other Kong Inc. pluginsN/AN/ANo cryptographic operations involved