Which design pattern aims to eliminate the accidental insertion of vulnerabilities into code and mitigate their consequences?

Which design pattern aims to eliminate the accidental insertion of vulnerabilities into code and mitigate their consequences?

• A. Storage Design Pattern
• B. Secure Design Pattern
• C. Container API
• D. Application Vetting

Answer: (B)

Designing software with security built in aims to prevent vulnerabilities from being introduced and to limit their impact if they occur. A Secure Design Pattern embodies this approach. It encourages integrating security into the architecture—separation of concerns, least privilege, secure defaults, input validation, robust error handling, and defense in depth—so risky weaknesses are avoided and the system can contain damage when issues arise. That's why this option is the best fit: it directly addresses preventing insecure code and mitigating consequences by design.

The other options describe patterns or practices not focused on embedding security into the design itself. A storage design pattern deals with how data is stored, not with preventing vulnerabilities. A container API pertains to container interfaces, not security design patterns. Application vetting is about reviewing software after development, not a design approach to reduce vulnerability introduction.