[Cryptography] Security Standard for Safety Critical Software

[Adrian McCullagh]

Darkpassenger wote:

afaik within some countries and regions there are organizations that 
have procedures
to examine a software for critical applications and gives series of 
evaluations for
"security level" of the target . like Common Criteria , CC , and AEL 
levels in the
U.S or there are many MIL-STDs in NATO area..

is this what you are talking about ?

_________________________________


No that is not what I am talking about.  I am fully aware of the Common Criteria (IEC 15408) and Target of Evaluation and EAL (Evaluated Assurance Levels).


What I am looking for is:  “Is there a specific standard dealing with security for safety critical software”.


I am aware of the Software Engineering Institutes work on Capability Maturity Models.


It appears to me that presently there is not a standard dealing with the development of security from the ground up in the development of Safety Critical Software.


I am simply asking the question as to whether there is such a standard and if so where I can get a copy of it.






Dr. Adrian McCullagh 
Ph.D. LL.B.(Hons) B. App. Sc. (Computing)
ODMOB Lawyers 
Mobile 0401 646 486
Skype.   Admac57
E: ajmccullagh57 at gmail.com
E: amccullagh at live.com 
The contents of this email are confidential between the sender and the intended recipient. If you are not the intended recipient then no rights are granted to you because of this error and as such you are requested to promptly inform the sender of the error and to promptly destroy all copies of the email in your power, possession or control. The sender reserves all rights concerning this email and its contents including any privilege, copyright and confidentiality associated with this email. Even though an email signature block has been appended to this email, and notwithstanding the Electronic Transactions Act (Qld) or the Electronic Transactions Act (Cth), the signature block does not exhibit the senders intention to be bound by an offer previously sent by the intended recipient, unless the email in its body specifically indicated that the sender hereby accepts such an offer previously sent by the intended recipient.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.metzdowd.com/pipermail/cryptography/attachments/20151023/82d92d54/attachment.html>