CTF7
PricingFree tierFAQ Sign in

CTF & cybersecurity glossary

80 Capture The Flag and cybersecurity terms, defined in plain language. If you are new to competitions or organizing your first event, use this A–Z reference for the jargon, from flag, jeopardy and checker to ROP, CVSS and Raw Ops. For full walkthroughs, head to the CTF learning hub.

This glossary covers the terms you meet when playing or running a CTF, plus the wider cybersecurity vocabulary that challenges draw on. Terms link to a longer guide where one exists, and several terms have their own in-depth explainer pages: dynamic flag, flag format, vulnbox checker and SLA, first blood, dynamic scoring, flag sharing, pwn, reverse engineering, OSINT, steganography, IDOR, SQL injection and XSS. New to all this? Start with What is a CTF? and work through its beginner roadmap.

A

Announcements

Messages organizers post to every participant during an event: schedule changes, fixes to broken challenges, clarifications and reminders. A typical one reads "web-200 was restarted at 14:10; flags submitted before the restart still count." Most events mirror them to a chat channel so nobody misses one.

API (Application Programming Interface)

A documented interface that lets one application or service exchange data or trigger actions in another system. Many web challenges are built around a broken API: change /api/notes/2 to /api/notes/1 and the server returns a note that belongs to someone else, because it never checks who is asking.

Attack/Defense CTF

An advanced format where each team runs an identical set of vulnerable services and must defend its own while attacking opponents' services to steal and submit flags. Each team's copy of the services runs on its own vulnbox, and an automated checker confirms every tick that those services still work. It tests offense, defense and incident response at once. See attack-defense in the formats guide.

Anti-cheat

Measures that detect and discourage cheating during a competition: submission logs, IP and browser signals, flag-sharing detection and alerts. The classic signal is two teams submitting the same flag for a hard challenge within seconds of each other, which dynamic flags turn from a hunch into evidence. Our guide to dynamic flags and anti-cheat explains how the two fit together.

B

Blue team

The defenders in a security exercise, responsible for monitoring, detection, incident response and hardening systems. Blue-team skills are tested in SOC simulations and the defensive half of attack-defense CTFs. See SOC simulation, or compare both sides in red team vs blue team.

Buffer overflow

A memory-corruption bug where a program writes more data into a buffer than it can hold, overrunning adjacent memory. Overwriting a saved return address this way is the classic entry point to binary exploitation.

Boot2Root

A challenge style where you start with no access to a vulnerable machine and must gain an initial foothold, then escalate privileges until you control the root or administrator account. Common in practice machines and in king-of-the-hill events.

Bug bounty

A security program in which researchers report real vulnerabilities to an organization under a defined scope, disclosure process and reward policy. Bug bounty hunting is the real-world cousin of CTF play, and CTF7's Raw Ops format simulates it. See how the two compare in CTF vs bug bounty.

C

Challenge

A self-contained task that tests a specific skill, concept or attack path. Solving it usually yields a flag worth points. Challenges are grouped into categories on the scoreboard. Organizers can start with how to create CTF challenges and our list of CTF challenge ideas.

Challenge categories

Groups that organize challenges by skill area, such as Binary Exploitation (Pwn), Reverse Engineering, Web Exploitation, Cryptography, Forensics, OSINT and Miscellaneous. A typical college jeopardy board has five to seven categories with an easy challenge in each, so a team strong in only one area still scores early. Our CTF categories guide explains each one.

Checker

In an attack-defense CTF, the automated script the game server runs against every team's services each tick. It stores a fresh flag, reads back recent flags and uses normal features the way a real user would, then rates whether the service still works. That rating drives the SLA score, so a patch that breaks functionality costs points even if no one attacked you. Full explainer: what is a checker and SLA?

CTF (Capture The Flag)

A hands-on cybersecurity competition where individuals or teams solve technical challenges and submit flags to earn points. Formats include jeopardy, attack-defense, King of the Hill and report-based Raw Ops. See What is a CTF? and how CTFs sit among other cybersecurity competitions.

CTF platform

The software that runs a Capture The Flag event: registration and teams, challenge delivery and file downloads, flag checking, scoring and the scoreboard, hints, announcements and organizer monitoring. Some are open-source projects you install and maintain on your own server; others are hosted services, and always-on practice CTFs keep challenges online year-round for self-study. Compare options in CTF platforms compared and open-source CTF platforms.

CVE (Common Vulnerabilities and Exposures)

A public catalog that assigns a unique identifier (for example, CVE-2021-44228) to a specific known software vulnerability, so everyone refers to the same flaw by the same name.

CVSS (Common Vulnerability Scoring System)

An open standard for rating the severity of a vulnerability on a 0–10 scale based on how it can be exploited and its impact. CTF7's Raw Ops format scores submitted vulnerability reports using CVSS 4.0. Our CVSS 4.0 guide explains the metrics.

