Searching over 5,500,000 cases.

Buy This Entire Record For $7.95

Download the entire decision to receive the complete text, official citation,
docket number, dissents and concurrences, and footnotes for this case.

Learn more about what you receive with purchase of this case.

Symantec Corp. v. Zscaler, Inc.

United States District Court, N.D. California

July 18, 2019

ZSCALER, INC., Defendant.

          DISCOVERY ORDER RE: DKT. NOS. 290, 291, 293, 294, 295, 297


         The Court had a telephonic hearing this afternoon concerning the parties' joint discovery letter briefs at ECF Nos. 291, 294 and 297. The Court now issues the following order on them and the related motions to seal.


         A. ECF No. 291

         Zscaler moves for a protective order to bar Symantec from deposing Kailash Kailash, its Chief Architect and co-founder, under the apex doctrine. In general, “[w]hen a party seeks the deposition of a high-level executive (a so-called ‘apex' deposition), the court may exercise its discretion under the federal rules to limit discovery.” Anderson v. Cty. of Contra Costa, 2017 WL 930315, at *3 (N.D. Cal. March 9, 2017) (citations and quotation marks omitted). “Discretion is necessary because apex depositions create a tremendous potential for abuse or harassment.” Id. (citations and quotation marks omitted). “Courts may limit discovery after considering (1) whether the deponent has unique first-hand, non-repetitive knowledge of the facts at issue in the case and (2) whether the party seeking the deposition has exhausted other less intrusive discovery methods.” Id. (citations and quotation marks omitted).

         Zscaler has failed to show that Kailash is a high-level executive. Zscaler's March 5, 2018 SEC Form S-1 identified the company's “executive officers and directors as of January 31, 2018.” It listed the CEO, CSO, CFO, CLO, CTO and COO as executive officers, but not the Chief Architect. Nor is Kailash a member of the Board of Directors. Symantec provided a Zscaler organizational chart in connection with the letter brief, and it shows that no one reports to Kailash - unlike the CEO, CSO, CFO, CLO, CTO and COO, who all have direct reports.[1] Oddly, Zscaler has put Jay Chaudry (the company's other co-founder, its CEO, and the Chairman of the Board) up for deposition and designated Amit Sinha (the CTO and a member of the Board of Directors) as a 30(b)(6) witness, even though Chaudry and Sinha are clearly higher level within the company than Kailash is. This is an inversion of the apex doctrine, offering up the highest-level executives and trying to block the deposition of someone less important. This is not what the apex doctrine is for.

         Regardless, even if Kailash were an apex witness, because he has been the Chief Architect of the accused platform since 2008, he likely has unique, non-repetitive knowledge. That's what the title “Chief Architect” implies. Zscaler refers to other witnesses Symantec has deposed but does not explain how they obviate the need to depose Kailash. Further, the fact that Kailash is listed as an inventor on several Zscaler patents related to the technology at issue in this case underscores his personal involvement in the development of the technology and makes it likely that he has unique, non-repetitive knowledge.

         Accordingly, Zscaler's motion for a protective order is DENIED.

         B. ECF No. 294

         This motion came into sharper focus during the hearing. In response to RFP 111, Zscaler is now seeking a visual inspection of the hardware on which Symantec's security software runs for those products listed in RFP 111 that are delivered to customers on hardware appliances. Zscaler is not asking to plug the hardware in, turn it on, or use it - just to look at it.

         This visual inspection has some relevance. Not a lot, but some. The patents in suit concern Symantec's software, not any hardware. Still, the extent to which Symantec's on-premise products compete with Zscaler's cloud offering is relevant to issues in the case other than liability. It used to be relevant to Symantec's lost profits claim, but Symantec has now abandoned that. It is still relevant to Symantec's claim for a permanent injunction. And it's relevant to whether Zscaler and Symantec are competitors in the same territory in the same line of business, which is one of the Georgia-Pacific factors in determining a reasonable royalty.

         To be sure, the primary evidence about whether Symantec's on-premise products compete with Zscaler's cloud offering would be market research, customer surveys, market-wide business trends, and the like. After all, the issue comes down to customer demand and whether customers view these products as alternatives to each other. There are probably a number of reasons customers have for thinking or not thinking of these products as alternatives to each other, such as cost, ease of use, effectiveness, and vendor reputation. But surely one of the most obvious differences is that an on-premise product requires the customer to install one or more pieces of hardware at its facility. The hardware takes up space. It uses energy. It probably has to be put somewhere secure and air conditioned. It's a piece of equipment that has to be cared for.

         What this equipment looks like, including how big it is, how it is shaped, how many cords it has, and so on, is relevant. What really matters, of course, is how customers perceive the hardware and the burdens it imposes, but even evidence of customer or market perception is made more understandable if Zscaler is able to do a visual inspection and bring along its witnesses and experts to take pictures of the hardware. This visual inspection of the hardware that has to be installed at the customer site lends concreteness to the difference between an on-premise product and a cloud offering. For example, pictures Zscaler takes of the hardware would make it easier for the trier of fact to appreciate the difference between Symantec's on-premise products and Zscaler's cloud product.

         Symantec says this will be burdensome, but its explanation of burden is unimpressive. Essentially, Symantec would have to find examples of its own products that are currently in its supply chain, ship them to a location, take them out of the boxes, and then ...

Buy This Entire Record For $7.95

Download the entire decision to receive the complete text, official citation,
docket number, dissents and concurrences, and footnotes for this case.

Learn more about what you receive with purchase of this case.