Cybersecurity Lab Evaluation Checklist: What to Test Before Subscribing

Quick answer

Before paying for a cybersecurity lab subscription, verify seven things: how instruction leads into practice; what workspace and connection options are included; what access or ownership continues after payment ends; how renewal, cancellation, and refund terms apply to the exact plan; whether the learning path information is current; what activity is authorized; and which important questions remain unanswered.

Official documentation shows that platforms can use different learning, workspace, and access models, so one platform’s rules should not be assumed to apply to another.
TryHackMe’s training-content documentation
and
HTB Academy’s introduction
illustrate those structural differences. This is an E1 checklist based on public sources, not direct product use.

Who this checklist is for

Use this checklist if you are a beginner-to-intermediate learner comparing cybersecurity practice-lab subscriptions before committing money and study time. It is most useful when a sales page looks appealing but leaves you unsure about the learning sequence, workspace requirements, access limits, cancellation effects, or fit with your current skills.

The goal is not to produce a universal verdict. The goal is to turn a vague purchase decision into a dated record of what you verified, what remains unknown, and which uncertainty matters enough to delay payment.

1. Apply the same questions to every platform or plan you are considering.
2. For each answer, record the exact product, plan, source, and checked date.
3. Mark each item as verified, not verified, or not applicable before deciding whether to proceed.

The decision areas to verify

Takeaway: A subscription decision is stronger when each row has a dated answer for the exact product and plan you are considering.

The full pre-subscription checklist

1. Confirm the product boundary

Start by identifying exactly what you are evaluating. TryHackMe’s public help pages organize training through rooms, modules, and learning paths. Hack The Box documentation distinguishes HTB Academy’s structured learning environment from the more independent Hack The Box Labs platform.
TryHackMe’s training overview,
its room documentation,
and
HTB Academy’s official introduction
describe these structures.

• Write down the exact product name, plan name, and learning environment.
• Confirm whether you are buying structured instruction, open-ended practice access, permanently unlocked modules, or a combination.
• List what is explicitly included and what remains unclear.
• Do not transfer a conclusion about one product layer to a different product from the same company.

2. Map instruction to practice

Compare the documented path from explanation to independent work. TryHackMe describes walkthrough, challenge, and network room types, while HTB Academy describes paths and modules that combine theory with practical targets and guided or exploratory work.
TryHackMe’s room guide
and
HTB Academy’s introduction
support comparing the learning structure, but they do not establish which structure will teach you more effectively.

• What knowledge is assumed before the first practical task?
• Does the material explain concepts before asking you to apply them?
• Are hints or solutions available, and when do they appear?
• Does the path gradually reduce guidance, or does it move quickly into independent work?
• Can you distinguish a guided exercise from an open-ended challenge?

Treat beginner suitability as a question to investigate, not as a label to accept. Official descriptions can reveal prerequisites and guidance, but they cannot establish your personal fit without stronger evidence.

3. Verify the workspace and connection model

Public documentation describes browser-based workspaces and VPN alternatives, but the available option can depend on the plan and context. TryHackMe documents the AttackBox and a VPN alternative; Hack The Box documents Pwnbox and OpenVPN connection options for Academy.
The AttackBox Explained,
Academy Subscriptions,
and
Connecting to Academy VPN
document those options. This checklist does not establish their usability, accessibility, latency, or performance.

• Is a browser workspace included in the plan you are considering?
• Are there session-time, reset, persistence, or concurrent-use limits?
• Can you use a local machine through a VPN if the browser workspace is unavailable or limited?
• Which operating systems, browsers, hardware resources, and network conditions are supported?
• What setup knowledge is assumed before you can start a lab?

4. Separate access from ownership

Do not treat every form of access as permanent ownership. HTB Academy’s subscription documentation distinguishes access-based plans from Cube-based module access, and its cancellation documentation describes different effects on Cubes, module access, and progress. TryHackMe’s cancellation documentation addresses renewal cancellation, access through the current billing period, and saved progress.
HTB Academy’s subscription guide,
its cancellation guide,
and
TryHackMe’s cancellation guide
show why the exact plan model matters.

• What is accessible only while the subscription is active?
• What, if anything, becomes permanently available after purchase or unlock?
• Can completed modules or rooms still be revisited after the plan ends?
• Is saved progress retained even when content access changes?
• Are Cubes or similar platform units retained after cancellation?

5. Read renewal, cancellation, and refund terms before paying

Check renewal, refund, cancellation timing, billing-period access, progress, ownership, and retained access separately for the exact plan. TryHackMe and HTB Academy publish different documentation for these topics, so a rule found on one platform should not be generalized to another.
TryHackMe’s cancellation documentation,
its refund policy,
HTB Academy’s subscription documentation,
and
its cancellation documentation
are the relevant official starting points.

• Does the plan renew automatically?
• When must cancellation occur to prevent another charge?
• Does access continue through the end of the current billing period?
• Which refund conditions apply, and which situations are excluded?
• What happens to saved progress, unlocked content, platform units, or completed work?
• Are the terms you are reading current for your market and exact plan?

Do not treat a help-page summary as a checkout quote or refund promise. Save the current terms and checked date before payment, and resolve any unclear condition with the provider.

6. Date-check learning paths and included content

Product structures can change. TryHackMe has published a notice describing retired or replaced learning paths, while HTB Academy maintains current documentation for its path and module structure.
TryHackMe’s learning-path change notice
and
HTB Academy’s introduction
support using checked dates. They do not establish a catalog-wide freshness judgment.

