Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 1 of 66 PageID #: 4408
`Case 1:23-cv-00758-JLH-SRF Document171-1 Filed 10/10/24 Page 1 of 66 PagelD #: 4408
`
`EXHIBIT 1
`EXHIBIT 1
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 2 of 66 PageID #: 4409
`
`McKenna, Krissy (BN)
`From:
`Bruner, Nicole (DC)
`Sent:
`Wednesday, October 2, 2024 4:55 PM
`To:
`Prasad, Praatika; #C-M ORCA SECURITY - WIZ - LW TEAM; JBlumenfeld@morrisnichols.com;
`RSmith@morrisnichols.com; cclark@morrisnichols.com
`WSGR - Orca Wiz; Cottrell@RLF.com; Farnan@RLF.com; haynes@rlf.com
`RE: Orca v. Wiz - Memorialization of 9/30 M&C
`
`Cc:
`Subject:
`
`Praatika,
`
`
`We disagree with your assertions below. It is also troubling that Wiz has refused to comply with the Court’s order to
`meet and confer to resolve or minimize disputes before bringing these issues to the Court, despite Orca repeatedly
`stating it would make itself available. We will address this and other inaccuracies in below in the parties’ briefing and/or
`at the hearing as necessary.
`
`
`Best,
`
`Nicole Elena Bruner
`
`
`LATHAM & WATKINS LLP
`555 Eleventh Street, NW | Suite 1000 | Washington, D.C. 20004-1304
`D: +1.202.654.7209 | M: +1.202.802.8093
`
`From: Prasad, Praatika <pprasad@wsgr.com>
`Sent: Wednesday, October 2, 2024 4:16 PM
`To: Bruner, Nicole (DC) <Nicole.Bruner@lw.com>; #C-M ORCA SECURITY - WIZ - LW TEAM
`<orcasecuritywiz.lwteam@lw.com>; JBlumenfeld@morrisnichols.com; RSmith@morrisnichols.com;
`cclark@morrisnichols.com
`Cc: WSGR - Orca Wiz <WSGR-Orca-Wiz@wsgr.com>; Cottrell@RLF.com; Farnan@RLF.com; haynes@rlf.com
`Subject: RE: Orca v. Wiz - Memorialization of 9/30 M&C
`
`Wiz and
`
`
`Nicole,
`
`Your misrepresenta(cid:415)ons and accusa(cid:415)ons about “Wiz’s representa(cid:415)ves . . . knowledge or authority” are not accurate or
`well-taken. The reason meet and confers are repeatedly “stalled” is because Orca con(cid:415)nually serves overbroad and
`irrelevant requests, and then insists on raising its issues first and forces more of its own issues into discussions about
`Wiz’s issues. As to the two Wiz issues that we did not discuss on Monday or yesterday, we have discussed those issues
`at length during mul(cid:415)ple meet and confers and Orca s(cid:415)ll con(cid:415)nues to refuse to provide the discovery we seek. This is
`true even as of Monday, when we invited Orca to propose a compromise during the meet and confer. Had Orca not
`insisted on injec(cid:415)ng irrelevant issues into the discussion, such as Orca’s own irrelevant RFPs, the produc(cid:415)on may have
`been more frui(cid:414)ul. In any event, we correct the most serious misrepresenta(cid:415)ons in your email below.
`
`
`Orca’s Issues
`
`
` Highly Confiden(cid:415)al – A(cid:425)orneys’ Eyes Only Informa(cid:415)on
`
`• RFP Nos. 91, 92, 94, 113: Your email is the first we have heard of Orca’s proposal regarding the page you
`cite. Wiz never “proposed” or “retracted” anything related to this document or page, whether during Monday’s
`meet and confer or otherwise. In any event, we understand your cita(cid:415)on to refer to the document with
`beginning Bates number WIZ_0032970 as that is where the page WIZ_0032973 originates from. Orca’s proposal
`1
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 3 of 66 PageID #: 4410
`
`to “limit[] these RFPs to the features and func(cid:415)onali(cid:415)es” in this document is meaningless because the document
`appears to list all Wiz features and func(cid:415)onali(cid:415)es—not those relevant to the issues in this case—and provides
`different licensing (cid:415)ers to access the various features and func(cid:415)onali(cid:415)es.
`
`• Documents/communica(cid:415)ons with
` Your conten(cid:415)on that Wiz was “not prepared to address the merits of
`the confiden(cid:415)ality agreement” is not true or produc(cid:415)ve. As Wiz noted during the meet and confer, Orca sat on
`the confiden(cid:415)ality agreement that we provided for weeks and did not provide its posi(cid:415)on regarding the
`agreement un(cid:415)l the call—and even then, we had to ask what Orca’s posi(cid:415)on was before we received a
`response. We were nevertheless prepared to discuss the agreement and did so, without any “convoluted set of
`caveats” as you claim. The issue is simple, and as we have repeatedly informed the Orca team: Wiz will produce
`non-privileged documents that are responsive to Orca’s other RFPs consistent with Wiz’s agreement to produce
`documents in response to those RFPs, irrespec(cid:415)ve of whether those documents were disclosed to
` or
`not. But the simple act of sharing a document with
` does not automa(cid:415)cally render that document
` that are not responsive to
`responsive. As such, Wiz will not iden(cid:415)fy or produce documents disclosed to
`Orca’s RFPs because those are protected by the common interest privilege.
`
`• ESI Dispute: As we explained during the meet and confer and reiterated in our previous email, no “filtering” was
`used to decide whether a document was responsive or not. Human reviewers made determina(cid:415)ons, on a
`document-by-document basis, based on relevance to the issues and defenses in this case. At no (cid:415)me did Wiz
`“admit” that it would “simply select documents it deemed least problema(cid:415)c” to share with Orca as samples of
`irrelevant documents—that is the posi(cid:415)on Orca took and is now falsely a(cid:425)ribu(cid:415)ng to Wiz. Regardless, we note
`that your email omits to men(cid:415)on that the par(cid:415)es, in view of Orca’s posi(cid:415)on, agreed during the meet and confer
`that an exchange of a sample set of documents would be unproduc(cid:415)ve.
`
`• Orca’s Interrogatory No. 15: During the meet and confer, Orca asked Wiz to supplement its response to
`Interrogatory No. 15 to include informa(cid:415)on about which Wiz employees accessed the Orca material. As we
`explained during the call and in our previous email, Interrogatory No. 15 does not request this informa(cid:415)on.
`
`
`
`Wiz’s Issues
`
`
`
`
`
`
`
`
`
`
`
`
`•
`
`Interrogatory Nos. 12 and 13 (discussed on the meet and confer): Wiz has explained on mul(cid:415)ple meet and
`confers and emails, including the most recent ones, why Orca’s responses are deficient. For example, our
`previous email makes clear that Orca’s response to Rog 12 “did not include a narra(cid:415)ve response regarding
`whether the documents were discussed with any third party other than one third party (AroundTown) that Orca
`iden(cid:415)fied in a previous supplemental response as having received the subject documents” and that “Orca’s
`response to Rog 13 was also deficient because it did not confirm that no one at Orca had received any Wiz
`documents other than those downloaded by Mr. Himi.” That Orca s(cid:415)ll does not understand what informa(cid:415)on
`these interrogatories seek is simply not credible.
`
`• Orca’s Deficient Core Technical Document Produc(cid:415)on (not discussed on the meet and confer): The response
`we have received from you confirms that any addi(cid:415)onal (cid:415)me spent mee(cid:415)ng and conferring on this issue will be
`unproduc(cid:415)ve. The par(cid:415)es have exchanged many emails and verbally met and conferred regarding this issue
`mul(cid:415)ple (cid:415)mes. There is nothing “baseless” about this dispute because Orca refuses to budge from its
`indefensible posi(cid:415)on. If there are addi(cid:415)onal responsive, non-privileged documents, Orca should produce
`them. If there are not, then Orca should confirm that that is the case. Wiz has been forced to bring this dispute
`to the Court because of Orca’s refusal to meaningfully engage regarding this topic, instead repeatedly and
`baselessly claiming that Wiz has not iden(cid:415)fied what is missing from the documents that Orca possesses, and that
`Wiz has no visibility into.
`
`• RFP Nos. 72 and 73 (not discussed on the meet and confer): To be clear, Wiz did not withdraw RFP 72. And as
`with Wiz’s other issues, the par(cid:415)es have exchanged many emails and verbally met and conferred regarding this
`issue at length, and over the course of several calls. S(cid:415)ll, Orca con(cid:415)nues to make the same arguments it made
`2
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 4 of 66 PageID #: 4411
`
`before the par(cid:415)es’ prolonged discussions about these RFPs. This confirms that Orca is using meet and confers to
`delay providing a real response to Wiz’s issues and to stall Wiz from raises these issues before the Court, even
`while con(cid:415)nuing to threaten to bring—and bring—its own baseless issues to the Court. Orca’s response also
`highlights another double standard, as Orca previously took the posi(cid:415)on that it could properly raise the dispute
`regarding the cloud na(cid:415)ve ESI term in briefing for the September 11, 2024 conference even though it had
`expressly withdrawn that dispute during the par(cid:415)es’ court-ordered meet and confer. See B. Davis Sept. 3, 2024
`email. Orca has no basis for now claiming that Wiz cannot bring a ripe dispute before the Court.
`
`
`
`Regards,
`Praa(cid:415)ka
`
`
`From: Nicole.Bruner@lw.com <Nicole.Bruner@lw.com>
`Sent: Tuesday, October 1, 2024 10:05 PM
`To: Prasad, Praatika <pprasad@wsgr.com>; orcasecuritywiz.lwteam@lw.com; JBlumenfeld@morrisnichols.com;
`RSmith@morrisnichols.com; cclark@morrisnichols.com
`Cc: WSGR - Orca Wiz <WSGR-Orca-Wiz@wsgr.com>; Cottrell@RLF.com; Farnan@RLF.com; haynes@rlf.com
`Subject: RE: Orca v. Wiz - Memorialization of 9/30 M&C
`
`
`EXT - nicole.bruner@lw.com
`
`
`
`Counsel,
`
`
`We are wri(cid:415)ng to assert Orca’s posi(cid:415)on and to address the deficiencies in your previous email.
`
`
`As an ini(cid:415)al ma(cid:425)er, yesterday’s meet and confer was again stalled because Wiz’s representa(cid:415)ves did not have the
`knowledge or authority to address disputed issues, provide updates on discovery progress, and commit to dates
`certain. This is not produc(cid:415)ve, as we have raised repeatedly. Going forward, we ask again that Wiz include members of
`its team that will have previously read the relevant disputes and be ready to discuss and poten(cid:415)ally resolve issues. Wiz’s
`current approach is inefficient and counterproduc(cid:415)ve to the goal of streamlining disputes for the Court.
`
`
`With respect to your summary below, we have corrected certain inaccuracies and provide our responses in red below.
`
`
`Regards,
`
`
`Nicole Elena Bruner
`
`
`LATHAM & WATKINS LLP
`555 Eleventh Street, NW | Suite 1000 | Washington, D.C. 20004-1304
`D: +1.202.654.7209 | M: +1.202.802.8093
`
`
`From: Prasad, Praatika <pprasad@wsgr.com>
`Sent: Tuesday, October 1, 2024 3:26 PM
`To: #C-M ORCA SECURITY - WIZ - LW TEAM <orcasecuritywiz.lwteam@lw.com>; JBlumenfeld@morrisnichols.com;
`RSmith@morrisnichols.com; cclark@morrisnichols.com
`Cc: WSGR - Orca Wiz <WSGR-Orca-Wiz@wsgr.com>; Cottrell, Fred <Cottrell@RLF.com>; Farnan, Kelly E.
`<Farnan@RLF.com>; Haynes, Christine D. <haynes@rlf.com>
`Subject: Orca v. Wiz - Memorialization of 9/30 M&C
`
`
`Wiz and
`
`
` Highly Confiden(cid:415)al – A(cid:425)orneys’ Eyes Only Informa(cid:415)on
`
`3
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 5 of 66 PageID #: 4412
`
`Counsel,
`
`We write to memorialize the par(cid:415)es’ September 30 Court-ordered meet and confer and to provide Wiz’s posi(cid:415)ons on
`certain of the issues discussed. We also include the Wiz issues not reached on the meet and confer. Please advise as to
`whether Orca agrees to Wiz’s requests in this regard.
`
`
`Orca’s Issues
`
`
`
`
`• RFP Nos. 91, 92, 94, 113: Orca asked Wiz if it was planning to produce documents consistent with the narrowed
`scope that Wiz agreed to in its August 20, 2024 supplemental responses. Wiz confirmed that it was planning to
`do so. Orca then asked if Wiz’s produc(cid:415)on would include documents rela(cid:415)ng to the Supply Chain Security and
`Run(cid:415)me Sensor features in view of the Court’s September 10, 2024 order, as the supplemental responses were
`served prior to the issuance of that order. Wiz explained that Wiz disagrees that those func(cid:415)onali(cid:415)es are
`relevant to the claims and defenses in this case, par(cid:415)cularly the Run(cid:415)me Sensor, because it relates to agent-
`based technology and Orca’s claims are limited to agentless technology. Wiz added that for purposes of
`resolving this dispute only (i.e., to reduce the number of issues for resolu(cid:415)on by the Court), it would be willing to
`produce documents regarding the Supply Chain Security and Run(cid:415)me Sensor features for these four RFPs; Wiz
`further explained that this would not be a concession that the Supply Chain Security or Run(cid:415)me Sensor features,
`or any agent-based features or func(cid:415)onali(cid:415)es, are in any way relevant, or all discovery should be supplemented
`to include those features, but that it would consider any future requests by Orca for addi(cid:415)onal discovery
`regarding those features for Orca’s other discovery requests on a case-by-case basis. Orca responded that what
`Wiz considers relevant does not ma(cid:425)er.
`o As Orca explained on the call, Wiz’s posi(cid:415)on that it intends to con(cid:415)nue withholding discovery regarding
`Supply Chain Security and Run(cid:415)me Sensor features because it disagrees with the Court’s Order is
`fundamentally improper. The Court plainly held that those features “fall within the scope of” Orca’s
`claims and infringement conten(cid:415)ons. D.I. 139 (The mo(cid:415)on is GRANTED with respect to the Supply Chain
`Security feature and the Run(cid:415)me Sensor, as well as the source code change logs and git history from
`2020 to the present for those specific features. The record before the court establishes that these
`func(cid:415)onali(cid:415)es fall within the scope of Plain(cid:415)ffs claims and infringement conten(cid:415)ons, as well as
`Defendant's response to Interrogatory No. 1 iden(cid:415)fying components in the Accused Product related to
`the accused func(cid:415)onali(cid:415)es.). Please confirm that Wiz is not withholding and will not withhold other
`discovery responsive to Orca’s RFPs as to Supply Chain Security and Run(cid:415)me Sensor features. As we
`stated on the meet and confer, this is not a dispute that should need to be raised again. If Wiz will not
`agree, Orca reserves the right to seek a(cid:425)orneys’ fees bringing any subsequent mo(cid:415)on.
`o As we stated during the meet and confer, for purposes of resolving the dispute regarding RFP Nos. 91,
`92, 94, 113, Wiz is willing to produce documents that are responsive to these RFPs related to the
`specifically accused “snapshot” func(cid:415)onality, as Wiz understands it, as well as the Supply Chain Security
`feature and the Run(cid:415)me Sensor feature. Please advise whether this resolves the dispute.
` Wiz’s response above simply highlights the same issue discussed in the par(cid:415)es’ meet and
`confer. There is no ques(cid:415)on that Supply Chain Security and Run(cid:415)me Sensor must be
`included. That is not a compromise, that is complying with the Court’s Order. The problem
`remains that Wiz refuses to explain what it means by “specifically accused ‘snapshot’
`func(cid:415)onality as Wiz understands it.” As Wiz ini(cid:415)ally proposed and then retracted, and Orca
`agreed as a compromise, Orca would be amenable to limi(cid:415)ng these RFPs to the features and
`func(cid:415)onali(cid:415)es in WIZ_0032973 that Wiz relies on as defining the features related to the Accused
`Func(cid:415)onali(cid:415)es in its response to Orca’s Interrogatory No. 1. Please let us know if Wiz agrees,
`otherwise we will con(cid:415)nue to seek the Court’s assistance.
`
`• Documents/communica(cid:415)ons with
` As we noted during yesterday’s meet and confer, Wiz provided Orca
`with a copy of the confiden(cid:415)ality agreement between
` weeks ago and did not hear back from
`Orca regarding this issue. Yesterday, Orca stated for the first (cid:415)me that it had reviewed the agreement and did
`not believe the common interest privilege applies. Wiz explained that there is a clear provision in the
`
`4
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 6 of 66 PageID #: 4413
`
`agreement regarding the common interest that supports invoca(cid:415)on of the common interest privilege. Orca
`asked if Wiz would provide it with a list of all documents exchanged with
` Wiz responded that the list
`Orca seeks would be common interest privileged and, as such, would not be provided. As we have previously
`said, Wiz will produce non-privileged documents that are responsive to Orca’s other RFPs, consistent with Wiz’s
`agreement to produce documents in response to those RFPs, irrespec(cid:415)ve of whether those documents were
`disclosed to
` As we made clear, however, Wiz will not provide a list of the specific documents that have
`been disclosed to
` or otherwise iden(cid:415)fy those documents; and Wiz does not agree to produce documents
`that are not independently responsive to the RFPs for which Wiz has agreed to produce documents, simply
`because they were disclosed to
` In other words, a document does not become responsive simply
`because it was exchanged with or disclosed to
` Orca asked if Wiz would be producing its
`correspondence with
` Wiz confirmed that such communica(cid:415)ons are protected by the common interest
`privilege and will therefore not be produced. Orca stated that it would maintain this dispute for the Court.
`o As discussed on the call, Orca disagrees that any provision establishes a common interest privilege, let
`alone to be so sweeping as to encompass
` Wiz was not
`prepared to address the merits of the confiden(cid:415)ality agreement during the call. Your convoluted set of
`caveats about what documents Wiz will or will not disclose also appears designed to prevent Orca from
`ascertaining relevant informa(cid:415)on regarding Wiz’s valua(cid:415)on and the value of the accused product and
`accused func(cid:415)onali(cid:415)es as part of that acquisi(cid:415)on. For example, if non-privileged materials were
`exchanged with
` by email, those emails have no underlying privilege and the common interest
`cannot apply irrespec(cid:415)ve of any agreement. We also disagree with Wiz’s caveats that it is selec(cid:415)vely
`disclosing some documents exchanged with
` but not others, based on some unilateral
`determina(cid:415)on that they are not “independently responsive.” Wiz should produce all documents
`responsive to Orca’s RFPs that were exchanged with
` Orca intends to request the Court’s
`assistance with respect to Wiz’s improper withholding of documents.
`
`• ESI Dispute: Orca asked for an explana(cid:415)on of how Wiz’s responsiveness review was conducted. Wiz explained
`that a document-by-document review was conducted by human reviewers and that documents were not
`automa(cid:415)cally withheld on the basis of hi(cid:427)ng on certain search terms. Orca then asked how responsiveness
`determina(cid:415)ons were made. Wiz explained that documents that were clearly irrelevant to the issues of the case
`were iden(cid:415)fied as nonresponsive. Wiz offered to share a sample of such documents with Orca to resolve this
`dispute, recognizing that doing so may not move the ball on this issue because Orca would likely claim the
`sample shared is not representa(cid:415)ve of all withheld ESI hits. Orca confirmed that it would indeed take this
`posi(cid:415)on. Orca then asked when Wiz would produce the addi(cid:415)onal responsive documents it had iden(cid:415)fied
`would be produced in an upcoming produc(cid:415)on. Wiz said it would follow up in wri(cid:415)ng.
`o Wiz expects to produce an ini(cid:415)al batch of responsive documents by Thursday, October 3, if not
`tomorrow, and the remainder by Friday, October 4. As we asked yesterday, please tell us the
`approximate volume of documents that are going to be produced.
`o Wiz’s statements regarding Wiz’s proposal of sharing a sample of withheld documents mischaracterizes
`the par(cid:415)es’ exchange. Once Wiz disclosed that its produc(cid:415)on involved a document-by-document review
`to filter for its interpreta(cid:415)on of relevance – despite the fact that each document already hit on agreed
`upon search terms – Orca requested addi(cid:415)onal details on Wiz’s filtering criteria. Wiz refused to provide
`any details. Wiz offered to share a sample of documents with Orca, admi(cid:427)ng this wouldn’t “move the
`ball” because Wiz could simply select documents it deemed least problema(cid:415)c. The only specific
`example that Wiz provided on the call of an allegedly “irrelevant” document was informa(cid:415)on regarding
`par(cid:415)cular personnel that had joined teams to work on par(cid:415)cular projects. Orca explained that Wiz
`seemed to be improperly withholding documents that would allow Orca to inves(cid:415)gate the person(s)
`most knowledgeable about par(cid:415)cular features and/or where addi(cid:415)onal discovery might be found. Wiz
`had no response. Orca nevertheless expressed willingness to review Wiz’s other examples of
`“irrelevant” documents, and asked that Wiz share its examples. We understand Wiz is now reneging on
`that proposal.
`
`
`
`
`
`5
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 7 of 66 PageID #: 4414
`• Orca’s Interrogatory No. 15: The par(cid:415)es discussed Orca’s Interrogatory No. 15 in conjunc(cid:415)on with Wiz’s
`Interrogatory Nos. 12 and 13 below. Wiz has not provided responsive informa(cid:415)on in its supplements to
`Interrogatory No. 15 including, for example, (1) iden(cid:415)fying employees who were exposed to the materials; (2)
`iden(cid:415)fying communica(cid:415)ons with third par(cid:415)es related to such documents; (3) describing Wiz’s understanding of
`the confiden(cid:415)ality and contractual protec(cid:415)ons for that informa(cid:415)on; or (4) confirming the scope of Orca
`documents in Wiz’s possession now or in the past. Orca has provided such informa(cid:415)on in its response to Wiz’s
`Interrogatory No. 12. Orca again requests that Wiz supplement its responses to Interrogatory No. 15 with at
`least the above-noted informa(cid:415)on. Furthermore, Wiz has not confirmed that no one at Wiz has received any
`documents other than what are expressly listed in its supplemental responses, reserving the right to add yet
`more informa(cid:415)on.
`
`•
`
`Interrogatory Nos. 12 and 13 (discussed on the meet and confer): Orca asked Wiz if it was going to change its
`posi(cid:415)on on these interrogatories given that Orca supplemented its responses to both an hour prior to the meet
`and confer. Wiz stated that it did not receive a supplemental response for Rog 13; Orca responded that its
`supplemental response to Rog 12 is incorporated in its response to Rog 13. Wiz explained that more (cid:415)me would
`be needed to review the supplemental response and documents cited for Rog 12, given that Orca supplemented
`its response so close in (cid:415)me to the meet and confer, but added that the supplemental response did not include
`a narra(cid:415)ve response regarding whether the documents were discussed with any third party other than one third
`party (AroundTown) that Orca iden(cid:415)fied in a previous supplemental response as having received the subject
`documents. Wiz added that Orca’s response to Rog 13 was also deficient because it did not confirm that no one
`at Orca had received any Wiz documents other than those downloaded by Mr. Himi. Orca was unable to provide
`a response to, or further informa(cid:415)on on, either of these points. Instead, it asked whether Wiz was going to
`supplement its response to Orca’s Rog 15 to include informa(cid:415)on about which Wiz employees had access to Orca
`material. Orca’s Rog 15 does not, however, include a request for iden(cid:415)fica(cid:415)on of all Wiz employees who had
`ever accessed the Orca material. As such, Wiz does not plan to supplement its response at this (cid:415)me.
`o As we asked on the meet and confer, and to which Wiz would not provide a response, what informa(cid:415)on
`is Wiz asking Orca to supplement that was not addressed in its current or prior
`supplementa(cid:415)ons? Orca’s supplement yesterday addressed all issues that Wiz previously raised, and it
`would be improper to raise new disputes that the par(cid:415)es have never before discussed. Your statements
`regarding Orca’s Interrogatory No. 15 are incorrect as discussed above. Orca will not agree to con(cid:415)nue
`its unilateral produc(cid:415)on of informa(cid:415)on when Wiz has forgone its own discovery obliga(cid:415)ons.
`
`
`
`Wiz’s Issues
`
`
`
`
`• Orca’s Deficient Core Technical Document Produc(cid:415)on (not discussed on the meet and confer): Wiz’s posi(cid:415)on
`has not changed with respect to this issue. As Wiz has explained mul(cid:415)ple (cid:415)mes, Orca has not met its obliga(cid:415)on
`to produce core technical documents describing how each of the accused func(cid:415)onali(cid:415)es operate. Contrary to
`Orca’s posi(cid:415)on, produc(cid:415)on of source code and git history is not sufficient in this situa(cid:415)on because they do not
`show how all of the accused func(cid:415)onali(cid:415)es work. In addi(cid:415)on, the documents Orca iden(cid:415)fies as purportedly
`sa(cid:415)sfying its obliga(cid:415)on to produce technical documents fail to describe how the accused features and
`func(cid:415)onali(cid:415)es work—that is a different inquiry than simply iden(cid:415)fying or poin(cid:415)ng to those features without any
`further explana(cid:415)on of how they operate. Please confirm if Orca will produce core technical documents showing
`how each of the accused features and func(cid:415)onali(cid:415)es operate, as the Delaware Default Rules require. Wiz will
`otherwise include this issue in its opening discovery le(cid:425)er.
`o Wiz’s posi(cid:415)on is misplaced. First, Orca has produced (1) its en(cid:415)re source code, (2) its Git history and
`repository informa(cid:415)on, which provides significant context for Wiz to understand the underlying
`technology, and (3) a wide array of technical documents. Even now, Wiz refuses to actually explain what
`it is seeking, and apparently refuses to discuss the issue on a meet and confer. Indeed, Orca expressly
`asked for Wiz to provide addi(cid:415)onal (cid:415)mes to verbally meet and confer so that we could try to address
`this dispute without Court interven(cid:415)on. We are s(cid:415)ll available. Orca has repeatedly and exhaus(cid:415)vely
`asked Wiz to provide any specificity for what else it believes is missing, and Wiz has refused to
`engage. Wiz appears dead set on bringing this baseless dispute to the Court, and we will address the
`
`6
`
`

`

