Sensitive data in logs cleanup

Description

It is necessary to review the information available in the module logs. Personally Identifiable Information (PII) that directly (explicit user personal data, financial information, etc.) or indirectly (references to files in S3 or local files containing personal information) allows the identification of a user must be removed. If removal is not possible, the information should be masked. Among the PII, the following should be removed (if applicable):

Direct Identifiers (explicitly identify an individual):

  • Full name

  • Social Security Number (SSN)

  • Passport number

  • Driver’s license number

  • Email address

  • Phone number

  • Physical address

Indirect Identifiers (can identify an individual when combined with other information):

  • Date of birth

  • IP address

  • Geolocation data

  • Employment information

  • Medical records

  • Financial data (e.g., credit card details)

Acceptance criteria:

All PII is not present in the module logs based on logs visual review.

Environment

None

Potential Workaround

None

defines

Checklist

hide

Activity

Show:

Bobby SharpMarch 10, 2025 at 1:06 PM

Not much to QA for this story. I wrote a log sanitization function to sanitize any logs with sensitive info (such as S3 credentials) and applied it to all the logs where there is a possibility of sensitive information showing up. No other functionality has been modified by this story.

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Corsair

Fix versions

Release

Sunflower (R1 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created February 6, 2025 at 5:51 PM
Updated March 11, 2025 at 7:31 PM
Resolved March 10, 2025 at 1:06 PM
TestRail: Cases
TestRail: Runs

Flag notifications