Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sxjBm-00ByYy-Q8 for pgsql-admin@arkaria.postgresql.org; Mon, 07 Oct 2024 08:33:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sxjBl-0084c8-2u for pgsql-admin@arkaria.postgresql.org; Mon, 07 Oct 2024 08:33:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sxjBk-0084c0-Lp for pgsql-admin@lists.postgresql.org; Mon, 07 Oct 2024 08:33:56 +0000 Received: from mail-lj1-x231.google.com ([2a00:1450:4864:20::231]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sxjBh-002vML-Ih for pgsql-admin@lists.postgresql.org; Mon, 07 Oct 2024 08:33:54 +0000 Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2fabd2c4ac0so43459541fa.1 for ; Mon, 07 Oct 2024 01:33:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1728290031; x=1728894831; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=zMEIQqx2GQHhMWOvErbVrWTIxGZUtIzr/VJ8/9hvzko=; b=gooX/JmLSSbMtIYcMLfbETDuuQfp1KupKnO8a2xwhswnpaTWZDnAFbN0zssV/qBVsv z+znzDPyZtEvkIfiJfspOeM1NPnyeXXFpdRiisjrbJm1wzKLlPIm8AKtaeWznCJREUBw 5lZvOzLYX5udBmpRDaozZeaOLOnDuLMWUkCCeQtIHTVDvOpTBta4MRpyzkmyAsTA6vNg cR4oqANNQR1Ast+tn0uEvbcRnvF1hEYCx1z4QNmCuHE4LdRrCflgwhiU+iq0/vdTgDDI oRLu2LKAtUKW84fiaprHGJMq7s8B4fYr6F9o0Etbn0gFkv37Iksir0t9iA2a06lH8xvE NGjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728290031; x=1728894831; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=zMEIQqx2GQHhMWOvErbVrWTIxGZUtIzr/VJ8/9hvzko=; b=b1G8xBN6Hu6fg9xPUcTf/fLDUnCoA8BL4xc7UcexEyk5Z+7IbNojfnuXaOg1xgcVG0 SJ9VGgfVMwlscLXZE+y6D1aTfpgkeSbQJQqSwB5sIGxz5zlHMVYN/irVHNkvmuZUeNoO gji40vXFq+D9hxtVU1Dr50B1VY+M0p5nIAyNk8/idGK4w9dl2DaJpZkJw08PjqZh5hkX fvxfWELeh/sL17A6/v8c9CdicG3vI4xBcnEDr+XtnT7WRFwoFQPGBDYRZ43V0s3MpCnV aN34+BMqAm5/zx5UMCkc9Juk3sHiDflxaj8X2R45tppkYUUd85Qy02wNuaFquaALuK+M SSdg== X-Gm-Message-State: AOJu0YzkoVH+WogJyeF/tiTopxdsA9T7MNbtbHSd10D8G+WJrGQt1Oqy xv/c3lJkGireZfaR4feA3dtfsd5qFLZ0AcwJslS+4MzI6tMfwf9MD4oLomFto6a27mELVGrWRM0 Gdd43uNvUHmCqeG8Hge0q+hxpwQehqDp0 X-Google-Smtp-Source: AGHT+IGeRtIFVJxTSoDAl7gUlax4EBMsbx1hRQ16YLgP6XPcOwSoiu7PDfJQkVfT4+Px8oKzL7w2OHC5VbYkUYFGdK4= X-Received: by 2002:a05:651c:a0b:b0:2f3:eeab:7f17 with SMTP id 38308e7fff4ca-2faf3da5956mr45702721fa.41.1728290031326; Mon, 07 Oct 2024 01:33:51 -0700 (PDT) MIME-Version: 1.0 From: pramod kg Date: Mon, 7 Oct 2024 14:03:24 +0530 Message-ID: Subject: Ensure 'User' Runtime Parameters are Configured To: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000062dd3c0623dee10e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000062dd3c0623dee10e Content-Type: text/plain; charset="UTF-8" Hi All, There is a requirement to monitor run time parameters and revert back changes (As per CIS Benchmark report). Requirement is to monitor user session parameter changes. How to achieve this? Any guidance is appreciated Complete remediation given by CIS benchmark is as follows: In the matter of a user session, the login sessions must be validated that it is not executing undesired parameter changes. In the matter of attributes that have been changed in entities, they must be manually reverted to its default value(s). Regards, Pramod --00000000000062dd3c0623dee10e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All,

There is a requirement=C2=A0to = monitor run time parameters and revert back changes (As per CIS Benchmark r= eport). Requirement is to monitor user session parameter changes. How to ac= hieve this? Any guidance=C2=A0is appreciated

Compl= ete remediation given by CIS benchmark is as follows:

In the matter of a user session, the login sessions must be validat= ed that it is not executing
undesired parameter changes. In the matter o= f attributes that have been changed in
entities, they must be manually r= everted to its default value(s).


Regards,
Pramod
--00000000000062dd3c0623dee10e--