A jeopardy-style CTF presents a board of separate challenges rather than one continuous task. You choose a challenge, read its instructions and rules, work on the supplied material or permitted target, and submit a flag to the event's checker.
A category groups related challenges, such as Files or Web. Points are units used for scoring. The scoreboard displays results. The event platform provides features such as accounts and scoring; those supporting systems are not automatically targets you may test.
Before you begin
- Recommended first
- Offensive work, defensive work, and CTFs
- Estimated time
- 10 min reading, 10 min activity. Setup and optional practice may take longer.
- Where you work
- Work on this lesson page in a desktop or mobile browser, with paper or a text editor for notes. You need no installation, account or terminal. The cases describe invented situations; your task is to read and reason about them.
- Without a lab
- Every worksheet appears in full on the page. A download saves a copy to your device; it is optional. If you cannot download, copy the fields into your notes. Without JavaScript, predict the decisions and explain your reasons on paper. Answer checking needs JavaScript; keeping the result after you leave also needs browser storage.
After this lesson you can:
- Identify a card's task, category, rules and flag-submission destination.
- Distinguish a permitted challenge target from the event's login and scoreboard.
- Choose an entry puzzle using its prerequisites.
01Example
This invented board has two choices. Read the task and prerequisite before comparing points. Neither card provides a live service or a hidden flag for you to find here.
FICTIONAL BOARD
Files / Read the notice / 50 points
Task: read the supplied notice and follow its instruction
Material: notice.txt, supplied by the event
Prerequisite: reading the card and event rules
Submit: the event's challenge-answer box
Web / Inspect the toy page / 100 points
Task: investigate the event's toy page
Prerequisite: the later web lessons
Allowed target: only the event-provided toy-page lab
Excluded: event login and scoreboard
Event rule: use only material and targets named on the chosen card.02Read before trying
Start with the task and allowed material. A challenge may supply a file or name a practice service. A target is the specific thing you may examine. A lab is a practice environment prepared for an exercise. Permission for that lab does not extend to other systems operated by the same organization.
In the example, the reading card is a suitable first choice for a learner who has only completed Start. The web card needs knowledge from later lessons. Its larger point value does not remove that prerequisite, and points alone do not establish difficulty.
Read the event-wide rules as well as the chosen card. If they conflict or leave a boundary unclear, pause and ask through the organizer's stated contact. Do not settle uncertainty by choosing the widest possible permission.
Choose from prerequisites and scope before points; the event login and scoreboard remain outside the toy-page target.Model. A teaching model drawn by hand. It shows the idea, not real tool output.
Read the full explanation below.
Only the supplied notice.txt; submit to the event answer box.
Files · 50 points
The notice card needs reading and event rules already available in Start.
The answer box is a submission destination, not a testing target.
The notice card needs reading and event rules already available in Start.
Follow the explanation
- The notice card needs reading and event rules already available in Start.
- The toy-page card requires later web lessons; 100 points does not remove that requirement.
Read every state and value
1. The notice card needs reading and event rules already available in Start.
- Task
- Read the notice
- Choice
- begin
- Relevant skills
- Read the card and event rules
2. The toy-page card requires later web lessons; 100 points does not remove that requirement.
- Task
- Inspect the toy page
- Choice
- later
- Relevant skills
- Later web lessons
03Flags and checking
Submit a discovered flag to the event's own answer box under its rules. The place where you submit a flag and the system you may examine can be different. A scoreboard showing your result is not therefore a testing target.
Events choose their own answer formats and checking behavior. A flag may need exact capitalization and punctuation. This course's treatment of capitals is not a rule for other platforms. CTFd, software used to run events, documents challenge submissions and awarded points, but an organizer can configure an event differently.
04Inspect a fresh card
Use this new card to practice separating the target, exclusions and submission destination. notice-lab is an invented system name. A later question uses another name, challenge-vm. VM stands for virtual machine, a computer environment created in software; Computers explains it. You need no practice computer for this reading exercise.
FICTIONAL CARD: First toy service
Category: Web
Task: investigate the supplied service after learning web basics
Allowed target: notice-lab
Allowed action: the toy-service exercise listed by the card
Excluded: results-page, event login, other teams' machines
Submit: the event's challenge-answer box
Stop: unclear permission, activity leaving the named lab, or private data
The names are labels. No address or flag is supplied here.- In your notes, copy the allowed target and action. On another line, list the excluded systems so they cannot be mistaken for additional targets.
- Record where a flag would be submitted. Explain why a submission destination can accept an answer without becoming a system you may test.
- Return to the two-card worked example. Choose a first card for someone who has completed only Start, and name the prerequisite that makes the other card wait.
- Review your note: it should distinguish the permitted challenge, the systems excluded from testing and the answer-submission destination. Finish with the reading decision; no connection or puzzle solve is required.
05When to use help
If you become stuck in a later event, record the task, action and result as you practiced earlier. Follow that event's hint and solution-sharing rules. Ask about your method without posting a flag publicly.
The Practice directory lists resources you can use later. Before beginning a challenge there, check its current rules, prerequisites and allowed target. A link in a directory does not enlarge the provider's permission. The next lesson gives you a method for reading that permission carefully.
06Optional challenge
Allow about 5 extra minutes. Write three preparation lines for the example Web card: the knowledge still needed, the allowed target and one excluded system. Explain why its point value does not change any of those facts.
07Fresh cases for the checks
Use these fictional cases for the checks below. They have different inputs from the worked examples. Read them here or make notes; no installation or external service is needed.
Event case A: fictional board and rulesOwned fixture. An original file made for this course. Follow the activity's instructions in your own lab.
CARD amber: category files; 80 points; open; read a supplied text file.
CARD birch: category pwn; 60 points; open; requires memory skills not yet learned.
CARD coral: category web; 50 points; closed.
Learner knows how to read supplied text, but has no memory-training prerequisite.
Submission destination: event flag box.
Permission: supplied challenge files only. Excluded: scoreboard service and other learners.
Required flag format: YS{...}; preserve case and braces. No flags are supplied here.
08Read the event card
Optional written self-check: Write category, state, task, prerequisite and submission destination for your selected card. Explain your scope decision using the permission and exclusion lines, rather than point value. Keep the candidate flag private and follow actual event rules.
09Common mistakes
If a login or scoreboard shares the challenge website, still check the rules. A shared website does not extend testing permission.
If another platform rejects a flag, inspect its required capitalization and punctuation. Do not assume its checker works like this course's checker.
If you are searching for a hidden flag in this page, return to the task. These are complete reading cases with no hidden service to investigate.
If a target or action is unclear, record the uncertainty and draft a clarification for the organizer's stated channel. Leave the technical exercise pending.
References
- CTFd: Challenges overview
Primary documentation on submitting flags to challenges and receiving points. It describes CTFd's role, not this invented board's rules.
- CTFd: Flags
Explains flags as proof of a challenge outcome. Check each actual event's format and rules separately.