Skip to main content
CBE Nexus · Undergraduate Computer Science

Chapter 11: Cybersecurity and Information Assurance

Undergraduate cybersecurity notes covering threat modelling, cryptography, identity, access control, secure coding, network defence, incident response, risk management, governance and digital forensics.

Back to Computer Science course guide

Chapter overview and learning outcomes

This chapter develops the theory and practical foundations of cybersecurity and information assurance, linking core concepts to the design, evaluation and responsible operation of computing systems.

1. Cybersecurity foundations and information assurance

Cybersecurity protects systems, networks, applications and information against unauthorised access, disruption, alteration and destruction. Information assurance is broader: it concerns confidence that information is available, accurate, authentic and appropriately protected throughout its lifecycle. Security objectives are often expressed through confidentiality, integrity and availability (the CIA triad). Additional objectives include authenticity, accountability, privacy and non-repudiation. Security is a socio-technical discipline: people, processes, technology, suppliers and governance all influence outcomes.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

2. Threats, vulnerabilities, exploits and threat modelling

A threat is a potential cause of harm; a vulnerability is a weakness that may be exploited; risk combines likelihood and impact in a defined context. Threat actors may include criminals, insiders, competitors or state-sponsored groups, but attribution is often uncertain. Threat modelling identifies assets, trust boundaries, entry points, data flows, abuse cases and mitigations. Frameworks such as STRIDE can help structure analysis. Models should be revisited when architecture, dependencies or attacker capabilities change.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

3. Security governance, policies and risk management

Governance establishes accountability, acceptable risk and decision-making authority. Policies state organisational requirements; standards define mandatory controls; procedures explain repeatable actions; guidelines offer recommendations. Risk assessment identifies assets, threats, vulnerabilities, likelihood, impact and existing controls. Treatment options include avoiding, mitigating, transferring or accepting risk. A risk register records owners, decisions and review dates. Security programmes should align controls with business objectives, legal obligations and operational capability.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

4. Cryptographic foundations

Cryptography supports confidentiality, integrity, authentication and key establishment. Symmetric encryption uses a shared secret key and is efficient for bulk data; asymmetric cryptography uses related public and private keys for functions such as key exchange and digital signatures. Hash functions map arbitrary input to fixed-length digests and are used for integrity checks and password storage constructions. A message authentication code verifies integrity and authenticity using a secret key. Algorithms do not compensate for poor key management or insecure implementation.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

5. Identity, authentication and access control

Identification claims an identity; authentication verifies the claim; authorisation determines permitted actions; accounting records relevant activity. Authentication factors include something known, possessed or inherent, with multi-factor authentication combining independent categories. Access control models include discretionary, mandatory, role-based and attribute-based approaches. Apply least privilege, separation of duties, secure account recovery, session expiry and lifecycle management. Shared accounts weaken accountability and should be avoided where individual identities are feasible.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

6. Network security and infrastructure defence

Network defence uses segmentation, firewalls, secure remote access, intrusion detection and prevention, endpoint protection, secure DNS and traffic monitoring. A firewall enforces rules between network zones but cannot prevent every attack, especially when permitted traffic carries malicious content. Zero-trust principles require explicit verification and least-privilege access rather than assuming trust based on network location. Secure configuration, timely patching, asset inventories and tested backups reduce common exposure.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

7. Application security and secure software development

Application security begins with requirements and design, not only final testing. Validate input at trust boundaries, encode output for its context, use parameterised database queries, protect sessions, enforce authorisation on the server and handle errors without exposing secrets. Common weaknesses include injection, broken access control, insecure deserialisation, misconfiguration and vulnerable dependencies. Secure development integrates code review, static and dynamic testing, dependency analysis, threat modelling and remediation tracking.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

8. Security operations, monitoring and incident response

Security operations collect and analyse logs, alerts, endpoint telemetry and network events to identify suspicious activity. An incident response plan defines preparation, detection, analysis, containment, eradication, recovery and lessons learned. Preserve evidence and maintain a clear timeline. Containment should limit harm without unnecessarily destroying forensic information. Escalation paths, communication roles, legal advice and business continuity arrangements should be agreed before an incident occurs and exercised through simulations.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

9. Digital forensics and evidence handling

Digital forensics applies repeatable methods to identify, preserve, acquire, examine, analyse and report digital evidence. Evidence may include disk images, volatile memory, logs, mobile devices, cloud records and network captures. Maintain chain of custody by recording who collected, handled, transferred and stored each item, when and how. Use write blockers and verified forensic copies where appropriate. Respect legal authority, privacy, proportionality and organisational policy; document limitations and alternative explanations.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

10. Security testing, vulnerability management and assurance

Vulnerability management includes asset discovery, scanning, validation, prioritisation, remediation and verification. Severity scores are useful inputs but do not replace context: exposure, exploitability, business criticality and compensating controls matter. Penetration testing is authorised, scoped testing that attempts to demonstrate realistic attack paths; it is not a substitute for secure design or continuous monitoring. Assurance combines evidence from audits, tests, configuration reviews, metrics and governance.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

