Know and understand secure socket layer (SSL) including encrypted links between the server and the client computer

ICT Syllabus – Quick Reference (IGCSE / A‑Level)

Syllabus BlockKey Concepts & Examples (AO1)Practical Skills (AO2)Evaluation / Decision‑making (AO3)
1. Computer SystemsCPU, RAM, storage (HDD/SSD), input & output devices, operating systems.Identify components in a diagram; install an OS.Compare advantages of SSD vs. HDD for a school server.
2. Input & OutputKeyboards, mouse, touch screen, scanners, printers, speakers.Configure a scanner; set up a printer driver.Assess the suitability of a touchscreen for a maths classroom.
3. Storage & RetrievalPrimary vs. secondary storage, magnetic, optical, flash, cloud.Organise files using a logical folder hierarchy.Evaluate cloud‑based backup vs. local backup for data security.
4. NetworksLAN, WAN, Wi‑Fi, topologies, protocols (TCP/IP, HTTP/HTTPS), IP addressing.Set up a small LAN; assign static IPs.Analyse the impact of network latency on online gaming.
5. Effects of ICTPositive/negative social, economic, environmental impacts; digital divide.Research a case study (e.g., e‑learning during lockdown).Debate the ethical implications of facial‑recognition surveillance.
6. ICT ApplicationsWord processing, spreadsheets, databases, presentations, web authoring, multimedia.Create a formatted report; design a chart in a spreadsheet.Choose the most appropriate application for managing a school library catalogue.
7. Systems Development Life‑Cycle (SDLC)Planning, analysis, design, development, testing, implementation, maintenance.Produce a simple flowchart for a student‑record system.Critique a given system design for usability issues.
9. Audience & CommunicationIdentifying audience, purpose, tone; copyright & plagiarism.Write an email to parents using appropriate tone.Evaluate the effectiveness of a promotional flyer for a school event.
10. File ManagementNaming conventions, folder structures, compression, backup.Compress a folder using ZIP; restore a backup.Recommend a file‑naming policy for a collaborative project.
12‑16. Document Production (Images, Layout, Styles, Proof‑reading, Graphs/Charts)Inserting/resizing images, applying styles, checking spelling/grammar, creating bar/pie charts.Design a newsletter page with consistent style.Assess the clarity of a chart that compares exam results.
17‑21. Databases, Spreadsheets, Presentations, Web AuthoringTables, primary/foreign keys, forms, queries; formulas, functions, sorting; master slides, transitions; HTML/CSS basics.Build a simple student database; create a budget spreadsheet; produce a 5‑slide presentation; publish a basic website.Compare the use of formulas vs. built‑in functions for financial calculations.

1. Personal Data & Legal/Ethical Principles (Syllabus 8.1)

PrincipleWhat It MeansExample in School Context
Lawful basisData may only be collected for a legitimate purpose.Collecting pupil contact details for emergency notices.
ConsentIndividuals must agree to the collection/use of their data.Getting parental permission before publishing a student’s photo on the school website.
Need‑to‑knowOnly authorised persons may access the data.Only teachers, not pupils, can view exam‑paper drafts.
Right to be forgottenPeople can ask for their personal data to be erased.Removing a former pupil’s email address from the alumni mailing list.
Data securityReasonable steps must be taken to protect data from loss or unauthorised access.Storing project files on a password‑protected USB drive.

Safe‑online Checklist for Students

  • Never share passwords, PINs, or personal photos with strangers.
  • Use strong, unique passwords; change them regularly.
  • Only log in to sites that display a padlock icon and start with https://.
  • Do not click links or open attachments from unknown senders.
  • Report cyber‑bullying, phishing, or suspicious activity to a teacher or trusted adult.

2. Threats to ICT Security & Protection Measures (Syllabus 8.3)

