United States Coverage

Penetration Testing Services in the United States

Manual penetration testing for U.S. enterprises that take regulators seriously. We deliver SOC 2, HIPAA, PCI DSS v4.0.1, GLBA Safeguards and NIST 800-53 aligned engagements led by senior offensive security testers, and every finding is manually verified.

This service is for U.S. financial services firms and fintechs, energy operators, SaaS platforms and federal supply-chain contractors that need penetration testing evidence an auditor or assessor can follow.

Prefer to talk? Call +1 307 310 7808

U.S. Compliance Frameworks We Map To

Penetration testing evidence can support each of the frameworks below. Some name penetration testing directly and some leave the method to you. We can map findings to them, but listing a framework here does not mean OraSec is certified under it.

SOC 2 Type II

The AICPA Trust Services Criteria are outcome-based and cover how an organization evaluates and monitors its controls. A penetration test is a common way to evidence that work, and customers and auditors often ask for one, so agree on scope and timing with your auditor before testing starts.

HIPAA Security Rule (45 CFR §164.308–§164.312)

§164.308(a)(1)(ii)(A) requires an accurate and thorough risk analysis, and §164.308(a)(8) requires periodic technical and nontechnical evaluation. Neither provision names penetration testing, but a test can provide evidence for both, with findings tracked through remediation.

PCI DSS v4.0.1: Requirement 11.4

Internal (11.4.2) and external (11.4.3) penetration testing is required at least once every 12 months and after any significant infrastructure or application upgrade or change. Exploitable vulnerabilities must be corrected according to your risk assessment and retested (11.4.4), and segmentation controls must be tested if segmentation isolates the CDE (11.4.5).

GLBA Safeguards Rule (16 CFR Part 314)

Unless you have effective continuous monitoring, §314.4(d)(2) requires annual penetration testing and vulnerability assessments at least every six months. The requirement comes from the FTC's 2021 amendments and applies to financial institutions under FTC jurisdiction, except those holding customer information on fewer than 5,000 consumers.

NIST SP 800-53 Rev. 5

CA-8 covers penetration testing, and its enhancement CA-8(1) covers using an independent agent or team. RA-5 covers vulnerability monitoring and scanning, and SI-2 covers flaw remediation. NIST developed the catalog under its FISMA responsibilities, and FedRAMP's Rev5 baselines draw on it. Which controls apply depends on your baseline.

CMMC Level 2

For contractors handling CUI, CMMC Level 2 security requirements are identical to NIST SP 800-171 Rev. 2. The Department of War suspended CMMC Phase II in July 2026, which paused new C3PAO assessment requirements, so check current guidance on which assessment your contract calls for. Penetration testing can support evidence for security control assessment (CA.L2-3.12.1) and vulnerability scanning (RA.L2-3.11.2).

What Each U.S. Sector Typically Needs

Requirements differ by sector. This is what organizations in each one typically ask a penetration tester to cover.

Financial services & fintech

Unless a limited exemption applies, NYDFS 23 NYCRR Part 500 requires covered entities to run penetration testing at least annually, from inside and outside their system boundaries. Testing typically covers trading platforms, banking apps and payment APIs.

Healthcare, payers & digital health

HIPAA-aligned reporting covering EHR systems, telehealth platforms, FHIR APIs and medical device gateways.

SaaS & technology

Multi-tenant isolation, SSO/OAuth, customer-data segregation and SOC 2 evidence collection for U.S. SaaS vendors selling into regulated markets.

Government & defense supply chain

CMMC Level 2 preparation, FedRAMP assessment support and CUI environment testing aligned with NIST SP 800-171 and SP 800-53 control families.

Legal & professional services

ABA Model Rule 1.6(c) expects lawyers to make reasonable efforts to prevent unauthorized access to client information. Testing typically covers client-confidentiality risk and deal data, and supports supply-chain due diligence.

Manufacturing & critical infrastructure

CISA's Cybersecurity Performance Goals and the ISA/IEC 62443 series are common reference points. Testing typically covers segmentation between IT and OT environments.

How Delivery Works for U.S. Teams

U.S. penetration testing isn't just a technical exercise. It often feeds the evidence behind an auditor's opinion or an assessor's report. That means reports need to read clearly to a SOC 2 service auditor, a HIPAA security officer, a PCI QSA or a contracting officer, depending on which rules apply to your business. Our team writes findings in language those readers expect.

U.S. engineering teams generally need triage during their working day. Our delivery shifts cover ET through PT, so kickoff, daily status and finding triage fall within your working hours in any of the four mainland time zones, and high-severity findings are escalated within four business hours.

Built for U.S. Buyers

  • ET–PT business-hour coverage with same-day triage
  • USD invoicing and SOC 2 / HIPAA / PCI DSS familiarity
  • Retest included to validate fixes before re-audit
  • MSA, BAA and DPA agreements available on request

Talk to a Penetration Tester

Tell us about the regulator on your back, the audit on the calendar, or the app you're shipping next week. We'll come back with a scoped engagement plan.

Frequently Asked Questions — U.S.

Are OraSec penetration testing reports HIPAA-aligned for U.S. healthcare organizations?+

Yes. Our reports can support your risk analysis under §164.308(a)(1)(ii)(A) and your evaluation under §164.308(a)(8). Those provisions do not name penetration testing, so the report is supporting evidence for your HIPAA program, not a compliance determination.

Can OraSec perform the penetration testing PCI DSS Requirement 11.4 calls for?+

Yes. Our PCI DSS engagements cover internal and external testing (11.4.2 and 11.4.3), segmentation testing where segmentation isolates the CDE (11.4.5) and retesting to verify corrections (11.4.4).

Do you support SOC 2 Type II penetration testing evidence?+

Yes. Every finding is manually verified and a retest is included, so your auditor can see that fixes were checked. Agree on scope and timing with your auditor before testing starts.

How does OraSec handle time-zone coverage for U.S. clients outside the East Coast?+

Our delivery model covers U.S. business hours across all four mainland time zones. Kickoff, daily status, and finding triage occur within your working day, and high-severity findings are escalated within four business hours regardless of whether the discovery happened during U.S. or overnight execution windows.

Also Operating in the United Kingdom?

UK Penetration Testing