Prof. Dr. Larry AdamsAcademic, Author & Researcher
Cybersecurity & Digital Risk Management · Book 1

Foundations of Cybersecurity and Digital Safety

Digital Literacy, Core Security Principles and Personal Protection

Dr. Lance Adams and Prof. Dr. Larry Adams

Free to read online. For a copy of this book, or to quote, highlight or reproduce any part of it, please request permission through the contact page beforehand.

Publication and use note

This document is an educational manuscript draft prepared for development, teaching and professional discussion. It is not legal advice, a guarantee of security, or a substitute for a qualified assessment of a specific environment. Technical configurations, product features, standards editions and legal obligations change. Before publication or operational use, verify all claims against current authoritative documentation and the relevant jurisdiction. Practical activities must be conducted only in authorised, controlled environments.

Preface

This volume forms part of the Cybersecurity & Digital Risk Management collection. It is designed to connect clear conceptual explanations with practical decisions, professional judgement and reflective learning. The aim is to help readers understand not only which controls may be useful, but why they matter, where they can fail and how their effectiveness can be evaluated.

Build a practical understanding of cybersecurity and help readers develop reliable habits for protecting devices, accounts, information and digital relationships.

Intended readership

The material is intended for students, educators, IT and security practitioners, managers, auditors, entrepreneurs and interested readers. Readers should adapt examples to their own context and seek specialist advice where technical, contractual or legal consequences are significant.

Learning outcomes

  • Explain confidentiality, integrity and availability and apply them to everyday situations.
  • Recognise common attack patterns including phishing, credential theft, malware and social engineering.
  • Strengthen account, device, browsing, backup and home-network security.
  • Assess personal digital risks and create a proportionate improvement plan.
  • Apply ethical, privacy-aware and responsible digital behaviour.

How to use this book

Read the chapters in sequence for a structured introduction, or use individual chapters as workshop material. Complete the practical tasks in a lab or with fictional data. For group learning, ask participants to state assumptions, compare alternative controls and explain the trade-offs between security, usability, cost, privacy and availability.

Contents

  • Chapter 1: Understanding Cybersecurity
  • Chapter 2: How Digital Threats Evolve
  • Chapter 3: Digital Identity, Passwords and Passkeys
  • Chapter 4: Phishing and Social Engineering
  • Chapter 5: Device Security and Safe Browsing
  • Chapter 6: Malware, Ransomware and Backups
  • Chapter 7: Privacy, Digital Citizenship and Personal Cyber Hygiene
  • Chapter 8: Building a Personal Security Plan
  • Applied case study
  • Practical activities and assessment
  • Glossary
  • Selected references and further reading

Chapter 1: Understanding Cybersecurity

Cybersecurity is the practice of protecting systems, services, networks and information against unauthorised access, disruption, alteration and destruction. It includes technology, people, processes and governance. A secure device is not enough if an account is poorly protected, a recovery email is exposed, or a user is persuaded to approve a fraudulent request. Security therefore works best as a layered system rather than as one product or setting.

The confidentiality, integrity and availability (CIA) triad provides a useful starting model. Confidentiality means information is disclosed only to authorised people; integrity means information remains accurate and trustworthy; availability means systems and data can be used when needed. A university, for example, must keep student records private, prevent unauthorised grade changes and keep learning platforms available during examinations. These goals can conflict, so security decisions should consider the purpose and context of the information.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on understanding cybersecurity?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 2: How Digital Threats Evolve

Cyber threats change as technology, incentives and user habits change. Criminals may seek money, personal information, access to business systems, influence or disruption. Some attacks are highly automated, while others rely on patient impersonation and manipulation. A threat is not the same as a vulnerability: a threat is a possible source of harm, while a vulnerability is a weakness that could be exploited. Risk arises when a threat can exploit a weakness and produce a meaningful impact.

A simple risk assessment asks what matters, what could go wrong, how likely it is, and how serious the consequences would be. A lost personal photo and a compromised business administrator account are not equivalent risks. Readers should prioritise likely, high-impact exposures instead of trying to eliminate every imaginable danger. Security is a continuous process: new devices, applications, jobs and travel patterns can change the risk picture.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on how digital threats evolve?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 3: Digital Identity, Passwords and Passkeys

