Skip to main content

CBE NEXUS · UNDERGRADUATE TEXTBOOK SERIES

Chapter 8: Cybersecurity, Privacy and Risk Management

Information Systems

Comprehensive undergraduate notes, security architecture diagrams, applied case studies and university assessment.

Undergraduate level · Chapter 8 of 16 · Security, privacy, assurance and organisational risk

Learning outcomes: Explain security objectives and threat concepts; assess vulnerabilities and risks; design identity and access controls; apply cryptographic, network and application protections; manage privacy and compliance; and plan monitoring, incident response and recovery.

Cybersecurity in modern information systems

Cybersecurity is the practice of protecting information, systems, networks and digital services from unauthorised access, disruption, alteration, destruction and misuse. It is not limited to installing antivirus software or building a firewall. It includes governance, people, processes, architecture, technology, assurance and incident response. An organisation's security posture is shaped by its most important assets, the threats it faces, the vulnerabilities present and the effectiveness of its controls.

Information systems process data that may have financial, academic, health, employment, identity or strategic value. A breach can create direct financial loss, regulatory exposure, interruption of essential services, reputational damage and harm to individuals. Security decisions should therefore be connected to business objectives and the consequences of failure. The appropriate level of protection depends on context, sensitivity, exposure and risk appetite.

Cybersecurity is a continuous process because systems, attackers, suppliers, users and business requirements change. New applications introduce dependencies; staff roles change; software becomes outdated; and attackers adapt their methods. A security programme must continually identify assets, assess risks, implement controls, test their effectiveness, monitor events and improve after incidents.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

The CIA triad and security objectives

Confidentiality means that information is accessible only to authorised people, processes or systems. Integrity means that information and system behaviour remain accurate, complete and protected from unauthorised modification. Availability means that authorised users can access information and services when required. These three objectives form the widely used confidentiality, integrity and availability (CIA) triad.

Controls can support more than one objective. Encryption protects confidentiality and may support integrity when combined with authenticated cryptographic mechanisms. Backups support availability and recovery of integrity after corruption. Access control protects confidentiality and integrity. Redundancy supports availability. Security design should identify which objective matters most for each asset and how controls interact.

Other objectives include authenticity, accountability, non-repudiation, privacy and safety. Authenticity concerns whether an identity or message is genuine. Accountability links actions to responsible identities through reliable logs. Non-repudiation provides evidence that an action or communication occurred, subject to the limits of the technical and legal arrangement. Privacy concerns appropriate handling of information about people.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Information assets, classification and ownership

An information asset is data or a resource that has value to an organisation or stakeholder. Examples include student records, customer accounts, source code, financial transactions, research data, employee files, credentials, network configurations, contracts and service availability. Asset management begins by identifying what exists, where it is stored, who owns it and which services depend on it.

Classification assigns handling requirements according to sensitivity, criticality and legal obligations. A simple scheme may distinguish public, internal, confidential and restricted information. The scheme must define practical controls: who may access data, where it may be stored, how it can be transmitted, how long it is retained and how it is destroyed. Labels without enforceable procedures provide little protection.

An asset owner is accountable for defining acceptable use and protection requirements, while custodians and technical teams implement controls. Asset inventories should include systems, cloud resources, endpoints, applications, data flows, suppliers and service accounts. Review inventories after acquisitions, migrations, major releases and organisational changes.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Threats, vulnerabilities and attack surfaces

A threat is a potential cause of harm, such as a malicious actor, human error, equipment failure, natural disaster or supplier outage. A vulnerability is a weakness that may be exploited or triggered. Risk arises when a threat can exploit a vulnerability and cause an adverse impact. A threat does not automatically become a successful incident; controls may prevent, detect or reduce its consequences.

The attack surface includes all points through which an attacker might interact with a system. It can include public web applications, APIs, remote access, email, cloud management consoles, wireless networks, user devices, software dependencies, physical facilities and supplier connections. Unused services and forgotten accounts increase exposure without providing value.

Threat modelling identifies assets, actors, entry points, trust boundaries, attack paths and mitigations before or during design. A useful model asks what can go wrong, who might cause it, what would be affected and which controls are proportionate. Revisit the model when architecture, data sensitivity, external integrations or threat conditions change.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Cyber threat actors and motivations

