Skip to content

CTF-101: Challenge CRUD

Statement

The system shall support creating, reading, updating, and deleting CTF challenges. Each challenge shall have: a title, description (supporting Markdown), point value, one or more flags, category assignment, and a visibility state. Challenges shall be scoped to a single CTF event.

Rationale

CRUD operations on challenges are the foundational data management capability that CTF adds to the Shifter platform. Every other challenge feature (categories, flags, hints, scoring) depends on challenges existing as first-class entities. These fields represent the minimum data model needed for organizers to create effective challenge sets within Shifter.

Traceability

  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/models/ (CTF models - CTFChallenge model with CRUD fields, category, points, visibility, event scoping)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/services/challenge/ (Challenge service - CRUD operations, flag normalization, and flag verification logic)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/forms/ (CTF forms - Django forms for challenge create/update input validation)
  • IMPLEMENTS → CODE_FILE shifter/shifter_platform/ctf/enums.py (CTF enums - ChallengeCategory, ChallengeDifficulty, and other enum definitions)
  • TESTS → TEST shifter/shifter_platform/tests/ctf/test_models.py (CTF model tests - Tests for CTFChallenge model validation and properties)