On Fri, Feb 16, 2024 at 4:04 PM sud wrote:
>
> Yes these are Account number/PCI data and "data at rest" encryption is
> something management is asking to have irrespective of whether we encrypt
> those before storing in the database or not. And this system needs to
> adhere to PCI 4.0 standards ,
On Fri, Feb 16, 2024 at 4:04 PM sud wrote:
> On Fri, Feb 16, 2024 at 10:50 PM Greg Sabino Mullane
> wrote:
>
>> You need to clearly define your threat model. What exactly are you
>> defending against? What scenario do you want to avoid?
>>
>> Also, your decision of on-premise or Aurora is extrem
On Fri, Feb 16, 2024 at 10:50 PM Greg Sabino Mullane
wrote:
> You need to clearly define your threat model. What exactly are you
> defending against? What scenario do you want to avoid?
>
> Also, your decision of on-premise or Aurora is extremely relevant to your
> range of options.
>
>
Thank you
On Fri, Feb 16, 2024 at 1:53 AM sud wrote:
> Hello Friends,
>
> We are newly moving to postgres database (yet to decide if it would be an
> on premise one or AWS aurora postgres). However , we want to understand
> what encryption / decryption techniques are available in the postgres
> database.
The phrases "personal information" and "data at rest encryption" strongly
indicate PCI, or something similar.
On Fri, Feb 16, 2024 at 12:20 PM Greg Sabino Mullane
wrote:
> You need to clearly define your threat model. What exactly are you
> defending against? What scenario do you want to avoid?
You need to clearly define your threat model. What exactly are you
defending against? What scenario do you want to avoid?
Also, your decision of on-premise or Aurora is extremely relevant to your
range of options.
Cheers,
Greg
Hello Friends,
We are newly moving to postgres database (yet to decide if it would be an
on premise one or AWS aurora postgres). However , we want to understand
what encryption / decryption techniques are available in the postgres
database.
We may have some sensitive/"personal information" (lik
