HTB CAPE exam-day guide
HTB CAPE · Prepare for the day ahead.
Your checklist
Review the official exam guide and scope one final time
Open the current HTB Academy CAPE exam page and note the exact duration, number of targets, flag format, and submission mechanism. Confirm any details that may have changed since you enrolled with the provider rather than relying on memory or third-party writeups.
Confirm your identity document requirements with the provider
Check which ID the provider accepts for your region and whether a webcam or proctoring check is required. If the exam is unsupervised and self-paced, confirm that too. Do not assume a specific ID policy; verify it in your account or with support before exam day.
Test your hardware and network
Verify your machine can run your hypervisor or VPN client, that your browser supports the exam platform, and that your connection is stable. Have a backup connection (mobile hotspot) ready. Reboot before starting to clear stale VPN routes.
Prepare your tooling and notes offline
Have your preferred notes, payload snippets, and command cheatsheets saved locally so a network hiccup does not block you. Confirm your attack VM is updated and your VPN profile works against a practice target beforehand.
Set up a findings log template
Create a document with sections per target: foothold, credentials found, privilege escalation path, and flags. Timestamp entries as you go. This doubles as your report source and stops you losing track mid-exam.
Plan a time budget and write it down
Split the exam duration into reconnaissance, exploitation, and reporting blocks, leaving a buffer at the end. Decide in advance how long you will stay stuck on one target before pivoting.
Arrange a quiet, uninterrupted workspace
Book a room, silence notifications, and tell housemates or colleagues you are unavailable. If the exam is timed and proctored, confirm the environment rules with the provider first.
Prepare flag submission and screenshot habits
Know exactly where flags are submitted and whether screenshots or command output are required as evidence. Capture proof as soon as you get a flag rather than reconstructing it later.
Rest, hydrate, and eat before starting
A long practical exam rewards stamina. Sleep the night before, keep water and food within reach, and avoid starting fatigued.
Have provider support contact ready
Save the support email or ticket link in case of platform outage, VPN failure, or a timer issue. Confirm the escalation process with the provider in advance.
Plan the day
Re-read the official exam scope and rules. Do a final light lab session on your weakest area (for example Active Directory enumeration or a specific exploitation chain) rather than learning something new. Verify your VPN profile and tooling against a practice machine, and confirm exam start time and time zone in your account.
Stop heavy studying. Update your notes and cheatsheets, back them up locally, and write your time budget. Check hardware, charger, headset, and backup internet. Confirm ID and proctoring requirements with the provider if unsure. Get a full night of sleep.
Eat properly, reboot your machine, start your attack VM, and test the VPN and exam platform login early. Close unnecessary applications. Have your findings log open and your time budget visible. Start on time and do a quick reconnaissance pass before committing to any single target.
Work methodically: enumerate fully, log every credential and flag immediately, and keep screenshots as evidence. Watch the clock against your budget and pivot when a target stalls. Reserve the final portion of the exam for verifying flags and completing any required report or submission. If the platform fails, note the time and contact support immediately.
Rules to check
Follow the provider's published rules on permitted tools, automation, and outside help. If anything is ambiguous, ask the provider before the exam rather than guessing.
Do not share, publish, or discuss exam content, flags, or target details. Treat the exam environment as confidential.
Use only the systems and targets provided. Do not attack infrastructure outside the exam scope.
Have valid identification ready if the provider requires it, and confirm the accepted ID type in advance.
Confirm break policy with the provider: whether the timer pauses, whether breaks are allowed, and whether you must remain at your desk.
Submit flags exactly in the required format and location; malformed or misplaced submissions may not count.
Keep your own evidence (screenshots, command output, notes) in case the provider requests verification of your work.
Understand the scoring and pass criteria from the official guide, and do not rely on secondhand claims about thresholds.