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.


10:30 AM
Connect Directly
E-Mail vvv

Incident Response: 3 Easy Traps & How to Avoid Them

Sage legal advice about navigating a data breach from a troubleshooting cybersecurity outside counsel.

While a serious security incident may be a rare occurrence inside an organization, as a troubleshooting outside counsel, I witness a range of incidents that run the gamut from serious to strange and are often riddled with common pitfalls. It never fails that the event seems to occur at the most inopportune times, such as Christmas Eve or when I'm standing in the middle of the frozen food section of the grocery store (both real-life examples) — the phone rings, and on the other line a client is experiencing their worst day ever. My job is to jump into the mix and begin troubleshooting the legal risks. Here are three traps I frequently see security teams fall into, and how best to navigate them.

Trap 1: Failure to Have a True Incident Response Plan (or to Follow It)
When was the last time you dusted off the ancient incident response plan and actually read it? No matter how sophisticated your organization may be, or how many times you've conducted a tabletop exercise in the last few years, it is important to review the plan and refresh it based on what incidents your organization may face today.

Do you know who is going to call outside counsel? Do you know who is alerting the insurance company? Or, better question, do you know what event triggers the alerting of both? These are often steps that need to happen either immediately or rapidly after first learning of an event.

Often, in the heat of a serious incident, the plan gets pushed to the wayside. Control of the incident response gets wrestled away from the CISO and may get placed in the hands of the CFO or the CEO. This is inevitable if the event is serious enough — not a single medical record compromised but the entire patient portal, for instance. You need to plan for those events that are catastrophic and work backward from there.

Is there a key member of the team that you know is going to be a part of the incident response, even if his or her job title doesn't lend itself to being in the room? For example, is Alex a trusted member of the C-suite as chief strategy officer? If so, Alex may need to be considered as part of the team when the worst hits. What is Alex's role? Practical planning in advance can save you a headache later.

Trap 2: Alerting the Wrong Law Enforcement Agency
This is another semiridiculous outcome. When the phone rings, a breathless client on the other end shares that law enforcement has already been alerted. Inevitably, it's the wrong law enforcement agency for the event. While local police are great practical friends of many companies, they are rarely the group that should be called during a cybersecurity incident. Even state police in most states do not have the resources to adequately respond to a data breach.

In some cases, the question of whom to call will depend on the actual nature of the event and on the severity of the issue. In all cases, the decision about whether to call, when to call, and whom to call needs to be a conversation you first have with an attorney. While you may think that calling the FBI Cyber Crimes Division is the always the right move, there are exceptions, especially if you are dealing with an incident involving W2s or Employer Identification Numbers (EIN) theft, which may require a call to an IRS Special Agent. If there is physical mail involved, the U.S. Postal Service Fraud Division may be able to assign an agent to the investigation. There are strategic reasons for those calls and sometimes the reason can be simply finding an investigative authority who has the time to look into your particular issue.

Calling law enforcement before you have your attorney's blessing can only make things more difficult. If you call the local police and they send over Deputy Andy with his cop car, employees will begin asking questions before the communications plan is ready to roll out.

Many if not most cybercrimes unfortunately do not result in handcuffs. And so some of you in the cybersecurity industry may ask whether it's worth calling law enforcement at all. From the perspective of outside counsel, it is always better to be able to say we are "working with law enforcement" on a particular event, especially if it is catastrophic. But getting to the "working with law enforcement" part can be tricky. Sometimes, just because of the sheer number of incidents outside counsel have experienced, they may be able to get through to the right investigative authority quicker than you can alone. Trust that outside counsel will know who to call and let the call be placed.

Trap 3: Being Careless about Communications
Your cybersecurity event is never a "breach" until the thoughtful decision is made to categorize it as a "breach." Until such time, it is an "incident" or an "event."

