The importance of robust passwords
Robust password is computationally impossible to crack using automated password cracking tools. To create one, user must use a variety of symbols that include both lowercase and capital letters, numbers and special characters. In addition to that a password must be at least 12 characters long – the shorter it is the faster it is to crack. It is recommended to create a unique password for each service and use a password manager that could store all the unique passwords. When logging in it is advisable to enable the “Show password” feature as it would help prevent entering incorrect password and having to reset it thus creating a vulnerability. It would also prevent the user being locked out of the account as many companies that follow NIST cybersecurity guidelines lock out the user after several unsuccessful login attempts. Wherever possible multi-factor authentication should be enabled when creating a password to complement a password with a code sent to your phone or another method. Password resets should be made after a security incident or once a year. More frequent password changes may encourage users to introduce only minor changes to the password, which compromises security as hackers are aware of this tendency and exploit it. On the administrator side, it is recommended to store user passwords as hashes in the database. It is also advisable that the passwords are salted before hashing, which involves adding extra characters to the password prior to it being hashed.
To give an example of a robust password I generated the following password using LastPass service
Z'n4--ye9w1(
I chose it because it has a combination of lowercase and capital letters, numbers and special characters and is 12 characters long.
I have tested this password on the Security.org website and the service estimated that it would take a computer about 400 000 years to crack.
When data is stored or sent in plain text it could be easily read by or intercepted by threat actors. To ensure data confidentiality encryption at rest and in motion is used. This is especially important for authentication procedures when passwords are being sent over the network and for personally identifiable information or personal health information being stored in a database. Email communications should also be encrypted, an example of an email client that uses end-to-end encryption is ProtonMail.
Below is the screenshot of the ProtonMail mobile application.
Comments
Post a Comment