ThreatDescription (AO1)Simple Mitigation (AO2)
PhishingFake emails or messages that trick users into giving personal data.Never enter credentials after clicking an unexpected link; verify the sender’s address.
PharmingManipulating DNS or hosts files so a legitimate URL leads to a fake site.Use reputable DNS services; check the certificate details before entering data.
Smishing / VishingPhishing via SMS (smishing) or voice calls (vishing).Do not reply with personal details; contact the organisation through an official channel.
Malware – VirusSelf‑replicating code that attaches to clean files.Keep anti‑virus definitions up‑to‑date; avoid downloading from untrusted sites.
Malware – RansomwareEncrypts files and demands payment for the decryption key.Regularly back up data; disable macro auto‑run in Office apps.
Card‑fraud / Online fraudUnauthorised use of payment details.Enter card numbers only on HTTPS sites; use virtual card numbers where possible.
Hacking / Unauthorised accessGaining control of a computer or network without permission.Use firewalls, keep software patched, enable two‑factor authentication.
Man‑in‑the‑middle (MITM)Attacker intercepts communication between client and server.Verify HTTPS certificates; use VPNs on public Wi‑Fi.

Security Toolbox (Common Protection Tools)

  • Firewalls – hardware or software that filters incoming and outgoing network traffic based on predefined rules.
  • Anti‑virus / anti‑malware software – scans for, quarantines, and removes malicious code.
  • Encryption

    • File‑level encryption (e.g., BitLocker, VeraCrypt) protects data stored on disks.
    • Email encryption (PGP, S/MIME) secures messages.
    • SSL/TLS encrypts data in transit (see Section 5).

  • Strong passwords & password managers – generate and store complex passwords securely.
  • Two‑factor authentication (2‑FA) – adds a second verification step (OTP, authenticator app, hardware token).
  • Digital certificates – electronic documents issued by a Certificate Authority (CA) that bind a public key to an entity’s identity.

3. Recognition & Authentication Methods (Syllabus 8.4)

MethodHow It Works (AO1)Strengths / Weaknesses (AO2)
Password / PINSomething the user knows.Easy to implement; vulnerable to guessing, theft, or reuse.
Biometric (fingerprint, face, iris)Something the user is.Hard to copy; may fail with dirty sensors; raises privacy concerns.
Smart‑card / NFC tagSomething the user has.Provides two‑factor security; can be lost or stolen.
One‑time password (OTP) via SMS or appSomething the user has for a short time.Effective for 2‑FA; depends on mobile network or app availability.

4. What Is SSL/TLS?

Secure Socket Layer (SSL) – now superseded by Transport Layer Security (TLS) – is a cryptographic protocol that creates an encrypted link between a web server (the “server”) and a web browser (the “client”). The link guarantees:

  • Confidentiality – data cannot be read by eavesdroppers.
  • Integrity – any alteration of the data is detected.
  • Authentication – the client can verify it is communicating with the intended server.

Key Cryptographic Concepts Used by SSL/TLS

  • Encryption – converting plaintext into ciphertext using an algorithm and a key.
  • Decryption – reversing the process with the correct key.
  • Asymmetric (public‑key) cryptography – a pair of mathematically linked keys: a public key (shared) and a private key (kept secret).
  • Symmetric cryptography – a single secret key used for both encryption and decryption; much faster than asymmetric encryption.
  • Digital certificate – an electronic document issued by a trusted Certificate Authority (CA) that binds a server’s public key to its domain name.

SSL/TLS Handshake – How the Secure Link Is Created

The handshake occurs before any application data is exchanged. It uses asymmetric encryption to agree on a symmetric session key, then switches to fast symmetric encryption.

StepMessagePurpose
1ClientHelloClient proposes TLS version, supported cipher suites, and sends random data (ClientRandom).
2ServerHelloServer selects TLS version and cipher suite; sends its random data (ServerRandom) and its digital certificate.
3Certificate verificationClient checks the certificate’s CA signature, expiry date, and that the domain name matches.
4ClientKeyExchange (pre‑master secret)Client creates a random pre‑master secret, encrypts it with the server’s public key, and sends it.
5Key generationBoth sides compute the same symmetric session keys from the pre‑master secret, ClientRandom, and ServerRandom.
6Finished (client)Client sends a hash of all handshake messages, encrypted with the newly created session key, to confirm integrity.
7Finished (server)Server replies with its own encrypted hash, completing the handshake.

Suggested diagram: SSL/TLS handshake flow – ClientHello → ServerHello (certificate) → encrypted pre‑master secret → symmetric session keys → encrypted Finished messages.

