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
83
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
38
The first few milliseconds of HTTPS
jaytaph
0
210
Paradoxes and theorems every developer should know
jaytaph
0
260
Paradoxes and theorems every developer should know
jaytaph
0
600
The first few milliseconds of HTTPS - PHPNW16
jaytaph
1
210
compiler_-_php010.pdf
jaytaph
0
96
Paradoxes and theorems every developer should know
jaytaph
0
220
Introduction into interpreters, compilers and JIT
jaytaph
1
270
Paradoxes and theorems every developer should know
jaytaph
1
870
Other Decks in Technology
See All in Technology
LLM とプロンプトエンジニアリング/チューターをビルドする / LLM, Prompt Engineering and Building Tutors
ks91
PRO
1
210
ElixirがHW化され、最新CPU/GPU/NWを過去のものとする数万倍、高速+超省電力化されたWeb/動画配信/AIが動く日
piacerex
0
110
Рекомендации с нуля: как мы в Lamoda превратили главную страницу в ключевую точку входа для персонализированного шоппинга. Данил Комаров, Data Scientist, Lamoda Tech
lamodatech
0
380
All You Need Is Kusa 〜Slackデータで始めるデータドリブン〜
jonnojun
0
140
【日本Zabbixユーザー会】LLDを理解するときの勘所 〜LLDのある世界を楽しもう!〜
yoshitake945
0
120
Webアプリを Lambdaで動かすまでに考えること / How to implement monolithic Lambda Web Application
_kensh
7
1.2k
Spice up your notifications/try!Swift25
noppefoxwolf
2
350
7,000名規模の 人材サービス企業における プロダクト戦略・戦術と課題 / Product strategy, tactics and challenges for a 7,000-employee staffing company
techtekt
0
260
古き良き Laravel のシステムは関数型スタイルでリファクタできるのか
leveragestech
1
640
入社後SREチームのミッションや課題の整理をした話
morix1500
1
250
SREが実現する開発者体験の革新
sansantech
PRO
0
280
Amazon CloudWatch Application Signals ではじめるバーンレートアラーム / Burn rate alarm with Amazon CloudWatch Application Signals
ymotongpoo
5
310
Featured
See All Featured
ReactJS: Keep Simple. Everything can be a component!
pedronauck
666
120k
Site-Speed That Sticks
csswizardry
5
480
The Cult of Friendly URLs
andyhume
78
6.3k
Embracing the Ebb and Flow
colly
85
4.6k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
41
2.2k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
A better future with KSS
kneath
239
17k
Raft: Consensus for Rubyists
vanstee
137
6.9k
Speed Design
sergeychernyshev
29
880
GraphQLの誤解/rethinking-graphql
sonatard
71
10k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
12k
The Invisible Side of Design
smashingmag
299
50k
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