Which of the following are common techniques for securing Nagios? (Select THREE correct answers)

Requiring authentication for CGI script access (e.g., via web server configuration) ensures that only authorized users can view the Nagios monitoring interface or issue commands.

While chroot jails can enhance security for some applications, running Nagios in a chroot jail is not a commonly recommended or standard security technique for typical deployments, often adding unnecessary complexity.

Nagios itself does not have a `enabletls` compilation option; TLS/SSL encryption for the web interface is typically configured at the web server layer (e.g., Apache, Nginx) that serves the Nagios CGI scripts.

Running the Nagios daemon as a dedicated non-root user adheres to the principle of least privilege, minimizing the impact if the Nagios process were to be compromised.

Disabling external commands (if not strictly required for functionality) mitigates the risk of unauthorized users or malicious scripts injecting arbitrary commands into the Nagios system.