Cyber Security Fundamentals

Chapter 1
Cybersecurity Foundations and Terminology

Diploma in Cyber Security
Cyber Security Fundamentals   •   Diploma

Cybersecurity Foundations and Terminology

Introduction

Cybersecurity is the disciplined practice of protecting information, systems, networks, applications, devices, and services from unauthorized access, misuse, disruption, alteration, or destruction. It is both a technical and organizational activity. Firewalls, encryption, identity systems, and monitoring tools are important, but they cannot provide effective protection without suitable policies, trained personnel, responsible leadership, and informed users.

Modern organizations depend on digital information assets for communication, financial transactions, service delivery, decision-making, and legal compliance. A security failure can therefore cause more than technical inconvenience. It may result in financial loss, safety risks, reputational damage, regulatory penalties, privacy violations, and loss of public trust.

This chapter introduces the vocabulary and conceptual models used throughout cybersecurity. It explains the relationship between assets, threats, vulnerabilities, exploits, controls, and risk. It also examines the confidentiality, integrity, and availability (CIA) triad, which provides a fundamental way of describing security objectives.

Learning Objectives

By the end of this chapter, you should be able to:

  1. Define cybersecurity and distinguish it from information security.
  2. Identify information assets and describe their value.
  3. Explain attack surfaces, threats, vulnerabilities, exploits, and risk.
  4. Describe the confidentiality, integrity, and availability triad.
  5. Classify common cybersecurity controls and explain their purposes.
  6. Apply foundational terminology to a practical organizational scenario.
  7. Describe ethical responsibilities and typical cybersecurity career duties.

1. Cybersecurity as a Discipline

Cybersecurity concerns the protection of digital and digitally connected environments. These environments include computers, mobile devices, cloud platforms, industrial control systems, applications, databases, communication networks, and internet-connected products.

Information security is the broader discipline concerned with protecting information in any form, including paper records and spoken information. Cybersecurity focuses particularly on information and systems exposed through digital technologies and networks. In practice, the terms overlap, and many organizations use them interchangeably.

Cybersecurity has three connected dimensions:

  • People: users, administrators, managers, customers, attackers, and security professionals.
  • Processes: policies, procedures, risk assessments, incident response, auditing, and recovery.
  • Technology: hardware, software, networks, cryptography, access controls, and monitoring systems.

A technically secure system can still fail if an administrator misconfigures it, a user discloses credentials, or an organization has no process for responding to an incident. Security is therefore a system of coordinated safeguards rather than a single product.

Security goals and business context

Security decisions should support legitimate organizational objectives. Excessive controls can reduce usability and productivity, while insufficient controls can expose important assets. For example, requiring multiple approvals for every low-risk action may delay routine work, whereas allowing unrestricted administrative access may create unacceptable exposure.

Cybersecurity professionals must therefore understand both technical risk and business impact. They should ask:

  • What must be protected?
  • From whom or from what?
  • What would happen if protection failed?
  • Which safeguards are proportionate and practical?
  • How will the organization detect, respond to, and recover from failure?

2. Information Assets

An asset is something valuable to an individual or organization. An information asset is information or a resource that supports the collection, processing, storage, transmission, or use of information.

Examples include:

  • customer records and payment information;
  • employee identity and payroll data;
  • intellectual property and research results;
  • databases, files, and backups;
  • laptops, servers, routers, and mobile devices;
  • cloud accounts, software applications, and application programming interfaces;
  • credentials, encryption keys, and digital certificates;
  • business processes and the availability of online services;
  • physical facilities supporting information systems.

Assets have different values and protection requirements. A public marketing brochure may require integrity protection but little confidentiality. A database containing health records requires strong confidentiality, integrity, and availability safeguards. Asset identification is therefore a necessary starting point for risk management.

An asset register commonly records the owner, location, classification, dependencies, responsible administrator, retention period, and required security controls. Ownership does not necessarily mean legal ownership. It usually means accountability for deciding how an asset is used and protected.

Data classification

Organizations often classify information according to sensitivity and business impact. A simple classification scheme might include:

ClassificationTypical meaningExample protection
PublicApproved for general disclosureIntegrity checks and version control
InternalIntended for authorized personnelAuthentication and access restrictions
ConfidentialDisclosure could harm the organization or individualsEncryption, least privilege, monitoring
RestrictedHighly sensitive or legally protectedStrong access control, encryption, auditing, segregation

Classification must be supported by handling rules. Labelling information “confidential” without controlling access, transmission, storage, and disposal provides little protection.

3. The CIA Triad

