As you have already responded very well from a technical point of view, I will reply from the UX point of view.
Why some systems require such strong passwords?
Because there’s a concern legitimate with the safety of users - and also with the business of the company. No matter what service you are offering (withdrawal of your own money or access to memes on Facebook, for example), if a user’s account is stolen that user will not be the only one having problems. The overall perception of the quality of the service will be affected in a short time, as the user will certainly share this occurrence with their peers. Moreover, while from the individual’s point of view the worst that can occur is the theft of your data/goods, from the company’s point of view the worst is the identity theft: by impersonating someone who is not, the meliante will have more facility to steal more users using social engineering (impersonating a Facebook friend, for example) and will help the problem grow exponentially.
The solution used then is to make unauthorized access as difficult as possible, even to the detriment of other qualities (further). As colleagues have already responded well, complex and larger passwords are statistically harder to guess and proven more difficult to break.
This would not make it difficult for the user to remember this password in a possible
back in the system?
Certainly. In the accepted reply it was commented that banks can allow themselves to provide short passwords because there are other (even physical) restrictions. Although that’s true, this is not motivation. This is another legitimate concern with users and business. A smaller password is potentially easier to remember, but the most important thing is that it’s faster to type it into the bank queue! Complex passwords require not only more complex (and expensive) equipment, but also more complex procedures. For example, the ATM numeric keypad occupies less physical space than an alphanumeric keypad; moreover, the user does not need to hold a SHIFT to enter a different character. That is, the bank’s concern is to make you wait less time in the queue because this is good for you and (mainly) for the bank, since it decreases the queues and allows the use by more customers.
In fact the ideal for a bank would not need any password, because any typo also generates delays (<ironia>
ah, yes, of course, let’s not forget the user, who would no longer need to remember anything</ironia>
). No wonder that even the Bank of Brazil now has Atms with fingerprint readers or palm...
Systems must force the user to create a strong password?
No, they shouldn’t. In fact my answer to that question is the suggestion to exchange a single word: Systems should auxiliary the user to create a strong password.
First of all, it is in the user’s interest that their profile, data and assets are kept safe, so that people naturally feel motivated to act to increase security. For example, you want more intrinsic motivation than being forced to change a password every 6 months, using a minimum size of 8 characters, at least 1 digit and 1 symbol, not being able to repeat the last 3 passwords used, and still continue using the service? (unfortunately it is a real case...). In other words, people tend to use the passwords that a company requires even if it makes their life hell. This makes me believe that if this process is facilitated, they will continue to have this interest (contrary to what may be believed there).
Secondly, it is already widely known that too complex passwords are bad not only for the user experience, but also for system security. If the user is forced to use a password difficult to remember (especially when the creation process is obscure for him), there are great chances of him annotate, reuse the same password in several different systems, and especially forget and need to change. Studies have shown, for example, that the forgetfulness of passwords does not result from age, as common sense may lead to believe, but to the amount of passwords used by the individual and the different contexts in which they are used (study reference: Passwords Usage and Human Memory Limitations: A Survey Across Age and Educational Background). In other words, the more passwords a person needs to remember, and the more out of context they use each of those passwords, the more people will forget the passwords and need to constantly change them.
So the ideal would be for designers to build the systems so that users are allowed to build passwords freely, but instructed to do so using real and meaningful sentences personally in the context of using the system. For example, users could be illustrated with a strong password for a literature website is not an excerpt from a Shakespeare book (which everyone can know), but a phrase of its own that translates as it sit down in relation to the service.
For example, consider the phrase, "The book I like best about George Orwell is 1984!". It is relatively easy to be remembered by the user because (1) it was he who chose it freely; (2) it is significant to the individual; and (3) it has a lot to do with the context of system use. One could argue that this reduces security because that information can be known by other people. But although this may be true, the phrase is sufficiently complex in the sense of the amount of permutations to make his divination enormously difficult exact. And in practice, this is what happens anyway: if the bookstore used the same tactics as the bank, the password of this user would probably be only "1984". :)
It comes down to this image
– Don't Panic
I will make a comment just as a matter of opinion, this is not a matter of Ubeing andXperience, this is security issue, common user does not understand security issues, he does not know that "brute force" software can break weak passwords quickly, the reason this exists is because UX cannot keep up with a basic need of the modern world.
– Guilherme Nascimento
Because credit card you can make a purchase using only a 3-digit numeric password?
– Don't Panic
as a complement to the @Everson comment, I leave as a suggestion a good technique for generating passwords, is the diceware https://antivigilancia.org/wordpress/wp-content/uploads/2015/06/diceware_ptbr.pdf created by Arnold Reinhold and an instructive explanation https://theintercept.com/2016/12/29/passwords-faceis-para-Voce-memorizar-e-que-nem-a-nsa-can’t-unravel/
– Flávio Granato
My banks require multiple checks. The account or card which is something more complicated to pick up from someone. The password. A fixed or variable token for operations that go beyond query. A data check. Not counting usage pattern check. It is complicated to use bank authentication.
– Maniero
I also agree that it’s a question relative of UX. Acculturating people is great, but it creates little monsters: an absurdly common trap is that, lately, everything that requires authentication is "found the last cookie in the package". Long, strong passwords are great, but your rock forum really needs it demand passwords composed of symbols and numbers? Does your non-interacting recruitment site really need a double authentication factor? The fact is that there is a lot of exaggeration in this. Security is also functionality: it should be used where it matters, not by default.
– Charles Roberto Canato
With strong password you are not protecting the user but protecting the system or the organization. Passwords very strong however (16 char, alpha, special etc.) end up being weak 9my opinion) because the user notes somewhere , under the keyboard for example ....
– Motta
The security you want to implement depends solely on the risk you are willing to take.
– Intruso
Just to reinforce I ended up reading this today that in a way has a little to do with the theme: Know the device capable of unlocking any iPhone 7
– Marconi