pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Postgres limitation in user management
Date: Sat, 4 Nov 2023 17:02:26 -0500
Message-ID: <9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.com> (raw)
In-Reply-To: <20231104215321.ojqhqo346bbsistg@hjp.at>
References: <SJ0PR03MB6304FF2873FD903C710CE8C283A5A@SJ0PR03MB6304.namprd03.prod.outlook.com>
	<20231104213303.4mtgamfyo4v5i33e@hjp.at>
	<SY4PR01MB7076F7F028CE147EC66F918DA1A4A@SY4PR01MB7076.ausprd01.prod.outlook.com>
	<20231104215321.ojqhqo346bbsistg@hjp.at>

On 11/4/23 16:53, Peter J. Holzer wrote:
> On 2023-11-04 21:42:34 +0000, Brent Wood wrote:
>>>> We have 2 sets of database user groups –
>>>>
>>>>   1. App – who owns the application schemas (and tables)
>>>>   2. Support – who provides db support
>>>>
>>>> We want Support users to have no SELECT or DML privilege but only ALTER
>> TABLE
>>>> to perform any troubleshooting in the database.
>>> This seems strange to me. What kind of troubleshooting requires to
>>> ability to ALTER TABLE but not to do DML?
>> Where your db admin & data admin are separated. Data security issues can
>> require minimal access to data, which a dba does not necessarily require.
>> Especially when the DBA role is contracted out.
>>
>> Sort of along this line, we have offloaded user management to AD, so our DB
>> user management is now carried out via in-house IT, who are not DBA's and have
>> no access to data.
> This doesn't answer the question why ALTER TABLE privilege would be
> required.

I bet the Good Idea Fairy whispered something into the CISO's ear.

-- 
Born in Arizona, moved to Babylonia.





view thread (8+ messages)  latest in thread

Message-ID: <9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.com>
Permalink:  ../9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.com/
Also on:    postgresql.org/message-id/9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.com

 · 

reply

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: ronljohnsonjr@gmail.com
  Subject: Re: Postgres limitation in user management
  In-Reply-To: <9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.com>
  References: <SJ0PR03MB6304FF2873FD903C710CE8C283A5A@SJ0PR03MB6304.namprd03.prod.outlook.com> <20231104213303.4mtgamfyo4v5i33e@hjp.at> <SY4PR01MB7076F7F028CE147EC66F918DA1A4A@SY4PR01MB7076.ausprd01.prod.outlook.com> <20231104215321.ojqhqo346bbsistg@hjp.at> <9faf2c18-5029-4d77-a937-ece6d25f9678@gmail.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