Encryption After the Handshake

  1. Application data (e.g., a web form) is taken as plaintext.
  2. The data is encrypted with the symmetric session key using a fast block cipher such as AES‑GCM.
  3. The ciphertext travels across the network.
  4. The receiver decrypts it with the same session key to obtain the original plaintext.

5. SSL/TLS Vulnerabilities & How to Avoid Them

  • Out‑dated protocol versions (SSL 2.0, SSL 3.0) – vulnerable to POODLE, BEAST, etc.


    Fix: Disable these versions; use TLS 1.2 or TLS 1.3 only.

  • Weak cipher suites (RC4, DES, 3DES, CBC without MAC) – can be broken with modern hardware.


    Fix: Configure servers to allow only strong ciphers such as AES‑256‑GCM or ChaCha20‑Poly1305.

  • Improper certificate validation – allows attackers to present fake certificates.


    Fix: Ensure browsers/clients check the CA signature, expiry, revocation status, and that the domain matches the certificate.

  • Heartbleed (CVE‑2014‑0160) – information leak in OpenSSL.


    Fix: Update OpenSSL libraries; re‑issue certificates if private keys may have been exposed.

Best Practices for Maintaining SSL/TLS Security

  1. Use the latest TLS version supported by both client and server (currently TLS 1.3).
  2. Disable obsolete protocols and weak cipher suites on the server.
  3. Obtain certificates from reputable Certificate Authorities; renew before expiry.
  4. Implement HTTP Strict Transport Security (HSTS) to force browsers to use HTTPS.
  5. Run regular external scans (e.g., Qualys SSL Labs) to detect mis‑configurations.
  6. Combine SSL/TLS with other security measures: firewalls, anti‑virus, strong passwords, and 2‑FA.

6. Common Browser Indicators of a Secure Connection

  • Padlock icon in the address bar.
  • URL begins with https:// rather than http://.
  • Clicking the padlock shows certificate details (issuer, validity dates, domain).
  • In some browsers, the address bar may turn green for Extended Validation (EV) certificates.

7. Mapping Topics to Assessment Objectives

TopicAO1 (Knowledge)AO2 (Application)AO3 (Evaluation)
Personal data & legal principlesDefine personal data; list the four Data Protection Act principles.Identify which principle applies to a given school scenario.Evaluate the effectiveness of a school’s data‑handling policy.
Threats & mitigationDescribe phishing, pharming, smishing, malware types, MITM.Choose appropriate protective tools for a given threat.Assess the risk of using public Wi‑Fi without a VPN.
Authentication methodsExplain password, biometric, smart‑card, OTP.Match a method to a security requirement (e.g., high‑value transaction).Compare the suitability of biometric vs. 2‑FA for a school login system.
SSL/TLS handshakeList the handshake steps; define asymmetric & symmetric encryption.Interpret a simplified handshake diagram.Critique the security of using TLS 1.0 for an online exam platform.
Vulnerabilities & best practiceIdentify outdated protocols and weak ciphers.Configure a web server to disable SSL 3.0 and enable TLS 1.3.Recommend a policy for certificate renewal and revocation checking.

8. Sample Exam‑Style Questions (Security Section)

  1. AO2 – Application

    A school website currently supports only TLS 1.0. Explain why this is a security risk and describe two steps the school IT officer should take to improve the site’s security.

  2. AO3 – Evaluation

    Two‑factor authentication (2‑FA) is introduced for the school’s virtual learning environment. Evaluate the advantages and possible drawbacks of this measure for students and staff.

  3. AO1 – Knowledge

    Define the term “digital certificate” and state the role of a Certificate Authority (CA) in the SSL/TLS process.

  4. AO2 – Application

    You receive an email that appears to be from your bank asking you to confirm your account details via a link. Using the “safe‑online checklist”, list three actions you should take before responding.

9. Summary

SSL/TLS creates a secure, encrypted link between a client computer and a server. The handshake uses asymmetric cryptography to exchange a secret pre‑master value, from which both parties derive a fast symmetric session key. All subsequent data is encrypted with this key, ensuring confidentiality, integrity, and authentication. Understanding SSL/TLS, together with the broader ICT concepts – personal data protection, common threats, authentication methods, and the full range of syllabus topics – equips students to use technology safely, evaluate security measures critically, and meet the demands of the Cambridge IGCSE/A‑Level ICT examinations.