---
title: Attack/defence events
description: Run an attack/defence event on Athena, where every team defends its own box and attacks everyone else's.
---

In an attack/defence event every team gets an identical **box** running the same deliberately vulnerable services. Each **tick**, a checker you supply stores a fresh flag in every team's services and reads earlier flags back. Teams patch their own box, exploit everyone else's, and submit the flags they steal.

Attack/defence is its own event format. The jeopardy guides elsewhere in this guide cover challenges, categories, container instances and dynamic scoring, and none of those exist in an attack/defence event. Account, workspace, billing, sign-in and announcement guides still apply as written. Certificate templates, tiers and issuing work as [Issue certificates](/organizers/how-to/issue-certificates) describes, except where players find them: a player's certificates appear on the event site's **Certificates** page as soon as you issue them, with no wait for the freeze, and the certificate email links there. Reports and feedback work the same way, with two differences: players report against a service or a part of the platform rather than a challenge, and the schedule's freeze time is labelled **Feedback opens**, because it opens player feedback without stopping the game or the scoreboard.

Attack/defence events are available on the **Pro** and **Enterprise** plans.

**[Tutorial](/organizers/attack-defence/tutorials/run-your-first-attack-defence-event)**

Take one event from creation to an open game network.

**[How-to guides](/organizers/attack-defence/how-to)**

Register services, bring an existing checker, lock the roster, run the game and recover boxes.

**[Reference](/organizers/attack-defence/reference)**

Event settings, the checker contract, scoring and the `athena ad` commands.

**[Concepts](/organizers/attack-defence/explanation)**

How an event moves from setup to end, and what happens when something fails.
