$30 off During Our Annual Pro Sale. View Details »

15 Years Later – Data Awareness In A Post Rober...

15 Years Later – Data Awareness In A Post Robert Hanssen World

Former FBI agent Robert Phillip Hanssen was arrested in 2001 for selling classified information to the Soviet Union and Russian Federation for more than $1.4 million in cash and diamonds over a 22-year period. Fifteen years later, classified data remains a target for security attacks. Though America has grown in terms of the technology at its disposal and its understanding of data security, a focus on locating and protecting sensitive data remains absent from many information security programs.

When companies lack visibility into their data, they make it possible for sensitive, personal information to exist in places people are unaware of. The consequences are visible in recent security breach reports from across the globe. On May 20 at the CyberSecureGov conference in Washington, D.C, DataGravity CISO Andrew Hay will share insights to help companies update their data security tactics, gain control of their sensitive data and avoid such consequences.

Data-awareness has changed in the post-Robert Hanssen world, and it will continue to evolve until companies and individuals can feel secure about their personal information. During the CyberSecureGov conference, additional interactive sessions and workshops will explore data security across multiple channels. Topics will include best practices for responding to major incidents, how to get through the aftermath of a security breach, companies’ top 10 security expectations and more. In his session, Andrew will present tips, tricks and proven methodologies for detecting, defending and even destroying sensitive data within an IT environment. As Andrew will cover, every organization should approach sensitive data management with respect and confidence – regardless of the target industry or company’s size.

End users and security pros alike need to become more data-aware, especially when sensitive data remains at risk.

Andrew Hay

May 20, 2016
Tweet

More Decks by Andrew Hay

Other Decks in Technology

