Website security basics for small businesses: the OWASP Top 10:2025 as a working checklist
Use OWASP Top 10:2025 as a security awareness checklist and plan authorized checks without treating the list as a certification.
OWASP calls its Top 10 a standard awareness document for developers and web application security (https://owasp.org/Top10/2025/). Its project page says the most current release is the 2025 edition (https://owasp.org/projects/top-ten). OWASP's developer guide lists the 2025 categories (https://devguide.owasp.org/en/07-training-education/05-top-ten/) and notes three changes from 2021: Server-Side Request Forgery is now part of Broken Access Control, Vulnerable and Outdated Components has grown into Software Supply Chain Failures, and Mishandling of Exceptional Conditions is new.
The ten categories, with a question for each
The category names are OWASP's. The questions and the "what to check" column are our own wording, as practical prompts.
| 2025 category | Ask your developer | A quick check you can do |
|---|---|---|
| A01 Broken Access Control | Can one customer reach another customer's data by changing an ID in the URL? (SSRF now sits here too: can users make our server fetch addresses they choose?) | Log in as user A, copy an order link, open it as user B |
| A02 Security Misconfiguration | What is switched on in production that should not be: debug mode, default accounts, public admin pages? | Try your /admin or equivalent address from a logged-out browser |
| A03 Software Supply Chain Failures | Which libraries, plugins and build tools do we depend on, and who updates them? | Ask for the dependency list and the last update date |
| A04 Cryptographic Failures | Is data protected in transit and at rest, and where are secret keys stored? | Check the site and API use HTTPS everywhere |
| A05 Injection | Is user input ever placed directly into a database query or command? | Ask how queries are built (parameterised or string-joined) |
| A06 Insecure Design | Did we list abuse cases before building the feature? | Ask for the abuse cases for checkout and sign-in |
| A07 Authentication Failures | How do sign-in, passwords and sessions work? | See our sign-in guide |
| A08 Software or Data Integrity Failures | Do we install code or updates without checking where they came from? | Ask how deployments and updates are verified |
| A09 Security Logging and Alerting Failures | Would we notice an attack, and would someone be told? | Ask what triggers an alert and who receives it |
| A10 Mishandling of Exceptional Conditions | What does the app do when something unexpected fails: does it stay safe, or leak details or skip checks? | Submit a form with odd input and see what error shows |
Only test systems you own or have explicit permission to assess, using test accounts and non-sensitive data. Stop if a check exposes another person's data; do not explore it further.
A one-hour review you can run
- Pick your most important flow (checkout or lead form).
- Walk through the ten rows for that flow only.
- Write each answer as confirmed, unknown or gap.
- Fix gaps in order: access control and authentication first, since they touch customer data directly.
- Put a date on the next review.
A worked example (hypothetical)
A shop's order page is /orders/1042. A customer changes it to /orders/1043 and sees someone else's order. That is a broken access control problem. The fix is on the server: it must check the order belongs to the signed-in user. Hiding or randomising the number alone does not solve it. This example is illustrative, not a reported incident.
Limits
This is awareness material, not a security test. We read the OWASP overview pages and the category list, not each category's full page. For depth, use OWASP's per-category pages. Payment or health data needs a proper professional review beyond a checklist.
By Omnistu.