Test your Secure Coding knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a "path traversal" (directory traversal) vulnerability, and how does secure coding typically prevent it?
Questions in this quiz
What is a "path traversal" (directory traversal) vulnerability, and how does secure coding typically prevent it?
What is the purpose of dependency/supply-chain security practices, like regularly scanning for known vulnerabilities in third-party packages a project depends on?
What does "defense in depth" mean as a secure coding/architecture principle?
What is "security by obscurity," and why is it generally considered an insufficient security strategy on its own?
What is Cross-Site Scripting (XSS), and what secure coding practice mitigates it?
What is the purpose of secure password storage practices, specifically using a slow, salted hashing algorithm (like bcrypt or Argon2) rather than a fast general-purpose hash (like plain SHA-256) or storing passwords in plaintext?
What does "fail securely" (or "fail closed") mean as a secure coding principle, as opposed to "fail open"?
What is the purpose of secure secret/credential management practices (e.g. never hardcoding API keys or database passwords directly in source code)?
What does "Secure Coding" refer to as a discipline?
Why is input validation considered a foundational secure coding practice, and where should it typically be enforced?
What does the practice of "sanitizing" versus "validating" user input mean, and how do the two differ?
What is the difference between authentication and authorization, and why does conflating them lead to security bugs?