Web Application Security Testing
Web applications are the primary gateway through which the public engages with your organisation. They reach deep into system architecture and connect to internal and third-party services, so a flaw in one application is a route into everything that application can touch.
What it covers
The application is crawled first, so the test works against the surface a real visitor meets rather than a list of URLs someone remembered. Testing follows the OWASP Testing Guide and targets the ways applications are actually broken:
- Injection, including SQL injection
- Cross-site scripting (XSS)
- Unauthorised access and broken access control
- Authentication handling, session management and the information a server gives away about itself
Every finding arrives with the evidence behind it, so it can be reproduced and fixed without a phone call.
How it is scoped and priced
Enter the starting URL and the spider maps the application's pages and forms. Work is sized at one testing day per ten form elements an anonymous visitor can reach, at a single published rate of €100 per testing day.
The scope, the price and the delivery date are all shown before any commitment, and the quote is a ceiling: if testing takes longer than expected, the total does not change. Testing starts the next business day after payment.
What you receive
A report with an executive summary, technical findings scored by severity, remediation guidance and a priority ranking, delivered one business day after testing completes. One free retest of the findings you fix is included.
If a second pair of eyes on the result is wanted, a security engineer can re-check every finding by hand for €40, removing false positives and expanding the detail on what is real. A live walkthrough of the findings with your team, review included, is €100.
Scope it, see the fixed price, pay, and get the report. From €100 per testing day, quoted in seconds against your live application.
What it does not cover
The published flow tests the anonymous level: what a visitor who has not logged in can reach. Authenticated coverage — what each role inside the application can see and change — needs a bespoke scope and is routed to a contact form rather than quoted automatically.
Nor does a test of the outside say anything about an attacker who already has a foothold inside the network. That is a different engagement.
Questions
- How is the price calculated?
- The spider counts the form elements an anonymous visitor can reach; one testing day covers ten of them, at €100 per testing day, minimum one day.
- What if testing takes longer than estimated?
- Nothing more is charged. The quoted price is a ceiling, not an estimate that gets billed upward.
- Do you test production or staging?
- Whichever environment reflects the real surface. Whichever is chosen must be reachable and authorised in writing before testing starts.
- How quickly can it start?
- Testing begins the next business day after payment, and the report follows one business day after testing completes.
- Is a retest included?
- One free retest of the findings you have fixed is included with every report.