Question

A privacy engineer reviewing a new microservice discovers that its application debug logs capture full HTTP request bodies, including customers' names, email addresses, and payment card numbers, and these logs are shipped to a centralized log aggregation platform accessible to the entire engineering team for troubleshooting. The service must retain some logging to diagnose production errors. Which approach BEST embeds privacy into the logging design?

Accepted Answer

Redact or tokenize personal data fields at the source before log entries are emitted, and restrict aggregated log access based on role

Answer

Encrypt the entire log store at rest and rely on the platform's default retention policy to purge old logs

Answer

Keep capturing full request bodies but require engineers to sign an acceptable-use policy acknowledging the presence of personal data

Answer

Disable all application logging for the microservice to eliminate the possibility of exposing personal data