pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedEnable DB level audit trail
8+ messages / 4 participants
[nested] [flat]
* Enable DB level audit trail
@ 2024-04-08 06:00 Siraj G <tosiraj.g@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Siraj G @ 2024-04-08 06:00 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hello Admins!
How do we enable DB level audit trail in PgSQL?
Regards
Siraj
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-08 07:56 Siraj G <tosiraj.g@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
1 sibling, 1 reply; 8+ messages in thread
From: Siraj G @ 2024-04-08 07:56 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Also, I would like to understand the implications of enabling the DB audit.
Appreciate the help.
Regards
Siraj
On Mon, Apr 8, 2024 at 11:30 AM Siraj G <tosiraj.g@gmail.com> wrote:
> Hello Admins!
>
> How do we enable DB level audit trail in PgSQL?
>
> Regards
> Siraj
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-08 12:53 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
1 sibling, 0 replies; 8+ messages in thread
From: Ron Johnson @ 2024-04-08 12:53 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
On Mon, Apr 8, 2024 at 2:01 AM Siraj G <tosiraj.g@gmail.com> wrote:
> Hello Admins!
>
> How do we enable DB level audit trail in PgSQL?
>
pgaudit.
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-08 12:54 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
0 siblings, 1 reply; 8+ messages in thread
From: Ron Johnson @ 2024-04-08 12:54 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Lots of extra stuff in the postgresql log files.
On Mon, Apr 8, 2024 at 3:56 AM Siraj G <tosiraj.g@gmail.com> wrote:
> Also, I would like to understand the implications of enabling the DB audit.
>
> Appreciate the help.
>
> Regards
> Siraj
>
> On Mon, Apr 8, 2024 at 11:30 AM Siraj G <tosiraj.g@gmail.com> wrote:
>
>> Hello Admins!
>>
>> How do we enable DB level audit trail in PgSQL?
>>
>> Regards
>> Siraj
>>
>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-16 17:32 Siraj G <tosiraj.g@gmail.com>
parent: Ron Johnson <ronljohnsonjr@gmail.com>
0 siblings, 2 replies; 8+ messages in thread
From: Siraj G @ 2024-04-16 17:32 UTC (permalink / raw)
To: Ron Johnson <ronljohnsonjr@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Thank you Ron.
Would it be good to use trigger based auditing or via pgAudit?
All we want is to capture changes in a few tables.
Regards
Siraj
On Mon, Apr 8, 2024 at 6:24 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
> Lots of extra stuff in the postgresql log files.
>
> On Mon, Apr 8, 2024 at 3:56 AM Siraj G <tosiraj.g@gmail.com> wrote:
>
>> Also, I would like to understand the implications of enabling the DB
>> audit.
>>
>> Appreciate the help.
>>
>> Regards
>> Siraj
>>
>> On Mon, Apr 8, 2024 at 11:30 AM Siraj G <tosiraj.g@gmail.com> wrote:
>>
>>> Hello Admins!
>>>
>>> How do we enable DB level audit trail in PgSQL?
>>>
>>> Regards
>>> Siraj
>>>
>>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-16 18:01 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Siraj G <tosiraj.g@gmail.com>
1 sibling, 1 reply; 8+ messages in thread
From: Ron Johnson @ 2024-04-16 18:01 UTC (permalink / raw)
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
"Audit tables" are tables just like any other table, which means they can
be changed by anyone with a superuser ROLE.
pgaudit and Qradar rsyslog is how you unalterably track table changes.
That, of course, means you need the Qradar software on another server, etc,
etc, etc.
But if lawyers and security compliance officers don't care... then sure,
triggers and "audit tables" work just fine. I recommend adding a timestamp
and "action code" ('I'=insert, 'U'=update, 'D'=delete) to the audit tables
in addition to cloning the base table's columns.
On Tue, Apr 16, 2024 at 1:32 PM Siraj G <tosiraj.g@gmail.com> wrote:
> Thank you Ron.
> Would it be good to use trigger based auditing or via pgAudit?
> All we want is to capture changes in a few tables.
>
> Regards
> Siraj
>
> On Mon, Apr 8, 2024 at 6:24 PM Ron Johnson <ronljohnsonjr@gmail.com>
> wrote:
>
>> Lots of extra stuff in the postgresql log files.
>>
>> On Mon, Apr 8, 2024 at 3:56 AM Siraj G <tosiraj.g@gmail.com> wrote:
>>
>>> Also, I would like to understand the implications of enabling the DB
>>> audit.
>>>
>>> Appreciate the help.
>>>
>>> Regards
>>> Siraj
>>>
>>> On Mon, Apr 8, 2024 at 11:30 AM Siraj G <tosiraj.g@gmail.com> wrote:
>>>
>>>> Hello Admins!
>>>>
>>>> How do we enable DB level audit trail in PgSQL?
>>>>
>>>> Regards
>>>> Siraj
>>>>
>>>
^ permalink raw reply [nested|flat] 8+ messages in thread
* Re: Enable DB level audit trail
@ 2024-04-16 18:11 GF <phabriz@gmail.com>
parent: Ron Johnson <ronljohnsonjr@gmail.com>
0 siblings, 0 replies; 8+ messages in thread
From: GF @ 2024-04-16 18:11 UTC (permalink / raw)
To: Ron Johnson <ronljohnsonjr@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Il mar 16 apr 2024, 20:01 Ron Johnson <ronljohnsonjr@gmail.com> ha scritto:
"Audit tables" are tables just like any other table, which means they can
be changed by anyone with a superuser ROLE.
... and trigger-based audit interferes with the transaction: think of an
exception while auditing, it would rollback also the statement(s) it was
tracking.
giovanni
^ permalink raw reply [nested|flat] 8+ messages in thread
* Enable DB level audit trail
@ 2024-04-16 18:23 Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
parent: Siraj G <tosiraj.g@gmail.com>
1 sibling, 0 replies; 8+ messages in thread
From: Wetmore, Matthew (CTR) @ 2024-04-16 18:23 UTC (permalink / raw)
To: Siraj G <tosiraj.g@gmail.com>; Ron Johnson <ronljohnsonjr@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Create a _hist table
From: Siraj G <tosiraj.g@gmail.com>
Sent: Tuesday, April 16, 2024 10:32 AM
To: Ron Johnson <ronljohnsonjr@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: [EXTERNAL] Re: Enable DB level audit trail
Thank you Ron.
Would it be good to use trigger based auditing or via pgAudit?
All we want is to capture changes in a few tables.
Regards
Siraj
On Mon, Apr 8, 2024 at 6:24 PM Ron Johnson <ronljohnsonjr@gmail.com<mailto:ronljohnsonjr@gmail.com>> wrote:
Lots of extra stuff in the postgresql log files.
On Mon, Apr 8, 2024 at 3:56 AM Siraj G <tosiraj.g@gmail.com<mailto:tosiraj.g@gmail.com>> wrote:
Also, I would like to understand the implications of enabling the DB audit.
Appreciate the help.
Regards
Siraj
On Mon, Apr 8, 2024 at 11:30 AM Siraj G <tosiraj.g@gmail.com<mailto:tosiraj.g@gmail.com>> wrote:
Hello Admins!
How do we enable DB level audit trail in PgSQL?
Regards
Siraj
^ permalink raw reply [nested|flat] 8+ messages in thread
end of thread, other threads:[~2024-04-16 18:23 UTC | newest]
Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-04-08 06:00 Enable DB level audit trail Siraj G <tosiraj.g@gmail.com>
2024-04-08 07:56 ` Siraj G <tosiraj.g@gmail.com>
2024-04-08 12:54 ` Ron Johnson <ronljohnsonjr@gmail.com>
2024-04-16 17:32 ` Siraj G <tosiraj.g@gmail.com>
2024-04-16 18:01 ` Ron Johnson <ronljohnsonjr@gmail.com>
2024-04-16 18:11 ` GF <phabriz@gmail.com>
2024-04-16 18:23 ` Wetmore, Matthew (CTR) <Matthew.Wetmore@evernorth.com>
2024-04-08 12:53 ` Ron Johnson <ronljohnsonjr@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox