Blame SOURCES/scap-security-guide-0.1.55-add_selector_for_R29-PR_6553.patch

d10e36
From 4d67a36c0a07ef8e07b8760b0e883bd42c0177ec Mon Sep 17 00:00:00 2001
d10e36
From: Watson Sato <wsato@redhat.com>
d10e36
Date: Thu, 21 Jan 2021 11:04:05 +0100
d10e36
Subject: [PATCH] Add variable selector and notes for R29
d10e36
d10e36
---
d10e36
 controls/anssi.yml | 14 +++++++++++++-
d10e36
 1 file changed, 13 insertions(+), 1 deletion(-)
d10e36
d10e36
diff --git a/controls/anssi.yml b/controls/anssi.yml
d10e36
index dec9d68c99..3303d70295 100644
d10e36
--- a/controls/anssi.yml
d10e36
+++ b/controls/anssi.yml
d10e36
@@ -521,10 +521,22 @@ controls:
d10e36
     description: >-
d10e36
       Remote user sessions (shell access, graphical clients) must be closed
d10e36
       after a certain period of inactivity.
d10e36
+    notes: >-
d10e36
+      There is no specific capability to check remote user inactivity, but some shells allow the
d10e36
+      session inactivity time out to be configured via TMOUT variable.
d10e36
+      In OpenSSH < 8.2 the inactivity of the user is implied from the network inactivity.
d10e36
+      The server is configured to disconnect sessions if no data has been received within the idle timeout,
d10e36
+      regardless of liveness status (ClientAliveCountMax is 0 and ClientAliveInterval is > 0).
d10e36
+      In OpenSSH >= 8.2 there is no way to disconnect sessions based on client liveness.
d10e36
+      The semantics of "ClientAliveCountMax 0" has changed from "disconnect on first timeout" to
d10e36
+      "don't disconnect network inactive sessions". The server either probes for the client liveness
d10e36
+      or keeps inactive sessions connected.
d10e36
+    automated: yes
d10e36
     rules:
d10e36
     - accounts_tmout
d10e36
+    - var_accounts_tmout=10_min
d10e36
     - sshd_set_idle_timeout
d10e36
-    - sshd_idle_timeout_value=5_minutes
d10e36
+    - sshd_idle_timeout_value=10_minutes
d10e36
     - sshd_set_keepalive
d10e36
 
d10e36
   - id: R30