Internet security — AQA A-Level Computer Science
Internet security encompasses the protocols, technologies, and practices designed to safeguard data transmission and network infrastructure against unauthorised access and cyber threats. In AQA A-Level Computer Science, this centres on asymmetric and symmetric encryption, digital signatures, digital certificates, firewalls, and mitigating vulnerabilities like DDoS and malware.
Internet security explained
A digital certificate is a file that binds a public key to the identity of an organisation or person, and it is issued by a trusted certificate authority (CA).
Read the full explanation
To obtain one, the applicant generates a public and private key pair, then sends the public key and identity details in a certificate signing request to a CA. The CA checks the applicant's identity, then signs the certificate with its own private key so that anyone can verify it using the CA's public key. A digital signature is created by the sender hashing a message and encrypting that hash with their private key, and it is used to confirm the sender's identity and show the message has not been altered. The receiver decrypts the signature with the sender's public key, hashes the received message, and compares the two hashes. A match confirms authenticity and integrity; a mismatch shows tampering or a fake sender.
Your focus
- Explain how digital certificates and digital signatures are obtained and used.
Which command word is this?
Set out the mathematical or logical reasons how or why a security mechanism works. Marks are awarded for detailed step-by-step links (e.g. hashing -> encrypting with private key -> comparing hashes).
Internet security exam tips
Topic Overview
Internet security encompasses the theoretical principles, cryptographic protocols, and architectural mechanisms engineered to protect data in transit and networked devices from interception, tampering, and disruption. In AQA A-Level Computer Science, this area bridges computer networks and computational logic, requiring students to master the mathematical foundation of encryption, the role of trusted intermediaries, and multi-layered network defences.
Understanding these security concepts is critical in an era dominated by cloud computing, ubiquitous web transactions, and pervasive cyber threats. Students examine not only how secure communication channels are established using hybrid cryptosystems and digital certificates, but also how vulnerabilities such as malware, social engineering, and distributed attacks compromise modern computing systems.
Key Concepts
- →Symmetric vs Asymmetric Encryption: Symmetric uses a single shared secret key for encryption and decryption; asymmetric utilizes mathematically linked public and private key pairs.
- →Digital Signatures and Hashing: A digital signature is produced by encrypting a message hash with the sender's private key, guaranteeing message integrity, authenticity, and non-repudiation.
- →Digital Certificates and CAs: Issued by trusted Certificate Authorities (CAs) to bind an entity's identity to their public key, containing the serial number, expiry date, public key, and CA digital signature.
- →Network Firewalls: Inspect traffic across network perimeters via packet filtering (stateless checks on IP, port, protocol), stateful inspection (monitoring connection state/context), and application proxies.
- →Cyber Threats: Classifications of threats including viruses, worms, trojans, phishing, pharming, and Distributed Denial of Service (DDoS) attacks.
Marking Points
- Describes the key pair being generated before a certificate is requested
- States that a certificate authority verifies the applicant's identity before issuing the certificate
- Explains that the CA signs the certificate with its private key
- Explains that the sender creates a hash of the message and encrypts it with their private key to form the signature
- Explains that the receiver decrypts the signature with the sender's public key and compares hashes to confirm integrity
Examiner Tips
- 💡Write the obtaining steps and usage steps as separate ordered sequences.
- 💡Name which key is used at each stage: the applicant's private key, the CA's private key, and the sender's public key.
- 💡Include the hash comparison as the final step of verification.
- 💡Always state the ownership and type of key explicitly. Never simply write 'encrypt with the key' — write 'Alice encrypts using Bob's public key'.
- 💡Remember the distinction between confidentiality and authenticity. Encrypting with a recipient's public key achieves confidentiality. Encrypting with a sender's private key achieves authentication/non-repudiation.
- 💡When explaining how digital signatures verify integrity, make sure to detail both sides: generating the hash at the sender end, and generating and matching the hash at the recipient end.
Common Mistakes
- Confuses the signature's purpose with encryption of the whole message; the signature is a hash encrypted with the private key, and the message itself is not necessarily encrypted. Correct by stating which part is encrypted.
- Says the receiver decrypts the signature with their own private key; the sender's public key is used. Correct by naming the matching key.
- Describes the certificate as a copy of the private key; the certificate contains the public key and identity details. Correct by naming the public key.
- Believing that public keys must be kept private: Public keys are intended for public distribution and can be freely published; only private keys must remain strictly confidential.
- Assuming firewalls detect and remove malware: Firewalls monitor and control network traffic based on transmission rules and port access, but they generally do not scan file contents for viruses or malicious payloads; this is the role of anti-malware software.
- Confusing viruses with worms: A virus requires a host file and human intervention (such as running an infected executable) to replicate, whereas a worm is a standalone self-replicating program that spreads across networks autonomously without user interaction.
Revision Plan
- 1Day 1-2: Master cryptographic fundamentals — compare symmetric and asymmetric encryption, key exchange problems, and computational overheads.
- 2Day 3-4: Diagram and write out step-by-step procedures for digital signatures, hashing algorithms, and digital certificates issued by CAs.
- 3Day 5-6: Study network perimeter defences, comparing packet filtering, stateful inspection, and proxy servers.
- 4Day 7: Review cyber attack vectors (malware types, phishing, pharming, DoS/DDoS) and test knowledge with past AQA paper scenario questions.
Exam Question Types
- 📋Step-by-step sequence questions: Detail the precise chronological sequence of key usages in SSL/TLS handshakes, digital signature verification, or encrypted email transmission.
- 📋Comparative analysis: Compare symmetric and asymmetric encryption in terms of speed, resource utilisation, key distribution, and typical practical use cases.
- 📋Contextual security evaluation: 6 to 9 mark scenarios evaluating network vulnerability to DDoS, eavesdropping, or man-in-the-middle attacks and recommending technical solutions.
Command Word Expectations (AQA)
Set out the mathematical or logical reasons how or why a security mechanism works. Marks are awarded for detailed step-by-step links (e.g. hashing -> encrypting with private key -> comparing hashes).
Identify specific technical similarities and differences between two security technologies (e.g. symmetric vs asymmetric encryption), structuring points around metrics like speed, key management, and security.
Explore multiple perspectives on a security problem or mitigation strategy, examining trade-offs such as computational overhead, user convenience, and defence efficacy before providing a justified conclusion.
How Students Lose Marks (Examiner Pitfalls)
Step-by-Step Worked Solutions
Question: Alice wants to send a confidential contract to Bob across an insecure network and ensure non-repudiation. Describe the step-by-step process of using asymmetric encryption, hashing, and digital signatures to achieve both confidentiality and integrity.
- 1.Step 1: Alice creates the contract and generates a fixed-length cryptographic hash digest of the document using a hashing algorithm (e.g. SHA-256).
- 2.Step 2: Alice encrypts the hash digest with her own private key to create the digital signature, providing authentication and non-repudiation.
- 3.Step 3: Alice appends the digital signature to the contract and encrypts both the contract and signature using Bob's public key to ensure confidentiality.
- 4.Step 4: Bob receives the cipher text and decrypts it using his own private key, revealing the plaintext contract and the digital signature.
- 5.Step 5: Bob decrypts the digital signature using Alice's public key to recover Alice's original hash digest.
- 6.Step 6: Bob hashes the decrypted contract independently using the same hashing algorithm and compares his calculated hash to the decrypted hash digest. If they match, integrity is confirmed and the sender's identity is verified.
Question: Explain how a Distributed Denial of Service (DDoS) attack operates and discuss why it is significantly harder to mitigate than a standard Denial of Service (DoS) attack.
- 1.Step 1: Define the mechanism of a DDoS attack. A malicious actor infects multiple internet-connected devices (often IoT devices or compromised hosts) with malware, creating a 'botnet' under the control of a command-and-control server.
- 2.Step 2: Explain the execution. The attacker commands the zombie devices in the botnet to simultaneously flood the target server with excessive requests (e.g. SYN floods or UDP floods), consuming bandwidth, memory, or CPU resources until the server crashes or becomes unresponsive to legitimate users.
- 3.Step 3: Contrast with DoS. In a standard DoS attack, traffic originates from a single IP address or host, which can be quickly detected and blocked using basic firewall IP filtering rules.
- 4.Step 4: Explain mitigation difficulty. In a DDoS attack, malicious traffic originates from thousands of geographically distributed and legitimate-looking IP addresses. Simple IP blacklisting is ineffective as it risks blocking genuine users, and the sheer volume of distributed traffic can overwhelm ISP-level upstream links before reaching local firewalls.