Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Partner Perspectives  Connecting marketers to our tech communities.
4/16/2015
03:00 PM
Ryan Vela
Ryan Vela
Partner Perspectives
Connect Directly
Twitter
RSS
50%
50%

Breach Defense Playbook

How to be smart about defending against your next attack.

Over the next several weeks, this blog series will outline breach prevention and incident response services that organizations can use to stay ahead of hackers and not fall victim to the cyberbreach fallout. However, before we look forward, let’s look back and recount what we’ve seen in the news recently so we can learn from others:

  • January 2015, Anthem: 80 million sets of names, birth dates, member IDs, social security numbers, addresses, phone numbers, email addresses, and employment histories are stolen from the second-largest health insurer in the U.S. Victims include current and former Anthem health plan members, and also non-members with other insurance companies for whom Anthem managed paperwork.
  • April-June 2014, Community Health Systems: 4.5 million patient records that included names, addresses, birth dates, telephone numbers, and social security numbers were available to hackers. The Heartbleed OpenSSL vulnerability was used for infiltration.
  • April-September 2014, Home Depot: 53 million email addresses and 56 million credit and debit card accounts were stolen from the largest home improvement retail chain. Hackers used custom malware to scrape data from self-checkout registers.
  • July 2014, JPMorgan Chase: 83 million personal accounts and 7 million small business accounts were stolen from the largest U.S. bank. Hackers stole the login credentials for a JPMorgan employee. One system that was not upgraded for two-factor authentication was targeted for infiltration. The same hackers also are suspected of targeting Citigroup, HSBC Holdings, E*Trade, Regions Financial, ADP, and Fidelity Investments.
  • February-March 2014, Ebay: 145 million users were asked to reset their passwords. Hackers stole email addresses, encrypted passwords, birth dates, addresses, and other information. Hackers were able to infiltrate the organization and access a database by using stolen employee credentials.
  • November-December 2013, Target: 70 million user accounts and 40 million credit and debit card accounts were stolen. Hackers used a third-party vendor to access the network and then used scrapers on point-of-sale devices to steal data.
  • British Airways, Japan Airways, Premera, Uber, Slack, Mozilla, Sony Pictures, Staples, UPS, Neiman Marcus, Korea Credit Bureau, European Central Bank, AOL, Living Social, Evernote, Gamigo, Court Ventures, Adobe, UbiSoft, Zappos, Steam, NHS, Blizzard, Sony Play Station Network, and the list goes on and on. I have been tracking over 100 major breaches since 2004.

If organizations want to keep their names off this list and out of the headlines, they need to know where to start. First, they need to identify what matters most within their organization so they can align their security strategy behind it. Whether it is financial data, personally identifiable information, or intellectual property, organizations need to know what directly influences their reputation (and revenue). Once they understand this key aspect of their cyber-infrastructure from a strategic perspective, they can make the right investments to protect it and secure the environment.

Second, organizations should get visibility into the data moving into, out of, and between segments of their network. Only through inspecting and adjudicating the content of moving data can an organization ensure that malicious activity is not going on.

Lastly, organizations should focus on implementing a defense-in-depth strategy for their cyber-infrastructure. Along with the “not if, but when” maxim, defense-in-depth will decrease the risk of critical data compromise while at the same time increase the probability of intrusion detection.

Building on these lessons, this blog series will examine the playbook organizations should follow to prevent and prepare for breaches. The series will begin with deterrence by talking about cybersecurity engineering, penetration testing, and security controls. Then it will touch on detection by hunting for breach indicators. From there we’ll move to prediction by reviewing an organization’s security program as well as using open-source intelligence. And, because we live in a “not if, but when” breach world, we’ll delve into response and assessing an organization’s incident response readiness. Lastly, we’ll get into governance with respect to risk, audits, and assessments. Stay tuned!

Ryan Vela is a Regional Director for Fidelis Cybersecurity. He has 15-years' experience in conducting investigations and digital forensic analysis. Ryan served as a Strategic Planner at the Defense Computer Forensics Laboratory (DCFL), where he established plans for the ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
97% of Americans Can't Ace a Basic Security Test
Steve Zurier, Contributing Writer,  5/20/2019
How Security Vendors Can Address the Cybersecurity Talent Shortage
Rob Rashotte, VP of Global Training and Technical Field Enablement at Fortinet,  5/24/2019
TeamViewer Admits Breach from 2016
Dark Reading Staff 5/20/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-7068
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7069
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7070
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .
CVE-2019-7071
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an out-of-bounds read vulnerability. Successful exploitation could lead to information disclosure.
CVE-2019-7072
PUBLISHED: 2019-05-24
Adobe Acrobat and Reader versions 2019.010.20069 and earlier, 2019.010.20069 and earlier, 2017.011.30113 and earlier version, and 2015.006.30464 and earlier have an use after free vulnerability. Successful exploitation could lead to arbitrary code execution .