Provide examples of secure coding practices a TA would require in software development projects.

• A. Hardcode credentials in configuration files to speed up deployment.
• B. Input validation, output encoding, secure authentication, proper session management, least privilege, secure error handling, and secure configuration management.
• C. Disable all logging and auditing to improve performance.
• D. Use outdated cryptography for compatibility.

Answer: (B)

Secure coding practices aim to reduce vulnerabilities by applying defensive techniques throughout development. The best answer presents a practical, comprehensive set you’d require in software projects, covering how data is handled, how access is controlled, and how the system is stabilized against misuse.

Input validation and output encoding prevent common attacks by ensuring received data is safe to process and safely displayed or stored. Secure authentication and proper session management protect credentials and keep user sessions from being hijacked or abused. Least privilege limits what each component or user can do, reducing the impact of any compromise. Secure error handling avoids leaking sensitive information and helps detect issues without exposing internals. Secure configuration management ensures sensitive settings and keys aren’t exposed, requires secure defaults, and supports rotation and proper secret storage.

Why the other options don’t fit: hardcoding credentials creates widespread risk because secrets are embedded in code or config files and are hard to rotate. Disabling logging removes essential visibility for detecting and investigating incidents. Using outdated cryptography introduces known weaknesses that attackers can exploit.

Together, these practices embody the disciplined approach to building secure software that a trusted agent would require.