Computer Science · 12th Grade

Active learning ideas

Common Cybersecurity Threats and Attack Vectors

Active learning works for this topic because cybersecurity threats feel abstract until students see how they function in real systems or manipulate human trust. Labs and role plays turn textbook definitions into visible, memorable experiences where mistakes teach more than lectures ever could.

• Common Core State Standards
• CSTA: 3B-NI-04
• CCSS.ELA-LITERACY.RST.11-12.3

• 30–55 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Escape Room
• 55 min · Pairs

Hands-On Lab: SQL Injection Sandbox

Students use a purpose-built vulnerable web application (like DVWA or a simplified teacher-built version) to attempt a SQL injection on a login form. After successfully bypassing authentication, they inspect the vulnerable code and rewrite it using parameterized queries. The before-and-after comparison makes input sanitization immediately meaningful rather than abstract.

Why is the human element often the weakest link in a security system?

Facilitation Tip

Use the SQL Injection Sandbox to let students attempt an attack and immediately see the database respond, making the vulnerability tangible.

What to look for

Provide students with three brief scenarios, each describing a different type of cyberattack (e.g., a user clicking a suspicious link, a database error message, a fake login page). Ask students to identify the primary attack vector for each scenario and briefly explain why.

• Remember
• Apply
• Analyze
• Relationship Skills
• Self-Management

Activity 02

• Role Play
• 30 min · Small Groups

Role Play: The Social Engineering Audit

One student acts as a helpdesk employee receiving a call from another student playing an urgent executive requesting a password reset without proper verification. The class observes and identifies red flags. After three rounds with different scenarios, the class builds a shared protocol for handling suspicious requests, turning observation into written procedure.

Differentiate between various types of cyberattacks and their primary objectives.

Facilitation Tip

During the Social Engineering Audit, stay outside the role play to observe which students rely on instinct versus structured questioning techniques.

What to look for

Pose the question: 'Why is the human element often considered the weakest link in cybersecurity?' Facilitate a class discussion where students share examples of social engineering and discuss the cognitive biases that make people susceptible.

• Apply
• Analyze
• Evaluate
• Social Awareness
• Self-Awareness

Activity 03

• Gallery Walk
• 40 min · Small Groups

Gallery Walk: The Anatomy of a Breach

Post case study cards for four real breaches (Equifax 2017, Target 2013, SolarWinds 2020, and a recent incident). Each card shows the attack vector, the technical and human failures, and the eventual impact. Groups rotate and identify the single point where each breach could have been prevented, then debrief on which attack vectors appeared most frequently across all four cases.

Analyze how different attack vectors exploit vulnerabilities in software or human behavior.

Facilitation Tip

For the Gallery Walk, position yourself at a station to overhear how students explain technical details to peers using their own words.

What to look for

Present students with a simplified code snippet that is vulnerable to SQL injection. Ask them to identify the vulnerable part of the code and write a single malicious SQL query that could exploit it in a controlled environment.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

A few notes on teaching this unit

Teachers approach this topic by balancing technical precision with human realism. Avoid oversimplifying social engineering as trickery alone; emphasize how attackers exploit predictable cognitive biases. Research shows students retain concepts better when they practice both exploiting and defending against the same attack, so labs and role plays should include debriefs that reverse the perspective.

Students will move from identifying attack vectors to explaining why they succeed and how to prevent them. Success looks like clear analysis of vulnerabilities, precise use of terminology, and thoughtful discussion of human and technical defenses as equally critical components of security.

---

Watch Out for These Misconceptions

• During the Role Play: The Social Engineering Audit, watch for students who assume only gullible people fall for social engineering.

  Use the spear phishing email crafted from a student’s public social media profile to show how personalized, credible attacks bypass skepticism even among security-aware professionals.

• During the Hands-On Lab: SQL Injection Sandbox, watch for students who believe SQL injection is too simple to evade modern developers.

  Have students audit a snippet of real open-source code for injection vulnerabilities. Point out how input validation is often omitted during fast-paced development, keeping SQL injection in the OWASP Top 10 for over a decade.

---

Methods used in this brief

• Escape Room
• Role Play
• Gallery Walk