Transcript

  1. 15 Years Later – Data Awareness In A Post Robert

    Hanssen World Andrew Hay, CISO DataGravity, Inc. www.datagravity.com [email protected] twitter: @andrewsmhay
  2. 3 About Me » Andrew Hay • Chief Information Security

    Officer (CISO) @ DataGravity • Former: – Director of Research @ OpenDNS – Chief Evangelist & Director of Research @ CloudPassage – Senior Security Analyst @ 451 Research » Wrote some books, blog, spend more time on planes than I care to mention…
  3. 4 Agenda » Who is Robert Hanssen? » What have

    we learned? » Defending against data theft » Detecting attempted data theft » Destroying data properly » Summary
  4. 6 Name Robert Phillip Hanssen Born April 18, 1944 in

    Chicago, Illinois. School BSc Chemistry @ Knox College Dental School @ Northwestern (DNF) Psychiatry @ Northwestern (DNF) MBA Accounting & Information Systems @ Northwestern Work History ~1966 - NSA Cryptographer – Application Rejected ~1973 - Chicago Police Department and assigned to police corruption division ~1974-1975 - FBI – Application Rejected ~1976 - FBI – Application Accepted Dossier: Robert P. Hanssen
  5. 7 Dossier: Robert P. Hanssen » Was assigned to the

    Bureau’s Gary, Indiana office » Transferred two years later to New York City » Hanssen was having a tough time making ends meet and decided to exploit his position with the FBI
  6. 8 Dossier: Robert P. Hanssen » Disenchanted by the lackadaisical

    attitude of fellow FBI agents » Hanssen approached Russian agents and offered to sell secret documents » He was rewarded but was caught by his wife while counting $20,000 and writing a letter to the Soviets in his basement.
  7. 9 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD 1972 1976 1H2001 2H2001 2002 1991
  8. 10 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI 1972 1976 1H2001 2H2001 2002 1991
  9. 11 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union 1972 1976 1H2001 2H2001 2002 1991
  10. 12 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 1991
  11. 13 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife 1991
  12. 14 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying 1991
  13. 15 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991
  14. 16 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence
  15. 17 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence FBI identifies Hanssen from a fingerprint & recording. FBI also obtains the complete original KGB dossier on Hanssen.
  16. 18 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence FBI identifies Hanssen from a fingerprint & recording. FBI also obtains the complete original KGB dossier on Hanssen. FBI begins surveillance on Hanssen
  17. 19 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence FBI identifies Hanssen from a fingerprint & recording. FBI also obtains the complete original KGB dossier on Hanssen. FBI begins surveillance on Hanssen Hanssen reassigned to obscure office at FBI HQ / arrested making drop at Virginia park
  18. 20 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence FBI identifies Hanssen from a fingerprint & recording. FBI also obtains the complete original KGB dossier on Hanssen. FBI begins surveillance on Hanssen Hanssen reassigned to obscure office at FBI HQ / arrested making drop at Virginia park Pleads guilty to 15 counts of espionage and conspiracy in exchange for no death penalty
  19. 21 Timeline of Events 1979 1980 1981 1985 1999 1H2000

    2H2000 Joins Chicago PD Joins FBI Begins spying for the Soviet Union Begins working Soviet counterintelligence unit 1972 1976 1H2001 2H2001 2002 Transferred to FBI HQ to track white-collar crime and foreign officials / caught by wife Resumes spying Breaks off relations with KGB 1991 Resumes spying for Russian Intelligence FBI identifies Hanssen from a fingerprint & recording. FBI also obtains the complete original KGB dossier on Hanssen. FBI begins surveillance on Hanssen Hanssen reassigned to obscure office at FBI HQ / arrested making drop at Virginia park Pleads guilty to 15 counts of espionage and conspiracy in exchange for no death penalty Sentenced to fifteen life terms without the possibility of parole
  20. 22 Dossier: Robert P. Hanssen » Hanssen was arrested on

    February 18, 2001 at Foxstone Park near his home in Virginia » Charged with selling U.S. secrets to the Soviet Union and the Russian Federation • For more than US$1.4 million in cash and diamonds over a 22-year period » Pleaded guilty to fifteen counts of espionage • Sentenced to fifteen life terms without the possibility of parole
  21. 24 What Have We Learned? » You’d think that such

    a high profile and damaging breach would have set us down the path to… • Data awareness • Better protecting our data • More quickly responding to data breaches » Right.....right???
  22. 25 Verizon DBIR 2016 » This year’s dataset is made

    up of over 100,000 incidents, of which 3,141 were confirmed data breaches » Of these, 64,199 incidents and 2,260 breaches comprise the finalized dataset that was used in the analysis and figures throughout the report
  23. 26 DBIR 2016 » Number of security incidents with confirmed

    data loss by victim industry and organization size, 2015 dataset • Finance – 795 • Accommodation - 282 • Public – 193 • Small is < 1,000 employees • Large is > 1,000 employees
  24. 27

  25. 28 Verizon DBIR 2016 » 66% of all security incidents

    in the public sector • Miscellaneous errors • Insider and privilege misuse • Physical theft and loss » Crimeware was also a significant factor, at16% of the total
  26. 29 What Have We Learned? » Technology has enabled •

    Faster data breaches • Larger data breaches • Automated data breaches • More profitable data breaches • More brand damaging data breaches • New revenue streams for organized crime
  27. 30 What Have We Learned? » • • • •

    • • » And, of course, job security for us J
  28. 34 How We Monitor » Perimeter • Logs & Alerts

    » Applications • Logs & Alerts » Server and Workstations • Logs & Alerts » Network • Logs & Alerts (and also flows/traffic)
  29. 35 What About The Data? » We often forget about

    monitoring the data » I mean, that’s where we keep the important stuff, right? » It’s like a present we hang onto until just the right time…
  30. 36 IP Theft Disgruntled employee copying files to Dropbox before

    leaving. Digital Extortion Manufacturer recovered from Ransomware without paying fines. Sensitive Data Exposure Government agency found 600 files with exposed PII. Admin inadvertently copied exec credit card # into public share. Company has illegal content on their file shares. Illegal Entry Data moving to Cloud in violation of regulator requirements or company policy. Data Trespassing Students storing personal MP3 collections on school servers. Government employee storing Lego movies on file share. Thwarted Theft Themes
  31. 37 Detecting Attempted Data Theft » Some indicators of attempted

    data theft include: • Abnormally high data reads and rights • Increased authentication/authorization failures – Followed by successful authentication/authorization • Access to never before accessed files • Off-hours access
  32. 38 Detecting Attempted Data Theft » Some indicators of attempted

    data theft include: • Large file transfers – Size & number of files • Communications with never before seen domains/IPs • Sustained network communications for long periods of time
  33. 41 » “It is a capital mistake to theorise before

    one has data.” ― Sir Arthur Conan Doyle, The Adventures of Sherlock Holmes
  34. 50 Once Upon A Time… » In a magical land

    called Bermuda » There was an evil semi- documented data destruction procedure
  35. 51 Once Upon A Time… » In a magical land

    called Bermuda » There was an evil semi- documented data destruction procedure » In it, were details of how to dispose of hard drives used by the bank
  36. 52 Once Upon A Time… » In a magical land

    called Bermuda » There was an evil semi- documented data destruction procedure » In it, were details of how to dispose of hard drives used by the bank » The procedure involved a scooter, a garbage dump, and a shovel…
  37. INTERLUDE This is the part of the presentation allocated to

    feeling sorry for the presenter and his impossible mission of securing a bank in Bermuda…
  38. 54 Proper Data Destruction » DoD 5220.22-M (“National Industrial Security

    Program Operating Manual “) » NIST 800-88 (“Guidelines for Media Sanitization”) » However…the responsibility for wiping cloud data to standards is almost always the responsibility of the customer
  39. 55 Summary » Look to your data for ways to

    detect data theft » It is incredibly difficult to defend your data when you don’t know where it’s located • Find it…find it all! » Data destruction needs to be carefully considered • Especially as storage mediums evolve