AI summary by TwinMind
Why You Should Turn On Two Factor Authentication
Tom Scott
8m 12s
Reagan Nuclear Code Incident (1981)
- President Reagan shot by gunman in Washington DC, non-fatal
- "Biscuit" (nuclear codes card) went missing during medical emergency
- Small plastic card in opaque case with secret codes
- Used to identify president for nuclear weapon authorization
- Card recovery unclear: stuffed in shoe during trauma care OR seized by FBI as evidence for days
- Vice president had backup codes, so nuclear capability maintained
- Incident added Cold War instability
Three Factors of Authentication
- Computer systems identify users through three methods:
- Something you know
- Something you are
- Something you have
- Multi-factor authentication = gold standard (minimum 2 factors)
- ATM example: card (have) + PIN (know) = two-factor authentication
Something You Know (Knowledge Factor)
- Passwords: traditional login system
- Credited to Dr. Fernando Corbeto at MIT, 1960s
- Made sense when keyboard was only input device
- Alternative forms: PINs, signatures (pre-computer era)
- Vulnerabilities:
- Signatures can be forged
- Passwords leaked/intercepted via server hacks, keyloggers, shoulder surfing
- Personal anecdote: learned teacher's password in high school through shoulder surfing
Something You Are (Biometric Factor)
- Fingerprints and face recognition
- Advantages: difficult to intercept, proves person identity
- Disadvantages:
- System must trust reading device isn't compromised
- Cannot change if compromised (unlike passwords)
- Cannot pretend not to know (unlike passwords)
- Fourth factor consideration: "somewhere you are" (location-based)
- Credit card geographic anomaly detection
- Future AI behavior pattern recognition
- Panopticon surveillance societies
Something You Have (Possession Factor)
- Physical objects: bank cards, phones, literal keys
- Ideal for same physical location scenarios
- Remote verification challenges solved by smartphones
Remote Authentication Methods
- British bank card readers:
- Plug in card, reads secret code from chip
- Enter PIN + one-time code from bank
- Mathematical processing creates verification number
- Modern smartphone solutions:
- App notifications for authentication
- SMS codes (not ideal due to security vulnerabilities)
- SIM swapping attacks: criminals redirect phone numbers
- Authenticator apps:
- Generate one-time codes
- Store long secret code from server
- Combine with current time for different 6-digit numbers every minute
- Password phone knows but user doesn't
High-Security Physical Tokens
- USB/Bluetooth tokens for maximum security
- Google employee implementation: reduced phishing attacks to zero
- Automatic bank card reader equivalent with complex mathematics
- Direct communication with correct web server only
- No user input required = no accidental code sharing
- Requires actual physical token possession
Nuclear Code Authentication System
- All three factors implemented:
- Something you have: "biscuit" code card
- Something you know: memorized position of correct code among fake codes
- Something you are: surrounded by security apparatus and top-secret infrastructure
- Authentication limitations:
- Confirms identity only
- Cannot verify sanity, coercion, or deception
Modern Security Recommendations
- Enable two-factor authentication on email and banking
- Authentication limitations remain:
- Won't prevent hacked company payment details
- Won't stop confidence tricks or MLM schemes
- Computers execute commands as given, not as intended
- Cannot prevent user from requesting harmful actions
- Authentication ensures identity verification, not decision quality