• Record the date of the path, module, prerequisite, and plan information you rely on.
• Confirm that the named path still exists and includes the content you expect.
• Check whether retired content has been replaced, renamed, or moved.
• Verify that prerequisite guidance still matches the current learning sequence.
• Recheck volatile information immediately before payment.

7. Use permitted free access carefully

A permitted free entry path can help you inspect navigation, instructional structure, workspace requirements, and the first steps of a learning flow. It cannot prove the value of a paid plan, the quality of the full catalog, or long-term fit.
TryHackMe’s workspace documentation,
its refund policy,
HTB Academy’s subscription documentation,
and
its VPN documentation
identify questions worth checking without supporting a preview-to-paid conclusion.

• Confirm that the preview is permitted and represents the product you are considering.
• Inspect how clearly prerequisites, instructions, and tasks are presented.
• Record which features or content remain locked.
• Do not assume a smooth preview proves full-catalog quality or paid-plan value.

8. Record the areas public documentation does not settle

Keep a separate list for accessibility, keyboard and screen-reader behavior, device compatibility, bandwidth, latency, reliability, support quality, checkout behavior, and personal fit. These areas were not directly evaluated for this checklist, and public marketing or help documentation should not be treated as proof of real-world performance.

• Ask the provider for current accessibility and device-support information when it affects your decision.
• Use a permitted preview to investigate only what the preview can actually show.
• Keep “not verified” visible instead of converting it into a positive or negative rating.
• Delay payment when a material requirement remains unresolved.

Authorization and platform rules

Cybersecurity practice must remain inside provider-authorized targets and environments. TryHackMe’s acceptable-use policy and Hack The Box’s platform rules define conduct boundaries and restrictions that users should read before starting practical work.
TryHackMe’s Acceptable Use Policy
and
Hack The Box Platform Rules
are the approved policy sources for this checklist.

• Use only the targets and environments the provider has made available for the exercise.
• Do not scan, disrupt, or access systems outside the defined scope.
• Check rules on automation, shared solutions, public writeups, and account conduct.
• Stop when the authorized boundary is unclear.

This section is an educational purchasing safeguard, not legal advice and not an operational security guide.

Alternatives before subscribing

Subscribing immediately is not the only valid next step. Depending on what remains unknown, you can:

• read the current official product, workspace, subscription, cancellation, refund, and policy pages;
• use a permitted free preview to inspect setup and instructional structure;
• delay payment until a material device, accessibility, or access question is answered;
• compare another platform using the same checklist rather than changing criteria mid-decision; or
• use non-subscription learning resources while you clarify your preferred learning model.

A delay is a useful outcome when it prevents you from paying before the essential conditions are understood.

Unknowns and limitations

• No account, checkout, room, module, lab, machine, browser workspace, VPN connection, cancellation, refund, or support workflow was directly tested.
• No accessibility, keyboard, screen-reader, mobile, bandwidth, latency, reliability, or device result was established.
• No exact price, discount, tax, total-cost estimate, checkout quote, or refund promise is included.
• No catalog-wide freshness judgment or named-platform learner-fit conclusion is supported.
• No quantitative search-demand, learner-interview, certification, pass-rate, employment, salary, or career outcome evidence is included.
• Vendor comparison pages can reveal marketing and search intent, but they are not neutral evidence for a product verdict.

The checklist should be refreshed when required sources change or after August 3, 2026, whichever happens first.

Make a proceed, delay, or compare decision

Use the completed checklist to choose one of three neutral outcomes:

Proceed

The exact product and plan meet your essential learning, workspace, access, terms, and authorization requirements, and the remaining unknowns are acceptable to you.

Delay

A material requirement is not verified, the current terms are unclear, or the evidence is too old for the decision you are making.

Compare

Apply the same criteria to another platform or plan without changing the questions to favor one option.

Record the decision date and the unresolved items. This makes it easier to revisit the choice when a provider updates a path, workspace, plan, or policy.

Methodology

This E1 checklist was assembled from official public documentation checked on July 20, 2026. The source set covers learning structure, browser workspaces and connection options, subscription and access models, cancellation and refund documentation, a documented learning-path change, and provider rules.

Each material statement was limited to one of seven approved claims. Documentation supported factual structure and plan questions; editorial conclusions were limited to a neutral pre-purchase method. No protected content, account workflow, direct product evaluation, learner research, price amount, commercial relationship, rating, comparative verdict, certification result, or career outcome was added.

A qualitative United States English search-result sample informed the page’s decision boundary, but no search-volume or conversion claim is made. Unknowns were retained rather than assigned a rating or converted into assumptions.

Sources

1. Training content overview, TryHackMe Help Center. Checked July 20, 2026.
2. Rooms, TryHackMe Help Center. Checked July 20, 2026.
3. The AttackBox Explained, TryHackMe Help Center. Checked July 20, 2026.
4. Cancelling Your Subscription, TryHackMe Help Center. Checked July 20, 2026.
5. Refund Policy, TryHackMe Help Center. Checked July 20, 2026.
6. Big Changes on TryHackMe: Retired Three Learning Paths, TryHackMe Help Center. Checked July 20, 2026.
7. Acceptable Use Policy, TryHackMe. Checked July 20, 2026.
8. Terms of Use, TryHackMe. Checked July 20, 2026.
9. Introduction to HTB Academy, Hack The Box Help Center. Checked July 20, 2026.
10. Academy Subscriptions, Hack The Box Help Center. Checked July 20, 2026.
11. Canceling an Academy Subscription, Hack The Box Help Center. Checked July 20, 2026.
12. Connecting to Academy VPN, Hack The Box Help Center. Checked July 20, 2026.
13. Hack The Box Platform Rules, Hack The Box Help Center. Checked July 20, 2026.