Definition of Fedora Common User Security Policy for fedora

based on jodehnal's bachelor thesis on creating a SCAP profile for common users of Fedora workstation - link will be added after publication

1.1: Protection of the BIOS or UEFI

Description: Users should protect their BIOS or UEFI with a password.

Levels:

Automated: no

No rules selected

1.2: Proper BIOS or UEFI Configuration

Description: Users should disable features and devices in the BIOS or UEFI that are not in use and should only include trusted devices in the boot order.

Levels:

Automated: no

No rules selected

1.3: 64-bit OS

Description: When possible, users should use a 64-bit system and hardware that supports it.

Levels:

Automated: no

No rules selected

2.1: Security Policy Selection

Description: Users should apply the Fedora Common User Security Policy in the installer.

Levels:

Automated: no

No rules selected

2.2: Disk Partitioning

Description: Users should put the /home, /tmp, /var, /var/tmp and /var/log directories on separate partitions.

Levels:

Automated: no

No rules selected

2.3: Password Security

Description: Users should ensure that all account passwords adhere to the password rules in rule 4.1.

Levels:

Automated: no

No rules selected

2.4: Disk Encryption

Description: Users should encrypt their disk with a passphrase that adheres to the password rules in rule 4.1.

Levels:

Automated: no

No rules selected

3.1: Bootloader Security

Description: If the BIOS or UEFI does not allow password protection of the boot process, users should set a bootloader password.

Levels:

Automated: no

Selections:

3.2: Software Updates

Description: Users should apply updates from the GNOME Software application at least once per day.

Levels:

Automated: no

Selections:

3.3: Filesystem Configuration

Description: Directories /home (-noexec), /tmp, /var, /var/tmp and /var/log mount option configuration.

Levels:

Automated: yes

Selections:

3.4: Crypto Policy

Description: System cryto policy configuation and ensuring it is not overridden in critical components.

Levels:

Automated: yes

Selections:

3.5: Auditing and Logging

Description: Auditd and journald configutation.

Levels:

Automated: yes

Selections:

3.6: Files, Permissions, and Ownership

Description: User and critical system file permissions and ownership, user and group file and directory ownership, identifiers.

Levels:

Automated: no

Selections:

3.7: Memory Protection

Description: Enable ASLR and ExecShield, restrict exposed kernel pointer.

Levels:

Automated: yes

Selections:

3.8: GUI Configuration

Description: Do not show user list, disable xdmpc and auto login, set up idle lock and protect the settings.

Levels:

Automated: yes

Selections:

3.9: Time and Schedulers

Description: Chrony and time-based scheduler security configuration.

Levels:

Automated: yes

Selections:

3.10: Service Minimization

Description: Users should remove any services that are not necessary for normal system usage.

Levels:

Automated: no

Selections:

4.1: Account Protection

Description: All account passwords must be passphrases of at least 4 words and 15 characters with at least three character classes, generated with a large wordlist and a source of randomness.

Levels:

Automated: no

Selections:

4.2: Sudo

Description: Secure sudo configuration.

Levels:

Automated: yes

Selections:

4.3: SSH Server

Description: Secure ssh server configuration.

Levels:

Automated: yes

Selections:

5.1: General Network Configuration

Description: If users did not configure IPv6 on the system and it is not needed, it should be disabled.

Levels:

Automated: no

Selections:

5.2: Firewall Configuration

Description: Users should ensure that all network interfaces are in the appropriate firewall zone and that ports and services allowed by the firewall are reduced to the necessary minimum.

Levels:

Automated: no

Selections:

6.1: Web Browser

Description: Users should install the Firefox Flatpak from FlatHub and use it instead of the default Firefox application. If the default Firefox application must be used, the users should apply the Common User Security Profile for Mozilla Firefox CaC profile.

Levels:

Automated: no

No rules selected

7.1: Mandatory Access Control

Description: Ensure SELinux is installed and enabled, in enforcing mode using targeted policy.

Levels:

Automated: no

Selections:

7.2: Periodic Compliance Scans

Description: Users should perform periodic system scans and remediations with the Common User Security Profile by using the oscap tool or SCAP Workbench.

Levels:

Automated: no

No rules selected