Know and understand minimising the potential danger of using online gaming including not using real names, not giving out personal or financial data

Topic 8 – Safety and Security (IGCSE ICT 0417)

Objective

Know and understand how to minimise the potential danger of using online gaming, including:

• Physical safety when using ICT equipment.
• e‑Safety – protecting personal and financial data.
• Security of data – recognising threats and applying appropriate protection mechanisms.
• How these concepts relate to the Cambridge IGCSE ICT assessment objectives (AO1, AO2, AO3).

Why Safety Matters in Online Gaming

Online games connect millions of players worldwide, offering entertainment and social interaction. At the same time they expose users to physical hazards, technical vulnerabilities and personal‑data risks. Understanding these risks enables learners to protect themselves, their devices and their personal information – a requirement of syllabus sections 8.2 (e‑Safety) and 8.3 (Security of data).

1. Physical Safety When Using ICT Equipment (Syllabus 8.2)

• Tripping or crushing hazards – loose cables, power strips or accessories on the floor can cause falls or injuries.
• Over‑heating of equipment – laptops, consoles or monitors left on for long periods become hot; ensure ventilation and never cover vents.
• Electrical safety – use surge protectors, plug devices into correctly rated sockets and never handle equipment with wet hands.
• Ergonomic posture – sit upright, keep the screen at eye level and take a 5‑minute break every hour to avoid eye strain and musculoskeletal problems.
• Battery safety – charge controllers, headsets or mobile devices on a stable surface and unplug once fully charged.

Exam tip (AO2): When answering a question on physical safety, cite at least two of the above hazards and explain why each is relevant to a gamer’s environment.

2. e‑Safety – Personal Data & Data Protection (Syllabus 8.2)

What counts as personal data?

• Personal data: any information that can identify an individual – name, address, email, date of birth, school, avatar image, gamer‑tag, etc.
• Sensitive data: details that could cause discrimination or harm if disclosed – health information, ethnicity, religion, financial details.

Key GDPR‑style principles (exam‑relevant AO1)

1. Lawful, fair and transparent processing
2. Purpose limitation
3. Data minimisation
4. Accuracy
5. Storage limitation
6. Integrity & confidentiality
7. Accountability

These principles underpin the Data Protection Act 2018 (UK) and similar legislation worldwide. In a gaming context, they mean you must only share the minimum information needed, keep it secure and never use it for unauthorised purposes.

Why avatars, gamer‑tags and chat logs are personal data

• They can be linked to a real‑world identity through search engines or social media.
• Sharing them without consent breaches data‑protection principles and can lead to identity theft, cyber‑bullying or targeted scams.

3. Common Threats to Data & Devices (Syllabus 8.3)

4. Protection Mechanisms (Syllabus 8.3)

• User‑ID / Password – unique login name plus a strong password.
• Two‑Factor Authentication (2FA) – authenticator app, SMS code or hardware token.
• Biometrics – fingerprint or facial recognition on consoles and mobile devices.
• Encryption & SSL/TLS – all web‑based purchases and account log‑ins should use https:// (SSL/TLS) to encrypt data in transit.
• Digital certificates – the game store’s server presents a trusted certificate to prove its identity.
• Firewalls – enable the operating‑system or router firewall to block unauthorised inbound connections.
• Anti‑malware software – keep real‑time protection active and run regular scans.
• Secure payment methods – use PayPal, virtual prepaid cards or platform‑managed wallets instead of storing raw card numbers.
• Regular updates – apply patches for the game client, operating system and security software promptly.
• Back‑ups – store game saves and important files on an external drive or cloud service with versioning.

5. Practical Safety Practices for Gamers (AO2 – Apply)

