Audit Logger

[elipe17]

Description: We would like to perform an audit of the information that is being logged to the console in the backend. We want to avoid logging any PII or other sensitive information.

Acceptance Criteria:

• [ ] No PII or other sensitive information is logged to the console or file
• [ ] Testing Checklist has been run and all tests pass
• [ ] README is updated, if necessary

Tasks: Create a list of granular, specific work items that must be completed to deliver the desired outcomes of this issue

• [ ] Check all logging statements in the backend for sensitive of PII and update appropriately
• [ ] Run Testing Checklist and confirm all tests pass

Notes: Add additional useful information, such as related issues and functionality that isn't covered by this specific issue, and other considerations that will be helpful for anyone reading this

• Alex can provide info on what fields in records are considered sensitive or PII.
  • SSN, DoB, case number containing SSN?, email address, user pass (see privacy act statement/doc)

Supporting Documentation: Please include any relevant log snippets/files/screen shots

• Doc 1
• Doc 2

Open Questions: Please include any questions or decisions that must be made before beginning work or to confidently call this issue complete

• Open Question 1
• Open Question 2

[ADPennington]

@elipe17 some evidence of sensitive PII fields in the logs below (note: this is not real PII, im testing reparsing in qasp env)