In log maintenance, which detail is discouraged due to privacy concerns?

• A. Users' full names
• B. Authentication data
• C. Error messages
• D. Timestamps

Answer: (A)

Protecting personal data in logs means minimizing information that could identify someone. Full names are highly identifying and, if logs are accessed by the wrong people or exposed in a breach, they can be used to pinpoint individuals or combine with other data to reveal more about them. Because logs are often kept for long periods and may be shared across systems and tools, including a person’s full name creates unnecessary privacy risk. The safer approach is to avoid capturing names and, when needed for auditing, substitute with non-identifying identifiers or redact sensitive details.

Other details like usernames used for authentication, carefully protected, and with credentials never logged in plaintext, can be necessary for tracing actions. Error messages can be sanitized to avoid leaking internal details, and timestamps are essential for sequencing events and troubleshooting, so they are not inherently privacy-risky in the same way.