CERTNEXUS-ITS-110-2025 practice question 26 of 35

A cloud developer for an IoT service is storing billing information. Which of the following should be considered a common vulnerability in regard to this data that could be used to compromise privacy?

Full set: 100 questions
Answer options
A: Enabled notifications as required by law
B: Lack of data retention policies Correct answer
C: Authorized access to personal information
D: Secured data in motion and at rest
Correct Answer:
B. Lack of data retention policies
Explanation

A lack of data retention policies is a critical vulnerability. Storing sensitive billing information indefinitely violates the core privacy principle of data minimization. This practice unnecessarily expands the timeframe during which the data is exposed to threats, increasing the attack surface. If a breach occurs, a larger volume of historical data is compromised. Proper data governance requires defining and enforcing policies to securely dispose of data once it is no longer required for legal or business purposes. Failure to do so represents a significant and common privacy risk.

Why Incorrect

A. Enabled notifications as required by law: This is a legal compliance measure designed to inform and protect users, not a vulnerability that compromises their privacy.
C. Authorized access to personal information: Authorized access is a necessary operational function. The vulnerability lies in unauthorized or excessive access, not in the existence of a controlled authorization system.
D. Secured data in motion and at rest: This describes the implementation of security controls (e.g., encryption) to protect data. It is a mitigation measure, the opposite of a vulnerability.

References

1. NIST Special Publication 800-53 Revision 5, Security and Privacy Controls for Information Systems and Organizations. The control family PM (Program Management), specifically PM-28 "Personally Identifiable Information Processing and Transparency," emphasizes the need for organizations to implement measures that include data minimization and retention limits for PII. A lack of such policies is a direct failure to implement this control.

2. NISTIR 8062, An Introduction to Privacy Engineering and Risk Management in Federal Systems. Section 2.2, "Privacy Principles," discusses data minimization as a fundamental concept. It states, "Systems should collect, use, and retain only the PII that is relevant and necessary for the specified and authorized purpose(s)." Storing data without a retention policy violates this principle.

3. University of California, Berkeley, Data Privacy and Security Courseware. In discussions on privacy-by-design, the principle of "Storage Limitation" (derived from frameworks like GDPR) is highlighted. It mandates that personal data should be "kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed." A lack of a retention policy is a direct contravention of this principle.

Scroll to Top