Master’s in Critical Software and Firmware Security Engineering (DevSecOps/DO-178C/IEC 61508)
Online master's programme of 1,900 hours in safety-critical software and firmware security engineering (DevSecOps/DO-178C/IEC 61508), structured in 12 modules covering DO-178C, IEC 61508 and derived standards, secure coding, static analysis and formal methods, testing, firmware security, DevSecOps, embedded cybersecurity and partitioning, with an assigned technical tutor.
Master’s in Critical Software and Firmware Security Engineering (DevSecOps/DO-178C/IEC 61508) — studying from Australia
Defence is one of Australia's largest engineering employers, with major programmes in land systems, naval platforms, aircraft and integrated systems managed through the Department of Defence. Land systems engineering supports armoured vehicles, weapons and logistics equipment, often through prime contractors and local industry partners. Industry involvement is strongly encouraged through the Defence industry policy framework. Engineers work on sustainment, capability development, systems integration and safety assurance, typically in Canberra, Adelaide, Melbourne and regional defence precincts.
Fees for Australia: A$15,800 (AUD), with instalments and employer sponsorship available.
Relevant bodies in Australia
Typical roles
Questions from Australia
How does defence engineering recognition work in Australia?
Defence engineering in Australia is largely run through the Department of Defence and its industry partners, which set their own security clearance and qualification requirements. Engineers Australia is the professional body for accreditation. SEIUM's private qualifications are not accredited by these bodies, so recognition is for employers or the relevant body to decide.
Which Australian employers hire in defence and land systems?
Australia has defence prime contractors, the Department of Defence, and specialist land systems firms. Many of these roles require Australian security clearances, which depend on citizenship and background checks rather than course completion. Ask employers how they weigh private qualifications against experience and clearance requirements.
Is the course manageable with a job, and does it need a visa?
The programmes are 100% online and taught in English, so you can study from Australia without a student visa. Specialist courses take 300 hours, diplomas 800 and master's 1,900. An assigned technical tutor supports you, fees are payable in instalments, and employer sponsorship may be possible.
Take the controls.
Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Apply DO-178C, IEC 61508 and ISO 26262 to software development.
Write code that complies with secure coding standards.
Use static analysis and formal methods in verification.
Plan testing with structural coverage criteria.
Protect firmware through secure boot and signed updates.
Integrate DevSecOps practices compatible with certification.
Carry out cybersecurity threat analyses of embedded systems.
Who it's for
- Safety-critical software engineers in aerospace, automotive or rail.
- Software verification engineers working on coverage, analysis and testing.
- Firmware security engineers protecting embedded devices.
- DevSecOps engineers adapting pipelines to certification requirements.
- Software certification specialists preparing DO-178C or IEC 61508 evidence.
- Embedded cybersecurity engineers applying IEC 62443, DO-326A or ISO/SAE 21434.
- Engineering or science graduates aiming to enter the aerospace and defence sector.
What you'll work with
- RTCA DO-178C (software considerations in airborne systems)
- IEC 61508 (functional safety of E/E/PE safety-related systems)
- ISO 26262 (road vehicle functional safety)
- IEC 62443 (industrial automation and control systems security)
- RTCA DO-326A (airworthiness security process)
- ISO/SAE 21434 (road vehicle cybersecurity engineering)
- MISRA C:2023 (C coding guidelines for critical systems)
- ARINC 653 (avionics application partitioning)
- Polyspace
- Frama-C
- LDRA Testbed
- Cppcheck
- GitLab CI
12 modules · 1900 h
1.1Safety-critical and mission-critical systems1.2Differences between software, firmware and programmable logic1.3Software failure modes1.4Historical accidents: Therac-25 and Ariane 51.5SIL, ASIL and DAL integrity levels1.6V-model life cycle for critical software1.7Safety versus security1.8Sector regulatory framework1.9Professional responsibility1.10Case study: analysis of the Ariane 5 failure
2.1Structure and objectives of DO-178C2.2DAL levels A to E2.3Software plans: PSAC, SDP and SVP2.4High-level and low-level requirements2.5Traceability and verification2.6MC/DC structural coverage2.7Supplements DO-330, DO-331, DO-332 and DO-3332.8DO-254 for complex hardware2.9Interaction with the certification authority2.10Workshop: drafting a simplified PSAC
3.1Structure of IEC 615083.2SIL allocation and technical measures3.3Part 3: software requirements3.4ISO 26262 in automotive3.5EN 50716 in railways3.6IEC 62304 in medical devices3.7IEC 60880 in nuclear3.8Comparison between standards3.9Third-party certification3.10Practical exercise: IEC 61508-3 technique matrix by SIL
4.1MISRA C:2023 and MISRA C++4.2SEI CERT C and C++4.3Safe languages: Ada, SPARK and Rust4.4Memory management and overflows4.5Safe concurrency4.6Defensive programming4.7Code reviews4.8Complexity metrics4.9Code documentation4.10Lab: fixing MISRA violations with Cppcheck
5.1Static data-flow analysis5.2Abstract interpretation: Polyspace and Astrée5.3Deductive verification with Frama-C5.4SPARK Ada and proof of absence of run-time errors5.5Model checking with CBMC5.6Formal specification with TLA+5.7Integration into the certification process5.8False positives and findings management5.9Tool qualification under DO-3305.10Practical exercise: verifying a function with Frama-C WP
6.1Unit, integration and system testing6.2Requirements-based testing6.3Statement, decision and MC/DC coverage6.4On-target and simulator testing6.5Robustness and boundary value testing6.6Interface fuzzing6.7Automated regression testing6.8LDRA, VectorCAST and gcov tools6.9Verification reports6.10Lab: measuring MC/DC coverage
7.1Embedded firmware architecture7.2Secure boot and chain of trust7.3Hardware roots of trust: TPM and TEE7.4Firmware signing and encryption7.5Secure OTA updates7.6Protection against side channels7.7Secure debugging and JTAG7.8Firmware binary analysis7.9Firmware vulnerability management7.10Practical exercise: secure boot with MCUboot
8.1Continuous integration with certification requirements8.2Pipelines with static analysis and testing8.3Configuration management and baselines8.4SBOM and third-party component management8.5Dependency and CVE scanning8.6Containers and reproducible environments8.7Artefact signing and SLSA8.8DevSecOps metrics8.9Balancing agility and certification8.10Workshop: GitLab CI pipeline with MISRA analysis
9.1IEC 62443 for industrial systems9.2DO-326A and DO-356A in aeronautics9.3ISO/SAE 21434 in automotive9.4TARA threat analysis9.5STRIDE threat modelling9.6Product cybersecurity requirements9.7Penetration testing of embedded systems9.8EU Cyber Resilience Act9.9Post-market vulnerability management9.10Case study: TARA of an ECU
10.1Real-time operating systems10.2ARINC 653 and space-time partitioning10.3Hypervisors for critical systems10.4WCET execution time analysis10.5Multicore platforms and CAST-32A10.6Inter-core interference10.7Mixed-criticality systems10.8Operating system certification10.9Kernel security10.10Lab: real-time schedulability analysis
11.1Certification planning11.2Software quality management11.3SOI stage audits11.4Software supplier management11.5Tool qualification11.6Problem and change management11.7Life-cycle documentation11.8Certification costs11.9Managing multidisciplinary teams11.10Case study: SOI audit plan
12.1Definition of the critical component12.2Safety and threat analysis12.3Software life-cycle plan12.4Design and implementation12.5Static and formal verification12.6Testing and coverage12.7Certification file12.8Conclusions and future work12.9Master's Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within the intake, so you can combine it with your job.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Polyspace, Frama-C, LDRA Testbed, Cppcheck and GitLab CI, in free, academic or evaluation versions. Testing is studied through real procedures for static and formal code verification, MC/DC structural coverage measurement and threat analysis of embedded systems. Assessment is continuous by module, plus the final Master's Thesis.
Standards covered: RTCA DO-178C, IEC 61508, ISO 26262, IEC 62443, RTCA DO-326A, ISO/SAE 21434, MISRA C:2023, ARINC 653.
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- University degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- Internet connection and a computer capable of running the programme software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with Polyspace, Frama-C, LDRA Testbed, Cppcheck and GitLab CI, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme software, and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in Ballistic Protection, APS and Multispectral Signature Management Engineering
Online master's programme of 1,900 hours in ballistic protection, APS and multispectral signature management engineering, with 12 modules covering protection materials, STANAG 4569 and AEP-55 testing,…
Master’s in Sonar and Underwater Acoustics
Online master's programme of 1,900 hours in sonar and underwater acoustics: 12 modules covering physical acoustics, ocean propagation, transducers, arrays and beamforming, sonar signal processing, detection,…
Master’s in Advanced Materials for Ballistic Protection
Online master's programme of 1,900 hours in advanced materials for ballistic protection, with 12 modules covering impact mechanics, dynamic material behaviour, metals, ceramics, fibres and composites,…
More in Defense, Military Engineering & Land Systems
All Defense, Military Engineering & Land Systems programmes → · How to apply · Fees & financing · Scholarships