feat(FSADT1-1281): add encryption to database

[paulushcgcj]

Description

As part of our Initial Security Risk assessment, one of the points raised was "Sensitive data exfiltration attack on the Postgres database".

We need to enhance the security of our PostgreSQL database by implementing encryption measures. This includes adding encryption at rest for the database, enabling connection encryption to ensure secure data transmission, and implementing field-level encryption for sensitive data.

• Connection Encryption:
  • Configure PostgreSQL to enforce SSL/TLS encryption for all client connections to the database.
  • Ensure that the SSL/TLS certificate is properly configured and valid.
• Field Encryption:
  • Identify sensitive fields in the database schema that require encryption, such as Personally Identifiable Information (PII).
  • Implement field-level encryption for the identified sensitive fields, ensuring that data is encrypted before being stored in the database and decrypted when retrieved.

Type of change

• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

• Manual tests (description below)
• Updated existing tests

For test, a user can log into the database pod and check the encrypted columns without passing the key

Checklist

• I have read the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

Further comments

---

Thanks for the PR!

Deployments, as required, will be available below:
Any successful deployments (not always required) will be available here

Please create PRs in draft mode. Mark as ready to enable:

• Analysis Workflow

After merge, new images are deployed in:

• Merge Workflow

[github-actions]

Current changelog

Features

• FSADT1-1281: enabling pgcrypto on database (672b8b0)