1. Create a pseudonym – a gaming name that contains no part of your real name, birth date or school.
2. Keep personal data private – never post address, phone number, school, or personal photos in public chat or profiles.
3. Use strong, unique passwords – at least 12 characters, mix of upper‑/lower‑case, numbers and symbols; change them every 6‑12 months.
4. Enable 2FA or biometrics wherever the platform offers it.
5. Guard financial information – use prepaid or platform‑managed payment methods; never share card details with other players.
6. Review and tighten privacy settings – set profiles to “Friends only”, disable location sharing, and limit who can send you messages.
7. Download only from official sources – the game’s own store, Google Play, Apple App Store or the console’s marketplace.
8. Keep anti‑malware and the OS up to date – enable automatic updates.
9. Use a firewall – keep the built‑in Windows/macOS firewall active, or configure your router’s firewall.
10. Take regular breaks and maintain ergonomics – 5‑minute break every hour, proper chair height, screen at eye level.
11. Report and block abusive or suspicious users – use the in‑game reporting tool; block the user to stop further contact.

Quick‑write (AO3): Choose two threats from the table and evaluate which would have the greatest impact on a 13‑year‑old’s gaming experience. Justify your answer using the CIA impact column.

6. Checklist for Safe Gaming (AO1 – Recall)

7. Mini‑Case Study – Designing a Safe‑Gaming Policy (Systems Life‑Cycle, Syllabus 7)

Scenario: A secondary school wants to create a policy that lets students play educational games safely on school‑provided tablets.

1. Analysis – Identify risks: physical (over‑heating tablets), e‑safety (sharing personal data), security (malware from unofficial mods).
2. Design – Draft rules: use school‑issued pseudonyms, enable 2FA, restrict app installations to the official store, set privacy to “Friends only”, schedule 5‑minute breaks every hour.
3. Implementation – Configure each tablet with a firewall, anti‑malware, and a shared password manager; distribute a step‑by‑step guide.
4. Testing – Run a pilot with a small class; monitor for incidents, check that updates install automatically, verify that privacy settings work.
5. Documentation – Produce a one‑page policy sheet, an FAQ, and a checklist for students and teachers.
6. Evaluation (AO3) – After one term, collect feedback: Did incidents of data sharing decrease? Were any devices overheating? Adjust the policy based on findings.

Exam tip (AO3): When asked to evaluate a safety solution, refer to the life‑cycle stages you have used and explain how each stage improves confidentiality, integrity or availability.

8. Audience, Copyright & File Management (Syllabus 9‑13)

• Audience awareness – Content shared in-game (avatars, screenshots, streams) should be appropriate for the age group of the audience and must not contain copyrighted material without permission.
• Copyright – Using game assets (music, images) in personal videos requires either the game’s licence permission or a fair‑use justification; otherwise it is infringement.
• File management – Store screenshots, chat logs and saved games in a clearly labelled folder hierarchy (e.g., Games → [GameName] → Screenshots). Back‑up important files to an external drive or cloud service to satisfy the “availability” aspect of data security.

9. Quick‑Check Questions (AO1–AO3)

1. List three physical hazards associated with long gaming sessions and suggest one mitigation for each. (AO1)
2. Explain why a gamer‑tag can be considered personal data under GDPR‑style legislation. (AO2)
3. Choose one threat from the table and evaluate how it could affect the confidentiality, integrity and availability of a player’s account. (AO3)
4. Design a one‑page safe‑gaming checklist for a school’s tablet lab, referencing at least four protection mechanisms from section 4. (AO2)

10. Summary

• Physical safety: keep cables tidy, ensure ventilation, use surge protectors and take regular ergonomic breaks.
• e‑Safety: treat avatars, gamer‑tags and chat logs as personal data; apply GDPR‑style principles of lawfulness, purpose‑limitation, data‑minimisation, etc.
• Security threats: phishing, smishing, vishing, pharming, malware, ransomware, card fraud, identity theft, data tracking, social engineering – each impacts confidentiality, integrity or availability.
• Protection mechanisms: strong passwords, 2FA/biometrics, encryption (SSL/TLS), digital certificates, firewalls, anti‑malware, secure payments, regular updates and backups.
• Practical steps: use a pseudonym, keep personal/financial data private, enable 2FA, download only from official sources, adjust privacy settings, report abuse, and maintain healthy gaming habits.
• Systems life‑cycle can be used to design, implement and evaluate a safe‑gaming policy for any organisation.