[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"similar-openappsec--openappsec":3,"tool-openappsec--openappsec":64},[4,16,27,35,48,56],{"id":5,"name":6,"github_repo":7,"description_zh":8,"stars":9,"difficulty_score":10,"last_commit_at":11,"category_tags":12,"status":15},8272,"opencode","anomalyco\u002Fopencode","OpenCode 是一款开源的 AI 编程助手（Coding Agent），旨在像一位智能搭档一样融入您的开发流程。它不仅仅是一个代码补全插件，而是一个能够理解项目上下文、自主规划任务并执行复杂编码操作的智能体。无论是生成全新功能、重构现有代码，还是排查难以定位的 Bug，OpenCode 都能通过自然语言交互高效完成，显著减少开发者在重复性劳动和上下文切换上的时间消耗。\n\n这款工具专为软件开发者、工程师及技术研究人员设计，特别适合希望利用大模型能力来提升编码效率、加速原型开发或处理遗留代码维护的专业人群。其核心亮点在于完全开源的架构，这意味着用户可以审查代码逻辑、自定义行为策略，甚至私有化部署以保障数据安全，彻底打破了传统闭源 AI 助手的“黑盒”限制。\n\n在技术体验上，OpenCode 提供了灵活的终端界面（Terminal UI）和正在测试中的桌面应用程序，支持 macOS、Windows 及 Linux 全平台。它兼容多种包管理工具，安装便捷，并能无缝集成到现有的开发环境中。无论您是追求极致控制权的资深极客，还是渴望提升产出的独立开发者，OpenCode 都提供了一个透明、可信",144296,1,"2026-04-16T14:50:03",[13,14],"Agent","插件","ready",{"id":17,"name":18,"github_repo":19,"description_zh":20,"stars":21,"difficulty_score":22,"last_commit_at":23,"category_tags":24,"status":15},6121,"gemini-cli","google-gemini\u002Fgemini-cli","gemini-cli 是一款由谷歌推出的开源 AI 命令行工具，它将强大的 Gemini 大模型能力直接集成到用户的终端环境中。对于习惯在命令行工作的开发者而言，它提供了一条从输入提示词到获取模型响应的最短路径，无需切换窗口即可享受智能辅助。\n\n这款工具主要解决了开发过程中频繁上下文切换的痛点，让用户能在熟悉的终端界面内直接完成代码理解、生成、调试以及自动化运维任务。无论是查询大型代码库、根据草图生成应用，还是执行复杂的 Git 操作，gemini-cli 都能通过自然语言指令高效处理。\n\n它特别适合广大软件工程师、DevOps 人员及技术研究人员使用。其核心亮点包括支持高达 100 万 token 的超长上下文窗口，具备出色的逻辑推理能力；内置 Google 搜索、文件操作及 Shell 命令执行等实用工具；更独特的是，它支持 MCP（模型上下文协议），允许用户灵活扩展自定义集成，连接如图像生成等外部能力。此外，个人谷歌账号即可享受免费的额度支持，且项目基于 Apache 2.0 协议完全开源，是提升终端工作效率的理想助手。",100752,2,"2026-04-10T01:20:03",[14,13,25,26],"图像","开发框架",{"id":28,"name":29,"github_repo":30,"description_zh":31,"stars":32,"difficulty_score":22,"last_commit_at":33,"category_tags":34,"status":15},4721,"markitdown","microsoft\u002Fmarkitdown","MarkItDown 是一款由微软 AutoGen 团队打造的轻量级 Python 工具，专为将各类文件高效转换为 Markdown 格式而设计。它支持 PDF、Word、Excel、PPT、图片（含 OCR）、音频（含语音转录）、HTML 乃至 YouTube 链接等多种格式的解析，能够精准提取文档中的标题、列表、表格和链接等关键结构信息。\n\n在人工智能应用日益普及的今天，大语言模型（LLM）虽擅长处理文本，却难以直接读取复杂的二进制办公文档。MarkItDown 恰好解决了这一痛点，它将非结构化或半结构化的文件转化为模型“原生理解”且 Token 效率极高的 Markdown 格式，成为连接本地文件与 AI 分析 pipeline 的理想桥梁。此外，它还提供了 MCP（模型上下文协议）服务器，可无缝集成到 Claude Desktop 等 LLM 应用中。\n\n这款工具特别适合开发者、数据科学家及 AI 研究人员使用，尤其是那些需要构建文档检索增强生成（RAG）系统、进行批量文本分析或希望让 AI 助手直接“阅读”本地文件的用户。虽然生成的内容也具备一定可读性，但其核心优势在于为机器",93400,"2026-04-06T19:52:38",[14,26],{"id":36,"name":37,"github_repo":38,"description_zh":39,"stars":40,"difficulty_score":22,"last_commit_at":41,"category_tags":42,"status":15},2268,"ML-For-Beginners","microsoft\u002FML-For-Beginners","ML-For-Beginners 是由微软推出的一套系统化机器学习入门课程，旨在帮助零基础用户轻松掌握经典机器学习知识。这套课程将学习路径规划为 12 周，包含 26 节精炼课程和 52 道配套测验，内容涵盖从基础概念到实际应用的完整流程，有效解决了初学者面对庞大知识体系时无从下手、缺乏结构化指导的痛点。\n\n无论是希望转型的开发者、需要补充算法背景的研究人员，还是对人工智能充满好奇的普通爱好者，都能从中受益。课程不仅提供了清晰的理论讲解，还强调动手实践，让用户在循序渐进中建立扎实的技能基础。其独特的亮点在于强大的多语言支持，通过自动化机制提供了包括简体中文在内的 50 多种语言版本，极大地降低了全球不同背景用户的学习门槛。此外，项目采用开源协作模式，社区活跃且内容持续更新，确保学习者能获取前沿且准确的技术资讯。如果你正寻找一条清晰、友好且专业的机器学习入门之路，ML-For-Beginners 将是理想的起点。",85267,"2026-04-18T11:00:28",[25,43,44,14,13,45,46,26,47],"数据工具","视频","其他","语言模型","音频",{"id":49,"name":50,"github_repo":51,"description_zh":52,"stars":53,"difficulty_score":22,"last_commit_at":54,"category_tags":55,"status":15},51,"gstack","garrytan\u002Fgstack","gstack 是 Y Combinator CEO Garry Tan 亲自开源的一套 AI 工程化配置，旨在将 Claude Code 升级为你的虚拟工程团队。面对单人开发难以兼顾产品战略、架构设计、代码审查及质量测试的挑战，gstack 提供了一套标准化解决方案，帮助开发者实现堪比二十人团队的高效产出。\n\n这套配置特别适合希望提升交付效率的创始人、技术负责人，以及初次尝试 Claude Code 的开发者。gstack 的核心亮点在于内置了 15 个具有明确职责的 AI 角色工具，涵盖 CEO、设计师、工程经理、QA 等职能。用户只需通过简单的斜杠命令（如 `\u002Freview` 进行代码审查、`\u002Fqa` 执行测试、`\u002Fplan-ceo-review` 规划功能），即可自动化处理从需求分析到部署上线的全链路任务。\n\n所有操作基于 Markdown 和斜杠命令，无需复杂配置，完全免费且遵循 MIT 协议。gstack 不仅是一套工具集，更是一种现代化的软件工厂实践，让单人开发者也能拥有严谨的工程流程。",76914,"2026-04-19T11:06:59",[13,14],{"id":57,"name":58,"github_repo":59,"description_zh":60,"stars":61,"difficulty_score":10,"last_commit_at":62,"category_tags":63,"status":15},7525,"codex","openai\u002Fcodex","Codex 是 OpenAI 推出的一款轻量级编程智能体，专为在终端环境中高效运行而设计。它允许开发者直接在命令行界面与 AI 交互，完成代码生成、调试、重构及项目维护等任务，无需频繁切换至浏览器或集成开发环境，从而显著提升了编码流程的连贯性与专注度。\n\n这款工具主要解决了传统 AI 辅助编程中上下文割裂的问题。通过将智能体本地化运行，Codex 能够更紧密地结合当前工作目录的文件结构，提供更具针对性的代码建议，同时支持以自然语言指令驱动复杂的开发操作，让“对话即编码”成为现实。\n\nCodex 非常适合习惯使用命令行的软件工程师、全栈开发者以及技术研究人员。对于追求极致效率、偏好键盘操作胜过图形界面的极客用户而言，它更是理想的结对编程伙伴。\n\n其独特亮点在于灵活的部署方式：既可作为全局命令行工具通过 npm 或 Homebrew 一键安装，也能无缝对接现有的 ChatGPT 订阅计划（如 Plus 或 Pro），直接复用账户权益。此外，它还提供了从纯文本终端到桌面应用的多形态体验，并支持基于 API 密钥的深度定制，充分满足不同场景下的开发需求。",75220,"2026-04-14T14:40:34",[46,13,14],{"id":65,"github_repo":66,"name":67,"description_en":68,"description_zh":69,"ai_summary_zh":70,"readme_en":71,"readme_zh":72,"quickstart_zh":73,"use_case_zh":74,"hero_image_url":75,"owner_login":67,"owner_name":67,"owner_avatar_url":76,"owner_bio":77,"owner_company":78,"owner_location":78,"owner_email":78,"owner_twitter":78,"owner_website":79,"owner_url":80,"languages":81,"stars":114,"forks":115,"last_commit_at":116,"license":117,"difficulty_score":118,"env_os":119,"env_gpu":120,"env_ram":120,"env_deps":121,"category_tags":134,"github_topics":135,"view_count":22,"oss_zip_url":78,"oss_zip_packed_at":78,"status":15,"created_at":151,"updated_at":152,"faqs":153,"releases":182},9778,"openappsec\u002Fopenappsec","openappsec","open-appsec is a machine learning security engine that preemptively and automatically prevents threats against Web Application & APIs. This repo include the main code and logic.","openappsec 是一款基于机器学习的开源安全引擎，专为 Web 应用程序和 API 提供主动式威胁防护。它能够有效抵御 OWASP Top 10 常见漏洞以及未知的零日攻击，解决了传统防火墙依赖固定规则、难以应对新型攻击的痛点。\n\n该工具的核心亮点在于其独特的“双重模型”机制：首先利用在全球数百万次请求中训练出的监督学习模型，快速识别已知攻击模式；随后结合在用户特定环境中实时构建的无监督学习模型，分析流量行为基线，精准判断异常请求。这种机制让 openappsec 能像人类一样“理解”正常业务逻辑，从而大幅降低误报率。\n\nopenappsec 非常适合 DevOps 工程师、后端开发者及安全运维人员使用。它部署灵活，可作为插件无缝集成到 Linux、Docker 或 Kubernetes 环境中，支持 NGINX、Kong、APISIX 及 Envoy 等主流网关。用户既可以通过声明式配置文件和 Helm Charts 进行管理，也能借助直观的 SaaS Web 界面实时监控安全态势。无论是用于测试环境的初步验证，还是生产环境的高强度防护，openappsec 都能提供自动化且智","openappsec 是一款基于机器学习的开源安全引擎，专为 Web 应用程序和 API 提供主动式威胁防护。它能够有效抵御 OWASP Top 10 常见漏洞以及未知的零日攻击，解决了传统防火墙依赖固定规则、难以应对新型攻击的痛点。\n\n该工具的核心亮点在于其独特的“双重模型”机制：首先利用在全球数百万次请求中训练出的监督学习模型，快速识别已知攻击模式；随后结合在用户特定环境中实时构建的无监督学习模型，分析流量行为基线，精准判断异常请求。这种机制让 openappsec 能像人类一样“理解”正常业务逻辑，从而大幅降低误报率。\n\nopenappsec 非常适合 DevOps 工程师、后端开发者及安全运维人员使用。它部署灵活，可作为插件无缝集成到 Linux、Docker 或 Kubernetes 环境中，支持 NGINX、Kong、APISIX 及 Envoy 等主流网关。用户既可以通过声明式配置文件和 Helm Charts 进行管理，也能借助直观的 SaaS Web 界面实时监控安全态势。无论是用于测试环境的初步验证，还是生产环境的高强度防护，openappsec 都能提供自动化且智能的安全保障，帮助团队轻松构建更稳固的应用防线。","\u003Cdiv align=center>\n\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_6de6edeceff0.png\" width=\"100\" height=\"100\"> \n\u003Ch1>openappsec\u002Fopenappsec\u003C\u002Fh1>\n\u003C\u002Fdiv>\n\n[![CII Best Practices](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_50ccde67b228.png)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F6629)\n\n# About\n[open-appsec](https:\u002F\u002Fwww.openappsec.io) (openappsec.io) builds on machine learning to provide preemptive web app & API threat protection against OWASP-Top-10 and zero-day attacks. It can be deployed as an add-on to Linux, Docker or K8s deployments, on NGINX, Kong, APISIX, or Envoy.\n\nThe open-appsec engine learns how users normally interact with your web application. It then uses this information to automatically detect requests that fall outside of normal operations, and conducts further analysis to decide whether the request is malicious or not.\n\nUpon every HTTP request, all parts are decoded, JSON and XML sections are extracted, and any IP-level access control is applied.\n\nEvery request to the application goes through two phases:\n\n1. Multiple variables are fed to the machine-learning engine. These variables, which are either directly extracted from the HTTP request or decoded from different parts of the payload, include attack indicators, IP addresses, user agents, fingerprints, and many other considerations. The supervised model of the machine learning engine uses these variables to compare the request with many common attack patterns found across the globe.\n\n2. If the request is identified as a valid and legitimate request the request is allowed, and forwarded to your application. If, however, the request is considered suspicious or high risk, it then gets evaluated by the unsupervised model, which was trained in your specific environment. This model uses information such as the URL and the users involved to create a final confidence score that determines whether the request should be allowed or blocked.\n\n![image](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_559cb5892f93.png)\n\n\nopen-appsec uses two machine learning models:\n\n1. A supervised model that was trained offline based on millions of requests, both malicious and benign.\n    \n    * A **basic model** is provided as part of this repository. It is recommended for use in Monitor-Only and Test environments.\n    * An **advanced model** which is more accurate and **recommended for Production** use can be downloaded from the [open-appsec portal](https:\u002F\u002Fmy.openappsec.io)->User Menu->Download advanced ML model. This model updates from time to time and you will get an email when these updates happen.\n\n2. An unsupervised model that is being built in real time in the protected environment. This model uses traffic patterns specific to the environment.\n\n\n# Management\n\nopen-appsec can be managed using multiple methods:\n* [Declarative configuration files](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n* [Kubernetes Helm Charts and annotations](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n* [Using SaaS Web Management](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fusing-the-web-ui-saas)\n\nopen-appsec Web UI:\n\u003Cimg width=\"1854\" height=\"775\" alt=\"image\" src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_1c627fe1884b.png\" \u002F>\n\n\n\n## Deployment Playgrounds (Virtual labs)\nYou can experiment with open-appsec using [Playgrounds](https:\u002F\u002Fwww.openappsec.io\u002Fplayground)\n\u003Cimg width=\"781\" height=\"878\" alt=\"image\" src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_1a54d82ab41b.png\" \u002F>\n\n# Resources\n* [Project Website](https:\u002F\u002Fopenappsec.io)\n* [Offical Documentation](https:\u002F\u002Fdocs.openappsec.io\u002F)\n* [Video Tutorials](https:\u002F\u002Fwww.openappsec.io\u002Ftutorials)\n\n# Installation\n\nFor Kubernetes (NGINX \u002FKong \u002F APISIX \u002F Istio) using Helm: follow [documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes)\n\nFor Linux (NGINX \u002F Kong \u002F APISIX) using the installer (list of supported\u002Fpre-compiled NGINX attachments is available [here](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fsupported-nginx.txt)):\n\n```bash\n$ wget https:\u002F\u002Fdownloads.openappsec.io\u002Fopen-appsec-install && chmod +x open-appsec-install\n$ .\u002Fopen-appsec-install --auto\n```\nFor kong Lua Based plug in follow [documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-linux)\n\nFor Linux, if you’ve built your own package use the following commands:\n\n```bash\n$ install-cp-nano-agent.sh --install --hybrid_mode\n$ install-cp-nano-service-http-transaction-handler.sh --install\n$ install-cp-nano-attachment-registration-manager.sh --install\n```\nYou can add the ```--token \u003Ctoken>``` and ```--email \u003Cemail address>``` and ```registered_server```  options to the first command, to get a token follow [documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fusing-the-web-ui-saas\u002Fconnect-deployed-agents-to-saas-management-k8s-and-linux). \n\nFor Docker: follow [documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-docker) \n\nFor more information read the [documentation](https:\u002F\u002Fdocs.openappsec.io\u002F) or follow the [video tutorials](https:\u002F\u002Fwww.openappsec.io\u002Ftutorials).\n\n# Repositories\n\nopen-appsec GitHub includes four main repositories:\n\n* [openappsec\u002Fopenappsec](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec) the main code and logic of open-appsec. Developed in C++.\n* [openappsec\u002Fattachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment) connects between processes that provide HTTP data (e.g NGINX) and the open-appsec Agent security logic. Developed in C.\n* [openappsec\u002Fsmartsync](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fsmartsync) in charge of correlating learning data from multiple agent instances and delivering a unified learning model for each asset. Developed in Golang.\n* [openappsec\u002Fsmartsync-shared-files](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fsmartsync-shared-files) interface to physical storage used by smartsync service for storing learning data. Developed in Golang.\n\n# Compilation instructions\n\n## Installing external dependencies\n\nBefore compiling the services, you'll need to ensure the latest development versions of the following libraries and tools:\n* Boost\n* OpenSSL\n* PCRE2\n* libxml2\n* GTest\n* GMock\n* cURL\n* Redis\n* Hiredis\n* MaxmindDB\n* yq\n\nAn example of installing the packages on Alpine:\n\n```bash\n $ apk update\n $ apk add boost-dev openssl-dev pcre2-dev libxml2-dev gtest-dev curl-dev hiredis-dev redis libmaxminddb-dev yq\n```\n\n## Compiling and packaging the agent code\n\n1. Clone this repository\n2. Run CMake command\n3. Run make install command\n\n```bash\n $ git clone https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec.git\n $ cd openappsec\u002F\n $ cmake -DCMAKE_INSTALL_PREFIX=build_out .\n $ make install\n $ make package\n```\n\n## Placing the agent code inside an Alpine docker image\n\nOnce the agent code has been compiled and packaged, an Alpine image running it can be created. This requires permissions to execute the `docker` command.\n\n```bash\n $ make docker\n```\n\nThis will create a local image for your docker called `agent-docker`.\n\n## Deployment of the agent docker image as a container\n\nTo run a Nano-Agent as a container the following steps are required:\n\n1. If you are using a container management system \u002F plan on deploying the container using your CI, add the agent docker image to an accessible registry.\n2. If you are planning to manage the agent using the open-appsec UI, then make sure to obtain an agent token from the Management Portal and Enforce.\n3. Run the agent with the following command (where -e https_proxy parameter is optional):\n\n`docker run -d --name=agent-container --ipc=host -v=\u003Cpath to persistent location for agent config>:\u002Fetc\u002Fcp\u002Fconf -v=\u003Cpath to persistent location for agent data files>:\u002Fetc\u002Fcp\u002Fdata -v=\u003Cpath to persistent location for agent debugs and logs>:\u002Fvar\u002Flog\u002Fnano_agent -e https_proxy=\u003Cuser:password@Proxy address:port> -e registered_server=\u003Cserver-type> -it \u003Cagent-image> \u002Fcp-nano-agent [--token \u003Ctoken> | --standalone]`\n\nExample:\n```bash\n $ docker run -d --name=agent-container --ipc=host -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fconf:\u002Fetc\u002Fcp\u002Fconf -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fdata:\u002Fetc\u002Fcp\u002Fdata -v=\u002Fhome\u002Fadmin\u002Fagent\u002Flogs:\u002Fvar\u002Flog\u002Fnano_agent –e https_proxy=user:password@1.2.3.4:8080 -e registered_server='nginx' -it agent-docker \u002Fcp-nano-agent --standalone\n $ docker ps\nCONTAINER ID        IMAGE               COMMAND                          CREATED             STATUS              PORTS               NAMES\n1e67f2abbfd4        agent-docker        \"\u002Fcp-nano-agent --hybrid-mode\"   1 minute ago        Up 1 minute                             agent-container\n```\n\n Note that you are not required to use a token from the Management Portal if you are managing your security policy locally. However, you are required to use the --standalone flag in such cases. In addition, the volumes in the command are mandatory only if you wish to have persistency upon restart\u002Fupgrade\u002Fcrash of the agent and its re-execution.\n Lastly, --ipc=host argument is mandatory in order for the agent to have access to shared memory with a protected attachment (NGINX server).\n\n Supported registered_server are: \n - NGINX\n - Kong\n - KongLua\n - APISIX\n - Envoy\n\n4. Create or replace the NGINX container using the [Attachment Repository](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment).\n\nThis will run a docker container using the agent docker image.\n\n# Contributing\nWe welcome everyone that wishes to share their knowledge and expertise to enhance and expand the project.\n\nPlease see the [Contributing Guidelines](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fblob\u002Fmain\u002FCONTRIBUTING.md).\n\n# Security\n\n### Security Audit\nopen-appsec code was audited by an independent third party in September-October 2022.\nSee the [full report](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fblob\u002Fmain\u002FLEXFO-CHP20221014-Report-Code_audit-OPEN-APPSEC-v1.2.pdf).\n\n### Reporting security vulnerabilities\nIf you've found a vulnerability or a potential vulnerability in open-appsec please let us know at security-alert@openappsec.io. We'll send a confirmation email to acknowledge your report within 24 hours, and we'll send an additional email when we've identified the issue positively or negatively.\n\n\n# License\nopen-appsec is open source and available under Apache 2.0 license.\n\nThe basic ML model is open source and available under Apache 2.0 license.\n\nThe advanced ML model is open source and available under Machine Learning Model license, available upon download in the tar file.\n","\u003Cdiv align=center>\n\u003Cimg src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_6de6edeceff0.png\" width=\"100\" height=\"100\"> \n\u003Ch1>openappsec\u002Fopenappsec\u003C\u002Fh1>\n\u003C\u002Fdiv>\n\n[![CII 最佳实践](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_50ccde67b228.png)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F6629)\n\n# 关于\n[open-appsec](https:\u002F\u002Fwww.openappsec.io)（openappsec.io）基于机器学习，提供针对OWASP十大威胁及零日攻击的主动式Web应用和API威胁防护。它可以作为附加组件部署在Linux、Docker或Kubernetes环境中，与NGINX、Kong、APISIX或Envoy集成。\n\nopen-appsec引擎会学习用户通常如何与您的Web应用交互。随后，它利用这些信息自动检测偏离正常操作模式的请求，并进一步分析以判断该请求是否具有恶意性。\n\n每当收到HTTP请求时，系统会对所有部分进行解码，提取JSON和XML内容，并应用IP级别的访问控制。\n\n每个发送到应用的请求都会经历两个阶段：\n\n1. 多个变量会被输入到机器学习引擎中。这些变量或直接从HTTP请求中提取，或从有效载荷的不同部分解码而来，包括攻击指标、IP地址、用户代理、指纹等众多因素。机器学习引擎的监督模型会利用这些变量，将请求与全球范围内常见的多种攻击模式进行比对。\n\n2. 如果请求被认定为合法有效的请求，则允许其通过并转发至您的应用。然而，若请求被视为可疑或高风险，它将进一步由在您特定环境中训练过的无监督模型进行评估。该模型会结合URL及涉及的用户等信息，生成最终置信度评分，以决定是否允许或阻止该请求。\n\n![image](https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_559cb5892f93.png)\n\n\nopen-appsec使用两种机器学习模型：\n\n1. 一种是基于数百万条恶意和良性请求离线训练而成的监督模型。\n    \n    * 本仓库提供一个**基础模型**，建议用于仅监控和测试环境。\n    * 另外还有一个更精确的**高级模型**，**推荐用于生产环境**，可从[open-appsec门户](https:\u002F\u002Fmy.openappsec.io) -> 用户菜单 -> 下载高级ML模型获取。该模型会定期更新，更新时您将收到电子邮件通知。\n\n2. 另一种是无监督模型，它会在受保护的环境中实时构建。此模型会根据特定环境中的流量模式进行学习。\n\n\n# 管理\n\nopen-appsec可以通过多种方式管理：\n* [声明式配置文件](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n* [Kubernetes Helm图表和注解](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n* [使用SaaS Web管理界面](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fusing-the-web-ui-saas)\n\nopen-appsec Web界面：\n\u003Cimg width=\"1854\" height=\"775\" alt=\"image\" src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_1c627fe1884b.png\" \u002F>\n\n\n\n## 部署沙盒（虚拟实验室）\n您可以使用[Playgrounds](https:\u002F\u002Fwww.openappsec.io\u002Fplayground)体验open-appsec。\n\u003Cimg width=\"781\" height=\"878\" alt=\"image\" src=\"https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_readme_1a54d82ab41b.png\" \u002F>\n\n# 资源\n* [项目官网](https:\u002F\u002Fopenappsec.io)\n* [官方文档](https:\u002F\u002Fdocs.openappsec.io\u002F)\n* [视频教程](https:\u002F\u002Fwww.openappsec.io\u002Ftutorials)\n\n# 安装\n\n对于使用Helm的Kubernetes环境（NGINX \u002F Kong \u002F APISIX \u002F Istio）：请参考[文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes)。\n\n对于使用安装程序的Linux环境（NGINX \u002F Kong \u002F APISIX）：支持的预编译NGINX模块列表可在[此处](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fsupported-nginx.txt)找到：\n\n```bash\n$ wget https:\u002F\u002Fdownloads.openappsec.io\u002Fopen-appsec-install && chmod +x open-appsec-install\n$ .\u002Fopen-appsec-install --auto\n```\n\n对于基于Lua的Kong插件，请参考[文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-linux)。\n\n对于自行构建软件包的Linux用户，可使用以下命令：\n\n```bash\n$ install-cp-nano-agent.sh --install --hybrid_mode\n$ install-cp-nano-service-http-transaction-handler.sh --install\n$ install-cp-nano-attachment-registration-manager.sh --install\n```\n\n您可以在第一条命令中添加```--token \u003Ctoken>```、```--email \u003Cemail address>```以及```registered_server```选项。如需获取令牌，请参阅[文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fusing-the-web-ui-saas\u002Fconnect-deployed-agents-to-saas-management-k8s-and-linux)。\n\n对于Docker环境：请参考[文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-docker)。\n\n如需更多信息，请阅读[文档](https:\u002F\u002Fdocs.openappsec.io\u002F)或观看[视频教程](https:\u002F\u002Fwww.openappsec.io\u002Ftutorials)。\n\n# 仓库\nopen-appsec GitHub包含四个主要仓库：\n\n* [openappsec\u002Fopenappsec](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec)：open-appsec的核心代码和逻辑，采用C++开发。\n* [openappsec\u002Fattachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment)：负责连接提供HTTP数据的进程（例如NGINX）与open-appsec Agent安全逻辑，采用C语言开发。\n* [openappsec\u002Fsmartsync](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fsmartsync)：负责关联来自多个Agent实例的学习数据，并为每个资产生成统一的学习模型，采用Golang开发。\n* [openappsec\u002Fsmartsync-shared-files](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fsmartsync-shared-files)：smartsync服务用于存储学习数据的物理存储接口，同样采用Golang开发。\n\n# 编译说明\n\n## 安装外部依赖\n在编译服务之前，您需要确保已安装以下库和工具的最新开发版本：\n* Boost\n* OpenSSL\n* PCRE2\n* libxml2\n* GTest\n* GMock\n* cURL\n* Redis\n* Hiredis\n* MaxmindDB\n* yq\n\n以下是在Alpine系统上安装这些软件包的示例：\n\n```bash\n $ apk update\n $ apk add boost-dev openssl-dev pcre2-dev libxml2-dev gtest-dev curl-dev hiredis-dev redis libmaxminddb-dev yq\n```\n\n## 编译并打包Agent代码\n1. 克隆本仓库\n2. 运行CMake命令\n3. 执行make install命令\n\n```bash\n $ git clone https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec.git\n $ cd openappsec\u002F\n $ cmake -DCMAKE_INSTALL_PREFIX=build_out .\n $ make install\n $ make package\n```\n\n## 将代理代码放入 Alpine Docker 镜像中\n\n在编译并打包好代理代码后，可以创建一个运行该代码的 Alpine 镜像。这需要具有执行 `docker` 命令的权限。\n\n```bash\n $ make docker\n```\n\n这将为您的 Docker 创建一个名为 `agent-docker` 的本地镜像。\n\n## 将代理 Docker 镜像部署为容器\n\n要以容器形式运行 Nano-Agent，需执行以下步骤：\n\n1. 如果您正在使用容器管理系统，或计划通过 CI 部署容器，请将代理 Docker 镜像添加到可访问的注册表中。\n2. 如果您计划使用 open-appsec UI 来管理代理，请确保从 Management Portal 和 Enforce 中获取代理令牌。\n3. 使用以下命令运行代理（其中 `-e https_proxy` 参数为可选）：\n\n`docker run -d --name=agent-container --ipc=host -v=\u003C代理配置持久化路径>:\u002Fetc\u002Fcp\u002Fconf -v=\u003C代理数据文件持久化路径>:\u002Fetc\u002Fcp\u002Fdata -v=\u003C代理调试和日志持久化路径>:\u002Fvar\u002Flog\u002Fnano_agent -e https_proxy=\u003Cuser:password@代理地址:端口> -e registered_server=\u003C服务器类型> -it \u003C代理镜像> \u002Fcp-nano-agent [--token \u003C令牌> | --standalone]`\n\n示例：\n```bash\n $ docker run -d --name=agent-container --ipc=host -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fconf:\u002Fetc\u002Fcp\u002Fconf -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fdata:\u002Fetc\u002Fcp\u002Fdata -v=\u002Fhome\u002Fadmin\u002Fagent\u002Flogs:\u002Fvar\u002Flog\u002Fnano_agent –e https_proxy=user:password@1.2.3.4:8080 -e registered_server='nginx' -it agent-docker \u002Fcp-nano-agent --standalone\n $ docker ps\nCONTAINER ID        IMAGE               COMMAND                          CREATED             STATUS              PORTS               NAMES\n1e67f2abbfd4        agent-docker        \"\u002Fcp-nano-agent --hybrid-mode\"   1 minute ago        Up 1 minute                             agent-container\n```\n\n请注意，如果您在本地管理安全策略，则无需使用来自 Management Portal 的令牌。但在这种情况下，必须使用 `--standalone` 标志。此外，命令中的卷挂载仅在您希望代理在重启、升级或崩溃后重新启动时保持数据持久性时才为必选项。\n\n最后，`--ipc=host` 参数是必需的，以便代理能够与受保护的应用程序（例如 NGINX 服务器）共享内存。\n\n支持的 `registered_server` 类型包括：\n- NGINX\n- Kong\n- KongLua\n- APISIX\n- Envoy\n\n4. 使用 [Attachment Repository](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment) 创建或替换 NGINX 容器。\n\n这将使用代理 Docker 镜像运行一个 Docker 容器。\n\n# 贡献\n我们欢迎所有希望分享知识和专长以改进和扩展该项目的人士。\n\n请参阅[贡献指南](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fblob\u002Fmain\u002FCONTRIBUTING.md)。\n\n# 安全\n### 安全审计\nopen-appsec 代码于 2022 年 9 月至 10 月由独立第三方进行了安全审计。\n请参阅[完整报告](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fblob\u002Fmain\u002FLEXFO-CHP20221014-Report-Code_audit-OPEN-APPSEC-v1.2.pdf)。\n\n### 报告安全漏洞\n如果您发现 open-appsec 中存在漏洞或潜在漏洞，请通过 security-alert@openappsec.io 告知我们。我们将在 24 小时内发送确认邮件以确认收到您的报告，并在确认或否定问题后再次发送邮件。\n\n\n# 许可证\nopen-appsec 是开源项目，采用 Apache 2.0 许可证。\n\n基础机器学习模型也是开源的，采用 Apache 2.0 许可证。\n\n高级机器学习模型同样是开源的，采用机器学习模型许可证，可在 tar 文件中下载获得。","# openappsec 快速上手指南\n\nopenappsec 是一款基于机器学习的开源 Web 应用及 API 安全防护工具，能够防御 OWASP Top 10 及零日攻击。它支持以插件形式部署在 Linux、Docker 或 Kubernetes 环境中，兼容 NGINX、Kong、APISIX 和 Envoy 等网关。\n\n## 环境准备\n\n### 系统要求\n- **操作系统**: Linux (推荐 Alpine, Ubuntu, CentOS)\n- **容器环境**: Docker 或 Kubernetes (可选)\n- **支持的网关**: NGINX, Kong, APISIX, Envoy, Istio\n\n### 前置依赖\n若需从源码编译，请确保安装以下开发库的最新版本：\n- Boost, OpenSSL, PCRE2, libxml2\n- GTest, GMock, cURL, Redis, Hiredis\n- MaxmindDB, yq\n\n**Alpine 系统安装示例：**\n```bash\n$ apk update\n$ apk add boost-dev openssl-dev pcre2-dev libxml2-dev gtest-dev curl-dev hiredis-dev redis libmaxminddb-dev yq\n```\n\n## 安装步骤\n\n根据部署环境选择以下一种方式：\n\n### 方式一：Linux 自动安装（推荐）\n适用于已预编译支持的 NGINX\u002FKong\u002FAPISIX 环境。\n\n```bash\n$ wget https:\u002F\u002Fdownloads.openappsec.io\u002Fopen-appsec-install && chmod +x open-appsec-install\n$ .\u002Fopen-appsec-install --auto\n```\n*注：如需连接 SaaS 管理平台，可在命令后添加 `--token \u003Ctoken>` 和 `--email \u003Cemail address>` 参数。*\n\n### 方式二：Kubernetes 部署\n使用 Helm Chart 进行部署（支持 NGINX Ingress, Kong, APISIX, Istio）。\n请参考官方文档执行 Helm 安装命令：\n[https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes)\n\n### 方式三：Docker 容器部署\n若已自行编译打包，可构建并运行 Docker 容器。\n\n1. **构建镜像**\n```bash\n$ make docker\n```\n这将生成名为 `agent-docker` 的本地镜像。\n\n2. **运行容器**\n```bash\n$ docker run -d --name=agent-container --ipc=host -v=\u003Cpath to persistent location for agent config>:\u002Fetc\u002Fcp\u002Fconf -v=\u003Cpath to persistent location for agent data files>:\u002Fetc\u002Fcp\u002Fdata -v=\u003Cpath to persistent location for agent debugs and logs>:\u002Fvar\u002Flog\u002Fnano_agent -e https_proxy=\u003Cuser:password@Proxy address:port> -e registered_server=\u003Cserver-type> -it \u003Cagent-image> \u002Fcp-nano-agent [--token \u003Ctoken> | --standalone]\n```\n\n**运行示例（ standalone 模式）：**\n```bash\n$ docker run -d --name=agent-container --ipc=host -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fconf:\u002Fetc\u002Fcp\u002Fconf -v=\u002Fhome\u002Fadmin\u002Fagent\u002Fdata:\u002Fetc\u002Fcp\u002Fdata -v=\u002Fhome\u002Fadmin\u002Fagent\u002Flogs:\u002Fvar\u002Flog\u002Fnano_agent –e https_proxy=user:password@1.2.3.4:8080 -e registered_server='nginx' -it agent-docker \u002Fcp-nano-agent --standalone\n```\n*注意：`--ipc=host` 参数是必须的，以便代理访问共享内存；`registered_server` 支持 NGINX, Kong, KongLua, APISIX, Envoy。*\n\n## 基本使用\n\n安装完成后，openappsec 将自动开始学习流量模式。其工作流程如下：\n\n1. **自动学习**：引擎分析传入的 HTTP 请求（包括解码 JSON\u002FXML），提取变量（如攻击指标、IP、User-Agent 等）。\n2. **双重检测**：\n   - **监督模型**：对比全球已知攻击模式进行初步筛选。\n   - **无监督模型**：针对当前环境特有的流量模式进行二次评估，生成置信度评分。\n3. **决策执行**：合法请求被放行，高风险请求将被拦截。\n\n### 管理配置\n您可以通过以下方式管理策略：\n- **声明式配置文件**：直接编辑本地配置。\n- **SaaS Web UI**：登录 [open-appsec Portal](https:\u002F\u002Fmy.openappsec.io) 查看实时威胁仪表盘、下载高级机器学习模型或管理分布式节点。\n- **Kubernetes Annotations**：通过 K8s 注解动态调整策略。\n\n### 获取高级模型（生产环境推荐）\n基础模型适用于测试环境。生产环境建议登录门户下载更精准的高级模型：\n1. 访问 [open-appsec Portal](https:\u002F\u002Fmy.openappsec.io)\n2. 进入 User Menu -> Download advanced ML model\n3. 将下载的模型部署至相应目录，系统将自动更新。\n\n更多详细配置与视频教程请访问 [官方文档](https:\u002F\u002Fdocs.openappsec.io\u002F)。","某电商平台的运维团队在“黑色星期五”大促期间，面临海量 API 请求下的安全防护挑战，需确保订单系统不被恶意攻击瘫痪。\n\n### 没有 openappsec 时\n- **规则维护滞后**：依赖传统 WAF 的正则规则库，无法及时识别新型零日攻击（Zero-day），往往在漏洞爆发后才被动更新特征库。\n- **误报率高影响业务**：僵硬的匹配规则常将正常的促销爬虫或复杂参数请求误判为攻击，导致真实用户下单失败，造成直接营收损失。\n- **响应速度缓慢**：安全团队需人工分析日志并手动调整策略，从发现异常到完成拦截通常有数小时延迟，错失最佳防御窗口。\n- **部署耦合度高**：每次升级防护逻辑都需要重启网关服务或修改核心配置文件，在大促高峰期不敢轻易变动，风险敞口大。\n\n### 使用 openappsec 后\n- **智能预判未知威胁**：openappsec 利用监督学习模型自动比对全球攻击模式，无需更新规则即可实时阻断未知的 OWASP Top 10 及零日攻击。\n- **动态基线降低误报**：其无监督学习模型实时学习该平台特有的流量行为，精准区分正常促销流量与恶意扫描，保障合法请求畅通无阻。\n- **毫秒级自动防御**：每个请求经过双重模型评估，一旦判定为高风险立即自动拦截，将响应时间从小时级缩短至毫秒级，实现全天候无人值守防护。\n- **无缝热部署集成**：作为 NGINX 或 K8s 的插件平滑接入，更新机器学习模型无需重启服务，确保大促期间业务连续性与安全性兼得。\n\nopenappsec 通过机器学习引擎将被动防御转变为主动预判，在零干扰业务的前提下为 Web 应用构建了自适应的智能化安全屏障。","https:\u002F\u002Foss.gittoolsai.com\u002Fimages\u002Fopenappsec_openappsec_1c627fe1.png","https:\u002F\u002Foss.gittoolsai.com\u002Favatars\u002Fopenappsec_a7429af0.png","open-appsec builds on machine learning to provide pre-emptive web app & API threat protection against OWASP-Top-10 and  zero-day attacks.",null,"https:\u002F\u002Fopenappsec.io","https:\u002F\u002Fgithub.com\u002Fopenappsec",[82,86,90,94,98,102,106,110],{"name":83,"color":84,"percentage":85},"C++","#f34b7d",88.7,{"name":87,"color":88,"percentage":89},"Shell","#89e051",4.7,{"name":91,"color":92,"percentage":93},"Mustache","#724b3b",2.7,{"name":95,"color":96,"percentage":97},"C","#555555",2.3,{"name":99,"color":100,"percentage":101},"CMake","#DA3434",1.1,{"name":103,"color":104,"percentage":105},"Python","#3572A5",0.6,{"name":107,"color":108,"percentage":109},"Go Template","#00ADD8",0.1,{"name":111,"color":112,"percentage":113},"Dockerfile","#384d54",0,1593,119,"2026-04-19T06:27:31","Apache-2.0",3,"Linux","未说明",{"notes":122,"python":120,"dependencies":123},"该工具核心引擎由 C++ 开发，附件（Attachment）由 C 开发，同步服务（Smartsync）由 Golang 开发，非 Python 项目。支持部署在 Linux、Docker 或 Kubernetes 环境中，作为 NGINX、Kong、APISIX 或 Envoy 的插件运行。编译前需安装指定的开发库（如 boost-dev, openssl-dev 等）。运行时若与受保护的附件（如 NGINX）共享内存，Docker 容器必须添加 '--ipc=host' 参数。机器学习模型分为开源的基础模型（适用于测试）和需下载的高级模型（适用于生产）。",[124,125,126,127,128,129,130,131,132,133],"Boost","OpenSSL","PCRE2","libxml2","GTest","GMock","cURL","Redis","Hiredis","MaxmindDB",[14],[136,137,138,139,140,141,142,143,144,145,146,147,148,149,150],"api-security","application-security","kubernetes","nginx","web-application-firewall","appsec","devsecops","kong","rate-limiting","security-tools","threat-prevention","waf","owasp","owasp-top-ten","nginx-proxy-manager","2026-03-27T02:49:30.150509","2026-04-20T04:04:10.685737",[154,159,164,169,174,178],{"id":155,"question_zh":156,"answer_zh":157,"source_url":158},43908,"如何在 ARM64 架构（如 AWS c7g 实例或 Ubuntu ARM）上编译 open-appsec？","可以在 ARM64 Ubuntu 24 上通过安装必要的依赖包进行编译。具体步骤如下：\n1. 更新包列表：sudo apt update\n2. 安装依赖：sudo apt install -y libboost-dev libssl-dev libpcre2-dev libxml2-dev libgtest-dev libcurl4-openssl-dev libhiredis-dev redis libmaxminddb-dev yq cmake build-essential zlib1g-dev libgmock-dev libboost-regex-dev libboost-context-dev libboost-filesystem-dev\n3. 在拥有 16GB 磁盘的 fresh c7g.xlarge AWS 实例上，编译过程大约需要 40 分钟。\n注意：'make package' 步骤可能会失败，因为它可能使用了 x86 平台的库或工具，目前尚无官方变通方案。","https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fissues\u002F19",{"id":160,"question_zh":161,"answer_zh":162,"source_url":163},43909,"Docker 或 Linux 版本启动后显示 'Policy load status: Error' 怎么办？","该问题在 CentOS 7 上已被确认，并在新版本（1.1.29）中修复。请尝试重新安装最新版本。\n如果问题依旧存在，可以尝试手动加载策略并收集日志供进一步分析：\n1. 运行命令加载策略：open-appsec-ctl --apply-policy\n2. 运行命令生成诊断包：open-appsec-ctl --info\n生成的 tar 文件路径会在脚本末尾显示，请将该文件发送至 info@openappsec.io 以便团队调查。","https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fissues\u002F332",{"id":165,"question_zh":166,"answer_zh":167,"source_url":168},43910,"SaaS 仪表板上的策略无法下载到本地，日志显示下载失败或网络错误，如何解决？","此类错误通常指示网络连接问题。建议采取以下步骤：\n1. 检查容器或主机的网络配置，确保能访问外网。\n2. 尝试从头开始重新创建环境（recreate everything from scratch），这有时能解决间歇性错误。\n3. 如果问题持续，可能需要联系支持团队进行远程会话排查。","https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fissues\u002F356",{"id":170,"question_zh":171,"answer_zh":172,"source_url":173},43911,"为什么在没有流量（空闲状态）时，open-appsec agent 的 CPU 占用率依然很高？","用户报告在空闲状态下（无流量），agent 进程（如 cp-nano-orchest, cp-nano-http-tr）仍占用显著 CPU（例如 30%）。维护者已确认该问题并在后续版本中进行了改进。如果您使用的是旧版本（如 1.1.14 或更早），请升级到最新版本以获取性能优化。如果升级后问题仍然存在，建议提供 top 命令截图和版本信息给开发团队。","https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fissues\u002F119",{"id":175,"question_zh":176,"answer_zh":177,"source_url":163},43912,"安装脚本下载失败或连接到 downloads.openappsec.io 超时怎么办？","如果在运行安装脚本（wget https:\u002F\u002Fdownloads.openappsec.io\u002Fopen-appsec-install）时遇到连接问题或 DNS 解析延迟，可能是网络波动或防火墙限制。建议：\n1. 检查服务器是否能 ping 通 downloads.openappsec.io。\n2. 确认没有代理设置阻碍连接，或者正确配置 https_proxy 环境变量。\n3. 稍后重试，因为服务端 IP 可能有多个（如 54.192.95.2 等），网络路由可能暂时不稳定。",{"id":179,"question_zh":180,"answer_zh":181,"source_url":163},43913,"如何验证 open-appsec agent 是否成功加载了策略？","可以通过以下命令检查策略加载状态：\n1. 进入容器或终端执行：open-appsec-ctl --status\n2. 查看输出中的 'Policy load status' 字段。如果显示 'Success' 则表示正常；如果显示 'Error'，则需参考相关故障排除步骤（如手动应用策略或检查日志）。\n此外，确保配置文件路径正确挂载（如 \u002Fetc\u002Fcp\u002Fconf\u002Flocal_policy.yaml），并且文件格式符合官方示例。",[183,188,193,198,203,208,213,218,223,228,233,238,243,248,253,258,263,268,273,278],{"id":184,"version":185,"summary_zh":186,"released_at":187},351360,"v1.1.3","# Added ⭐ \r\n- Option to prevent upgrade in docker, using the no-upgrade flag\r\n- Profile ID to open-appsec-ctl --status output\r\n- Adding Token to Docker Deployment can be done with AGENT_TOKEN environment variable, allowing to redeploy dockers with the same volumes. \r\n- standalone flag is no longer needed in Docker deployments.\r\n- adding node selector to learning deployment (#127) \r\n# Fixed :lady_beetle:\r\n-  Various bug fixes and improvements \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.12...1.1.13\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.13](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fagent\u002Fpkgs\u002Fcontainer\u002Fagent)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.4.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-latest.tgz)\r\n- [Helm chart open-appsec for Kong based on version 3.6](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-latest.tgz)","2024-07-02T13:04:42",{"id":189,"version":190,"summary_zh":191,"released_at":192},351361,"1.1.12","# Fixed :lady_beetle:\r\n-  Various bug fixes and improvements \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.11...1.1.12\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.12](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fagent\u002Fpkgs\u002Fcontainer\u002Fagent)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.4.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-latest.tgz)\r\n- [Helm chart open-appsec for Kong based on version 3.6](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-latest.tgz)","2024-06-27T08:08:11",{"id":194,"version":195,"summary_zh":196,"released_at":197},351342,"1.1.33","# 新增 ⭐ \n- 支持 Debian Buster 和 Trixie #342 \n# 修复 🐞 \n- Kong Lua 插件部署相关问题 #346 \n- 通用性错误修复\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.32...1.1.33\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理 1.1.33 版本](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec 代理 1.1.33 版本，与 NGINX 1.25.0 集成版](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- 所有相关容器的列表可在此查看：[这里](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages)。\n## Helm Chart :hammer:\n- [Helm 仓库](https:\u002F\u002Fcharts.openappsec.io)","2026-01-20T13:18:57",{"id":199,"version":200,"summary_zh":201,"released_at":202},351343,"1.1.32","# 新增 ⭐ \n- 声明式模式下的 Prometheus 支持，详情请见 [这里](https:\u002F\u002Fdocs.openappsec.io\u002Fprometheus)\n# 修复 🐞 \n- Docker Compose PostgreSQL 问题 #361 \n- Kubernetes 中的声明式策略问题 #370 \n- Agent 在收到 SIGTERM 信号时无法退出。\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.30...1.1.32\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec Agent 版本 1.1.32](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec Agent 版本 1.1.32，与 NGINX 1.25.0 集成](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- 所有相关容器镜像列表可在此查看：[这里](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages)。\n## Helm Chart :hammer:\n- [Helm 仓库](https:\u002F\u002Fcharts.openappsec.io)","2025-11-26T11:39:39",{"id":204,"version":205,"summary_zh":206,"released_at":207},351344,"1.1.30","# 已修复 🐞 \n- Content-Encoding WAF 欺骗问题 #353 \n- CVE-2025-59375 漏洞 #349 \n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.29...1.1.30\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.30](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec 代理版本 1.1.30，与 NGINX 1.25.0 集成](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- 所有附件容器的列表可以在这里找到：[这里](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages)。\n## Helm Chart :hammer:\n- [Helm 仓库](https:\u002F\u002Fcharts.openappsec.io)","2025-10-08T12:04:27",{"id":209,"version":210,"summary_zh":211,"released_at":212},351345,"1.1.29","# 新增🌟\n- 对 Kong Lua 插件的 Beta 支持，更多信息请参阅我们的[博客文章](https:\u002F\u002Fwww.openappsec.io\u002Fpost\u002Fintroducing-open-appsec-machine-learning-driven-waf-for-kong-gateway-featuring-a-new-flexible-lu)。\n- 各种问题修复和错误修正。\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.27...1.1.29\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.29](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec 代理版本 1.1.29，与 NGINX 1.25.0 集成](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- 所有附件容器的列表可在此处查看：[这里](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages)。\n## Helm Chart :hammer:\n- [Helm 仓库](https:\u002F\u002Fcharts.openappsec.io)","2025-08-12T08:25:52",{"id":214,"version":215,"summary_zh":216,"released_at":217},351346,"1.1.27","# 新增🌟\n- Istio 的 Beta 支持：您现在可以在 Kubernetes 上将 open-appsec 部署并集成到现有的 Istio Ingress Gateway 部署中。[了解详情](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes\u002Finstall-using-helm-istio)。\n# 修复 :lady_beetle:\n- 各种问题和错误修复。\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.26...1.1.27\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.27](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [与 NGINX 1.25.0 统一的 open-appsec 代理版本 1.1.27](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- [带有 open-appsec 附件的 NGINX Ingress Controller 版本 1.12.1](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \n- [带有 open-appsec 附件的 NGINX 版本 1.25.4](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\n- [带有 open-appsec 附件的 NGINX 代理管理器版本 v2.12.3](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\n- [带有 open-appsec 附件的 Kong 网关版本 3.4.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\n- [带有 open-appsec 附件的 Kong 版本 3.7.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\n## Helm Charts :hammer:\n- [Helm 仓库](https:\u002F\u002Fcharts.openappsec.io)","2025-06-30T11:55:24",{"id":219,"version":220,"summary_zh":221,"released_at":222},351347,"1.1.26","# 新增🌟\n- Helm 仓库支持——open-appsec Chart 现可通过 https:\u002F\u002Fcharts.openappsec.io 获取。[请参阅文档中的安装说明。](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes\u002Finstall-using-helm-new-flow-beta)\n- Prometheus 集成（Beta）——初步支持将 open-appsec 指标导出至 Prometheus，更多信息请见 [此处](https:\u002F\u002Fdocs.openappsec.io\u002Fprometheus)。\n- NGINX Proxy Manager——已升级至最新版本。\n# 修复 :lady_beetle:\n- 解决了导致 Agent 容器意外重启的问题。\n- 修复了 IPv6 CIDR 计算中的一个 bug ([#288](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopen-appsec\u002Fissues\u002F288))。\n## 链接 :pushpin:\n- **完整变更日志**：https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopen-appsec\u002Fcompare\u002F1.1.25...1.1.26\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec Agent 版本 1.1.26](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec Agent 版本 1.1.26 与 NGINX 1.25.0 集成版](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- [带有 open-appsec 插件的 NGINX Ingress Controller 版本 1.12.1](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \n- [带有 open-appsec 插件的 NGINX 版本 1.25.4](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\n- [带有 open-appsec 插件的 NGINX Proxy Manager 版本 v2.12.3](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\n- [带有 open-appsec 插件的 Kong Gateway 版本 3.4.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\n- [带有 open-appsec 插件的 Kong 版本 3.7.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\n## Helm Charts :hammer:\n- [适用于 NGINX Ingress Controller 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.26.tgz)\n- [适用于 Kong 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.26.tgz)\n- [适用于 APISIX 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-1.1.26.tgz)","2025-06-17T08:04:51",{"id":224,"version":225,"summary_zh":226,"released_at":227},351348,"1.1.25","# 修复 :lady_beetle:\n- 各种错误修复和改进\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.24...1.1.25\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.25](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [与 NGINX 1.25.0 集成的 open-appsec 代理版本 1.1.25](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- [带有 open-appsec 附件的 NGINX Ingress 控制器版本 1.12.1](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \n- [带有 open-appsec 附件的 NGINX 版本 1.25.4](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\n- [带有 open-appsec 附件的 NGINX 代理管理器版本 v2.12.1](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\n- [带有 open-appsec 附件的 Kong 网关版本 3.4.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\n- [带有 open-appsec 附件的 Kong 版本 3.7.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\n## Helm Chart :hammer:\n- [适用于 NGINX Ingress 控制器的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.25tgz)\n- [适用于 Kong 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.25.tgz)\n- [适用于 APISIX 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-1.1.25.tgz)","2025-04-24T07:50:45",{"id":229,"version":230,"summary_zh":231,"released_at":232},351349,"1.1.24","# 已修复 :lady_beetle:\n-  ✏️ 【2025年3月25日更新】发布了一个新的 NGINX Ingress 控制器 Helm 图表，以修复 NGINX 中的一个安全漏洞，详情请见[此处](https:\u002F\u002Fwww.openappsec.io\u002Fpost\u002Fremediation-for-ingress-nginx-controller-vulnerability)。\n- 各种错误修复和改进\n## 链接 :pushpin:\n- **完整变更日志**：https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.23...1.1.24\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.24](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec 代理版本 1.1.24，与 NGINX 版本 1.24.0 统一](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- [NGINX Ingress 控制器版本 1.21.1，附带 open-appsec 插件](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \n- [NGINX 版本 1.25.4，附带 open-appsec 插件](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\n- [NGINX 代理管理器版本 v2.12.1，附带 open-appsec 插件](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\n- [Kong 网关版本 3.4.0，附带 open-appsec 插件](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\n- [Kong 版本 3.7.0，附带 open-appsec 插件](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\n## Helm 图表 :hammer:\n- [适用于 NGINX Ingress 控制器的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.24tgz)\n- [适用于 Kong 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.24.tgz)\n- [适用于 APISIX 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-1.1.24.tgz)","2025-03-24T11:57:01",{"id":234,"version":235,"summary_zh":236,"released_at":237},351350,"1.1.23","# 🚀 新增\n- open-appsec Web UI 管理更新，包括改进的 WAF 实践以及合并 Web 应用和 Web API 资产。\n# :lady_beetle: 修复\n- 各种错误修复和改进\n## 链接 :pushpin:\n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.22...1.1.23\n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\n## 容器 :gift:\n- [open-appsec 代理版本 1.1.23](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\n- [open-appsec 代理版本 1.1.23 与 NGINX 1.24.0 统一版](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\n- [带有 open-appsec 附件的 NGINX Ingress Controller 版本 1.25.3](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \n- [带有 open-appsec 附件的 NGINX 版本 1.25.4](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\n- [带有 open-appsec 附件的 NGINX Proxy Manager 版本 v2.12.1](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\n- [带有 open-appsec 附件的 Kong Gateway 版本 3.4.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\n- [带有 open-appsec 附件的 Kong 版本 3.7.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\n## Helm Charts :hammer:\n- [适用于 NGINX Ingress Controller 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.23tgz)\n- [适用于 Kong 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.23.tgz)\n- [适用于 APISIX 的 open-appsec](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-1.1.23.tgz)","2025-03-03T14:06:13",{"id":239,"version":240,"summary_zh":241,"released_at":242},351351,"1.1.22","# 🚀 新增  \n\n- **Envoy 在 Docker 上的 Beta 支持** – 现已可用！有关集成的更多信息，请参阅[此处](https:\u002F\u002Fwww.openappsec.io\u002Fpost\u002Fopen-appsec-integration-with-envoy-proxy-docker-now-available-in-beta)。  \n- **v1beta2 CRD 和本地配置的 Beta 版本** – 在与 Web UI 保持一致的同时，支持 open-appsec 的完整本地配置。了解详情[请见此处](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-kubernetes\u002Fconfiguration-using-crds-v1beta2)。  \n\n# :lady_beetle: 修复  \n- 解决了一个问题：在特定情况下，当启用 open-appsec 附件时，Nginx 中加载的其他模块可能无法正常工作。  \n  - 如果您正在容器化平台（Docker、K8s）上部署 open-appsec，请务必更新到最新的容器镜像。  \n\n## 链接 :pushpin:  \n- **完整变更日志**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.21...1.1.22  \n    - [open-appsec 文档](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)  \n\n## 容器 :gift:  \n- [open-appsec 代理版本 1.1.22](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)  \n- [open-appsec 代理版本 1.1.22，与 Nginx 1.24.0 统一](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)  \n- [带有 open-appsec 附件的 Nginx Ingress Controller 版本 1.25.3](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment)  \n- [带有 open-appsec 附件的 Nginx 版本 1.25.4](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)  \n- [带有 open-appsec 附件的 Nginx Proxy Manager 版本 v2.12.1](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)  \n- [带有 open-appsec 附件的 Kong Gateway 版本 3.4.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)  \n- [带有 open-appsec 附件的 Kong 版本 3.7.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)  \n\n## Helm :hammer:  \n- [适用于 Nginx Ingress Controller 的 open-appsec Helm Chart](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.22tgz)  \n- [适用于 Kong 的 open-appsec Helm Chart](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.22.tgz)  \n- [适用于 APISIX 的 open-appsec Helm Chart](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-1.1.22.tgz)","2025-02-19T14:17:46",{"id":244,"version":245,"summary_zh":246,"released_at":247},351352,"1.1.21","# Added ⭐ \r\n- docker-compose files added for all deployments, read more [here](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-docker\u002Fdeploy-with-docker-compose-beta).\r\n- Geo-Location Rule for Rate Limiting: Tailor your security policies with greater precision by applying rate limits based on the geographic origin of incoming traffic.\r\n- Custom Rules and Exceptions by Practice: Simplify rule management by selecting practices per rule, making it easier to share and reuse exceptions across multiple assets\r\n# Fixed :lady_beetle:\r\n- issue in helm #219 \r\n- Performance improvement fix in docker. \r\n- Various bugs fixes and improvements \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.20...1.1.21\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.21](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\r\n- [open-appsec agent version 1.1.21 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.12.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.21tgz)\r\n- [Helm chart open-appsec for Kong](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.21.tgz)\r\n- [Helm Chart open-appsec for APISIX](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-latest.tgz)","2025-01-21T13:48:21",{"id":249,"version":250,"summary_zh":251,"released_at":252},351353,"1.1.20","# Added ⭐ \r\n- New Advanced Machine Learning model, you can read more on how to deploy it [here](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fusing-the-advanced-machine-learning-model).\r\n# Fixed :lady_beetle:\r\n- Various bugs fixes and improvements \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.19...1.1.120\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.20](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\r\n- [open-appsec agent version 1.1.20 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.20tgz)\r\n- [Helm chart open-appsec for Kong](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.20.tgz)\r\n- [Helm Chart open-appsec for APISIX](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fapisix\u002Fopen-appsec-k8s-apisix-latest.tgz)","2024-12-02T09:20:40",{"id":254,"version":255,"summary_zh":256,"released_at":257},351354,"1.1.19","# Added ⭐ \r\n- Apache APISIX API Gateway support, read more [here](https:\u002F\u002Fwww.openappsec.io\u002Fpost\u002Fannouncing-open-appsec-waf-integration-with-apache-apisix-api-gateway)\r\n# Fixed :lady_beetle:\r\n-  Error Messages in  \u002Fvar\u002Flog\u002Fnano_agent\u002Fk8s-log-file-handler.sh.err #194 \r\n-  Issue with exceptions in local policy #138 \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.18...1.1.19\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.19](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\r\n- [open-appsec agent version 1.1.19 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.19.tgz)\r\n- [Helm chart open-appsec for Kong based on version 2.41.1](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.19.tgz)","2024-11-10T14:38:26",{"id":259,"version":260,"summary_zh":261,"released_at":262},351355,"1.1.18","# Fixed :lady_beetle:\r\n-  Various bug fixes and improvements \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.17...1.1.18\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.18](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\r\n- [open-appsec agent version 1.1.18 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.18.tgz)\r\n- [Helm chart open-appsec for Kong based on version 2.41.1](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.17.tgz)","2024-10-13T12:42:53",{"id":264,"version":265,"summary_zh":266,"released_at":267},351356,"1.1.17","# Fixed :lady_beetle:\r\n- Issue with persisting agent ID in docker #159 \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.16...1.1.17\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.17](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent)\r\n- [open-appsec agent version 1.1.17 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.17.tgz)\r\n- [Helm chart open-appsec for Kong based on version 2.41.1](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.17.tgz)","2024-09-24T08:17:29",{"id":269,"version":270,"summary_zh":271,"released_at":272},351357,"1.1.16","# Fixed :lady_beetle:\r\n- Issue with Installing REHL 9.3 & 9.4 (#152)\r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.16...1.1.15\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.16](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fagent\u002Fpkgs\u002Fcontainer\u002Fagent)\r\n- [open-appsec agent version 1.1.16 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.7.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.16.tgz)\r\n- [Helm chart open-appsec for Kong based on version 3.6](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.16.tgz)","2024-08-28T07:53:09",{"id":274,"version":275,"summary_zh":276,"released_at":277},351358,"1.1.15","# Added ⭐ \r\n- Added a deployment option: open-appsec unified with NGINX, read more [here](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fstart-with-docker). \r\n- Support for declarative mode in Docker. \r\n# Fixed :lady_beetle:\r\n- Various bug fixes and improvements.\r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.14...1.1.15\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.15](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fagent\u002Fpkgs\u002Fcontainer\u002Fagent)\r\n- [open-appsec agent version 1.1.15 unified with NGINX version 1.24.0](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fagent-unified)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.4.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-1.1.15.tgz)\r\n- [Helm chart open-appsec for Kong based on version 3.6](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-1.1.15.tgz)","2024-08-01T10:40:06",{"id":279,"version":280,"summary_zh":281,"released_at":282},351359,"1.1.14","# Fixed :lady_beetle:\r\n-  removed unneeded logging to systemd #63 \r\n## Links :pushpin:\r\n- **Full Changelog**: https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fopenappsec\u002Fcompare\u002F1.1.13...1.1.14\r\n- [open-appsec documentation](https:\u002F\u002Fdocs.openappsec.io\u002Fgetting-started\u002Fgetting-started)\r\n## Containers :gift:\r\n- [open-appsec agent version 1.1.14](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fagent\u002Fpkgs\u002Fcontainer\u002Fagent)\r\n- [NGINX ingress controller version 1.25.3 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Fopenappsec\u002Fattachment\u002Fpkgs\u002Fcontainer\u002Fnginx-ingress-attachment) \r\n- [NGINX version 1.25.4 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-attachment)\r\n- [NGINX Proxy Manager version v2.11.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fnginx-proxy-manager-attachment)\r\n- [Kong gateway version 3.4.0 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-gateway-attachment)\r\n- [Kong version 3.4.1 with open-appsec attachment](https:\u002F\u002Fgithub.com\u002Forgs\u002Fopenappsec\u002Fpackages\u002Fcontainer\u002Fpackage\u002Fkong-attachment)\r\n## Helm :hammer:\r\n- [Helm chart open-appsec for NGINX Ingress Controller based on version 4.10.0](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fnginx-ingress\u002Fopen-appsec-k8s-nginx-ingress-latest.tgz)\r\n- [Helm chart open-appsec for Kong based on version 3.6](https:\u002F\u002Fdownloads.openappsec.io\u002Fpackages\u002Fhelm-charts\u002Fkong\u002Fopen-appsec-k8s-kong-latest.tgz)","2024-07-08T07:16:22"]