CE251-5-AU-CO:
Secure Software Engineering

The details
2026/27
Computer Science and Electronic Engineering (School of)
Colchester Campus
Autumn
Undergraduate: Level 5
Future
Thursday 08 October 2026
Friday 18 December 2026
15
01 May 2026

 

Requisites for this module
(none)
(none)
(none)
(none)

 

(none)

Key module for

BSC G111N4 Computing,
BSC G112N4 Computing (Including Year Abroad),
BSC G113N4 Computing (Including Placement Year),
BSC I900 Cyber Security,
BSC I901 Cyber Security (including Placement Year),
BSC I902 Cyber Security (including Year Abroad)

Module description

This module focuses on the principles and practice of secure software engineering, emphasising the identification, analysis and mitigation of security vulnerabilities throughout the software development lifecycle. Students examine common attack vectors, secure design patterns, threat modelling approaches, and techniques for building resilient software systems.


The module explores how security must be embedded within requirements, architecture, implementation and testing, rather than treated as an afterthought. By integrating security measures at the earliest stages of system development, the module highlights how risks can be significantly reduced. Students will explore key principles of secure design, focusing on proactive strategies to identify and mitigate weaknesses before they can be exploited. Through case studies and real-world examples, the module provides a comprehensive understanding of how security can be embedded into the architecture of both software and hardware systems. Through practical laboratory exercises and applied security analysis, students develop the skills required to evaluate, harden and assure the security of software systems in realistic threat environments.

Module aims

The aims of this module are:



  • To introduce students to the principles of security-by-design within the software development lifecycle.

  • To provide students with an understanding of common software vulnerabilities, attack techniques and mitigation strategies.

  • To enable students to analyse and assess security risks within software systems.

  • To develop students' ability to apply secure coding practices and vulnerability assessment techniques.

  • To foster awareness of professional, ethical and regulatory responsibilities in secure software development.

Module learning outcomes

By the end of the module, students will be expected to:



  1. Analyse software systems to identify potential security vulnerabilities and attack surfaces.

  2. Evaluate common classes of software vulnerabilities and recommend appropriate mitigation strategies.

  3. Apply secure design principles and coding practices to develop or improve software components.

  4. Assess security risks using structured approaches such as threat modelling and risk analysis frameworks.

  5. Design and implement security controls to enhance the robustness and resilience of software systems.

Module information

Indicative syllabus



  • Security principles and secure software development lifecycle (SSDLC)

  • Threat modelling methodologies

  • Common software vulnerabilities (e.g. injection, authentication flaws, insecure deserialisation, buffer overflows)

  • Secure coding practices and defensive programming

  • Input validation, authentication and authorisation mechanisms

  • Cryptographic integration and secure API usage

  • Secure design patterns and architectural security considerations

  • Static and dynamic analysis tools

  • Secure testing methodologies including the use of ethical hacking

  • Risk assessment and vulnerability management

  • Legal, ethical and professional considerations in secure development

Learning and teaching methods

This module will be delivered via:

  • Ten 2-hour lectures
  • Ten 2-hour laboratory sessions
  • Twenty academic support hours

Lectures introduce theoretical foundations, structured security concepts and case-based analysis. Laboratory sessions provide hands-on experience in vulnerability identification, secure coding, threat modelling and use of security analysis tools. Students are expected to undertake guided reading and independent practice outside scheduled teaching hours.

Teaching materials will be made available through the University's virtual learning environment (Moodle) including lecture recordings, structured lab guides and supplementary resources.

Inclusive learning is supported through clear task scaffolding, step-by-step laboratory guidance, accessible digital materials, flexible engagement with recorded content, and formative feedback opportunities. Adjustments can be made where required in accordance with individual learning plans.

Laboratory activities may involve security analysis and simulated attack scenarios; care will be taken to ensure activities are conducted within controlled environments and that appropriate guidance is provided. CSEE have an existing "Cyber security environment" that has been validated by the Digital Innovation and Technology Services (DITS) section as providing the suitable controls to operate the laboratories safely.

Bibliography

(none)

Assessment items, weightings and deadlines

Coursework / exam Description Deadline Coursework weighting
Exam  Main exam: In-Person, Open Book (Restricted), 120 minutes during Summer (Main Period) 
Exam  Reassessment Main exam: In-Person, Open Book (Restricted), 120 minutes during September (Reassessment Period) 

Exam format definitions

  • Remote, open book: Your exam will take place remotely via an online learning platform. You may refer to any physical or electronic materials during the exam.
  • In-person, open book: Your exam will take place on campus under invigilation. You may refer to any physical materials such as paper study notes or a textbook during the exam. Electronic devices may not be used in the exam.
  • In-person, open book (restricted): The exam will take place on campus under invigilation. You may refer only to specific physical materials such as a named textbook during the exam. Permitted materials will be specified by your department. Electronic devices may not be used in the exam.
  • In-person, closed book: The exam will take place on campus under invigilation. You may not refer to any physical materials or electronic devices during the exam. There may be times when a paper dictionary, for example, may be permitted in an otherwise closed book exam. Any exceptions will be specified by your department.

Your department will provide further guidance before your exams.

Overall assessment

Coursework Exam
30% 70%

Reassessment

Coursework Exam
30% 70%
Module supervisor and teaching staff

 

Availability
No
No
Yes

External examiner

No external examiner information available for this module.
Resources
Available via Moodle
No lecture recording information available for this module.

 

Further information

Disclaimer: The University makes every effort to ensure that this information on its Module Directory is accurate and up-to-date. Exceptionally it can be necessary to make changes, for example to programmes, modules, facilities or fees. Examples of such reasons might include a change of law or regulatory requirements, industrial action, lack of demand, departure of key personnel, change in government policy, or withdrawal/reduction of funding. Changes to modules may for example consist of variations to the content and method of delivery or assessment of modules and other services, to discontinue modules and other services and to merge or combine modules. The University will endeavour to keep such changes to a minimum, and will also keep students informed appropriately by updating our programme specifications and module directory.

The full Procedures, Rules and Regulations of the University governing how it operates are set out in the Charter, Statutes and Ordinances and in the University Regulations, Policy and Procedures.