There is a site built on CMS 1C-Bitrix. The site along with the admin stick to the Internet. Since 1C-Bitrix is a very popular CMS, I’m expected to worry about the possibility of publishing serious vulnerabilities in it and the possibility of script script script scripts on the site, since I’ll determine that the site is managed by this particular CMS. not difficult.
What measures can be taken to:
- make it difficult to automatically determine if the site is managed by CMS Bitrix?
- to protect the admin Beatrix from brute force admin password?
So far, the simplest thing has come to my mind is to restrict access to the admin panel by IP addresses of those who administer the site, but this solution is not universal, and sooner or later it will have to be abandoned - as soon as it becomes necessary to edit the materials on the site from an arbitrary place the planet 24/7, not bothering with a proxy / VPN.
Update: Bitrix’s position on this issue, as I understood from the correspondence with their support, comes down to using the features of the CMS 1C-Bitrix Proactive Defense module, which allows you to configure IP access restriction and two-factor authorization of admins, and much more including mentioned in the answers below. However, my question is rather about server-level protection, not application level. In addition, this solution has a big drawback - it is not universal: the Proactive Defense module is not included in all editions (types of licenses) of this CMS.