The CIA triad represents three central security objectives: confidentiality, integrity, and availability. It is a conceptual model, not a complete security standard. Other objectives, such as authenticity, accountability, privacy, and non-repudiation, may also be required.

Confidentiality

Confidentiality means preventing information from being disclosed to unauthorized people, processes, or systems. Controls supporting confidentiality include:

  • authentication and authorization;
  • encryption in storage and transit;
  • secure disposal;
  • network segmentation;
  • data-loss prevention;
  • privacy policies and staff training.

Confidentiality is not the same as secrecy in every situation. Some information must be shared, but only with authorized recipients and for authorized purposes. A failure of confidentiality is often called a data disclosure or data breach.

Integrity

Integrity means maintaining the accuracy, completeness, consistency, and trustworthiness of information and systems. Integrity protection helps ensure that data is not changed improperly, whether by an attacker, software defect, operator error, or hardware failure.

Common integrity controls include hashes, digital signatures, access restrictions, input validation, transaction controls, change management, version history, and independent verification. A hash can indicate that content has changed, but it does not by itself prove who created the content or whether the original content was trustworthy.

Availability

Availability means that authorized users can access information and services when required. Availability depends on functioning systems, reliable networks, adequate capacity, power, maintenance, and effective recovery arrangements.

Availability controls include redundancy, backups, fault tolerance, preventive maintenance, capacity planning, disaster recovery, and denial-of-service protection. A service can be available but insecure, or secure but unavailable. Effective security must balance both conditions.

Security objectives can conflict

Security objectives are not always maximized simultaneously. Strong encryption may increase processing requirements. Extensive access checks may reduce convenience. A highly redundant service may cost more to operate. Security professionals must assess the context and select controls according to risk, legal duties, operational requirements, and organizational priorities.

4. Attack Surface and Exposure

An attack surface is the collection of points through which an unauthorized party could attempt to enter, interact with, influence, or disrupt an environment. It includes technical, human, physical, and supply-chain elements.

Examples include:

  • internet-facing web servers and remote-access services;
  • open network ports and exposed APIs;
  • user accounts, passwords, and privileged identities;
  • email and messaging systems;
  • mobile devices and wireless networks;
  • third-party software and cloud services;
  • physical entrances, removable media, and unattended equipment;
  • employees who may be deceived through social engineering.

The attack surface changes continuously. New software, temporary accounts, remote workers, software updates, acquired companies, and supplier connections can increase exposure. Attack-surface management therefore requires asset discovery, secure configuration, vulnerability management, identity governance, and continuous monitoring.

An attack vector is a path or method used to conduct an attack. Phishing, exploitation of a vulnerable web application, theft of credentials, and physical access are examples of attack vectors. Attack surface describes possible exposure; attack vector describes how that exposure may be used.

5. Threats, Vulnerabilities, Exploits, and Attacks

These terms are related but should not be treated as synonyms.

Threat

A threat is a potential cause of harm. Threats may be intentional or accidental and may originate inside or outside an organization.

Examples include:

  • cybercriminal groups seeking financial gain;
  • insiders misusing legitimate access;
  • state-sponsored operations;
  • competitors or activists;
  • malware and automated scanning;
  • accidental deletion or misconfiguration;
  • fire, flood, power failure, or equipment breakdown.

A threat actor is the person, group, or system capable of carrying out a threat. A threat event is an occurrence that could result in harm.

Vulnerability

A vulnerability is a weakness that could be used to compromise an asset or security objective. Vulnerabilities may exist in software, hardware, configuration, procedures, architecture, or human practices.

Examples include an unpatched application, excessive privileges, weak passwords, insecure default settings, missing backups, inadequate physical access control, or unclear incident procedures. A vulnerability does not automatically mean that an incident will occur. Its significance depends on exposure, likelihood of exploitation, the capabilities of potential attackers, and the resulting impact.

Exploit

An exploit is a technique, code, sequence of actions, or tool that takes advantage of a vulnerability. An exploit may be publicly available, privately developed, automated, or carried out manually. The existence of an exploit can increase the likelihood associated with a vulnerability.

Attack and incident

An attack is a deliberate attempt to compromise confidentiality, integrity, availability, or another security objective. A security incident is an event that actually or potentially jeopardizes information or systems. Not every incident is a successful attack; for example, a suspicious login attempt may be an incident even if access was blocked.

A breach generally refers to a confirmed compromise, especially unauthorized access to or disclosure of protected information. Organizations should define these terms in their policies because legal and regulatory meanings can vary.

6. Risk and Risk Management

Risk is the possibility that a threat will exploit a vulnerability and cause harm to an asset or organization. Risk assessment commonly considers likelihood and impact. A simple conceptual relationship is:

