Navigation ...
|
|
|
Scientific Writing ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other Writing ...
|
|
|
|
|
|
Reference details
Author(s)
| Year
| Title
| Reference
| View/Download
|
Les Hatton | 2013f | Some reflections on software systems: Where does safety stop and security start ? | Keynote at IET , 16-Oct-2013 | IET-16-10-2013_SafetySecurity.pdf |
Synopsis and invited feedback
This work was or is being reviewed by domain-specific experts appointed independently.
If you would like to provide feedback just e-mail me here.
Synopsis
| Invited Feedback
| Importance (/10, author rated :-) )
|
System safety has rightly been a mainstream part of software systems engineering for a long time. However, as most control systems were essentially closed in the early days, security has generally been treated as somebody else's problem. This situation has completely changed now for various reasons. First of all, embedded systems have grown massively in their resource requirements and frequently sit on top of a standard OS stack such as Linux. In other words, they look more and more like normal systems. Secondly, and partly resulting from the first point, they have become open to the outside world in some sense. The arguments in favour of this include compelling ones such as the logistics of patching software defects. Thirdly, while this has been going on, software security has become a major growth area in its own right in response to the very considerable increase in sophistication and intensity of attack vectors, both malicious and espionage related. An early warning shot of the confluence of these factors was the Stuxnet virus.
In this talk, I will muse over system properties in general before concentrating on the rapidly growing overlap between software system safety and software system security. Its not particularly good news. | None yet | 8 |
Related links
Related papers and links
|
Sorry, no links registered in database yet. |
Auto-generated: $Revision: 1.64 $, $Date: 2022/05/20 08:41:34 $, Copyright Les Hatton 2001-
|