11. Privacy, ethics, resilience and emerging challenges

Privacy requires responsible collection, use, sharing, retention and disposal of personal information. Data minimisation, purpose limitation, transparency, access controls and secure deletion reduce exposure. Security professionals must act within legal authority, obtain permission, avoid harm and disclose findings responsibly. Cloud services, connected devices, AI systems and supply chains expand the attack surface. Resilience depends on preparation, redundancy, recovery objectives, supplier oversight and learning from near misses as well as incidents.

Applied study: Work through a realistic scenario from the domain. Identify the assumptions, constraints, relevant stakeholders and expected outcome. Explain the reasoning behind a proposed method, compare it with at least one alternative, and discuss reliability, security, performance, ethical implications and limitations.

Learning activity: Prepare a labelled model or worked example, define how you would test it, and write a short reflection on what evidence would change your conclusion.

Figure 1. Cybersecurity risk cycle
Identify assets and trust boundaries→Model threats and vulnerabilities→Assess likelihood and impact→Select and test controls→Monitor and improve

Conceptual diagram for learning and revision.

Figure 2. Identity and access decision
User or service claims identity→Authenticate the claim→Authorise requested action→Record relevant activity

Conceptual diagram for learning and revision.

Figure 3. Incident response lifecycle
Prepare and detect→Analyse and contain→Eradicate and recover→Review lessons learned

Conceptual diagram for learning and revision.

Practical laboratory or project activity

  1. Choose a bounded problem relevant to this chapter and state its purpose.
  2. Identify inputs, outputs, constraints, assumptions and potential failure cases.
  3. Develop a small model, prototype, experiment or worked analysis.
  4. Use appropriate tools and authorised datasets or test environments.
  5. Test normal, boundary and failure conditions; record reproducible observations.
  6. Write a report explaining method, evidence, limitations and recommendations.

Follow institutional rules, protect private information and obtain permission before testing systems or collecting data.

Worked reasoning and self-assessment

Start by translating the question into a precise problem statement. Define variables and assumptions before calculating or implementing. Work through a small example manually, then verify it with an appropriate tool. Explain why the selected approach is suitable, identify an alternative, and discuss its trade-offs. For empirical claims, describe the data and method needed to support them; for system claims, specify observable tests and expected outcomes.

Examination and revision questions

Answer using precise definitions, diagrams, calculations and examples where appropriate.

  1. Explain the CIA triad.

    Show answer guidance

    Confidentiality restricts unauthorised disclosure; integrity protects accuracy and completeness; availability ensures authorised access when needed.

  2. Differentiate a threat and a vulnerability.

    Show answer guidance

    A threat can cause harm; a vulnerability is a weakness that a threat may exploit.

  3. What is threat modelling?

    Show answer guidance

    A structured process for identifying assets, trust boundaries, threats and mitigations during system design.

  4. What is a hash function used for?

    Show answer guidance

    It produces a fixed-length digest used in integrity checks and cryptographic constructions.

  5. Differentiate encryption and hashing.

    Show answer guidance

    Encryption is designed to be reversible with a key; a secure hash is designed to be one-way.

  6. What is multi-factor authentication?

    Show answer guidance

    Authentication using at least two independent factor categories.

  7. Define least privilege.

    Show answer guidance

    Granting only the minimum permissions required for a task and only for as long as needed.

  8. What is network segmentation?

    Show answer guidance

    Dividing a network into zones to control traffic and limit lateral movement.

  9. Name two common web application risks.

    Show answer guidance

    Examples include injection, cross-site scripting, broken access control and security misconfiguration.

  10. List the main incident response stages.

    Show answer guidance

    Preparation, detection and analysis, containment, eradication, recovery and lessons learned.

  11. What is chain of custody?

    Show answer guidance

    A documented record of evidence collection, handling, transfer and storage.

  12. Why prioritise vulnerabilities by context?

    Show answer guidance

    Severity alone omits exposure, exploitability, asset criticality and compensating controls.

  13. What is a security policy?

    Show answer guidance

    An approved statement of organisational security requirements and responsibilities.

  14. Why are tested backups important?

    Show answer guidance

    They establish that data and services can be restored within required recovery objectives.

  15. Name two privacy-by-design practices.

    Show answer guidance

    Data minimisation, purpose limitation, access control, retention limits and transparency.

Revision checklist

Further study and academic references

Consult current university textbooks, peer-reviewed conference and journal papers, official standards and authoritative technical documentation. Verify versions and publication details before citing sources. Use the citation style required by your institution, cite data and software as well as written sources, and distinguish published evidence from your own analysis. Do not invent references, measurements or experimental outcomes.

Academic and responsible-use note: These notes support undergraduate study and do not replace your institution's course outline, laboratory rules or supervisor guidance. Respect privacy, intellectual property, licences, research ethics and applicable law.

Return to the full Computer Science course guide

Official Education References

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