Risk ≈ Likelihood × Impact

Here, likelihood describes the chance or plausibility of an adverse event, and impact describes the magnitude of its consequences. This expression is a decision-making model, not a universal physical law. Numerical scores are meaningful only when the scales, assumptions, and assessment method are defined consistently.

For example, suppose an organization rates likelihood from 1 to 5 and impact from 1 to 5. If a ransomware event is rated likelihood 4 and impact 5, a relative risk score is:

4 × 5 = 20

The score of 20 has meaning only within that organization’s rating scheme. It does not mean that the event has a 20 percent probability, nor can it be compared automatically with a score produced using different definitions.

Risk treatment

Risk management includes identifying, analysing, evaluating, treating, and monitoring risk. Common treatment options are:

  • Avoid: discontinue the activity creating unacceptable exposure.
  • Reduce or modify: implement controls to lower likelihood or impact.
  • Transfer or share: use insurance, contracts, or outsourcing arrangements, while recognizing that accountability may remain with the organization.
  • Accept: consciously retain the risk when it is within approved tolerance.

Risk acceptance should be informed and documented. Ignoring a risk is not the same as accepting it responsibly.

Inherent and residual risk

Inherent risk is the level of risk before additional controls are applied. Residual risk is the risk remaining after controls are implemented. Controls rarely eliminate risk completely. They may fail, be bypassed, become outdated, or introduce new dependencies.

7. Security Controls

A security control is a safeguard or countermeasure designed to prevent, detect, correct, deter, or compensate for an undesirable event.

Controls can be classified by their function:

Control typePurposeExample
PreventiveReduce the chance of an incidentMulti-factor authentication
DetectiveIdentify events or weaknessesSecurity monitoring and alerts
CorrectiveRestore or correct conditionsMalware removal and patching
DeterrentDiscourage harmful behaviourWarning notices and sanctions
RecoveryRestore services and dataTested backups and disaster recovery
CompensatingProvide alternative protectionAdditional monitoring when a legacy system cannot support modern authentication

Controls can also be administrative, technical, or physical. Administrative controls include policies, training, risk assessments, and contracts. Technical controls include encryption, firewalls, endpoint protection, and access systems. Physical controls include locks, guards, cameras, barriers, and environmental protections.

Foundational control principles

Least privilege gives users and processes only the access needed for legitimate tasks. Separation of duties divides important responsibilities so that one person cannot complete a sensitive process without oversight. Defense in depth uses multiple layers of protection so that failure of one control does not expose the entire environment. Secure by design incorporates security requirements during architecture and development rather than treating security as a late addition.

Other important practices include secure defaults, regular patching, strong identity management, network segmentation, logging, backup testing, vulnerability scanning, configuration management, and incident-response exercises.

8. A Practical Security Lifecycle

A useful operational lifecycle consists of the following activities:

  1. Identify: discover assets, owners, dependencies, threats, and vulnerabilities.
  2. Protect: implement policies, safeguards, training, and secure configurations.
  3. Detect: monitor systems and investigate unusual activity.
  4. Respond: contain incidents, communicate appropriately, and remove causes.
  5. Recover: restore normal operations, validate systems, and improve controls.

These activities are continuous rather than strictly linear. Lessons from an incident may change asset inventories, controls, training, and risk assessments. Documentation is essential because it supports consistency, accountability, auditability, and knowledge transfer.

9. Illustrative Case Study: Regional Clinic Ransomware Event

Background

A regional clinic stores patient records in a cloud-hosted application. Staff access the application from clinic offices and remotely. The clinic also uses email, a file-sharing service, and several medical devices connected to its internal network.

Problem

An employee receives a convincing message that appears to come from a supplier. After entering credentials into a fraudulent website, the employee’s account is used to access email and cloud files. The attacker deploys ransomware on several workstations and encrypts a shared file repository. Appointment scheduling is disrupted.

Analysis

The clinic’s assets include patient information, appointment data, clinical systems, staff identities, medical devices, and service availability. The attack surface includes email, remote access, cloud accounts, endpoints, and supplier communications.

Relevant vulnerabilities include insufficient phishing resistance, lack of phishing-resistant multi-factor authentication for administrators, excessive access permissions, inadequate network segmentation, and backups that have not been tested recently. The threat is a financially motivated criminal group. The exploit is the use of stolen credentials and a weakness in access controls; the broader attack includes credential theft, unauthorized access, and ransomware deployment.

