In Zabbix 5.0, a new feature was introduced - encryption between the Zabbix server and the database. In Zabbix 3.0, we introduced encryption between different Zabbix components - Zabbix servers, Zabbix proxy, Zabbix agents, and command-line utilities, so the system has become much more secure. All other components didn’t have an encrypted connection. In Zabbix 2.0, you could encrypt only the connection to the frontend and keep your password safe in the database by hashing them in MD5. Zabbix 2.0 was a very innovative though not a very secure monitoring solution. Conclusion ( 33:08) Evolution of security In addition, Zabbix can execute remote commands on your production servers. Zabbix needs to be secure as Zabbix configuration contains credentials, which are used to access all other systems, and the data collected from those systems may contain very sensitive information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |