`
`l.
`
`
`
`DECLARATION OF FRANK JAS
`
`I, Frank Jas, declare as follows:
`I have personal knowledge of the facts set forth in this declaration, and I could and would testify
`competently thereto if called upon to do so.
`I am a Distinguished Engineer with Juniper Networks, Inc. ("Juniper"). Prior to working at
`2.
`Juniper, I was Chief Technology Officer with Cyphort Inc. ("Cyphort").
`I have been responsible for the
`development of various different components of the ATP Appliance, and J understand how the device operates.
`3.
`The collectors push files to the SmartCore using an "HTTP Rest APL" To do this, the collectors
`use a "submit_sample" function that posts a file to an HTTP endpoint in the SmartCore called the "central
`manager."
`
`
`
`shows that the method to do this is a standard
`HTTP post command. During this process, the SmartCore is able to receive the transmitted file data, but does
`not gather additional data on its own. Id. Thus, the SmartCore simply receives files, it does not retrieve them.
`Finjan Ex. 15 (JNPR-FNJN _ 29018 _ 00975646) discusses a "cluster database" for communicating
`4.
`with the SmartCore and Ex. 16 (JNPR-FNJN_029018_00962784) discusses the integration of SRX and ATP
`Appliance. These are both development documents that post-date the expiration of the '780 Patent, which I
`understand was November 6, 2017. The cluster database feature was never actuaJly implemented. And, the SRX
`was not integrated with the ATP Appliance until March 2018.
`When processing archive files ( e.g., .zip or .jar), the ATP Appliance performs separate hashing
`functions on the parent archive file and the "children" or files contained in the archive file. This is shown in the
` The ATP Appliance treats archive files like .jar files the
`same as .zip files, as shown in the source code file at
`
`
`Executed this � day of April, 20 I 9, at Si.Jn� Q,_, Cit .
`I decJa,e under penally of perjury under the laws �t ;� is true and correct.
`
`5.
`
`REDACTED VERSION OF DOCUMENT SOUGHT TO BE SEALED
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
