Conclusion
Automatically check safety protocols
Article REF: RE95 V1
Conclusion
Automatically check safety protocols

Authors : Yohan BOICHUT, Pierre-Cyrille HÉAM, Olga KOUCHNARENKO

Publication date: October 10, 2007 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

6. Conclusion

The quality/reliability approach is not as demanding in IT as it is in fields such as mechanics. Selling buggy software with a signed license releasing the programmer from any liability in the event of damage caused by the software doesn't frighten any publisher, whereas it would seem outrageous to buy a microwave oven or a car. While this can be explained in part by the multiplicity of media and possible interactions between software and hardware products, the trend is changing, particularly with regard to so-called critical software, i.e. software for which a flaw could have significant or serious human or financial consequences. This is the case for embedded computing in civil or military aerospace, or for information security (and therefore indirectly for commerce). Security protocols fall into the latter category, and the aim of the AVISPA platform is to successfully meet this need...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Article included in this offer

"Networks and Telecommunications"

( 170 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details