Digital identity is the collection of accounts and attributes through which a person is recognised online. Email accounts are particularly important because they often reset passwords for many other services. Use unique passwords, preferably generated and stored by a reputable password manager. Reusing a password allows a breach at one service to endanger other accounts, even when those services are unrelated.

Multifactor authentication adds another verification factor, such as an authenticator app, security key or device prompt. Passkeys use public-key cryptography and can reduce exposure to fake sign-in pages when implemented correctly. Recovery methods deserve equal attention: a strong password does not help if an attacker controls the recovery email or phone number. Review account sessions, remove unknown devices, save recovery codes securely and avoid approving sign-in prompts that you did not initiate.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on digital identity, passwords and passkeys?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 4: Phishing and Social Engineering

Social engineering manipulates people into revealing information, transferring money, opening files or granting access. Messages may create urgency, fear, curiosity or a sense of authority. Phishing commonly arrives through email, but similar approaches occur in text messages, phone calls, collaboration tools and social media. A message can appear convincing because criminals copy branding, use publicly available details and exploit real business processes.

Pause before acting on unexpected requests. Check the sender and the destination of links, but remember that display names and caller IDs can be spoofed. Verify payment changes and sensitive requests using a separate, trusted channel—not the phone number or link supplied in the suspicious message. Report suspected phishing through the organisation's approved process. If you have already clicked or shared credentials, change the affected password from a trusted device, revoke suspicious sessions and contact the relevant service or security team promptly.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on phishing and social engineering?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 5: Device Security and Safe Browsing

Devices should receive supported operating-system and application updates, use screen locks, encrypt storage where available and run only software from trusted sources. Remove applications that are no longer needed and review their permissions. Administrative access should be used only when necessary. A device used for banking or work deserves stronger protection than an old device used only for offline reading, although every connected device can create a route into a network.

Websites may use encryption while still being fraudulent; a padlock or HTTPS connection does not prove that a business is trustworthy. Avoid downloading unexpected attachments or installing software prompted by pop-up warnings. On public Wi-Fi, prefer trusted services and encrypted connections, disable unnecessary sharing, avoid unknown captive portals and use a trusted mobile connection for especially sensitive tasks when practical. A VPN can protect some network traffic from local observers, but it does not make a malicious website safe or prevent account compromise.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on device security and safe browsing?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 6: Malware, Ransomware and Backups

Malware is software designed to perform harmful or unauthorised actions. It may steal credentials, spy on activity, disrupt operations or encrypt files. Ransomware often combines data encryption with threats to publish stolen information. Common entry routes include malicious attachments, compromised credentials, unpatched systems and unsafe software. Warning signs may include unusual device behaviour, unexpected security alerts, unfamiliar applications or files becoming inaccessible.

Backups are valuable only if they can be restored. Keep more than one copy of important data, use a backup that is not continuously writable from the everyday device, protect backup credentials and test restoration periodically. If ransomware is suspected, disconnect the affected device from networks where safe to do so, preserve relevant details and contact qualified support. Do not rush to wipe a device if evidence may be needed. Payment does not guarantee recovery or deletion of stolen data.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on malware, ransomware and backups?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 7: Privacy, Digital Citizenship and Personal Cyber Hygiene

Privacy is not simply secrecy; it concerns appropriate collection, use, sharing and retention of information. Review social-media visibility, location sharing, app permissions and old accounts. Be cautious about publishing travel plans, identity documents, school details or answers that could expose account-recovery information. Consent and context matter: information shared with one audience may be copied to another without permission.

Good digital citizenship includes respectful communication, checking information before forwarding it, protecting other people's data and reporting abuse. A monthly cyber-hygiene routine can include installing updates, reviewing account activity, checking backups, removing unused apps and examining privacy settings. Small habits are effective when they are repeatable and supported by simple checklists.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on privacy, digital citizenship and personal cyber hygiene?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Chapter 8: Building a Personal Security Plan

