If a file contains employee names, birthdates, and social security numbers, what is the recommended confidentiality stance for internal access?

If a file contains employee names, birthdates, and social security numbers, what is the recommended confidentiality stance for internal access?

• A. Withhold both social security numbers and birthdates
• B. Share access for convenience
• C. Share birthdates but withhold social security numbers
• D. Share all data to improve communication

Answer: (A)

Protecting sensitive personal data through least-privilege access and data minimization is the main idea. Social security numbers and birthdates are highly sensitive PII; exposing them internally increases the risk of identity theft and misuse. Internal access should be limited to those who need it to do their jobs, and information should be minimized to what is necessary for the task at hand. In this case, the safest stance is to withhold both birthdates and social security numbers from general internal access, allowing access only to the minimum identifiers needed (like names) and to escalate to secure systems with proper authorization if verification is required. Sharing data for convenience or exposing SSNs or birthdates unnecessarily would raise risk and conflict with confidentiality principles. Thus, the recommended stance is to restrict access and protect these sensitive fields by default.

Protecting sensitive personal data through least-privilege access and data minimization is the main idea. Social security numbers and birthdates are highly sensitive PII; exposing them internally increases the risk of identity theft and misuse. Internal access should be limited to those who need it to do their jobs, and information should be minimized to what is necessary for the task at hand. In this case, the safest stance is to withhold both birthdates and social security numbers from general internal access, allowing access only to the minimum identifiers needed (like names) and to escalate to secure systems with proper authorization if verification is required. Sharing data for convenience or exposing SSNs or birthdates unnecessarily would raise risk and conflict with confidentiality principles. Thus, the recommended stance is to restrict access and protect these sensitive fields by default.