throbber
Case 3:17-cv-05659-WHA Document 506 Filed 06/03/19 Page 1 of 4
`
`
`Philip C. Swain (SBN 150322)
`Philip C. Swain (SBN 150322)
`pswain@foleyhoag.com
`pswain@foleyhoag.com
`FOLEY HOAG LLP
`FOLEY HOAG LLP
`155 Seaport Boulevard
`155 Seaport Boulevard
`Boston MA 02210
`Boston MA 02210
`Telephone: 617-732-1000
`Telephone: 617-732-1000
`Facsimile: 617-832-7000
`Facsimile: 617-832-7000
`
`Attorneys for Non-Party Joe Security, LLC
`Attorneys for Non-Party Joe Security, LLC
`
`UNITED STATES DISTRICT COURT
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`NORTHERN DISTRICT OF CALIFORNIA
`
`FINJAN, INC.
`
`FINJAN, INC.
`
`Plaintiff,
`Plaintiff,
`
`vs.
`vs.
`
`JUNIPER NETWORKS, INC.
`JUNIPER NETWORKS, INC.
`
`Defendant.
`Defendant.
`
`
`
`
`
`
`Case No. C 17-05659 WHA
`Case No. C 17-05659 WHA
`
`NON-PARTY JOE SECURITY, LLC'S
`NON-PARTY JOE SECURITY, LLC’S
`STATEMENT IN RESPONSE TO
`STATEMENT IN RESPONSE TO
`COURT ORDER (DKT 497)
`COURT ORDER (DKT 497)
`
`
`
`
`
`
`Non-party Joe Security, LLC ("Joe Security") hereby responds to the Court's Order (Dkt.
`Non-party Joe Security, LLC (“Joe Security”) hereby responds to the Court’s Order (Dkt.
`
`497) that it make a submission explaining the confidential nature of the Joe Security documents
`497) that it make a submission explaining the confidential nature of the Joe Security documents
`
`the parties have attempted to file under seal in this action.1 Joe Security respectfully requests that
`the parties have attempted to file under seal in this action.1 Joe Security respectfully requests that
`
`this Court exclude its confidential documents from filing in this action. In the alternative, Joe
`this Court exclude its confidential documents from filing in this action. In the alternative, Joe
`
`Security requests that the Court require that the documents be filed under seal, or that Joe
`Security requests that the Court require that the documents be filed under seal, or that Joe
`
`Security be allowed to redact the most sensitive information from those documents.
`Security be allowed to redact the most sensitive information from those documents.
`
`DISCUSSION
`DISCUSSION
`
`The documents at issue are Joe Security's Installation Guide, Interface Guide, and User
`The documents at issue are Joe Security’s Installation Guide, Interface Guide, and User
`
`Guide. Joe Security understands that these were produced by Juniper during discovery, pursuant
`Guide. Joe Security understands that these were produced by Juniper during discovery, pursuant
`
`
`
`i Joe Security is not a party to this action and has no presence in California. Given the circumstances whereby Joe
`1 Joe Security is not a party to this action and has no presence in California. Given the circumstances whereby Joe
`Security was required to make this submission or face having its Guides made public, Joe Security had no choice but
`Security was required to make this submission or face having its Guides made public, Joe Security had no choice but
`to do so. Joe Security appears on this limited basis and expressly contests personal jurisdiction in this Court.
`to do so. Joe Security appears on this limited basis and expressly contests personal jurisdiction in this Court.
`
`_____________________________________________________________________________
`NON-PARTY JOE SECURITY'S STATEMENT — CASE NO. C17-05659 WHA
`NON-PARTY JOE SECURITY’S STATEMENT – CASE NO. C17-05659 WHA
`
`
`
`
`1
`1
`
`2
`2
`
`3
`3
`
`4
`4
`
`5
`5
`
`6
`6
`
`7
`7
`
`8
`8
`
`9
`9
`
`10
`10
`
`11
`11
`
`12
`12
`
`13
`13
`
`14
`14
`
`15
`15
`
`16
`16
`
`17
`17
`
`18
`18
`
`19
`19
`
`20
`20
`
`21
`21
`
`22
`22
`
`23
`23
`
`24
`24
`
`25
`25
`
`26
`26
`
`27
`27
`
`28
`28
`
`

`

