Penetration Testing a Small Web App: What to Ask For and What You Get
Short answer: A penetration test is a planned, authorised attempt to break into your web app using the methods a real attacker would try. For a small business, a good test defines its scope in writing, runs in an agreed environment, produces a report with each finding, its severity and steps to reproduce it, and ends with a retest of the fixes. Price depends on the number of pages, roles, integrations and the depth of testing, so ask for a fixed-scope quote. An automated vulnerability scan is cheaper and useful for routine checks, but it does not replace a tester who chains weaknesses together.
Define the scope before you ask for a quote
Scope is the most important part of the job. Write down the following before you contact any tester:
- The web addresses in scope, such as the customer portal and the admin area.
- The user roles to test, for example a customer, a staff member and an administrator.
- The integrations, such as a payment provider, a booking system or a third-party login.
- The environment: a staging copy, a production site, or both.
- Anything out of bounds, such as third-party systems you do not own or denial-of-service attacks.
- Whether the tester may use test accounts, and who will create them.
Take a fictional clinic booking app called Coastline Care as an example. Its scope might cover the patient portal, the clinician dashboard and the booking API, tested on a staging copy with two patient accounts and two clinician accounts. Payment and the third-party SMS provider are excluded, because the owner does not control them.
Test environment and rules of engagement
Most testers prefer a staging environment with realistic data removed or replaced. Testing production is possible but needs more care, because a tester may create records, lock accounts or trigger alerts. The rules of engagement should state the testing window, the contact person, what to do if something breaks, and how urgent findings are reported during the test.
Keep a signed copy of the rules of engagement. If your hosting company or payment provider asks about the test, you will have the dates and the scope in writing.
Choosing a tester and reading a quote
Look for a tester who can explain their method, names the frameworks they use, and offers references from businesses of similar size. Ask who will do the work. A quote from a firm that sends a junior staff member without senior review may look cheap, but the quality varies.
A fixed-scope quote should list the number of test days or hours, the environments, the roles, the retest allowance and the report format. Be wary of quotes that give a price without describing what is included. Price also rises with the number of integrations and the complexity of business logic, such as discounts, approvals and multi-step bookings.
What the report contains
A useful report has four parts:
- An executive summary that describes the overall risk in plain language for the owner.
- A findings table with each issue, its severity, the affected area and a status.
- Detailed findings, each with a description, the steps to reproduce, evidence such as a screenshot or request, and the business impact.
- Remediation advice that tells your developers what to change, in order of priority.
Severity is often rated using a scale such as CVSS. Read the rating together with the business impact. A medium-rated issue that exposes patient records may matter more to a clinic than a high-rated issue on a page that has no sensitive data.
Acting on the findings
Do not try to fix everything at once. Agree a timeline with your developers based on severity. A common approach for a small app is:
- Critical findings: fixed within days, with a temporary control if a full fix takes longer
- High findings: fixed within weeks, and tested before the next release
- Medium and low findings: scheduled into normal development, with a note on each ticket
- Informational items: reviewed and either fixed or accepted with a reason
Keep a remediation log that shows each finding, the fix, the person responsible and the date. When the fix is ready, ask for a retest of that specific issue. Retests are often cheaper than the original test and give you evidence for customers or auditors.
Automated scans and when they are enough
An automated scanner checks for known weaknesses such as outdated software, missing security headers and some common injection patterns. It is useful as a monthly or release-level check, and it can run without a specialist. It is not enough when your app has accounts, payments or sensitive records, because many serious problems involve how features are used rather than a known signature.
As a rule, use a scanner for routine checks and a human-led test once a year or after major changes to login, payments or data storage.
Common surprises
- Test accounts are not set up, so the tester spends half the first day waiting
- Staging has different settings from production, so findings do not match real behaviour
- Third-party services are included in scope without anyone checking their terms
- The report arrives without retest allowance, and the fixes are checked only by the developer
- Findings are handed to a developer who was not told the business reason for the feature
A short checklist
- Scope written down with URLs, roles and integrations
- Environment and testing window agreed
- Rules of engagement signed
- Quote compared on scope, not only on price
- Report format agreed before testing starts
- Remediation timeline agreed by severity
- Retest included or budgeted
FAQ
How long does a test take?
For a small web app with a few roles, testing often takes a few days, and the report follows after. Longer for more complex apps.
Do I need to tell my customers?
Not usually, but check your contracts, especially if you hold regulated information. Some clients ask for proof of testing, and a summary report can help.
Can I run the test myself?
Only with real skill and authority. Self-testing can find basic problems but rarely gives the independent view that a tester brings.
Where can I find guidance on what to test?
The Australian Cyber Security Centre publishes guidance for small businesses, and the OWASP Web Security Testing Guide is widely used by testers as a reference.
If you want help writing a scope for your web app and comparing quotes from testers, reach out through our enquiry page.