Threat actors include financially motivated criminals, organised crime groups, insiders, opportunistic attackers, hacktivists, competitors and state-linked groups. Their capabilities and objectives vary. Some exploit widely known weaknesses at scale, while others conduct targeted reconnaissance and persistence. Defensive planning should consider likely adversaries without assuming that every incident is highly sophisticated.

Motivations may include theft, extortion, espionage, disruption, ideological expression, revenge, fraud or unauthorised curiosity. An insider may misuse legitimate access deliberately or accidentally. A compromised supplier account may provide a route into several customer environments. Attack paths often combine technical weaknesses with social engineering and poor operational controls.

Organisations should use threat intelligence as one input to risk assessment, not as a substitute for asset knowledge. Relevant intelligence includes exploited vulnerabilities, phishing campaigns, malicious infrastructure, sector alerts and supplier advisories. Evaluate the source, freshness, relevance and confidence of intelligence before making changes.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Social engineering and human-centred security

Social engineering manipulates people into disclosing information, transferring funds, granting access or performing unsafe actions. Phishing commonly uses deceptive messages or websites; spear phishing targets specific people; smishing uses text messages; and vishing uses voice calls. Business email compromise may imitate an executive or supplier to redirect a payment or obtain sensitive information.

Effective awareness programmes teach users to recognise unusual urgency, unexpected attachments, credential requests, changed payment instructions and mismatched domains. Staff need a simple reporting route and reassurance that early reporting is valued. Training should be reinforced by technical controls such as multifactor authentication, email filtering, domain protection and payment verification procedures.

Security culture is shaped by leadership, workload, interface design and incentives. If a process makes secure behaviour difficult, users may find unsafe workarounds. Design workflows that support verification, least privilege and safe reporting. Simulated phishing should be ethical, proportionate and used for learning rather than public humiliation.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Malware, ransomware and malicious code

Malware is software designed to perform unauthorised or harmful actions. Categories include viruses, worms, trojans, spyware, keyloggers, rootkits, botnets and ransomware. A single incident may involve several types. Malware can arrive through malicious attachments, compromised websites, software vulnerabilities, removable media or stolen credentials.

Ransomware may encrypt data, disrupt services and threaten disclosure of stolen information. Recovery requires more than paying a demand: organisations need isolated backups, tested restoration, incident response, legal advice and communication plans. A payment does not guarantee recovery or deletion of stolen data. Preventive controls include patching, least privilege, endpoint protection, application control and secure email handling.

Malicious code analysis should be performed only in authorised, isolated environments by qualified personnel. Users should not open suspicious files or attempt amateur cleanup on systems containing evidence. Disconnecting a device from networks may limit spread, but follow the incident response plan so that evidence and critical operations are handled appropriately.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Identity and access management

Identity and Access Management (IAM) governs digital identities and their permissions. An identity may represent a person, device, application or automated workload. IAM includes identity proofing, account creation, authentication, authorisation, provisioning, review, suspension and deprovisioning. Poor account lifecycle management creates orphaned accounts and excessive privileges.

The principle of least privilege gives each identity only the access needed for its role and task. Role-based access control assigns permissions through job or functional roles; attribute-based access control uses contextual attributes such as department, resource sensitivity or device posture. Separation of duties prevents one person from controlling incompatible steps in a sensitive process.

Joiner, mover and leaver procedures should create, adjust and revoke access promptly. Periodic access reviews confirm that privileges remain justified. Shared accounts weaken accountability and should be avoided where individual identities are practical. Service accounts need named owners, limited permissions, secret rotation and monitoring.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Authentication and multifactor security

Authentication verifies a claimed identity. Common factors include something the user knows, such as a password; something the user has, such as a cryptographic authenticator; and something the user is, such as a biometric characteristic. Multifactor authentication combines distinct factors. Two passwords are not two independent factors because both are knowledge factors.

Passwords should be unique and sufficiently long, and organisations should support password managers and secure recovery. Systems should store passwords using salted, purpose-designed password-hashing functions with suitable work factors, not reversible encryption or plain text. Rate limiting, breached-password screening and suspicious-login detection reduce common account attacks.

