1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 NETSKOPE, INC., Case No. 25-cv-02360-HSG
8 Plaintiff, ORDER GRANTING IN PART AND DENYING IN PART DEFENDANT 9 v. FORTINET, INC.’S MOTION TO DISMISS 10 FORTINET, INC., Re: Dkt. No. 37 11 Defendant.
12 13 Pending before the Court is Defendant Fortinet, Inc.’s (“Fortinet”) motion to dismiss. Dkt. 14 No. 37. The Court found the matter appropriate for disposition without oral argument and took 15 the matter under submission. See Civil L.R. 7-1(b). For the following reasons, the Court 16 GRANTS IN PART and DENIES IN PART Fortinet’s motion with leave to amend. 17 I. BACKGRUOND 18 Plaintiff Netskope, Inc. (“Netskope”) filed this case on March 7, 2025 accusing Fortinet of 19 infringing nine patents: U.S. Patent Nos. 8,356,336 (the “’336 Patent”); 8,543,710 (the “’710 20 Patent”); 8,117,639 (the “’639 Patent”); 8,224,983 (the “’983 Patent”); 8,327,426 (the “’426 21 Patent”); 7,593,936 (the “’936 Patent”); 8,397,282 (the “’282 Patent”); 8,661,153 (the “’153 22 Patent”); and 8,635,697 (the “’697 Patent”) (collectively, the “Asserted Patents”). Dkt. No. 1. 23 Netskope filed an amended complaint on April 14, 2025, Dkt. No. 13, which Fortinet moved to 24 dismiss on May 30, 2025. Dkt. No. 22. In conjunction with its opposition brief, Netskope filed a 25 second amended complaint (“SAC”). Dkt. No. 29. Fortinet moved to dismiss again, Dkt. No. 37, 26 and Netskope opposed and further sought to amend its pleading. Dkt. No. 44; Dkt. No. 44-28. 27 Netskope alleges that Fortinet infringed the Asserted Patents through features Fortinet built 1 and FortiAP infringe the ’336 and ’710 Patents, id. ¶¶ 386, 403; FortiGate and FortiOS infringe 2 the ’639 Patent, id. ¶ 420; FortiGate infringes the ’983 and ’153 Patents, id. ¶¶ 437, 505; FortiGate 3 NGFW infringes the ’282 Patent, id. ¶ 488; FortiOS infringes the ’697 Patent, id. ¶ 522; and 4 FortiAuthenticator infringes the ’426 Patent, id. ¶ 454. For each of the Asserted Patents, Netskope 5 alleges that the infringing features are “specifically programmed and adapted [to be] central to the 6 products’ operation,” and the features “are not staple articles of commerce suitable for substantial 7 non-infringing uses.” Id. ¶¶ 386, 403, 420, 437, 454, 471, 488, 505, 522. 8 II. LEGAL STANDARD 9 Federal Rule of Civil Procedure 8(a) requires that a complaint contain “a short and plain 10 statement of the claim showing that the pleader is entitled to relief.” Fed. R. Civ. P. 8(a)(2). A 11 defendant may move to dismiss a complaint for failing to state a claim upon which relief can be 12 granted under Rule 12(b)(6). “Dismissal under Rule 12(b)(6) is appropriate only where the 13 complaint lacks a cognizable legal theory or sufficient facts to support a cognizable legal theory.” 14 Mendiondo v. Centinela Hosp. Med. Ctr., 521 F.3d 1097, 1104 (9th Cir. 2008). To survive a Rule 15 12(b)(6) motion, a plaintiff need only plead “enough facts to state a claim to relief that is plausible 16 on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). A claim is facially plausible 17 when a plaintiff pleads “factual content that allows the court to draw the reasonable inference that 18 the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). 19 In reviewing the plausibility of a complaint, courts “accept factual allegations in the complaint as 20 true and construe the pleadings in the light most favorable to the nonmoving party.” Manzarek v. 21 St. Paul Fire & Marine Ins. Co., 519 F.3d 1025, 1031 (9th Cir. 2008). Nevertheless, courts do not 22 “accept as true allegations that are merely conclusory, unwarranted deductions of fact, or 23 unreasonable inferences.” In re Gilead Scis. Secs. Litig., 536 F.3d 1049, 1055 (9th Cir. 2008) 24 (quoting Sprewell v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001)). 25 III. ANALYSIS 26 Section 271(a) provides that “whoever without authority makes, uses, offers to sell, or sells 27 any patented invention… during the term of the patent therefor, infringes the patent.” 35 U.S.C. 1 direct infringement by a third party. See In re Bill of Lading Transmission & Processing Sys. 2 Patent Litig., 681 F.3d 1323, 1333 (Fed. Cir. 2012). Fortinet does not contest Netskope’s direct 3 infringement allegations here. It only challenges Netskope’s indirect infringement claims 4 regarding three patents, and contributory infringement claims regarding all of the patents. 5 A. Indirect Infringement Related to the ’153, ’983, and ’639 Patents 6 Fortinet contends that it lacked knowledge of the ’153, ’983, and ’639 Patents such that it 7 could not be liable for indirect infringement. Dkt. No. 37 at 10–12. Netskope argues that Fortinet 8 waived this argument by not raising it an earlier motion to dismiss. Dkt. No. 44 at 3–4. Netskope 9 also contends that Fortinet had notice of the patents because it cited the ’153 patent application 10 and genealogically related patent applications in exchanges with the USPTO, and because it had 11 robust knowledge of patents in this field. Id. at 4–6. 12 i. Waiver under Rule 12(g)(2) 13 Netskope argues that Fortinet waived the argument that it lacked knowledge of the patents 14 because it did not raise it in its first motion to dismiss. Dkt. No. 44 at 3 (citing Fed. R. Civ. P. 15 12(g)(2)); see Dkt. No. 22. Fortinet responds that this claim is inapplicable where the Court did 16 not decide the prior motion on the merits. Dkt. No. 46 at 7. 17 Under Rule 12(g)(2), “[e]xcept as provided in Rule 12(h)(2) or (3), a party that makes a 18 motion under this rule must not make another motion under this rule raising a defense or objection 19 that was available to the party but omitted from its earlier motion.” But courts in this Circuit have 20 not applied Rule 12(g)(2) as a bar when the court did not decide the first motion to dismiss on the 21 merits. See, e.g., Kilopass Tech, Inc. v. Sidense Corp., No. 10-cv-2066-SI, 2010 WL 5141843, at 22 *3 (N.D. Cal. Dec. 13, 2010). And even then, courts read Rule 12(g)(2) in light of the general 23 policy of securing a “just, speedy, and inexpensive determination of every action and proceeding.” 24 In re Apple iPhone Antitrust Litig., 846 F.3d 313, 318 (9th Cir. 2017) (quoting Fed. R. Civ. P. 1). 25 This means that courts have discretion to decide a successive motion to dismiss if doing so would 26 lead to a speedier resolution of the case. Id. Denying a successive motion to dismiss on waiver 27 grounds “can produce unnecessary and costly delays, contrary to the direction of Rule 1.” Id. 1 tactics.” See Allstate Ins. Co. v. Countrywide Fin. Corp., 524 F.Supp.2d 1164, 1175 (C.D. Cal. 2 2011). Netskope filed an amended complaint on April 15, 2025, Dkt. No.
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 NETSKOPE, INC., Case No. 25-cv-02360-HSG
8 Plaintiff, ORDER GRANTING IN PART AND DENYING IN PART DEFENDANT 9 v. FORTINET, INC.’S MOTION TO DISMISS 10 FORTINET, INC., Re: Dkt. No. 37 11 Defendant.
12 13 Pending before the Court is Defendant Fortinet, Inc.’s (“Fortinet”) motion to dismiss. Dkt. 14 No. 37. The Court found the matter appropriate for disposition without oral argument and took 15 the matter under submission. See Civil L.R. 7-1(b). For the following reasons, the Court 16 GRANTS IN PART and DENIES IN PART Fortinet’s motion with leave to amend. 17 I. BACKGRUOND 18 Plaintiff Netskope, Inc. (“Netskope”) filed this case on March 7, 2025 accusing Fortinet of 19 infringing nine patents: U.S. Patent Nos. 8,356,336 (the “’336 Patent”); 8,543,710 (the “’710 20 Patent”); 8,117,639 (the “’639 Patent”); 8,224,983 (the “’983 Patent”); 8,327,426 (the “’426 21 Patent”); 7,593,936 (the “’936 Patent”); 8,397,282 (the “’282 Patent”); 8,661,153 (the “’153 22 Patent”); and 8,635,697 (the “’697 Patent”) (collectively, the “Asserted Patents”). Dkt. No. 1. 23 Netskope filed an amended complaint on April 14, 2025, Dkt. No. 13, which Fortinet moved to 24 dismiss on May 30, 2025. Dkt. No. 22. In conjunction with its opposition brief, Netskope filed a 25 second amended complaint (“SAC”). Dkt. No. 29. Fortinet moved to dismiss again, Dkt. No. 37, 26 and Netskope opposed and further sought to amend its pleading. Dkt. No. 44; Dkt. No. 44-28. 27 Netskope alleges that Fortinet infringed the Asserted Patents through features Fortinet built 1 and FortiAP infringe the ’336 and ’710 Patents, id. ¶¶ 386, 403; FortiGate and FortiOS infringe 2 the ’639 Patent, id. ¶ 420; FortiGate infringes the ’983 and ’153 Patents, id. ¶¶ 437, 505; FortiGate 3 NGFW infringes the ’282 Patent, id. ¶ 488; FortiOS infringes the ’697 Patent, id. ¶ 522; and 4 FortiAuthenticator infringes the ’426 Patent, id. ¶ 454. For each of the Asserted Patents, Netskope 5 alleges that the infringing features are “specifically programmed and adapted [to be] central to the 6 products’ operation,” and the features “are not staple articles of commerce suitable for substantial 7 non-infringing uses.” Id. ¶¶ 386, 403, 420, 437, 454, 471, 488, 505, 522. 8 II. LEGAL STANDARD 9 Federal Rule of Civil Procedure 8(a) requires that a complaint contain “a short and plain 10 statement of the claim showing that the pleader is entitled to relief.” Fed. R. Civ. P. 8(a)(2). A 11 defendant may move to dismiss a complaint for failing to state a claim upon which relief can be 12 granted under Rule 12(b)(6). “Dismissal under Rule 12(b)(6) is appropriate only where the 13 complaint lacks a cognizable legal theory or sufficient facts to support a cognizable legal theory.” 14 Mendiondo v. Centinela Hosp. Med. Ctr., 521 F.3d 1097, 1104 (9th Cir. 2008). To survive a Rule 15 12(b)(6) motion, a plaintiff need only plead “enough facts to state a claim to relief that is plausible 16 on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). A claim is facially plausible 17 when a plaintiff pleads “factual content that allows the court to draw the reasonable inference that 18 the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009). 19 In reviewing the plausibility of a complaint, courts “accept factual allegations in the complaint as 20 true and construe the pleadings in the light most favorable to the nonmoving party.” Manzarek v. 21 St. Paul Fire & Marine Ins. Co., 519 F.3d 1025, 1031 (9th Cir. 2008). Nevertheless, courts do not 22 “accept as true allegations that are merely conclusory, unwarranted deductions of fact, or 23 unreasonable inferences.” In re Gilead Scis. Secs. Litig., 536 F.3d 1049, 1055 (9th Cir. 2008) 24 (quoting Sprewell v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001)). 25 III. ANALYSIS 26 Section 271(a) provides that “whoever without authority makes, uses, offers to sell, or sells 27 any patented invention… during the term of the patent therefor, infringes the patent.” 35 U.S.C. 1 direct infringement by a third party. See In re Bill of Lading Transmission & Processing Sys. 2 Patent Litig., 681 F.3d 1323, 1333 (Fed. Cir. 2012). Fortinet does not contest Netskope’s direct 3 infringement allegations here. It only challenges Netskope’s indirect infringement claims 4 regarding three patents, and contributory infringement claims regarding all of the patents. 5 A. Indirect Infringement Related to the ’153, ’983, and ’639 Patents 6 Fortinet contends that it lacked knowledge of the ’153, ’983, and ’639 Patents such that it 7 could not be liable for indirect infringement. Dkt. No. 37 at 10–12. Netskope argues that Fortinet 8 waived this argument by not raising it an earlier motion to dismiss. Dkt. No. 44 at 3–4. Netskope 9 also contends that Fortinet had notice of the patents because it cited the ’153 patent application 10 and genealogically related patent applications in exchanges with the USPTO, and because it had 11 robust knowledge of patents in this field. Id. at 4–6. 12 i. Waiver under Rule 12(g)(2) 13 Netskope argues that Fortinet waived the argument that it lacked knowledge of the patents 14 because it did not raise it in its first motion to dismiss. Dkt. No. 44 at 3 (citing Fed. R. Civ. P. 15 12(g)(2)); see Dkt. No. 22. Fortinet responds that this claim is inapplicable where the Court did 16 not decide the prior motion on the merits. Dkt. No. 46 at 7. 17 Under Rule 12(g)(2), “[e]xcept as provided in Rule 12(h)(2) or (3), a party that makes a 18 motion under this rule must not make another motion under this rule raising a defense or objection 19 that was available to the party but omitted from its earlier motion.” But courts in this Circuit have 20 not applied Rule 12(g)(2) as a bar when the court did not decide the first motion to dismiss on the 21 merits. See, e.g., Kilopass Tech, Inc. v. Sidense Corp., No. 10-cv-2066-SI, 2010 WL 5141843, at 22 *3 (N.D. Cal. Dec. 13, 2010). And even then, courts read Rule 12(g)(2) in light of the general 23 policy of securing a “just, speedy, and inexpensive determination of every action and proceeding.” 24 In re Apple iPhone Antitrust Litig., 846 F.3d 313, 318 (9th Cir. 2017) (quoting Fed. R. Civ. P. 1). 25 This means that courts have discretion to decide a successive motion to dismiss if doing so would 26 lead to a speedier resolution of the case. Id. Denying a successive motion to dismiss on waiver 27 grounds “can produce unnecessary and costly delays, contrary to the direction of Rule 1.” Id. 1 tactics.” See Allstate Ins. Co. v. Countrywide Fin. Corp., 524 F.Supp.2d 1164, 1175 (C.D. Cal. 2 2011). Netskope filed an amended complaint on April 15, 2025, Dkt. No. 13, which Fortinet 3 moved to dismiss on May 30. Dkt. No. 22. Netskope opposed the motion to dismiss and 4 separately filed a second amended complaint, Dkt. Nos. 29–30, leading to the termination of 5 Fortinet’s motion. Dkt. No. 34. This motion addresses the sufficiency of the Second Amended 6 Complaint. Dkt. No. 37. There is no implication that Fortinet sought delay by seeking the Court’s 7 determination—for the first time—as to the sufficiency of the pleadings. The Court finds that 8 Fortinet did not waive its indirect infringement arguments, and will address them on the merits. 9 ii. Merits 10 To plead an indirect infringement claim, a plaintiff must allege plausible facts showing that 11 the defendant “knew of the patent and that ‘the induced acts constitute patent infringement.’” 12 Commil USA, LLC v. Cisco Sys., Inc., 575 U.S. 632, 639 (2015) (quoting Global-Tech Appliances, 13 Inc. v. SEB S.A., 563 U.S. 754, 766 (2011)). 14 Netskope argues the SAC sufficiently alleges knowledge of the ’153, ’983, and ’639 15 Patents. Dkt. No. 44. It contends that that Fortinet referred to the ’153 Patent application in 16 Information Disclosure Statements (IDSs) to the USPTO, id. at 4–6, that the ’983 Patent is a direct 17 continuation of the ’153 Patent, id. at 6, and that Fortinet had a practice of monitoring a portfolio 18 of patents, which included the ’153, ’983, and ’639 Patents. Id. at 6–7. Fortinet counters that all 19 three patents were expired at the time Netskope notified it of these patents in a November 2024 20 letter and that this new evidence does not save the indirect infringement claims. Dkt. No. 37 at 21 10–11; Dkt. No. 46 at 8–11. It suggests that knowledge of a patent application cannot give a party 22 knowledge of the later issued patent, and that knowledge of one patent (or patent application) 23 cannot give a party knowledge of another patent’s claims. Id. 24 But Netskope’s argument does not rely on the Second Amended Complaint: instead, it 25 cites new exhibits attached to its opposition, and seeks leave to file yet another amended 26 complaint.1 See Dkt. No. 44 at 4–6. Netskope does not appear to contest that its Second 27 1 Amended Complaint is deficient regarding Fortinet’s knowledge of the three patents. Id. at 14. 2 Since Netskope does not defend the three contested indirect infringement claims actually raised in 3 the Second Amended Complaint, the Court DISMISSES them with leave to amend. 4 To streamline any future motions practice, the Court addresses Netskope’s new arguments. 5 “Filing an application is no guarantee any patent will issue and a very substantial percentage of 6 applications never result in patents. What the scope of claims in patents that do issue will be is 7 something totally unforeseeable.” State Industries, Inc. v. A.O. Smith Corp., 751 F.2d. 1226, 1236 8 (Fed. Cir. 1985). Numerous cases from this district have found that knowledge of a patent 9 application is insufficient to establish knowledge of a later issued patent. See, e.g., NetFuel, Inc. v. 10 Cisco Sys. Inc., No. 18-cv-2352-EJD, 2018 WL 4510737, at *1–2 (N.D. Cal. Sept. 18, 2018); VIA 11 Techs., Inc. v. ASUS Computer Int’l, No. 14-cv-3586-BLF, 2015 WL 3809382, at *3 (N.D. Cal. 12 June 18, 2015); Vasudevan Software, Inc. v. TIBCO Software, Inc., No. 11-cv-6638-RS, 2012 WL 13 1831543, at *3 (N.D. Cal. May 18, 2012); see also WCM Indus., Inc. v. IPS Corp., 721 F.App’x 14 959, 970 & n.4 (Fed. Cir. 2018) (declining to decline whether “knowledge of a pending patent 15 application cannot support a finding of willfulness”). A citation to a patent application in an IDS 16 similarly does not establish knowledge of the later issued patent. See MasterObjects, Inc. v. 17 Amazon.com, Inc., No. 20-cv-8103-WHA, 2021 WL 4685306, at *4 (N.D. Cal. Oct. 7, 2021). A 18 plaintiff might have a better argument when the IDS cites the application of an already issued 19 patent. Id. 20 Awareness of a relative or similar patent is also insufficient to establish knowledge of a 21 separate issued patent. See, e.g., Fluidigm Corp. v. IONpath, Inc., No. 19-cv-5639-WHA, 2020 22 WL 408988, at *3 (N.D. Cal. Jan. 24, 2020); Software Rsch, Inc. v. Dynatrace LLC, 316 23 F.Supp.3d 1112, 1133 (N.D. Cal. 2018) (cannot infer knowledge of from knowledge of other 24 patents). And general monitoring of a portfolio of patents alone is not enough to establish 25 knowledge. NetFuel, Inc., No. 18-cv-2352-EJD, 2018 WL 4510737, at *2–3; Vasudevan 26 Software, No. 11-cv-6638-RS, 2012 WL 1831543, at *3. 27 1 *** 2 Fortinet’s motion to dismiss the indirect infringement claims related to the ’153, ’983, and 3 ’639 Patents is GRANTED with leave to amend if Netskope can truthfully do so consistent with 4 counsel’s Rule 11 obligations and the authority discussed above. 5 B. Contributory Infringement 6 To adequately plead contributory infringement, a plaintiff must tie the specific infringing 7 components of the allegedly infringing products to an infringing use and plausibly allege that the 8 component has no substantial non-infringing uses. As explained in Bill of Lading: 9 Contributory infringement occurs if a party sells or offers to sell, a material or apparatus for use in practicing a patented process, and that 10 material or apparatus is material to practicing the invention, has no substantial non-infringing uses, and is known by the party to be 11 especially made or especially adapted for use in an infringement of such patent. 12 In re Bill of Lading, 681 F.3d at 1337 (internal citations and quotations omitted); see also Fortinet, 13 Inc. v. Forescout Techs., Inc., 543 F. Supp. 3d 814, 839–40 (N.D. Cal. 2021) (finding sufficient 14 allegations that allowed the “inference” that components of the accused product lacked substantial 15 non-infringing uses) (emphasis in original); Software Rsch., 316 F. Supp. 3d at 1136 (finding 16 sufficient allegations that the accused product, “when used in its normal and intended” way, 17 infringes). 18 Netskope alleges that Fortinet’s products used in combination include features that infringe 19 its patents. SAC ¶¶ 386, 403, 420, 437, 454, 471, 488, 505, 522. Netskope’s opposition quotes 20 from the allegations and explains why those allegations are sufficient to create at least a 21 reasonable inference of infringement. Dkt. No. 44 at 7–9. Netskope argues that “Any 22 hypothetical non-infringing use would require disabling the very functionality at issue. 23 Accordingly, these features, as described, do not have any substantial noninfringing uses.” Id. The 24 Court observes that Netskope pleads the absence of “substantial non-infringing uses” throughout 25 its complaint. SAC ¶¶ 386, 403, 420, 437, 454, 471, 488, 505, 522. 26 Fortinet moves to dismiss the contributory infringement counts on the ground that 27 1 Netskope has not pled that there are no substantial non-infringing uses.2 Dkt. No. 37 at 11–16. 2 Fortinet makes three arguments. First, Fortinet contends that the pleadings are deficient because 3 they contain conclusory allegations. Id. at 11–13. Second, Fortinet argues that Netskope’s 4 allegations that the Accused Products were specifically designed and intended to operate in an 5 allegedly infringing manner are insufficient as a matter of law. Id. at 13–15. And lastly, Fortinet 6 suggests that Netskope’s pleading is insufficient because the accused features are not separable 7 components, such that the Accused Products have substantial non-infringing uses. Dkt. No. 37 at 8 15–16. The Court finds Fortinet’s arguments unconvincing. 9 First, Fortinet argues that Netskope’s pleadings are deficient as generally pled. Netskope 10 cites to Fortinet v. Forescout to support its position that its pleading was sufficient as a matter of 11 law. Dkt. No. 44 at 9. In that case, the complaint contained the same paragraph regarding each 12 patent, which alleged “software components. . . are especially made for an infringing use, and 13 have no substantial noninfringing use.” Fortinet, 543 F.Supp.3d at 839. There, Judge Chen 14 considered the “issue is a close one” but found the allegations sufficient. Id. at 840. Pleading that 15 an accused product is incapable of substantial non-infringing use necessarily involves some degree 16 of stated conclusions. Id. at 840. But Judge Chen found that allegations that “software 17 components are ‘programmed… to infringe’ are sufficient to ‘allow an inference that the 18 components… have no substantial non-infringing uses.’” Id. (quoting In re Bill of Lading, 681 19 F.3d at 1337); see also Software Rsch., 316 F.Supp.3d at 1136 (allegation that product was 20 “especially made or especially adapted for use in infringement,” and infringed “in its normal and 21 intended usage” sufficient); AlexSam, Inc. v. Aetna, Inc., 119 F.4th 27, 46–47 (Fed. Cir. 2024) 22 (allegation that component was “especially adapted for use in the infringing systems, and it has no 23 substantial non-infringing uses” was sufficient when supported by expert declaration). The Court 24 similarly finds that Netskope’s pleading here alleges enough. 25 Second, Fortinet contends that the contributory infringement allegations are contradicted 26
27 2 Since Netskope failed to plead that Fortinet had knowledge of the ’153, ’983, and ’639 Patents, 1 by two documents cited in, but not attached to, the complaint. Dkt. No. 46 at 14. The first is a 2 marketing brochure regarding the FortiAP Series that was partially quoted in the complaint. SAC 3 ¶ 403 & n.29.3 The full quotation states that, “FortiAP access points are managed centrally by the 4 integrated WLAN controller of any FortiGate® security appliance or can be managed through the 5 free FortiCloud provisioning and management portal… This enables you to easily manage wired 6 and wireless security from a Single-pane-of-glass management console and protects your network 7 from the latest security threats.” Dkt. No. 37-6 at 1 (emphasis added to phrase omitted from 8 complaint). Fortinet argues that since Netskope did not present any evidence that FortiAP and 9 FortiCloud together infringe a patent, but has alleged that FortiAP and FortiGate working together 10 infringe patents and can only work together, the ’336 and ’710 Patent claims fail. Dkt. No. 37 at 11 13–14. But that was not Netskope’s argument. It alleged that any non-infringing use of the 12 products would require disabling the infringing features. Dkt. No. 44 at 8. Nothing in the full 13 quotation contradicts Netskope’s allegation. Making all reasonable inferences in favor of the non- 14 moving party, as the Court must at this stage, Fortinet has not shown any inherent contradiction in 15 Netskope’s allegations. 16 The second document is a 2,846-page administrative guide that, according to Fortinet, 17 shows that Netskope is only claiming a small subset of features infringe five of the patents. Dkt. 18 No. 37 at 14. Outside of its bare citation to paragraphs referring to this document, id. (citing SAC 19 ¶¶ 420, 437, 488, 505, 522), Fortinet does not explain how “the document forms the basis of the 20 plaintiff’s claim.” Khoja v. Orexigen Therapeutics, Inc., 899 F.3d 988, 1002 (9th Cir. 2018). As 21 such, Fortinet fails to meet its burden of showing that the Court may consider its contents on a 22 motion to dismiss. 23 Third, Fortinet argues that the accused features of its products are not separable, but 24 integrated components, such that the products could not infringe the patents because there are 25 substantial non-infringing uses of the product. It argues that Netskope’s complaint alleges that the 26
27 3 Fortinet argues that Netskope cited and relied upon this document by offering an incomplete ] allegedly infringing features are “central to the products’ operation” and therefore did not infringe, 2 || because they were part of a “comprehensive security platform.” Dkt. No. 37 at 15-16. Fortinet’s 3 argument is unpersuasive. On a motion to dismiss, the Court makes all reasonable assumptions in 4 || favor of the non-moving party. Fortinet’s argument assumes that when an infringing feature is 5 “central to the product’s operation” that the feature must be integral to aspects of the 6 || “comprehensive security platform.” Therefore, it contends the products at issue have substantial 7 || non-infringing uses. The Court cannot make this leap on a motion to dismiss.* 8 The Court DENIES Fortinet’s motion to dismiss the contributory infringement counts. 9 || IV. CONCLUSION 10 The Court GRANTS IN PART and DENIES IN PART Fortinet’s motion to dismiss, 11 with leave to amend. Dkt. No. 37. Any amended complaint must be filed within 21 days of the « 12 || date of this order and may not add any new claims or defendants.
13 IT IS SO ORDERED.
14 || Dated: March 6, 2026
HAYWOOD S. GILLIAM, JR. = 16 United States District Judge
Z 18 19 20 21 22 23 24 25 26 7 4 While not necessary to the outcome of the motion, Fortinet’s position also is not self-evidently correct. See Ricoh Co., Ltd. v. Quanta Computer Inc., 550 F.3d 1325, 1337-38 (Fed. Cir. 2008) 28 (finding that defendant could not “escape liability as a contributory infringer merely by embedding that microcontroller in a larger product with some additional, separable feature”).