PrepPilotPractise free

Application Security (OWASP) interview questions

OWASP Top 10, secure coding, auth, secrets, SAST/DAST

16 questions · OWASP · updated November 2026

Practise these as flashcards. One or two lines each; the ones you miss come back first.

Start free

Core questions

What is the OWASP Top 10 and why is it important?

The OWASP Top 10 is a list of the ten most critical web application security risks, updated regularly by the Open Web Application Security Project. It's important because it highlights the most common and impactful vulnerabilities, helping teams prioritize security efforts.

How can SQL injection be prevented?

SQL injection can be prevented by using parameterized queries or prepared statements, which separate user input from SQL code. This ensures that user data can't change the intent of the query.

What is an example of broken access control?

An example is when a user can access another user's data just by changing a user ID in the URL, because the server doesn't check if they have permission to view that data.

Why shouldn't secrets be hardcoded in source code?

Hardcoding secrets in code risks accidental exposure through source control or logs. Instead, secrets should be stored securely, such as in environment variables or a secrets manager.

Intermediate questions

How do you securely manage authentication sessions?

I use secure, HttpOnly cookies for session tokens, set the Secure and SameSite flags, and ensure sessions expire after inactivity. I also implement logout endpoints and rotate session tokens on privilege changes.

What is IDOR and how do you prevent it?

IDOR stands for Insecure Direct Object Reference, where attackers access objects by manipulating identifiers in requests. To prevent it, always enforce authorization checks server-side and avoid exposing raw IDs when possible.

What is the difference between SAST and DAST?

SAST analyzes source code or binaries for vulnerabilities without running the application, while DAST tests the application in a running state by simulating attacks from the outside. Both approaches are complementary.

How do you handle secrets in CI/CD pipelines?

I use the CI/CD platform's secrets management features to inject secrets as environment variables at runtime, and restrict access to only the necessary jobs or stages. I never store secrets in code or pipeline configs.

What are some items you check during a secure code review?

I check for proper input validation, secure handling of authentication and sessions, correct access control enforcement, no hardcoded secrets, safe use of dependencies, and appropriate error handling.

How does SCA help improve application security?

Software Composition Analysis (SCA) scans dependencies for known vulnerabilities and license issues. It helps ensure that third-party libraries don't introduce security risks into the application.

Why is server-side validation important even if you validate on the client?

Client-side validation can be bypassed by attackers, so server-side validation is essential to enforce security and data integrity regardless of how the request is made.

Senior questions

How would you design a system to minimize the risk of broken access control?

I'd use a centralized authorization layer, apply the principle of least privilege, and ensure all resource access is checked server-side. I'd also use opaque identifiers instead of sequential IDs and regularly audit access logs for anomalies.

Describe how you would integrate SAST, DAST, and SCA into a CI/CD pipeline.

See the answer in the app, free

How do you handle secrets rotation in production systems?

See the answer in the app, free

How do you balance usability and security in authentication mechanisms?

See the answer in the app, free

What steps do you take to ensure your application is resilient to new OWASP Top 10 risks?

See the answer in the app, free

More Quality & Security topics