← Blog Published November 20, 2026

Blue Magma · Guides

Does SOC 2 require a penetration test? Short answer: no. Long answer: yes.

Ian Martin, co-founder at Blue Magma

November 20, 2026

A founder asked me this last month and then answered it himself before I could: "SOC 2 doesn't actually require a pen test, right? I read that somewhere." He's right. He's also going to need one. Both of those are true at the same time, which is the most SOC 2 thing I can think of.

So let me untangle it, because the gap between what the standard says and what your auditor expects is exactly where founders either overspend out of fear or skip something and blow up their timeline two weeks before the report.

What the standard actually says

The AICPA's Trust Services Criteria never once tell you to buy a penetration test. There's no line item, no frequency, no mandate. As the folks at SOC 2 Auditors put it plainly, "SOC 2 does not require a penetration test, and the AICPA's Trust Services Criteria set no testing frequency". If someone tells you it's required by the framework, they're repeating a thing they heard, not reading the document.

The word shows up in exactly one spot, and it shows up as an example. Under CC4.1, the monitoring criterion, penetration testing is listed as one option alongside vulnerability scans and third-party assessments. It's a "you could do this" not a "you must do this." A different control, CC7.1, asks for periodic vulnerability scans, which is a separate thing entirely: automated, checking a defined set of targets for known weaknesses. A pen test is a human trying to break in under agreed rules.

That distinction matters more than people realize. A scan is a smoke detector. A pen test is someone actually trying to light a fire to see what catches. Your auditor cares about both, but they're not the same purchase and they're not interchangeable.

So why does everyone end up buying one

Because "not required by the framework" and "not required for your audit" are different sentences.

A pen test becomes mandatory for you through three doors, and almost every company walks through at least one. First, your own system description. If you write "we perform annual penetration testing" into your controls, congratulations, you just made it required for yourself, and your auditor will ask for the report. Second, the evidence your CPA firm needs to feel good about CC4.1. Most auditors have decided a pen test is the cleanest way to show you actually monitor and evaluate your controls, so they expect to see one even though the standard only offers it as an example. Third, your customers. The enterprise prospect holding up your biggest deal does not care what the AICPA technically mandates. Their security questionnaire asks for a recent pen test report, and "the framework didn't require it" is not an answer that closes the contract.

"Not required by the framework" and "not required for your audit" are different sentences, and the second one is the one that signs the check.

Here's the trap I watch founders fall into. They read a blog saying it's optional, they leave it out of the plan, and then the auditor asks for it in month three of the observation window. Now you're scrambling to schedule a tester, waiting on results, and remediating findings while the clock on your Type II is running. The thing you saved by skipping it early costs you triple in panic later. We've written before about how "later" already lost the deal, and this is a clean example of it.

What it costs in 2026

This is where the real decision lives, because pen testing prices are all over the map and the range is wide enough to make your eyes water.

For a web application, the spread tells the whole story. On the low end, Affordable Pentesting lists web app testing "from $3,000" and Blaze Infosec starts at "$4,999," with a simple SaaS app running "$4,999 to $8,999 for 3 to 7 testing days". On the higher end of the same scope, Synack lists a human-led web application test whose scope explicitly names SOC 2 at "$10,283". Same category of thing, roughly double the price, and the difference is almost entirely about who is doing the testing and how deep they go.

The pattern underneath all those numbers is worth memorizing. As that same breakdown summarizes it, "a single-scope test on a web application or API generally starts between $3,000 and $5,000," while "human-led testing scoped for a compliance framework" lands "closer to $10,000". If you want the number to put in your budget before you've scoped anything, ten thousand for a real human-led test against your app is a safe place to anchor.

If you'd rather think in day rates, the labor math is out there too. Budget Security puts human tester rates at "$985 per tester-day," and Blaze Infosec quotes "$250 to $300 per hour". Multiply that by the testing days for your scope and you'll land in the same neighborhood as the fixed-price quotes, which is a decent gut check that a quote is honest.

How to actually decide

Don't buy a pen test because a blog scared you. Buy the right one for where you are. Here's the order I'd run it in.

The sequence that keeps you out of trouble:

  1. Write your controls carefully. Before you commit to "annual penetration testing" in your system description, know that you're binding yourself to it. Match the words to what you'll actually do.
  2. Ask your auditor what they expect, in writing, before you scope anything. Most expect a pen test for CC4.1. Knowing their bar before you buy stops you from over-scoping or under-scoping.
  3. Time it to your observation window, not your panic. Schedule it early enough that you can remediate findings and retest before the report closes. A pen test with open critical findings and no fix is worse than no pen test.
  4. Keep the report fresh. Customers and auditors want a dated, recent one. A two-year-old pen test is a question mark on your biggest deals, so treat it as an annual cycle, not a one-time box to check.

The honest summary: SOC 2 does not require a penetration test, and you will almost certainly do one anyway, and that's fine. Just do it on purpose, scoped to your actual systems, timed so the findings help you instead of ambushing you. The founders who treat it as a planned part of the program spend less and sleep better than the ones who treat it as a surprise tax.

How we handle this for you

This is the kind of thing I don't want on your plate. At Blue Magma we run the SOC 2 work for you, which means we track the pen test and risk assessment cycles as part of the program, scope the test to what your auditor actually expects, and manage the auditor through the report so the findings land when you can still act on them. You keep sign-off on everything that goes out under your name. I don't want SOC 2 to be your priority. I want it to be mine, so you can get back to your customers. Down for a chat?

Blue Magma

Stop managing compliance manually.

Blue Magma's AI maps your infrastructure, collects evidence automatically, and keeps you audit-ready — from early-stage startup to enterprise. Built from your org up, not a template down.

Begin onboarding for FREE Book a demo