This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new 940b14c1d5a [INLONG-1186][Doc] Update security doc (#1187)
940b14c1d5a is described below
commit 940b14c1d5a246b6adcf03b80bcf4b742989d098
Author: fuweng11 <[email protected]>
AuthorDate: Tue Jun 30 20:36:46 2026 +0800
[INLONG-1186][Doc] Update security doc (#1187)
---
docs/security.md | 7 ++++++-
i18n/zh-CN/docusaurus-plugin-content-docs/current/security.md | 7 ++++++-
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/docs/security.md b/docs/security.md
index 1cb6f172948..636c19ff679 100644
--- a/docs/security.md
+++ b/docs/security.md
@@ -16,5 +16,10 @@ The security mailing address is:
## Security Model
-Apache InLong's Sort module provides real-time synchronization capabilities,
supporting reading from and writing to various types of databases with trusted
data. Unless specified otherwise, the presence of malicious data in the
database is considered a security risk for the user. We emphasize that users
are responsible for ensuring the security of their database data. Therefore, if
vulnerabilities are triggered by the content of the synchronized data, such
issues should not be reported a [...]
+Apache InLong modules have clearly defined responsibilities for security
boundaries based on their design roles. The following scenarios are not
considered vulnerabilities in Apache InLong and should not be reported as
security issues:
+- The Sort module provides real-time data synchronization capabilities,
responsible for reading and writing trusted data across various databases.
Unless otherwise specified, malicious data within the database is considered
unsafe input, and users must ensure the security of their data sources
themselves, including but not limited to validating incoming data and
authenticating access origins.
+
+- The Manager module provides tenant isolation capabilities. Within the same
tenant, any member can view all business information under that tenant,
including Groups, Sinks, Streams, and more. Under the tenant permission model,
only the Group owner has the authority to modify or delete their respective
Groups, Sinks, Streams, and related data; normal operations performed by
members within their granted permissions also fall under this category. To
prevent business information from being [...]
+
+It should be noted that the above explanation aims to clarify the security
boundaries. We always welcome community input on enhancing codebase security
and improving boundary protection, working together to drive the project's
continuous evolution.
\ No newline at end of file
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/security.md
b/i18n/zh-CN/docusaurus-plugin-content-docs/current/security.md
index fde1ab64e32..069aa3ded97 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/security.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/security.md
@@ -16,5 +16,10 @@ Apache 软件基金会积极致力于消除针对其产品的安全问题和拒
## 安全模型
-Apache InLong 中 Sort
模块提供实时同步的能力，支持在各种类型的数据库中读取/写入受信任的数据。除非另有规定，否则数据库中存在恶意的数据是不安全的。我们认为，用户需要确保其数据库中的数据是安全的。因此，如果是因为同步的数据内容可能触发某些漏洞，则不要将此问题报告为
Apache InLong 的漏洞。我们欢迎提出强化代码库的建议。
+Apache InLong 各模块基于其设计定位，对安全边界有明确的责任划分。以下情况不属于 Apache InLong 的漏洞，无需作为安全问题提交报告：
+- Sort
模块提供实时数据同步能力，负责在各类数据库之间读取与写入受信任的数据。除非另有约定，数据库中的恶意数据均被视为不安全输入，用户应自行确保数据源的安全性，包括但不限于对入库数据进行校验、对访问来源进行鉴权等。
+
+- Manager 模块提供租户隔离能力。在同一租户内，任意成员均可查看该租户下的全部业务信息，包括 Group、Sink、Stream
等。在租户权限模型下，仅 Group 责任人有权对其名下的 Group、Sink、Stream
等信息进行修改与删除；成员在被授予的权限范围内执行的正常操作亦属此列。如需防止业务信息被他人查看，用户只需确保未将无关人员加入当前租户。
+
+需要说明的是，以上说明旨在明确安全边界。我们始终欢迎社区就强化代码库安全性、完善边界防护等提出建议，共同推动项目持续演进。
\ No newline at end of file