Similarly, the way you characterize and describe the incident can have ramifications in potential lawsuits later on. When alerting employees, remember to use phrases like "our company has been the victim of a cybercrime." Also, if Marla at the front desk clicked on a phishing email and exposed the crown jewels, now is not the time to say in group emails without counsel copied that you've been lobbying for her to be fired for failing to pass company phishing tests for years. As always, keep in mind that the highest cloak of confidentiality you can throw over communications is to loop in your attorney and use attorney-client privilege. Without that, every communication you send may be an exhibit in a later lawsuit.

Related Content:

Beth Burgin Waller is a lawyer who knows how to navigate between the server room and the board room. As chair of the cybersecurity & data privacy practice at Woods Rogers, she advises clients on cybersecurity and on data privacy concerns. In this capacity, she ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
User Rank: Ninja
5/24/2019 | 2:32:45 PM
Re: InfoSec Law for Dummies (or Engineers)
The Landscape itself was changed with first WannaCry in 2017 and then the Experian catastrophe - the effective Chernobyl of data breach stories.  After these two incidents, data breach and ransomware assumed a whole new face and import.  And corporate reaction took a beating after what Experian and brain-dead CEO stated in testimony.  We are MUCH more aware as a result of the downside beating a firm can take in private and public. 
User Rank: Ninja
5/23/2019 | 12:36:32 PM
InfoSec Law for Dummies (or Engineers)
This article is a reminder that many engineers are woefully clueless when it comes to cyberlaw and some are clearly the wrong person to have in a room with lawyers after an "event".  It also calls to my attention that it seems the rift between the lawyers and security engineers is often vast.  At a minimum companies should keep documentation and provide training along the lines of "InfoSec Law for Dummies (or Engineers)" so everyone is speaking the same language.  Additionally, there should be regular face-to-face moments between an organization's cyberlaw team and the techs who do the work.  In the FLOSS realm, lawyers are often programmers themselves, and the language of law and tech among FLOSS coders is pretty fluid.  We're versed on the law through necessity.  However, in the corporate world, this seems far from common and the divide can be so vast as to be an "event" in and of itself.
US Formally Attributes SolarWinds Attack to Russian Intelligence Agency
Jai Vijayan, Contributing Writer,  4/15/2021
Dependency Problems Increase for Open Source Components
Robert Lemos, Contributing Writer,  4/14/2021
FBI Operation Remotely Removes Web Shells From Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/14/2021
Register for Dark Reading Newsletters
White Papers
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-04-20
An unsafe deserialization vulnerability in Bridgecrew Checkov by Prisma Cloud allows arbitrary code execution when processing a malicious terraform file. This issue impacts Checkov 2.0 versions earlier than Checkov 2.0.26. Checkov 1.0 versions are not impacted.
PUBLISHED: 2021-04-20
An information exposure through log file vulnerability exists in Palo Alto Networks PAN-OS software where secrets in PAN-OS XML API requests are logged in cleartext to the web server logs when the API is used incorrectly. This vulnerability applies only to PAN-OS appliances that are configured to us...
PUBLISHED: 2021-04-20
An information exposure through log file vulnerability exists in Palo Alto Networks PAN-OS software where the connection details for a scheduled configuration export are logged in system logs. Logged information includes the cleartext username, password, and IP address used to export the PAN-OS conf...
PUBLISHED: 2021-04-20
A denial-of-service (DoS) vulnerability in Palo Alto Networks GlobalProtect app on Windows systems allows a limited Windows user to send specifically-crafted input to the GlobalProtect app that results in a Windows blue screen of death (BSOD) error. This issue impacts: GlobalProtect app 5.1 versions...
PUBLISHED: 2021-04-19
An out-of-bounds (OOB) memory access flaw was found in fs/f2fs/node.c in the f2fs module in the Linux kernel in versions before 5.12.0-rc4. A bounds check failure allows a local attacker to gain access to out-of-bounds memory leading to a system crash or a leak of internal kernel information. The hi...