Description: Only the components strictly necessary to the service provided by the system should be installed. Those whose presence can not be justified should be disabled, removed or deleted.
Level: minimal
Automated: partially
Selections:Description: Services are often installed with default configurations that enable features potentially problematic from a security point of view. The features configured at the level of launched services should be limited to the strict minimum.
Level: intermediary
Automated: yes
No rules selected
Description: The services and executables available on the system must be analyzed in order to know the privileges they require, and must then be configured and integrated to use the bare necessities.
Level: enhanced
Automated: partially
Selections:Description: It is recommended to use the mandatory access control (MAC) features in addition to the traditional Unix user model (DAC), or possibly combine them with partitioning mechanisms.
Level: high
Automated: yes
Selections:Description: Under Unix and derivatives, defense in depth must be based on a combination of barriers that must be kept independent of each other.
Level: minimal
Automated: partially
Selections:Description: Network services should as much as possible be hosted on isolated environments. This avoids having other potentially affected services if one of them gets compromised under the same environment.
Level: enhanced
Automated: yes
No rules selected
Description: The activities of the running system and services must be logged and archived on an external, non-local system.
Level: enhanced
Automated: yes
Selections:Description: None
Level: minimal
Automated: yes
Selections:Description: None
Level: intermediary
Automated: partially
Selections:Description: When the machine supports 64-bit operating systems, prefer it.
Level: intermediary
Automated: yes
Selections:Description: The iommu = force directive must be added to the list of kernel parameters during startup in addition to those already present in the configuration files of the bootloader (/boot/grub/menu.lst or /etc/default/grub).
Level: high
Automated: yes
Selections:Description: None
Level: intermediary
Automated: partially
Selections:Description: When possible, the /boot partition should not be mounted. In any case, access to the /boot directory must only be allowed to the root user.
Level: enhanced
Automated: yes
Selections:Description: The selection of packages installed should be as small as possible, limiting itself to select only what is required.
Level: intermediary
Automated: no
No rules selected
Description: Only up-to-date official repositories of the distribution must be used.
Level: minimal
Automated: partially
Selections:Description: When the distribution provides several types of repositories, preference should be given to those containing packages subject to additional hardening measures. Between two packages providing the same service, those subject to hardening (at compilation, installation, or default configuration) must be preferred.
Level: enhanced
Automated: yes
No rules selected
Description: A boot loader to protect the password boot must be to be privileged. This password must prevent any user from changing their configuration options.
Level: enhanced
Automated: yes
Selections:Description: None
Level: minimal
Automated: partially
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: All secret elements or those contributing to the authentication mechanisms must be set up as soon as the system is installed: account and administration passwords, root authority certificates, public keys, or certificates of the host (and their respective private key).
Level: enhanced
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: The loading of the kernel modules can be blocked by the activation of the sysctl kernel.modules_disabledconf: Prohibition of loading modules (except those already loaded to this point) kernel.modules_disabled = 1
Level: enhanced
Automated: yes
Selections:Description: It is recommended to load the Yama security module at startup (by example passing the security = yama argument to the kernel) and configure the sysctl kernel.yama.ptrace_scope to a value of at least 1.
Level: enhanced
Automated: yes
Selections:Description: Unused user accounts must be disabled at the system level.
Level: enhanced
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: no
No rules selected
Description: Each service must have its own system account and be dedicated to it exclusively.
Level: enhanced
Automated: yes
No rules selected
Description: Remote user sessions (shell access, graphical clients) must be closed after a certain period of inactivity.
Level: enhanced
Automated: yes
Selections:Description: None
Level: minimal
Automated: no
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: Any password must be protected by cryptographic mechanisms.
Level: minimal
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: The system umask must be set to 0027 (by default, any created file can only be read by the user and his group, and be editable only by his owner). The umask for users must be set to 0077 (any file created by a user is readable and editable only by him).
Level: enhanced
Automated: partially
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: minimal
Automated: yes
Selections:Description: Setuid executables should be as small as possible. When it is expected that only the administrators of the machine execute them, the setuid bit must be removed and prefer them commands like su or sudo, which can be monitored
Level: enhanced
Automated: yes
No rules selected
Description: Each user or service account must have its own temporary directory and dispose of it exclusively.
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
No rules selected
Description: None
Level: minimal
Automated: no
No rules selected
Description: The chosen syslog server must be hardened according to the security guides associated with this server. The configuration of the service must be performed according to the 'Security Recommendations for the implementation of a logging system' (DAT-NT-012) accessible on the ANSSI website.
Level: intermediary
Automated: partially
Selections:Description: None
Level: intermediary
Automated: yes
No rules selected
Description: The syslog services must be isolated from the rest of the system in a dedicated container.
Level: high
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: partially
Selections:Description: The logging of the system activity must be done through the auditd service.
Level: enhanced
Automated: yes
No rules selected
Description: Any file that is not transient (such as temporary files, databases, etc.) must be monitored by a sealing program. This includes: directories containing executables, libraries, configuration files, as well as any files that may contain sensitive elements (cryptographic keys, passwords, confidential data).
Level: high
Automated: yes
Selections:Description: The sealing database must be protected from malicious access by cryptographic signature mechanisms (with the key used for the signature not locally stored in clear), or possibly stored on a separate machine of the one on which the sealing is done. Check section "Database and config signing in AIDE manual" https://github.com/aide/aide/blob/master/doc/manual.html
Level: high
Automated: yes
No rules selected
Description: The deployed services must have their access restricted to the system strict minimum, especially when it comes to files, processes or network.
Level: enhanced
Automated: yes
No rules selected
Description: Each component supporting the virtualization must be hardened, especially by applying technical measures to counter the exploit attempts.
Level: enhanced
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: None
Level: intermediary
Automated: yes
No rules selected
Description: A group dedicated to the use of sudo must be created, and only members of this group are allowed to execute sudo.
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: partially
Selections:Description: The calling user must be authenticated before running any command with sudo.
Level: minimal
Automated: yes
Selections:Description: The targeted users of a rule should be, as much as possible, non privileged users.
Level: intermediary
Automated: yes
Selections:Description: The commands requiring the execution of sub-processes (EXEC tag) must be explicitly listed and their use should be reduced to a strict minimum.
Level: enhanced
Automated: yes
No rules selected
Description: The sudoers configuration rules should not involve negation.
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
Selections:Description: None
Level: intermediary
Automated: yes
No rules selected
Description: All AppArmor security profiles on the system must be enabled by default.
Level: high
Automated: yes
No rules selected
Description: It is recommended to enable the targeted policy when the distribution support it and that it does not operate another security module than SELinux.
Level: high
Automated: yes
Selections:Description: It is recommended to set the following Booleans: allow_execheap to off, forbids processes to make their heap executable; allow_execmem to off, forbids processes to have both write and execute rights on memory pages; allow_execstack to off, forbids processes to make their stack executable; secure_mode_insmod to on, prohibits dynamic loading of modules by any process; ssh_sysadm_login to off, forbids SSH logins to connect directly in sysadmin role.
Level: high
Automated: yes
Selections:Description: SELinux policy manipulation and debugging tools should not be installed on a machine in production.
Level: high
Automated: yes
Selections:Description: Interactive non-privileged users of a system must be confined by associating them with a SELinux confined user.
Level: high
Automated: yes
No rules selected