Penetration Testing in Lake Oswego, OR
Human-led penetration testing for Lake Oswego 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 Lake Oswego organizations, with findings mapped to SOC 2 and the other frameworks Oregon businesses answer to.
Every organization assumes its controls work. A penetration test is how you find out whether they do before someone else does. Organizations in Lake Oswego in Clackamas County operate within Oregon’s economy of technology and semiconductors, manufacturing and forestry, and the systems that run that work — public applications, internal systems and the cloud infrastructure tying them together — are exactly what CyberFortify is engaged to test.
Businesses in Lake Oswego carry the same exposure as their larger peers elsewhere, often with leaner security teams. Broken access control, authorization logic that trusts the client, and segmentation that exists on a diagram but not in the routing table are the findings that recur — and the ones no scanner reports.
Our Lake Oswego 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 Lake Oswego organizations
Oregon’s economy is not one thing, and neither is its risk. These are the sectors we most often test for Lake Oswego organizations, and what an attacker goes after in each.
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.
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 Lake Oswego
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
Broken access control, cross-tenant authorization and business logic, tested by hand.
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.
Network Penetration Testing
Whether your segmentation holds once someone is already inside the network.
OT & ICS Penetration Testing
IEC 62443-aligned assessment of the plant floor and its SCADA systems.
Cloud Penetration Testing
Over-broad IAM, exposed storage and escalation from one compromised workload.
Evidence for the frameworks Oregon businesses answer to
These are the frameworks that bite hardest for Lake Oswego businesses, given Oregon’s technology and semiconductors, manufacturing and forestry. We scope one test to satisfy all of them at once.
SOC 2
The testing behind CC7 that turns a claimed control into a demonstrated one.
ISO 27001
The independent testing your ISO auditor expects for technical controls.
HIPAA
What a Security Rule evaluation expects: controls verified, not assumed.
Organizations handling personal data in Oregon also fall under Oregon Consumer Privacy Act (OCPA). 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 Lake Oswego 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 Oregon 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 Lake Oswego 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 Lake Oswego engineer can fix them and an auditor can accept them. Fixed price, same-day critical escalation, retest included.
Penetration testing in Lake Oswego, answered
Do you need to be on-site in Lake Oswego?
Usually not. Web, API, cloud, mobile and external network testing is delivered remotely from our US-based team, which is how most Lake Oswego engagements run. Internal network, wireless and physical assessments are the cases where we come on-site, and travel is quoted up front.
How is pricing set for a Lake Oswego engagement?
Price follows scope, not location. The variables are the number of applications, cloud accounts, live hosts and user roles in scope. After a 30-minute scoping call we return a fixed price, usually within the hour, and it does not change once work begins.
Will the report satisfy our auditor?
It is designed to. Each finding is reproducible, scored and tied to the control it breaks, which is what an assessor needs. For most Oregon businesses the relevant framework is SOC 2, and we scope the engagement to it directly.
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 Lake Oswego engagement that usually starts with cross-tenant data access and works outward from there.
Is penetration testing mandated in Oregon?
Oregon does not name penetration testing outright, but Oregon Consumer Privacy Act (OCPA) 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 Lake Oswego 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 Lake Oswego?
Most Lake Oswego 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 Lake Oswego
We work across Oregon. See nearby cities or the full state overview.
Test your Lake Oswego systems before someone else does.
A 30-minute scoping call gets you a fixed price and a start date, usually within the hour.