Home > Articles > Responding to a Breach

Responding to a Breach

Chapter Description

In this sample chapter from Investigating the Cyber Breach: The Digital Forensics Guide for the Network Engineer, you will explore the basic concepts for proper incident response procedure to understand why organizations commonly fail at the process when responding to a breach. The authors also share techniques used by organizations that have a successful incident response plan and provide an overview of industry-proven components required to build an incident response process within your organization.

  • Never confuse a single defeat with a final defeat.”

    —Scott Fitzgerald

On May 31, 2017, OneLogin, a San Francisco–based software security company that specializes in managing logins to applications and multiple websites, reported a data breach where threat actors allegedly may have attempted unauthorized access to OneLogin data and networks. The full extent of this breach is currently not known. However, OneLogin is sold as software to help increase a person’s overall security. There is no doubt that people started questioning the effectiveness of OneLogin security solutions after the data breach occurred. Evidence of this can be seen on Reddit discussions found on discussion forums at www.reddit.com/r/technology/comments/6emqwz/password_manager_onelogin_admits_data_breach_in/.

Fool.com reported in an article posted on May 27, 2014, how a cyberattack exposed 233 million registered eBay accounts. The article criticizes eBay’s handling of the breach, claiming it took nearly three months to notice the breach and two additional weeks to report it (www.fool.com/investing/general/2014/05/27/ebay-data-breach-response-teaches-everyone-how-not.aspx).

An article in TechCrunch on February 2, 2017, reported that Verizon knocked off $350 million US in its offer to purchase Yahoo!, after Yahoo! suffered two massive data breaches. Many security professionals questioned how well Yahoo! was handling security for its own users after these breaches were disclosed (techcrunch.com/2017/02/21/verizon-knocks-350m-off-yahoo-sale-after-data-breaches-now-valued-at-4-48b/).

These examples show how critical it is to respond to a breach correctly and effectively. Many organizations have completely tarnished their reputation, lost customers, and in some cases, never been able to fully recover after a large-scale data breach. Many of these pitfalls could have been avoided with the proper incident response plans and techniques.

Digital forensic network engineers are involved in part of the process of responding to a data breach. In many cases, their role is much more technical in providing the details around the breach. However, in this chapter, we look at the full scope that is normally required when organizations respond to a breach. This allows a network engineer to fully understand the process and ensure specific tasks meet the needs of the organization during an incident. It is important to point out that incident response is different from digital forensics; however, many incident response plans include using forensics to understand what occurred, proving theories about the incident, or preparing for potential future legal action.

This chapter provides an overview of the incident response process from a managerial point of view rather than a technical one. As a network engineer, you will be engaged in a small portion of the entire incident response process, but we believe it is important for you to understand the challenges that organizations face when building an incident response team (IRT) and engaging in the process. Remember that technical services should always track back to a business goal to be relevant. Understanding this will help maintain funding and support for your forensic practice.

The goal of this chapter is to make sure you understand why organizations fail at the process when responding to a breach and examine the techniques used by organizations that have a successful incident response plan. We have combined several accepted frameworks published on building a successful incident response team to develop the content for this chapter. We have additionally added our own experience as well as an overview on industry-proven components required to build an incident response process within your organization.

In Chapter 5, “Investigations,” we go into the technical details for an investigation that are relevant to network engineers. This includes software used by network engineers when responding to a breach and how to use that software when collecting, preserving, and analyzing evidence. You will use the techniques in Chapter 5 to provide detailed evidence and telemetry data needed by incident response teams at different stages of their investigation, which are outlined in this chapter. Before we do that, let’s step back and examine the basic concepts for proper incident response procedures.

Why Organizations Fail at Incident Response

Any organization or business that has had to deal with a cyberbreach understands the stress that accompanies the process, no matter how well prepared or rehearsed it is for cyber events. All breaches come with their unique set of challenges and requirements. The stakes are high because the public can lose complete trust in a company brand, liability can hurt an organization financially, and being complacent may lead to criminal neglect. With so much at stake, you may think that organizations would be well prepared to deal with cyberbreaches. The sad truth is that they are not. Many organizations don’t want to deal with the problems, efforts, and cost required to develop a true response plan for a potential data breach. The idea of a data breach scares organizations, and many of them would rather bury their head in the sand rather than face the reality, which is that they need significant work to prepare a proper incident response plan. We have questioned hundreds of organizations about their incident response plan while evaluating their security and have received answers such as “What incident response plan?” or “We call John in IT and he handles everything.”

When Hollywood Presbyterian Medical Center paid approximately $17,000 US in early 2016 to remove ransomware, it did so because it could not provide the best patient care services to its customers (www.latimes.com/business/technology/la-me-ln-hollywood-hospital-bitcoin-20160217-story.html). The medical center, its reputation, and the public’s trust for the organization are immediately put at risk after these types of attacks occur. Some organizations believe that hiring a security services company and keeping it on standby as much preparation as they might need for a future incident. Organizations simply cannot rely on having an expert on retainer and buying cyber insurance as their method to respond to a breach. Not having an incident response process could represent a lack of due diligence for enforcing the minimal level of required security and could cause the company to be legally liable regardless of what services are outsourced. Many insurance companies engage a third-party auditor to validate existing controls, which means you need to ensure that you have not only technology in place, but also an acceptable incident response plan.

Many organizations see information technology (IT) investments and, by extension, IT security as costs they can reduce. With the intention of creating better efficiencies, some organizations implement defensive solutions that consolidate or eliminate security programs. This includes sacrificing a complete IT data security program responsible for security awareness, incident response, and breach reaction components because they do not think they will need it or are under the impression that their existing solutions and polices already address these problems. Many enterprise corporations have been guilty of failing to budget a plan because they believe the massive amounts of investments they have made in regulatory and compliance practices, such as HIPAA and PCI DSS, have given them adequate protection and responsive capabilities to deal with a breach. If you recall from our previous chapters, compliance should be your minimum level of security, which means it should not be where you stop your investment, because many of these programs use dated material and just are not good enough to prepare you for real-world threats. The truth is that many compliance programs are not risk based but are written as a one-size-fits-all approach. Every organization is different and so are the vulnerabilities, so you need a tailored program based on your business requirements to be successful.

It is common for organizations to simply overestimate how capable they are in responding to a breach. Many branches of the US government run “tabletop” exercises to practice their incident response capabilities. According to Ready.gov, “Tabletop exercises are discussion-based sessions where team members meet in an informal, classroom setting to discuss their roles during an emergency and their responses to a particular emergency situation. A facilitator guides participants through the discussion of one or more ‘scenarios’” (www.ready.gov/business/testing/exercises). These simulation exercises can include situations such as a major power outage, outbreak of diseases, and even cyberattacks. The idea behind tabletop exercises is well intentioned, meaning it is designed to prepare for a real event, but it is not close to a true penetration test or what a red-team-blue-team (attack and defend) training program would offer. In some cases, using tabletop conversations as the only training could provide a false sense of how prepared an organization is for a real cyber incident.

Organizations fail at adequately preparing their programs by not havening continuous, ongoing training. Training exercises should not be treated as special events. Organizations should build continuous training and response procedures that are embedded into an organization’s standard operating procedure. Training should combine the practical, technical, and business aspects of responding to a breach by all team members involved. When should organizations train their incident response teams to respond to a breach? All the time.

2. Preparing for a Cyber Incident | Next Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020