TK Study

Software Engineering › Key terms › Y12 Secure Software Architecture › Cryptography

Cryptography

Term Y12 Secure Software Architecture

Definition

Converting readable data (plain text) into unreadable cipher text with an algorithm and key so only the holder of the right key can read it; also supports hashing and digital signatures.

Example: Encryption keeps the data confidential.

Found in: syllabus, school notes.

Where it is used in the test

Syllabus area: Y12 Secure Software Architecture.

Question types it can appear in

Where it has appeared in the paper

Secure Software Architecture (Part B). Part letters follow each paper’s own layout.

Related past questions

These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.

Study links

How to use it in an answer

A model sentence

General advice, built from the definition and example above

“Converting readable data (plain text) into unreadable cipher text with an algorithm and key so only the holder of the right key can read it; also supports hashing and digital signatures.” Then apply it: Encryption keeps the data confidential.

In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.

Command words used with it

From the linked past questions
  • Identify: Recognise and name. (Sample exam Q3 (1 mark): Encryption)

Technique for the question types

Worked answers from the marking guidelines

Sample exam Q3 (1 mark): Encryption (1 mark): criteria and sample answer

Criteria

1: Identifies the correct answer.

Sample answer

Implement data encryption

Open the question page

Common mistakes

General advice
  • Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
  • Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.

Same group in the syllabus: Security by design · Sandboxing · Privacy by design · Proactive not reactive · Embed privacy into design · Respect for user privacy

← Cross-site scripting (XSS)In Y12 Secure Software ArchitectureCyber attack →