Annual security review 2025: Secrets Management

[OlgaLiber2]

Describe the task
For each release, ensure that any new secrets are added to the Secrets Registry.

Annually, review the Secrets Registry, ensure it is up to date, and ensure that credentials are being rotated at least annually.

Acceptance Criteria

• Refer to item #9
• Consult Secrets Registry to rotate (or regenerate)/add/remove credentials if needed to DEV -> TEST then PROD
• Make sure Secrets Registry is up to date
• Some credential update might be challenging, for example BCSC or IDIM, if that's the case, may need to create separate tickets for appropriate procedure for them to be updated if necessary.

Additional context

• Maybe discuss the need of Secrets Registry for FOM and IDIM-Proxy?
• Or here

[ianliuwk1019]

2025 rotation checklist added - https://apps.nrs.gov.bc.ca/int/confluence/display/FSAST1/Secrets+Rotation+-+2025 for the progress.

[ianliuwk1019]

Most secrets were rotated for 2025.
Two tickets are created #1747 and #1759 to deal with database (AWS-Terraform) secrets and BCSC key separately.