On the first critical one, the list is as shown below. I have rebooted from the Plesk CP, and the list remains the same. Am I being silly?Critical Risk: Un-Applied updates for your system were detected. A full list of available updates is available in /var/asl/data/updates_pending.log
Critical Risk: ASL is in warn-only mode for detecting and disabling dangerous PHP functions.
High Risk: Kernel check, Main executable randomization (ET_EXEC) failed
High Risk: Allow URL Include is enabled. This allows an attacker to remotely include files into PHP scripts through urls.
High Risk: PHP function exec() allows an attacker to execute shell commands through php.
High Risk: PHP Function popen() allows attacker to execute commands on a system.
High Risk: SSH No Administrative users are defined: Administrative users are the users that maintain this system, that should su or sudo to root. This test verifies that administrative users are defined. It is not recommended to manage the system by directly logging in as root.
High Risk: SSH setting: Password Authentication is allowed. Passwords are easily compromised, lost, and are a poor security model. Implement two factor authentication with SSH keys.
High Risk: SSH setting: The system allows remote root logins
and can someone advise on best practice for the other critical and high vulnerable issues on whether I should change them.[root@plesk2 ~]# cat /var/asl/data/updates_pending.log
dbus-python.x86_64 0.70-9.el5_4 updates
httpd.x86_64 2.2.3-31.el5.centos.2 updates
httpd-devel.x86_64 2.2.3-31.el5.centos.2 updates
httpd-manual.x86_64 2.2.3-31.el5.centos.2 updates
libvorbis.i386 1:1.1.2-3.el5_4.4 updates
libvorbis.x86_64 1:1.1.2-3.el5_4.4 updates
libvorbis-devel.i386 1:1.1.2-3.el5_4.4 updates
libvorbis-devel.x86_64 1:1.1.2-3.el5_4.4 updates
mod_ssl.x86_64 1:2.2.3-31.el5.centos.2 updates
[root@plesk2 ~]#
Thanks, as ever, in advance.