Watch your door.-Ensure the security of the authentication mechanism (2)-Secure handling of sensitive information

The first thing to declare is that this article is purely an ignorant view of a little developer without foresight and knowledge, and is intended only for reference in Web system security.

1. Prerequisites

Implementing a secure authentication mechanism not only meets several key security goals at the same time, but also at the expense of other goals. such as ease of use, cost, and functionality.
We need to consider these factors in a comprehensive light:
The degree of security of the functions provided by the system;
User tolerance and acceptance of different types of validation controls;
Support a less-than-friendly interface requires the overall cost (convenience and security is often the two directions of a thing)
The value of the information or assets protected by the system.

2. Handling sensitive information securely

Some basic requirements, written down, can also be consulted later.
1. Secure all communication between client and server using well-known encryption technologies (such as SSL);
2. It is generally not necessary to use specific programmes to protect the transmission of data;
3. If there is a condition, start using HTTPS from loading the login form instead of using HTTPS when submitting the information;
4. You can only submit sensitive information to the server by using the Post method. Do not place sensitive information in URL parameters or cookies;
5. The sensitive information must not be returned to the client, even if the redirect parameter is not available;
6. Store sensitive information to prepare for the worst. If an attacker is able to access all the data in the application database, it is not easy to recover the original values of the sensitive information, such as using the SHA-256 function. (The fortress is often easily compromised from within);
7. In general, "Remember me" function should only remember the user name of this non-confidential data, but now in order to further improve user-friendliness, more and more passwords are stored in the "Remember Me" cookie, so the importance of the payment password and other passwords are increased ...
8. Change the password regularly (but there are also papers saying this is invalid, a matter of opinion)
9. Send sensitive information to new accounts with special requirements (batch create users, etc.), transfer in the safest possible form and set time limit (both client and server), require user to change password at first login (client to prompt, server to execute logically), And tell the user to delete the sensitive information (although it's useless in most cases, but what if it works?) ）
10. If the security requirements are high enough to use a soft keyboard or other variable, but then again, if the attacker has compromised the user's computer, theoretically, he can record anything on the computer, such as mouse activity, HTTPS forms and other behaviors.

Watch your door.-Ensure the security of the authentication mechanism (2)-Secure handling of sensitive information