The incident affects all three CIA objectives:

  • Confidentiality: email and files may have been viewed or copied.
  • Integrity: files and system configurations were altered.
  • Availability: scheduling and file access were interrupted.

Approach and solution

The clinic isolates affected devices, disables compromised accounts, preserves logs, contacts its incident-response provider, and informs relevant leadership and legal advisers. It verifies the scope of the compromise before restoring systems. It then implements phishing-resistant multi-factor authentication for privileged users, reduces unnecessary permissions, segments medical devices, improves email filtering, establishes immutable and regularly tested backups, and conducts role-based staff training.

Outcome

The clinic restores essential services from verified backups and improves its recovery procedures. The event is reported where required by applicable law and contractual obligations. A post-incident review identifies additional improvements, including supplier verification and more frequent access reviews.

Learning points

  1. A user action can expose highly valuable assets when identity controls are weak.
  2. Availability planning must include tested recovery, not merely backup creation.
  3. Security responsibilities cross technical, managerial, legal, and clinical roles.
  4. Risk assessment should consider dependencies and the consequences of service interruption.
  5. Incident response should preserve evidence while restoring essential services.

10. Professional Responsibilities and Career Roles

Cybersecurity professionals have responsibilities to their organizations, users, clients, colleagues, and the wider public. They should protect information, respect privacy, maintain competence, report risks honestly, avoid unauthorized access, preserve evidence, and follow applicable law and professional codes.

Common diploma-level roles include:

  • Security operations analyst: monitors alerts, investigates events, and escalates incidents.
  • Help-desk or identity technician: manages accounts, authentication, access requests, and user support.
  • Junior vulnerability analyst: performs scanning, validates findings, tracks remediation, and prepares reports.
  • Network or systems administrator: configures systems securely, applies updates, and maintains logs and backups.
  • Incident-response assistant: supports containment, evidence handling, documentation, and recovery.
  • Governance, risk, and compliance assistant: maintains policies, risk registers, control evidence, and audit records.

Professional conduct requires authorization. Security testing must have a defined scope, written permission, agreed methods, and procedures for reporting findings. Discovering a vulnerability does not grant permission to exploit it. Confidential information encountered during work must be protected and disclosed only through authorized channels.

Good practitioners also communicate clearly. A technically correct report that does not explain business impact, affected assets, evidence, confidence, and recommended action may not support effective decisions.

11. Governance, Law, Ethics, and Contemporary Developments

Cybersecurity operates within legal and regulatory environments involving privacy, records retention, breach notification, critical infrastructure, intellectual property, and computer misuse. Requirements differ by jurisdiction and sector. Professionals should not assume that a technically possible action is legally permissible.

Privacy is related to confidentiality but is broader. Confidentiality concerns unauthorized disclosure; privacy concerns the appropriate collection, use, sharing, retention, and disposal of information about individuals. Data minimization, purpose limitation, transparency, and secure deletion support responsible privacy practices.

Cloud computing, remote work, mobile devices, software supply chains, and artificial intelligence have expanded the attack surface. Artificial intelligence can assist defenders with alert triage, anomaly detection, summarization, and code review. It can also help attackers produce convincing phishing content, automate reconnaissance, or generate malicious code. AI outputs require human validation because they may be inaccurate, biased, insecure, or based on unauthorized data.

Contemporary best practice emphasizes identity-centric security, zero-trust principles, secure software development, continuous asset visibility, supplier risk management, resilience, and tested recovery. Zero trust does not mean that no users or devices are trusted; it means that access decisions should be continuously evaluated using identity, device, context, and policy rather than relying solely on network location.

Chapter Summary

Cybersecurity protects information, systems, networks, devices, and services from unauthorized or harmful actions. Its success depends on people, processes, and technology. Information assets include data, systems, credentials, services, and supporting facilities, each with different values and protection requirements.

The attack surface is the set of possible exposure points, while an attack vector is a method of using that exposure. A threat is a potential cause of harm, a vulnerability is a weakness, an exploit uses that weakness, and an attack is an attempt to compromise security. Risk represents the possibility and consequence of harm; it is assessed and treated through controls, monitoring, and informed decisions.

The CIA triad—confidentiality, integrity, and availability—provides a foundational model for security objectives. Controls may be preventive, detective, corrective, deterrent, recovery, or compensating, and may be administrative, technical, or physical. Effective cybersecurity uses defense in depth, least privilege, separation of duties, secure design, tested backups, and continuous improvement.

Cybersecurity professionals must work ethically, respect authorization and privacy, communicate risks accurately, and understand the operational and legal consequences of security decisions.

Key Terms

Asset: Something valuable that requires protection.

