zabbix_selinux(8)
π zabbix_selinux(8) β the SELinux policy for zabbix, explained π
Okay bestie, gather round, because this is the manual page for zabbix_selinux β the SELinux policy situation for alllll the zabbix processes. Yes, the whole page. No skipping. Periodt.
β¨ NAME β¨
zabbix_selinux β the Security Enhanced Linux Policy for the zabbix processes π«Ά
πΈ DESCRIPTION πΈ
So like, Security-Enhanced Linux secures the zabbix processes via flexible mandatory access control. That's the whole vibe β SELinux is the bouncer at the club and it checks everybody's label before letting them touch anything. π
The zabbix processes execute with the zabbix_t SELinux type. Wanna check if you've got these processes running? Just run the ps command with the -Z qualifier, easy peasy:
ps -eZ | grep zabbix_t
That's it. That's the whole vibe check. π₯
π¦ ENTRYPOINTS π¦
The zabbix_t SELinux type can be entered via the zabbix_exec_t file type. Think of it as the door β¨ into the domain.
The default entrypoint paths for the zabbix_t domain are literally these:
/usr/bin/zabbix_proxy, /usr/bin/zabbix_server,
/usr/bin/zabbix_proxy_mysql, /usr/bin/zabbix_proxy_pgsql,
/usr/bin/zabbix_server_mysql, /usr/bin/zabbix_server_pgsql,
/usr/bin/zabbix_proxy_sqlite3, /usr/bin/zabbix_server_sqlite3
Not me listing all eight, but yes, all eight, because every single one matters. π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. It's giving "everybody gets their own little name tag." π
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. The SELinux zabbix policy is very flexible, allowing users to setup their zabbix processes in as secure a method as possible. Iconic honestly.
The following process types are defined for zabbix:
zabbix_t, zabbix_agent_t, zabbix_script_t
Note:semanage permissive -a zabbix_tcan be used to make the process typezabbix_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
So like, permissive = it won't block you, but it WILL still snitch in the logs. π Keep that in mind, bestie.
π₯ BOOLEANS π₯
SELinux policy is customizable based on least access required. The zabbix policy is extremely flexible and has several booleans that allow you to manipulate the policy and run zabbix with the tightest access possible. Security girlboss behaviour. π
If you want to determine whether zabbix can connect to all TCP ports, you must turn on the zabbix_can_network boolean. Disabled by default.
setsebool -P zabbix_can_network 1
If you want to allow Zabbix to run su/sudo, you must turn on the zabbix_run_sudo boolean. Disabled by default.
setsebool -P zabbix_run_sudo 1
If you want to dontaudit all daemons scheduling requests (setsched, sys_nice), you must turn on the daemons_dontaudit_scheduling boolean. Enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
See how the -P is there every time? That's the "make it permanent" slay. π«Ά
π PORT TYPES π
SELinux defines port types to represent TCP and UDP ports.
You can see the types associated with a port by using the following command:
semanage port -l
Policy governs the access confined processes have to these ports. The SELinux zabbix policy is very flexible, allowing users to setup their zabbix processes in as secure a method as possible.
The following port types are defined for zabbix:
zabbix_agent_port_t- Default Defined Ports:
tcp 10050
- Default Defined Ports:
zabbix_port_t- Default Defined Ports:
tcp 10051
- Default Defined Ports:
Two ports, two moods. π
π§ MANAGED FILES π§
The SELinux process type zabbix_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions β SELinux is not out here doing DAC's job for it, no cap.
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
faillog_t
/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*
krb5_host_rcache_t
/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0
lastlog_t
/var/log/lastlog.*
/var/lib/lastlog(/.*)?
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
zabbix_log_t
/var/log/zabbix.*
zabbix_tmp_t
(no paths listed, it's just vibes β¨)
zabbix_tmpfs_t
(also no paths listed π)
zabbix_var_lib_t
/var/lib/zabbix(/.*)?
/var/lib/zabbixsrv(/.*)?
zabbix_var_run_t
/run/zabbix(/.*)?
That's the whole roster, bestie. Every single one. π₯
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. It's giving "every file needs its label or it's not getting in." π
You can see the context of a file using the -Z option to ls.
Policy governs the access confined processes have to these files. The SELinux zabbix policy is very flexible, allowing users to setup their zabbix processes in as secure a method as possible.
πΈ EQUIVALENCE DIRECTORIES πΈ
zabbix policy stores data with multiple different file context types under the /var/lib/zabbix directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv directory you would execute the following command:
semanage fcontext -a -e /var/lib/zabbix /srv/zabbix
restorecon -R -v /srv/zabbix
Two commands, one slay. Don't forget the restorecon or it won't actually be applied, and then you'll be sad. π
π¦ STANDARD FILE CONTEXT π¦
SELinux defines the file context types for zabbix. If you wanted to store files with these types in different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t zabbix_exec_t '/srv/zabbix/content(/.*)?'
restorecon -R -v /srv/myzabbix_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. iykyk π
The following file types are defined for zabbix:
zabbix_agent_exec_tβ Set files with thezabbix_agent_exec_ttype, if you want to transition an executable to thezabbix_agent_tdomain.zabbix_agent_initrc_exec_tβ Set files with thezabbix_agent_initrc_exec_ttype, if you want to transition an executable to thezabbix_agent_initrc_tdomain.zabbix_exec_tβ Set files with thezabbix_exec_ttype, if you want to transition an executable to thezabbix_tdomain.
Paths:
/usr/bin/zabbix_proxy, /usr/bin/zabbix_server,
/usr/bin/zabbix_proxy_mysql, /usr/bin/zabbix_proxy_pgsql,
/usr/bin/zabbix_server_mysql, /usr/bin/zabbix_server_pgsql,
/usr/bin/zabbix_proxy_sqlite3, /usr/bin/zabbix_server_sqlite3
zabbix_initrc_exec_tβ Set files with thezabbix_initrc_exec_ttype, if you want to transition an executable to thezabbix_initrc_tdomain.zabbix_log_tβ Set files with thezabbix_log_ttype, if you want to treat the data as zabbix log data, usually stored under the/var/logdirectory.zabbix_script_exec_tβ Set files with thezabbix_script_exec_ttype, if you want to transition an executable to thezabbix_script_tdomain.
Paths:
/usr/lib/zabbix/externalscripts(/.*)?,
/var/lib/zabbix/externalscripts(/.*)?
zabbix_tmp_tβ Set files with thezabbix_tmp_ttype, if you want to store zabbix temporary files in the/tmpdirectories.zabbix_tmpfs_tβ Set files with thezabbix_tmpfs_ttype, if you want to store zabbix files on a tmpfs file system.zabbix_var_lib_tβ Set files with thezabbix_var_lib_ttype, if you want to store the zabbix files under the/var/libdirectory.
Paths:
/var/lib/zabbix(/.*)?, /var/lib/zabbixsrv(/.*)?
zabbix_var_run_tβ Set files with thezabbix_var_run_ttype, if you want to store the zabbix files under the/runor/var/rundirectory.zabbixd_var_lib_tβ Set files with thezabbixd_var_lib_ttype, if you want to store the zabbixd files under the/var/libdirectory.
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels.
Lowkey the most important note on this whole page β chcon is temporary, semanage fcontext + restorecon is forever. π«Ά
β COMMANDS β
Here's the little toolbox, all the semanage subcommands doing their thing:
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage portcan also be used to manipulate the port definitions.semanage booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. Yes, a GUI. For when clicking is the mood. π±οΈβ¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage. A robot wrote it, and honestly? It ate. π€π
π SEE ALSO π
selinux(8)zabbix(8)semanage(8)restorecon(8)chcon(1)sepolicy(8)setsebool(8)zabbix_agent_selinux(8)zabbix_agent_selinux(8)zabbix_script_selinux(8)zabbix_script_selinux(8)
(Yes, zabbix_agent_selinux(8) and zabbix_script_selinux(8) are each listed twice in the original, and we're keeping it that way. Iconic repetition. π)
okay that's the whole page bestie, mwah π β this little love letter is zabbix, dated 26-10-06, and it's the zabbix_selinux(8) manual page. go forth and label responsibly πΈπ¦π
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms