Which statement identifies a common privacy risk with address data and its mitigation?

Which statement identifies a common privacy risk with address data and its mitigation?

• A. Encrypt addresses but never log
• B. Exposure via logs, exports, or insecure transfers; mitigate with encryption, access controls, data masking, and secure export procedures
• C. Publicly posting address data on a website
• D. Share addresses with third parties freely

Answer: (B)

Addresses are highly sensitive personal data, and the main risk comes from where they can appear in systems or transfers: inside logs, in exports, or over unprotected channels. The best approach to mitigate this is a layered set of protections that cover storage, visibility, and movement of the data. Exposure through logs happens because many systems record user activity and data in logs. Even if the primary data at rest is protected, seeing full addresses in logs is a privacy breach. The remedy is to limit what gets logged, redact or mask sensitive fields in logs, and enforce strict access controls so only necessary personnel can view logs. Exports and data transfers are another common risk. When data is exported or moved between systems, it can be exposed if not properly protected. Using encryption for the data in transit and at rest, implementing secure export procedures (such as authenticated, audited exports), and ensuring that only authorized processes can perform exports are essential steps. Insecure transfers, like sending raw addresses over unencrypted channels, pose immediate risk. Always use secure channels (TLS, VPNs, or secure file transfer methods) to move address data. Data masking and access controls complement these measures: masking parts of an address when full detail isn’t needed, and applying least-privilege access so only authorized users can view or process addresses. The other options fall short because they either ignore a layer of protection (like relying on encryption alone without secure transfers and access controls) or describe actions that create obvious privacy risks (posting publicly or sharing freely).

Addresses are highly sensitive personal data, and the main risk comes from where they can appear in systems or transfers: inside logs, in exports, or over unprotected channels. The best approach to mitigate this is a layered set of protections that cover storage, visibility, and movement of the data.

Exposure through logs happens because many systems record user activity and data in logs. Even if the primary data at rest is protected, seeing full addresses in logs is a privacy breach. The remedy is to limit what gets logged, redact or mask sensitive fields in logs, and enforce strict access controls so only necessary personnel can view logs.

Exports and data transfers are another common risk. When data is exported or moved between systems, it can be exposed if not properly protected. Using encryption for the data in transit and at rest, implementing secure export procedures (such as authenticated, audited exports), and ensuring that only authorized processes can perform exports are essential steps.

Insecure transfers, like sending raw addresses over unencrypted channels, pose immediate risk. Always use secure channels (TLS, VPNs, or secure file transfer methods) to move address data.

Data masking and access controls complement these measures: masking parts of an address when full detail isn’t needed, and applying least-privilege access so only authorized users can view or process addresses.

The other options fall short because they either ignore a layer of protection (like relying on encryption alone without secure transfers and access controls) or describe actions that create obvious privacy risks (posting publicly or sharing freely).