Attack surface: The collection of points through which an environment may be exposed to attack.

Attack vector: A path or method used to conduct an attack.

Availability: The property that authorized users can access information and services when needed.

Breach: A confirmed compromise, often involving unauthorized access to protected information.

CIA triad: The model of confidentiality, integrity, and availability.

Confidentiality: Protection against unauthorized disclosure.

Control: A safeguard or countermeasure used to manage security risk.

Exploit: A technique, code, or action that takes advantage of a vulnerability.

Incident: An event that actually or potentially jeopardizes information or systems.

Integrity: The accuracy, completeness, consistency, and trustworthiness of information.

Least privilege: Providing only the access necessary for an authorized task.

Residual risk: Risk remaining after controls are applied.

Risk: The possibility that a threat will exploit a vulnerability and cause harm.

Security by design: Incorporating security requirements throughout system design and development.

Threat: A potential cause of harm.

Threat actor: A person, group, or system capable of carrying out a threat.

Vulnerability: A weakness that could be used to compromise an asset or security objective.

Zero trust: An approach that continuously evaluates access rather than automatically trusting users or devices based on network location.

Review Questions

Short Answer Questions

  1. Define cybersecurity and explain why it involves more than technology.
  2. What is an information asset? Give three examples.
  3. Distinguish between a threat, vulnerability, exploit, and attack.
  4. What are the three elements of the CIA triad?
  5. Explain the principle of least privilege.

Long Answer Questions

  1. Explain how confidentiality, integrity, and availability apply to an online banking service.
  2. Describe the relationship between attack surface, attack vector, and vulnerability.
  3. Compare preventive, detective, corrective, and recovery controls, giving an example of each.
  4. Explain the risk-management options of avoidance, reduction, transfer, and acceptance.
  5. Discuss why cybersecurity requires cooperation between technical staff, managers, users, legal advisers, and suppliers.

Analytical / Application Questions

  1. A college leaves an internet-facing server unpatched for six months. Identify the asset, threat, vulnerability, possible exploit, affected CIA objectives, and suitable controls.
  2. An organization rates a threat’s likelihood as 3 and impact as 4 on defined five-point scales. Calculate its relative risk score using Risk ≈ Likelihood × Impact, and explain why the score is not a percentage probability.
  3. Design a layered response to a phishing incident involving stolen employee credentials. Include preventive, detective, corrective, and recovery controls.

Multiple Choice Questions with Answers

Question 1

Which statement best describes confidentiality?

A. Ensuring systems are available at all times

B. Preventing unauthorized disclosure of information

C. Ensuring data is accurate and complete

D. Recording every system change

Correct Answer: B. Preventing unauthorized disclosure of information

Question 2

Which item is an information asset?

A. A customer database

B. An attacker’s exploit only

C. A random internet scan

D. An unverified rumour

Correct Answer: A. A customer database

Question 3

What is a vulnerability?

A. A potential cause of harm

B. A weakness that may be exploited

C. A completed recovery process

D. An approved security policy

Correct Answer: B. A weakness that may be exploited

Question 4

What is an attack vector?

A. The value assigned to an asset

B. A method or path used to conduct an attack

C. The remaining risk after controls

D. A type of backup

Correct Answer: B. A method or path used to conduct an attack

Question 5

Which control is primarily detective?

A. Multi-factor authentication

B. Security monitoring and alerting

C. A firewall rule blocking traffic

D. A tested backup

Correct Answer: B. Security monitoring and alerting

Question 6

An organization rates likelihood as 3 and impact as 4. Using Risk ≈ Likelihood × Impact, what is the relative score?

A. 7

B. 9

C. 12

D. 16

Correct Answer: C. 12

Question 7

Which principle gives users only the access needed for their duties?

A. Defense in depth

B. Least privilege

C. Open access

D. Non-repudiation

Correct Answer: B. Least privilege

Question 8

Which CIA objective is most directly affected when ransomware prevents access to files?

A. Availability

B. Confidentiality

C. Authenticity only

D. Privacy only

Correct Answer: A. Availability

Question 9

What is residual risk?

A. Risk before any controls exist

B. Risk remaining after controls are applied

C. Risk caused only by natural disasters

D. Risk that has been legally transferred and eliminated

Correct Answer: B. Risk remaining after controls are applied

Question 10

Which action is most appropriate before conducting an authorized security test?

A. Exploit every discovered system without limits

B. Obtain written permission and define the scope

C. Publish all findings immediately

D. Delete logs to avoid disruption

Correct Answer: B. Obtain written permission and define the scope

Cyber Security Fundamentals
Chapter 1 of 14