CTF7
PricingFree tierFAQ Sign in

CTF7 Code of Conduct

Standards for fair competition, responsible cybersecurity practice and professional conduct across CTF7 events, hackathons, training and platform activity. Every participant agrees to follow them.

CTF7 is built for learning, competition and ethical cybersecurity practice. Every participant is expected to act with integrity, follow event rules and help keep the environment safe and respectful for others. This Code of Conduct applies alongside our Terms of Service and any rules published for a specific event.

The short version

  • Solve challenges yourself or with your registered team. Never share flags or solutions.
  • Only attack what's in scope. Never attack the CTF7 platform, other players or third parties.
  • No denial-of-service, brute-forcing or automation unless a challenge explicitly allows it.
  • Treat everyone with respect. Harassment is not tolerated, anywhere.
  • See something wrong? Report it to the organizers or support@ctf7.com.

1. Scope

This Code applies to everyone who takes part in activity on or connected to CTF7: players, team captains, mentors, judges, organizers, staff, volunteers, sponsors and speakers. It covers CTF competitions, Raw Ops, attack-defense, king of the hill and SOC events, hackathons, War Zone, Bootcamp, workshops, conferences and meetups, plus the community spaces around them such as the CTF7 forum, event chat servers and social media threads about an event.

2. Fair play

Competitions only mean something when the scoreboard reflects real skill. These rules protect the players who earn their points honestly.

No flag or solution sharing

Do not share flags, hints or solutions with anyone outside your registered team, during the event or before it officially ends. Asking other teams for flags counts as sharing. Events that use dynamic flags give every team a unique flag, so a shared flag identifies both the giver and the receiver.

No teaming in solo events

In solo events, informal teaming, answer sharing or outside assistance is treated as cheating and may result in immediate disqualification. In team events, collaborate only within your registered team and respect the team-size limit.

No pre-solved flags or external solutions

Reusing pre-solved flags, previously obtained answers or unauthorized writeups from past events is cheating. Challenges must be solved during the event by the registered participant or team, unless the rules for that challenge say otherwise. Publish your own writeups only after the event ends.

One identity per player

Register once, under your own identity. Multiple accounts, account sharing or playing on behalf of someone else are not allowed.

Automation and brute force

Do not use bots, brute-force tooling or automated scripts against challenges or the flag submission system unless a challenge explicitly permits automation. When automation is allowed, keep it within the published challenge scope and platform limits.

Use of AI and automated assistants

Generative AI and automated assistance tools (such as LLMs, coding assistants and autonomous exploit agents) may only be used if the specific event rules explicitly permit them. When permitted, players must still understand and verify their solutions; submitting AI-generated output without comprehending the exploit or using automated agents against restricted platform services is prohibited.

Time limits and submission rules

Late submissions are not accepted unless stated otherwise. Follow the instructions for submission format, naming and platform use. In Raw Ops events, follow the report format and any reporting deadlines in the event scope.

3. Stay in scope

CTF challenges give you permission to attack specific, deliberately vulnerable targets. That permission ends at the edge of the published scope.

  • Do not attack the infrastructure. The scoreboard, registration system, flag submission API, hosting servers and CTF7's own services are never targets unless an organizer explicitly lists them as in scope.
  • No denial-of-service. DoS and DDoS attacks, deliberate overloading or any attempt to disrupt the platform, challenge instances or other players are forbidden. In attack-defense and king of the hill events, keeping services available is part of the game; knocking them offline through resource exhaustion is not.
  • Leave other players alone. Don't attack other participants' machines, accounts or networks, except where the format explicitly makes them targets, such as rival services in an attack-defense CTF.
  • Report bugs, don't abuse them. Exploiting bugs, loopholes or unintended behavior in the platform for an unfair advantage is prohibited. Report platform vulnerabilities through the bug reporting page and challenge issues to the organizers through the official event channel.
  • Obey the law. Do not attack, probe or interfere with third-party systems, services or infrastructure. All activity must stay within the published event scope, applicable law and the educational purpose of the platform.

4. Hackathon originality

Submit original work unless the event rules expressly allow reused components. Copying substantial code, content or project work without attribution or permission is not acceptable. Open-source tools, libraries and APIs may be used when the rules permit them and they are properly credited.

5. Respectful behavior and harassment

Treat all participants, mentors, organizers, staff and volunteers with respect. Competitive banter is part of CTF culture; making someone feel unwelcome or unsafe is not.

Harassment includes, but is not limited to:

  • Offensive comments related to gender, gender identity, sexual orientation, disability, appearance, race, ethnicity, religion, caste, age, nationality or skill level
  • Hate speech, threats, intimidation or deliberate insults
  • Unwelcome sexual attention, images or comments
  • Stalking, doxxing or publishing someone's private information
  • Sustained disruption of chats, talks, streams or event spaces
  • Offensive team names, usernames or avatars

This applies to written, verbal and digital behavior, in public channels and private messages alike. If someone asks you to stop, stop.

6. Ethics beyond the event

CTF7 promotes ethical hacking and responsible cybersecurity practice. Participants are expected to stay professional across event spaces, community channels and any platform activity connected to the competition. Skills learned on CTF7 should be used lawfully: on systems you own, have written permission to test, or that are explicitly provided for practice.

7. Reporting

If you witness or experience cheating, harassment, technical abuse or any other misconduct, report it through the official event channel or by email to support@ctf7.com. Helpful details include:

  • The event name and, if relevant, the challenge
  • What happened, when, and who was involved (usernames or team names)
  • Screenshots, links or logs, if you have them

Reports are handled as discreetly as possible and reviewed by the organizing team. Retaliation against anyone who reports in good faith is itself a violation of this Code.

Found a security vulnerability in the CTF7 platform itself? Please use the bug reporting page rather than a public channel.

8. Enforcement

Organizers and CTF7 may investigate suspicious activity using signals such as submission logs, flag-reuse alerts and IP and browser data. Depending on severity, violations may result in:

ActionTypical use
WarningMinor or first-time issues, such as off-topic disruption or an accidental rule breach
Score adjustmentRemoving points gained unfairly, for example through a shared flag or an unintended exploit
DisqualificationFlag sharing, teaming in solo events, attacking infrastructure, DoS or harassment
Prize revocationCheating discovered after results are announced
Ban from future eventsSerious or repeated misconduct, on a specific organizer's events or across CTF7

Serious misconduct can lead directly to disqualification or a ban without a prior warning. Organizers' decisions on their own events are final; if you believe a decision was a mistake, you can email support@ctf7.com with the details.

9. Event-specific rules

Organizers may publish additional rules for their event, such as team-size limits, eligibility, allowed tools or scoring details. By registering, you agree to follow both this Code and those rules. Where they conflict, the stricter rule applies.

10. Changes to this Code

We may update this Code of Conduct as the platform and community grow. The effective date at the top of this page shows when it last changed. This version is effective from 1 October 2026.

Thank you for helping keep CTF7 a secure, fair and professional place to compete. Questions? See the FAQ or contact us.

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