13
A B C D # Logins by User Joe to Machine Z Client System 0 5 10 15 20 25 30

# Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

  • Upload
    others

  • View
    1

  • Download
    0

Embed Size (px)

Citation preview

Page 1: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

A B C D

# Logins by User Joe to Machine Z

Client System

05

1015

2025

30

Page 2: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

Hour of User Joe's Logins to Machine Z

Hour of Day

Freq

uenc

y

0 5 10 15 20

02

46

810

Page 3: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

1 day of “crud” seen at ICSI (110K times)

Page 4: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)
Page 5: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)
Page 6: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)
Page 7: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)
Page 8: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

Adversary can fill the entire buffer with just a single connection!Policy 1: Restrict per-connection buffer to threshold (= ?)

Page 9: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

Adversary can fill the entire buffer with just a single connection!Policy 1: Restrict per-connection buffer to threshold (say 20KB)

Page 10: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

• Adversary can create multiple connections to exhaust the buffer!

• Policy 2: Do not allow a single host to create two connections with holes

Page 11: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

• Adversary attacks from distributed hosts! (zombies)– No connection can be isolated as adversary’s… all of them

look good

• Policy 3: Upon buffer exhaustion …– … Evict one buffer page randomly

and reallocate it to new packet– Kill the connection of the evicted page (mod details)

• And recover all of its pages

• If the buffer is large, then most evicted connections belong to the adversary– They fight an uphill battle!

Page 12: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)

• Suppose total 512 MB, 2KB page, 25KB/conn

Avg. Legitimate Buffer = 30 KB

Page 13: # Logins by User Joe to Machine Z · 20 25 30. Hour of User Joe's Logins to Machine Z Hour of Day Frequency 0 5 10 15 20 0 2 4 6 8 10. 1 day of “crud”seen at ICSI (110K times)