Phishing-resistant authentication, including appropriately deployed passkeys or hardware-backed authenticators, can reduce credential theft. Recovery channels must be protected because an attacker who can reset an account can bypass a strong login. Privileged accounts should have stronger controls, separate administrative identities and enhanced monitoring.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Authorisation, privilege and access reviews

Authorisation determines which actions an authenticated identity may perform on a resource. It should be enforced server-side for every sensitive request. Hiding a button in the interface is not an access control. A user who changes a record identifier in a URL should not gain access to another user's record unless policy explicitly permits it.

Role design should be based on duties and data sensitivity. Excessive permissions increase the impact of compromised accounts and insider misuse. Privileged access management can provide time-limited elevation, approval, session recording and controlled administrative access. Emergency access should be logged, reviewed and restricted to genuine operational need.

Access reviews compare current permissions with job responsibilities, project assignments and approved exceptions. Review dormant accounts, external users, service identities, privileged groups and inherited permissions. Evidence should record the reviewer, date, decisions, removals and unresolved exceptions.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Cryptography and key management

Cryptography uses mathematical techniques to protect information and verify messages. Symmetric encryption uses a shared secret key; asymmetric cryptography uses related public and private keys; and cryptographic hashes produce fixed-length digests. Digital signatures can provide evidence of message origin and integrity when keys and trust processes are sound.

Encryption at rest protects stored information, while encryption in transit protects communications across networks. Authenticated encryption is preferred because it protects confidentiality and detects tampering. Hashing is not encryption: a hash is designed to be one-way, and passwords require specialised salted password-hashing methods rather than a fast general-purpose digest.

Key management is as important as the algorithm. Keys need secure generation, storage, access control, rotation, backup, revocation and destruction. A key stored beside the encrypted data may provide little protection. Hardware security modules or managed key services can reduce exposure, but their configuration and permissions still require governance.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Network security controls and secure architecture

Network controls include segmentation, firewalls, secure remote access, network access control, intrusion detection, intrusion prevention, secure DNS, endpoint controls and monitoring. A defence-in-depth strategy layers preventive, detective and corrective measures so that failure of one control does not expose the entire environment.

A secure architecture identifies trust boundaries and limits unnecessary communication. Public-facing services should not have unrestricted access to internal databases or management interfaces. Administrative access should be separated from ordinary user traffic. Egress filtering can reduce unauthorised outbound communication, while logging supports detection and investigation.

Network controls must be maintained as systems change. Review firewall rules, VPN accounts, exposed ports, wireless security, routing and device firmware. Remove temporary rules after projects end. Test segmentation from both permitted and prohibited paths, because a policy that looks correct in a console may behave differently in production.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Application and API security

Application security protects software throughout requirements, design, development, testing, deployment and maintenance. Common weaknesses include injection, cross-site scripting, broken access control, insecure deserialisation, unsafe file uploads, authentication failures, misconfiguration and vulnerable dependencies. APIs introduce risks such as excessive data exposure, weak object-level authorisation and unrestricted resource consumption.

Secure development uses threat modelling, code review, parameterised queries, output encoding, input validation, safe error handling, dependency management and automated testing. Secrets must not be embedded in source code or public client bundles. API endpoints should validate caller identity and resource-level permission, apply rate limits and return only data required by the task.

Security testing should include static analysis, dynamic testing, dependency scanning, configuration review and authorised penetration testing. Findings should be prioritised by exploitability and impact, assigned owners and tracked through remediation. A clean automated scan is not proof of security because tools have coverage limits and may miss logic flaws.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Endpoint, mobile and device security

Endpoints include laptops, desktops, smartphones, tablets, servers and specialised devices. They store credentials, process data and connect to organisational services, making them important security boundaries. Endpoint controls include supported operating systems, patching, endpoint detection and response, disk encryption, secure boot, application control and managed configuration.

Mobile devices introduce risks from loss, theft, unsafe applications, insecure networks and mixing personal and organisational data. Mobile device management or mobile application management can enforce screen locks, encryption, approved applications and selective data removal. Bring-your-own-device arrangements need clear privacy boundaries and acceptable-use policies.

