Compliance

Phase 1, Phase 2, then keep it running

A fixed-price gap analysis, remediation through to your audit, and upkeep after it. All in a workspace you keep.

All compliance →
Security

Testing, review and leadership

Led by a published security researcher with five CVEs. A findings report, a letter of attestation for your buyers, and a retest of your fixes.

All security →
Who we help

Prove you are secure

To the people you sell to, raise from or answer to.

All industries →
Resources

Learn the space

Original research, free tools, and plain-language guides on security and compliance, from a published security researcher.

Read the blog →
Security

From OSCP to Paid Client Work: What Changes After the Exam

Moving from OSCP to paid pentest work means trading an exam built around compromising machines for engagements built around a client's scope, risk and report. The exploitation skills carry over. What changes is everything around them: written authorization, scope limits, coverage against a method, client communication, report quality under review, and retesting fixes after the client remediates.

What the exam proves, and what it does not

OSCP is a respected practical credential. Passing it shows you can enumerate a network, find a way in, escalate privileges and document what you did under time pressure. Firms read it as evidence that you can work through a hands-on problem without someone handing you the answer. That is a real signal, and it is why many firms treat it as a baseline for junior and intermediate testers.

What the exam cannot show is how you behave when the goal is not "get root." On a paid engagement, the goal is to give a client an accurate picture of the risk in a defined set of systems, in a form they can act on and hand to an auditor or a customer. Those are different jobs, and the gap between them is where most new testers stumble.

Exam habits that need to change

Exploit everything versus prove enough

The exam rewards full compromise. Client work usually rewards demonstrating impact with the least disruption. If you can show that an SQL injection exposes a customer table by reading one redacted row, you do not dump the table. If a remote code execution path exists on a production server, you typically confirm it in a controlled way and stop, or ask before going further. The rules of engagement often say this explicitly, and they may forbid denial of service, destructive payloads or persistence entirely.

Anything reachable versus what is in scope

In an exam, every machine on the network is a target. On a client engagement, the scope names specific hostnames, URLs, API paths, cloud accounts or ranges, and everything else is off limits, including third-party services the client uses but does not own. In Canada, accessing a computer system without authorization can be an offence under section 342.1 of the Criminal Code. If you find credentials that would open a system outside the scope, the correct action is to stop, document and ask.

Your own pace versus a client's window

Client testing happens in agreed windows, from known source IP addresses, with named contacts who need to know if something breaks. You may be asked to pause because of a release, or to slow a scan because their monitoring is paging someone at 2 a.m. Responding quickly and calmly to those requests is part of the work.

Method and coverage replace instinct

Exam strategy rewards following the most promising lead. Paid testing rewards covering the scope systematically, because the client is paying for assurance across the whole target, not for the single most interesting bug. Most firms anchor that coverage to published methods:

  • PTES for the overall shape of an engagement: pre-engagement, intelligence gathering, threat modelling, vulnerability analysis, exploitation, post-exploitation and reporting.
  • The OWASP Web Security Testing Guide for web application test cases, from configuration and authentication through session management, authorization, input validation and business logic.
  • OWASP ASVS as a requirements baseline when the client wants to know how an application measures up against a defined level.

In practice, that means a coverage checklist: each area in scope, each test case, the result and where the evidence lives. It feels slow at first. It is also what lets a reviewer confirm that the authorization testing for every role happened, and what protects you when a client later asks whether a specific issue was checked. Authorization and business logic flaws are often the most valuable findings in a web test, and they rarely appear in exam-style environments.

Client communication is part of the deliverable

An exam has no client. A paid engagement has several people with different interests: an engineering lead who wants clear reproduction steps, a CTO who wants to know if the business is exposed, and sometimes a compliance owner who needs the report for an audit. Expect to:

  • Join a kickoff call to confirm scope, accounts, windows and contacts.
  • Report critical findings promptly during testing rather than holding them for the final report, if the rules of engagement call for it.
  • Answer questions about findings without becoming defensive, and adjust when the client shows you context you did not have.
  • Explain risk in business terms, not only in CVSS vectors.

Report quality is what gets you hired again

