United States: Another Way To Challenge Standing In Data Breach Cases

This article by counsel member David Cohen and associate  Ani-Rae Lovell was published by Law360 on April 24, 2017.

A common tactic in defending federal consumer data breach litigation is challenging the plaintiff's standing on a motion to dismiss. Specifically, defendants contest whether the plaintiff suffered an actual or imminent injury from the breach sufficient to create a "case or controversy" under Article III of the U.S. Constitution. Most such challenges are "facial" — that is, defendants argue that the complaint fails to plausibly plead an actual or imminent injury. These facial challenges are frequently successful. They are not, however, a defendant's only option for seeking dismissal on standing grounds. A recently decided district court case, Foster v. Essex Property Inc., No. 5:14-cv-05531-EJD, 2017 WL 264390 (N.D. Cal. Jan. 20, 2017), demonstrates an additional avenue for challenging standing in data breach litigation — a so-called "factual" challenge to standing, which is based on evidence. Defendants should not overlook this potentially powerful tool when assessing their options for seeking early termination of the litigation.

Facial Attacks on Standing in Data Breach Litigation

Any private plaintiff in federal court bears the burden of demonstrating the "irreducible constitutional minimum of standing" — (1) an injury in fact; (2) caused by the defendant's conduct; (3) that is redressable by a favorable court decision.1 To attack standing on a motion to dismiss, a defendant may bring either a facial or factual challenge.2 A facial challenge is resolved solely based on the well-pleaded facts alleged by the plaintiff, which a judge takes as true for purposes of resolving the motion, and reasonable inferences from those allegations.3 But a factual challenge is resolved based on evidence. The defendant may submit affidavits or declarations introducing facts from outside of the pleadings that disprove the plaintiff's allegations.4 In response, a plaintiff has the opportunity to respond with her own evidence.5

Standing has proven a crucial threshold issue in consumer data breach litigation. Even in cases where plaintiffs have suffered direct losses from identity theft or fraud, it can be difficult, if not impossible, to establish that the fraudulent losses at issue were caused by the breach. Moreover, where the breach is of payment card data, consumers tend to be fully reimbursed for fraudulent charges, due to the card brands' zero liability policies. And many plaintiffs have experienced no fraud at all. Plaintiffs therefore frequently resort to alleging a risk of future harm — either the increased risk of future harm itself, or harm stemming from present expenditures meant to mitigate the risk of future harm (such as purchasing credit monitoring). Defendants have had a great deal of success in arguing that such harms are insufficient to warrant Article III standing under the holding of the 2013 U.S. Supreme Court case Clapper v. Amnesty International. Clapper rejected allegations of "possible future injury" where the threatened injury was not "certainly impending" and of mitigation costs incurred in reaction to future injury that is itself not cognizable: Plaintiffs "cannot manufacture standing by incurring costs in anticipation of non-imminent harm." 6

Most of these successful attacks on standing in data breach litigation have been facial challenges, underscoring that such challenges are frequently viable.7 But there have been exceptions. Most notably, the Sixth and Seventh Circuits recently found that alleged risks to consumer data breach plaintiffs of future harm, when coupled with efforts by the plaintiffs to mitigate that risk, met the Clapper standard under the circumstances of those cases. The first of these opinions — the 2015 Seventh Circuit opinion Remijas v. Neiman Marcus Group LLC — arose out of a 2013 cyberattack on Neiman Marcus Group Inc. stores, with approximately 350,000 payment cards allegedly compromised. Reversing the district court, the Seventh Circuit held that the plaintiffs—not just certain consumers who had allegedly already experienced credit-card fraud but also some who had not — had sufficiently pleaded Article III standing. The court reasoned that given allegations that "hackers deliberately targeted" Neiman Marcus to obtain payment-card data, stole the data, and then misused 9,200 of the stolen card numbers, "it is plausible to infer that the plaintiffs have shown a substantial risk of harm." Ultimately, while the court acknowledged the possibility that plaintiffs would ultimately be unable to prove they faced such a risk, the plaintiffs "had no such burden at the pleading stage." In 2016, the Sixth Circuit in Galaria v. Nationwide Mutual Insurance Co. and the Seventh Circuit in Lewert v. P.F. Chang's China Bistro Inc. found the risk of future harm and mitigation costs sufficiently pleaded to survive facial challenges in decisions that largely mirrored the Neiman Marcus reasoning.8

