From 58c45bdf4d50f18054e25e909147dcb17289c303 Mon Sep 17 00:00:00 2001 From: Olivier Dony Date: Tue, 17 Apr 2018 02:34:49 +0200 Subject: [IMP] doc: setup/deploy: add security recommendations Extra recommendations about remote SSH access and demo data on internet-facing servers, in light of issue #24120. --- doc/setup/deploy.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) (limited to 'doc/setup') diff --git a/doc/setup/deploy.rst b/doc/setup/deploy.rst index 5aea431caf4..13d4198cceb 100644 --- a/doc/setup/deploy.rst +++ b/doc/setup/deploy.rst @@ -442,6 +442,10 @@ security-related topics: only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases. +- Do **not** install demo data on internet-facing servers. Databases with demo data contain + default logins and passwords that can be used to get into your systems and cause significant + trouble, even on staging/dev systems. + - Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the hostname. See :ref:`db_filter`. @@ -474,6 +478,12 @@ security-related topics: and then enable the :option:`proxy mode ` option. See also :ref:`https_proxy`. +- If you need to allow remote SSH access to your servers, make sure to set a strong password + for **all** accounts, not just `root`. It is strongly recommended to entirely disable + password-based authentication, and only allow public key authentication. Also consider + restricting access via a VPN, allowing only trusted IPs in the firewall, and/or + running a brute-force detection system such as `fail2ban` or equivalent. + - Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production. -- cgit v1.2.3