Adobe Data Breach Presentation
Adobe Data Breach Presentation
Adobe Data Breach Presentation
1. Brief Background
2. Likely incident causes
3. Short-term and long-term impacts of the incident
4. Suggested prevention actions and associated solutions
1. Brief Background
Adobe data breach in 2013
--one of the biggest incidents of the 21st century.
◺ From 2011 to 2013, Adobe shifted from selling desktop licenses to cloud-
based service. Moving to cloud creates vulnerabilities to Adobe’s data
security.
- - technical &
organizational blind spots.
3
Adobe data breach in 2013
Timeline
◺ Hackers accessed a source code repository sometime in mid-August 2013
◺ Adobe utilised a two-factor authentication for data and conducted vulnerability scanning
at the end of the Sep in 2013.
◺ 2013, Oct,3: Adobe first confirmed that 2.9 million customers have had private information
stolen. \cite{}
◺ 2013, Oct,29 : Adobe completed resetting the passwords for all Adobe IDs involved.
◺ 2013, Oct,30: Adobe increased the number of attacked account to 38 million. \cite{}
◺ At 30th of June 2015, Adobe engaged an independent auditor to certify that it has
implemented the remediation work required by the government.
◺ 2018: The company was still dealing with the cleanup and announced a new Experience
Cloud feature that makes security more important. 4
2. Likely incident causes
Technical Issues
6
Organizational Blind Spots
⮚ Outdated organization structure
Different departments were working
separately. (the product engineering was
totally separate
from IT security)
--Lack of communication
--Some overlooking of responsibility during
technical operations
● Legal Action
○ Facing legal liability
13
Prevention Action
● Regular inspection and maintenance
14
Response
● Towards User
○ Notify customers and business
○ Give Apology and compensation to users who were
influenced
● Towards Public
○ Hire external auditors to do a full investigation
○ Call a press conference
15
Response
● Towards Government
○ Pay the fine against the agreement
○ Consult with legal counsel
16
References
‘5 Damaging Consequences of A Data Breach’, METACOMPLIANCE MARKETING TEAM,
25/2/2020 https://www.metacompliance.com/blog/5-damaging-consequences-of-a-data-breach/
‘Adobe’s CSO talks security, the 2013 breach, and how he sets priorities’, Terena Bell, 12/4/2018
https://www.csoonline.com/article/3268035/adobe-s-cso-talks-security-the-2013-breach-and-how-he-sets-priorities.html
‘Single block cipher on backup system allowed customer detail access in Adobe breach: OAIC’, Chris Duckett, 9/7/2015
https://www.zdnet.com/article/backup-system-with-single-block-cipher-cause-of-adobe-2013-hack-oaic/
‘Adobe To Announce Source Code, Customer Data Breach’, Brian Krebs, 3/10/2013
https://krebsonsecurity.com/2013/10/adobe-to-announce-source-code-customer-data-breach/
‘Adobe pays US$1.2M plus settlements to end 2013 breach class action’, Darren Pauli, 17/8/2015
https://www.theregister.com/2015/08/17/adobe_settles_claims_for_data_breach/
17