Back to all articles

How to start a penetration testing course

Start a penetration testing course with the right basics, safe lab practice and a realistic study plan. Learn what to check before choosing your training.

COEditorial TeamNov 17, 2026 — 8 min read
Learner practicing cybersecurity at a bright desk with purple-lit lab screens and a network sketchbook

A penetration testing course is easier to follow when you can explain a basic network connection, navigate a computer’s command line, and practice in a clearly authorized lab. Start there, then choose training that moves from explained demonstrations to hands-on exercises and written findings. You do not need to master every security tool before enrolling.

For a beginner or career switcher, the aim is not to collect commands. It is to understand what you are testing, why a result matters, and how to explain it. This guide walks through a practical starting sequence and shows what to check before paying for training.

What should a beginner penetration testing course teach?

Penetration testing is an authorized assessment of a system’s security. A tester looks for weaknesses, checks their significance within agreed limits, and reports evidence that helps the owner fix them. Permission and boundaries are part of the work, not a disclaimer added at the end.

A useful beginner course should connect these activities:

  • Define the scope: identify the systems, accounts, techniques and time limits the owner has authorized.
  • Understand the environment: learn what the application or network does before interpreting potential weaknesses.
  • Investigate findings: distinguish an observation from a confirmed security issue, without exceeding the exercise’s instructions.
  • Explain the result: record evidence, describe the potential impact and suggest a relevant fix.

Look for a learning sequence rather than a long tool list. A demonstration that ends with a successful result should also explain the assumptions behind it, the limits of the test and what a defender would change.

For web-focused training, the OWASP Web Security Testing Guide provides a useful reference for understanding the breadth of testing and the importance of clear reporting. You do not need to read the entire guide before your first lesson.

Step 1: Check your foundations before choosing a course

“Beginner” can mean new to penetration testing or new to computing altogether. Those are different starting points. Use a small practical check to see whether you need a foundations module first.

Understand a simple network connection

Be able to describe, in ordinary language, how your browser reaches a website. Know that an IP address identifies a network destination, a port identifies a service endpoint, and DNS helps translate names into addresses. Recognize the difference between a local lab network and the public internet.

You do not need to memorize every protocol. You should be able to explain what a web server does and why a service being reachable does not automatically make it vulnerable.

Get comfortable with the command line

Practice moving between folders, reading a text file, locating a downloaded file and recognizing a permission error. Learn the difference between a file, a running program and a user account.

If those actions are unfamiliar, start with operating-system basics. Otherwise, a security lesson can become an exercise in copying instructions without understanding what changed.

Learn the basics of web applications

Understand the roles of a browser, a server, a request and a response. Know that signing in establishes an identity, while authorization determines what that identity is allowed to access.

A simple readiness exercise is to explain why being logged in should not give someone access to another user’s private information. That distinction will make later web-security lessons easier to follow.

Move on when: you can explain these concepts without reading a definition and complete the basic computer tasks yourself. Gaps are a study list, not a reason to abandon the subject.

Step 2: Choose a course you can actually practice alongside

Before buying, inspect the syllabus and the access details. Video length alone does not tell you how much independent work you will do.

Ask these questions:

  1. Who is the stated audience? Check whether networking or Linux knowledge is assumed.
  2. What will you do yourself? Look for exercises, not just demonstrations to watch.
  3. Where does practice happen? Confirm whether the provider supplies a browser-accessible environment or expects you to set up virtual machines.
  4. What happens when you get stuck? Check for explanations, hints, walkthroughs or an identified support route.
  5. Will you write findings? Reporting practice helps connect a technical observation to its significance.
  6. What does your purchase include? Confirm lab access, access duration and any separate subscription requirements.

CodeRed’s Pentesting Agent – Beginner learning path is one option to examine. Its product page lists 28 hours and 36 minutes of video content, 22 labs, a beginner difficulty label and validation of completion. It introduces Kali Linux pentesting and tools including Metasploit and Burp Suite.

Treat those details as a starting point for checking fit, not a promise that every new learner will finish at the same pace. Read the current access terms and review any prerequisites before enrolling.

Step 3: Establish safe practice boundaries

Use the training provider’s designated lab or an isolated environment you are authorized to test. Do not point a lesson’s tools at an employer’s network, a school system, a public website or someone else’s device just because you can reach it.

Before each exercise, write down:

  • The lab name and the exact target assigned to you.
  • The actions the exercise permits.
  • Any stated restrictions or stop conditions.
  • How to reset the environment when you finish.

