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
46
The first few milliseconds of HTTPS
jaytaph
0
240
Paradoxes and theorems every developer should know
jaytaph
0
300
Paradoxes and theorems every developer should know
jaytaph
0
680
The first few milliseconds of HTTPS - PHPNW16
jaytaph
1
240
compiler_-_php010.pdf
jaytaph
0
120
Paradoxes and theorems every developer should know
jaytaph
0
250
Introduction into interpreters, compilers and JIT
jaytaph
1
330
Paradoxes and theorems every developer should know
jaytaph
1
920
Other Decks in Technology
See All in Technology
どうなる Remix 3
tanakahisateru
2
350
フライトコントローラPX4の中身(制御器)を覗いてみた
santana_hammer
1
140
手を動かしながら学ぶデータモデリング - 論理設計から物理設計まで / Data modeling
soudai
PRO
11
3.3k
LINE公式アカウントの技術スタックと開発の裏側
lycorptech_jp
PRO
0
350
内部品質・フロー効率・コミュニケーションコストを悪化させ現場を苦しめかねない16の組織設計アンチパターン[超簡易版] / 16 Organization Design Anti-Patterns for Software Development
mtx2s
2
190
QAセントラル組織が運営する自動テストプラットフォームの課題と現状
lycorptech_jp
PRO
0
350
マーケットプレイス版Oracle WebCenter Content For OCI
oracle4engineer
PRO
3
1.3k
開発者が知っておきたい複雑さの正体/where-the-complexity-comes-from
hanhan1978
6
2.4k
Design and implementation of "Markdown to Google Slides" / phpconfuk 2025
k1low
1
390
こんな時代だからこそ! 想定しておきたいアクセスキー漏洩後のムーブ
takuyay0ne
4
530
[mercari GEARS 2025] Keynote
mercari
PRO
0
160
ある編集者のこれまでとこれから —— 開発者コミュニティと歩んだ四半世紀
inao
1
240
Featured
See All Featured
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
253
22k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
Practical Orchestrator
shlominoach
190
11k
Keith and Marios Guide to Fast Websites
keithpitt
413
23k
Rebuilding a faster, lazier Slack
samanthasiow
84
9.3k
Principles of Awesome APIs and How to Build Them.
keavy
127
17k
Optimising Largest Contentful Paint
csswizardry
37
3.5k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
249
1.3M
Build your cross-platform service in a week with App Engine
jlugia
234
18k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
24
1.5k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
GraphQLの誤解/rethinking-graphql
sonatard
73
11k
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