Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
WTF, 2FA!? Y U NO PROTECT ME?
Search
Christine
April 05, 2019
Technology
0
85
WTF, 2FA!? Y U NO PROTECT ME?
Two factor authentication the worst, the best, and everything in-between.
Christine
April 05, 2019
Tweet
Share
More Decks by Christine
See All by Christine
One does not simply add MFA
tech_christine
0
66
Listening - Your Communication Superpower
tech_christine
0
220
Hanami 2.0 and You
tech_christine
1
280
ONE DOES NOT SIMPLY ADD MFA
tech_christine
0
380
One does not simply add MFA
tech_christine
0
210
MFA_Petfriendly.pdf
tech_christine
0
220
Hack Your Brain - Improve yourself and your work
tech_christine
0
600
A tale of two sides of 2FA
tech_christine
0
540
A tale of two sides of 2FA
tech_christine
0
580
Other Decks in Technology
See All in Technology
LangfuseでAIエージェントの 可観測性を高めよう!/Enhancing AI Agent Observability with Langfuse!
jnymyk
0
170
Langchain4j y Ollama - Integrando LLMs con programas Java @ Commit Conf 2025
deors
1
130
テキスト解析で見る PyCon APAC 2025 セッション&スピーカートレンド分析
negi111111
0
280
JPOUG Tech Talk #12 UNDO Tablespace Reintroduction
nori_shinoda
1
120
SREの視点で考えるSIEM活用術 〜AWS環境でのセキュリティ強化〜
coconala_engineer
1
260
Lightdashの利活用状況 ー導入から2年経った現在地_20250409
hirokiigeta
2
270
20250413_湘南kaggler会_音声認識で使うのってメルス・・・なんだっけ?
sugupoko
1
400
Zabbixチョットデキルとは!?
kujiraitakahiro
0
180
はてなの開発20年史と DevOpsの歩み / DevOpsDays Tokyo 2025 Keynote
daiksy
5
1.4k
7,000名規模の 人材サービス企業における プロダクト戦略・戦術と課題 / Product strategy, tactics and challenges for a 7,000-employee staffing company
techtekt
0
260
AIエージェントの地上戦 〜開発計画と運用実践 / 2025/04/08 Findy W&Bミートアップ #19
smiyawaki0820
26
8.5k
Стильный код: натуральный поиск редких атрибутов по картинке. Юлия Антохина, Data Scientist, Lamoda Tech
lamodatech
0
430
Featured
See All Featured
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
Done Done
chrislema
183
16k
Reflections from 52 weeks, 52 projects
jeffersonlam
349
20k
Learning to Love Humans: Emotional Interface Design
aarron
273
40k
Music & Morning Musume
bryan
47
6.5k
Why You Should Never Use an ORM
jnunemaker
PRO
55
9.3k
StorybookのUI Testing Handbookを読んだ
zakiyama
29
5.6k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
Designing Dashboards & Data Visualisations in Web Apps
destraynor
231
53k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2k
Art, The Web, and Tiny UX
lynnandtonic
298
20k
Transcript
@tech_christine WTF, 2FA!? Y U NO PROTECT ME? Two factor
authentication the worst, the best, and everything in-between
None
@tech_christine
None
@tech_christine Back to the beginning
@tech_christine What was the hacker up to? Calling your mobile
provider
@tech_christine Still on the phone with your mobile provider... Using
social engineering
@tech_christine And now they have all the access... Sim swap/sim
hijacking
@tech_christine
“ @tech_christine We learned that SMS-based authentication is not nearly
as secure as we would hope, and the main attack was via SMS intercept Christopher Slowe Reddit chief technology officer and founding engineer August 2018
@tech_christine What is authentication? The process of verifying that someone
or something is the actual entity that they claim to be. - OWASP.org (these people know what they are talking about when it comes to security)
@tech_christine ... but what are the different factors of auth?
1 factor is knowledge (i.e. your password) 2 is the other method choice - Possession (token/soft token) - Identity (biometrics)
@tech_christine 2FA == 2SV == MFA 2FA = Two factor
authentication 2SV = Two Step verification MFA = Multi-factor authentication What about all those other acronyms...
@tech_christine Why didn't 2FA help? •SMS was used •2FA wasn't
even enabled
@tech_christine •Most common method •Most compromised •Not recommended by NIST
since 2016 SMS
@tech_christine Let's figure out all the ways SMS can be
hacked... 1. Sim-swap (aka what just happened to us) 2. Port-out scam 3. Brute force on the application itself
@tech_christine Time-based One Time Password aka App based aka soft
token •Authy •Google Authenticator •1Password TOTP
@tech_christine •Associated with the certain authorized devices •Not visible on
a locked phone screen Push Based Authentication
@tech_christine Token based Physical keys that can auth •USB drive
•near-field communication •Many use U2F (Universal 2nd Factor)
What would you change now?
@tech_christine So what could you have changed? •Setting up with
a VOIP number •Secure with alternate authentication method •Pin/password protect phone provider Keep on being @awesome
@tech_christine ...wait I lost my phone/app access/token Use a recovery
code Allows you access to application
@tech_christine More on recovery codes •Stored as hashes •One time
use •Shown only once
@tech_christine 2FA Implementation Best Practices • Rate limiting prevents brute
force attacks • Use a truncated exponential back-off algorithm
@tech_christine What is an exponential back-off algorithm?
@tech_christine Example in Ruby login_request if retries <= max_retries retries
+= 1 sleep (retries + rand(100)/1000) retry else raise "You've hit your max retries!" end
@tech_christine Get user buy-in Enforce authentication on all pages Users
with the most amount of privilege, 2FA is a requirement not optional
@tech_christine Now you are the info sec professional
None
@tech_christine Thank you Kernelcon and all the staff Tyson Reeder
for the final graphic(@tysondreeder) For references and further reading checkout https://christine-seeman.com/talks/