`Case 3:17-cv-05659-WHA Document 506 Filed 06/03/19 Page 2 of 4
`
`
`to the Protective Order entered by this Court. (Dkt. 148 and 149). 2 The documents should this
`to the Protective Order entered by this Court. (Dkt. 148 and 149). 2 The documents should this
`
`be subject to the protections provided in the Protective Order for confidential documents.
`be subject to the protections provided in the Protective Order for confidential documents.
`
`These documents contain confidential trade secret information relating to computer
`These documents contain confidential trade secret information relating to computer
`
`malware prevention programs that, if made public, could compromise Joe Security's malware
`malware prevention programs that, if made public, could compromise Joe Security’s malware
`
`prevention programs currently being used by Joe Security's customers, including governmental
`prevention programs currently being used by Joe Security’s customers, including governmental
`
`security agencies and Fortune 500 companies, which in turn would compromise their computer
`security agencies and Fortune 500 companies, which in turn would compromise their computer
`
`systems and render them more susceptible to computer malware.
`systems and render them more susceptible to computer malware.
`
`Joe Security is a Swiss entity located in Reinach, Switzerland. See Declaration of Stefan
`Joe Security is a Swiss entity located in Reinach, Switzerland. See Declaration of Stefan
`
`Bahlmann ("Bahlmann Decl."), at ¶3 (Exhibit A). Joe Security is in the computer security
`Bühlmann (“Bühlmann Decl.”), at ¶3 (Exhibit A). Joe Security is in the computer security
`
`business. Id. at ¶¶4, 6. Joe Security has developed a malware analysis and detection system
`business. Id. at ¶¶4, 6. Joe Security has developed a malware analysis and detection system
`
`named Joe Sandbox that enables computer systems to detect and protect against computer
`named Joe Sandbox that enables computer systems to detect and protect against computer
`
`viruses and malware threats. Id. A review of its product by SC Magazine, the leading magazine
`viruses and malware threats. Id. A review of its product by SC Magazine, the leading magazine
`
`for IT security professionals (also available at https://www.scmagazine.com/home/reviews/first-
`for IT security professionals (also available at https://www.scmagazine.com/home/reviews/first-
`
`looks/first-look-joe-security-joe-sandbox-cloud/), explains Joe Security's product and concludes
`looks/first-look-joe-security-joe-sandbox-cloud/), explains Joe Security’s product and concludes
`
`that it "is a must-have tool for IT security shops in organizations of just about any size."
`that it “is a must-have tool for IT security shops in organizations of just about any size.”
`
`(Exhibit B.)
`(Exhibit B.)
`
`Joe Security carefully screens its customers and only licenses its product to reputable
`Joe Security carefully screens its customers and only licenses its product to reputable
`
`governmental security agencies and select corporations. Bahlmann Decl. at ¶7. The total
`governmental security agencies and select corporations. Bühlmann Decl. at ¶7. The total
`
`number of Joe Security customers is limited and its customer list is confidential. Id. All of Joe
`number of Joe Security customers is limited and its customer list is confidential. Id. All of Joe
`
`Security's business and governmental partners agree to strict confidentiality restrictions as a
`Security’s business and governmental partners agree to strict confidentiality restrictions as a
`
`condition of using its solution. Id. at ¶8. Joe Security's customers install its solution into their
`condition of using its solution. Id. at ¶8. Joe Security’s customers install its solution into their
`
`
`
`2 While it is not clear to Joe Security at this time whether the documents as produced were all designated as
`2 While it is not clear to Joe Security at this time whether the documents as produced were all designated as
`"Confidential" or "Highly Confidential" when produced by Juniper, Joe Security believes they should have been so
`“Confidential” or “Highly Confidential” when produced by Juniper, Joe Security believes they should have been so
`designated when they were produced, as explained herein.
`designated when they were produced, as explained herein.
`
`_____________________________________________________________________________
`NON-PARTY JOE SECURITY'S STATEMENT — CASE NO. C17-05659 WHA
`NON-PARTY JOE SECURITY’S STATEMENT – CASE NO. C17-05659 WHA
`
`
`
`
`1
`1
`
`2
`2
`
`3
`3
`
`4
`4
`
`5
`5
`
`6
`6
`
`7
`7
`
`8
`8
`
`9
`9
`
`10
`10
`
`11
`11
`
`12
`12
`
`13
`13
`
`14
`14
`
`15
`15
`
`16
`16
`
`17
`17
`
`18
`18
`
`19
`19
`
`20
`20
`
`21
`21
`
`22
`22
`
`23
`23
`
`24
`24
`
`25
`25
`
`26
`26
`
`27
`27
`
`28
`28
`
`

`

