by Nic Plum on Tuesday 10 April, 2012 - 21:25 GMT
This is something that has been bumbling around for some considerable time - safety and security. By that I whether there is something useful that an enterprise architecture view can be used for in the system safety and security disciplines.
On the face of it there is quite a bit of overlap. Both are ultimately concerned with risk inherent in a solution design which arises from threats (security) or hazards (safety). Both involve management with the aim to reduce the risk, threat or accident (safety) to an acceptable or tolerable target. I suspect also that security management also uses categories to classify acceptable severity or probability in much the same way that the various system safety management standards in defence do (MIL STD 882D, DEF STAN 00-56). Both also involve mitigation of risk by design - through structure, behaviour, or adherence to a normative process of some sort.
There are bound to be some differences, not the least of which is terminology. In the security area we seem to have constructs like:
- Threat poses Risk
- Threat exploits Vulnerability
- design aka TRAK:Resource (System, Software, Organisation, Job or Role) exposed to Risk (and subsequently that Risk is mitigated by the (improved) Resource or Function (of that Resource)
In the safety area we seem to have constructs like:
- Failure may present Hazard
- Hazard can cause Accident
- Accident poses Risk
- Resource exhibits Failure
and attributes such as probability, impact, severity.
Anyway it seems sensible to open up the debate so I’ve posted some thoughts in the forums within the TRAK Viewpoints project site on Sourceforge. Something is definitely needed and my hunch is that there is so much overlap that it would be possible to create a Viewpoint that addresses the risk within a solution design. This may of course end up being two viewpoints depending on the concerns and therefore concepts (metamodel stereotypes) and relationships involved. What is needed is more debate and input from those involved with system safety and system security - hence the post. As ever with TRAK the objective is economy so that we have something that is just or barely adequate to describe the concerns and concepts involved and no more.
- DEF STAN 00-56/4 Part 1 / Part 2 Safety Management Requirements For Defence Systems. [registration needed to access]
- MIL STD 882D. Department Of Defense Standard Practice For System Safety. February 2000
- Cabinet Office. Security Policy Framework. V7 October 2011.
- Security Ontology. Stefan Fenz.
- Secure Business Austria. Security Ontology.
- HIPAA Security Series. 6 Basics of Risk Analysis and Risk Management.
- Safety & Functional Safety. ABB Brochure 1SFC001008B0201.
Be the first to comment on this post.