If you build your own virtual lab, follow the training provider’s setup guidance and check its network configuration before running exercises. A virtual machine is a software-based computer; creating one does not, by itself, guarantee isolation from other devices.

For an absolute beginner, a supplied practice environment can remove some setup work. A self-managed lab offers more control but also gives you more configuration to understand. Choose the option that lets you learn the intended lesson without losing sight of the boundaries.

Move on when: you can identify the approved target and explain what you must not test. If either is unclear, pause and ask the provider.

Step 4: Use a learn, practice, explain routine

Watching a demonstration and understanding it in the moment is not the same as repeating the reasoning independently. Give each lesson a short learning cycle.

Learn one concept

Choose one objective, such as understanding a web request or identifying a service in a supplied lab. Watch the relevant explanation and note unfamiliar terms. Avoid opening several unrelated courses when one concept becomes difficult.

Practice the matching exercise

Complete the designated lab while keeping notes about your observations. Record what you expected to happen, what actually happened and which explanation helped you make sense of the difference.

If you need a walkthrough, use it deliberately. Read enough to identify the next concept, then return to the exercise. Afterward, repeat the reasoning without keeping the full solution open.

Explain the result

Write a short account in your own words:

  • What was the exercise asking you to establish?
  • What evidence supported your conclusion?
  • What could the result mean in the exercise’s scenario?
  • What change would address the underlying issue?

You have a stronger grasp of the lesson when you can explain why a result appeared, not just reproduce the final screen. Keep notes private if the provider restricts sharing solutions or screenshots.

Step 5: Build a study schedule around complete exercises

Start with a schedule you can sustain alongside work or other commitments. The following is a suggested routine, not a required timetable or a completion forecast:

  • First session: review one concept and its demonstration.
  • Second session: complete the matching authorized lab and record your observations.
  • Third session: revisit a difficult step and write a short finding or explanation.

Use the next available session to finish an incomplete exercise rather than rushing into another topic. Lab setup, troubleshooting and review all count as study time.

The published video duration is only the time spent watching. Your total learning time will also depend on your starting knowledge, the exercises you repeat and how much explanation you need. Do not turn a course’s video hours into a guaranteed date for becoming job-ready.

At the end of each study cycle, identify one thing you can now do independently and one thing you still need help with. That gives the next session a purpose.

Step 6: Add challenges after guided practice

A capture-the-flag challenge, usually called a CTF, is a controlled exercise in which you solve a security problem and submit a designated proof of completion. It can help you test whether you recognize a concept without being told every step.

Choose a challenge related to something you have already practiced. If you have just learned basic web requests, jumping into an unrelated advanced challenge may measure missing prerequisites rather than reinforce the lesson.

When stuck, identify the missing piece before seeking the full answer. Is the obstacle an unfamiliar term, a misunderstood instruction or a technical result you cannot interpret? Review that piece and try again.

Challenge completion is useful feedback, but it is not the whole skill. A professional finding also needs context, evidence, limitations and a clear explanation for the person responsible for fixing it.

What should you have at the end of your first course?

Aim for evidence of learning rather than an inflated claim of expertise. Your first course should leave you better able to work within a defined scope, explain the basic assessment process and document a simple lab result.

Useful private study records include:

  • A lab notebook with the objective, permitted target and outcome of each exercise.
  • A short glossary of terms you can explain in your own words.
  • A sample finding from an authorized training scenario, where sharing is permitted.
  • A list of gaps to address in your next course or practice block.

A validation of completion records completion of the relevant training. It is not automatically the same as an independently assessed professional certification, and neither guarantees employment. If a certification is your goal, check that qualification’s own assessment and experience requirements separately.

Choose your next training step

If the foundation check felt difficult, work on networking, operating systems and web basics before taking on more complex assessments. If those basics are comfortable, review a beginner syllabus and choose one learning sequence to follow with its matching practice.

CodeRed offers courses and learning paths alongside practice labs and CTF challenges. Access depends on the plan: the current subscription page distinguishes Pro’s courses and learning paths from Pro+’s additional labs and challenges. Compare the current CodeRed Pro plans against the way you intend to study before subscribing.

Unsure whether your background fits the training? Ask CodeRed about your learning needs. Include what you already know, the role or skill you want to work toward, and whether you need a supplied lab environment. That makes the conversation more useful than asking which course is best without any context.