CWE (Common Weakness Enumeration)

A community catalog of software and hardware weakness types (for example, CWE-79 for cross-site scripting). Where a CVE names a specific bug, a CWE names the class of mistake behind it.

Command injection

A web or application vulnerability where attacker-controlled input is passed to a system shell, letting the attacker run operating-system commands on the server. Often a fast route to remote code execution, and a core topic in web exploitation CTFs.

Cryptography

The CTF category focused on breaking or exploiting weak encryption and encoding, from classical ciphers to RSA and AES. Encoding (like base64) is not encryption. Our cryptography CTF guide goes deeper, and the categories overview shows where it fits.

Cyber range

A controlled, simulated environment that replicates real networks and systems for security training and exercises. Attack-defense and SOC simulations effectively run on a cyber range. Learn more in what is a cyber range?

D

Deserialization attack

Exploiting how an application reconstructs objects from serialized data. Crafted malicious input can corrupt program state or achieve code execution. A recurring advanced topic in web exploitation challenges.

DFIR (Digital Forensics and Incident Response)

The discipline of investigating security incidents and recovering and analyzing digital evidence. CTF forensics challenges (disk, memory and network) are miniature DFIR exercises; see the forensics CTF guide.

Dynamic flag

A flag that is unique per team (per player in solo events) rather than shared by everyone. If team B submits the flag issued to team A, the platform rejects it and records where it came from, so sharing is detectable. Read the full explainer: what is a dynamic flag?

Dynamic scoring

A scoring scheme where a challenge's point value decreases as more teams solve it, so harder, less-solved challenges are worth more. Also called decay scoring. Contrast with static scoring; the CTF scoring guide walks through the math. Full explainer: what is dynamic scoring?

E

EDR (Endpoint Detection and Response)

Security software that monitors endpoints (laptops, servers) for malicious activity, records telemetry and enables investigation and response. An EDR alert such as "Word spawned PowerShell with an encoded command" is a common starting point in blue-team and SOC exercises.

Enumeration

The systematic reconnaissance stage of an attack: discovering hosts, ports, services, directories, users and configuration before exploiting anything. "Enumerate harder" is a running piece of CTF advice for a reason.

Exploit

Code or a technique that takes advantage of a vulnerability to make a system behave unexpectedly, such as leaking data or executing commands. Writing a reliable exploit is the goal of most offensive challenges.

F

Foothold

The initial access an attacker gains on a target, the first shell or entry point, before escalating privileges or pivoting deeper. Central to boot2root and king-of-the-hill play.

Format string bug

A vulnerability where user input is used directly as a format string (for example in printf), letting an attacker read from or write to arbitrary memory. A classic pwn primitive; see the binary exploitation CTF guide.

Fuzzing

Automatically feeding a program or endpoint large volumes of varied or malformed input to discover crashes and vulnerabilities. Used in web content discovery (with tools like ffuf) and in binary bug hunting. More in our CTF tools guide.

First blood

The first valid solve of a given challenge in a competition. Many CTFs award a bonus or public callout for first blood, adding a competitive rush to being the first to crack a challenge. See how CTF scoring works for common schemes. Full explainer: what is first blood?

Flag

The proof that a challenge has been solved, usually a formatted string such as CTF7{This_is_an_example_flag}. Submitting a valid flag earns points on the scoreboard. Each event publishes its own pattern; see what is a flag format?

Flag sharing

Giving a solved flag, or the full solution, to a team outside your own during a competition. The most common form of cheating in jeopardy events, since a flag is a short string. Per-team dynamic flags and anti-cheat checks make it detectable. Full explainer: what is flag sharing?

Forensics

The CTF category focused on recovering hidden data and evidence from files, disk images, memory dumps and network captures, including steganography. Our forensics CTF guide covers the main challenge types.

G

Gadget

A short sequence of existing machine instructions ending in a return, reused as a building block in a return-oriented-programming (ROP) chain. Tools like ROPgadget find them inside a binary.

H

Hash

A fixed-length fingerprint produced from data by a one-way function (such as SHA-256). Hashes verify integrity and store passwords; CTF crypto challenges often involve identifying and cracking them with hashcat or John. See the cryptography CTF guide.

Hackathon

A time-boxed build event where participants create prototypes, products or experiments, often in teams, and judges score the result against a published rubric. A security hackathon might ask for a detection rule set or a tool that audits cloud permissions. See how to run a hackathon.

Heap exploitation

Advanced binary exploitation that abuses bugs in dynamic memory management (the heap), such as use-after-free, double-free and allocator metadata corruption, to hijack a program. A hard subset of the pwn category; start with the binary exploitation guide.

Hint

Optional guidance from organizers to help participants make progress on a challenge, often in tiers: a cheap nudge first ("look at the response headers"), a more revealing one later. Hints may cost points, usually charged when unlocked whether or not the team then solves. See hint costs.

I

IDOR (Insecure Direct Object Reference)

A web access-control flaw where changing an identifier in a request (such as a user ID in a URL) lets you read or modify data you shouldn't. A common and beginner-accessible bug, covered in our web exploitation CTF guide. Full explainer: what is IDOR?

IOC (Indicator of Compromise)

An artifact that suggests a system has been breached, such as a malicious IP address, file hash, domain or registry key. Blue-team and SOC challenges often task you with finding IOCs in logs.

J

Jeopardy-style CTF

The most common CTF format: teams choose from a published board of challenges grouped by category and point value and solve them in any order. Beginner-friendly, and the usual first format for a new organizer. See jeopardy CTF and CTF formats.

K

King of the Hill (KotH)

A format where teams compete to gain and then maintain control of a shared machine or service, patching it to lock out rivals while defending against them. Points accrue for time held: a team that holds a hill for 14 one-minute checks at 10 points each earns 140. See King of the Hill in the formats guide.

L

Lab

A guided, hands-on exercise or practice environment designed to teach a skill, workflow or security concept outside a competitive setting. A lab usually comes with instructions and hints, and resets cleanly for the next learner, where a competition challenge comes with neither.

Leaderboard

The official ranking of participants or teams by points, with ties broken by solve time or another published rule. Two teams on 4,120 points are ordered by who reached 4,120 first. Some events freeze the public leaderboard for the final hour to keep the finish suspenseful; see tie-breaks.

M

MITRE ATT&CK

A globally used knowledge base of adversary tactics and techniques observed in real attacks, organized into a matrix. Blue teams use it to map detections and describe threats consistently.

N

Nonce

A "number used once": a value that must not repeat within a cryptographic protocol. Reusing a nonce (for example in AES-GCM or a signature scheme) is a common flaw that crypto challenges exploit.

O

Open source

Software released under a license that lets others inspect, use, modify and often redistribute its source code. Most CTF tools, such as Ghidra, Wireshark and pwntools, are open source.

Organizer

A person, team, school, company or community group responsible for creating an event, publishing challenges and rules, answering support tickets and reviewing suspicious activity. Start with how to host a CTF and our CTF rules template.

OSINT (Open-Source Intelligence)

Gathering information from publicly available sources, such as search engines, social media, archives and metadata. A typical CTF OSINT challenge gives a single photo and asks for the city it was taken in, solvable from a shop sign, a landmark and the angle of the shadows. Also a beginner-friendly CTF category; see our OSINT CTF guide. Full explainer: what is OSINT?

OWASP Top 10

A widely referenced list, published by the Open Worldwide Application Security Project, of the most critical web application security risks. It's a useful map of the bug classes behind many web-category challenges.

P

Participant

A registered user who joins an event to learn, compete or collaborate, either solo or as part of a team. Rules usually tie eligibility to the participant, not the team: one person, one account, one team per event, with student or regional divisions checked at registration.

Payload

The part of an exploit that performs the attacker's intended action once a vulnerability is triggered, such as shellcode that opens a reverse shell. Distinct from the delivery mechanism that gets it there.

Pivoting

Using a compromised machine as a stepping stone to reach other systems that weren't directly accessible. In a network challenge, a foothold on a public web server might be the only route to a database on an internal subnet, reached through an SSH tunnel or a SOCKS proxy. Common in network-based and boot2root challenges.

Privilege escalation

Gaining higher permissions than you were granted, for example going from a normal user to root or administrator by abusing a misconfiguration or vulnerability. A key step in boot2root and king-of-the-hill play.

Purple team

A collaborative approach where red (offense) and blue (defense) teams work together so that attack techniques directly improve detection and response. It blends the two disciplines rather than opposing them.

Pwn (Binary Exploitation)

The CTF category focused on exploiting memory-corruption bugs in compiled programs, such as buffer overflows and heap flaws, to hijack execution. Our binary exploitation CTF guide explains the core ideas. Full explainer: what is pwn?

R

Raw Ops

CTF7's anti-CTF bug-hunting format: there are no flags. Participants investigate a realistic target, submit vulnerability reports, and are scored after triage using CVSS 4.0, with chaining multiple weaknesses encouraged. It simulates real VAPT and pentest work. See Raw Ops.

RCE (Remote Code Execution)

A vulnerability that lets an attacker run arbitrary code on a target system over the network, often the highest-impact bug in web and pwn challenges and in real assessments.

Red team

The offensive side of a security exercise, emulating real attackers to test an organization's defenses and detection. The counterpart to the blue team; see red team vs blue team.

Repository (Repo)

A version-controlled location for code, documentation and change history, commonly hosted on platforms such as GitHub or GitLab. Teams often coordinate CTF scripts and writeups in a shared repo; see how to build a CTF team.

Reverse engineering

The CTF category of analyzing compiled programs without source code to understand their behavior and recover a hidden flag or logic. Our reverse engineering CTF guide covers the workflow. Full explainer: what is reverse engineering?

Reverse shell

A shell where the target machine connects back to the attacker's listener, rather than the attacker connecting in. It's a common goal after achieving code execution, especially when firewalls block inbound connections.

ROP (Return-Oriented Programming)

An exploitation technique that chains together small existing code snippets ("gadgets") ending in a return instruction to perform actions without injecting new code, defeating non-executable-memory defenses. Central to modern binary exploitation.

S

Scoreboard

The ranking view that shows points, solves and placement during or after an event, usually updated as each flag is accepted. Point values depend on the scheme; see how CTF scoring works.

Shellcode

Compact machine code, delivered as a payload, that performs a small task when executed, classically spawning a shell. pwntools can generate shellcode for you with its shellcraft module.

SIEM (Security Information and Event Management)

A system that aggregates and correlates logs and security events from across an environment to support detection, alerting and investigation. Blue teams live in the SIEM during SOC exercises.

SLA (Service Level Agreement)

In attack-defense CTFs, an availability check: the scoring system periodically confirms each team's services still work correctly. Break your own service while patching it and you lose SLA points, even if no one attacked you. The checker runs those checks; see checker and SLA explained.

SOC (Security Operations Center)

The team and facility responsible for continuously monitoring, detecting and responding to security threats. A SOC simulation recreates that work as an exercise: alert triage, log analysis and an incident report.

Solver

A participant or team that successfully submits a valid flag for a challenge. "Solves" is also the count of teams that have cracked a given challenge, which drives dynamic scoring.

Sponsor

An organization that supports an event through funding, prizes, infrastructure, mentorship or promotion. Organizers usually credit sponsors on the event page and in announcements, so agree on placement and deliverables early.

SQL injection (SQLi)

A web vulnerability where attacker-controlled input is interpreted as part of a database query, allowing data theft or manipulation. The textbook example is a login form where the username ' OR '1'='1' -- turns the password check into a condition that is always true. A foundational web exploitation technique. Full explainer: what is SQL injection?

SSRF (Server-Side Request Forgery)

A web flaw that tricks a server into making requests on the attacker's behalf, often to reach internal services or cloud metadata endpoints. A frequent path to deeper compromise in web and cloud challenges.

Static scoring

A scoring scheme where each challenge keeps a fixed point value no matter how many teams solve it. Simpler than dynamic scoring, but a challenge that turns out easier than planned hands out cheap points. Compare them in the CTF scoring guide.

Steganography

Hiding data inside other data, such as concealing a message in an image, audio file or document. A recurring theme in the forensics category, tackled with tools like steghide and zsteg. See the steganography CTF guide. Full explainer: what is steganography?

T

Team

A group of participants competing under a shared name and score. Most jeopardy CTFs cap teams at three to five players, and attack-defense finals often allow more. Building one? See how to build a CTF team or try the CTF team name generator.

Tick

A fixed time interval (a round) in an attack-defense CTF. Each tick, flags are rotated into services, the checker runs SLA checks and scores are tallied, so the game advances in discrete steps. See checker and SLA explained.

V

VAPT (Vulnerability Assessment and Penetration Testing)

A combined approach to finding vulnerabilities (assessment) and safely exploiting them to prove impact (penetration testing). CTF7's Raw Ops format simulates VAPT engagements, and findings are written up much like our vulnerability report template.

Vulnbox

In an attack-defense CTF, the identical vulnerable machine each team is given to both defend and study. Teams patch their own vulnbox while exploiting the same bugs on everyone else's, and the checker keeps testing it to award SLA. Full explainer: what is a vulnbox?

W

Write-up

A post-event explanation documenting the solving process, tools, reasoning and lessons learned for a challenge. Reading and writing writeups is one of the fastest ways to improve. Learn how to write a CTF writeup.

X

XSS (Cross-Site Scripting)

A web vulnerability where an attacker injects malicious scripts that run in other users' browsers, used to steal sessions or perform actions as the victim. A core web exploitation technique, cataloged as CWE-79 in the CWE list. Full explainer: what is XSS?

To put these terms into practice, start with the beginner guide, practice on Ouroboros CTF, browse CTF7 events, or host your own CTF.

Plan your next event with us

A free jeopardy event for up to 50 players goes live when you publish it. For flagship events, our team can build the challenges and run the managed formats: attack-defense, King of the Hill and SOC simulations.

CTF7 mascot holding a CTF7 flag