A personal security plan starts with important assets: accounts, devices, documents, photographs, financial services and work or study records. Identify the most serious plausible threats and the controls that reduce them. Prioritise unique passwords, multifactor authentication, updates, backups and reliable recovery methods before buying complex tools. Record what to do if a phone is lost, an account is hijacked or a payment request appears fraudulent.

Security plans should be usable under stress. Keep support contacts available through a trusted channel, know how to freeze payment cards or report identity theft, and avoid putting recovery secrets in an unprotected document. Review the plan when circumstances change. The aim is not perfect protection; it is to make common attacks harder, detect problems sooner and reduce the damage when something goes wrong.

Chapter application

Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.

Reflection questions

  • What are the three most important ideas from this chapter on building a personal security plan?
  • Which assumptions would need to be verified before applying this guidance in a real environment?
  • What evidence would demonstrate that the proposed controls are operating effectively?

Integrated case study

A student receives a message apparently from the university IT team saying that their mailbox will be closed in 20 minutes unless they sign in through a supplied link. The page looks familiar and asks for a password and one-time code. A safe response is to avoid the link, check the request through the university's known helpdesk channel, report the message and inspect account activity if credentials were entered.

Case study analysis

  • Identify the important assets, stakeholders and business objectives.
  • Describe the likely threat scenarios and the evidence needed to assess them.
  • Recommend immediate actions and longer-term preventive improvements.
  • Explain how the organisation should document decisions and measure effectiveness.
  • Identify privacy, legal, ethical or operational considerations that require specialist review.

Practical activities and assessment

  • Complete a personal cyber-safety audit for five important accounts and three devices.
  • Create a phishing checklist and use it to assess three sample messages.
  • Document a backup and account-recovery plan without recording passwords or secret codes.
  • Prepare a 30-day improvement plan ranked by risk and effort.

Suggested assessment rubric

Glossary of key terms

Asset: Something of value to an individual or organisation, including data, services, identities and systems.

Authentication: A process used to establish that a user, device or service is the entity it claims to be.

Confidentiality: Protection against unauthorised disclosure of information.

Control: A safeguard or process intended to modify risk.

Incident: An event that compromises or threatens the security or operation of systems, services or information.

Least privilege: The principle of granting only the access and permissions needed for a defined task.

Residual risk: Risk remaining after controls and treatment decisions are considered.

Resilience: The ability to anticipate, withstand, recover from and adapt to disruption.

Threat: A potential cause of unwanted harm.

Vulnerability: A weakness that could be exploited or otherwise contribute to harm.

Selected standards and further reading

The following are starting points for verification and further study. Confirm the current edition, applicability and licensing conditions before quoting or relying on a standard.

  • National Institute of Standards and Technology (NIST). Cybersecurity Framework (CSF) 2.0. NIST, 2024.
  • International Organization for Standardization. ISO/IEC 27001, Information security management systems — Requirements. Consult the current edition.
  • International Organization for Standardization. ISO/IEC 27002, Information security controls. Consult the current edition.
  • International Organization for Standardization. ISO 31000, Risk management — Guidelines. Consult the current edition.
  • Center for Internet Security. CIS Critical Security Controls. Consult the current version.
  • National Institute of Standards and Technology. NIST Privacy Framework. Consult the current version.
  • OWASP Foundation. OWASP Top 10 and other relevant application-security guidance. Consult the current version.
  • National Institute of Standards and Technology. Relevant SP 800-series publications on security, privacy, incident response and contingency planning; verify the publication status and current revision.

Editorial development checklist

  • Verify every technical claim and update examples to reflect current practice.
  • Add properly sourced APA 7 in-text citations throughout the manuscript before publication.
  • Review jurisdiction-specific legal and regulatory sections with qualified advisers.
  • Add diagrams, figures and accessible alt text where they materially aid understanding.
  • Conduct technical peer review and copy-editing; validate all exercises in authorised lab settings.
  • Add index, acknowledgements, final copyright details and publisher information when known.