5. Security Requirements

5.1. System hardening

5.1.1. Disk encryption

5.1.1.1. Features

• USR-TAP-SEC-ENC-001 The OS MUST provide a way for the user to encrypt their drive upon installation.
• USR-TAP-SEC-ENC-002 The OS MAY provide a way for the user to encrypt their data after installation.
• USR-TAP-SEC-ENC-003 The OS MUST enable disk decryption using a passphrase.
• USR-TAP-SEC-ENC-004 The OS SHOULD enable disk decryption using a smartcard (YubiKey).

5.1.1.2. Acceptance criteria

• The user can choose to install the distribution with full disk encryption.
• The user can choose to encrypt a drive as they use the system.
• The user can decrypt their drive with a passphrase.
• The user can decrypt their drive with a YubiKey smartcard.

5.2. Data storage security

5.3.1. System state recovery

5.3.1.1. Features

• USR-TAP-SEC-STO-001 The OS MUST save the state of the system on every update.
• USR-TAP-SEC-STO-002 The OS MUST allow the (admin) user to restore system snapshots.

5.3.1.2. Acceptance criteria

• A snapshot is made everytime the system is updated.
• Snapshots can be restored even if the update fails.

5.3.2. User data recovery

5.3.2.1. Features

• USR-TAP-SEC-STO-003 The OS SHOULD save the user’s data at regular intervals as snapshots.
• USR-TAP-SEC-STO-004 The OS SHOULD allow the user to restore snapshots of their data.

5.3.2.2. Acceptance criteria

• The user can take a snapshot of their data.
• The user can recover older versions of their data.

5.3.3. Remote storage

5.3.3.1. Features

• USR-TAP-SEC-STO-005 The OS MUST allow the user to store data in a remote location and use it like a regular drive.
• USR-TAP-SEC-STO-006 The solutions transmits encrypted data over the network.

5.3.3.2. Acceptance criteria

• The user has access to a remote storage they can mount like a drive and access like a directory.
• The solution does not transmit data in clear.

5.3.4. Data replication

5.3.4.1. Features

• The OS MAY be compatible with data replication systems, such as RAID or ZFS.

5.3.4.2. Acceptance criteria

• The user can choose to install the OS using a RAID, ZFS, or any relevant partitioning scheme.

5.4. Identities

5.4.1 Passwords and authentication

5.4.1.1. Features

• USR-TAP-SEC-AUT-001 The OS MUST provide a secure way for the user to store and retrieve passwords.
• USR-TAP-SEC-AUT-002 The OS SHOULD enable physical MFA when applicable.

5.4.1.2. Acceptance criteria

• The OS features a password manager or an equivalent browser extension.
• The OS is compatible with smartcards.

5.5. Privacy requirements

5.5.1. Open-source software

5.5.1.1. Features

• USR-TAP-SEC-PRV-001 The OS MUST only provide applications that respect the user’s privacy.
• USR-TAP-SEC-PRV-002 All applications SHOULD be open-source software.

5.5.1.2. Acceptance criteria

• All applications are open-source software when possible.

5.6. Log files

5.6.1. Log files storage

5.6.1.1. Features

• USR-TAP-SEC-LOG-001 The OS MUST store log files regarding system services.
• USR-TAP-SEC-LOG-002 The solution MAY be a remote storage or aggregator.

5.6.1.2. Acceptance criteria

• The system logs activity.

5.6.2. Log file rotation

• USR-TAP-SEC-LOG-003 The log files MUST NOT occupy more than a set space on disk.
• USR-TAP-SEC-LOG-004 Log files MUST be compressed after 1 week.

5.6.3. Log file retention

• USR-TAP-SEC-LOG-005 The OS MUST store log files locally for one month.

5.7. Compliance

5.7.1. Security recommendations

5.7.1.1. Features

• USR-TAP-SEC-REC-001 The OS hardening measures MUST be expressed with respect to the hardening guide published by the French ANSSI.

5.7.1.2. Acceptance criteria

• The hardening measures can be sorted by M I R E levels.