Ensure Apache AppArmor Profile is in Enforce Mode

FaibleNiveau 2Automatiséeapache

Description

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.

Méthode de vérification

Méthode d'audit: Commande 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"}'

Sortie attendue: compliant

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

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

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: apacheapparmor
Référence: CIS Apache HTTP Server 2.4 Benchmark v2.4.0 - 12.3 Ensure Apache AppArmor Profile is in Enforce Mode

Vérifier cet hôte

Exécutez cette commande sur une machine que vous êtes autorisé à auditer. L'analyse est en lecture seule.

shell

tmaegis scan --target apache --level 2