User Authentication Flashcards
Name the three general credential categories, also called authentication factors.
Knowledge
Ownership
Inherence (biometrics)
Give examples for a wide-spread commercial 2-factor authentication system, and name the involved factors.
ATM (card + pin)
Google (password + phone)
User authentication credentials
A credential is the ‘thing’ used for authentication.
Credential categories (“factors”) and typical examples: 1.Knowledge-based (“something you know”): fex Passwords
- Ownership-based (“something you have”): Fex Tokens
- Inherence-based (“something you are/do”): Fex Biometrics, physiological, biometric characteristics, behavioural biometric characteristics
4.Secondary channel (a channel you control): SMS, email, etc.
Combinations, called multi-factor authentication
How is passwords stored? (Hash function)
Passwords are typically stored as hash values.
A hash function is easy to compute but hard to invert.
The authentication function first computes the hash of received password, then compares against the stored hash value.
3 strategies for cracking passwords
Cracking hashed passwords:
The attacker hashes a possible password and checks if the hash value is found in the password file. The password has been cracked if the hash value is found.
Brute-force search:
Hash and check all possible passwords (a powerful GPU computer can test passwords up to 8 characters in 1 day)
Intelligent search:
- User names
- Names of friends/relatives
- Phone numbers
- Birth dates
- Dictionary attack
- Try all words from a dictionary
Password salting
Appending random data (salt) to a users password before hashing.
- In Unix: a randomly chosen integer from 0 to 4095.
- Different salt for each user
- Produces different hashes for equal passwords
- Prevents that users with identical passwords get the same password hash-value
- Increases the amount of work for hash precomputation
- Makes it necessary to compute new table for each user
- Makes hash tables and rainbow tables impractical for password cracking
BruteForce Attacks
The effort of bruteforce attacks depends on:
- The length and complexity of passwords
- The complexity of the hash algorithm
Bcrypt
Special hashing algorithm.
Has high memory consumption.
Scrypt
Special hashing algorithm.
Has a very high memory consumption.
Argon2
Currently the best password hashing function.
Password Do’s and Dont’s
Never send unprotected passwords in clear.
A password sent “in clear” can be captured during transmission, so an attacker may reuse it. An attacker setting up a fake server can get the password from the user (E.g. phishing attack).
Solutions to these problems include:
- Encrypted communication channel
- One-time passwords (token-based authentication)
- Challenge-response protocols
OTP Token
A one-time password (OTP) is type of password that is valid for only one use.
A OTP is a security technique that provides protection against various password-based attacks, specifically password sniffing and replay attacks.
It provides more enhanced protection than static passwords, which remain the same for multiple login sessions. OTP works through randomness algorithms that generate a new and random password each time they are used.
Comparison characteristics
False positives etc
Coming
E-authentication for e-Gov.
Trust in identity is a requirement for e-Government
Authentication assurance produces identity trust.
Authentication depends on technology, policy, standards, practice, awareness and regulation.
Common e-authentication frameworks allow cross-national and cross-organisational solutions that give convenience, cost savings and security.
RAU Norway 2008
Rammeverk for Autentisering og Uavviselighet(Framework for Authentication and Non-Repudiation)
RAU AAL-4: High authentication assurance
E.g. two-factor, where at least one must be dynamic, and at least one is provisioned in person RAU AAL-3: Moderate authentication assurance
E.g. OTP calculator with PIN provisioned by mail to user’s official address RAU AAL-2: Low authentication assurance
E.g. fixed password provisioned in person or by mail to user’s official address RAU AAL-1: Little or no authentication assurance :
E.g. Online self-registration and self-chosen password Norway has adopted eIDASin 2018 (RAU will no longer be used)