Ensure Apache AppArmor Profile is in Enforce Mode

BajaNivel 2Automatizadaapache

Descripción

AppArmor profiles may be in one of three modes: disabled, complain or enforce. In the complain mode, any violations of the access controls are logged but the restrictions are not enforced. Also, once a profile mode has been changed, it is recommended to restart the Apache server, otherwise the currently running process may not be confined by the policy. aa-status must list running apache2 processes only under "processes are in enforce mode" (none unconfined or in complain mode); fails when Apache is not running. Not applicable without /etc/apparmor.d.

Cómo se verifica

Método de auditoría: Comando de shell

shell

out=$(aa-status 2>/dev/null) || exit 1; printf '%s\n' "$out" | awk '/processes are in enforce mode/{s="e"; next} /processes are (in complain|unconfined|in kill|in prompt)/{s="x"; next} /profiles are/{s=""; next} /apache2|httpd/{if(s=="e") e=1; if(s=="x") bad=1} END{print (e&&!bad)?"compliant":"noncompliant"}'

Salida esperada: compliant

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

aa-enforce /usr/sbin/apache2 (after tuning the profile in complain mode), then restart Apache.

Propiedades

Sistemas operativos: Cualquiera
Etiquetas: apacheapparmor
Referencia: CIS Apache HTTP Server 2.4 Benchmark v2.4.0 - 12.3 Ensure Apache AppArmor Profile is in Enforce Mode

Verificar este host

Ejecute esto en un equipo que tenga permiso para auditar. El escaneo es de solo lectura.

shell

tmaegis scan --target apache --level 2