Implementing authentication controls
Authentication for mobile applications can occur from both server side and client side. IoT mobile applications can make use of both design patterns although each have their own risk considerations when implementing in production. This section will discuss some of these risks as well as best practice design implementations for server and client-side authentication.
How to do it...
General application principles for securely authenticating users apply to mobile applications as well. A great reference is OWASP's Authentication Cheat Sheet (https://www.owasp.org/index.php/Authentication_Cheat_Sheet). Common authentication controls and best practices consist of:
- Proper password strength controls
- Password length
- 10 characters or more
- Password complexity policies
- 1 uppercase, 1 lowercase, 1 digit, 1 special character, and disallowing 2 consecutive characters such as 222
- Enforce password history
- Disallow the last three used passwords (password reuse)
- Password length
- Transmitting...