bastion

Introduction to OWASP Top 10

Build this skill

Describe the purpose of the OWASP Top 10 and classify realistic application findings into its risk categories.

A shared list of the mistakes that keep happening

Two weeks before the Diwali sale, Vikram Deshmukh asks Rohan Iyer a simple question: "Is the app secure?" Rohan has built every screen of the Tulsi Health app, but he has no idea where to begin answering. Should he worry about passwords, about the reviews, about the cloud settings, about the libraries he downloaded? Thousands of developers face the same question every day, and most of them start in the same place: the OWASP Top 10, a short public list of the most critical kinds of security risk in web applications, written so that developers, testers and managers can all use it.

Who OWASP is and how the list is made

OWASP, the Open Worldwide Application Security Project, is a non-profit foundation. Volunteers from companies, universities and the security community around the world write its guides, build its free tools and run local meetings, including chapters in several Indian cities. Nothing OWASP publishes costs money, and none of it belongs to a single company, which is one reason so many organisations trust it.

The Top 10 is its best-known document. Every few years, organisations that test applications for a living share data on the weaknesses they found across a very large number of real applications. OWASP groups those weaknesses into risk categories, each one a family of related mistakes rather than a single bug, and ranks the families by how often they appear and how much damage they cause. A few categories are added from a survey of practitioners, to catch newer problems the data has not caught up with yet. The editions so far include 2017, 2021 and the current 2025 edition, and the list shifts between them as applications and attacks change.

OWASP Top 10 · 2025 edition the most critical web application risks, in plain words 1 Access control who can see what 2 Misconfigured unsafe settings 3 Supply chain others' code 4 Cryptography weak protection 5 Injection input as commands 6 Insecure design flaw in the plan 7 Authentication proving who you are 8 Integrity unchecked updates 9 Logs & alerts not noticing 10 Error handling failing unsafely Rohan “Which of these could be hiding in our app?” Each card is a family of related weaknesses, not one single bug.

Ten families of risk fit on one board, which is exactly why the list is used to start conversations about security.

What the Top 10 is for, and what it is not

The purpose of the OWASP Top 10 is awareness. It gives everyone a shared vocabulary, so that when a tester writes "broken access control" in a report, Rohan, Neha and Rathi Softech all know the kind of problem meant. It gives a sensible starting point for training new developers, for planning what to test before a release, and for asking a supplier about their software. It turns "is the app secure?" into ten concrete questions.

The traffic police publish the most common causes of road accidents: speeding, no helmet, using a phone while driving, jumping signals. That list is a wonderful place to start teaching new drivers, and a city that tackled only those causes would save many lives. But nobody would call a driver "safe" just because they avoid those four things; a pothole or a stray cow can still cause a crash. The Top 10 works the same way. It is not a complete checklist, not a standard you can be certified against, and an app that avoids all ten families can still have serious problems that fall outside them.

What the Top 10 isAn awareness documentA shared vocabularyA starting point for testingBased on real findingsFree and regularly updatedWhat it is notA complete checklistA certificate of safetyA list of single bugsA replacement for testingThe same forever

Treat the list as the first ten questions to ask about an application, never as the last.

The ten categories in plain words

The 2025 edition names these ten families, from the top of the list down. The names are OWASP's; the explanations and examples are in plain words.

# Category In plain words A Tulsi Health example
1 Broken Access Control People reach data or actions that are not theirs Changing an order number shows another customer's prescription
2 Security Misconfiguration Safe software set up unsafely A store router still on admin / admin
3 Software Supply Chain Failures Weak or tampered parts made by others An outdated free library with a known flaw inside the app
4 Cryptographic Failures Sensitive data badly protected or not scrambled at all Customer passwords stored as readable text
5 Injection Typed input treated as commands A search box whose text is run as a database command; also cross-site scripting
6 Insecure Design A flaw in the plan itself, not the code A "reset password" flow that asks only for a phone number
7 Authentication Failures Weak ways of proving who someone is No limit on login attempts, so passwords can be guessed
8 Software or Data Integrity Failures Trusting updates or data without checking them Installing a billing update without confirming who it came from
9 Security Logging and Alerting Failures Attacks happen but nobody notices 500 failed logins in one night and no alert to Neha
10 Mishandling of Exceptional Conditions The app behaves unsafely when something goes wrong A payment error that marks the order as paid anyway

The ten are easier to remember in a few groups, by the question each one answers. Some are about who is allowed to do what, some about trusting things that come from outside, some about how the system was planned and set up, and some about what happens when things go wrong.

Web app risksOWASP Top 10, 2025Who may actaccess, authenticationOutside inputinjection, supplychain, integrityPlans and setupdesign, settings,cryptoWhen it breakslogging, error handling

Four questions cover all ten: who may act, what comes from outside, how was it planned and set up, and what happens when something goes wrong.

Neha has collected findings from a quick review of the Tulsi Health app. Put each one in the family it belongs to below. Some findings mention words that point to the wrong family, so think about what actually goes wrong.

Why knowing the names changes what gets built

Most successful attacks on web applications do not use brilliant new tricks. They use the same well-known families of mistake, again and again, in application after application. That is the real importance of vulnerability awareness: a developer who knows what broken access control looks like asks "whose order is this?" while writing the order page, instead of a tester discovering the gap after launch, or an attacker discovering it first. A mistake caught while the code is being written takes minutes to fix; the same mistake found after a data leak costs money, customers' trust and sometimes a legal case.

Awareness also has to be refreshed. Between the 2021 and 2025 editions, the category about outdated components grew into the wider supply chain family, and the category about mishandling errors appeared for the first time. A developer who learnt the list once, years ago, is preparing for yesterday's attacks.

Awareness is only useful if it leads to action, and a team rarely has time to fix everything at once. Score the findings below by how likely each is to be exploited and how bad the result would be, and see which ones Rohan should fix before the Diwali sale.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close