Skip to main content
An authorised penetration-testing workbench with a laptop, test router, scope checklist and findings
Offensive security

Offensive Security (Pentest / Red Team)

An assessment role where permission, reproducibility and useful reporting matter alongside finding vulnerabilities.

Explore the work, check your starting point and try one scoped task before committing to a course or exam.

Try this pathway in practice

The route

Where this route starts: Junior Pentester or AppSec Engineer

  1. Starting roleJunior Pentester or AppSec EngineerRead the broader role guide

A general route, not a personal plan. Linked guides describe the broader role family; a junior or support starting point may have a narrower remit. Compare the responsibilities with the actual vacancy.

Phased progression

Build on your existing experience, demonstrate the next responsibility and review it with the people who rely on your work.

Progress through demonstrated capability and agreed responsibility. These stages are not a fixed timetable or a salary ladder.

  1. Build on existing experience

    Your starting capability

    Practical focus

    Review your existing work against Junior Pentester or AppSec Engineer responsibilities. Identify one gap in judgement, delivery or ownership and agree a scoped way to demonstrate it.

    Something to demonstrate

    A short account of what you can already do and the next gap to investigate.

    In focus CRTO · Burp Suite Certified Practitioner

  2. Demonstrate readiness

    Move into the specialism

    Practical focus

    Explore Junior Pentester or AppSec Engineer responsibilities. Check the supervision and prior experience expected; demonstrate the relevant work before increasing your scope.

    Something to demonstrate

    A concise finding with scope, reproduction steps, impact, remediation and retest result.

    In focus Junior Pentester or AppSec Engineer

  3. Demonstrate reliable practice

    Specialisation

    Practical focus

    Take on a scoped responsibility, test your decisions and collect feedback. Add a credential only where it supports that work.

    Something to demonstrate

    A test record and feedback showing how you improved a piece of work.

    In focus eJPT · PNPT

  4. Broaden responsibility

    Deepen, lead or move sideways

    Practical focus

    Red Team Lead or Adversary Simulation. The operational shift from operator to designer.

    Something to demonstrate

    Examples of broader ownership, with the scope and responsibility agreed.

    In focus OSEP

The work itself

What you would spend time doing

Test an agreed scope, reproduce weaknesses and explain their impact and remediation. Client communication, evidence handling and retesting are part of the engagement.

Your starting point

What to bring to this route

Understand web or network fundamentals before specialising. Practise only in explicitly authorised labs; exam success does not establish readiness to run a client engagement alone.

Ask a course provider or employerWho approves scope changes and reviews findings before they reach the client?

The verdict

You've already got writeups, CTF solves or HTB ranks that prove the hands work. You'll happily write a 40-page report for every fortnight of testing.

Engagement scope and reporting deadlines can constrain the investigation. Clarify travel, retest expectations and how findings are reviewed before delivery to clients.

Certification sequence

Study options, not a checklist. Choose for the work you need to demonstrate, then check the provider’s current requirements and renewal terms.

Practical projects

Produce something you can explain, test and improve with feedback.

A scoped starting exercise

Try the work before choosing the route

Choose one deliberately vulnerable training application you are authorised to test. Define the scope, reproduce one finding and retest an available fix within the lab.

What to keepA concise finding with scope, reproduction steps, impact, remediation and retest result.

Free text worksheet · no account needed. Add your checks, results and feedback as you work.

Review the evidence

  1. Could a defender reproduce and fix the issue using your report?
  2. Have you stated the permission boundary and avoided claiming impact you did not demonstrate?

Label planned, simulated and completed work accurately. A practice exercise helps you test your interest and reasoning; it does not establish production experience or guarantee an interview.

Larger portfolio ideas for later

Choose one once you have the foundations and permissions it needs. Scope it to a task you can test and explain.

  • TryHackMe + HackTheBox streaks with public write-ups
  • Internal CTF write-ups on a personal blog
  • Custom Burp extension or a small C2 plugin

Use synthetic or approved information. Keep employer, customer and account details out of public examples.

Red TeamerAppSec EngineerAdversary Simulation
  • ·SOC-first then pivot offensive
  • ·AppSec via developer background

Realistic expectations

Check these assumptions against the course, vacancy or team you are considering.

Misconception

That a title or credential establishes readiness by itself. Compare the advertised supervision with your evidence of authorised testing, reproducible findings and clear reporting.

Readiness check

Compare the advertised supervision with your evidence of authorised testing, reproducible findings and clear reporting. Direct junior entry and transitions from other roles are both possible; no duration guarantees either.

Editorial route and career guidance. No separate external evidence review is recorded for this assessment.

Editorial evidence review: pending · UK market. Vendor facts and prices elsewhere on this page have their own sources and check dates.