Workshop hub
CTFs
Workshop Hub

CTFs

Hub command view

Dashboard

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

Overview
Global leaderboard
Capture the Flag

Command Center

The switches that control the event: registration, participant login, global ranking, the registration code and Groups.

Controls
Infrastructure

Server Status

Live CPU, memory and activity of the hub server and of every CTF container, each in its own panel.

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 Access open Leaderboard Container Status Active players Assigned resources (max)
Capture the Flag

Groups

Split a big event into groups: each CTF and each participant belongs to one group, and a participant only sees the CTFs of their group plus the ones open to ALL.

Groups
All groups
Group CTFs Users Actions
Capture the Flag

Announcements

Tell the participants something right now: a card appears in the middle of the screen, in the hub and in every CTF they have open, for everybody or for one group.

New announcement
Sent
Message Type For Sent Status Actions
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.

All admins
Username Scope Status Actions
Administration

Logs

What the admins did: every change made in the hub and in the CTFs, with the time and the IP it came from. The last 30 days are kept.

Admin activity
Time Admin Where Action Detail Result IP
Participants

Users

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

All users
Username Registered CTFs joined Entries Total points Detail Actions
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.

Realism
Workshop Hub

About

Made with love, coffee, and a suspicious number of “just one last tweak” moments. Built by humans who care about the details, even the tiny ones nobody notices… until they do.

PlatformWorkshop Hub · Multi CTF
Built byNetskope Iberia team
PurposeWorkshop & Training
One container per CTF
One account for every CTF
Global ranking
Monitoring & benchmark
Updates Check GitHub for a newer version of the platform.
Maintenance Inspect the release notes.
☕
Fuel for the team

If this lab helped your workshop run smoother, the Netskope Iberia team accepts thanks in coffee, cold beers, Bitcoin, or a good conversation at the next meetup.

Reference rate: 1 good conversation = 1 coffee. Premium challenge stories may qualify for beer tier. ₿
Hub configuration

Global settings

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

Hub resource limits

Maximum memory and CPUs of the hub's own container. 0 = unlimited. Applied live, without restarting, and re-applied at every start. CTFs have their own limits in CTFs → Edit.

Memory: 0 or at least 256 MB · CPUs: 0 or at least 0.25.
Sample data

Preview the dashboard, the global leaderboard and the awards ceremony with sample data: 10 sample participants (hub accounts, flagged sample), enrolled in the chosen CTF(s) with sample challenges and progress. Running it again regenerates their progress; Remove sample deletes the sample 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.

Points on their own, as a CSV you can open in a spreadsheet: every challenge completed, wrong answer and hint of every participant in every CTF, with the time. Import it to put the points back: it replaces the activity of those CTFs, and you see what will happen before you confirm.

Admin logs

The Logs page keeps the last 30 days of admin activity. Set a maximum size for it: when the log grows past it, the oldest entries are deleted first. 0 = no size limit (only the 30 days apply).

—
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