extern/zabbix-docker
1
0
Fork 0
mirror of https://github.com/zabbix/zabbix-docker.git synced 2024-12-22 22:41:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

Added security information

Browse Source
This commit is contained in:
Alexey Pustovalov 2024-02-12 19:01:30 +09:00
parent dccaf5e781
commit a6c9533168
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
SECURITY.md
View File

@ -26,7 +26,7 @@ The following information will be helpful for Zabbix Security team:
1. Zabbix Security team reviews the issue and evaluates its potential impact. 1. Zabbix Security team reviews the issue and evaluates its potential impact.
2. If the security issue is found not to be related to security then the issue will be moved to ZBX project. 2. If the security issue is found not to be related to security then the issue will be moved to ZBX project.
3. Zabbix security team works on the issue to provide a solution and keeps all details on the problem until the next version of Zabbix is out. 3. Zabbix security team works on the issue to provide a solution and keeps all details on the problem until the next version of Zabbix is out.
4. New images are created and made available for download on [https://zabbix.com/download](http://hub.docker.com/r/zabbix/) and [Red Hat Certified Container Catalog](https://catalog.redhat.com/software/containers/search?vendor_name=Zabbix%20Sia&p=1) 4. New images are created and made available for download on [https://www.zabbix.com/container_images](https://www.zabbix.com/container_images), [https://hub.docker.com/u/zabbix](http://hub.docker.com/r/zabbix/) and [Red Hat Certified Container Catalog](https://catalog.redhat.com/software/containers/search?vendor_name=Zabbix%20Sia&p=1)
5. Zabbix requests [CVE identifiers](https://cve.mitre.org/) for the security issue. 5. Zabbix requests [CVE identifiers](https://cve.mitre.org/) for the security issue.
6. Clients with valid support agreements are emailed giving a period of time when it is possible to upgrade before the issue becomes known to the public. 6. Clients with valid support agreements are emailed giving a period of time when it is possible to upgrade before the issue becomes known to the public.
7. A public announcement for the community is made. 7. A public announcement for the community is made.