From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
To: pgsql-general <pgsql-general@postgresql.org>
Subject: Re: Exclude certain application pgaudit logging?
Date: Tue, 6 Feb 2024 10:18:12 -0800
Message-ID: <2beb61a5-903a-4caf-ac97-d4c2ef9b62f7@aklaver.com> (raw)
In-Reply-To: <CANzqJaAav-ycVS3zAGFsCD-1ft=2xUcNqXcihZk57=s4qhUZiw@mail.gmail.com>
References: <CANzqJaAav-ycVS3zAGFsCD-1ft=2xUcNqXcihZk57=s4qhUZiw@mail.gmail.com>
On 2/6/24 10:11 AM, Ron Johnson wrote:
> Currently, we use Object audit logging to capture all READ access to
> columns FOO_1, FOO_2 and FOO_3 in table BAR.SCRABBLE. (They are the
> three columns have PII data.)
Using what audit software?
>
> The problem is that the application legitimately reads these columns
> thousands of times per day. Thus, the log fills up with meaningless
> data that swamps any legitimate invalid accesses.
How do you know they are legitimate requests?
>
> Thus, I'd like to exclude reads from "Postgresql JDBC Driver".
> (Currently, I filter that out using "grep -v" in a shell script
> that runs hourly from cron, but I find that unsatisfactory.)
--
Adrian Klaver
adrian.klaver@aklaver.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, ronljohnsonjr@gmail.com
Subject: Re: Exclude certain application pgaudit logging?
In-Reply-To: <2beb61a5-903a-4caf-ac97-d4c2ef9b62f7@aklaver.com>
References: <CANzqJaAav-ycVS3zAGFsCD-1ft=2xUcNqXcihZk57=s4qhUZiw@mail.gmail.com> <2beb61a5-903a-4caf-ac97-d4c2ef9b62f7@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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