Inventory devices and assign ownership. Remove unsupported operating systems and disable unnecessary services. Protect administrator privileges and use standard user accounts for routine work. Remote wipe and device tracking must be governed by policy and applicable law. Lost devices should be reported promptly so that credentials and sessions can be revoked.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Cloud security and shared responsibility

Cloud security depends on the service model and provider architecture. Providers typically secure facilities and foundational infrastructure, while customers remain responsible for aspects such as identity, data classification, application code, configuration and user access. The precise division differs between IaaS, PaaS and SaaS and must be confirmed for each service.

Common cloud risks include public storage exposure, overly permissive IAM policies, leaked API keys, insecure network rules, unprotected backups, weak logging, vulnerable workloads and shadow IT. Cloud resources can be created quickly, so governance needs automated guardrails, inventory, configuration assessment and clear ownership.

Secure cloud foundations use multifactor authentication, least-privilege roles, separate production environments, private networking where suitable, encryption, central audit logs, backup protection and policy-as-code. Review provider security advisories and customer responsibilities. Provider certification does not guarantee that an individual tenant is correctly configured.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Data privacy, protection and information lifecycle

Privacy concerns the appropriate collection, use, sharing, retention and disposal of information about identifiable people. Data protection translates legal and organisational duties into controls over personal data. The lifecycle includes collection, recording, storage, access, use, disclosure, retention, archiving and deletion. Controls should apply throughout this lifecycle, including copies and derived datasets.

Data minimisation means collecting only what is necessary for a defined purpose. Purpose limitation restricts reuse that is incompatible with the original purpose unless a valid legal basis or exception applies. Accuracy, storage limitation, transparency, security and accountability are widely recognised data-protection principles, although exact legal wording and obligations vary by jurisdiction.

Privacy by design embeds privacy requirements early in systems and processes. Privacy impact assessments help identify risks before processing begins. Pseudonymisation can reduce direct identifiability but does not necessarily make information anonymous. Anonymisation requires a robust assessment of re-identification risk, including when datasets can be combined.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Legal, regulatory and contractual compliance

Cybersecurity and privacy obligations arise from national laws, sector regulations, contractual terms, professional standards and cross-border arrangements. Requirements vary by jurisdiction and data type. Organisations should identify which laws apply, who is responsible, what evidence is needed and how obligations change when suppliers or processing locations change.

A compliance register maps obligations to controls, owners, evidence and review dates. Examples of control areas include access management, incident notification, retention, encryption, supplier due diligence, data-subject rights and business continuity. A policy statement alone is not evidence that a control operates effectively.

Compliance and security overlap but are not identical. A system may satisfy a checklist yet remain vulnerable to a practical attack. Conversely, a sound technical control may not satisfy a specific legal duty if transparency, lawful basis, retention or accountability is missing. Use legal and regulatory expertise for decisions with material consequences.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Cybersecurity risk management

Risk management identifies uncertain events that may affect objectives, estimates likelihood and impact, selects responses and monitors residual exposure. Risk can be described qualitatively or quantitatively. A simple qualitative matrix may combine likelihood and consequence, but scores should not create false precision. Define rating criteria so different assessors apply them consistently.

Risk responses commonly include avoiding an activity, mitigating the risk through controls, transferring or sharing some financial consequences, and accepting residual risk within authorised limits. Insurance transfers some financial exposure but does not prevent harm or remove legal responsibilities. Risk acceptance should identify an accountable decision-maker and review date.

A risk register records the asset or objective, threat scenario, vulnerability, existing controls, likelihood, impact, rating, treatment, owner, due date and residual risk. Review it after incidents, major changes, new threats, audit findings and supplier changes. High risks should have funded, time-bound treatment plans or explicit senior acceptance.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Security governance, policies and organisational roles

Security governance establishes direction, accountability, decision rights, oversight and performance measures. The board or governing body sets expectations and risk appetite; executives allocate resources; security leaders coordinate programmes; system owners manage service risk; and employees follow policy and report concerns. In smaller organisations, roles may be combined, but accountability should remain explicit.

A policy states management intent and mandatory principles. Standards specify required configurations or practices; procedures describe repeatable steps; and guidelines provide recommended approaches. Policies should be approved, communicated, accessible and reviewed. They must be realistic enough to follow and specific enough to assess.

