Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpxGy-0002Aa-Am for pgsql-general@arkaria.postgresql.org; Wed, 15 Aug 2018 14:59:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fpxGw-0003Ew-5C for pgsql-general@arkaria.postgresql.org; Wed, 15 Aug 2018 14:59:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fpxGY-0001P3-Tl; Wed, 15 Aug 2018 14:59:19 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fpxGV-0001xR-AM; Wed, 15 Aug 2018 14:59:16 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1fpxGS-00037N-Go; Wed, 15 Aug 2018 10:59:12 -0400 Date: Wed, 15 Aug 2018 10:59:12 -0400 From: Bruce Momjian To: Benedict Holland Cc: "David G. Johnston" , "bejita0409@yahoo.co.jp" , "pgsql-admin@lists.postgresql.org" , "pgsql-general@lists.postgresql.org" Subject: Re: How to revoke privileged from PostgreSQL's superuser Message-ID: <20180815145912.GA11573@momjian.us> References: <913907.28546.qm@web103014.mail.kks.yahoo.co.jp> <20180810194105.GD7840@momjian.us> <20180814195919.GA29140@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180814195919.GA29140@momjian.us> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Aug 14, 2018 at 03:59:19PM -0400, Bruce Momjian wrote: > On Fri, Aug 10, 2018 at 04:06:40PM -0400, Benedict Holland wrote: > > I also would take Bruce's comment with a massive grain of salt. Everything that > > everyone does on a database is logged somewhere assuming proper logging. Now do > > you have the person-power to go through gigs of plain text logs to find out if > > someone is doing something shady... that is a question for your management > > team. Also, if you suspect someone of doing something shady, you should > > probably revoke their admin rights.  > > Agreed, the best way to limit the risk of undetected DBA removal of data > is secure auditing --- I should have mentioned that. So, how do you securely audit? You ship the logs to a server that isn't controlled by the DBA, via syslog? How do you prevent the DBA from turning off logging when the want to so something undetected? Do you log the turning off of logging? -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +