Which statement explains why security is included in Level 1 coding standards?

• A. To prevent common vulnerabilities, protect data, and promote secure-by-default practices from the start
• B. To promote secure-by-default practices only after features are complete
• C. To delay security reviews until after deployment
• D. To rely on manual security checks during QA

Answer: (A)

Security in Level 1 coding standards should be built into the process from the start. This means preventing common vulnerabilities, protecting data, and promoting secure-by-default practices from the very beginning of development. When security is treated as an integral part of coding, issues are caught and mitigated as features are being built, which reduces risk, improves consistency, and keeps costs lower because you’re fixing problems earlier rather than after deployment. Relying on security reviews only after deployment or waiting until QA or post-release to address security creates exposure and makes fixes more difficult and expensive. That’s why the statement that best fits is the one describing security as preventing vulnerabilities, protecting data, and promoting secure-by-default practices from the start.