throbber
Case 3:17-cv-05659-WHA Document 524-1 Filed 06/07/19 Page 1 of 2
`
`
`
`Philip C. Swain (SBN 150322)
`pswain@foleyhoag.com
`FOLEY HOAG LLP
`155 Seaport Boulevard
`Boston MA 02210
`Telephone: 617-732-1000
`Facsimile: 617-832-7000
`
`Attorneys for Non-Party Joe Security, LLC
`
`UNITED STATES DISTRICT COURT
`
`NORTHERN DISTRICT OF CALIFORNIA
`
`
`FINJAN, INC.
`
`Plaintiff,
`
`vs.
`
`JUNIPER NETWORKS, INC.
`
`Defendant.
`
`
`
`
`Case No. C 17-05659 WHA
`
`SECOND DECLARATION OF STEFAN
`BUEHLMANN IN SUPPORT OF
`MOTION TO FILE UNDER SEAL (DKT
`513)
`
`
`
`
`
`
`
`
`
`I, Stefan Buehlmann, hereby state the following under oath:
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`I live in Witterswil, Switzerland.
`
`I am the General Manager of Joe Security LLC ("Joe Security").
`
`Joe Security is a Swiss entity located in Reinach, Switzerland.
`
`I have been involved in computer security and malware detection for 15 years.
`
`Joe Security is in the computer security business. Specifically, Joe Security has
`
`developed a malware analysis and detection system, called the Joe Sandbox system that enables users
`
`to detect and analyze computer viruses and malware threats.
`
`6. We carefully screen our customers and only license our product to reputable
`
`governmental security agencies and select corporations. The total number of Joe Security
`
`customers is limited. Our customer list is confidential.
`
`7.
`
`All of our business and governmental partners agree to strict confidentiality
`
`restrictions as a condition of using our solution.
`
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`28
`
`

`

`Case 3:17-cv-05659-WHA Document 524-1 Filed 06/07/19 Page 2 of 2
`
`
`
`8.
`
`Our customers install our solution into their computer infrastructure to help protect
`
`against malware threats.
`
`9.
`
`Juniper Networks, the defendant in this case, is one of our customers.
`
`10.
`
`In his deposition dated February 7, 2019, Khurram Islah, a software developer for
`
`Juniper Networks described the technical details of Joes Security’s Joe Sandbox system. The
`
`testimony and descriptions of the Joe Sandbox system in the Islah deposition are trade secrets and
`
`highly confidential information of Joe Security.
`
`11. As a company that focuses on computer malware, we know that the efficacy of our
`
`product could be immediately, directly and completely compromised if the information in the Islah
`
`deposition is made public. Hackers would be able to use this information to modify their malware to
`
`circumvent our malware detection and prevention system.
`
`12. We would prefer that no part of the Islah deposition be made public. Public disclosure
`
`of the descriptions and technical details in the deposition would compromise the efficacy of our
`
`malware prevention product.
`
`13.
`
`In the event that the Court declines to allow the deposition sealed in its entirety, we
`
`would request the opportunity to redact the confidential references (although I estimate the redactions
`
`would be substantially more than 50% of the deposition transcript).
`
`I declare under the pains and penalties of perjury that the foregoing is true and correct this 7th day of
`June, 2019.
`
`Stefan Buehlmann
`
`
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`8
`
`9
`
`10
`
`11
`
`12
`
`13
`
`14
`
`15
`
`16
`
`17
`
`18
`
`19
`
`20
`
`21
`
`22
`
`23
`
`24
`
`25
`
`26
`
`27
`
`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