--- title: "How to Integrate Apache APISIX with open-appsec WAF - API7.ai" description: "Learn how to integrate open-appsec WAF with Apache APISIX across Linux, Docker, and Kubernetes deployment environments." url: "https://api7.ai/blog/apisix-integrates-with-open-appsec-waf" --- [Blog](https://api7.ai/blog) [Products](https://api7.ai/category/products)[Technology](https://api7.ai/category/technology)[Ecosystem](https://api7.ai/category/ecosystem)[Case Study](https://api7.ai/category/usercase)[Team & Community](https://api7.ai/category/community) Search ⌘ + K [Blog](https://api7.ai/blog) Ecosystem # How to Integrate Apache APISIX with open-appsec WAF [![Christopher Lutat](https://github.com/ByteSkater.png)](https://github.com/ByteSkater) [Christopher Lutat](https://github.com/ByteSkater) October 21, 2024 [Ecosystem](https://api7.ai/category/ecosystem) ## Introduction open-appsec WAF integrates with Apache APISIX to inspect traffic and return allow-or-block decisions for APIs and web applications exposed through the gateway. This tutorial covers the integration workflow for Linux, Docker, and Kubernetes deployments. > This contributed tutorial reflects the integration workflow at publication time. Before deploying it, check the current [open-appsec documentation](https://docs.openappsec.io/) and [supported APISIX versions](https://downloads.openappsec.io/packages/supported-apisix.txt) for compatibility updates. ### About Apache APISIX [Apache APISIX](https://apisix.apache.org/) is a modern, flexible, and high-performance open-source API gateway solution designed to handle various use cases in microservices and cloud-native architectures. Its primary purpose is to facilitate API management by serving as a gateway for managing, securing, and optimizing API traffic between clients and backend services. Further use cases for APISIX as an API gateway include load balancing, rate limiting, authentication, and authorization. It provides comprehensive features such as traffic control, dynamic upstream, and plugin extensibility, enabling developers to customize and extend functionality according to their specific needs. - Website: [apisix.apache.org](https://apisix.apache.org/) - Github: [github.com/apache/apisix](https://github.com/apache/apisix) - Docs: [apisix.apache.org/docs](https://apisix.apache.org/docs) ### About open-appsec WAF [open-appsec WAF](https://www.openappsec.io/) provides automatic, preemptive threat prevention and integrates with various types of reverse proxies like NGINX as well as API gateways like APISIX. It is machine-learning-based, meaning it doesn't require signatures (or updates) at all. This enables it to provide automatic, state-of-the-art threat prevention even for true zero-day attacks while significantly reducing both administrative effort and the amount of false positives. In addition, open-appsec provides many additional security layers such as AntiBot, rate limiting, schema enforcement, snort signature support, custom rules/exceptions, and more. open-appsec can be managed centrally using a Web UI provided as a SaaS service and also locally using a declarative configuration file. - Website: [www.openappsec.io](https://www.openappsec.io/) - Github: [github.com/openappsec](https://github.com/openappsec) - Docs: [docs.openappsec.io](https://docs.openappsec.io/) - Playgrounds: [www.openappsec.io/playground](https://www.openappsec.io/playground) ## Integrating Apache APISIX with open-appsec open-appsec provides a WAF integration for Apache APISIX that inspects traffic to APIs and web applications exposed through the gateway. Users can deploy the free and open-source open-appsec Community Edition to apply its machine-learning-based protections and configure the additional security capabilities described below. The following sections cover Linux, Docker, and Kubernetes deployment workflows. ### Linux **For Linux "embedded" deployments** of APISIX, an open-appsec installer will add an "open-appsec attachment" module to the existing APISIX installation and also install the "open-appsec agent" alongside it, which will receive the traffic from the attachment, inspect it, and return the concluded action to block or allow the traffic back to the APISIX respectively the open-appsec attachment integrated with it. Here's a simple architecture schematic for Linux deployment. ![Architecture for Linus Deployment](https://static.api7.ai/uploads/2024/10/18/6QZvRy6P_linux-deployment.png?imageMogr2/format/webp) ### Docker **For Docker-based deployments** of APISIX with open-appsec WAF, there is a special APISIX container image available, to which the open-appsec attachment was already added and also an enhanced docker-compose file, which deploys both, the APISIX gateway container as well as an open-appsec Agent that does the security inspection and returns the concluded decisions to the APISIX gateway to allow or block traffic. Here's a simple architecture schematic for deployment on Docker. ![Architecture for Docker-Based Deployment](https://static.api7.ai/uploads/2024/10/18/bxKsXOqW_docker-deployment.png?imageMogr2/format/webp) ### Kubernetes **For Kubernetes based-deployments** of APISIX integrated with open-appsec, there's a Helm chart available, which is based on the official APISIX Helm chart and further enhanced to also include the open-appsec attachment in the APISIX gateway container and also deploys the open-appsec agent. Further, you will have the option to configure open-appsec in a declarative "DevOps-style" way using custom resources in K8s as an alternative to using the open-appsec central management Web UI. Here's a simple architecture schematic for deployment on Kubernetes. ![Architecture for Kubernetes Deployment](https://static.api7.ai/uploads/2024/10/18/SEZQ6E14_k8s-deployment.png?imageMogr2/format/webp) ## Adding open-appsec WAF to APISIX on Linux To install open-appsec on a Linux system with APISIX installed, please follow these steps: ### 1. Prerequisites - The Linux platform must be Ubuntu 22.04. - Make sure to have APISIX installed. You can find the list of supported APISIX versions here: . If you don't have APISIX installed yet, you can use the following commands to perform an APISIX installation in "traditional mode". By running these commands you will first install the etcd database for APISIX, then add the required repos before installing and starting APISIX. **Install etcd Database** ``` ETCD_VERSION='3.5.4' wget https://github.com/etcd-io/etcd/releases/download/v${ETCD_VERSION}/etcd-v${ETCD_VERSION}-linux-amd64.tar.gz tar -xvf etcd-v${ETCD_VERSION}-linux-amd64.tar.gz && cd etcd-v${ETCD_VERSION}-linux-amd64 cp -a etcd etcdctl /usr/bin/ nohup etcd >/tmp/etcd.log 2>&1 & etcd ``` **Add and Update Package Repositories** ``` apt install gnupg echo "deb http://openresty.org/package/debian bullseye openresty" | tee /etc/apt/sources.list.d/openresty.list wget -O - https://openresty.org/package/pubkey.gpg | apt-key add - wget -O - http://repos.apiseven.com/pubkey.gpg | apt-key add - echo "deb http://repos.apiseven.com/packages/debian bullseye main" | tee /etc/apt/sources.list.d/apisix.list apt update ``` **Install, Initiate, and Start APISIX** ``` apt install apisix=3.9.1-0 apisix init apisix start ``` ### 2. Download the open-appsec Installer ``` wget https://downloads.openappsec.io/open-appsec-install && chmod +x open-appsec-install ``` ### 3. Install open-appsec Install open-appsec to integrate with the existing APISIX installation. > Note that the `--prevent` flag will install open-appsec with a default policy already set to prevent mode. ``` ./open-appsec-install --auto --prevent ``` ### 4. Get and Store APISIX Admin Key Get the APISIX admin key from the APISIX `config.yaml` configuration file and store it in the `APISIX_KEY` env variable. ``` export APISIX_KEY=$(awk '/key:/{ if ($2 ~ /^edd1/) print $2 }' /usr/local/apisix/conf/config.yaml ) ``` ### 5. Configure Route to Expose Services Configure an example route in the APISIX gateway to expose an external web service or web API. In this example, we use `httpbin.org` as the example backend. ``` curl http://127.0.0.1:9180/apisix/admin/routes/100 -H "X-API-KEY:$APISIX_KEY" -X PUT -d '{ "methods": [ "GET" ], "uri": "/anything", "upstream": { "type": "roundrobin", "nodes": { "httpbin.org:80": 1 } } }' ``` ### 6. Validate Let's see if this route works by accessing it. ``` curl -s -v -G --data-urlencode email=user@domain.abc http://localhost:9080/anything ``` ### 7. Simulate an SQL Injection Attack Now let's try to simulate an SQL injection attack (see `'OR '1'='1'` in the below HTTP request) against the `httpbin.org` service exposed by the APISIX gateway which is now protected by the open-appsec WAF. ``` curl -s -v -G --data-urlencode email=user@domain.abc' OR '1'='1 http://localhost:9080/anything ``` This simulated attack now gets blocked successfully by open-appsec's contextual machine-learning WAF engine. ### 8. Review Log Files Check out the corresponding log files showing the "prevent" for the HTTP request with the simulated attack that we just sent. ``` tail -f /var/log/nano_agent/cp-nano-http-transaction-handler.log*| grep -i user@domain.abc ``` Alternatively you can use the `open-appsec-ctl` tool: ``` open-appsec-ctl --view-logs | grep -i user@domain.abc ``` ### 9. Connect to open-appsec for Central Management (Optional) Optionally you can connect your deployment now to [https://my.openappsec.io](https://my.openappsec.io/) for centrally managing open-appsec with an easy-to-use Web UI, monitoring security events and more, see section **How to Manage Your open-appsec WAF Deployment Centrally?** further below for more information. **Congratulations!** You successfully added open-appsec WAF to your existing APISIX installation and verified that your web services exposed by the APISIX gateway are now protected against web attacks. ## Deploying APISIX with open-appsec WAF on Containerized Platforms (Docker) To install APISIX integrated with open-appsec on Docker, you can follow the steps shown below. Opposite to the above example here we are deploying APISIX in "standalone mode", which means it's declaratively configured using a docker volume mount with a yaml file that holds the configurations and therefore won't require an etcd database deployment. > Note that APISIX supports both, traditional as well as standalone modes in all deployment types (Linux, Docker, …) ### 1. Prerequisite Make sure to have a Linux platform with both Docker and docker-compose tools installed. ### 2. Create a Folder for open-appsec Within the directory that you want to use for the deployment, create a folder `appsec-localconfig` which will hold the appsec declarative configuration file: ``` mkdir ./appsec-localconfig ``` ### 3. Download the open-appsec File into the Folder Download the initial declarative configuration file for open-appsec into that folder. ``` wget https://raw.githubusercontent.com/openappsec/openappsec/main/config/linux/latest/prevent/local_policy.yaml -O appsec-localconfig/local_policy.yaml ``` > Note that this example declarative configuration file is already set to prevent attacks. ### 4. Create a Folder for APISIX Create another folder `apisix-localconfig` which will hold the declarative configuration file for APISIX: `mkdir ./apisix-localconfig`. ### 5. Download APISIX File into the Folder Let's download a simple declarative configuration file also for APISIX so we can verify open-appsec protection after the deployment. ``` wget https://raw.githubusercontent.com/openappsec/openappsec/main/deployment/apisix/apisix-example-config/apisix-standalone.yaml -O ./apisix-localconfig/apisix-standalone.yaml ``` ### 6. Create a `docer-compose.yaml` File Create a `docker-compose.yaml` file with the content below, which can be downloaded as follows: ``` wget https://raw.githubusercontent.com/openappsec/openappsec/main/deployment/apisix/docker-compose.yaml ``` ``` version: "3" services: apisix: container_name: apisix image: "ghcr.io/openappsec/apisix-attachment:latest" ipc: service:appsec-agent restart: always volumes: - ./apisix-localconfig/apisix-standalone.yaml:/usr/local/apisix/conf/apisix.yaml:ro environment: - APISIX_STAND_ALONE=true ports: - "9180:9180/tcp" - "9080:9080/tcp" - "9091:9091/tcp" - "9443:9443/tcp" appsec-agent: container_name: appsec-agent image: 'ghcr.io/openappsec/agent:latest' ipc: shareable restart: unless-stopped environment: # adjust with your own email below - user_email=user@email.com - registered_server="APISIX Server" volumes: - ./appsec-config:/etc/cp/conf - ./appsec-data:/etc/cp/data - ./appsec-logs:/var/log/nano_agent - ./appsec-localconfig:/ext/appsec command: /cp-nano-agent ``` ### 7. Update Your Email Address (Optional) Edit the `docker-compose.yaml` file and replace "" with your own email address, so we can provide assistance in case of any issues with the specific deployment in the future and provide information proactively regarding open-appsec. This is an optional parameter and can be removed. If we send automatic emails, there will also be an opt-out option included for receiving similar communication in the future. ### 8. Start All Containers Run docker-compose up to start the deployment of all relevant containers: ``` docker-compose up -d ``` ### 9. Check Container Status Check if the `apisix-attachment` and the `appsec-agent` containers are up and running. ``` docker ps ``` ### 10. Validate the Standalone Configuration Let's see if the standalone configuration works by accessing it. ``` curl -s -v -G --data-urlencode email=user@domain.abc http://localhost:9080/anything ``` ### 11. Simulate an SQL Injection Attack Now let's try to simulate an SQL injection attack against the httpin.org service exposed by the APISIX gateway container which is now protected by open-appsec. ``` curl -s -v -G --data-urlencode email=user@domain.abc' OR '1'='1 http://localhost:9080/anything ``` ### 12. Connect to open-appsec for Central Management (Optional) Optionally you can connect your deployment now to `https://my.openappsec.io` for centrally managing open-appsec with an easy-to-use Web UI, monitoring security events, and more, see section **How to Manage Your open-appsec WAF Deployment Centrally?** further below for more information. ## Deploying APISIX with open-appsec WAF on Kubernetes Using Helm ### 1. Prerequisite Make sure the Kubernetes platform and Helm tool are available. ### 2. Download open-appsec Download the open-appsec for the APISIX Helm chart here. ``` wget https://downloads.openappsec.io/packages/helm-charts/apisix/open-appsec-k8s-apisix-latest.tgz ``` ### 3. Install Helm Chart This example `helm install` command is installing the open-appsec for the APISIX Helm chart which is based on an extended version of the official APISIX Helm chart. It will deploy the APISIX gateway as the APISIX Ingress Controller, as well as open-appsec WAF integrated with it. It also offers an additional configuration option specifically for open-appsec WAF (see `values.yaml` inside the Helm chart and open-appsec [docs](https://docs.openappsec.io/)). After deployment, you can assign your K8s ingress resources to the APISIX gateway by configuring them to use the following ingress class: `appsec-apisix`. ``` helm install open-appsec-k8s-apisix-latest.tgz \ --name-template=appsec-apisix \ --set rbac.create=true \ --set appsec.mode=standalone \ --set service.type=LoadBalancer \ --set appsec.persistence.enabled=false \ --set ingress-controller.enabled=true \ --set ingress-controller.config.ingressClass=appsec-apisix \ --set appsec.userEmail=”” \ --set appsec.agentToken= \ --create-namespace \ -n appsec-apisix ``` > Replace in the Helm install command above with your own email address, so we can send you news and updates related to open-appsec and better support you with your deployment if needed! You can unsubscribe at any time or alternatively, just remove that line if you prefer not to provide your email. ### 4. Validate Validate that pods were properly deployed and are in a ready state: ``` kubectl get pods -n appsec-apisix ``` ### 5. Create an open-appsec Policy Resource Run the following command to create the "open-appsec-best-practice-policy" in K8s. > Note that this example policy is already pre-configured to prevent attacks. ``` kubectl apply -f https://raw.githubusercontent.com/openappsec/openappsec/main/config/k8s/v1beta1/open-appsec-k8s-prevent-config-v1beta1.yaml ``` You can also create your own custom policy, [here](https://docs.openappsec.io/getting-started/start-with-kubernetes/configuration-using-crds) you find all the details. ### 6. Fetch the Target Resource Name Find out the name of the relevant ingress resource which you want to protect: ``` kubectl get ing -A ``` ### 7. Edit the Ingress Resource ``` kubectl edit ing/ -n ``` ### 8. Change the ingressClassname Change the ingressClassname to use open-appsec: ``` spec: ingressClassName: appsec-apisix ``` ### 9. Add Annotation to the Ingress Resource Add this annotation to the ingress resource to activate open-appsec for this ingress by specifying the desired open-appsec policy custom resource. ``` openappsec.io/policy: open-appsec-best-practice-policy ``` ### 10. Validate the Standalone Configuration Let's see if the standalone configuration works by accessing it: ``` curl -s -v -G --data-urlencode email=user@domain.abc http://[YOUR-INGRESS-HOSTNAME] ``` ### 11. Simulate an SQL Injection Attack Now let's try to simulate an SQL injection attack against the `httpin.org` service exposed by the APISIX gateway container which is now protected by open-appsec. ``` curl -s -v -G --data-urlencode email=user@domain.abc' OR '1'='1 http://[YOUR-INGRESS-HOSTNAME] ``` Replace \[YOUR-INGRESS-HOSTNAME] in the command above with the hostname you set in the ingress resource which you protected with open-appsec WAF in the earlier steps, also change "http" to "https" if required. **Congratulations!** You successfully deployed APISIX integrated with open-appsec WAF and verified that your web services exposed by the APISIX Gateway are now protected against attacks. ## How to Manage Your open-appsec WAF Deployment Centrally? If you like you can also manage your open-appsec WAF deployment (integrated with APISIX) centrally using the open-appsec Web UI (SaaS Service) available at [https://my.openappsec.io](https://my.openappsec.io/), by connecting the open-appsec agent to a deployment profile in the central Web UI. You can alternatively continue to manage your deployment locally but still connect to a central WebUI profile in "Declarative mode" so that you will be able to see the local configuration (read-only) in the Web UI. Alongside the configuration of open-appsec the Web UI allows you to also see much more information like the status of deployed open-appsec agents, security logs, dashboards, and more. For instructions on how to connect your deployment to the central Web UI see the open-appsec docs available at [https://docs.openappsec.io](https://docs.openappsec.io/). Below you find some screenshots of the Web UI. ![Open-websec UI 1](https://static.api7.ai/uploads/2024/10/11/MzsUwqh3_open-appsec-4.jpeg?imageMogr2/format/webp) ![Open-websec UI 2](https://static.api7.ai/uploads/2024/10/11/YFofdEzT_open-appsec-5.jpeg?imageMogr2/format/webp) ## Summary In this blog we explained how open-appsec can integrate with Apache APISIX on all of the following: regular Linux-based deployments, containerized deployments (Docker), and also Kubernetes environments. Following the deployment steps for APISIX with open-appsec WAF, we simulated SQL injection attacks, which were effectively prevented by open-appsec's machine learning-based WAF technology. Additionally, it was explained, what the benefits are of connecting to open-appsec central WebUI for managing, monitoring, log analysis, and reporting. These workflows show how open-appsec WAF can protect APIs and web applications exposed through Apache APISIX. Contact us if you have feedback, questions, or technical issues. You can reach the open-appsec team through the chat at [openappsec.io](https://www.openappsec.io/) or by email at . ## Additional Resources ### open-appsec WAF Website: [https://www.openappsec.io](https://www.openappsec.io/) GitHub: Docs: [https://docs.openappsec.io](https://docs.openappsec.io/) Playgrounds: Blogs: ### Apache APISIX Website: [https://apisix.apache.org](https://apisix.apache.org/) GitHub: Docs: Blogs: Tags: [WAF](https://api7.ai/tags/waf) [API Security](https://api7.ai/tags/api-security) [Data Security](https://api7.ai/tags/data-security) Share article link Share Related Posts [![WAF & API Gateway Integration: Protecting Your APIs](https://static.api7.ai/uploads/2024/01/29/xV7L0ef7_APISIX_WAF_Cover.jpeg)](https://api7.ai/blog/waf-and-api-gateway-integration) ## [WAF & API Gateway Integration: Protecting Your APIs](https://api7.ai/blog/waf-and-api-gateway-integration) [![mTLS Everywhere: How to Configure TLS for APISIX](https://static.api7.ai/uploads/2024/12/24/DVhnbLpy_apisix-mtls.png)](https://api7.ai/blog/configure-tls-for-apisix) ## [mTLS Everywhere: How to Configure TLS for APISIX](https://api7.ai/blog/configure-tls-for-apisix) Table of Contents - [Introduction](#introduction) - [About Apache APISIX](#about-apache-apisix) - [About open-appsec WAF](#about-open-appsec-waf) - [Integrating Apache APISIX with open-appsec](#integrating-apache-apisix-with-open-appsec) - [Linux](#linux) - [Docker](#docker) - [Kubernetes](#kubernetes) - [Adding open-appsec WAF to APISIX on Linux](#adding-open-appsec-waf-to-apisix-on-linux) - [1. Prerequisites](#1-prerequisites) - [2. Download the open-appsec Installer](#2-download-the-open-appsec-installer) - [3. Install open-appsec](#3-install-open-appsec) - [4. Get and Store APISIX Admin Key](#4-get-and-store-apisix-admin-key) - [5. Configure Route to Expose Services](#5-configure-route-to-expose-services) - [6. Validate](#6-validate) - [7. Simulate an SQL Injection Attack](#7-simulate-an-sql-injection-attack) - [8. Review Log Files](#8-review-log-files) - [9. Connect to open-appsec for Central Management (Optional)](#9-connect-to-open-appsec-for-central-management-optional) - [Deploying APISIX with open-appsec WAF on Containerized Platforms (Docker)](#deploying-apisix-with-open-appsec-waf-on-containerized-platforms-docker) - [1. Prerequisite](#1-prerequisite) - [2. Create a Folder for open-appsec](#2-create-a-folder-for-open-appsec) - [3. Download the open-appsec File into the Folder](#3-download-the-open-appsec-file-into-the-folder) - [4. Create a Folder for APISIX](#4-create-a-folder-for-apisix) - [5. Download APISIX File into the Folder](#5-download-apisix-file-into-the-folder) - [6. Create a `docer-compose.yaml` File](#6-create-a-docer-composeyaml-file) - [7. Update Your Email Address (Optional)](#7-update-your-email-address-optional) - [8. Start All Containers](#8-start-all-containers) - [9. Check Container Status](#9-check-container-status) - [10. Validate the Standalone Configuration](#10-validate-the-standalone-configuration) - [11. Simulate an SQL Injection Attack](#11-simulate-an-sql-injection-attack) - [12. Connect to open-appsec for Central Management (Optional)](#12-connect-to-open-appsec-for-central-management-optional) - [Deploying APISIX with open-appsec WAF on Kubernetes Using Helm](#deploying-apisix-with-open-appsec-waf-on-kubernetes-using-helm) - [1. Prerequisite](#1-prerequisite-1) - [2. Download open-appsec](#2-download-open-appsec) - [3. Install Helm Chart](#3-install-helm-chart) - [4. Validate](#4-validate) - [5. Create an open-appsec Policy Resource](#5-create-an-open-appsec-policy-resource) - [6. Fetch the Target Resource Name](#6-fetch-the-target-resource-name) - [7. Edit the Ingress Resource](#7-edit-the-ingress-resource) - [8. Change the ingressClassname](#8-change-the-ingressclassname) - [9. Add Annotation to the Ingress Resource](#9-add-annotation-to-the-ingress-resource) - [10. Validate the Standalone Configuration](#10-validate-the-standalone-configuration-1) - [11. Simulate an SQL Injection Attack](#11-simulate-an-sql-injection-attack-1) - [How to Manage Your open-appsec WAF Deployment Centrally?](#how-to-manage-your-open-appsec-waf-deployment-centrally) - [Summary](#summary) - [Additional Resources](#additional-resources) - [open-appsec WAF](#open-appsec-waf) - [Apache APISIX](#apache-apisix) ## Related Posts [![PHP2Shell Emergency Mitigation: Blocking Risky Requests at the Gateway with Apache APISIX](https://static.api7.ai/uploads/2026/10/24/z1kzFYbs_php2shell-content-cover-en-wechat.webp)](https://api7.ai/blog/php2shell-mitigation-with-apache-apisix) Technology October 24, 2026 #### [PHP2Shell Emergency Mitigation: Blocking Risky Requests at the Gateway with Apache APISIX](https://api7.ai/blog/php2shell-mitigation-with-apache-apisix) Mitigate PHP2Shell with Apache APISIX: reject unwanted multipart requests or inspect uploads with Coraza WAF while preparing PHP security updates. [API Security](https://api7.ai/tags/api-security) [APISIX](https://api7.ai/tags/apisix) [WAF](https://api7.ai/tags/waf) [![API7 Enterprise v3.2.16.3 Integrates with AWS Secrets Manager](https://static.api7.ai/uploads/2025/02/13/nrkyTz2U_3.2.16.3-aws-secrets-manager.png)](https://api7.ai/blog/api7-3.2.16.3-supports-aws-secrets-manager) Products November 7, 2024 #### [API7 Enterprise v3.2.16.3 Integrates with AWS Secrets Manager](https://api7.ai/blog/api7-3.2.16.3-supports-aws-secrets-manager) API7 Enterprise v3.2.16.3 integrates with AWS Secrets Manager for secure, efficient management and protection of sensitive data. [API Security](https://api7.ai/tags/api-security) [Data Security](https://api7.ai/tags/data-security) [API7 Enterprise](https://api7.ai/tags/api7-enterprise) [![API7 Enterprise v3.2.16: Integrated Secret Providers](https://static.api7.ai/uploads/2024/09/29/QQqmcORv_Integrated%20Secret%20Providers.png)](https://api7.ai/blog/api7-3.2.16-integrated-secret-providers) Products October 10, 2024 #### [API7 Enterprise v3.2.16: Integrated Secret Providers](https://api7.ai/blog/api7-3.2.16-integrated-secret-providers) API7 Enterprise v3.2.16 seamlessly integrates with secret providers like HashiCorp Vault, enabling effortless management and referencing of external sensitive information. [API Security](https://api7.ai/tags/api-security) [Data Security](https://api7.ai/tags/data-security) [API7 Enterprise](https://api7.ai/tags/api7-enterprise)