> ## Documentation Index
> Fetch the complete documentation index at: https://stem-docs.intellectualpoint.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Welcome and team setup

> Meet your team, assign roles, and prepare for the Cyber Defense Challenge.

## Welcome to Day 1

Today kicks off the **Introduction to Cybersecurity** STEM workshop. Over the next five days, you will build a company, defend it against cyberattacks, and learn the foundations of how security professionals protect organizations every day.

<Info>
  **Camp dates**: June 23-27, 2026 | **Time**: 9:00 AM - 1:00 PM ET each day
</Info>

By the end of today you will:

* Form your Cyber Defense Challenge team and assign roles
* Understand the four categories and six types of security controls
* Learn the CIA Triad - the foundation of all information security
* Explore authentication factors and access control models

## The Cyber Defense Challenge

Your mission for the week:

> **Your team just started a new company. Every business faces cyber threats. Build your company, protect it, and respond when attacks happen.**

This is a multi-day competition that runs alongside your lessons. Each day you learn new concepts and apply them to your company's defenses. By Day 4, your defenses will be put to the test with live attack scenarios.

<Steps>
  <Step title="Day 1: Build your team and learn the basics">
    Form your team, assign roles, learn security controls, the CIA Triad, and authentication. These are the building blocks for everything that follows.
  </Step>

  <Step title="Day 2: Understand your enemies">
    Study threat actors, the cyber kill chain, and common attacks like phishing, SQL injection, and malware. Know your enemy before you build your defenses.
  </Step>

  <Step title="Day 3: Build your defenses">
    Purchase security controls for your Donuts & Dragons donut shop on a limited budget. Every dollar counts - choose wisely.
  </Step>

  <Step title="Day 4: Survive the attacks">
    Face live attack scenarios. Your defenses are tested, your team responds to incidents, and you see what held up and what didn't.
  </Step>

  <Step title="Day 5: Final project">
    Unbox your USB Rubber Ducky hardware, write DuckyScript payloads, and see offensive security in action.
  </Step>
</Steps>

## Breaking into teams

Your instructor will divide the class into teams of 3-5 students. Each team will:

* Choose a **team name** and create a **company name** for the wargame
* Assign **roles** to each member (detailed below)
* Work together all week to build, defend, and respond

<Tip>
  Pick a team name that you are proud of - you will be announcing it to the whole class. Your company name is the fictional business you are defending in the Donuts & Dragons wargame.
</Tip>

## Team roles

Every team member plays a specific part. Some roles overlap, and that's by design - cybersecurity is a team sport.

