From b0b989cb23ef0eee8d1dc1dd5ea204c76eb97292 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Sat, 11 Oct 2025 15:41:22 +0800 Subject: [PATCH 1/2] Update best-practices-for-security-configuration.md --- best-practices-for-security-configuration.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/best-practices-for-security-configuration.md b/best-practices-for-security-configuration.md index 9f5320ebf32f1..e0150488d9131 100644 --- a/best-practices-for-security-configuration.md +++ b/best-practices-for-security-configuration.md @@ -66,7 +66,7 @@ By default, TiDB Dashboard is designed for trusted users. The default port inclu By default, TiDB installation includes several privileged interfaces for inter-component communication. These ports typically do not need to be accessible to users, because they are primarily for internal communication. Exposing these ports on public networks increases the attack surface, violates the principle of least privilege, and raises the risk of security vulnerabilities. The following table lists the default listening ports in a TiDB cluster: -| Component | Default port | Protocol | +| Component | Default port| Protocol | |-------------------|-------------|------------| | TiDB | 4000 | MySQL | | TiDB | 10080 | HTTP | @@ -78,15 +78,15 @@ By default, TiDB installation includes several privileged interfaces for inter-c | TiFlash | 20170 | Protocol | | TiFlash | 20292 | HTTP | | TiFlash | 8234 | HTTP | -| TiFlow | 8261 | HTTP | -| TiFlow | 8291 | HTTP | -| TiFlow | 8262 | HTTP | -| TiFlow | 8300 | HTTP | +| DM master | 8261 | HTTP | +| DM master | 8291 | HTTP | +| DM worker | 8262 | HTTP | +| TiCDC | 8300 | HTTP | | TiDB Lightning | 8289 | HTTP | | TiDB Operator | 6060 | HTTP | | TiDB Dashboard | 2379 | HTTP | -| TiDB Binlog | 8250 | HTTP | -| TiDB Binlog | 8249 | HTTP | +| TiDB Binlog | 8250 | HTTP | +| TiDB Binlog | 8249 | HTTP | | TMS | 8082 | HTTP | | TEM | 8080 | HTTP | | TEM | 8000 | HTTP | @@ -100,7 +100,7 @@ By default, TiDB installation includes several privileged interfaces for inter-c | AlertManager | 9093 | HTTP | | AlertManager | 9094 | Protocol | | Node Exporter | 9100 | HTTP | -| Blackbox Exporter | 9115 | HTTP | +| Blackbox Exporter | 9115 | HTTP | | NG Monitoring | 12020 | HTTP | It is recommended to only expose the `4000` port for the database and the `9000` port for the Grafana dashboard to ordinary users, while restricting access to other ports using network security policies or firewalls. The following is an example of using `iptables` to restrict port access: From 32e28f1fffd77d05b83201de2c055b935665e680 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Sat, 11 Oct 2025 16:05:20 +0800 Subject: [PATCH 2/2] Update best-practices-for-security-configuration.md --- best-practices-for-security-configuration.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/best-practices-for-security-configuration.md b/best-practices-for-security-configuration.md index e0150488d9131..36053b8f868e3 100644 --- a/best-practices-for-security-configuration.md +++ b/best-practices-for-security-configuration.md @@ -85,8 +85,6 @@ By default, TiDB installation includes several privileged interfaces for inter-c | TiDB Lightning | 8289 | HTTP | | TiDB Operator | 6060 | HTTP | | TiDB Dashboard | 2379 | HTTP | -| TiDB Binlog | 8250 | HTTP | -| TiDB Binlog | 8249 | HTTP | | TMS | 8082 | HTTP | | TEM | 8080 | HTTP | | TEM | 8000 | HTTP |