Skip to content
Exploited OpenSSH flaw CVE-2026-123158 lets long passwords bypass sign-in on musl Linux
Black Shard

Loading

    How a penetration test is quoted, and what moves the cost

    A penetration testing quote in Australia follows scope, and there is no standard rate card. Six scoping decisions move a quote, and the cheapest quote in your inbox is usually a vulnerability scan sold as a penetration test.

    Black Shard Guides

    Updated 6 min read

    Share
    On this page
    1. Why nobody can give you a number without a scope
    2. What moves the price
    3. Penetration testing prices in Australia, by engagement type
    4. Why the cheapest quote in your inbox is usually a scan
    5. Scoping is the one lever that makes any of these numbers real
    6. How to get a penetration testing quote in Australia
    7. The practical takeaway

    Why nobody can give you a number without a scope

    Typical Australian market range, November 2026: A$5,000 to A$15,000 ex GST for an external network test, A$5,000 to A$30,000 ex GST per web application, and A$10,000 to A$30,000 ex GST for an internal network test. The bands come from published Australian pricing guides and provider pages and describe the market as a whole. A Black Shard quote is set by your scope.

    A penetration test is skilled human time, and skilled human time is what you are pricing when you ask for a quote. Two requests that read identically on the surface, test our web app, can differ several times over in the tester-days behind them, depending on how many roles the application has, whether the tester works with credentials or without, and whether staging sits alongside production in scope. The word application hides all of that variation.

    A provider's advertised entry figure is useful when it names exactly what it buys. A useful quote for the rest follows a conversation about your systems, because the scoping questions are what turn that figure into a fixed one.

    What moves the price

    Strip away the marketing and a quote comes down to a small set of decisions, each of which changes how many tester-days the work takes. Ask a provider to walk through these before comparing any two numbers.

    • Attack surface: how many applications, APIs, hosts and live environments are in scope, and how many distinct user roles each application carries
    • Methodology depth: an unauthenticated surface sweep versus authenticated testing of every role, since almost everything that matters in a modern application sits behind the login
    • Environments: production alone, or production plus staging and development, each one adding testing time
    • Reporting depth: a findings list versus a ranked report with reproduction steps, business impact, and a specific fix for every issue
    • Retest: whether verifying that the fixes landed is inside the original price or billed again once the report is delivered
    • Delivery: remote scoping and testing, or on-site work with the travel and coordination that adds

    Penetration testing prices in Australia, by engagement type

    The figures below describe how the Australian market generally prices these engagements. They are not a quote, and every range can be pushed well past its top end by an environment that is larger, more tenanted or more regulated than the average, just as it can be undercut by a provider selling something narrower than the label on the invoice suggests. Treat them as a shape to sanity-check a quote against; they are not a number to hold anyone to.

    A single small web application with a couple of user roles, tested by a provider issuing test credentials, tends to sit toward the bottom of its band. A multi-tenant platform with a dozen roles, an admin console and an API surface of its own pushes the same category well past the top. The pattern repeats across every row: scope decides where in the range you land far more than the category label does.

    • Engagement type: Vulnerability scan (included for contrast; it is not a penetration test)

      What it typically covers
      Automated, signature-based scanning of hosts and services, one-off or on a schedule
      Typical market range (AUD)
      Low hundreds a month for continuous scanning; low thousands for a one-off pass across a modest estate
      What pushes it toward the top
      Host count and how often it runs; there is no manual work to scale with depth
    • Engagement type: Web application penetration test

      What it typically covers
      One application, tested authenticated across its roles, against the OWASP playbooks
      Typical market range (AUD)
      Roughly $5,000 to $30,000 per application
      What pushes it toward the top
      Extra roles, an admin tier, an API of its own, or multi-tenancy that needs the tenant boundary tested; complex platforms pass $40,000
    • Engagement type: External network penetration test

      What it typically covers
      What an internet attacker can reach from outside the perimeter
      Typical market range (AUD)
      Roughly $5,000 to $15,000
      What pushes it toward the top
      A larger internet-facing footprint and more discrete services exposed to it
    • Engagement type: Internal network penetration test

      What it typically covers
      An assumed-breach foothold, measuring how far it goes: lateral movement, privilege escalation, Active Directory
      Typical market range (AUD)
      Roughly $10,000 to $30,000
      What pushes it toward the top
      More sites, more segments, a larger directory, and on-site delivery; multi-site estates reach about $55,000
    • Engagement type: External and internal combined

      What it typically covers
      Both of the above run together as one engagement, priced as a package
      Typical market range (AUD)
      Roughly $18,000 to $45,000
      What pushes it toward the top
      Everything above, plus the coordination of running both in one window
    • Engagement type: Social engineering or phishing simulation

      What it typically covers
      A campaign against a defined user population, measuring what people click and report
      Typical market range (AUD)
      Roughly $4,000 to $10,000 per campaign
      What pushes it toward the top
      Multiple rounds, a larger user population, or pairing email with vishing or physical pretexting
    Typical Australian market ranges by engagement type, November 2026, in Australian dollars. Published guides that state a GST basis quote excluding GST.

    Why the cheapest quote in your inbox is usually a scan

    A handful of tells separate a genuine penetration test quote from a vulnerability scan sold under that name, and none of them require reading the fine print. The price scales cleanly with a number typed into a form, IP count or page count, rather than following a conversation about what the business is trying to protect.

    Turnaround is quoted in a day or two, which is enough time for a tool to run but not enough for a person to enumerate, chain and write up findings by hand. Nobody asks for test credentials, because there is no login to test from the inside, only a perimeter to sweep from outside it. The report, when a sample is offered, reads as a list with the same generic remediation text attached to every instance of the same finding, and no named tester is attached to the work.

    None of that makes a scan a bad product. Automated scanning is cheap for a reason: it is software, it is fast, and it is worth running continuously rather than once. The problem is only the label.

    A scan priced and delivered as a penetration test sells a buyer pentest expectations, human validation, chained findings, business-logic testing, at scan depth, and the gap only becomes visible when the report lands or when an auditor asks a question the document cannot answer. Our note on the difference between the two, and our guide to choosing the right assessment for where you are, cover the mechanics of what each instrument finds and what it structurally cannot.

    Scoping is the one lever that makes any of these numbers real

    Everything above is a market shape. The number that applies to your systems comes out of a scoping conversation, and three decisions inside that conversation move it more than anything else. Name the actual objective: the customer database, the tenancy boundary, the ability to reach production, so effort goes where compromise would hurt instead of spreading evenly across everything.

    Decide upfront whether authenticated testing across every role is included, since a quote that withholds credentials is pricing a perimeter check and calling it an application test. And settle what a retest looks like before you sign anything: whether verifying the fixes is inside the fixed price or a second invoice once the report is in your hands.

    The rest of a penetration test scope covers environments and exclusions, timing windows and rules of engagement, and the questions a competent provider asks before quoting anything at all.

    How to get a penetration testing quote in Australia

    Black Shard quotes every penetration test as a fixed scope, with the price and the timeframe set in writing before work starts. An external penetration test under Black Shard's penetration testing service in Australia comes with a written report and a re-test of the reported findings.

    The quote names its drivers: the size of the attack surface, the number of environments in scope, tenancy count for multi-tenant products, and whether any of the work needs to run on-site. The re-test sits inside the fixed scope, and rules of engagement are agreed in writing before testing begins.

    A free 30-minute scoping call produces the quote, or a brief through the contact form or to info@blackshard.com.au starts scoping from the detail you have and works out whichever of these details are still open.

    • The applications, APIs, networks or cloud environments in question, and whether each is internet-facing or internal
    • The user roles in each application, and whether test accounts can be issued for every role
    • The environments in scope: production, staging, or both
    • For a multi-tenant product, the tenancy count and whether the tenant boundary is in scope
    • Whether any of the work needs to run on-site
    • The deadline the report has to meet, such as an audit, a tender or a customer security review, and who will read it

    The practical takeaway

    Use the ranges above to sanity-check a quote. They are not a basis for negotiating one. If a number comes in well under its band, ask what is missing: credentials, a retest, a named tester, a report that goes beyond a findings list, a penetration test attestation letter you can hand to a customer.

    If it comes in well over, ask what in your scope is driving that, and expect a specific answer. Either way, the conversation that produces a real number is the same one that produces a useful test: it starts from what you are trying to protect and what it would cost you if someone reached it.

    Tell us what you need tested.