[Security] Harden pgaudit For Gids Database in Prod

[Efe-Oddball]

Description

DB scans from July reported that pgaudit.conf needs to be reviewed and updated to ensure we capture everything needed. These updates have been implemented in the Dev and Staging environments for the Gids database.

Acceptance Criteria

• [ ] pgaudit.conf configured and hardened for Gids database in prod
• [ ] Ensure DB scans captures the necessary audit data

Refinement Guidance - Check the following before working on this issue:

• [ ] Epic assigned (if needed)
• [ ] Estimated (points assigned)
• [ ] Sprint assigned (once planned)
• [ ] Team member(s) assigned
• [ ] Understands how this work aligns with the overall platform

[Efe-Oddball]

https://github.com/department-of-veterans-affairs/devops/pull/14765

[Efe-Oddball]

Configuration has been changed. There was a little issue with storage size in prod that prevented me from implementing the database update. I should update database later today

[Efe-Oddball]

Waiting to schedule security re-scan to ensure that audit details are being logged

[Efe-Oddball]

Due to the effects of the audit logs to the functionality of the database, we have to go back to the drawing board to discuss what needs to be done with adding audit logs to the prod databases. The audit logs tend to fill up the database memory really really fast. This ticket will be on hold, until we discuss the way forward with the team.

[Efe-Oddball]

Due to the effect of audit logs on database storage, I am moving this ticket to a blocked state until the database discovery ticket attached to this issue is resolved