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 1rXQ1Y-00AYt1-Hn for pgsql-general@arkaria.postgresql.org; Tue, 06 Feb 2024 18:18:25 +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 1rXQ1X-005qJw-Mr for pgsql-general@arkaria.postgresql.org; Tue, 06 Feb 2024 18:18:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rXQ1V-005qJo-Vu for pgsql-general@lists.postgresql.org; Tue, 06 Feb 2024 18:18:23 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rXQ1S-005o3L-Eu for pgsql-general@postgresql.org; Tue, 06 Feb 2024 18:18:21 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 98BEF5C01EE; Tue, 6 Feb 2024 13:18:15 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Tue, 06 Feb 2024 13:18:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1707243495; x=1707329895; bh=7k355+2WX8vII5UVeX2D8GCA48sIWFNPCbN/fksWUbw=; b= Z6EWLycArkB/Wp99MJBYmBVsodeoHI3Q8cxt8lNFTBw2oSnyfVInnDmOxVM8YRDS VAQwdoYgVb3W5oTLINTp9ZoD8kpU8t9qehTdEwTEHDDvnaIjJnu1+HvcJFWZUNv9 R+TRgMRX2cMxBL7LCgJvCBStQrQJ2E3VnM0FAJ8RxpvafMCd3zdbqztcqVJkILaQ k9dEwfu0jNRDL+PoDREac3lxf3ecUACRpqa2s/kf48TauPJMHqd+79Mvw0a197Lk 0LXFnzpRpGoEUqegERi23qFPep8nJHsEsY0y6MExEadqBmXiu1PKvgfM35sh1r5I i6gMJ+k0LE4aXWSv4umydA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1707243495; x= 1707329895; bh=7k355+2WX8vII5UVeX2D8GCA48sIWFNPCbN/fksWUbw=; b=R TrN5Ohzf3ebCSWGeVA4a0dWjrurLRnd7NJ9A5aFgLb9X3ep7m9uCNnLhyViWIMej zspLcPCeQD928E8clePh5rvNMcG+6fXH4FWf1AD79giX5rqzoTnCT76tcmb/h8Po 49xseW7higN9uzYZ56v9/eJc/uT46omwjkkmAHi9X+/AFMlxMr85v+FhEk0Jppt4 1jilcPuq+i2e49e2jaJyKFqujN5f0K0aX2QpWGECf4eWAii33h/WHOLHdW9jggVg QyaVxo7uAbzeEj9Td4M5IhoKqhPRIoPjdRF4SfPHSQ4Z5kUpP7fsnF+7Pkz6S8ey TESy3CQPg7kQupnZAC2nQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrtddtgdekudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeffleegieefgf evudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheejheenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 6 Feb 2024 13:18:14 -0500 (EST) Message-ID: <2beb61a5-903a-4caf-ac97-d4c2ef9b62f7@aklaver.com> Date: Tue, 6 Feb 2024 10:18:12 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Exclude certain application pgaudit logging? To: Ron Johnson , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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