Factual Attacks on Standing — Foster v. Essex Property

Even in the wake of Neiman Marcus, P.F. Chang's and Nationwide, facial attacks on standing remain a powerful tool for many data breach defendants. Such attacks are not, however, defendants' only option for seeking early dismissal. A recent decision from the Northern District of California illustrates how a so-called "factual" challenge to standing can succeed. In Foster v. Essex Property, a couple alleged violations of several California state laws after a real estate company's internal computer system suffered a security breach. The couple, Mark and Akiko Foster, rented an apartment from Essex Property Inc. Essex is a real estate trust involved in the development and management of properties in California and Seattle. The Fosters alleged Essex required certain personal identifying information, including names, addresses, emails, birthdays, credit and debit card numbers, employment information, and Social Security numbers, as well as authorization to conduct credit checks, in order to rent an apartment. That information, the Fosters allege, was stored on Essex's internal computer system. Essex's internal computer system suffered a security breach, allegedly exposing the plaintiffs' personal identifying information to "cybercriminals" who made fraudulent charges on plaintiffs' credit cards and exposed them both to an increased risk of fraud and identity theft.

Essex moved to dismiss the Fosters' claims. Rather than merely arguing that the plaintiffs' allegations in the pleadings were insufficient to establish Article III standing, the defendant's motion to dismiss included two declarations from Essex managers.

One declaration from Essex's IT manager explained that Essex's internal computer system was the only system breached, and the couple's credit card information was not initially stored on the internal system nor transferred to that system at any point. He concluded, therefore, that it was impossible for the attack on Essex's internal network to cause or aid unauthorized credit charges to the couple's credit cards.

A second declaration from a customer care and collections manager disclosed that the plaintiffs did not provide their credit or debit card information on their rental application, they did not pay their deposit with a card, and they did not pay their rent with a card either. Further, any credit report information retained by Essex was printed and stored in a paper file, not on an electronic network.

The plaintiffs did not counter with any of their own evidence.

Weighing the evidence in those declarations against the plaintiff's allegations, the court found the plaintiffs failed to establish Article III standing. The declarations, the court found, disproved any particularized and concrete injury as well as causation between the breach and any alleged harms. If the information was never stored on the system, it could not have been stolen by criminals through a breach of that system.


Foster illustrates that defendants should not overlook the potential for a factual challenge to standing in data security breach litigation. Such challenges may be viable where, as in Foster, the premise of the plaintiffs' theory of harm — that his or her data was stolen in the breach — can be readily disproven.9 But defendants can also consider factual challenges in a broader variety of contexts. Where only payment card data was stolen, for instance, defendants can consider offering evidence of the zero-liability policies of the major payment card brands providing that consumers will be reimbursed for any fraudulent payment card charges.10

Of course, before bringing a factual challenge, defendants should weigh potential downsides. A factual motion to dismiss may be more costly. Defendants will have to prepare a declaration or affidavit, requiring an internal investigation. However, following a data breach, internal, forensic investigations are likely already being conducted, so obtaining evidence for a factual challenge may not require any additional resources. A defendant's use of a factual challenge may also prompt the plaintiff to request discovery from the defendant. But depending on the context, the company may have viable objections to such requests. Moreover, as Foster illustrates, the upside of a factual challenge can be significant — it may eliminate the case entirely.


1 Lujan v. Def. of Wildlife, 504 U.S. 555, 560-61 (1992).

