Penetration Testing for Small Businesses: What It Is, What Drives the Cost, and When You Need One

Quick take
- A penetration test (pen test) is a hired, permitted “fake attack” that shows how far a real hacker could get.
- Some rules require one: the FTC Safeguards Rule (for many non-bank financial firms) and PCI DSS (if you handle card payments). HIPAA may require one soon.
- There is no honest one-size price. Cost depends on what you test, so scope it from a risk assessment first.
A customer, insurer or auditor just asked: “Have you had a penetration test?”
If you’re not sure what that means, you’re not alone. This guide explains it in plain English.
You’ll learn what a pen test is, how it differs from a scan, which rules call for one, and how to plan one that’s worth the money.
What is a penetration test?
A penetration test is a simulated attack that you approve in advance.
A trained tester tries to break in the way a real attacker would. Then they write down how far they got and how to fix it.
The FTC’s Safeguards Rule defines it as a test where assessors “attempt to circumvent or defeat the security features of an information system” from outside or inside your systems (16 CFR 314.2(n)).
A good test is more than hacking. NIST’s testing guide, NIST SP 800-115, says it also needs:
- A written testing policy
- Careful planning of what to test and how
- Safe execution
- Finding the root cause of each problem
- A report that turns findings into real fixes
Vulnerability scan vs. pen test
People mix these up all the time. Here’s the difference:
- Vulnerability scan: an automated tool checks for known weak spots, like missing updates or old software. It’s fast and broad. But it doesn’t prove a hacker could actually use the weakness.
- Penetration test: a person links weak spots together to show real damage. Example: going from one stolen password to your customer files. It goes deeper and gives you proof.
Regulators treat them as two separate jobs. The FTC Safeguards Rule lists a yearly pen test and a vulnerability check every six months as different requirements (16 CFR 314.4(d)(2)).
Most businesses need both. Scan often to catch easy problems. Pen test from time to time to find what scanners miss.
Does my business need one?
Not every business is legally required to test. But several common rules require it or are heading that way.
FTC Safeguards Rule (non-bank financial businesses)
This rule covers many financial businesses that aren’t banks. They must test or monitor their security.
Unless they run “effective continuous monitoring,” they must do a pen test every year. They also need vulnerability checks at least every six months and after big changes (16 CFR 314.4(d)(2)).
Exception: that testing rule doesn’t apply if you keep customer information on fewer than 5,000 consumers (16 CFR 314.6). You still have the general duty to test or monitor.
PCI DSS (businesses that take card payments)
PCI DSS is the security standard for anyone who stores, processes or sends card data.
Version 4.0.1 requires internal and external pen tests at least once every 12 months. You also need one after any major system change (PCI DSS Requirement 11.4.2).
The tester must be qualified and independent. Your payment processor can tell you how this applies to you. The official standard is in the PCI Security Standards Council document library.
HIPAA (healthcare practices and their vendors)
Today’s HIPAA Security Rule requires a thorough risk analysis and a “periodic technical and nontechnical evaluation.” It does not name pen testing (45 CFR Part 164, Subpart C).
That may change. In January 2025, HHS proposed requiring a pen test “at least once every 12 months” (Federal Register, Jan. 6, 2025).
It’s still only a proposal. In July 2026, HIPAA Journal reported the target date for a final rule is now July 2027.
New Jersey healthcare practices can use that time to get a first test done before it becomes required.
What drives the cost?
We won’t quote a generic price, because there isn’t an honest one. Two “pen tests” can be very different amounts of work.
These are the things that shape the price:
- Size: how many internet-facing addresses, office networks, locations, cloud accounts and staff are included.
- Type of test: outside network, inside network, website or app, cloud setup, Wi-Fi, or phishing (fake scam emails to staff). Each is its own job.
- How complex your apps are: a simple website is very different from a customer portal with logins, payments and APIs (connections between software).
- How much the tester knows up front: nothing (“black box”), some logins and documents (“gray box”), or full details (“white box”).
- Compliance needs: whether the report must match PCI DSS, the Safeguards Rule, HIPAA or a customer’s rules.
- Scheduling: after-hours testing, or a tight deadline for an audit or contract.
- Retesting: whether a follow-up test to confirm your fixes is included. PCI DSS expects problems to be fixed and checked again (Requirement 11.4).
Small businesses often overspend by buying the wrong size test. Too broad, and it’s not affordable. Too narrow, and it misses where your sensitive data lives.
The fix is to plan the test from a risk assessment. That’s also what the Safeguards Rule requires (16 CFR 314.4).
Free resources
- CISA Cyber Hygiene services: free scanning of your internet-facing systems and websites. It’s only for government groups and critical infrastructure organizations (CISA). CISA also lists other free cybersecurity tools.
- NJCCIC membership: New Jersey’s state cybersecurity office offers free membership with alerts, warnings about weak spots, and weekly updates (NJCCIC).
Pen test checklist
- List what you need to protect: customer data, card data, health records, money systems.
- Confirm which rules apply to you: Safeguards Rule, PCI DSS, HIPAA, customer contracts, cyber insurance.
- List everything that faces the internet: websites, portals, remote access, email and cloud services.
- Write or update a risk assessment so the test matches your real risks.
- Run vulnerability scans first and fix the easy problems.
- Pick a qualified, independent tester. Get written permission and clear rules.
- Agree on testing times and an emergency contact in case something breaks.
- Ask for a short summary for leaders plus technical details for IT.
- Fix the biggest risks first, then retest to confirm the fixes worked.
- Keep reports and fix records. PCI DSS expects them kept for at least 12 months (Requirement 11.4.1).
- Put the next test on the calendar, and test again after big changes.
Get a free risk assessment from a Newark team
Gr8 Eagle Cyber helps small and midsize businesses in Newark, across New Jersey and beyond with pen testing, vulnerability management, risk management and compliance.
Every job is planned around your setup and your rules. No one-size-fits-all package.
Got a questionnaire, audit or insurance renewal on your desk? Contact us for a free consultation and risk assessment. We’ll help you decide what testing you actually need before you spend a dollar.
Sources
- eCFR: 16 CFR 314.2, Definitions (FTC Safeguards Rule)
- eCFR: 16 CFR 314.4, Elements (FTC Safeguards Rule)
- eCFR: 16 CFR 314.6, Exceptions (FTC Safeguards Rule)
- PCI DSS v4.0.1 Requirement 11.4.2 (PCIComplianceHub)
- PCI DSS v4.0.1 Requirement 11.4.1 (PCIComplianceHub)
- PCI Security Standards Council: Document Library
- eCFR: 45 CFR Part 164, Subpart C (HIPAA Security Rule)
- Federal Register: HIPAA Security Rule To Strengthen the Cybersecurity of ePHI (proposed rule, Jan. 6, 2025)
- HIPAA Journal: HIPAA Security Rule Update Postponed (July 8, 2026)
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment
- CISA: Cyber Hygiene Services
- CISA: No-Cost Cybersecurity Services and Tools
- NJCCIC: Membership