Dr Tim Bell ran a webinar at the start of 2025 to help teachers understand Encryption. The recording of this can be found on Youtube L2 External - Encryption Webinar
This online webinar looks at what the general topic is about, and some specific learning activities that you can use with your students to engage them with the key concepts in the topic.
Check out the Computer Science Field Guide: https://www.csfieldguide.org.nz/en/chapters/coding-encryption/
Watch the video and read through the chapters thoroughly.
The encryption exam questions may cover any of the following:
AES (Advanced Encryption Standard)
privacy
remote garage door openers
SHA-256 (Secure Hash Algorithm)
the key exchange problem
uses in healthcare.
Questions may cover symmetric encryption, asymmetric encryption, hashing, VPN use of encryption, WPA2/WPA3 Personal and Enterprise Wi-Fi in schools, device encryption such as BitLocker in schools, password managers, and digital signatures. Impact questions focus on human factors and social impact.
The standard progresses from explaining the concept to evaluating its wider implications.
students identify the concept and explain what it is, how it works, and where it is applied, using accurate terminology, a relevant mechanism, and a specific school-based example.
students go further by explaining an impact of the concept, showing through clear cause-and-effect links why a technical choice changes outcomes for people or the organisation, including relevant human factors or social consequences.
students explain key problems or issues by evaluating limitations, trade-offs, competing needs, and remaining risks, then drawing a justified conclusion supported by multiple connected examples and reasoned judgement.
Plaintext: The original readable data before encryption.
Ciphertext: The unreadable output produced by an encryption algorithm.
Encryption algorithm: A defined procedure that transforms plaintext into ciphertext using a key.
Decryption: The process of recovering plaintext from ciphertext using the appropriate key.
Key: A value that controls an encryption, decryption, signing, or verification operation.
Symmetric encryption: The same secret key is used to encrypt and decrypt.
Asymmetric cryptography: A mathematically related public key and private key perform different operations.
Hashing: A one-way process that produces a fixed-length digest from input data.
Salt: A unique random value combined with a password before password hashing.
Digital signature: Evidence created with a private key that can be checked with the associated public key to support integrity and authenticity.
Certificate: A signed digital record that connects an identity or service to a public key.
Key exchange: A protocol used to establish shared key material across an untrusted network.
Hybrid encryption: Asymmetric cryptography establishes or protects a session key; symmetric encryption then protects the main data.
Encryption at rest: Protection applied to stored data such as drives, files, backups, or cloud storage.
Encryption in transit: Protection applied while data travels through a network.
Confidentiality: Information is available only to authorised people.
Integrity: Information remains accurate and unauthorised changes can be detected.
Authenticity: There is evidence about the source or signer of information.
Availability: Authorised users can access information when needed.
· A teacher laptop uses full-disk encryption so student information is not readable if the device is stolen while locked.
· WPA3-Enterprise gives staff and students individual Wi-Fi access rather than one shared password for the whole school.
· A staff member uses an encrypted VPN tunnel to reach an internal file service from home.
· A password manager creates a different password for every school service and protects the vault with MFA.
· A school website uses a certificate and TLS so visitors can verify the service and communicate over an encrypted connection.
· An official assessment document is digitally signed so recipients can check that it is authentic and unchanged.
· A school stores BitLocker recovery keys in a restricted administrative system and records when a key is accessed.
· A login system stores salted password hashes rather than readable passwords.
Encryption is only effective when keys are generated securely, given to the correct people or devices, stored safely, replaced when necessary, revoked after compromise, and recoverable by authorised people. Certificates help connect public keys to identities, but users and devices must trust the certificate issuer and must respond safely to warnings.
Confidentiality versus recovery: Keys should be difficult for unauthorised people to obtain, but authorised recovery may be required after a forgotten password, failed device, or staff departure.
Protection versus availability: Encryption can protect lost devices, but lost keys can make legitimate information permanently inaccessible.
Individual access versus complexity: Enterprise Wi-Fi and certificates improve individual control but require more infrastructure, expertise, and support.
Security versus compatibility: Newer standards may improve protection while excluding older devices or creating BYOD problems.
Privacy versus lawful or organisational access: Strong encryption protects people and organisations, while governments or employers may seek exceptional access. Any deliberate weakness can create risk for all users.
Trust versus warning fatigue: Certificate and security warnings are useful only when users understand them and can act without being overwhelmed.
Centralised recovery versus concentrated risk: A central store of recovery keys supports continuity but becomes a high-value target.
Current protection versus future change: Algorithms, devices, protocols, and certificate practices must be updated over time, which creates cost and migration challenges.
Human factors are shaped by system design, workload, accessibility, training, trust, incentives, and organisational culture. Encryption should not be treated as purely mathematical because its success depends on people using keys, recovery processes, devices, warnings, and access systems correctly.
Complex Wi-Fi enrolment may disadvantage students with older devices or limited technical support.
A requirement to use a personal phone or particular biometric can create accessibility, privacy, and equity concerns.
·Lost recovery keys can interrupt teaching, assessment, or administration.
Users may ignore certificate warnings if they see too many warnings or do not understand the consequences.
A data breach may harm wellbeing, trust, reputation, and participation even when technical services are restored.
·Password managers reduce memory load, but users need confidence in the vault and access to secure recovery.
·Encryption protects confidential communication for ordinary users, journalists, communities, and organisations, but can also be misused to conceal harmful activity.
Central management can improve consistency while increasing the power and responsibility of administrators and third-party providers.
Scenario: Kōwhai College stores student records, assessment files, staff documents, and backups. Staff use laptops, cloud services, remote access, and school Wi-Fi.
Classify each example as plaintext, ciphertext, key, hash, certificate, digital signature, or recovery information.
For each example, connect it to confidentiality, integrity, authenticity, or availability.
A readable assessment spreadsheet before encryption.
An unreadable encrypted copy of the spreadsheet.
A BitLocker recovery key stored in the school administration system.
A SHA-256 digest published beside a software download.
A certificate presented by the school website.
A signed assessment schedule sent to teachers.
Extension: Identify which items must remain secret and which may be public.
The readable assessment spreadsheet is plaintext. Its confidentiality could be harmed if an unauthorised person reads it, while unauthorised changes affect integrity.
The encrypted copy is ciphertext. It can be stored or transmitted, but it is only useful protection if the decryption key is secured.
The BitLocker recovery key is highly sensitive key-recovery information. It supports availability for authorised recovery but can defeat confidentiality if exposed.
A file hash is not secret and does not encrypt the file. It can be compared with a newly calculated hash to detect a change.
Encryption is a method of converting information into a code to prevent unauthorized access. It keeps digital communication and data private and secure.
Uses mathematical algorithms and keys to scramble (encrypt) and unscramble (decrypt) messages.
Two main types:
Symmetric encryption (same key for encryption and decryption)
Asymmetric encryption (public and private keys)
Common algorithms: AES, RSA
Education
Online banking and shopping (HTTPS)
Messaging apps (WhatsApp, Signal)
Secure login systems
Protecting stored data on devices and in the cloud
Essential for digital security and protecting personal and financial information.
Enables trust in online systems and services.
1. Key, password, and recovery management
Encryption only works if keys, passwords, private keys, and recovery keys are managed safely. If they are stolen, the data may be exposed. If they are lost, the school may be locked out of important files, devices, or backups.
2. Human behaviour and false security
Encryption does not stop phishing, weak passwords, password sharing, unlocked devices, or staff accidentally sending information to the wrong person. Schools may also assume encrypted data is completely safe, even though attackers can still target users or accounts.
3. Usability, cost, and access trade-offs
Strong encryption can make systems harder to use and manage. Schools need technical support, staff training, recovery procedures, and compatible devices. If security is too difficult, users may try to bypass it, but if it is too weak, sensitive student and staff data is at risk.
Run through the main points, summerising the content on the CS Field Guide
Refer to Dr Tim Bell's Webinar (above under Teacher Help) for some learning activites.
Foundational understanding to the problem of sending secure information
The Problem
You want to send a secret message to a neighbour via an untrusted messenger.
Locking the message box helps, but how can your neighbour unlock it without giving the key to the messenger?
Pass 1:
You lock the message in a box and send it (still locked) to your neighbour via the messenger.
Pass 2:
Your neighbour adds their own lock (now double-locked) and sends it back.
Pass 3:
You remove your lock and send the singly locked box (with your neighbour’s lock only) back.
The messenger could fake the protocol:
Adds their own lock instead of delivering to your neighbour.
Tricks you into removing your lock.
Ends up with a box only locked with their lock, which they can now open.
Lesson:
Even clever protocols can be broken if identity or authenticity isn’t verified.
To understand encryption and secure transfer of information we must fist understand how Public and Private keys work.
How to share Keys
When two computers want to communicate securely, they need a shared secret key. But sending that key directly over a public network risks interception.
Diffie-Hellman solves this by allowing both parties to agree on a shared secret without ever transmitting it directly.
How it works:
Both sides agree on a public base and modulus.
Each chooses a private secret number.
They compute a value using:
modular exponentiation → (base^secret) mod modulus
and exchange those values.
Each party raises the received value to the power of their own secret → resulting in the same shared key.
Even if someone intercepts the public values, they can’t reverse the process easily due to the discrete logarithm problem.
Why it’s secure:
Uses math that’s easy to compute but hard to reverse.
Keeps private keys secret.
Widely used for securing internet traffic (e.g. HTTPS).
Important:
Modulus should be a large prime.
Base should be a primitive root to ensure key diversity.
Without these, brute-force attacks become easier.
0:00 – Introduction to Secure Communication
Shared secret key enables encrypted communication.
Known as symmetric key cryptography.
0:36 – The Key Exchange Problem
Sending a secret key publicly is insecure.
Solution needed: agree on a key without revealing it.
0:53 – Enter Diffie-Hellman Protocol
Allows two parties to establish a shared secret key over a public channel.
Based on mathematics, not secrecy of transfer.
1:08 – Basic Idea Behind Shared Secrets
Each person chooses a secret number.
Goal: combine secrets into a shared value without exposing individual secrets.
2:03 – A Flawed Addition-Based Example
Demonstrates why simple operations like addition are insecure.
Easy to reverse with subtraction.
3:52 – Modular Exponentiation to the Rescue
Core operation of Diffie-Hellman:
base^secret mod modulus
Easy to compute, hard to reverse (known as the discrete logarithm problem).
5:55 – How Diffie-Hellman Works (Step-by-Step)
Agree on public base and modulus.
Each party chooses a private secret.
Calculate and exchange modular exponents.
Each raises the received value to their private secret → shared key.
7:17 – Security Requirements
Use a large prime modulus.
Choose a good base (e.g. a primitive root).
Avoid weak bases (like 1 or non-diverse remainders).
8:44 – Real-World Use
Diffie-Hellman secures internet communication (e.g. HTTPS).
Prevents attackers from decrypting messages even on public networks.
To understand encryption and secure transfer of information we must fist understand how Public and Private keys work.
Core Idea of Encryption
Encryption transforms plaintext into ciphertext using a secret key. A simple method like bitwise XOR (exclusive or) offers perfect secrecy only if the key is never reused — a limitation known as the one-time pad.
What Makes a Good Cipher
According to Claude Shannon, strong ciphers should exhibit:
Confusion: Complex relationships between the key and ciphertext.
Diffusion: A small change in plaintext should cause widespread change in the ciphertext.
Security Through Design
The combination of substitution, shifting, mixing, and key addition in AES introduces both confusion and diffusion. Each transformation increases resistance to attacks, making it computationally infeasible to break with current technology — especially with longer key lengths (AES-128, AES-192, AES-256).
Secure Communication:
AES is used to encrypt data transmitted over the internet, including emails, chat applications, and instant messaging, ensuring privacy and preventing eavesdropping.
File and Disk Encryption:
Many operating systems and file storage solutions use AES to encrypt files and hard drives, protecting sensitive data from unauthorized access.
Wireless Security:
AES is a core component of WPA2 and WPA3 protocols, which secure Wi-Fi networks and protect data transmitted over wireless connections.
Virtual Private Networks (VPNs):
VPNs use AES to encrypt network traffic, securing online activities and communications.
Financial Transactions:
Banks and financial institutions use AES to protect sensitive information like credit card details and transaction data during online transactions.
Background
In 1997, NIST called for a new encryption standard.
After years of analysis, Rijndael was chosen and became AES.
Now widely used to encrypt data on drives, in HTTPS, and on devices.
Plaintext + Secret Key → Ciphertext
Uses bitwise XOR (exclusive OR) for one-time pad encryption (secure only if key is used once).
Repeating keys weakens security due to detectable patterns.
Based on block cipher (fixed-size blocks, typically 128 bits).
Built around two key concepts from Claude Shannon:
Confusion – makes key influence complex.
Diffusion – spreads plaintext bits across ciphertext.
1. Key Expansion
Original key is expanded into round keys via byte transformations and constants.
Ensures bits in round keys depend on many parts of original key.
2. SubBytes (Substitution)
Each byte is replaced using a non-linear substitution table (S-box).
Adds confusion.
3. ShiftRows
Rows in the 4×4 byte grid (the "state") are cyclically shifted.
Spreads byte values across columns → diffusion.
4. MixColumns
Each column’s bytes are mathematically mixed (finite field arithmetic).
Spreads influence of each byte → more diffusion.
5. AddRoundKey
Each round’s key is XORed with the state.
Binds the encryption to the key.
Initial AddRoundKey.
Then multiple rounds of:
SubBytes → ShiftRows → MixColumns → AddRoundKey
Final round omits MixColumns.
Number of rounds:
10 for 128-bit keys (AES-128)
12 for 192-bit keys
14 for 256-bit keys
Each step contributes to security:
SubBytes hides structure.
ShiftRows + MixColumns obscure patterns.
Multiple rounds increase complexity.
Key size determines resistance to brute-force attacks.
Encryption is important in education because schools store and send sensitive information every day. This includes student records, assessment results, attendance data, medical information, learning support notes, staff files, passwords, financial information, and communication with whānau. If this data is intercepted, stolen, or accessed without permission, it could harm students, staff, families, and the school’s reputation.
Encryption protects data by converting readable information, called plaintext, into unreadable ciphertext. The data can only be changed back into readable form if the correct key or method is used. This means that even if a file, device, or message is stolen, the information may still be protected.
Symmetric encryption is where the same secret key is used to encrypt and decrypt data. Schools might use symmetric encryption to protect stored files, backups, laptops, or network traffic because it is fast and efficient. A limitation is that the key must be stored and shared securely. If the key is stolen, the encrypted data may be exposed.
Asymmetric encryption, which uses a public key and a private key. The public key can be shared, but the private key must be kept secret. This is useful for secure websites, certificates, digital signatures, and setting up secure communication. For example, when a teacher logs into a secure school learning platform using HTTPS, encryption helps protect login details and student information as it travels across the internet.
Is related to encryption but works differently. A hash turns data into a fixed-length value, but it is not designed to be reversed. Schools can use hashing to store password checks safely. Instead of storing the actual password, the system stores a hashed version. When a user logs in, the password they type is hashed and compared with the stored hash. Strong password systems also use salts and slow hashing methods to make attacks harder.
Is also used in school Wi-Fi. WPA2 and WPA3 help protect wireless communication so that people nearby cannot easily read data being sent over the network. WPA2/WPA3-Personal may use a shared password, while WPA2/WPA3-Enterprise can give each user their own login. Enterprise systems are usually better for schools because access can be removed for one user without changing the password for everyone.
Such as BitLocker, on staff laptops. If a laptop is lost or stolen, device encryption helps prevent someone from removing the drive and reading files directly. This is especially important where staff devices contain reports, assessment files, student data, or saved login information.
Encryption also supports password managers. A password manager stores many strong, unique passwords inside an encrypted vault. This helps staff and students avoid weak or reused passwords. However, it depends on the user protecting the master password and using multi-factor authentication where possible.
Are another use of encryption. They can show that a message or file came from the claimed sender and has not been changed. In a school context, this could help protect official documents, reports, assessment files, or software updates from tampering.
The social impact of encryption in education is that it helps protect privacy, trust, and safety. Students and families expect schools to protect personal information. At the same time, schools must balance security with usability. If encryption systems are too difficult, people may try to work around them by sharing passwords, using personal email, or saving files insecurely.
Encryption does not stop someone from giving away their password, clicking a phishing link, leaving a laptop unlocked, or sending information to the wrong person. It also does not protect data once an authorised user has opened it. Strong encryption can also create usability issues. For example, if a staff member forgets a password or loses access to a recovery key, important files may become unavailable
Overall, encryption is a key protection for education systems. It helps keep school data confidential, supports secure communication, protects lost or stolen devices, and makes password storage safer. However, encryption works best when combined with good human practices, such as strong passwords, multi-factor authentication, staff training, secure key management, backups, and clear school procedures.
What is BitLocker and BitLocker recovery?
Good for explaining device encryption, lost/stolen laptops, and the issue of recovery keys. This links well to a school context: “What happens if a teacher’s laptop with assessment files is stolen?”
Microsoft’s own BitLocker overview is also useful as a teacher reference: BitLocker encrypts drives so that someone trying to access the disk offline cannot read its contents, and recovery keys may be needed after security or hardware changes.
Your scenario could involve:
a secondary school network
staff laptops and assessment files
student records and reports
school Wi-Fi
a learning management system
cloud storage
email communication with whānau
remote staff access
password managers
digitally signed school documents
Your response should explain how encryption works, where it is used, what problems it addresses, what its limitations are, and how it affects people in a school community.
Explain the key ideas behind encryption in your school scenario.
You should include:
plaintext
ciphertext
encryption
decryption
keys
symmetric encryption
asymmetric encryption
hashing
confidentiality
integrity
authentication
digital signatures
For example:
Student assessment records are plaintext when a teacher can read them. If the files are stored on an encrypted staff laptop, the data is converted into ciphertext so that someone who steals the laptop cannot easily read the files. The encryption key is needed to decrypt the data. This helps protect the confidentiality of student information, but it depends on the login password and recovery key being managed securely.
A strong response should show how the ideas connect rather than giving isolated definitions.
You could include:
symmetric encryption
asymmetric encryption
hashing and salted password storage
HTTPS / TLS
VPN encryption
WPA2 / WPA3-Personal
WPA2 / WPA3-Enterprise
BitLocker or other device encryption
password managers
digital signatures
For each mechanism you choose, explain:
what problem it addresses
how the mechanism works
where it would be used in a school
which information, device, account, or system it protects
its important limitations
For example:
WPA2/WPA3-Enterprise can protect school Wi-Fi by giving each user their own login rather than using one shared password for everyone. This means a student, teacher, or guest can be given access individually, and access can be removed without changing the Wi-Fi password for the whole school. It helps protect data travelling over the wireless network and reduces the risk of unauthorised access. However, it still depends on secure account management, correct configuration, and users not sharing their login details.
Another example:
BitLocker is device encryption that protects the data stored on a laptop drive. If a staff laptop containing reports or assessment files is lost or stolen, the files cannot easily be read by removing the drive and connecting it to another computer. However, if the teacher is already logged in, leaves the device unlocked, or gives away their password through phishing, BitLocker will not stop the attacker from accessing data as that user.
You could discuss:
staff managing passwords and recovery keys
students using school accounts and Wi-Fi
families trusting the school with personal data
teachers accessing files from home
technical staff managing certificates, keys, devices, and accounts
phishing and stolen passwords
lost or stolen laptops
password managers and master passwords
access problems when encryption or MFA fails
privacy and monitoring
digital signatures for trust in documents
the consequences of a data breach
For example:
A password manager can help staff use strong, unique passwords for school systems. This reduces the risk that one stolen or reused password will expose many accounts. However, it also creates a human risk because the master password becomes extremely important. If staff forget the master password, lose access to recovery options, or do not understand how to use the password manager safely, they may be locked out or may return to unsafe habits such as writing passwords down.
Another example:
Encryption helps protect student privacy because medical notes, pastoral records, learning support information, and assessment data are sensitive. If families believe the school cannot protect this information, trust in the school may be damaged. However, strong encryption also creates access and recovery responsibilities. The school must make sure authorised staff can still access information when it is needed for student safety or learning.
Possible perspectives include:
students and school leaders
teachers and network administrators
parents/whānau and the school
privacy advocates and safety teams
ordinary users and technical staff
schools and cloud-service providers
staff working remotely and the people responsible for security
users who want convenience and users whose data needs protection
privacy versus monitoring
security versus convenience
strong encryption versus recovery problems
individual Wi-Fi accounts versus setup complexity
device encryption versus access when passwords or recovery keys are lost
password managers versus reliance on one master password
VPN access versus risks from unmanaged home devices
HTTPS and certificates versus users trusting fake websites
digital signatures versus users not understanding what they prove
encrypted data versus data exposed after an authorised user opens it
cost and support versus level of protection
using WPA2/WPA3-Enterprise for school Wi-Fi
enabling BitLocker on staff laptops
using password managers for staff
using MFA for important school accounts
using HTTPS/TLS for school platforms
storing password hashes securely with salts
protecting and auditing recovery keys
using digital signatures for official files or software
training staff and students about phishing
creating clear procedures for lost devices
testing backup and recovery processes
providing accessible alternatives for users who struggle with authentication systems
which encryption mechanisms should be used
why encryption must be combined with good procedures
which risks cannot be removed completely
how the school should balance confidentiality, access, privacy, usability, and cost
when systems would be safe enough to use
when access should be restricted or stopped
Encryption is not just one tool. In schools, it is a set of mechanisms that protect data while it is stored, sent, or verified.
Symmetric encryption, asymmetric encryption, hashing, WPA2/WPA3, HTTPS/TLS, BitLocker, password managers, VPNs, and digital signatures can all protect school systems in different ways. However, encryption does not remove every risk. It depends on secure keys, strong passwords, good configuration, recovery procedures, user training, and responsible behaviour.
A school encryption system should therefore be judged not only by whether it uses strong algorithms, but also by whether it protects student and staff data in a way that is usable, recoverable, fair, maintainable, and appropriate for the people affected.
DTTA will provide one at the start of Term 3. This will be advertised on the DTTA Mobilse forum.
This the DTTA Derived Grade Exam Resources for 91898 provided in 2024
Your teacher will provide this. Do your best and remember to give specific examples!