Penetration Testing in Durham, NH
Exploit-driven penetration testing for Durham organizations, reported for engineers and auditors alike. Fixed price, audit-ready reports mapped to ISO 27001, and a free remediation retest.
What you actually get from a penetration test
CyberFortify runs manual web, API, network and cloud penetration tests for Durham organizations, with findings mapped to ISO 27001 and the other frameworks New Hampshire businesses answer to.
Security tooling tells you what is theoretically exposed. A penetration test tells you what a capable attacker would actually do with it. Organizations in Durham in Strafford County operate within New Hampshire’s economy of advanced manufacturing, technology and healthcare, and the systems that run that work — customer-facing applications, the APIs beneath them and the networks they sit on — are exactly what CyberFortify is engaged to test.
The findings that change a roadmap are almost never the ones a tool ranks highest. In Durham engagements they are the quiet ones: a session that survives a password reset, a role that can read another tenant, a bucket reachable without the app in front of it. Those take a person to find.
That is the work CyberFortify does for Durham: a named tester, manual exploitation, and a report written so your engineers can fix what we found and your auditor can accept that it was fixed.
The threats facing Durham organizations
New Hampshire’s economy is not one thing, and neither is its risk. These are the sectors we most often test for Durham organizations, and what an attacker goes after in each.
Manufacturing
Manufacturers increasingly run converged IT and operational-technology networks, where a phishing email that lands in the front office can end up on the plant floor. Downtime is measured in lost production, and ransomware operators know it — manufacturing is among the most-targeted sectors for exactly that reason.
We test the corporate network and the boundary between it and the OT environment, following the paths an attacker would use to move from email to ERP to the systems that control production, with safety and uptime treated as hard constraints.
Technology and SaaS
Software and SaaS companies carry a specific risk: a single flaw is multiplied across every customer on the platform. Multi-tenant isolation, API authorization and the cloud infrastructure underneath are the crown jewels, and a SOC 2 report is now the price of entry for selling to any serious buyer.
We test tenant isolation and object-level authorization across accounts, the API surface your product and integrations expose, and the AWS, Azure or Google Cloud configuration that a single leaked key could turn into a full-tenant compromise.
Healthcare and providers
Provider groups, clinics and digital-health companies hold protected health information across patient portals, scheduling systems, EHR integrations and a widening fleet of connected devices. A single broken authorization check can expose one patient’s record or an entire panel, and the HIPAA Security Rule treats that exposure as a reportable event with real financial and reputational cost.
We test patient portals and their APIs for broken object-level authorization, insecure direct object references and session weaknesses, examine the integrations that move records between systems, and assess whether a compromised clinical workstation can reach data it should never touch.
Penetration testing services for Durham
Pick the services that match your exposure; most Durham clients run two or three together in one engagement.
Web Application Penetration Testing
Broken access control, cross-tenant authorization and business logic, tested by hand.
Cloud Penetration Testing
Over-broad IAM, exposed storage and escalation from one compromised workload.
Mobile Application Penetration Testing
What a decompiled build and a bypassed pin reveal about your mobile app.
API Penetration Testing
Authorization and data-exposure testing for REST and GraphQL interfaces.
Network Penetration Testing
Perimeter exposure and internal domain compromise paths, mapped end to end.
OT & ICS Penetration Testing
Control-network testing that treats safety and uptime as first-order constraints.
Evidence for the frameworks New Hampshire businesses answer to
Because New Hampshire’s economy runs on advanced manufacturing, technology and healthcare, Durham organizations are most often held to these frameworks — a single engagement produces evidence for each.
ISO 27001
Evidence that Annex A controls work, not just that they are documented.
CMMC 2.0
Testing the boundary that protects controlled unclassified information.
HIPAA
Testing the portals, APIs and systems that hold protected health information.
Organizations handling personal data in New Hampshire also fall under New Hampshire Data Privacy Act. It does not name penetration testing, but it expects reasonable security to be verified rather than assumed — and after an incident, a recent test is the evidence that it was.
How a Durham engagement runs
The same sequence every time, so the result is defensible.
Testing aligns to PTES and NIST SP 800-115, application work follows OWASP, and exploitation maps to MITRE ATT&CK. Automated tooling enumerates the surface; a named tester confirms every finding by hand.
Findings your team can fix and your auditor accepts
Every finding is reproducible, scored in context, and tied to the control it defeats.
The example alongside is illustrative — not from a client engagement — to show how each issue is documented and mapped to ISO 27001 and the standards New Hampshire organizations answer to.
| Ref | Finding | Severity | CVSS |
|---|---|---|---|
| F-01 | IDOR exposes cross-tenant records | Critical | 9.1 |
| F-02 | Over-privileged service account | High | 8.2 |
| F-03 | Session persists after reset | Medium | 5.4 |
| F-04 | Verbose error disclosure | Low | 3.1 |
What sets a Durham engagement with us apart
A scan-and-report vendor
Automated output rebadged as a test. Severities the tool assigned, findings you cannot reproduce, no real attempt at authorization logic or privilege escalation — and a report your assessor hands back. The retest is a new invoice.
CyberFortify
A named tester who works the target by hand, chains findings to prove real impact, and writes them so a Durham engineer can fix them and an auditor can accept them. Fixed price, same-day critical escalation, retest included.
Penetration testing in Durham, answered
Is testing done on-site in Durham or remotely?
For the common cases, no. Anything reachable over the internet — web, API, cloud, external network — is tested remotely. On-site is reserved for internal, wireless and physical work, and we agree it and its cost during scoping.
What does a penetration test cost for a Durham business?
There is no per-city rate; cost tracks the size of the engagement — how many apps, cloud accounts, hosts and roles are in scope. You get a fixed quote after scoping, usually the same hour, and it holds for the agreed work.
Will the report satisfy our auditor?
Yes. Every finding carries reproduction steps, CVSS v3.1 scoring and a control mapping, so an assessor can trace a requirement to the test that exercised it. For New Hampshire organizations that most often means ISO 27001, and we scope to the evidence your assessor expects.
What do you focus on for Manufacturing organizations?
We test the corporate network and the boundary between it and the OT environment, following the paths an attacker would use to move from email to ERP to the systems that control production, with safety and uptime treated as hard constraints. In a Durham engagement that usually starts with it-to-ot pivot paths and works outward from there.
Does New Hampshire law require security testing?
Not by name. New Hampshire Data Privacy Act requires reasonable security for personal data rather than a specific test, but a current penetration test is the standard way to show that requirement was met if you are ever questioned after a breach.
Can you sign our vendor security questionnaire?
Yes. We complete SIG, CAIQ and custom questionnaires and can join the vendor review call. For Durham companies selling into larger enterprises, a current test plus a completed questionnaire is usually what unblocks the deal.
What is the lead time for testing in Durham?
Typically within one to two weeks of agreeing scope, and sooner where a deadline requires it. Book a scoping call and you will have a fixed-price quote and a proposed start date, usually within the hour.
Penetration testing near Durham
We work across New Hampshire. See nearby cities or the full state overview.
Test your Durham systems before someone else does.
A 30-minute scoping call gets you a fixed price and a start date, usually within the hour.