Penetration Testing in Herriman, UT
Human-led penetration testing for Herriman businesses and the systems they run on. Fixed price, audit-ready reports mapped to SOC 2, and a free remediation retest.
Why a scan is not a penetration test
CyberFortify runs manual web, API, network and cloud penetration tests for Herriman organizations, with findings mapped to SOC 2 and the other frameworks Utah 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 Herriman, part of Salt Lake County, operate within Utah’s economy of technology and SaaS, financial services 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 Herriman 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 Herriman: 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 Herriman organizations
The threats that matter in Utah track the work Herriman organizations actually do — here is where compromise tends to start in the sectors that define the local economy.
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.
Financial services
Banks, credit unions, insurers, fintechs and payment companies are the most directly targeted sector there is, because the payoff is immediate. Attackers pursue account-takeover, business email compromise and wire fraud, and the systems in scope — online banking, payment APIs, lending platforms — sit under GLBA, the FTC Safeguards Rule and PCI DSS at once.
We test authentication and transaction logic for account-takeover and authorization flaws, payment and API flows for business-logic abuse, and the internal paths a fraudster or compromised employee would take toward money movement and customer data.
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 Herriman
You rarely need all of these at once — we scope to the systems where a breach would hurt and start there.
Web Application Penetration Testing
Every user role exercised for the authorization and logic flaws scanners miss.
API Penetration Testing
Testing the endpoints your web app, mobile app and partners actually depend on.
Network Penetration Testing
External perimeter and internal Active Directory, tested the way an intruder moves.
OT & ICS Penetration Testing
Where a compromised business network reaches equipment that moves the physical world.
Cloud Penetration Testing
Over-broad IAM, exposed storage and escalation from one compromised workload.
Mobile Application Penetration Testing
Local storage, certificate pinning and the API behind the app.
Evidence for the frameworks Utah businesses answer to
Given Utah’s technology, financial services, healthcare and mining, these are the frameworks a Herriman engagement most often produces evidence for. One test, evidence for all of them.
SOC 2
The testing behind CC7 that turns a claimed control into a demonstrated one.
PCI DSS 4.0
The annual and post-change testing the standard requires, scoped correctly.
HIPAA
The technical half of a Security Rule risk analysis for regulated health data.
Organizations handling personal data in Utah also fall under Utah Consumer Privacy Act (UCPA). 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 Herriman 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 SOC 2 and the standards Utah 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 Herriman 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 Herriman engineer can fix them and an auditor can accept them. Fixed price, same-day critical escalation, retest included.
Penetration testing in Herriman, answered
Do you need to be on-site in Herriman?
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 Herriman 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.
Is the report accepted by auditors and enterprise customers?
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 Utah organizations that most often means SOC 2, and we scope to the evidence your assessor expects.
What do you focus on for Technology organizations?
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. In a Herriman engagement that usually starts with cross-tenant data access and works outward from there.
Does Utah law require security testing?
Utah does not name penetration testing outright, but Utah Consumer Privacy Act (UCPA) expects organizations to maintain and verify reasonable security for personal data. After an incident, assuming it was secure is not a defense — a recent test is the evidence it was checked.
Can you sign our vendor security questionnaire?
Yes. We complete SIG, CAIQ and custom questionnaires and can join the vendor review call. For Herriman 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 Herriman?
Most Herriman engagements begin one to two weeks out, or faster against a hard deadline. A scoping call gets you a fixed price and a start date the same hour in most cases.
Penetration testing near Herriman
We work across Utah. See nearby cities or the full state overview.
Test your Herriman systems before someone else does.
A 30-minute scoping call gets you a fixed price and a start date, usually within the hour.