Data rights, such as the right to retrieve, print or update information in a database. Methods for user identification and authentication 16.1.7. Authentication is the process by which a claimed identity is verified and access permissions are confirmed before access is granted. 16.1.8. User authentication can be achieved by various means, including biometrics, cryptographic tokens, software tokens, passphrases, passwords and smartcards. Where this manual refers to passwords it equally applies to passphrases. 16.1.9. Authentication mechanisms are invariably described in terms of factors of authentication as follows: 1. Something you have (preferably NOT the device itself but a SEPARATE authentication device such as a token, RFID card or smartcard). This is also known as the possession factor; 2. Something you know such as a PIN, One-Time Password (OTP), reusable password, pattern or other component of a standard authentication mechanism. This is also described as the knowledge factor; 3. Something you are (biometrics of various types). This is also described as theinherence factor. 16.1.10. Commonly used two factor authentication schemes are combinations of physical presence, a token and a PIN/Password. Biometrics are less commonly used on mobile or remote systems. Software Tokens 16.1.11. Software Tokens, Soft Tokens or “softokens” are typically applications that run on mobile devices such as smart phones, tablets, laptops other workstations. They are sometimes also known as “virtual tokens”. When soft tokens are used the device itself then becomes the “possession factor”. Functionality may include: Transfer between devices by the user. Use of Quick Response (QR) codes to facilitate deployment. Manages international time zones changes when travelling. 16.1.12. The soft token (secret) is vulnerable to any attacker that can gain full access to the device through theft, loss or download of malware. This is not as secure as a separate hardware token which is more resistant to attack and tampering. Passwords and Password storage 16.1.13. Password length and composition (character type) has been found to be a primary factor in characterizing password strength [Strength][Composition]. Passwords that are too short yield to brute force attacks as well as to dictionary attacks using words and commonly chosen passwords. 16.1.14. The minimum password length that should be required depends to a large extent on the threat model being addressed. Online attacks where the attacker attempts to log in by guessing the password can be mitigated by limiting the rate of login attempts permitted. In order to prevent an attacker (or a persistent claimant with poor typing skills) from easily inflicting a denial-of-service attack on the subscriber by making many incorrect guesses, passwords need to be complex enough that the rate limiting does not occur after a modest number of erroneous attempts, but does occur before there is a significant chance of a successful guess. 16.1.15. Offline attacks are sometimes possible when one or more hashed passwords are obtained by the attacker through a database breach. The ability of the attacker to determine one or more users' passwords depends on the way in which the password is stored. Commomly, passwords are salted with a random value and hashed, preferably using a computationally expensive algorithm. Even with such measures, the current ability of attackers to compute many billions of hashes per second with no rate limiting requires passwords intended to resist such attacks to be orders of magnitude more complex than those that are expected to resist only online attacks. 16.1.16. Users should be encouraged to make their passwords as lengthy as they want, within reason. A reasonable upper limit is 64 characters. 16.1.17. Since the size of a hashed password is independent of its length, there is no reason not to permit the use of lengthy passwords (or passphrases) if the user wishes. Extremely long passwords (perhaps megabytes in length) could conceivably require excessive processing time to hash, so it is reasonable to have some limit. Password Character Set Limitations 16.1.18. Limitations set on credential or password length or on the use of special characters can facilitate brute-force attacks. 16.1.19. A brute-force attack is a trial-and-error method used to discover information such as a user password, a personal identification number (PIN), or to decrypt encrypted data. Automation can be used to generate a large number of consecutive guesses. Similar methods are used by security analysts to test an organisation's system security, often described as penetration testing. 16.1.20. Organisations should not permit the use of short or no-length passwords, restrict the use of character sets or apply encoding restrictions on entry or storage of credentials. 16.1.21. Password length, character variation and use of symbols, numbers and special characters including emoticons will increase the resistance of hash values to attack. These practices will assist in limiting a variety of malicious attacks on IT systems. Hashing 16.1.22. Hashing is a one-way function where data is mapped to a fixed-length value. It also protects a password by producing ciphertext. Contrast hashing with encryption is a two-way function where the data can be encrypted and decrypted. 16.1.23. In general, applications use secure hashing algorithms for: Password Protection; Integrity checking: e.g. a tamper-evident seal for a file (checksum); Authentication: e.g. Digital signatures, Hashed Message Authentication Codes (HMAC) and pseudo-random number generation (PRNG). 16.1.24. Very large passwords can create system performance issues and choke points. Password hashing reduces all passwords to a fixed length, improving efficiency and reducing the volume of credential traffic. 206 Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents