Demystifying TLS, SSL, and IPsec for the A-Level IT (9626) Syllabus
How TLS and IPsec protect different communication boundaries, and how to explain their mechanisms without confusing channel protection with authorization.
By Abdurrahman Tolay ·
Network security in Cambridge A-Level IT (9626) is no longer a definitions topic. Across the 2025 to 2027 syllabus cycle, the expected depth has moved decisively from "state what encryption is" to protocol mechanics: how a session key comes into existence, why a certificate proves anything, and which layer of the stack a given protocol operates at.
Candidates who prepared with the older definition-first approach tend to write fluent, confident answers that collect roughly half the available marks. The gap is almost always mechanism. This guide covers the mechanics the current mark schemes reward.
The examinable idea in this topic is not "encryption keeps data safe". It is how two machines that have never met agree on a shared secret across a hostile network.
Symmetric vs. Asymmetric Encryption
Almost every extended-response question in this area depends on the candidate handling this distinction cleanly, then showing how the two are combined.
Symmetric encryption
A single shared key both encrypts and decrypts. It is computationally cheap and therefore suitable for bulk data transfer. The standard example is AES, typically at 128 or 256 bit key lengths.
Its weakness is the key distribution problem. Both parties must hold the same key, and delivering that key across an untrusted network is precisely the problem encryption was meant to solve. Additionally, in a network of n participants who each need private communication, the number of keys required grows quadratically, which does not scale.
Asymmetric encryption
A mathematically linked key pair. The public key may be distributed freely and is used to encrypt; the corresponding private key never leaves its owner and is used to decrypt. The standard examples are RSA and elliptic curve cryptography (ECC).
It solves distribution elegantly, but it is orders of magnitude slower than symmetric encryption and produces larger ciphertext. Encrypting a video stream with RSA would be technically possible and practically absurd.
How TLS combines them
This is the highest-value sentence a candidate can write in this topic: asymmetric cryptography is used to establish the session, and symmetric cryptography is used to protect the data. The full sequence:
- ClientHello. The client sends supported TLS versions, a list of cipher suites, and a client random value.
- ServerHello. The server selects protocol parameters. In a certificate-authenticated TLS 1.3 handshake, the certificate and authentication messages follow separately, not inside ServerHello.
- Certificate validation. The client verifies the certificate authority's signature, the domain name, and the expiry date against its trusted root store.
- Key agreement. In modern TLS this uses ephemeral Diffie-Hellman (DHE or ECDHE), where both parties contribute to a shared secret that is never transmitted. The server's private key is used to sign, proving identity.
- Traffic key derivation. TLS 1.3 derives handshake and application traffic secrets using HKDF and the handshake transcript; separate keys protect each direction.
- Encrypted application data. All subsequent traffic is protected symmetrically, with integrity provided by AEAD constructions such as AES-GCM.
Ephemeral key exchange also delivers forward secrecy: compromising the server's long-term private key later does not decrypt previously captured sessions. Naming this earns credit in higher-mark answers.
State it explicitly in the exam: asymmetric encryption solves key distribution, symmetric encryption solves performance, and TLS uses both in sequence.
The Reality of SSL vs. TLS
In everyday professional language, "SSL" survives everywhere. Certificates are sold as SSL certificates, libraries are named OpenSSL, and network engineers still say it out of habit. The syllabus does not accept that habit.
- SSL (Secure Sockets Layer) is the historical protocol. SSL 2.0 and SSL 3.0 are formally deprecated and carry known structural weaknesses, including the POODLE attack against SSL 3.0.
- TLS (Transport Layer Security) is the successor. TLS 1.2 remains widely deployed, and TLS 1.3 is the current standard. TLS 1.0 and 1.1 are also deprecated.
- TLS 1.3 removes legacy algorithms and commonly completes a full handshake in one round trip. Ephemeral (EC)DHE provides forward secrecy; PSK-only key exchange and replay-prone 0-RTT early data require separate caveats.
In Paper 1 and Paper 3 theory answers, the expected articulation is that SSL is the obsolete predecessor and TLS is the current secure standard, and that the terms are not interchangeable even though industry uses them loosely. Writing "the website uses SSL to encrypt data" where the mark scheme expects TLS is an avoidable loss.
IPsec in Virtual Private Networks
The most common structural error in 9626 answers is treating IPsec as "another version of TLS". They operate at different layers and therefore protect different things.
IPsec protects IP-layer traffic selected by policy. Protection can be transparent to applications, but a policy may protect, bypass or discard particular traffic: not every packet is automatically encrypted. TLS protects a connection above a reliable transport, not all traffic on a device. Neither protocol alone establishes continuing application authorization.
The two protocols within IPsec
- AH (Authentication Header) provides integrity and authentication but no confidentiality.
- ESP (Encapsulating Security Payload) can provide confidentiality, integrity and data-origin authentication, depending on the negotiated security association.
- IKE (Internet Key Exchange) handles negotiation of the security association and key material, playing a role analogous to the TLS handshake.
Transport mode versus Tunnel mode
Extended-response questions frequently ask candidates to distinguish these and justify a choice for a given organisation.
- Transport mode encrypts only the payload of the IP packet and leaves the original IP header intact. Overhead is lower, but the source and destination addresses remain visible to anyone observing the traffic. It suits host-to-host communication inside an already trusted network, such as two servers in a data centre.
- Tunnel mode encapsulates the entire original packet, header included, inside a new IP packet with a new outer header. The internal addressing scheme is therefore hidden from observers. This is the mode used for site-to-site VPNs between branch offices and for remote-worker gateway VPNs.
Tunnel mode hides the original header, which hides the internal network topology. That single consequence is usually the mark the question is looking for.
A well-structured answer for a company connecting two offices across the public internet would therefore name IPsec in tunnel mode with ESP, explain that the whole packet is encapsulated so internal addressing is concealed, and note that protection applies to all traffic between the sites regardless of application.
Exam Technique for 6 to 8 Mark Responses
Extended-response marks on encryption protocols are rarely lost to ignorance. They are lost to one-sided answers that describe a technology enthusiastically and never evaluate it.
A structure that scores
- Define precisely. One or two sentences naming the protocol, its layer, and its purpose. Use syllabus vocabulary: confidentiality, integrity, authentication.
- Explain the mechanism. Show how it works, not just what it does. For TLS, the handshake. For IPsec, the mode and the encapsulation.
- Apply to the given scenario. Name the organisation or use case from the question stem explicitly. Generic answers are capped.
- Give advantages. Tied to the scenario, not abstract.
- Give limitations. Processing overhead and increased latency, certificate management cost and renewal, complexity of configuration, key compromise risk, and the fact that encryption protects data in transit but not data at rest on either endpoint.
- Conclude with a judgement. A justified recommendation, referencing the trade-off you consider decisive.
The evaluation the mark scheme wants
A two-sided response might argue that for a retailer processing card payments, TLS 1.3 is essential because it protects individual customer sessions and is natively supported by every browser, but that it adds handshake latency and requires ongoing certificate management. For the same retailer's connection between its warehouse and head office, IPsec in tunnel mode is more appropriate because it protects all inter-site traffic transparently, at the cost of gateway hardware and more complex configuration.
Full marks in this topic come from candidates who explain a mechanism, apply it to the stated business context, and then honestly state what it costs.
Vocabulary checklist before you write
- Confidentiality through encryption.
- Integrity through hashing and message authentication codes.
- Authentication through digital certificates issued by a certificate authority.
- Non-repudiation through digital signatures.
- Forward secrecy through ephemeral key exchange.
Naming all of these in the correct places is frequently what separates a partial answer from a complete one.
Protocol references and study scope
RFC 8446 (TLS 1.3) and RFC 4301 (IPsec architecture) are the technical references. Digital signatures can support non-repudiation in suitable systems; an ordinary TLS session does not automatically provide it.