<AccordionGroup>
  <Accordion title="Team Captain" icon="crown">
    The Team Captain is the leader. You run team discussions, make final decisions when the group can't agree, and brief the main room during presentations.

    **Responsibilities:**

    * Lead team discussions and keep everyone focused
    * Make the final call when the team is split on a decision
    * Present your team's strategy to the class
    * Coordinate between team members during attack scenarios

    **Key questions you should always be asking:**

    | Question             | Why it matters                                            |
    | -------------------- | --------------------------------------------------------- |
    | What happened?       | You need to understand the situation before deciding      |
    | What's the plan?     | Your team needs direction, not chaos                      |
    | What's our priority? | You can't fix everything at once - pick what matters most |

    <Note>
      Being the captain doesn't mean you make every decision alone. The best captains listen to their team and make informed calls.
    </Note>
  </Accordion>

  <Accordion title="Budget Specialist" icon="wallet">
    The Budget Specialist controls the money. In the Donuts & Dragons wargame, your team has a limited budget to purchase security controls. You decide what to buy, track spending, and calculate the cost of attacks.

    **Responsibilities:**

    * Track the team's total budget and remaining funds
    * Purchase security controls from the pricing guide
    * Calculate financial losses when attacks hit
    * Recommend where to spend (and where to save)

    **Key questions you should always be asking:**

    | Question                              | Why it matters                                              |
    | ------------------------------------- | ----------------------------------------------------------- |
    | Can we afford more security?          | You need to know your limits before committing              |
    | What's our remaining budget?          | Overspending leaves you exposed later                       |
    | What's the cost of *not* buying this? | Sometimes the cheapest option is the most expensive mistake |

    <Warning>
      Budget mistakes are permanent in the wargame. Once you spend money, you don't get it back. Plan carefully before purchasing.
    </Warning>
  </Accordion>

  <Accordion title="Report Specialist" icon="clipboard">
    The Report Specialist is the team's historian. You document every decision, every incident, and every lesson learned. When the team is asked "what happened?" - you have the answer.

    **Responsibilities:**

    * Record all team decisions and the reasoning behind them
    * Document incidents as they happen (what, when, how)
    * Create incident reports after attack scenarios
    * Track lessons learned for future rounds

    **Key questions you should always be asking:**

    | Question                 | Why it matters                              |
    | ------------------------ | ------------------------------------------- |
    | What happened?           | You need an accurate record, not a guess    |
    | What did we do about it? | Your response matters as much as the attack |
    | What should we improve?  | Every incident is a learning opportunity    |

    <Tip>
      Keep your notes organized from the start. During attack scenarios, things move fast. If you don't write it down immediately, you will forget details.
    </Tip>
  </Accordion>

  <Accordion title="Incident Responders (everyone)" icon="shield-alert">
    Every team member is an incident responder. When an attack hits, the whole team works together to analyze, contain, recover, and improve.

    **Responsibilities:**

    * Analyze attacks to understand what happened and how
    * Contain incidents to stop them from spreading
    * Recover systems and restore normal operations
    * Improve defenses so the same attack can't work twice

    **Key questions every responder should ask:**

    | Question                          | Why it matters                           |
    | --------------------------------- | ---------------------------------------- |
    | How do we stop this?              | Containment is your first priority       |
    | How do we recover?                | Getting back to normal is the goal       |
    | How do we prevent this next time? | The best teams learn from every incident |

    <Info>
      In real cybersecurity, incident response is everyone's job - from the CEO to the newest intern. The same applies here.
    </Info>
  </Accordion>
</AccordionGroup>

## Red vs Blue

Throughout this camp, you will hear the terms **Red Team**, **Blue Team**, and **Gray Team**. Here's what they mean:

<CardGroup cols={3}>
  <Card title="Blue Team - Defenders" icon="shield" color="#2563EB">
    That's you. The Blue Team defends the organization. You build defenses, monitor for threats, respond to incidents, and recover from attacks. Your goal is to protect your company's assets.
  </Card>

  <Card title="Red Team - Attackers" icon="swords" color="#DC2626">
    The Red Team simulates real attackers. In our wargame, the instructors control the Red Team. They will launch attack scenarios against your defenses to test how well you prepared.
  </Card>

  <Card title="Gray Team - Referees" icon="gavel" color="#6B7280">
    The Gray Team referees the exercise. Your instructors serve as the Gray Team - they set the rules, judge whether your defenses stopped an attack, and calculate the results.
  </Card>
</CardGroup>

<Note>
  In professional cybersecurity, there is also a **Purple Team** that combines Red and Blue team exercises for collaborative improvement. You will learn more about this concept as the week progresses.
</Note>

## What to expect today

Here is your Day 1 schedule:

| Time                | Activity                           |
| ------------------- | ---------------------------------- |
| 9:00 - 9:15 AM      | Welcome and introductions          |
| 9:15 - 9:45 AM      | Team formation and role assignment |
| 9:45 - 10:30 AM     | Security controls lesson           |
| 10:30 - 10:45 AM    | Break                              |
| 10:45 - 11:30 AM    | CIA Triad lesson                   |
| 11:30 AM - 12:15 PM | Authentication and access control  |
| 12:15 - 12:30 PM    | Break                              |
| 12:30 - 12:55 PM    | Team business briefing activity    |
| 12:55 - 1:00 PM     | Wrap-up and homework               |

## Team business briefing

At the end of today, your team will create a **business briefing** for your new company. You will present:

1. Your **team name** and **company name**
2. What your company does (pick an industry - tech, food, healthcare, retail, etc.)
3. Who holds each **role** on the team
4. What you think your company's biggest cyber risk will be

<Tip>
  Think about real companies you interact with daily. What kind of data do they store? What would happen if that data was stolen or destroyed? Use that thinking when you build your fictional company.
</Tip>

<Warning>
  This camp covers offensive security techniques for **educational purposes only**. All skills taught must be used ethically and legally. Unauthorized use of these techniques is illegal.
</Warning>
