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
Sponsored
·
Ship Features Fearlessly
Turn features on and off without deploys. Used by thousands of Ruby developers.
→
Joshua Thijssen
August 19, 2012
Technology
2
100
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
58
The first few milliseconds of HTTPS
jaytaph
0
270
Paradoxes and theorems every developer should know
jaytaph
0
330
Paradoxes and theorems every developer should know
jaytaph
0
770
The first few milliseconds of HTTPS - PHPNW16
jaytaph
1
270
compiler_-_php010.pdf
jaytaph
0
140
Paradoxes and theorems every developer should know
jaytaph
0
280
Introduction into interpreters, compilers and JIT
jaytaph
1
360
Paradoxes and theorems every developer should know
jaytaph
1
950
Other Decks in Technology
See All in Technology
サイボウズ 開発本部採用ピッチ / Cybozu Engineer Recruit
cybozuinsideout
PRO
10
76k
Change Calendarで今はOK?を仕組みにする
tommy0124
1
120
Phase12_総括_自走化
overflowinc
0
1.7k
スケールアップ企業でQA組織が機能し続けるための組織設計と仕組み〜ボトムアップとトップダウンを両輪としたアプローチ〜
qa
0
350
TUNA Camp 2026 京都Stage ヒューリスティックアルゴリズム入門
terryu16
0
560
来期の評価で変えようと思っていること 〜AI時代に変わること・変わらないこと〜
estie
0
110
SaaSに宿る21g
kanyamaguc
2
180
CloudFrontのHost Header転送設定でパケットの中身はどう変わるのか?
nagisa53
1
210
ハーネスエンジニアリング×AI適応開発
aictokamiya
1
330
Datadog で実現するセキュリティ対策 ~オブザーバビリティとセキュリティを 一緒にやると何がいいのか~
a2ush
0
160
Blue/Green Deployment を用いた PostgreSQL のメジャーバージョンアップ
kkato1
0
150
Kiro Meetup #7 Kiro アップデート (2025/12/15〜2026/3/20)
katzueno
2
260
Featured
See All Featured
YesSQL, Process and Tooling at Scale
rocio
174
15k
BBQ
matthewcrist
89
10k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.3k
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
360
GraphQLとの向き合い方2022年版
quramy
50
14k
KATA
mclloyd
PRO
35
15k
It's Worth the Effort
3n
188
29k
Principles of Awesome APIs and How to Build Them.
keavy
128
17k
Building Better People: How to give real-time feedback that sticks.
wjessup
370
20k
How STYLIGHT went responsive
nonsquared
100
6k
Collaborative Software Design: How to facilitate domain modelling decisions
baasie
0
170
Self-Hosted WebAssembly Runtime for Runtime-Neutral Checkpoint/Restore in Edge–Cloud Continuum
chikuwait
0
420
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