2 C. Wright & A. Miller, Federal Practice and Procedure § 1364 (1969); see, e.g., Wolfe v. Strankman, 392 F.3d 358, 362 (9th Cir. 2004); Ohio Nat’l Life Ins. Co. v. US, 922 F.2d 320, 325 (6th Cir. 1990); Williamson v. Tucker, 645 F.2d 404, 413 (5th Cir. 1981); Mortensen v. First Fed. Sav. and Loan Ass’n, 549 F.2d 884, 891 (3d Cir. 1977).

3 Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). In addition, on a facial challenge a court may consider certain additional documents, but only those in limited categories—for instance, materials incorporated into the complaint by reference, documents relied on by the complaint, certain public records, and matters subject to judicial notice. See, e.g., Philips v. Pitt Cty. Mem’l Hosp., 572 F.3d 176, 180 (4th Cir. 2009) (recognizing a court “may property take judicial notice of matters of public record”); Doss v. Clearwater Title Co., 551 F.3d 635, 640 (7th Cir. 2008) (recognizing a court make take judicial notice of certain materials); Am. Chiropractic Ass’n, Inc. v. Trigon Healthcare Inc., 367 F.3d 212, 234 (4th Cir. 2004) (recognizing a court may generally consider documents “integral and explicitly relied on in the complaint”); Chambers v. Time Warner, Inc., 282 F.3d 147, 152-53 (2d Cir. 2002) (recognizing a court may consider documents attached to, referenced by, or integral to a complaint).

4 See, e.g., Leite v. Crane Co., 749 F.3d 1117, 1121 (9th Cir. 2014).

5 See, e.g., Wolfe, 392 F.3d at 362.

6 Clapper v. Amnesty Int’l USA, 133 S.Ct. 1138, 1143, 1147, 1155 (2013).

7 See, e.g., Attias v. CareFirst, Inc., No. 15-CV-00882, 2016 WL 4250232 (D.D.C. Aug. 10, 2016); Allison v. Aetna, Inc., No. 09-2560, 2010 WL 3719243 (E.D. Pa. Mar. 9, 2010); Amburgy v. Express Scripts, Inc., 671 F. Supp. 2d 1046 (E.D. Mo. 2009); Hinton v. Heartland Payment Sys., Inc., No. 09-594, 2009 WL 704139 (D.N.J. Mar. 16, 2009).

8 See also In re Horizon Healthcare Servs. Inc. Data Breach Litigation, 846 F.3d 625, 640-41 (3d Cir. 2016) (rejecting facial challenge on the ground that alleged violation of federal privacy statute resulting in disclosure of personal information to third party was sufficient for standing in data breach case) (citing Spokeo, Inc. v. Robins, 136 S.Ct. 1540 (2016)); but see Beck v. McDonald, Nos. 15-1395, 15-1715, 2017 WL 477781, at *9 (4th Cir. Feb. 6, 2017) (sustaining both facial and factual challenges to standing in data breach action, and in doing so rejecting the “risk of harm” theory).

9 Whether plaintiff’s data was stolen can also be raised in a facial challenge, if the pleading fails to adequately allege the theft. See In re Supervalu, Inc., No. 14-4660, 2016 WL 81792, at *5 (D. Minn. Jan. 7, 2016) (dismissing complaint upon facial challenge because the pleading required the court to “speculate about whether the hackers who gained access to Defendants’ payment processing network were able to capture or steal Plaintiffs’ PII; whether the hackers or other criminals will attempt to use the PII; and whether those attempts will be successful”).

10 Defendants also have strong arguments that such policies, which are widely known, can be considered on a facial challenge. As the Sixth Circuit noted outside the data breach context, courts do not “assess the plausibility of an inference in a vacuum,” and the “existence of obvious alternatives” to the plaintiff’s theory—here, the likelihood that consumers were or will be reimbursed for any fraudulent charges—“simply illustrates the unreasonableness of the inference sought [by the plaintiff] and the implausibility of the claims made.” 16630 Southfield Ltd. P’ship v. Flagstar Bank, 727 F.3d 502, 505 (6th Cir. 2013). Should a court decline to consider such policies on a facial attack, however, the company can then offer them in a factual attack.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) 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 these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.