Skip to content

Fix: Update security guidelines and add missing ports to documentation [4.6.0] #10473

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

Open
wso2-engineering-bot wants to merge 1 commit into
base: 4.6.0
Choose a base branch
from
Open

Fix: Update security guidelines and add missing ports to documentation [4.6.0] #10473

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 2 additions & 1 deletion ...etup/deployment-best-practices/security-guidelines-for-production-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -446,7 +446,8 @@ This section provides a list of security guidelines for configuring the network
<tr class="odd">
<td><p>Check open ports and services</p></td>
<td><p>Periodically check for open ports using port scanning tools and make sure that only the necessary ports are open to both internal and external networks. Be sure that only the ports relevant to your WSO2 products are open for communication. If there are other ports started, be sure to monitor them.</p>
<p>For the full list of ports in all WSO2 products, see <a href="{{base_path}}/install-and-setup/setup/reference/default-product-ports/">Default Product Ports</a>.</p></td>
<p>For the full list of ports in all WSO2 products, see <a href="{{base_path}}/install-and-setup/setup/reference/default-product-ports/">Default Product Ports</a>.</p>
<p><strong>Note:</strong> Some ports may be dynamically allocated during server operations. When monitoring open ports, verify that any dynamic ports are expected and properly secured according to your deployment requirements. Dynamic port allocation can occur due to specific runtime configurations, JMX monitoring, clustering, and other operational requirements.</p></td>
</tr>
<tr class="even">
<td><p>Configure device-level security</p></td>
Expand Down
40 changes: 40 additions & 0 deletions en/docs/install-and-setup/setup/reference/default-product-ports.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,14 @@ Listed below are the ports used by the API-M runtime when the [port offset]({{ba
SSL port of the secure transport for receiving throttling events. This is required when the binary data publisher is used for throttling.
</td>
</tr>
<tr>
<td>
<code>10711</code>
</td>
<td>
SSL port for the secure transport used in data publishing and analytics. This port is used for secure communication with analytics servers.
</td>
</tr>
<tr>
<td>
<code>9099</code>
Expand All @@ -93,6 +101,38 @@ Listed below are the ports used by the API-M runtime when the [port offset]({{ba
Web Socket ports.
</td>
</tr>
<tr>
<td>
<code>8099</code>
</td>
<td>
Web Socket secure port (WSS).
</td>
</tr>
<tr>
<td>
<code>9021</code>
</td>
<td>
TCP port used for internal event streaming and communication between API-M components.
</td>
</tr>
<tr>
<td>
<code>8021</code>
</td>
<td>
Port used for internal event streaming communication.
</td>
</tr>
<tr>
<td>
<code>8672</code>
</td>
<td>
Port used for message broker AMQP transport with SSL.
</td>
</tr>
<tr>
<td>
<code>8000</code>
Expand Down