Privacy flaws can MOST effectively be minimized during which phase of the software development life cycle?

The correct answer is A. Planning and design. Privacy flaws are most cost-effectively and thoroughly addressed during the planning and design phase through the principle of Privacy by Design (PbD). Identifying and embedding privacy requirements at the outset - such as data minimization, purpose limitation, and access control

Privacy Architecture

Question

Options

APlanning and design
BMaintenance
CTest and release
DDevelopment

How the community answered

(25 responses)

A
92% (23)
C
4% (1)
D
4% (1)

Explanation

Privacy flaws are most cost-effectively and thoroughly addressed during the planning and design phase through the principle of Privacy by Design (PbD). Identifying and embedding privacy requirements at the outset - such as data minimization, purpose limitation, and access controls - prevents privacy vulnerabilities from being built into the system in the first place. Fixing flaws found later in the lifecycle (testing, release, or maintenance) is significantly more expensive, disruptive, and less effective than designing them out from the start. Maintenance (B) is reactive and costly. Test and release (C) can identify issues but remediating design-level flaws at this stage is difficult. Development (D) is earlier than testing, but design decisions made before coding begins are more foundational.

Topics

#SDLC#Privacy by Design#Privacy Engineering#Risk Mitigation

Community Discussion

No community discussion yet for this question.

Full CDPSE Practice