Governance measures should connect to risk reduction and service outcomes. Examples include privileged-access review completion, critical patch exposure, backup restoration success, incident response time, phishing report rate and supplier assessment coverage. Metrics need definitions and context; a high training completion percentage does not prove that staff can recognise a real attack.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Security awareness, training and professional ethics

Security awareness helps people recognise threats and understand their responsibilities. Training should be role-specific: developers need secure coding; finance teams need payment-change verification; administrators need privileged access and incident procedures; and general users need safe handling of credentials, devices and data. Training should be repeated and updated as threats and workflows change.

Professional ethics requires confidentiality, honesty, competence, respect for privacy, lawful authority and responsible disclosure. Security testing must have explicit authorisation, scope, time limits and rules of engagement. Access to sensitive records for curiosity or personal reasons is inappropriate even when technical access is available.

Organisations should encourage prompt reporting without retaliation for good-faith mistakes. After an incident, learning-focused reviews can identify unclear procedures, workload pressures or interface problems. Accountability remains necessary for deliberate misconduct, but blame alone discourages early reporting and hides systemic weaknesses.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Security monitoring, logging and threat detection

Security monitoring collects and analyses events from endpoints, identity systems, applications, networks, cloud platforms and physical controls. Logs can support detection, investigation, compliance and operational troubleshooting. Useful records include timestamps, actor identity, source, action, target, outcome and correlation identifiers, while avoiding unnecessary sensitive content.

A Security Information and Event Management (SIEM) platform can aggregate, normalise and correlate events. Detection rules identify patterns such as unusual login locations, privilege escalation, unexpected data transfer or repeated authentication failures. Endpoint detection and response tools provide visibility into host behaviour. Alerts require triage, context and documented escalation.

Logging should be tamper-resistant, time-synchronised, access-controlled and retained according to purpose and legal requirements. Excessive logs can create cost and privacy risks; insufficient logs prevent investigation. Test alerts and response procedures. Tune detections to reduce noise without suppressing important events.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Incident response and digital forensics

A security incident is an event that compromises or threatens confidentiality, integrity or availability, or violates security policy. Incident response prepares the organisation to identify, analyse, contain, eradicate, recover from and learn about incidents. Preparation includes roles, contact lists, tools, legal advice, backups, communications and supplier coordination.

Containment limits damage while preserving essential evidence. Eradication removes the cause, such as compromised credentials, malware or an exposed service. Recovery restores trusted operations and increases monitoring. Evidence handling should preserve integrity, record who collected it and when, and follow authorised procedures. Do not destroy logs or reimage systems before considering forensic needs.

Incident communications should be accurate, timely and coordinated. Notify affected parties, regulators, law enforcement or contractual partners when required and advised. Avoid speculation about cause or impact before facts are established. Conduct a post-incident review to improve controls, training, architecture and response capability.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Business continuity, backup and disaster recovery

Business continuity maintains critical activities during disruption; disaster recovery restores technology and data services. They are related but distinct. Continuity planning considers people, premises, suppliers, communications, manual workarounds and priority processes. Disaster recovery focuses on systems, infrastructure, applications and information restoration.

Recovery Time Objective (RTO) defines the target time to restore a service. Recovery Point Objective (RPO) defines the target maximum data loss measured in time. A service with a four-hour RTO and 30-minute RPO requires a recovery design and operational capability that can meet those targets under the stated scenario. Targets should be agreed with business owners.

Backups should be protected from production credentials, encrypted, retained and regularly tested. Replication alone is not a backup because accidental deletion or corruption may replicate. Recovery exercises should test complete dependencies, including identity, DNS, network connectivity, application configuration, data and user access.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Third-party, supplier and supply-chain security

Organisations rely on cloud providers, software vendors, payment processors, consultants, managed service providers and other partners. A supplier may access sensitive data or connect directly to internal systems. Supply-chain risk includes compromised software updates, insecure dependencies, weak supplier access and service disruption.

