From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Securing Information |
Date: | 2016-12-28 18:13:06 |
Message-ID: | CANu8FixBk_D-3_Vg2ENhz1djVssqL2EvSCCueJhq9AX1tJNgPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Dec 28, 2016 at 11:49 AM, Rich Shepard <rshepard(at)appl-ecosys(dot)com>
wrote:
> On Tue, 27 Dec 2016, Chris Weekes wrote:
>
> I was wondering what steps if any need to be taken to ensure that the
>> patient and operational data is secure on a machine and or across the
>> network.
>>
>
> Chris,
>
> I'm far from an expert but until more knowledgeable folks respond I'll
> offer a couple of quick suggestins. First, in your postgres data/ directory
> modify pg_hba.conf. Specifying hostssl and an appropriate authentication
> method
> will help. Second, partition your users into postgres role specifying what
> each role can access and do.
>
> The postgresql-9.6-US.pdf manual has all the details.
>
> HTH,
>
> Rich
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
*Another thing to consider is DO NOT create your tables in the public
schema.Instead, create a separate schema, then only grant access to that
schema and tablesto users that are authorized to access them.*
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Moench-Tegeder | 2016-12-28 19:20:45 | Re: LYDB: What advice about stored procedures and other server side code? |
Previous Message | Steven Grimm | 2016-12-28 16:58:24 | Row value expression much faster than equivalent OR clauses |