Cyber security threats — AQA GCSE Computer Science
Cyber security threats are malicious acts or vulnerabilities that compromise the confidentiality, integrity, or availability of computer systems and data. In AQA GCSE Computer Science, threats encompass social engineering, malware, brute force attacks, denial of service, data interception, and SQL injection.
Cyber security threats explained
Penetration testing is authorised, simulated attacking of a system to find security weaknesses before a real attacker does.
Read the full explanation
A tester, often working with the system owner's permission, probes networks, software or accounts using the same kinds of techniques an attacker might use, then reports what was found. It is used to identify vulnerabilities such as weak configurations, unpatched software or poor access controls, to confirm whether existing defences actually work, and to prioritise fixes. Because it is authorised, it differs from an actual attack: the aim is to improve security, not to cause harm or steal data. A typical test might involve attempting to gain access to a system and recording how far the tester got and why. Results feed into remediation, so the organisation can patch, reconfigure or strengthen controls.
Your focus
- Define penetration testing as authorised simulated attacking of a system.
- Explain the purposes of penetration testing, including finding and fixing vulnerabilities.
- Distinguish penetration testing from a real attack and from protective software.
Which command word is this?
Set out the causes, mechanisms, or reasons behind a concept. For threats, describe how the attack works and what consequence it produces, using linking phrases like 'because' or 'which results in'.
Cyber security threats exam tips
Topic Overview
Cyber security threats represent the diverse array of digital and psychological methods used by malicious actors to compromise systems, networks, and confidential data. In AQA GCSE Computer Science (8525), students explore technical vulnerabilities such as SQL injection and malware alongside human vulnerabilities exploited through social engineering techniques.
Understanding these threats enables computer scientists to build resilient systems using effective prevention and mitigation strategies like firewalls, parameterised queries, and access control. This topic forms a foundational pillar of software engineering and network administration, bridging theoretical computer science with real-world security practices.
Key Concepts
- →Social engineering exploits human error rather than software bugs, using techniques like phishing, shoulder surfing, and pretexting.
- →Malware includes various malicious software types such as viruses (which self-replicate by attaching to host files), worms (standalone self-replicating programs), trojans (disguised as benign software), spyware, and ransomware.
- →Network-based attacks include Denial of Service (DoS/DDoS), data interception via packet sniffing or man-in-the-middle attacks, and brute force password cracking.
- →System-level vulnerabilities arise from unpatched software, weak passwords, misconfigured access rights, and unvalidated user input leading to SQL injection.
Marking Points
- Defines penetration testing as authorised, simulated attempts to find security weaknesses.
- States that it is carried out with the owner's permission, distinguishing it from a real attack.
- Explains that it identifies vulnerabilities such as weak configurations, unpatched software or poor access controls.
- Explains that results are used to fix or prioritise improvements to security.
- Applies the idea to a scenario, for example testing whether an attacker could access a network and reporting the findings.
Examiner Tips
- 💡Include the word authorised to show you understand it is permitted testing.
- 💡Give at least one concrete use, such as finding vulnerabilities so they can be fixed.
- 💡Link the test to a follow-up action, for example patching or reconfiguring the system.
- 💡Avoid generic terms like 'the computer breaks' or 'hackers steal files'; always specify the exact mechanism, such as 'encrypting data and demanding a ransom' or 'capturing unencrypted packets across a network'.
- 💡When explaining social engineering scenarios, distinguish clearly between the vector (the communication method) and the payload or objective (what the attacker wants to acquire).
- 💡Remember that mitigation questions require direct matching: parameterised queries prevent SQL injection, strong password policies and lockouts mitigate brute force, and off-site backups mitigate ransomware.
Common Mistakes
- Describing penetration testing as a real criminal attack; correction: it is authorised and intended to improve security.
- Treating it as the same as installing antivirus; correction: it is a testing activity that finds weaknesses, not protective software.
- Omitting the purpose and only describing the activity; correction: explain both what it is and what it is used for, such as finding and fixing vulnerabilities.
- Believing viruses and worms are identical: A virus requires an executable host file and human intervention to propagate, whereas a worm is a standalone program that self-replicates across networks automatically.
- Assuming all cyber attacks exploit software flaws: A significant proportion of successful security breaches exploit human psychology through social engineering rather than technical system bugs.
- Thinking anti-malware and firewalls stop SQL injection: SQL injection exploits unvalidated application inputs passing into database queries; network firewalls and standard anti-virus software do not parse or sanitise SQL logic.
Revision Plan
- 1Step 1: Create a flashcard taxonomy of all malware forms (virus, worm, trojan, spyware, adware, ransomware) highlighting their defining operational traits.
- 2Step 2: Learn social engineering vectors (phishing, blagging/pretexting, shouldering/shoulder surfing) and match each to its typical prevention method.
- 3Step 3: Trace technical attacks including SQL injection syntax, brute force password cracking, and DoS packet flooding.
- 4Step 4: Work through paired past paper questions that ask you to evaluate a scenario, identify the threat, and propose appropriate defensive mitigations.
Exam Question Types
- 📋Scenario-based threat identification: You are given a workplace scenario and must identify the threat taking place (e.g. employee looking over another's shoulder or a suspicious email).
- 📋Mechanistic explanation: Short-answer questions (2-4 marks) asking you to explain step-by-step how an attack functions (e.g. how a distributed denial of service attack overwhelms a server).
- 📋Defensive design and mitigation: Questions requiring you to justify why a specific measure (e.g. input sanitisation or multi-factor authentication) counteracts a named threat.
Command Word Expectations (AQA)
Set out the causes, mechanisms, or reasons behind a concept. For threats, describe how the attack works and what consequence it produces, using linking phrases like 'because' or 'which results in'.
Give an account of the characteristics or features of a threat or defensive tool without necessarily linking deep cause and effect.
Explore multiple perspectives or evaluate strengths, weaknesses, and broader impacts of security threats and counter-measures, usually in a structured long-response format.
How Students Lose Marks (Examiner Pitfalls)
Step-by-Step Worked Solutions
Question: An e-commerce website uses a database to store customer records. An attacker inputs "' OR '1'='1" into the username login field. Explain the type of attack being attempted, how it functions, and one method to prevent it. (4 marks)
- 1.Step 1: Identify the attack type. The input is structured SQL syntax, which indicates an SQL injection attack.
- 2.Step 2: Explain how the attack functions. The malicious SQL statement modifies the underlying query run by the database backend.
- 3.Step 3: Detail the effect of the specific code provided. The condition "'1'='1" always evaluates to true, bypassing authentication checks to grant unauthorised access or reveal data without a valid password.
- 4.Step 4: State a valid prevention method. Provide a recognised mitigation technique such as input validation, sanitisation, or using prepared statements/parameterised queries.
Question: A school network experiences a cyber incident where files on the main file server are encrypted, and a message demands payment in cryptocurrency to restore access. Identify the malware responsible and describe two measures the school should implement to minimise the disruption caused by future occurrences of this attack. (4 marks)
- 1.Step 1: Identify the malware. Malicious software that encrypts user data and demands payment for decryption is ransomware.
- 2.Step 2: Identify mitigation measure 1. Focus on recovery and data availability, specifically regular, automated backups stored offline or off-site so encrypted data can be restored without paying.
- 3.Step 3: Identify mitigation measure 2. Focus on prevention or limiting propagation, such as staff training to identify phishing emails that deliver ransomware, maintaining up-to-date anti-malware software, or applying operating system patches.