zabbix_agent_selinux(8)

📦
version 20250627+git412.dbf877ab7 · 7 versions
, in opensuse-leap 16.0

✨ NAME ✨

okay so this is zabbix_agent_selinux(8), the manual page for Security Enhanced Linux Policy for the zabbix_agent processes. Literally the SELinux policy glow-up for zabbix_agent, and it's giving secure-but-flexible main character energy. 💅

💖 DESCRIPTION 💖

Security-Enhanced Linux secures the zabbix_agent processes via flexible mandatory access control. No cap, that's the whole vibe: flexible mandatory access control doing its thing.

The zabbix_agent processes execute with the zabbix_agent_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

For example:

ps -eZ | grep zabbix_agent_t

🚪 ENTRYPOINTS 🚪

The zabbix_agent_t SELinux type can be entered via the zabbix_agent_exec_t file type. iykyk — that's the doorway.

The default entrypoint paths for the zabbix_agent_t domain are the following:

/usr/bin/zabbix_agentd

🧠 PROCESS TYPES 🧠

SELinux defines process types (domains) for each process running on the system. periodt, every process gets its little domain situation.

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux zabbix_agent policy is very flexible allowing users to setup their zabbix_agent processes in as secure a method as possible. Obsessed — flexible but still locked down.

The following process types are defined for zabbix_agent:

zabbix_agent_t
Note: semanage permissive -a zabbix_agent_t can be used to make the process type zabbix_agent_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So bestie, permissive is not "no messages" — the denials still show up in the group chat. 😭

🎚️ BOOLEANS 🎚️

SELinux policy is customizable based on least access required. zabbix_agent policy is extremely flexible and has several booleans that allow you to manipulate the policy and run zabbix_agent with the tightest access possible. Least access required is the whole mood. ✨

  • daemons_dontaudit_scheduling — 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
  • fips_mode — 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
  • nis_enabled — 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
  • zabbix_run_sudo — 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

🔌 PORT TYPES 🔌

SELinux defines port types to represent TCP and UDP ports. Ports are having a moment.

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. SELinux zabbix_agent policy is very flexible allowing users to setup their zabbix_agent processes in as secure a method as possible. Flexible, but make it secure. 🦋

The following port types are defined for zabbix_agent:

zabbix_agent_port_t

Default Defined Ports:

  • tcp 10050

That's the port, bestie. 🍓

📁 MANAGED FILES 📁

The SELinux process type zabbix_agent_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the process's UID still need to have DAC permissions. Yes, SELinux does its thing, and DAC permissions still need to be there too. 🫶

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_tmpfs_t

This file type is listed here with no default path block printed underneath. It's giving mysterious little cameo. 💅

zabbix_var_run_t

/run/zabbix(/.*)?

🏷️ FILE CONTEXTS 🏷️

SELinux requires files to have an extended attribute to define the file type. Extended attributes are doing the absolute most, and honestly? Slay.

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. SELinux zabbix_agent policy is very flexible allowing users to setup their zabbix_agent processes in as secure a method as possible. It's flexible, it's secure, it's the vibe. 🌈

🎀 STANDARD FILE CONTEXT 🎀

SELinux defines the file context types for the zabbix_agent. If you wanted to store files with these types in a 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_agent_exec_t '/srv/zabbix_agent/content(/.*)?'
restorecon -R -v /srv/myzabbix_agent_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies, rise. ✨

The following file types are defined for zabbix_agent:

  • zabbix_agent_exec_t — set files with the zabbix_agent_exec_t type, if you want to transition an executable to the zabbix_agent_t domain.
  • zabbix_agent_initrc_exec_t — set files with the zabbix_agent_initrc_exec_t type, if you want to transition an executable to the zabbix_agent_initrc_t domain.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. So don't just chcon and ghost it — permanent changes need the proper semanage fcontext + restorecon combo, bestie. 😭

🛠️ COMMANDS 🛠️

  • semanage fcontext can also be used to manipulate default file context mappings.
  • semanage permissive can also be used to manipulate whether or not a process type is permissive.
  • semanage module can also be used to enable/disable/install/remove policy modules.
  • semanage port can also be used to manipulate the port definitions.
  • semanage boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings.

Toolbox unlocked, bestie. 🧰💖

✍️ AUTHOR ✍️

This manual page was auto-generated using sepolicy manpage . Not me being auto-generated and still serving looks. 💅

👀 SEE ALSO 👀

selinux(8), zabbix_agent(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)

Okay that's the whole manual, bestie 🫶 — this zabbix_agent_selinux(8) page is from source/version zabbix_agent and dated 26-10-06. Now go forth and vibe-check your SELinux labels! 💅✨

📦 where this page comes from