Cybersecurity and CTF Team
A CTF team server: live event channels, a writeups forum, tooling, learning paths per category and a team-only room.
- 8 categories
- 35 channels
- 15 roles
- Medium
Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.
Server structure
Channels
BRIEFING
- team-charter
Only targets you are authorised to attack. No exceptions, no 'just checking'.
- ctf-calendar
Events the team is entering, with dates, format and the platform link.
- event-announcements
Registrations, results and roster calls. Mentions CTF Pings.
- role-select
Web, Pwn, Crypto, Rev, Forensics, OSINT and CTF Pings.
ACTIVE CTF
- ctf-lobby
Coordination during an event: who is on what, who needs a hand.
- challenge-board
One thread per challenge. Claim it in the first message, tag it Solved when the flag lands.
- flags-and-scoreboard
Standings posted by a captain from the platform. Nobody else posts here.
- ctf-infraHidden from @everyone
VPN configs, VM images and credentials for the event. Team only.
WRITEUPS
- writeups
One thread per solved challenge: the event, the category, the approach, the flag path.
- writeup-requests
Ask for a writeup of a challenge you could not solve.
- techniques-index
Curated links to the writeups that teach a technique, by category.
TOOLING
- tool-talk
Scanners, debuggers, decompilers and what replaced what.
- scripts-and-snippets
Solve scripts and helpers. Say what it is for in the first line.
- lab-setup
VMs, containers, network isolation and the toolchain that finally worked.
LEARNING PATHS
- beginner-path
Start here: what to learn first in each category and where.
- web-security-study
Injection, auth flaws, client-side bugs and the labs that teach them.
- binary-exploitation-study
Memory corruption, mitigations and how to read a crash.
- crypto-study
The maths, the mistakes and the classic attacks.
- forensics-study
Disk, memory, network captures and steganography.
- practice-boxes
Practice-lab progress and hints. No full solutions for active boxes.
- security-certs
Which certification, when, and how the exam actually went.
TEAM ONLY
- team-room
The team. Everything that is not for the learners' eyes.
- strategyHidden from @everyone
Which events to enter, who plays which category, what to study next.
- roster-and-availability
Who is playing the next event. Captains promote from here.
- Team Ops
LOUNGE
- hack-chat
Security news, career talk and everything else.
- Hack Lounge
- CTF Room 1
- CTF Room 2
- Study Group
- Debrief
- AFK
STAFF
- captains-roomHidden from @everyone
Captains only. Promotions, disputes and the roster decisions.
- applications-reviewHidden from @everyone
Vetox posts team applications here.
- team-logsHidden from @everyone
Vetox posts moderation, role and join logs here.
Roles
- CaptainAdministrator
- Co-CaptainAdministrator
- ModeratorModerator
- Team Member
- Trainee
- Alumni
- Web
- Pwn
- Crypto
- Rev
- Forensics
- OSINT
- CTF Pings
- Muted
Overview
A server for a capture-the-flag team and the people learning around it. The Briefing category is read-only: #team-charter states the one rule that matters - only targets you are authorised to attack - #ctf-calendar lists the events the team is entering and #role-select hands out the category roles. Active CTF is what makes this layout different: #ctf-lobby is the coordination channel for the event weekend, #challenge-board is a forum where every challenge gets a thread tagged Web, Pwn, Crypto, Rev, Forensics or Misc and marked Solved when the flag lands, #flags-and-scoreboard is captain-only so the standings are never a guess, and #ctf-infra carries the VPN and VM details for the event. Writeups is a forum tagged by category so a solved challenge becomes a document someone can learn from. Learning Paths gives each category a study channel plus #beginner-path, #practice-boxes and #security-certs. Team Only is hidden from guests and holds #team-room, #strategy, #roster-and-availability and a Team Ops voice channel; the Lounge has two CTF rooms, a study group room and a Debrief stage. Staff have a hidden captains' room and #applications-review for people applying to join the team.
When to use it
During a CTF weekend your one channel becomes unreadable: three people are on the same web challenge without knowing it, the flag someone found is buried under a crypto discussion, and after the event the solutions are lost in scrollback. This layout gives each challenge a thread with a Solved tag, keeps the scoreboard captain-only, moves post-event solutions into a writeups forum tagged by category, and separates the team's private planning from the learners who follow along.
What makes it different
- #challenge-board is a forum with one thread per challenge, tagged by category and marked Solved when the flag lands.
- #flags-and-scoreboard is captain-only, so standings during an event are never a guess.
- Writeups is a forum tagged Web, Pwn, Crypto, Rev, Forensics and OSINT, so solutions become study material.
- Learning Paths gives each category its own study channel plus a read-only #beginner-path.
- Team Only is hidden from guests and learners; the roster, strategy and Team Ops voice live there.
Recommended Vetox setup
Applications
Create a team application form whose submissions land in #applications-review, so the captains see a candidate's writeups and availability before they vote.
Self-Roles
Post Self-Roles in #role-select for Web, Pwn, Crypto, Rev, Forensics and OSINT plus CTF Pings, so a challenge thread can mention the specialists.
Reminders
Schedule a Reminder in #ctf-lobby an hour before each event starts and another at the halfway point, with the #ctf-infra link.
Temp Voice
Point Temp Voice at Hack Lounge so a pair working one challenge gets a room of their own during the event instead of talking over the team.
Questions
What can learners see compared with the team?
Everything except Team Only, #ctf-infra and Staff: the briefing, the live event channels, writeups, tooling, learning paths and voice. They can follow an event in #challenge-board and help in threads. The roster, the strategy channel and Team Ops voice are for Team Members, Trainees and Alumni.
How does a Trainee become a Team Member?
By playing. Captains promote from #roster-and-availability after a trainee has been on the roster for a couple of events and posted writeups. Alumni is for members who stepped back but keep access to the team room.
Why is the scoreboard captain-only?
During an event people post standings from memory, and a wrong one changes what the team works on. #flags-and-scoreboard has one source: a captain, posting from the platform. Everyone else reads it.
Common mistakes
- Running an event in one channel, so three people attack the same challenge and the found flag scrolls away under the crypto debate.
- Skipping the charter, which is the line between a security community and a liability.
More in Developers
View allDev Team Internal
FeaturedA private server for one engineering team: async standups, sprint rituals, code review, incidents and deploy feeds.
DevOps and Cloud Engineers
FeaturedDevOps and cloud engineers: provider channels, Kubernetes help, CI/CD, incident war stories and certifications.
Open-Source Project Hub
FeaturedA home for one open-source project: contributor onboarding, issue triage, RFCs, release notes and read-only CI feeds.
Programming Community
FeaturedA public programming server: per-language channels, a tagged help forum, a jobs board and a project showcase.
0.0k
Servers
0+
Commands
0
Users
0
Languages
