Skip to content
Computer Science · Grade 12

Active learning ideas

Cryptography: Symmetric & Asymmetric

Active learning works best here because cryptography’s abstract concepts become concrete when students physically simulate failures, code real algorithms, and role-play secure exchanges. These hands-on experiences expose key distribution risks and encryption trade-offs in ways lectures cannot, building durable mental models through repeated action and reflection.

Ontario Curriculum ExpectationsCS.N.7CS.S.2
30–50 minPairs → Whole Class4 activities

Activity 01

Problem-Based Learning35 min · Pairs

Simulation Lab: Symmetric Key Sharing Failures

Pairs simulate a network: one encrypts messages with a shared key, an 'eavesdropper' intercepts during exchange. Groups document breach points, then discuss solutions. Introduce asymmetric basics via provided diagram.

How does asymmetric encryption solve the problem of secure key exchange?

Facilitation TipIn the Simulation Lab, set a visible timer to pressure key exchange and make breaches visible the moment they occur, reinforcing why secure distribution matters.

What to look forPresent students with three scenarios: 1) encrypting a large video file for personal backup, 2) a secure chat application needing to establish a connection, and 3) signing a digital document. Ask students to identify which type of encryption (symmetric, asymmetric, or both) would be most appropriate for each scenario and briefly justify their choice.

AnalyzeEvaluateCreateDecision-MakingSelf-ManagementRelationship Skills
Generate Complete Lesson

Activity 02

Problem-Based Learning50 min · Individual

Coding Challenge: Implement Basic Ciphers

Individuals code a symmetric Caesar shift in Python, test on sample data. Switch to asymmetric demo using libraries like cryptography. Compare output security and speed with class timer.

Differentiate between symmetric and asymmetric encryption algorithms.

Facilitation TipFor the Coding Challenge, provide starter code with intentional errors so students debug encryption outputs, building intuition about cipher behavior.

What to look forFacilitate a class discussion using the prompt: 'Imagine you are designing a secure messaging app. What are the primary challenges of distributing encryption keys to your users? How would you use both symmetric and asymmetric encryption to overcome these challenges and ensure privacy?'

AnalyzeEvaluateCreateDecision-MakingSelf-ManagementRelationship Skills
Generate Complete Lesson

Activity 03

Problem-Based Learning40 min · Small Groups

Role-Play: Asymmetric Handshake Protocol

Small groups act as client, server, and attacker in a TLS-like exchange. Use cards for public/private keys. Rotate roles, debrief on how asymmetry prevents interception.

Justify the use of different encryption types for various security needs.

Facilitation TipDuring the Role-Play, assign roles strictly: one group plays Alice, one Bob, and one Eve, forcing students to act out each protocol step and witness trust establishment.

What to look forOn an index card, ask students to define one key term (e.g., public key, symmetric encryption) in their own words and then explain one specific advantage of using asymmetric encryption over symmetric encryption for secure key exchange.

AnalyzeEvaluateCreateDecision-MakingSelf-ManagementRelationship Skills
Generate Complete Lesson

Activity 04

Case Study Analysis30 min · Whole Class

Case Study Analysis: Algorithm Justification Debate

Whole class reviews scenarios like email vs video streaming. Groups chart pros/cons of AES vs RSA, present justifications. Vote on best fits with evidence.

How does asymmetric encryption solve the problem of secure key exchange?

Facilitation TipIn the Case Study Debate, assign half the class to defend hybrid protocols and half to advocate for pure asymmetric, ensuring balanced arguments.

What to look forPresent students with three scenarios: 1) encrypting a large video file for personal backup, 2) a secure chat application needing to establish a connection, and 3) signing a digital document. Ask students to identify which type of encryption (symmetric, asymmetric, or both) would be most appropriate for each scenario and briefly justify their choice.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

A few notes on teaching this unit

Experienced teachers approach this topic by first grounding students in the human need for secure communication, then layering math only after the problem feels real. They avoid rushing into key generation before students grasp why keys must stay secret, and they explicitly connect failed simulations to real-world breaches. Research shows that pairing concrete simulations with abstract math (like modular arithmetic) deepens retention, so teachers weave coding and role-play alongside explanations.

By the end of these activities, students will confidently distinguish symmetric from asymmetric encryption, justify key choices in real scenarios, and critique algorithm strengths without confusing public and private roles. They will also articulate why hybrids are common and how trust is established online.


Watch Out for These Misconceptions

  • During the Simulation Lab: Symmetric Key Sharing Failures, students may assume symmetric encryption is always more secure because it feels simpler.

    Use the lab’s timed breaches to visibly show that symmetric keys fail without secure exchange. Pause after each breach to ask students to explain why the key was compromised, then contrast with asymmetric’s trust-first approach.

  • During the Role-Play: Asymmetric Handshake Protocol, students may believe the public key can decrypt messages it encrypts.

    Have the Eve role attempt to decrypt a message with the public key during the role-play. When it fails, prompt students to revisit the math behind trapdoor functions and re-label roles to reinforce one-way security.

  • During the Case Study: Algorithm Justification Debate, students may argue that asymmetric encryption replaces symmetric entirely.

    After the debate, collect performance timings from the Coding Challenge and use them to show bulk encryption delays with pure asymmetric. Ask groups to revise their justifications to include efficiency trade-offs.


Methods used in this brief