@@ -144,6 +144,49 @@ You can configure JWT settings in the Glances configuration file:
144144 **Note: ** The token endpoint (``/api/4/token ``) does not require authentication.
145145Protected endpoints support both Bearer token and Basic Auth authentication methods.
146146
147+ .. _security :
148+
149+ Security
150+ --------
151+
152+ By default, Glances web server runs **without authentication ** and binds to
153+ **all network interfaces ** (``0.0.0.0 ``). This means any client that can reach
154+ the server on the network can access the full REST API, including sensitive
155+ system information such as process command-lines, which may contain credentials
156+ (passwords, API keys, tokens passed as arguments).
157+
158+ This default is intentional for ease of use on private, trusted networks (home
159+ labs, local machines, internal infrastructure). However, if your Glances
160+ instance is reachable from untrusted networks, you should take the following
161+ precautions:
162+
163+ **Enable authentication ** by starting Glances with the ``--password `` option:
164+
165+ .. code-block :: bash
166+
167+ glances -w --password
168+
169+ **Bind to localhost only ** if remote access is not needed:
170+
171+ .. code-block :: bash
172+
173+ glances -w --bind 127.0.0.1
174+
175+ **Use a reverse proxy ** (nginx, Caddy, Apache) with TLS and authentication for
176+ any public-facing or semi-public deployment. This is the recommended approach
177+ for production environments.
178+
179+ .. code-block :: ini
180+
181+ # Example: restrict bind to localhost, access via reverse proxy
182+ # In glances.conf:
183+ [outputs]
184+ # Set the bind address to localhost
185+ # then configure your reverse proxy to forward to 127.0.0.1:61208
186+
187+ When Glances is started without authentication, a warning message is displayed
188+ at startup to remind you of the risk.
189+
147190WebUI refresh
148191-------------
149192
0 commit comments