Skip to main content
Security guideReviewed

Penetration testing cost in Australia: what sets the price and how to compare quotes

What a penetration test costs depends on its scope.

This guide shows what two Australian providers publish, as checked on 13 November 2026, explains each factor that moves the effort, and gives you a worksheet to scope your own test and line quotes up side by side.

Australian penetration test budget worksheet

Copy this worksheet into a document and fill in Part A for your own application. Mark each factor light, moderate or heavy with Part B, then use Part D to line up the quotes you receive.

How to use it

Part C shows three invented example scopes filled in, and Part E lists the published market figures with the date they were checked.

penetration-testing-cost.txt

Introduction2 lines

AUSTRALIAN PENETRATION TEST BUDGET WORKSHEET Fill in one copy for each application you want tested. Bring it to any provider's scoping call, and use Part D when the quotes arrive.

How penetration tests are priced in Australia

There is no standard price list for penetration testing in Australia, and a figure quoted without a scope tells you very little.

What a provider sells is testing effort: a tester working through your application for a set amount of time, then writing up what was found. Two Australian providers that publish prices say this plainly. Siege Cyber's pricing page says penetration testing is priced on tester days, and Compliance Council's cost guide says most Australian tests are priced in tester-days underneath.

So the useful question is less what a penetration test costs and more how much testing your application needs. That depends on things you can count before you speak to anyone: the routes that accept input or return private data, the roles and customer organisations that must be kept apart, the APIs, how far behind the login the testing goes, whether the tester can read the code, what production allows, and who will read the report.

The sections below take each in turn, and the worksheet turns your answers into a scope you can hand to any provider.

Clever Ops does not publish prices. We quote each test after a free scoping call, once those factors are known, and the written scope that comes with the quote states what is tested, what is excluded and what the retest covers.

What Australian providers publish, checked on 13 November 2026

The figures below come from two Australian providers' own pages, opened and read in full on 13 November 2026.

Each is the provider's published figure for its own scope, excluding GST, with ranges written using "to". Prices change, so open the provider's page again before relying on any of them.

Siege Cyber: price ranges by test type

Siege Cyber states that the prices on its pricing page are current as of 18 October 2026, in Australian dollars and excluding GST, and that every price includes manual testing, the report, a debrief call and the retest. 1 min read

Siege Cyber: a fixed-scope web application test

Siege Cyber also sells a fixed-scope test it calls Essentials, priced at $4,400 excluding GST. 1 min read

Compliance Council: indicative bands with tester-days

Compliance Council's 2026 Australian pricing guide publishes indicative bands, ex GST, for comparable scopes, with the tester-days behind each. 1 min read

Reading the figures side by side

Each figure belongs to its provider's own definition of a scope, so the figures do not combine into a market average or a typical price. 1 min read

Seven factors that change the testing effort

Each factor below either adds things to test or adds time to each test.

None of them carries a fixed price, and providers weigh them differently, but every one of them shows up in how a scope is written. Count them for your own application before you ask anyone for a quote.

Routes and features

A route is any page or API endpoint that accepts input or returns data that is not public: a login form, a search box, an invoice download, the endpoint the browser calls to save a booking. 1 min read

Roles and customer organisations

Access control is tested between people, so effort grows with the number of combinations, not only the number of roles. 1 min read

APIs

Most modern web applications are a front end over an API, and the API is where the rules have to hold. 1 min read

Testing depth: outside only, or signed in

An unauthenticated test looks at what anyone on the internet can reach: exposed files, the login and reset flows, response headers, visible software versions and the public forms. 1 min read

Source code access

A test without code access works from the outside, which is how an attacker starts. 1 min read

Production constraints

A staging copy with seeded data is the lighter path, because the tester can create, change and delete records freely. 1 min read

Reporting and retesting

The report is the part you keep, and its audience changes the work. 1 min read

How to read a penetration testing quote

Two quotes for the same application can differ widely without either provider being unreasonable, because they describe different work.

Before comparing totals, put each quote through the same questions. Part D of the worksheet sets them out as a grid.

  • Scope named in full: the domains and API addresses, the environment, the routes or features, and the roles and customer organisations to be tested. If any of these is missing, the total rests on an assumption you have not seen.
  • Effort stated: the tester-days, or a description of the work clear enough to judge it by. A low total with no stated effort tells you little about what you are buying.
  • Method: whether a tester works through the application while signed in and checks each finding, or whether the work is mainly an unattended automated scan. Both have a place, and they are different purchases.
  • Depth: authenticated or outside only, the API tested directly or only through the screens, and code access used or not.
  • Exclusions, written down. A quote that lists none leaves you to discover them when the report arrives.
  • Assumptions: what the total depends on, and what happens if the application turns out larger than described. Settle that before testing starts.
  • Report: who it is written for, what each finding contains, and whether it will satisfy the customer or auditor who asked for the test.
  • Retest: included or extra, which findings it covers, and the window for requesting it.
  • GST: whether the total includes it. Both providers above publish their figures excluding GST.

