In re: Data Breach Security Litigation Against Caesars Entertainment, Inc.

CourtDistrict Court, D. Nevada
DecidedOctober 14, 2025
Docket2:23-cv-01447
StatusUnknown

This text of In re: Data Breach Security Litigation Against Caesars Entertainment, Inc. (In re: Data Breach Security Litigation Against Caesars Entertainment, Inc.) is published on Counsel Stack Legal Research, covering District Court, D. Nevada primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In re: Data Breach Security Litigation Against Caesars Entertainment, Inc., (D. Nev. 2025).

Opinion

1 UNITED STATES DISTRICT COURT

2 DISTRICT OF NEVADA

3 * * *

4 In re: DATA BREACH SECURITY Case No. 2:23-cv-01447-ART-BNW LITIGATION AGAINST CAESARS 5 ENTERTAINMENT, INC. ORDER 6

8 9 Before this Court is Defendants Coforge Ltd. and Coforge Inc.’s (Coforge) Motion to Stay 10 Discovery. ECF No. 138. Plaintiffs opposed the motion (ECF No. 158), and Coforge replied 11 (ECF No. 158). The parties are familiar with the arguments. As a result, this Court does not repeat 12 them. Instead, it will incorporate the arguments as necessary and relevant to this order. 13 I. Legal Standard 14 The Federal Rules of Civil Procedure do not provide for automatic or blanket stays of 15 discovery because a potentially dispositive motion is pending. Skellerup Indus. Ltd. v. City of 16 L.A., 163 F.R.D. 598, 600–01 (C.D. Cal. 1995). A court may, however, stay discovery under Fed. 17 R. Civ. P. 26(c). The standard for staying discovery under Rule 26(c) is good cause. 18 The Ninth Circuit has not provided a rule or test that district courts must apply to 19 determine if good cause exists to stay discovery. But it has identified one scenario in which a 20 district court may stay discovery and one scenario in which a district court may not stay 21 discovery. The Ninth Circuit has held that a district court may stay discovery when it is convinced 22 that the plaintiff will be unable to state a claim upon which relief can be granted. See Wood v. 23 McEwen, 644 F.2d 797, 801 (9th Cir. 1981). The Ninth Circuit also has held that a district court 24 may not stay discovery when discovery is needed to litigate the dispositive motion. Alaska Cargo 25 Transp., Inc. v. Alaska R.R. Corp., 5 F.3d 378, 383 (9th Cir. 1993). 26 Based on this Ninth Circuit law, district courts in the District of Nevada have applied the 27 preliminary peek test to determine when discovery may be stayed. See, e.g., Kor Media Group, 1 following three requirements before the court will stay discovery pending a motion to dismiss: (1) 2 the pending motion must be potentially dispositive; (2) the potentially dispositive motion be 3 capable of resolution without additional discovery; and (3) after taking a “preliminary peek” at 4 the merits of the potentially dispositive motion, the court must be convinced that the plaintiff will 5 be unable to state a claim for relief. Id. at 581. The point of the preliminary peek test is to 6 “evaluate the propriety of an order staying or limiting discovery with the goal of accomplishing 7 the objectives of [Federal] Rule [of Civil Procedure] 1.” Tradebay, LLC v. eBay, Inc., 278 F.R.D. 8 597, 603 (D. Nev. 2011). This Court has found the preliminary peek test can sometimes be 9 problematic because it can be inaccurate and inefficient. See Schrader v. Wynn Las Vegas, LLC, 10 No. 2:19-CV-02159-JCM-BNW, 2021 WL 4810324, at *3 (D. Nev. Oct. 14, 2021). Importantly, 11 the application of the preliminary peek test as written (i.e., the Court must be convinced after a 12 superficial look at the dispositive motion that the plaintiff cannot state a claim), inevitably leads 13 to few motions to stay discovery being granted, and those are typically baseless cases. Id. at * 3-4. 14 The Court believes a more workable analytical framework exists for determining when 15 motions to stay should be granted. As a result, the test this Court considers (1) whether the 16 dispositive motion can be decided without further discovery, and (2) whether good cause exists to 17 stay discovery. 18 Good cause may be established using the preliminary peek test, but it may also be 19 established by other factors not related to the merits of the dispositive motion. For example, in 20 many cases, the movant seeks a stay of discovery to prevent “undue burden or expense.” See Fed. 21 R. Civ. P. 26(c)(1). In those cases, the movant must establish what undue burden or expense will 22 result from discovery proceeding when a dispositive motion is pending. While good cause may be 23 established based on such non-merits-based considerations, the merits of the case may certainly 24 also play a role in the analysis. In some cases, the merits of the dispositive motion may influence 25 the decision even if the court is not “convinced” after taking a peek. Ultimately, guided by Fed. 26 R. Civ. P. 1, the Court is trying to determine “whether it is more just to speed the parties along in 27 discovery and other proceedings while a dispositive motion is pending, or whether it is more just 1 to delay or limit discovery and other proceedings to accomplish the inexpensive determination of 2 the case.” Tradebay, 278 F.R.D. at 603. 3 “The burden is upon the party seeking the order to ‘show good cause’ by demonstrating 4 harm or prejudice that will result from the discovery.” Rivera v. NIBCO, Inc., 364 F.3d 1057, 5 1063 (9th Cir. 2004). 6 II. Analysis 7 At the outset, this Court notes both parties agree that Coforge’s motion to dismiss is 8 potentially dispositive and that it does not require discovery for its resolution. The parties do 9 disagree, nonetheless, as to whether there is good cause to stay discovery. 10 A. Preliminary peek 11 As explained above, it is impossible to take a “peek” at the arguments made in Coforge’s 12 motion to dismiss and be “convinced” of its outcome. Here, in light of the parties’ extensive (and 13 in some instances, novel) arguments, this Court does not opine as to its outcome. 14 B. Good cause 15 Based on the August 2023 cyberattack targeting Caesars, plaintiffs filed a putative class 16 action against Coforge asserting they have been negligent and violated the consumer protection 17 laws of four different states.1 At the time of this order, plaintiffs have propounded forty requests 18 for production of documents ranging from Coforge’s corporate governance to Caesars’ oversight 19 over their services vis a vis the cyberattack. Of note, Coforge Ltd. is based in India. As discovery 20 progresses, the Coforge Defendants explain that there may be need to depose individuals from 21 India and that it will need to retain experts on matters regarding cyber security. Thus, as in the 22 majority of data breach class actions, discovery in this case will be costly.2 23 Having said that, it is true that even if Coforge’s motion to dismiss is granted, they will 24 still need to respond to plaintiffs’ Rule 45 subpoena.3 And, as the parties recognize, the subpoena

25 1 This case has been consolidated with plaintiffs’ claims against Defendant Caesars. 26 2 A detailed accounting of discovery costs is not required for the Court to find good cause. In many cases, the showing may be made through reference to the type of action, the breadth of 27 discovery sought, and case-specific indicators that the costs are likely to be substantial. 3 It is not clear when Coforge’s motion to dismiss will be decided. It is entirely possible for expert 1 || and the document requests are substantially the same. Thus, a stay of discovery will not relieve 2 || the Coforge Defendants of the need (or cost) of complying with plaintiffs’ document requests.* 3 || Accordingly, this Court will take a bifurcated approach to discovery. It will order the Coforge 4 || Defendants to respond to the requests for production but will stay any other discovery (including 5 || depositions and expert discovery) until the motion to dismiss is decided.” 6 Under the guidance of Rule 1, it is more just to bifurcate and partially stay discovery 7 || pending the resolution of Coforge’s motion to dismiss. Tradebay, 278 F.R.D. at 603.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
In re: Data Breach Security Litigation Against Caesars Entertainment, Inc., Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-data-breach-security-litigation-against-caesars-entertainment-inc-nvd-2025.