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: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration
Date: Wed, 21 Dec 2022 17:10:00 -0600
Message-ID: <2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@gmail.com> (raw)
In-Reply-To: <CAD+mzowEcJ9==68MkZd7vFUVHuJPGQsrx=ztQp7Sp1T5M0TeoQ@mail.gmail.com>
References: <MAXPR01MB2688CFCA349F11FAD7B495EB9EEB9@MAXPR01MB2688.INDPRD01.PROD.OUTLOOK.COM>
	<285552b7273f57396398e5f7c538c7c4be60dce7.camel@cybertec.at>
	<69C40063-CF22-44FE-958A-74845CFBB039@ultra-secure.de>
	<CAD+mzowEcJ9==68MkZd7vFUVHuJPGQsrx=ztQp7Sp1T5M0TeoQ@mail.gmail.com>

If a hacker gets in with root access, they can copy /your/ (and my) 
Postgresql database files (or, more easily, the backup files) off site, 
restore them, and then have access to your database.  Not so much 
TDE-encrypted databases, since the backups are encrypted too and you need 
the key to decrypt them,

As for the Bad Things which happen if you lose the keys... well, *don't lose 
the keys!!*

On 12/21/22 16:25, Benedict Holland wrote:
> What would you be missing? You can encrypt databases. You can encrypt the 
> s3 buckets using kms. You can govern access via ssh Auth. When you do 
> backups, you can encrypt the tar.gz files or whatever format and store it 
> on s3. Same with the wal files. The fact that oracle charges for this is a 
> joke. Of course, you would need to ensure compliance with your opsec teams 
> and stuck with best security practices but it seems top to bottom 
> encryption is unrelated or tangentially related to the databases.
>
> Also, if you lose the encryption keys for your backups then bad things 
> happen. I doubt what I did was production viable but I limited database 
> access to a handful of users, encrypted the disks, left the Wal files 
> unencrypted but mounted with read access for a single user, compressed 
> full backups with encryption and a password, generated sah keys for anyone 
> who needed service accounts to access the systems, enforced database 
> ownership permissions, and and gave server access to a tiny team with 2fa. 
> The way 8 figured it, if someone somehow rooted the box we were screwed 
> anyway.
>
> For an internal database, this seemed sufficient. For an external 
> database, I would highly recommend paid consulting security firms or hire 
> people who know to build an externally facing platform.
>
> Thanks
> Ben
>
> On Wed, Dec 21, 2022, 4:39 PM Rainer Duffner <rainer@ultra-secure.de> wrote:
>
>
>
>>     Am 21.12.2022 um 22:34 schrieb Laurenz Albe <laurenz.albe@cybertec.at>:
>>
>>     There is no exact equivalent, but there is something similar and much
>>     better: you can
>>     authenticate the client with SSL client certificates:
>>     https://www.postgresql.org/docs/current/auth-cert.html
>
>
>     Isn’t the wallet the part where the encryption keys are stored?
>
>     Indeed, one of the few remaining features that only Oracle (and of
>     course other commercial RDMSs) has seems to be full HSM support for TDE.
>
>
>     Rainer
>

-- 
Angular momentum makes the world go 'round.

view thread (14+ messages)  latest in thread

Message-ID: <2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@gmail.com>
Permalink:  ../2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@gmail.com/
Also on:    postgresql.org/message-id/2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@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: Regd. the Implementation of Wallet (in Oracle) config equivalent in postgreSQL whilst the database migration
  In-Reply-To: <2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@gmail.com>
  References: <MAXPR01MB2688CFCA349F11FAD7B495EB9EEB9@MAXPR01MB2688.INDPRD01.PROD.OUTLOOK.COM> <285552b7273f57396398e5f7c538c7c4be60dce7.camel@cybertec.at> <69C40063-CF22-44FE-958A-74845CFBB039@ultra-secure.de> <CAD+mzowEcJ9==68MkZd7vFUVHuJPGQsrx=ztQp7Sp1T5M0TeoQ@mail.gmail.com> <2b9e2d41-9eb8-7ab9-0cb7-816b9eb1cef1@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