Blame SOURCES/scap-security-guide-0.1.55-add_notes_and_rule_for_R35-PR_6548.patch

618a7c
From cb299dd0ce870d55cb530bc5e5ad9a9f52734bf4 Mon Sep 17 00:00:00 2001
618a7c
From: Watson Sato <wsato@redhat.com>
618a7c
Date: Tue, 19 Jan 2021 09:42:26 +0100
618a7c
Subject: [PATCH] Add metadata to ANSSI R35
618a7c
618a7c
Current implementation cannot diferentiate between system and
618a7c
standard user umask, they are both set to the same value.
618a7c
---
618a7c
 controls/anssi.yml | 8 ++++++++
618a7c
 1 file changed, 8 insertions(+)
618a7c
618a7c
diff --git a/controls/anssi.yml b/controls/anssi.yml
618a7c
index dec9d68c99..621996e985 100644
618a7c
--- a/controls/anssi.yml
618a7c
+++ b/controls/anssi.yml
618a7c
@@ -572,10 +572,18 @@ controls:
618a7c
       only be read by the user and his group, and be editable only by his owner).
618a7c
       The umask for users must be set to 0077 (any file created by a user is
618a7c
       readable and editable only by him).
618a7c
+    notes: >-
618a7c
+      There is no simple way to check and remediate different umask values for
618a7c
+      system and standard users reliably.
618a7c
+      The different values are set in a conditional clause in a shell script
618a7c
+      (e.g. /etc/profile or /etc/bashrc).
618a7c
+      The current implementation checks and fixes both umask to the same value.
618a7c
+    automated: partially
618a7c
     rules:
618a7c
     - var_accounts_user_umask=077
618a7c
     - accounts_umask_etc_login_defs
618a7c
     - accounts_umask_etc_profile
618a7c
+    - accounts_umask_etc_bashrc
618a7c
 
618a7c
   - id: R36
618a7c
     title: Rights to access sensitive content files