Re: Ensure 'User' Runtime Parameters are Configured

From: Muhammad Usman Khan <usman(dot)k(at)bitnine(dot)net>
To: pramod kg <pramod11287(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Ensure 'User' Runtime Parameters are Configured
Date: 2024-10-08 03:20:59
Message-ID: CAPnRvGsbFQt5sUYH-QgMyKHs7F8T2oOH8BAMzrWg84pNZq+psA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,
There is not a predefined method to achieve this but you can get your
desired output by implementing the following logics:

- Enable Detailed Logging by setting the following parameters in
postgresql.conf file:
logging_collector = on
log_statement = 'all'
log_duration = on
- Implement Auditing with pgaudit
- Restrict Privileges
- Automated Reversion:
Schedule a job that compares current settings with default_parameters
and reverts any discrepancies.

On Mon, 7 Oct 2024 at 13:33, pramod kg <pramod11287(at)gmail(dot)com> wrote:

> 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
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Sameer Malve 2024-10-08 08:24:11 RHEL certified repo provided PostgreSQL Major Version Upgrade.
Previous Message Sam Stearns 2024-10-07 15:36:30 Re: Same Table Name - 2 Owners