`
`
`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 8 of 66 PageID #: 4415
`
`par(cid:415)es’ history of correspondence and Wiz’s refusal to substan(cid:415)vely meet and confer on this issue in
`response to Wiz’s le(cid:425)er.
`
`• RFP Nos. 72 and 73 (not discussed on the meet and confer): Wiz’s posi(cid:415)on has not changed with respect to
`these RFPs. These RFPs mirror Orca’s RFP Nos. 38 and 41; Wiz therefore proposed earlier that each party agree
`to produce documents in response to the other’s requests. Orca has consistently refused to produce any
`documents in response to RFP No. 72 even though such documents are plainly relevant to show Orca’s
`engagement of CGI Group to conduct compe(cid:415)(cid:415)ve business intelligence ac(cid:415)vi(cid:415)es related to its compe(cid:415)tors,
`including Wiz. Orca claims that any documents responsive to RFP No. 73 are somehow privileged even though
`they involve a third party, but has s(cid:415)ll not ar(cid:415)culated a basis for how communica(cid:415)ons with such third par(cid:415)es
`can be privileged. Please advise if Orca will change its posi(cid:415)on and produce documents responsive to both
`these Requests. Wiz will otherwise raise this issue with the Court in this week’s briefing.
`o For Request 73, Orca confirmed that there are no non-privileged responsive documents to the RFPs
`rela(cid:415)ng to CGI Group, excluding email or other forms of electronic correspondence (which the par(cid:415)es
`agreed are not responsive to Wiz’s RFPs, D.I. 71 at 3), and that to the extent there are responsive ESI
`documents rela(cid:415)ng to CGI Group they will be produced or logged in accordance with the scheduling
`order. See K. McKenna Aug. 28, 2024 Email. Wiz also expressly withdrew RFP 72, so that issue is not
`properly before the Court. Wiz appears to be set on bringing a baseless dispute to the Court without
`mee(cid:415)ng and conferring, as Orca said it would be available to discuss.
`
`
`
`Please confirm which of Orca’s issues you s(cid:415)ll intend to raise with the Court in this week’s briefing and advise on Orca’s
`posi(cid:415)ons regarding Wiz’s issues so we can evaluate next steps.
`
`
`Regards,
`Praa(cid:415)ka
`
`
`
`
`Praatika Prasad (she/her) | Associate | Wilson Sonsini Goodrich & Rosati
`1301 Avenue of the Americas, 40th Floor | New York, NY 10019 | 212.453.2803 | pprasad@wsgr.com
`
`
`
`
`
`
`
`
`
`This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the
`intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly
`prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the
`original and any copies of this email and any attachments thereto.
`_________________________________
`
`
`This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the
`intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission
`is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies including any
`attachments.
`
`
`Latham & Watkins LLP or any of its affiliates may monitor electronic communications sent or received by our networks
`in order to protect our business and verify compliance with our policies and relevant legal requirements. Any personal
`information contained or referred to within this electronic communication will be processed in accordance with the
`firm's privacy notices and Global Privacy Standards available at www.lw.com.
`
`
`
`7
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 9 of 66 PageID #: 4416
`
`This email and any attachments thereto may contain private, confidential, and privileged material for the sole use of the
`intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is strictly
`prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the
`original and any copies of this email and any attachments thereto.
`
`8
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 10 of 66 PageID #:
`4417
`
`EXHIBIT 2
`
`

`

`Case 1:23-cv-00758-JLH-SRF Document 171-1 Filed 10/10/24 Page 11 of 66 PageID #:
`4418
`
`McKenna, Krissy (BN)
`From:
`Davis, Blake (Bay Area)
`Sent:
`Thursday, September 26, 2024 9:20 PM
`To:
`Prasad, Praatika; haynes@rlf.com; WSGR - Orca Wiz; Cottrell@RLF.com
`Cc:
`#C-M ORCA SECURITY - WIZ - LW TEAM; cclark@morrisnichols.com;
`JBlumenfeld@morrisnichols.com; RSmith@morrisnichols.com
`RE: Orca v Wiz - meet and confer re Dkt. 147
`
`Subject:
`
`Praatika,
`
`That works for us. Please circulate a dial in.
`
`Thanks,
`Blake
`
`Sent with BlackBerry Work
`(www.blackberry.com)
`
`
`From: Prasad, Praatika <pprasad@wsgr.com>
`Date: Thursday, Sep 26, 2024 at 8:13 AM
`To: Davis, Blake (Bay Area) <Blake.Davis@lw.com>, haynes@rlf.com <haynes@rlf.com>, WSGR - Orca Wiz <WSGR-Orca-
`Wiz@wsgr.com>, Cottrell@RLF.com <Cottrell@RLF.com>
`Cc: #C-M ORCA SECURITY - WIZ - LW TEAM <orcasecuritywiz.lwteam@lw.com>, cclark@morrisnichols.com
`<cclark@morrisnichols.com>, JBlumenfeld@morrisnichols.com <JBlumenfeld@morrisnichols.com>,
`RSmith@morrisnichols.com <RSmith@morrisnichols.com>
`Subject: RE: Orca v Wiz - meet and confer re Dkt. 147
`
`Blake,
`
`We are not available during those times. We are available on Monday between 2:30-3:30 ET. Please let us know if that
`works for you.
`
`Regards,
`Praat