[root@server5 log]# getsebool -a | grep httpd
httpd_anon_write → off
httpd_builtin_scripting → on
httpd_can_check_spam → off
httpd_can_connect_ftp → off
httpd_can_connect_ldap → off
httpd_can_connect_mythtv → off
httpd_can_connect_zabbix → off
httpd_can_manage_courier_spool → off
httpd_can_network_connect → on
httpd_can_network_connect_cobbler → off
httpd_can_network_connect_db → on
httpd_can_network_memcache → off
httpd_can_network_relay → off
httpd_can_sendmail → on
httpd_dbus_avahi → off
httpd_dbus_sssd → off
httpd_dontaudit_search_dirs → off
httpd_enable_cgi → on
httpd_enable_ftp_server → off
httpd_enable_homedirs → off
httpd_execmem → off
httpd_graceful_shutdown → off
httpd_manage_ipa → off
httpd_mod_auth_ntlm_winbind → off
httpd_mod_auth_pam → off
httpd_read_user_content → off
httpd_run_ipa → off
httpd_run_preupgrade → off
httpd_run_stickshift → off
httpd_serve_cobbler_files → off
httpd_setrlimit → off
httpd_ssi_exec → off
httpd_sys_script_anon_write → off
httpd_tmp_exec → off
httpd_tty_comm → off
httpd_unified → off
httpd_use_cifs → off
httpd_use_fusefs → off
httpd_use_gpg → off
httpd_use_nfs → off
httpd_use_opencryptoki → off
httpd_use_openstack → off
httpd_use_sasl → off
httpd_verify_dns → off
[root@server5 log]# getsebool -a | grep mysql
mysql_connect_any → off
mysql_connect_http → off
selinuxuser_mysql_connect_enabled → off
SELinux at enforcing denies and logs actions that policy does not allow.
SELinux at permissive logs but allows actions that policy does not allow.
Since denying one action will prevent followup actions, those are not logged when enforcing.
Hence permissive gives better picture of everything that policy might need.
However, all actions are not logged by default. See man semanage-dontaudit
The audit2why ought to tell all the things that sealert/setroubleshoot tells.
The man audit2allow has an examples of steps to create and load a module policy.