> For the complete documentation index, see [llms.txt](https://docs.kc7cyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kc7cyber.com/camp/kc7-attribution-challenge.md).

# KC7 Attribution Challenge

### Summary

The KC7 Attribution Challenge is a fast-paced, team-based cyber investigation game designed for middle and high school students. In this version of the game, students are dropped into the middle of a ransomware crisis and must work together to investigate the incident, uncover who is responsible, and earn points by submitting accurate, well-supported answers.

This game focuses on **teamwork, analysis, and investigation**. Points are earned through correct actions—like solving technical puzzles, submitting strong attribution cases, or asking sharp investigative questions. The experience is still immersive and role-based, but much easier to manage for facilitators and more intuitive for students.

### 🧠 Game Objective

Each team plays the role of a cyber incident response unit in a fictional organization that has just suffered a ransomware attack. Their mission is to:

1. Investigate how the ransomware attack occurred (technical forensics).
2. Gather clues and analyze evidence (both in-game and from physical documents).
3. Identify the hacker or hacking group responsible (attribution).
4. Submit findings to the **Investigative Committee**, and earn points based on the quality and accuracy of their submissions.

The team that earns the **most points by the end of the game** wins.

This game format can be applied to multiple scenarios! 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kc7cyber.com/camp/kc7-attribution-challenge.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.