Skip to content

security: remove mention of "TiFlow" (#21886) #21891

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 11, 2025
Merged

security: remove mention of "TiFlow" (#21886) #21891

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b80c8fe
Update best-practices-for-security-configuration.md
hfxsd Oct 11, 2025
d79578d
Update best-practices-for-security-configuration.md
hfxsd Oct 11, 2025
739e383
Update best-practices-for-security-configuration.md
hfxsd Oct 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions best-practices-for-security-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,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 |
Copy link

@gemini-code-assist gemini-code-assist bot Oct 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

To improve the readability of the markdown source, it's good practice to align the table header with the column content. The current formatting has some inconsistent spacing in the header.

Suggested change
| Component | Default port| Protocol |
| Component | Default port | Protocol |

|-------------------|-------------|------------|
| TiDB | 4000 | MySQL |
| TiDB | 10080 | HTTP |
Expand All @@ -76,10 +76,10 @@ 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 |
Expand All @@ -98,7 +98,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:
Expand Down
Loading