59
Lessons Learned from a Breach Eric van Wiltenburg University of Victoria @e_vanwiltenburg

Lessons Learned from a Breach

  • Upload
    nijole

  • View
    21

  • Download
    0

Embed Size (px)

DESCRIPTION

Lessons Learned from a Breach. Eric van Wiltenburg University of Victoria @ e_vanwiltenburg. Let’s start with some exercise. Hey Eric, aren’t you embarrassed?. “Transparency is an asset.” Eric van Wiltenburg, January 31, 2012. OK, so what happened anyway?. +. +. =. 11845. - PowerPoint PPT Presentation

Citation preview

Page 1: Lessons Learned from a Breach

Lessons Learned from a Breach

Eric van WiltenburgUniversity of Victoria

@e_vanwiltenburg

Page 2: Lessons Learned from a Breach

Let’s start with some exercise

Page 3: Lessons Learned from a Breach

Hey Eric, aren’t you embarrassed?

Page 4: Lessons Learned from a Breach

“Transparency is an asset.”Eric van Wiltenburg, January 31, 2012

Page 5: Lessons Learned from a Breach

OK, so what happened anyway?

Page 6: Lessons Learned from a Breach
Page 7: Lessons Learned from a Breach
Page 8: Lessons Learned from a Breach

+

Page 9: Lessons Learned from a Breach
Page 10: Lessons Learned from a Breach

+

Page 11: Lessons Learned from a Breach
Page 12: Lessons Learned from a Breach

=

Page 13: Lessons Learned from a Breach
Page 14: Lessons Learned from a Breach
Page 15: Lessons Learned from a Breach
Page 16: Lessons Learned from a Breach
Page 17: Lessons Learned from a Breach
Page 18: Lessons Learned from a Breach
Page 19: Lessons Learned from a Breach
Page 20: Lessons Learned from a Breach
Page 21: Lessons Learned from a Breach
Page 22: Lessons Learned from a Breach
Page 23: Lessons Learned from a Breach

11845

Page 24: Lessons Learned from a Breach

• employee names• employee numbers • Social Insurance Numbers• bank account • employee classification code • amount of last deposit

Page 25: Lessons Learned from a Breach

January 2010

January 2012

Page 26: Lessons Learned from a Breach
Page 27: Lessons Learned from a Breach

Lesson

• Having good policies in place is very important, even if nobody reads them

Page 28: Lessons Learned from a Breach

UVic Privacy Policy

Page 29: Lessons Learned from a Breach

Privacy Breach Response Team

Page 30: Lessons Learned from a Breach
Page 31: Lessons Learned from a Breach

• University Secretary• Vice President Finance and Operations• Manager Privacy, Access and Policy• University Legal Counsel • Information Security Manager• Director, Communications• Associate Vice-President Human Resources• Associate Vice-President Faculty Relations• Assistant Director, Campus Security• Executive Director, Government Relations• Vice-President External Relations• Assistant Treasurer • Risk Analyst

Page 32: Lessons Learned from a Breach

FIPPAOIPC

Page 33: Lessons Learned from a Breach
Page 34: Lessons Learned from a Breach

Lesson

• Effective external communication to {organization, staff, community} is important for {salvaging reputation, reassuring affected individuals, ensuring resolution}, even if the internal politics, communications and logistics cause friction.

Page 35: Lessons Learned from a Breach
Page 36: Lessons Learned from a Breach
Page 37: Lessons Learned from a Breach
Page 38: Lessons Learned from a Breach
Page 40: Lessons Learned from a Breach
Page 41: Lessons Learned from a Breach

uvic.ca/infobreach

Page 42: Lessons Learned from a Breach
Page 43: Lessons Learned from a Breach
Page 44: Lessons Learned from a Breach

Regular bulletin updates• Information sent to current and former UVic employees, Jan. 9, 2012• Letter from Vice-president Finance and Operations Gayle Gorrill, Jan. 10, 2012• A message from President David Turpin, Jan. 11, 2012• Jan. 12, 2012 update• Jan. 13, 2012 update• Jan. 19, 2012 update• Jan. 20, 2012 update - Launch of review• Jan. 23, 2012 update - Phishing attacks & fraud investigation• Jan. 25, 2012 update - Preliminary report to board• Jan. 27, 2012 update - Agreement reached on Credit Monitoring Service• Jan. 26, 2012 update - Saanich police release info• Feb. 3, 2012 update - Credit monitoring service available Monday• Feb. 6, 2012 update - Credit monitoring instructions

Page 45: Lessons Learned from a Breach

Lesson

• Bad guys and gals know how to read the news

Page 46: Lessons Learned from a Breach
Page 47: Lessons Learned from a Breach
Page 48: Lessons Learned from a Breach
Page 49: Lessons Learned from a Breach

Lesson

• Understand what “reasonable security arrangements” are

Page 50: Lessons Learned from a Breach
Page 51: Lessons Learned from a Breach
Page 52: Lessons Learned from a Breach

Lesson

• If you don’t need it, get rid of it (or don’t collect it).

• Data minimization

Page 53: Lessons Learned from a Breach
Page 54: Lessons Learned from a Breach

Lesson

• Effective project management helps ensure the last mile is completed.

Page 55: Lessons Learned from a Breach

Lesson

• Keeping momentum once the storm blows over can be difficult

Page 56: Lessons Learned from a Breach

Lesson

• Centralized command and control for privacy and security is necessary, even in a decentralized environment

Page 57: Lessons Learned from a Breach

Lesson

• A crisis can be a platform for change

Page 58: Lessons Learned from a Breach

Lesson

• Having good policies in place is very important, and everybody should read them

Page 59: Lessons Learned from a Breach

Remember…

• It’s not IF you’re going to have a breach, it’s WHEN you’ll have a breach and HOW you respond to it and what you LEARN from it that really matters.