Ensure the LXD remote API is not listening on all interfaces

ВисокаНиво 1Аутоматскаlxd

Опис

core.https_address exposes the LXD REST API (full control of every instance and the host) over the network. The audit reads it with "lxc config get core.https_address" and passes when it is unset (local unix socket only) or bound to a specific address; it fails on wildcard binds such as [::], 0.0.0.0 or a bare :8443. The lxc client must reach the daemon (run as root or a member of the lxd group).

Како се проверава

Метод провере: Команда љуске

shell

lxc info >/dev/null 2>&1 || exit 1
v=$(lxc config get core.https_address 2>/dev/null) || exit 1
case "$v" in
  "[::]"*|0.0.0.0*|:*) echo "remote API listens on all interfaces: $v"; exit 1 ;;
esac
echo compliant

Очекивани излаз: compliant

Како се исправља

Метод исправке: Смерница или закрпа инфраструктуре

If remote access is not needed: lxc config unset core.https_address. Otherwise bind to the management interface only, e.g. lxc config set core.https_address 10.0.0.5:8443, and restrict port 8443 with the host firewall.

Својства

Оперативни системи: Било који
Ознаке: lxdcontainersnetwork
Референца: CIS-style LXD hardening guidance - Restrict remote API exposure (no CIS benchmark section; verify against your hardening standard)

Проверите овај рачунар

Покрените ово на рачунару за који имате дозволу за проверу. Скенирање ради у режиму само за читање.

shell

tmaegis scan --target lxd