From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Encryption in pg_dump
Date: Thu, 23 Jul 2020 02:17:54 -0500
Message-ID: <a91e4430-6e74-2980-b914-7a045d3636ad@gmail.com> (raw)
In-Reply-To: <CAJ7S9TW2j7Dk3k62_b_oZg9X=7jKMyLuebcBgtj0aWjSjzGJTw@mail.gmail.com>
References: <CAD7GeHRZ3tu8y9VG_0juVK3RQq6r+t6HciguEz_C8Eh85Hmq3A@mail.gmail.com>
<2BCA8D4B-E94D-4F2F-99A5-D783912A1CDF@gmail.com>
<20200722185541.GE3899@momjian.us>
<6D40812C-3F42-41A2-A548-4EC7754DF473@gmail.com>
<87zh7qbxqk.fsf@gmail.com>
<CAJ7S9TW2j7Dk3k62_b_oZg9X=7jKMyLuebcBgtj0aWjSjzGJTw@mail.gmail.com>
On 7/23/20 1:58 AM, Olivier Gautherot wrote:
> Hi all,
>
> Le jeu. 23 juil. 2020 à 07:34, Tim Cross <theophilusx@gmail.com
> <mailto:theophilusx@gmail.com>> a écrit :
>
>
> Paul Förster <paul.foerster@gmail.com
> <mailto:paul.foerster@gmail.com>> writes:
>
> > Hi Bruce,
> >
> >> On 22. Jul, 2020, at 20:55, Bruce Momjian <bruce@momjian.us
> <mailto:bruce@momjian.us>> wrote:
> >>
> >> Does anyone know why we are getting so many requests for encrypting
> >> dumps all of a sudden?
> >
> > probably because a) people don't read past posts and b) more and
> more IT heads decide that *everything*, be it internal to the company
> or not, has to be encrypted.
> >
>
> Yes, I think the IT heads issue is the primary driver - combined with
> very poor understanding of information security at senior levels and a
> huge growth of poor quality and 'snake oil salesmen' in the IT
> security space
> due to the amount of money ill informed senior managers are throwing at
> what they think is a technical problem which usually is in fact a
> business process problem.
>
>
> The root cause is probably that, if you can't separate sensitive
> information, you must encrypt everything - hence the dump. It may be a
> sign of bad design to start with, with data at rest not protected in the
> first place. It may also be a sign of "encrypt everything to be safe" as a
> false perception of security, increasing the attack surface instead of
> reducing it. And we could carry on with this list.
>
> Put it on the account of GDPR, as compliance is not an easy job.
>
When Oracle, SQL Server and MySQL Enterprise all have Transparent Data
Encryption, the expectation is that all databases should have TDE.
Auditors and IT upper management don't really understand the limitations of
TDE, but that does not matter. The magic word *Encryption* is in there, and
that means they like it
Adding hooks into libgpgme from pg_dump and pg_restore (needed for
--format=directory) would be *Very Helpful*.
--
Angular momentum makes the world go 'round.
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Encryption in pg_dump
In-Reply-To: <a91e4430-6e74-2980-b914-7a045d3636ad@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