Due diligence should examine security governance, certifications where relevant, incident history, subcontractors, data locations, access controls, vulnerability management, continuity, insurance and contractual obligations. Assessment should be proportionate to the supplier's access and criticality. A questionnaire is only one source of evidence and may need independent validation.

Contracts should define permitted processing, security requirements, breach notification, audit rights, service levels, data return or deletion, subcontracting and exit support. Supplier access should be time-limited and monitored. Reassess critical suppliers periodically and when services, ownership or threat conditions change.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Vulnerability and patch management

A vulnerability is a weakness that can be exploited or triggered. Vulnerability management identifies assets, scans for weaknesses, validates findings, prioritises remediation, applies fixes or compensating controls and verifies results. Scanning without ownership and remediation creates lists rather than reduced risk.

Patch priority should consider exploit availability, active exploitation, exposure, asset criticality, business impact and compensating controls. A severe vulnerability on an Internet-facing service may require urgent action; a lower-risk issue on an isolated legacy system may need a planned change. Emergency changes still require testing, approval and rollback planning appropriate to the risk.

Maintain an accurate asset inventory and supported software versions. Test patches in representative environments, monitor vendor advisories and track exceptions with owners and expiry dates. Where patching is impossible, reduce exposure, disable vulnerable features, segment the asset and monitor for exploitation until replacement or remediation.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Secure software development lifecycle and DevSecOps

A Secure Software Development Life Cycle (SSDLC) integrates security from requirements through retirement. Requirements identify data sensitivity, access rules and abuse cases; design includes threat modelling; development follows secure coding standards; testing examines vulnerabilities; deployment uses hardened configuration; and operations monitor and patch the service.

DevSecOps automates repeatable security checks within development and delivery pipelines. Tools may include secret scanning, static analysis, software composition analysis, container scanning, infrastructure-as-code checks and dynamic testing. Automation provides feedback early, but findings need prioritisation and human review to distinguish real issues from false positives.

Software bills of materials can help identify components and versions used in an application. Dependency governance should include trusted sources, update policy, licence review and vulnerability response. Retire unsupported libraries. Security gates should be proportionate and measurable so that critical risks are not ignored and low-value alerts do not overwhelm teams.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Security audits, assurance and maturity

A security audit evaluates whether controls are designed and operating according to defined criteria. Internal audits support improvement and governance; external audits may provide independent assurance. Penetration tests simulate authorised attacks within a defined scope. Vulnerability assessments identify known weaknesses but do not necessarily demonstrate exploitability or business impact.

Audit evidence may include policies, access records, configuration exports, change tickets, incident records, backup tests, training data and interviews. Evidence should be reliable, relevant, current and traceable. A control that exists on paper but is not consistently performed is not operating effectively.

Maturity models help organisations understand repeatability, measurement and improvement. A maturity score should guide investment rather than become a vanity metric. Prioritise foundational controls such as asset inventory, identity, patching, backups, logging and incident response before pursuing complex tools that the organisation cannot operate.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Emerging cybersecurity challenges and responsible innovation

Emerging challenges include cloud concentration, connected devices, AI-enabled social engineering, deepfakes, software supply-chain attacks, cryptographic change, operational technology exposure and increasingly automated attacks. New tools can improve defence but also create new attack surfaces, data flows and dependencies.

AI systems may process sensitive prompts, retrieve confidential documents or generate code with vulnerabilities. Secure deployment requires access controls, data minimisation, prompt-injection testing, output validation, human oversight and monitoring. Do not place confidential information into unapproved external services. Evaluate model providers and retention practices.

Security professionals should remain curious but sceptical. Assess new technologies through threat modelling, controlled pilots, independent testing, legal review and measurable outcomes. Responsible innovation protects users, respects rights and avoids creating disproportionate surveillance or exclusion. The objective is trustworthy information systems, not security theatre.

For each topic, translate the principle into a documented control with an owner, scope, operating frequency and evidence requirement. Consider how the control could fail, how an exception is approved and how effectiveness is measured. Controls should be tested in the actual environment and adjusted when business processes, technology, suppliers or threat conditions change.

Case study: ransomware at a regional university

A university's administrative network becomes unavailable after staff discover that shared files have been encrypted. Some departments report suspicious login alerts, and the institution is unsure whether student information was copied. Online registration and finance services are affected during a busy period.

