On 2019-06-06 23:51:02 +, Jan Bilek wrote:
> Process For Managing Secure Data With PostgreSQL
[...]
> Another process running with permissions to access the underlying data is then
> running (probably running as postgres user):
>
> 1. Run the following forever:
>
> a. Wait for pending_s
Thank you all - Karsten, Benjamin, Pavel, PostgreSql team,
I've discussed all your inputs with our developers and they came with a
solution for this problem, which was already agreed (on a high level) by our
auditor.
I am adding it here so it can inspire the others, when potentially getting in
On Thu, Jun 06, 2019 at 11:41:40AM +0700, Benjamin Scherrey wrote:
> You should never store such information
> in a database product unless you plan of decommissioning ALL of the media
> that stores the information once you're supposed to lose custody.
Use a tablespace on a dedicated disk.
Move
:57 AM Jan Bilek wrote:
> Hi,
>
> We've build a Payments Authorisation system (Box solution) on Postgresql
> database and now we are hitting following issue with our PA:DSS audit -
> requirement PA-DSS 1.1.4:
>
> <>
> 1.1.4 Securely delete any track data (from th
:56:47+10:00 Jan Bilek wrote:
>
> Hi,
>
> We've build a Payments Authorisation system (Box solution) on Postgresql
> database and now we are hitting following issue with our PA:DSS audit -
> requirement PA-DSS 1.1.4:
>
> <>
> 1.1.4 Securely delete any
ase and now we are hitting following issue with our PA:DSS audit -
requirement PA-DSS 1.1.4:
<>
1.1.4 Securely delete any track data (from the magnetic stripe or equivalent
data contained on a chip), card verification values or codes, and PINs or PIN
block data stored by previous ver
Hi,
We've build a Payments Authorisation system (Box solution) on Postgresql
database and now we are hitting following issue with our PA:DSS audit -
requirement PA-DSS 1.1.4:
<>
1.1.4 Securely delete any track data (from the magnetic stripe or equivalent
data contained on a
