System Safety Engineering employs a top-down approach that helps developers incorporate safety features that will ensure that an acceptable, or at worst tolerable, level of safety is achieved. Safety assumes a dumb environment where if an internal or external event happens the system will react in a repeatable way. So a safety function can be relied on to address a set of input conditions. Furthermore, very rare input conditions remain very rare and therefore can be addressed using a risk based framework.
There is growing awareness that this model for safety may be flawed when it comes to the potential for cyber security issues to affect safety. Security attackers are potentially actively searching the input space for a system to find input sets that may have safety implications, thus making these input conditions less rare. They may use mechanisms such as fail-safe to generate denial of service, or put the system into an unsafe state. Once they can do this for a single example of the system they can potentially do it for all examples of that system.
Considerable work is ongoing in academic and industrial practitioner communities to address these issues. This course addresses these issues. It aims to
By the end of this course you will be able to:
This course is suitable for:
A basic understanding of system safety terminology and lifecycle via prior learning or industrial experience. It is useful for you to have taken our Foundations of System Safety Engineering course, but if you have not, please email us with your details so we can check your suitability for taking this course.
The course takes place over one week at the University of York. This week consists of a mixture of lectures and practicals, but we expect you to put in around 30 hours of private study.
Over the week, there will be a series of lectures and a number of case studies. The case studies give you the chance to work through an example to reinforce your learning from the lectures. This is also a chance to gain other insights from the experience and knowledge of other delegates. You will also be able to call on the experience and knowledge of our specialised teaching staff during these sessions.
The course ends with an assessed exercise, which you have the option of completing. It takes approximately 35 hours in addition to the scheduled teaching time and can be completed on or off site. All assessed exercises are open (so you won't take an exam in supervised conditions), and comprise a report, case study, or documented piece of software.
If you choose to take and pass your assessment, your results can count towards the completion of the MSc in Safety Critical Systems Engineering. Our MSc in Safety Critical Systems Engineering is an accredited course, recognised by both the BCS, the Chartered Institute for IT and the Institution of Engineering and Technology (IET) for the purposes of partial fulfilment of the educational requirement for CEng registration.
These details are not yet available - recommended reading will be published shortly.
|Charles P. Pfleeger and Shari L. Pfleeger||Security in computing||Prentice Hall||2007|
|Dieter Gollmann||Computer security||Wiley||2006|
|Ross J. Anderson||Security engineering: a guide to build dependable distributed systems||Wiley||2001|
Make sure you book your place for the next course w/c 27th April 2020.
Before booking please read our Booking Conditions (PDF , 104kb).
To book your place, please complete the booking form: CPD Booking Form (MS Word , 92kb) and the accompanying payment form: CPD Payment Form 18/19 (MS Word , 50kb) and return to Heather Taylor, our CPD & Postgraduate Programmes Administrator. Payment for your place can be made via credit/debit card or invoice (please email Heather Taylor).
If you have any queries, please contact Heather Taylor, our course administrator or call 01904 325536.