Ways to reduce the effort without narrowing what matters

Part of any test goes on work that is not testing: waiting for accounts, rediscovering routes, working around a build that changes halfway through.

Taking that time out lowers the effort a provider has to allow for, and none of it reduces what gets tested.

  • Send the route list and any API schema with your scoping request, so discovery starts from your map rather than from nothing.
  • Have test accounts ready for every role, in two customer organisations if your application has more than one, with sample records in each.
  • Offer a staging copy that matches production in configuration, with seeded data, so the tester can write freely.
  • Clear what you already know about. Fix the findings from your platform's own security checks and any recent scan, so the test spends its time on what a scan cannot find.
  • Freeze the build for the testing window, or tell the tester which areas are changing and when.
  • Name a technical contact who can answer questions and reset data while testing runs.
  • If the budget is tight, rank routes by the harm a failure would do and test the top of the list first: sign-in and password reset, payments, anything that shows one customer's data, and admin functions. Schedule the rest rather than dropping it.

When the lower quote is the wrong one

A lower quote is the right one when it covers what you need.

It is the wrong one when the scope leaves out the thing that prompted the test, or when the report will not satisfy the person who asked for it. Watch for these mismatches.

  • Your customers log in, but the quote covers only what is visible without signing in.
  • Your application serves several customer organisations, but the quote tests one role in one organisation.
  • A customer, insurer or tender asked for a penetration test, and the quote describes an automated scan.
  • The request requires an accreditation the provider does not hold. If a tender requires CREST, Clever Ops is not CREST accredited, so we refer that work to a provider that is.
  • The request asks for an independent tester, and the quote comes from the people who built or host the system. When Clever Ops tests a site it built or hosts, the work is a security review rather than an independent test, and the report says who built and who hosts it.
  • The person who asked for the test wants evidence that serious findings were fixed, and the quote has no retest.

How Clever Ops scopes and quotes a test

Clever Ops tests what customers reach through a browser or an API: websites, WordPress sites and WooCommerce stores, custom web applications and their APIs, apps made with AI builders, and AI chatbots and agents.

We do not publish prices or packages, because the factors on this page decide the work, and a quote follows a free scoping call.

Bring the worksheet on this page to that call. It covers the questions the call needs answered, so the conversation can go straight to the parts of your application that carry the risk. You then receive a written scope and quote naming the targets, environment, routes, roles and exclusions, and what the one included retest covers. Testing begins once the owner of each target has signed an authorisation.

Some work belongs with another kind of provider, and saying so early saves you a scoping round: internal networks and staff devices, phishing, load or denial-of-service testing, and incident response or malware cleanup. Very logic-heavy platforms, such as marketplaces or lending products, are scoped individually or referred to a larger firm.

Frequently asked questions

It depends on the scope, and both Australian providers quoted on this page tie their published figures to it. On 13 November 2026, Siege Cyber listed its web application and API test at $5,900 to $16,500 excluding GST, and Compliance Council's indicative band for one or two applications with three roles and authenticated API testing was $16k to $30k ex GST. Where an application lands depends on its routes, roles, APIs, testing depth, code access, production constraints, reporting and retest. Clever Ops quotes after a free scoping call and does not publish prices.

Mostly because the quotes describe different work. The number of tester-days, whether a tester works through the application or a scan does most of the work, whether the test signs in as every role, and whether a retest is included can each move a quote a long way. Ask every provider to state those four things, then compare scopes before you compare totals.

It depends on the provider and the offer. Of the published Australian offers on this page, one includes a retest in every price, one sells it as an optional extra at $975 excluding GST, and one includes a retest of Critical and High findings within 90 days. Every Clever Ops test includes one consolidated retest of the reported findings, requested within the window set in your statement of work.

Not from Clever Ops. A figure given before the routes, roles and constraints are known would be a guess, and the gap would surface later as a change of scope or a shallower test. The scoping call is free, and the worksheet on this page covers what it asks, so the call can be short.

It is a different purchase. A scan compares what it can reach against known issues and is useful between tests. It does not sign in as each role and try to break the rules your application is meant to enforce, which is where access control and business logic flaws sit. If someone else asked for a penetration test, check that what you buy matches their wording before you sign.

It can, when your application fits inside its limits. Read the role cap, the API limits and the exclusions against what you run. A multi-tenant application, more than three roles or a separately named API can fall outside a fixed scope, and the published fixed-scope offer on this page lists those cases itself.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.