Conclusion
Authentication methods. Description, uses and stakes
Article REF: H5535 V2
Conclusion
Authentication methods. Description, uses and stakes

Author : Pascal THONIEL

Publication date: April 10, 2017 | 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?

5. Conclusion

In the final analysis, there are no good or bad strong authentication methods. What should be definitively banned is weak authentication using static IDs and passwords, when the security stakes are high. What should be avoided is offering average authentication solutions (e.g. 2-factor authentication via SMS) and passing them off as strong authentication. It is urgent that certain Internet players use their budget to deploy and implement genuine strong authentication solutions, rather than spending it on communication to extol the hypothetical security of weak or average solutions.

The choice of a strong authentication method must first and foremost depend on its use and context. What's good for controlling direct access to equipment or premises is not necessarily good for controlling remote access over a network such as the Internet. And vice versa. The level of...

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

"Security of information systems"

( 86 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