The incident team should activate the response plan, establish command roles, preserve relevant logs and isolate affected systems in a controlled way. Revoke suspected compromised credentials and sessions, identify the scope of affected devices and services, and engage authorised forensic, legal and communications support. Do not assume that encrypted files are the only impact; investigate possible data exfiltration and persistence.

Restore only from trusted, tested backups after the entry route is understood and removed. Prioritise critical services using agreed continuity plans. Communicate verified facts and required notifications through authorised channels. After recovery, improve multifactor authentication, privileged access, endpoint controls, segmentation, patching, offline backups and staff reporting.

Prepare an incident timeline, stakeholder map, evidence register, risk assessment and improvement plan for this scenario. Distinguish confirmed facts from hypotheses, identify decision authority and record the reason for consequential actions. Evaluate both technical recovery and the effect on people, business services, legal duties and public trust.

Case study: student records exposed through cloud storage

A college discovers that a cloud storage location containing student documents was configured for public access. The exposure may have lasted several weeks. The institution needs to establish which records were accessible, whether they were downloaded and what obligations apply.

Immediately restrict access while preserving configuration and access logs. Identify affected objects, time period, data categories, identities and access events. Involve the data protection officer, legal advisers, cloud administrator and senior incident lead. Assess the risk to individuals and follow applicable notification and communication requirements.

Prevent recurrence with private-by-default storage, policy-as-code, least-privilege identities, continuous configuration monitoring, data classification, logging and periodic access reviews. Test public exposure from an external perspective. Ensure that ownership and review responsibility are assigned to every storage resource.

Prepare an incident timeline, stakeholder map, evidence register, risk assessment and improvement plan for this scenario. Distinguish confirmed facts from hypotheses, identify decision authority and record the reason for consequential actions. Evaluate both technical recovery and the effect on people, business services, legal duties and public trust.

Case study: business email compromise and fraudulent payment

A finance officer receives a convincing email that appears to come from a senior manager requesting an urgent supplier bank-account change. A payment is made before the discrepancy is noticed. The attacker may have compromised a mailbox or impersonated a supplier.

Contact the bank and relevant payment providers immediately through verified channels. Preserve email headers, message copies, authentication logs and payment records. Check mailbox forwarding rules, delegated access, sessions and authentication events. Reset compromised credentials, revoke sessions and apply stronger authentication. Coordinate legal, fraud and law-enforcement advice as appropriate.

Introduce independent verification of payment-detail changes using a previously established contact method. Require dual approval for high-value transfers, monitor unusual mailbox rules and train staff to report pressure tactics. Review supplier master-data controls and test the process through realistic tabletop exercises.

Prepare an incident timeline, stakeholder map, evidence register, risk assessment and improvement plan for this scenario. Distinguish confirmed facts from hypotheses, identify decision authority and record the reason for consequential actions. Evaluate both technical recovery and the effect on people, business services, legal duties and public trust.

Cybersecurity and risk management diagrams

Risk management cycle
Identify assets, threats and vulnerabilities
↓
Analyse likelihood and impact
↓
Evaluate against risk criteria
↓
Treat, transfer, avoid or accept
↓
Monitor controls and residual risk
↓
Review after changes and incidents
Identity and access lifecycle
Joiner: verify identity and create approved access
↓
Role change: adjust permissions and ownership
↓
Periodic review: confirm business need
↓
Leaver: revoke accounts, sessions and credentials
↓
Audit: retain evidence and investigate exceptions
Incident response lifecycle
Prepare people, tools, playbooks and backups
↓
Detect and analyse event
↓
Contain affected systems and accounts
↓
Eradicate root cause and persistence
↓
Recover trusted services and monitor
↓
Learn, report and improve controls
Defence in depth
Governance, policy and user awareness
↓
Identity, authentication and least privilege
↓
Network segmentation and secure gateways
↓
Endpoint, application and data controls
↓
Logging, detection and incident response
↓
Backup, recovery and business continuity

University examination and revision questions

Use clear definitions, examples and structured reasoning. Model answers identify the central concepts expected in a university response.

Question 1. Define cybersecurity.