The exam report proves you completed the objectives. A client report has to stand on its own months later. Each finding needs a clear title, a severity under a stated and consistently applied rating method, the affected asset, reproduction steps someone else can follow, evidence, business impact in plain language, remediation specific to the client's technology, and a retest status. The report also needs an executive summary a non-technical reader can absorb quickly, and a scope and method section that matches what you actually tested.

Common early mistakes: scanner output pasted as findings, unverified false positives, inflated severity to make the report look busy, and copied remediation that does not fit the stack. Our post on what a security deliverable looks like shows a full structure, and what a SOC 2 auditor accepts in a penetration test report explains why scope, dates and remediation evidence matter so much when the report is used for compliance.

Retesting closes the loop

Exams end when time runs out. Client engagements usually include a retest: after the client fixes findings, you verify each fix and update its status. Good retesting means confirming the original issue is gone, checking the fix did not just move the problem (a filter that blocks one payload but not a trivial variant), and recording new evidence. A finding marked "resolved" without retest evidence is a common reason auditors push back on a report.

OSCP and other credentials

OSCP is one of several practical credentials firms recognise. OSWE focuses on white-box web application testing and source code review. CPTS and PNPT are practical penetration testing credentials with their own exam formats and report requirements. Each signals hands-on ability in a slightly different area. None of them replaces a sample report or evidence that you have worked inside a scope, and none is a legal requirement to test in Canada. Choose the next credential based on the work you want, not on which acronym is trending.

If you are past the credential and now working out how to find contracts, our guide on how to get contract penetration testing work covers subcontracting, insurance and setting up the practice. For how scoped client work compares with bounty programs, see pentest platforms versus bug bounty platforms.

Where the TrazTech Associate Network fits

We run the TrazTech Associate Network, so weigh this accordingly. The Associate Network brings independent practitioners into TrazTech client work, and offensive security is one of its practices. If you hold a verified credential such as OSCP, OSWE, CPTS or PNPT, you take the fast lane and skip the simulated assessment. Without one, you complete a simulated client engagement of about three hours of work, with 72 hours to submit. Either way, a selection call follows, then portal setup with the agreement signed online. Applying takes about five minutes.

Associates are independent contractors, remote in Canada or the US, part-time or full-time, with no exclusivity. You need at least five hours a week, and if you are employed, your employer must allow side work. Work comes as fixed-scope work orders with a fixed fee per milestone agreed before work starts, and you can decline any offer. Testing runs through the TrazTech VPN using your own tools. Coverage checklists keep the work consistent, larger engagements run as teams with a Lead, and a TrazTech Principal signs off every deliverable before the client sees it. Payment goes out every Friday. Work follows client demand in your practice, so approval does not guarantee a volume of work. See the associate penetration tester role or the careers page for the other practices.

Common questions about going from OSCP to paid pentest work

Is OSCP enough to get paid penetration testing work?

It gets your application read, and some firms treat it as a baseline. Most also want a sample report and some sign that you can work inside a scope. The credential plus a client-style report is a much stronger combination than either alone.

What is the biggest difference between the OSCP exam and a client pentest?

The goal. The exam rewards compromising machines. A client test rewards accurate, complete coverage of a defined scope with minimal disruption, and a report the client can act on and show to others.

Should I get OSWE, CPTS or PNPT after OSCP?

Pick based on the work you want. OSWE suits web application and code review work. CPTS and PNPT are broader practical credentials. A strong sample report often does more for your next contract than a second credential.

Do I need to follow OWASP or PTES on client engagements?

Most firms anchor their method to one or both. The OWASP Web Security Testing Guide and ASVS are standard for web applications, and PTES describes the overall engagement. Clients and auditors expect a named method in the report.

What happens during a pentest retest?

After the client fixes findings, you verify each fix, check that simple variants of the original issue also fail, record new evidence, and update each finding's status in the report.

Put your OSCP to work on scoped client engagements. Verified credentials skip the simulated assessment, and every work order shows the scope and fee before you accept.

Apply to the networkSee the role

Do this work with TrazTech

The TrazTech Associate Network is for independent security and compliance practitioners: scoped client work, no exclusivity, feedback after every job and a published path to the core team.

Apply to the network Open roles How it works