Test your Security Best Practices knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What is the risk of using outdated, unpatched software dependencies (libraries/frameworks) in an application?
In this round
What is the risk of using outdated, unpatched software dependencies (libraries/frameworks) in an application?
What is the difference between "authentication" and "authorization," as two distinct security concepts?
What is the general security risk of exposing detailed error messages/stack traces directly to end users in a production application?
What is SQL injection, and what is the primary defense against it?
What is a "supply chain attack," in the context of software dependencies, and why has it become an increasingly cited concern?
What is "rate limiting" as a security practice, and what kinds of attacks does it help mitigate?
Why is it generally considered a security anti-pattern to implement custom, "homegrown" cryptographic algorithms rather than using well-established, publicly-vetted cryptographic libraries/algorithms?
What is the security concern behind exposing overly verbose or unnecessary HTTP response headers (like a specific server software version), and what is a common mitigation?
Why is storing secrets (API keys, database passwords, private keys) directly in source code (committed to version control) considered a serious security risk?
What is Cross-Site Scripting (XSS), and what is a primary defense against it?
What is the security risk of overly permissive CORS (Cross-Origin Resource Sharing) configuration, such as allowing `Access-Control-Allow-Origin: *` on an API that handles sensitive, authenticated data?
What is "defense in depth," as a broader security design philosophy?
Gaps to close?
Read the curated Security Best Practices notes — core concepts, patterns, interview prep.