Model answer: The practice of protecting information, systems, networks and digital services against unauthorised access, disruption, alteration, destruction and misuse.

Question 2. Explain the CIA triad.

Model answer: Confidentiality restricts access to authorised entities; integrity protects accuracy and completeness; availability ensures authorised access when needed.

Question 3. Differentiate a threat and a vulnerability.

Model answer: A threat is a potential cause of harm; a vulnerability is a weakness that a threat may exploit.

Question 4. What is an attack surface?

Model answer: All interfaces, systems, services, people and connections through which an attacker may interact with an organisation.

Question 5. Define information classification.

Model answer: Assigning handling categories to information according to sensitivity, criticality and obligations.

Question 6. Explain least privilege.

Model answer: Giving each identity only the permissions needed for its authorised tasks.

Question 7. Differentiate authentication and authorisation.

Model answer: Authentication verifies identity; authorisation determines permitted actions and resources.

Question 8. What is multifactor authentication?

Model answer: Authentication using two or more distinct factor categories, such as knowledge, possession and inherence.

Question 9. Why should passwords be salted and hashed?

Model answer: A unique salt and suitable password-hashing function make offline guessing and reuse of precomputed tables more difficult.

Question 10. Compare symmetric and asymmetric cryptography.

Model answer: Symmetric cryptography uses a shared secret key; asymmetric cryptography uses related public and private keys.

Question 11. What is a digital signature used for?

Model answer: It provides cryptographic evidence of message integrity and signing-key use, subject to key trust and identity controls.

Question 12. Define data minimisation.

Model answer: Collecting and processing only personal information necessary for a specified legitimate purpose.

Question 13. What is a privacy impact assessment?

Model answer: A structured assessment that identifies and evaluates privacy risks arising from a proposed data-processing activity.

Question 14. Explain phishing.

Model answer: A deceptive communication intended to persuade a recipient to disclose information, transfer funds or perform an unsafe action.

Question 15. What is ransomware?

Model answer: Malicious software or an attack operation that disrupts access to data or systems, commonly through encryption and extortion.

Question 16. Differentiate preventive and detective controls.

Model answer: Preventive controls seek to stop incidents; detective controls identify suspicious activity or control failures.

Question 17. What is a security information and event management system?

Model answer: A platform that aggregates and correlates security events to support monitoring, alerting and investigation.

Question 18. Define risk appetite and residual risk.

Model answer: Risk appetite is the level and type of risk an organisation is willing to pursue or retain; residual risk remains after controls.

Question 19. State four risk treatment options.

Model answer: Avoid, mitigate, transfer or share, and accept within authorised limits.

Question 20. What is a security incident response plan?

Model answer: A documented arrangement defining roles and actions for preparation, detection, analysis, containment, eradication, recovery and learning.

Question 21. Differentiate RTO and RPO.

Model answer: RTO is the target restoration time; RPO is the target maximum data loss measured in time.

Question 22. Why is replication not equivalent to backup?

Model answer: Deletion, corruption or malicious encryption may replicate; independent protected backups are needed for recovery.

Question 23. What is a supply-chain security risk?

Model answer: Risk arising from suppliers, software dependencies, service providers or external parties that can affect organisational systems or data.

Question 24. Explain vulnerability management.

Model answer: The process of identifying, prioritising, remediating and verifying weaknesses across assets and software.

Question 25. What is a secure software development lifecycle?

Model answer: A development approach that integrates security requirements, design analysis, secure coding, testing, deployment and maintenance.

Question 26. Differentiate a security audit and penetration test.

Model answer: An audit evaluates controls against criteria; a penetration test performs authorised attack simulation within a defined scope.

Question 27. Why are access reviews necessary?

Model answer: They identify unnecessary, excessive, dormant or inappropriate permissions as roles and business needs change.

Question 28. What is defence in depth?

Model answer: Using multiple complementary security controls so that failure of one does not expose the whole system.

Question 29. State four elements of a supplier security assessment.

Model answer: Access and data scope, security controls, incident history, subcontractors, location, continuity, contractual duties and assurance evidence.

Question 30. Explain the purpose of a post-incident review.

Model answer: To identify root causes, control gaps and improvement actions, strengthening prevention, detection and recovery.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.