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
A history on security and how to win the battle
Search
Joshua Thijssen
August 19, 2012
Technology
2
85
A history on security and how to win the battle
Joshua Thijssen
August 19, 2012
Tweet
Share
More Decks by Joshua Thijssen
See All by Joshua Thijssen
RAFT: A story on how clusters of computers keep your data in sync
jaytaph
0
41
The first few milliseconds of HTTPS
jaytaph
0
220
Paradoxes and theorems every developer should know
jaytaph
0
280
Paradoxes and theorems every developer should know
jaytaph
0
630
The first few milliseconds of HTTPS - PHPNW16
jaytaph
1
220
compiler_-_php010.pdf
jaytaph
0
110
Paradoxes and theorems every developer should know
jaytaph
0
230
Introduction into interpreters, compilers and JIT
jaytaph
1
290
Paradoxes and theorems every developer should know
jaytaph
1
890
Other Decks in Technology
See All in Technology
ネットワーク保護はどう変わるのか?re:Inforce 2025最新アップデート解説
tokushun
0
150
Fabric + Databricks 2025.6 の最新情報ピックアップ
ryomaru0825
1
160
Lambda Web Adapterについて自分なりに理解してみた
smt7174
5
140
Understanding_Thread_Tuning_for_Inference_Servers_of_Deep_Models.pdf
lycorptech_jp
PRO
0
150
AIとともに進化するエンジニアリング / Engineering-Evolving-with-AI_final.pdf
lycorptech_jp
PRO
0
140
「Chatwork」の認証基盤の移行とログ活用によるプロダクト改善
kubell_hr
1
240
製造業からパッケージ製品まで、あらゆる領域をカバー!生成AIを利用したテストシナリオ生成 / 20250627 Suguru Ishii
shift_evolve
PRO
1
160
開発生産性を組織全体の「生産性」へ! 部門間連携の壁を越える実践的ステップ
sudo5in5k
0
530
プロダクトエンジニアリング組織への歩み、その現在地 / Our journey to becoming a product engineering organization
hiro_torii
0
140
AI専用のリンターを作る #yumemi_patch
bengo4com
4
2.1k
生成AI時代の開発組織・技術・プロセス 〜 ログラスの挑戦と考察 〜
itohiro73
1
380
Should Our Project Join the CNCF? (Japanese Recap)
whywaita
PRO
0
300
Featured
See All Featured
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
8
680
KATA
mclloyd
30
14k
Optimizing for Happiness
mojombo
379
70k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
500
Building Applications with DynamoDB
mza
95
6.5k
Done Done
chrislema
184
16k
Code Review Best Practice
trishagee
69
18k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
720
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
32
2.4k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
17
950
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
29
9.5k
Transcript
A history on security and how to win the battle...
Joshua Thijssen
Channeling and restricting flow
Sometimes channels don’t listen
Failure is always an option
Security is a business value
Security is a business value
Security is a business value
Let others take care of security
Let others take care of security
History of (computer) security
Security in the “old days”
I wasn’t kidding when I said: “old days”
5.25” high density disks
5.25” high density disks
Copying was a breeze
Copy protection
Copy protection
Let’s try dongles
NOPE!
8086 segmented memory layout
8086 segmented memory layout segment reg. 16-bit
8086 segmented memory layout segment reg. offset reg. 16-bit 16-bit
8086 segmented memory layout segment reg. offset reg. physical address
16-bit 16-bit 20-bit
8086 segmented memory layout segment reg. offset reg. << 4
physical address 16-bit 16-bit 20-bit
8086 segmented memory layout segment reg. offset reg. << 4
+ physical address 16-bit 16-bit 20-bit
07C0:0050 07C00 0050+ 07C50 8086 segmented memory layout segment reg.
offset reg. << 4 + physical address 16-bit 16-bit 20-bit
07C0:0050 07C00 0050+ 07C50 0000:7C50 00000 07C50+ 07C50 8086 segmented
memory layout segment reg. offset reg. << 4 + physical address 16-bit 16-bit 20-bit
07C0:0050 07C00 0050+ 07C50 0000:7C50 00000 07C50+ 07C50 007C:7490 007C0
07490+ 07C50 8086 segmented memory layout segment reg. offset reg. << 4 + physical address 16-bit 16-bit 20-bit
8086 segmented memory layout segment reg. offset reg. << 4
+ physical address 16-bit 16-bit 20-bit
386 protected memory layout + descriptor directory entry page table
entry physical address directory page offset cr3 gdt / ldt page directory page table page frame linear address descriptor table selector offset 32-bit 16-bit
None
None
Ring 0 Kernel
Ring 0 Kernel Ring 1 Device drivers
Ring 0 Kernel Ring 1 Device drivers Ring 2 Device
Drivers
Ring 0 Kernel Ring 1 Device drivers Ring 2 Device
Drivers Ring 3 Applications
Security today
The weakest link
Humans
it is much easier to trick someone into giving a
password for a system than to spend the effort to crack into the system -- K. Mitnick
Raising awareness on browsers
It’s a trap!
We’re curious
People are resourceful
Weird hobby’s
Weird hobby’s
00710022211101015511130102359000000000
00710033308171115011231111700000000000
00710033308171115011231111700000000000 00710022211101015511130102359000000000
00710033308171115011231111700000000000 00710022211101015511130102359000000000
00710022211101015511130102359000000000 00710033308171115011231111700000000000
00710044401011200001231122359000000000
None
Magnetic card reader/writer: $ 250
Magnetic card reader/writer: $ 250 Parking costs per night: $40
Magnetic card reader/writer: $ 250 Parking costs per night: $40
Free parking: priceless
How can we cure this problem?
We need to implement REAL security, not fake.
How do we win the war? How do we win
the war?
If we as developers have to keep thinking about security,
we will lose...
We need to deflect *EVERY* attack, They only need *ONE*
to win...
99.999% of all programmers are NOT trained or have the
capability to identify security threats. The other 0.001% will not be able to identify them ALL OF THEM ALL THE TIME.
A day in the life of a PHP programmer...
$result = mysql_query('SELECT * FROM users WHERE username="'.$_GET['username'].'"');
You should use mysql_real_escape_string!
No, you shouldn’t!
You just put a developer who wasn’t aware of security
issues, in charge of security...
Let others handle security (PDO)
There is no (quick) solution.
There is no (quick) solution. but we have to change
the way we deal with security radically,
There is no (quick) solution. but we have to change
the way we deal with security radically, by not dealing with security...
Let others take care of security
Any questions (maximum 5)?
Find me on twitter: @jaytaph Find me for development and
training: www.noxlogic.nl Find me on email:
[email protected]
Find me for blogs: www.adayinthelifeof.nl Thank you! http://joind.in/6853