Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsBS3-00GDgl-49 for pgsql-general@arkaria.postgresql.org; Wed, 12 Mar 2025 02:04:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tsBS1-00BVgq-FS for pgsql-general@arkaria.postgresql.org; Wed, 12 Mar 2025 02:04:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tsBS1-00BVg1-27 for pgsql-general@lists.postgresql.org; Wed, 12 Mar 2025 02:04:05 +0000 Received: from mail-oi1-x232.google.com ([2607:f8b0:4864:20::232]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tsBRy-002Kgw-1f for pgsql-general@lists.postgresql.org; Wed, 12 Mar 2025 02:04:03 +0000 Received: by mail-oi1-x232.google.com with SMTP id 5614622812f47-3eb6b16f1a0so1792207b6e.3 for ; Tue, 11 Mar 2025 19:04:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741745042; x=1742349842; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=8dka5ZgNpwgAtTpEj4DcNxcRsoeaIrjgxwtH33adinI=; b=cn4Rh4HYYVRxBOwK4qGVpnRwGuOKHJCXjNF5K4Fd8BnteLUuuomALBi2olMwTYRBCI eeP4erWCbufz0c/t9Xt2zhpSMleGD+EUjvmmHruafES/YEpY8nbgkljskzf/qs0bLO3r 439E0uUNpWm5tx3VB4wZoutHzM/RMARz9GQ+anX6Ch3F5vcuTZb0nstbW42BGpXRiykB r5Elnt+JrxqC9UFFGMjNuNlGlK3Fxj3+fFqCyCvU3UgckON7sRCNe5UHUw8qsT+nxsbk 286cqTI4fJJBCOAuxEAEIu5c60mJXLrs4pJiBBzWw+OrSlWOMDORIFHgh0ZBYM+IK+5V BMRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741745042; x=1742349842; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=8dka5ZgNpwgAtTpEj4DcNxcRsoeaIrjgxwtH33adinI=; b=jKgZmRIiyDn0QQzWbi5sWNteWOSJvkSxltOe8hqL8LonXHynBrH6Jm2irTEYFAr9hD 9PdNHfglsngFOn3RHekIk/1EutcZVrwVLdWwmzibKE/67XO591Tkf9QbqLT5ffyce2Mb 3pfFItjfiSJcnSj3XAzDZIukJQScryvpvt/ka68AgPIabuZp32w5mP1P7rhzOkAhnDc6 gN5oBAeioJ53ldVLBJozHw+rKUEZH9PWphsNBL4eTNFlZfBcE23kYRRPfQgD4wZQ0DV8 bGis8uFcWMd74sZMzrpuW5b6HTnOJUMqZC5KNU9PCBjGVS01FcB61Krqj1zjb6/5kB21 yaXA== X-Gm-Message-State: AOJu0YwdHNuDLhs+zCwaev5tkVbkmenJRFP9i5VRqZOsbGe6m/T1hKHr Uetr87v583Vm7Tn09efvg/sP8rlX9nYbPsoGjeIKck3pYbSv7fx1D8S5ZweHn1ROzmg+CuGIIZT 4XypMgVmePuWGUASA0qd5rEcpbJb9cQ== X-Gm-Gg: ASbGncuYgZFr9JBDkady8xd0g951oJADdY+p21VSk4oQ9VrDhqIuPDibZipXWxCNsjK vjAiBV+l9jc1pIrTHstPvlqvcTATK9CjBkQQPAzxAgQSeGuEMbdKSxUduPk7UHBXgu8rbuiS6/8 4oMAAumCcvaoVZqDbsZSm/0fInELhAJwJqOAxG3oGd8bfCq8YqDdu665M9caCo4+HX+NlE/A== X-Google-Smtp-Source: AGHT+IEXYV+BM40S2FO/cXeMKvBypJDeykr2goXpJIjV8wuc7/Y/FGTCso803mRbOB5+OXs+exGDnhistTqIL+nFm44= X-Received: by 2002:a05:6808:2e8d:b0:3fa:adc7:1ab with SMTP id 5614622812f47-3faadc70538mr2415086b6e.17.1741745041703; Tue, 11 Mar 2025 19:04:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 11 Mar 2025 22:03:50 -0400 X-Gm-Features: AQ5f1JoTQg5WHMFtp-XrfoL7Ht5CMk0uZfcg8x5YxnD1nsbmgpYTyfx_NaUy62k Message-ID: Subject: Re: hide data from admins To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000800c5106301b9e0f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000800c5106301b9e0f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Mar 11, 2025 at 9:48=E2=80=AFPM Siraj G wrote= : > Hello Experts! > > What are the features available in Postgresql to hide PII (personal > identifiable information) from the Admin team? Like in Oracle we have dat= a > vault and data redaction, I am looking for similar features in > PostgreSQL.We do not want to do code level changes. > Look at pgsodium. However, "no code level changes" is code for at-rest encryption. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000800c5106301b9e0f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Mar 11, 2025 at 9:48=E2=80=AFPM S= iraj G <tosiraj.g@gmail.com&g= t; wrote:
Hello=C2=A0Experts!=

What are the features available in Postgresql to hi= de PII (personal identifiable information) from the Admin team? Like in Ora= cle we have data vault and data redaction, I am looking for similar feature= s in PostgreSQL.We do not want to do code level changes.

Look at pgsodium.=C2=A0 However, "no code le= vel changes" is code for at-rest encryption.

--
Death to <Redacted>, and butte= r sauce.
Don't boil me, I'm still alive.
<Redac= ted> lobster!
--000000000000800c5106301b9e0f--