All subjects · Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

Certificate-based encryption and digital certificates

Edexcel IAL Information Technology · WIT13 2 hour written exam on data, enabling technologies and systems development

Public key encryption only works if you can trust that a public key really belongs to who it claims. Digital certificates, issued by certificate authorities, provide that trust (spec 13.5.3).

Practise this in the app: instant marking and a fix for every mistake. Free, no email needed to start.

Practise this lesson

The problem certificates solve

If an attacker can swap their own public key for the bank's, a customer would encrypt data for the attacker (a man-in-the-middle attack). A public key certificate (digital certificate) binds a public key to an identity, and is digitally signed by a trusted third party, a certificate authority (CA), which has checked that identity.

What a certificate contains

Certificates on the web follow the X.509 standard. The IETF profile (RFC 5280) lists these basic fields:

FieldMeaning
VersionCertificate format version (version 3 when extensions are present)
Serial numberUnique number given by the issuing CA
Signature algorithmThe algorithm the CA used to sign the certificate
IssuerThe name of the CA that issued it
ValidityNot before and not after dates
SubjectThe name of the owner (for example a website's domain or an organisation)
Subject public key infoThe owner's public key and its algorithm
ExtensionsExtra information such as permitted uses
CA's signatureThe CA's digital signature over all the above

How certificate-based encryption works (HTTPS)

1. The browser connects to a website, which sends its certificate.

2. The browser checks the certificate: the CA's signature is valid (using the CA's public key, which is pre-installed in the browser or operating system as a trusted root certificate, possibly via a chain of intermediate certificates), the dates are valid, the domain name matches, and it has not been revoked (CAs publish certificate revocation lists).

3. The browser uses the site's public key to agree a symmetric session key securely.

4. All data in the session is encrypted with the session key.

If any check fails, the browser shows a warning.

Other uses: signing software and emails, authenticating devices and users (client certificates), VPNs.

Strengths and weaknesses

Strengths: verifies identity, prevents man-in-the-middle attacks, enables secure key exchange, supports integrity and non-repudiation through signatures.

Weaknesses: trust depends on CAs; a compromised or careless CA can issue fraudulent certificates; users often ignore warnings; certificates expire and must be renewed; a valid certificate proves who owns a domain, not that the site is honest.

Worked example

A user visits an online shop. Explain how the shop's certificate allows the user's card details to be sent securely.

  1. The shop's server sends its certificate, containing its domain name and public key, signed by a CA.
  2. The browser verifies the CA's signature with the CA's trusted public key, and checks the dates and domain.
  3. Now confident the public key is genuine, the browser uses it to agree a session key with the server.
  4. Card details are encrypted with the session key, so an eavesdropper cannot read them.

Answer: The certificate proves the public key belongs to the shop, enabling secure key exchange

Key idea: A digital certificate binds a public key to an identity and is signed by a certificate authority. Browsers check the signature, dates, domain and revocation, then use the public key to set up a symmetric session key.

Check yourself

  1. What is the role of a certificate authority?
    • To encrypt every website's data itself
    • To store users' passwords
    • To provide internet access
    • To verify an organisation's identity and digitally sign its certificate
    Show answer

    To verify an organisation's identity and digitally sign its certificate. The CA vouches for the key's owner.

  2. Which item is found in a public key certificate?
    • The subject's private key
    • The subject's public key
    • The user's password
    • The session key
    Show answer

    The subject's public key. Private keys are never in a certificate.

  3. How does a browser check that a certificate is genuine?
    • It phones the website owner
    • It decrypts the website's private key
    • It compares the colour of the padlock
    • It verifies the CA's digital signature using the CA's public key
    Show answer

    It verifies the CA's digital signature using the CA's public key. Signature verification with the trusted CA key.

  4. Which attack do certificates mainly help prevent?
    • Man-in-the-middle attacks that substitute a fake public key
    • Denial of service attacks
    • Shoulder surfing
    • Power cuts
    Show answer

    Man-in-the-middle attacks that substitute a fake public key. They prove whose key it is.

  5. A company's private key is stolen. What should happen to its certificate?
    • Nothing, because certificates cannot be changed
    • The public key should be emailed to all customers
    • The CA should revoke it so browsers stop trusting it
    • The certificate's validity should be extended
    Show answer

    The CA should revoke it so browsers stop trusting it. Revocation lists warn relying parties.

  6. Explain why a browser warns the user when a website's certificate has expired.
    Show answer

    An expired certificate is no longer guaranteed by the certificate authority, so the browser cannot be sure the public key still belongs to the site, which means the connection might not be secure or trustworthy.. Validity, so trust cannot be confirmed.

Practise with instant feedback

Sources

Last updated 8 November 2026. Spotted a mistake? Tell us.