`Case 3:17-cv-05659-WHA Document 506 Filed 06/03/19 Page 3 of 4
`
`
`computer infrastructure to help protect against malware threats. Id. at ¶9. Customers who
`computer infrastructure to help protect against malware threats. Id. at ¶9. Customers who
`
`purchase Joe Security's malware program are provided Joe Security's Installation Guide,
`purchase Joe Security’s malware program are provided Joe Security’s Installation Guide,
`
`Interface Guide, and User Guide (collectively, Joe Security's "Guides"). Id. at ¶10. Joe
`Interface Guide, and User Guide (collectively, Joe Security’s “Guides”). Id. at ¶10. Joe
`
`Security's Guides contain highly confidential trade secrets including the password to its system,
`Security’s Guides contain highly confidential trade secrets including the password to its system,
`
`the otherwise secret IP and MAC addresses on which the system runs, file names, network ports
`the otherwise secret IP and MAC addresses on which the system runs, file names, network ports
`
`and network protocols. Id. at ¶11. The Guides also contain a roadmap to Joe Security's product.
`and network protocols. Id. at ¶11. The Guides also contain a roadmap to Joe Security’s product.
`
`Id. at ¶13.
`Id. at ¶13.
`
`The efficacy of Joe Security's security product could be immediately, directly and
`The efficacy of Joe Security’s security product could be immediately, directly and
`
`completely compromised if the information contained in the Guides is made public. Balmann
`completely compromised if the information contained in the Guides is made public. Bühlmann
`
`Decl. at ¶12. Hackers would be able to use the information in the Guides to modify their
`Decl. at ¶12. Hackers would be able to use the information in the Guides to modify their
`
`malware to circumvent Joe Security's malware detection and prevention system. Id. at ¶¶12, 13
`malware to circumvent Joe Security’s malware detection and prevention system. Id. at ¶¶12, 13
`
`CONCLUSION
`CONCLUSION
`
`Joe Security submits that the foregoing presents "compelling reasons" sufficient to justify
`Joe Security submits that the foregoing presents “compelling reasons” sufficient to justify
`
`keeping its Guides from public filing. In the event the Court declines to allow the Guides to be
`keeping its Guides from public filing. In the event the Court declines to allow the Guides to be
`
`filed under seal, Joe Security asks in the alternative that it be given the opportunity to redact the
`filed under seal, Joe Security asks in the alternative that it be given the opportunity to redact the
`
`most sensitive of information in the Guides (i.e., Joe Security's system access password, IP and
`most sensitive of information in the Guides (i.e., Joe Security’s system access password, IP and
`
`MAC addresses on which the system runs, file names, network ports and network protocols).
`MAC addresses on which the system runs, file names, network ports and network protocols).
`
`See Balmann Decl. at ¶14.
`See Bühlmann Decl. at ¶14.
`
`Dated: June 3, 2019
`Respectfully submitted,
`Dated: June 3, 2019 Respectfully submitted,
`
`JOE SECURITY, LLC
`JOE SECURITY, LLC
`
`by its attorneys,
`by its attorneys,
`
`
`
`
`
`s/Philip C. Swain
`_s/Philip C. Swain____
`Phillip C. Swain
`Phillip C. Swain
`FOLEY HOAG LLP
`FOLEY HOAG LLP
`155 Seaport Boulevard
`155 Seaport Boulevard
`Boston, MA 02210
`Boston, MA 02210
`Tel: (617) 832-1000
`Tel: (617) 832-1000
`Fax: (617) 832-7000
`Fax: (617) 832-7000
`pswain@foleyhoag.com
`pswain@foleyhoag.com
`_____________________________________________________________________________
`NON-PARTY JOE SECURITY'S STATEMENT - CASE NO. C17-05659 WHA
`NON-PARTY JOE SECURITY’S STATEMENT – CASE NO. C17-05659 WHA
`
`
`
`
`1
`1
`
`2
`2
`
`3
`3
`
`4
`4
`
`5
`5
`
`6
`6
`
`7
`7
`
`8
`8
`
`9
`9
`
`10
`10
`
`11
`11
`
`12
`12
`
`13
`13
`
`14
`14
`
`15
`15
`
`16
`16
`
`17
`17
`
`18
`18
`
`19
`19
`
`20
`20
`
`21
`21
`
`22
`22
`
`23
`23
`
`24
`24
`
`25
`25
`
`26
`26
`
`27
`27
`
`28
`28
`
`

`

`Case 3:17-cv-05659-WHA Document 506 Filed 06/03/19 Page 4 of 4
`
`
`
`
`
`CERTIFICATE OF SERVICE
`CERTIFICATE OF SERVICE
`I certify that this document filed through the ECF system will be sent electronically to
`I certify that this document filed through the ECF system will be sent electronically to
`the registered participants as identified on the Notice of Electronic Filing (NEF) and paper
`the registered participants as identified on the Notice of Electronic Filing (NEF) and paper
`copies will be sent to those indicated as non-registered participants, if any, on this 3rd day of
`copies will be sent to those indicated as non-registered participants, if any, on this 3rd day of
`June, 2019.
`June, 2019.
`
`/s/ Philip C. Swain
`/s/ Philip C. Swain
`
`
`
`
`
`
`_____________________________________________________________________________
`NON-PARTY JOE SECURITY'S STATEMENT - CASE NO. C17-05659 WHA
`NON-PARTY JOE SECURITY’S STATEMENT – CASE NO. C17-05659 WHA
`
`
`
`
`1
`1
`
`2
`2
`
`3
`3
`
`4
`4
`
`5
`5
`
`6
`6
`
`7
`7
`
`8
`8
`
`9
`9
`
`10
`10
`
`11
`11
`
`12
`12
`
`13
`13
`
`14
`14
`
`15
`15
`
`16
`16
`
`17
`17
`
`18
`18
`
`19
`19
`
`20
`20
`
`21
`21
`
`22
`22
`
`23
`23
`
`24
`24
`
`25
`25
`
`26
`26
`
`27
`27
`
`28
`28
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket