Workshop hub
CTFs
Workshop Hub

CTFs

Hub command view

Dashboard

Monitor every CTF, its participants and the global ranking from one overview.

Hub readiness
Global leaderboard
Infrastructure

Server Status

Live CPU and memory of the hub server. Each CTF's resources are shown in the CTFs table.

Capture the Flag

CTFs

Create, start and manage each CTF container. Every CTF keeps its own challenges, timer, leaderboard and gateway settings.

All CTFs
CTF CTF Status Visible Registration Leaderboard Container Status CPU / Memory / Uptime
All CTFs together

Global ranking

Each participant's points are summed across every visible CTF. Data refreshes every few seconds.

Ranking
Administration

Admin access management

An admin can be global (the whole hub and every CTF) or administer one or several specific CTFs.

Add admin Use an existing username, or a new one: the account is created with a random password shown once.
All admins
Username Scope Status Actions
Participants

Users

Registered participants. Admins are managed in Admins. A user can join any CTF with that CTF's registration code.

All users
Username CTFs joined Total points Detail Password Disable Delete
Performance

Benchmark

Simulate a full event (several CTFs, many participants, chat) and check that the platform holds before the real one.

Load test

Simulates a real event: creates throw-away CTFs (named [LoadTest], visible in the selector while it runs) and test users, runs virtual participants against them (login, join, SSO, timer polling, challenges, leaderboard, flags; chat for CTF AI GW through a mock gateway, never the real Netskope/AI providers) and reports latency, errors, container CPU/memory against the server capacity you declare, and hub↔CTF consistency. Everything it created is removed at the end. It runs from the hub container, so it also uses hub CPU: for the cleanest numbers, run it from a quiet server.

Hub configuration

Global settings

Maintenance actions that apply to the CTFs registered in the hub: to one of them or to all.

Registration codes

Each CTF has its own registration code (see Edit CTF). On top of those, you can set one hub-wide code that is accepted by every CTF whose registration is open. A CTF can also have open access (no code at all) from its Edit dialog, and you can enrol users directly from Users → Add to CTFs.

4-64 characters. Participants can type it instead of a CTF's own code.
Demo data

Preview the dashboard, the global leaderboard and the awards ceremony with sample data: 10 demo participants (hub accounts, flagged demo), enrolled in the chosen CTF(s) with sample challenges and progress. Running it again regenerates their progress; Remove demo deletes the demo accounts, their progress and the [Demo] challenges from every CTF.

Backup & restore

Export everything to one file: hub accounts, the CTF list (with their secrets), memberships, admins and settings, plus each CTF's database (challenges, participants, progress, settings). Import it on this hub or on a fresh one to restore the hub and its CTFs. The file contains password hashes and secrets: keep it safe.

Danger zone

Destructive maintenance

Use these actions only when preparing the lab for a new run or cleaning a completed workshop. Choose whether they apply to one CTF or to all of them.

One CTF, all CTFs, the hub's accounts, or everything.
Clear Database

Deletes participants, challenges and all progress of the selected CTF(s) and/or the hub's participant accounts. Settings and admins are kept.

This will permanently delete:
  • All participants of the CTF (they must rejoin with its code)
  • All challenges, completions and point penalties
  • With Hub/Everything: the hub's participant accounts and memberships
CTFs go back to Stop. Admins, settings and the CTF list are kept.
Factory Reset

Clears the data and also puts the selected CTF(s) back to their default configuration for the next group.

On top of Clear, it resets:
  • Timer, retries and leaderboard visibility
  • Registration: closed, with a new code
  • Portal appearance back to automatic
The display name and admins are kept (managed by the hub).
—
Challenge progress
Activity timeline