Penetration Testing in Ann Arbor, MI
Manual, exploit-driven security testing for organizations in Ann Arbor. Fixed price, audit-ready reports mapped to ISO 27001, and a free remediation retest.
Why a scan is not a penetration test
CyberFortify runs manual web, API, network and cloud penetration tests for Ann Arbor organizations, with findings mapped to ISO 27001 and the other frameworks Michigan businesses answer to.
A scanner produces a list. A penetration tester produces a path — the specific chain of steps that turns a minor flaw into a breach. Organizations in Ann Arbor across Washtenaw County operate within Michigan’s economy of automotive and mobility, advanced manufacturing and healthcare, and the systems that run that work — the web apps, APIs, identity systems and cloud accounts that run day to day — are exactly what CyberFortify is engaged to test.
The findings that change a roadmap are almost never the ones a tool ranks highest. In Ann Arbor 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.
Our Ann Arbor engagements are priced up front, run by hand rather than by scanner alone, and closed out with a retest that proves the fixes held — not a second invoice.
The threats facing Ann Arbor organizations
Risk in Michigan looks different by industry. For the sectors that anchor Ann Arbor, this is what attackers target and what our testing is built to find.
Automotive and mobility
Automotive manufacturers, suppliers and dealer networks span plant-floor OT, connected-vehicle data and dealer systems holding customer finance information. ISO/SAE 21434 and UNECE R155 now set expectations for cybersecurity across the vehicle lifecycle and its supply chain.
We test the manufacturing environment and its IT boundary, the platforms and APIs handling connected-vehicle and customer data, and the dealer-facing systems where personal and financial information concentrates.
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.
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 Ann Arbor
Most engagements combine two or three of these, scoped to where a compromise would cost Ann Arbor the most.
Web Application Penetration Testing
Authenticated testing that finds what an attacker with a valid login could reach.
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.
Cloud Penetration Testing
Over-broad IAM, exposed storage and escalation from one compromised workload.
Mobile Application Penetration Testing
Device-side controls and the server they are supposed to protect.
API Penetration Testing
Authorization and data-exposure testing for REST and GraphQL interfaces.
Evidence for the frameworks Michigan businesses answer to
Given Michigan’s automotive and mobility, advanced manufacturing and healthcare, these are the frameworks a Ann Arbor engagement most often produces evidence for. One test, evidence for all of them.
How a Ann Arbor 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 Michigan 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 Ann Arbor 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 Ann Arbor engineer can fix them and an auditor can accept them. Fixed price, same-day critical escalation, retest included.
Penetration testing in Ann Arbor, answered
Is testing done on-site in Ann Arbor or remotely?
Most of it is remote. Application, API, cloud and external testing does not require us in the building, and that covers the majority of Michigan engagements. Where scope is internal network, wireless or physical, we arrange to be on-site and cost the travel transparently.
What does a penetration test cost for a Ann Arbor business?
It depends on scope rather than where you are. We count applications, cloud accounts, hosts and distinct roles, then quote one fixed price after a short scoping call — typically within the hour, with no hourly meter afterward.
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 Michigan organizations that most often means ISO 27001, and we scope to the evidence your assessor expects.
What do you focus on for Automotive organizations?
We test the manufacturing environment and its IT boundary, the platforms and APIs handling connected-vehicle and customer data, and the dealer-facing systems where personal and financial information concentrates. In a Ann Arbor engagement that usually starts with plant-floor ot exposure and works outward from there.
Can you sign our vendor security questionnaire?
Yes. We complete SIG, CAIQ and custom questionnaires and can join the vendor review call. For Ann Arbor companies selling into larger enterprises, a current test plus a completed questionnaire is usually what unblocks the deal.
How quickly can you begin in Ann Arbor?
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 Ann Arbor
We work across Michigan. See nearby cities or the full state overview.
Test your Ann Arbor systems before someone else does.
A 30-minute scoping call gets you a fixed price and a start date, usually within the hour.