Finjan LLC v. Sonicwall, Inc.

[3] 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 SAN JOSE DIVISION [7] 8 FINJAN, INC., Case No. 17-cv-04467-BLF (VKD) 9 Plaintiff, ORDER DENYING LEAVE TO 10 v. AMEND INFRINGEMENT CONTENTIONS 11 SONICWALL, INC., Re: Dkt. No. 216 Defendant. [13] 14 In this patent infringement action, plaintiff Finjan, Inc. (“Finjan”) moves for leave to 15 amend its infringement contentions. Dkt. No. 216. Defendant SonicWall, Inc. (“SonicWall”) 16 opposes. Dkt. No. 221. The motion was referred to the undersigned judge. Dkt. No. 75. The 17 Court heard oral argument on the matter on January 28, 2020. Dkt. No. 227. Having considered 18 the parties’ submissions and arguments made at the hearing, the Court denies Finjan’s motion for 19 leave to amend. 20 I. BACKGROUND 21 On April 10, 2018, Finjan served its original infringement contentions, asserting 22 infringement of the following ten patents: U.S. Patent Nos. 6,154,844 (“the ’844 patent”); 23 7,058,822 (“the ’822 patent”); 6,804,780 (“the ’780 patent”); 7,613,926 (“the ’926 patent”); 24 7,647,633 (“the ’633 patent”); 8,141,154 (“the ’154 patent”); 8,677,494 (“the ’494 patent”); 25 7,975,305 (“the ’305 patent”); 8,225,408 (“the ’408 patent”); and 6,965,968 (“the ’968 patent”). 26 See Dkt. No. 112-2 at 2. After SonicWall objected to this original disclosure, Finjan served 27 supplemental infringement contentions on November 9, 2018. Dkt. No. 118 at 2. 1 2019. Dkt. No. 112. Finjan opposed the motion on February 15, 2019. Dkt. No. 118. In its 2 opposition, Finjan made specific representations about its infringement theories, including the 3 following statements: 4 [C]ertain products are appliances that are capable of infringing malware analysis “on the box” (without connecting to the cloud) and 5 infringe through the use of this analysis engine. However, these products can also connect to Capture ATP in the “cloud” for further 6 malware analysis that also infringes. . . . [7] Thus, Finjan’s contention is that SonicWall’s Gateway, ESA, and 8 SMA instrumentalities infringe on their own, but also infringe when used with Capture ATP, as identified in Finjan’s infringement 9 contentions. Thus, Finjan’s contentions explain how products infringe alone or with Capture ATP. [10] Dkt. No. 118 at 6, 7 (footnote omitted); see also Dkt. No. 129 at 12:09–14:57. [11] On May 1, 2019, the Court granted SonicWall’s motion and ordered Finjan to amend its [12] infringement contentions. Dkt. No. 146. That order required Finjan to eliminate open-ended [13] language and references to unidentified components by, among other things, removing placeholder [14] reference to unspecified products, services, or components, and specifying whether a product or [15] service infringes alone or in combination. Id. Specifically, in response to Finjan’s representations [16] that it believed the Gateways and ESA instrumentalities could infringe in two ways—(1) “on the [17] box,” without connecting to cloud-based components, or (2) in combination with Capture ATP— [18] the Court ordered Finjan to amend its contentions to specify whether an accused product or service [19] infringes alone or in combination with Capture ATP. Dkt. No. 146 at 5. The Court also ordered [20] Finjan to amend its contentions to specifically identify the elements of the accused [21] instrumentalities that satisfy certain limitations of claim 6 of the ’305 patent, claim 22 of the ’926 [22] patent, claim 9 of the ’408 patent, claims 1 and 15 of the ’844 patent, claim 9 of the ’780 patent, [23] claims 1, 10, and 3 of the ’154 patent, and claims 1, 7, and 11 of the ’968 patent. Id. [24] Finjan served its second supplemental infringement contentions on May 31, 2019. Dkt. [25] No. 170 at 2. On September 24, 2019, SonicWall moved to strike parts of Finjan’s second [26] supplemental infringement contentions on the ground that Finjan’s amendments did not comply [27] with the Court’s May 2019 order and asserted new theories of infringement not permitted under 1 that order. Dkt. No. 164. Finjan opposed SonicWall’s motion to strike, arguing that the second 2 supplemental infringement contentions did not include new theories of infringement, but instead 3 reflected Finjan’s efforts to comply with the Court’s order to more specifically identify infringing 4 components. Dkt. No. 170. 5 On November 20, 2019, the Court granted in part SonicWall’s motion to strike.1 Dkt. No. 6 210. The Court struck Finjan’s contentions for the ’926, ’305, ’844, ’633, ’154, ’780, ’822, and 7 ’494 patents that referred to the Gateways and ESA instrumentalities in combination with the 8 CloudAV and GRID sandboxes, and honeypots and webcrawlers, based on Finjan’s earlier 9 repeated representations that the Gateways and ESA instrumentalities infringed either alone or in 10 combination with Capture ATP only. Id. at 3–6, 8. The Court also struck the portions of Finjan’s 11 contentions for the ’154 patent that referred to the Gateways and ESA instrumentalities in 12 combination with the Stats server and URL Thumbprint Database as a new theory of infringement 13 that Finjan had not previously disclosed. Id. at 9. Finally, the Court struck the portions of 14 Finjan’s contentions for the ’968 patent identifying WXA appliances for the first time with respect 15 to certain limitations as a new theory of infringement that Finjan had not previously disclosed. Id. 16 at 9–10. 17 Finjan now seeks leave to amend its infringement contentions to include the infringement 18 theories that the Court struck in November 20192: (1) the CloudAV and GRID Sandbox 19 contentions in the Gateways and ESA “alone” charts for the ’926, ’305, ’844, ’633, ’154, ’780, 20 ’822, and ’494 patents; (2) the Stats server and the URL Thumbprint Database contentions in the 21 Gateways and ESA “alone” charts for the ’154 patent; and (3) the WXA appliance contentions in 22 the charts for the ’968 patent. Dkt. No. 216 at 3–4. [25] 1 The Court’s order issued under seal on November 20, 2019. Dkt. No. 196. Because the parties did not indicate that any redactions needed to be made to that order (see Dkt. Nos. 197, 208), the [26] Court re-filed the order without any redactions on December 3, 2019. Dkt. No. 210. [27] 2 Finjan represents (and SonicWall does not dispute) that its proposed amendments are II. LEGAL STANDARD [1] A plaintiff may amend its infringement contentions “only by order of the Court upon a [2] timely showing of good cause,” such as the “[r]ecent discovery of nonpublic information about the [3] Accused Instrumentality.” Patent L.R. 3-6. When determining whether to grant leave to amend, [4] the Court first considers whether the party seeking leave acted diligently. Apple Inc. v. Samsung [5] Elecs. Co., No. CV 12-00630 LHK, 2012 WL 5632618 , at *2 (N.D. Cal. Nov. 15, 2012) (citation [6] omitted). The Court then considers whether the proposed amendment would unduly prejudice the [7] non-moving party. Id. (citation omitted). [8] III. DISCUSSION [9] A. Finjan’s Diligence [10] 1. Sandbox contentions [11] The Court first considers whether Finjan has been diligent with respect to its motion to [12] amend to add contentions that SonicWall’s Gateways and ESA appliances infringe in combination [13] with the CloudAV and GRID sandboxes (“the sandbox contentions”). [14] Whether a party has been diligent encompasses two considerations: (1) diligence in [15] discovering the basis for amendment, and (2) diligence in seeking amendment once the basis for [16] amendment has been discovered. Monolithic Power Sys., Inc. v. Silergy Corp., No. 14-cv-0174517 VC (KAW), 2015 WL 5440674 , at *2 (N.D. Cal. Sept. 15, 2015) (citing Positive Techs., Inc. v. [18] Sony Elecs., Inc., No. C 11-2226 SI, 2013 WL 322556 , at *2 (N.D. Cal. Jan. 28, 2013)). The party [19] seeking leave to amend carries the burden of establishing diligence. Id. (citing Radware Ltd. v. F5 [20] Networks, Inc., No. C-13-02021-RMW, 2014 WL 3728482 , at *1 (N.D. Cal. July 28, 2014)). [21] “Diligence is a fact intensive inquiry, and courts do not apply a mechanical rule in assessing a [22] party’s diligence but instead consider the factual circumstances in total.” Word to Info Inc. v. [23] Facebook Inc., No. 15-cv-3485-WHO, 2016 WL 6276956 , at *6 (N.D. Cal. Oct. 27, 2016). [24] Finjan argues that it has been diligent in seeking to add the sandbox contentions. It says it [25] obtained new evidence from SonicWall in April 2019 regarding the CloudAV and GRID [26] sandboxes. Dkt. No. 216 at 1, 3. Finjan included contentions concerning the Gateways and ESA [27] instrumentalities in combination with the CloudAV and GRID sandboxes—without first seeking 1 leave—in the second supplemental contentions served on May 31, 2019. Finjan characterizes 2 these sandbox contentions as “clarify[ing] and updat[ing]” its early contentions and insists that 3 they raised no “new infringement issues.” Id. at 3. Finjan says that it did not and could not have 4 known that the Court would view the sandbox contentions as new infringement theories for which 5 leave to amend had not been granted until the Court issued its November 20, 2019 order striking 6 Finjan’s second supplemental contentions. Dkt. No. 216 at 5; Dkt. No. 225 at 1; see also Dkt. No. 7 232 at 17:22-25, 19:17–20:14. Finjan suggests that requiring it to obtain leave to amend under 8 these circumstances is a mere procedural formality. See Dkt. No. 216 at 5. 9 The problem with this argument is that it contradicts Finjan’s own representations to the 10 Court about its infringement theories. In February 2019, Finjan asserted two types of 11 infringement with respect to the Gateways and ESA instrumentalities: (1) “on the box” without 12 connection to cloud-based components, and (2) in combination with Capture ATP. Because the 13 Court did not give Finjan leave to amend to add an additional theory—i.e., the Gateways and ESA 14 instrumentalities infringe in combination with other cloud-based components such as the 15 CloudAV and GRID sandboxes—Finjan was required to seek leave of the Court before including 16 that theory in its infringement contentions. It did not seek leave. Finjan argues that it could not 17 have known its unauthorized addition of the sandbox contentions was a problem until the Court 18 said so in November 2019. Dkt. No. 232 at 10:1-11 (“It wasn’t until November 20th that we were 19 made aware from this Court that . . . [GRID] and Cloud AV were actually new contentions in 20 [t]his case . . . . So I would say that the diligence period doesn’t start until, you know, the earliest 21 of November 20th, 2019 . . . .”). That argument is not credible, given Finjan’s specific 22 representations to the Court in February 2019 about its theories of infringement and the well23 established requirements of the Patent Local Rules governing amendments. See Dkt. No. 210 at 424 6 (rejecting Finjan’s argument that its May 2019 contentions disclosed existing infringement 25 theories with greater particularity). 26 By Finjan’s own account, the delay between Finjan’s discovery of new evidence 27 supporting its sandbox contentions and its December 2019 motion for leave to amend is eight 1 months.3 Finjan bears the burden of establishing that it was diligent in seeking amendment of its 2 contentions in these circumstances. Critical to this inquiry is the connection between the proposed 3 amendments and the newly discovered evidence. Synopsys, Inc. v. ATopTech, Inc., No. 13-cv4 02965-MMC (DMR), 2016 WL 4945489 , at *3 (N.D. Cal. Sept. 16, 2016). Finjan argues that, 5 despite diligently seeking discovery from SonicWall, Finjan only “recently” obtained technical 6 documents and source code for the CloudAV and GRID sandboxes. Dkt. No. 216 at 3, 5; Dkt. No. 7 225 at 1, 2. By “recently,” the Court understands Finjan to mean that it obtained new evidence in 8 April or May 2019, after serving its first supplemental infringement contentions in November 9 2018. In its opening brief, Finjan describes the circumstances of its discovery of new evidence as 10 follows: 11 SonicWall stymied Finjan’s diligent discovery efforts, delaying Finjan’s ability to present these infringement contentions 12 prior to May 2019. Since October 3, 2018, Finjan sought discovery of detailed technical information about SonicWall’s GRID and 13 CloudAV sandboxes. At the time Finjan served its May 2019 infringement contentions, SonicWall still had not made any detailed 14 technical disclosures regarding the GRID or CloudAV sandboxes so it was unclear if any to what extent the functionalities of either 15 sandbox utilized components in the cloud versus on the box. . . . Finjan eventually sought relief from the Court, which ordered 16 SonicWall to run additional keyword searches for the production of detailed technical documents relating to these topics. [17] Finjan also diligently attempted to obtain relevant details 18 about the accused instrumentalities, and Grid [sic] and CloudAV in particular, through deposition of 30(b)(6) topics, including for 19 example, “[t]he use of SonicWall’s Capture Labs and GRID Threat Network by the Accused Instrumentalities.”). Still no depositions 20 have taken place to date. 21 Finjan also repeatedly pressed Sonic Wall to provide source code for GRID, WXA, SMA and data for the Thumbprint database. 22 SonicWall only made some of this source code available for inspection, but not until August 2019, forcing Finjan to use the 23 limited discovery available to it to include this functionality in the May 2019 Contentions. [24] Dkt. No. 216 at 5–6 (citations omitted). Finjan does not tie any information that SonicWall [26] 3 In its opening brief, Finjan says it obtained new evidence from SonicWall in April 2019, but in [27] its reply brief, Finjan says it did not have the critical discovery until May 2019. Compare Dkt. 1 belatedly produced to Finjan’s proposed sandbox contentions. In fact, Finjan concedes that its 2 proposed amendments are supported entirely with citations to documents and source code that 3 SonicWall produced in May and November 2018. See Dkt. No. 221 at 1, 3–5, 8. However, in its 4 reply brief, Finjan argues that the new information justifying its amendments is not any particular 5 evidence SonicWall produced, but rather SonicWall’s counsel’s representation that the source 6 code for the GRID sandbox overlaps with the source code for Capture ATP. See Dkt. No. 225 at 7 2. Putting aside Finjan’s improper reliance on an argument made for the first time in its reply 8 brief, the Court has reviewed the communications between counsel on which Finjan relies. See 9 Dkt. No. 215-6, Ex. 3 at 5–9. Those exchanges reflect disagreement between counsel regarding 10 characterization of “GRID,” “CloudAV,” and “Capture ATP.” But even if the Court were to adopt 11 Finjan’s interpretation of these exchanges, it is not clear how SonicWall’s alleged representation 12 about the relationship between the GRID sandbox source code and the Capture ATP source code 13 supports the proposed amendments or justifies Finjan’s delay in seeking leave to amend. 14 Finjan urges the Court to overlook its failure to seek leave earlier because, it argues, 15 SonicWall has had the benefit of disclosure of Finjan’s sandbox contentions since at least May 31, 16 2019 and did not move to strike those contentions for four months. Dkt. No. 216 at 2, 6; Dkt. No. 17 225 at 8. While these arguments might bear on the Court’s consideration of whether SonicWall 18 has suffered prejudice, the Court need not reach the question of prejudice unless it is satisfied that 19 Finjan has been diligent in seeking amendment. O2 Micro Int’l Ltd. v. Monolithic Power Sys., 20 Inc., 467 F.3d 1355 , 1368 (Fed. Cir. 2006); Synopsys, 2016 WL 4945489 , at *5. Here, Finjan’s 21 failure to move promptly for leave to amend—before adding new infringement contentions— 22 contravenes one of the principal objectives of the Patent Local Rules: achieving certainty as to the 23 patent holder’s theories of infringement and the accused infringer’s theories of invalidity. See O2 24 Micro, 467 F.3d at 1365–66; Nova Measuring Instruments Ltd. v. Nanometrics, Inc., 417 F. Supp. 25 2d 1121, 1123 (N.D. Cal. 2006) (“The [patent local] rules are designed to require parties to 26 crystallize their theories of the case early in the litigation and to adhere to those theories once they 27 have been disclosed.”). 1 the sandbox contentions in Finjan’s May 2019 second supplemental infringement contentions, or 2 for Finjan’s eight-month delay in seeking leave to amend. The record contains no evidence that 3 SonicWall misled Finjan about its position with respect to the second supplemental infringement 4 contentions. See O2 Micro, 467 F.3d at 1367 (suggesting that one party’s misleading conduct 5 regarding stipulated amendment might justify delay in seeking leave of court). Rather, in failing 6 to seek leave as the Patent Local Rules require, Finjan took a risk that SonicWall would object to 7 the new infringement contentions. SonicWall did object, and the Court finds the objections are 8 well taken. 9 Finjan has not demonstrated diligence in seeking leave to amend its infringement theories 10 with respect to the sandbox contentions for the ’926, ’305, ’844, ’633, ’154, ’780, ’822, and ’494 11 patents. 12 2. Stats server/URL Thumbprint Database and WXA appliances 13 Finjan’s briefing provides very little discussion in support of its amendments adding the 14 Stats server and URL Thumbprint Database to the contentions for the ’154 patent and adding 15 WXA appliances to the contentions for the ’968 patent. Dkt. No. 216 at 6; Dkt. No. 225 at 7. 16 Finjan argues that it could not have made the proposed amendments prior to May 2019 because 17 SonicWall did not make relevant source code information available for inspection until August 18 2019, thus Finjan was forced to rely on the only information it had available at the time. Dkt. No. 19 216 at 6; Dkt. No. 225 at 7; but see Dkt. No. 232 at 22:19-21 (asserting that SonicWall did not 20 produce source code for Stats server and URL Thumbprint Database until May 2019). 21 The problem with Finjan’s argument is that, by its own admission, there are no differences 22 between its second supplemental infringement contentions served in May 2019 and the proposed 23 amendments it now seeks to make. Finjan does not refer to any source code or other technical 24 documentation made available for the first time in August 2019. In particular, Finjan does not 25 explain how its discovery of any new information ties to its proposed amendments, which is 26 critical to the Court’s assessment of diligence. Synopsys, 2016 WL 4945489 , at *3–5. 27 Finjan has not demonstrated diligence in seeking leave to amend with respect to its 1 with respect to the WXA appliances for the ’968 patent. 2 B. Prejudice to SonicWall 3 Because the Court concludes that Finjan has not acted diligently in seeking leave to amend 4 || its contentions, it does not reach the question of whether SonicWall would suffer prejudice if the 5 amendments are permitted. O2 Micro, 467 F.3d at 1368; Synopsys, 2016 WL 49454839 , at *5. 6 || IV. CONCLUSION 7 For the foregoing reasons, Finjan’s motion for leave to amend its infringement contentions 8 || is denied. 9 IT IS SO ORDERED. 10 Dated: March 9, 2020 [11] 2 □ 2 ‘ VIRGINIA K. DEMARCHI 13 United States Magistrate Judge [16] it 4 18