throbber
Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 1 of 12
`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 1 of 12
`
`
`
`EXHIBIT 13
`
`EXHIBIT 13
`
`
`
`
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 2 of 12
`
`LL™
`
`SonicWall™ Email Security 9.0.1
`Release Notes
`
`April 2017
`
`These release notes provide information about the SonicWall™ Email Security 9.0.1 release.
`
`Topics:
`
`• About Email Security
`
`• Features and Enhancements
`
`• Resolved Issues
`
`• Known Issues
`
`• Product Licensing
`
`• Upgrade and Installation Instructions
`
`• SonicWall Support
`
`About Email Security
`
`Email Security provides a flexible solution to protect email from spam, phishing, and viruses that extends Email
`Security to a new family of appliances. Email Security 9.0.1 is a patch that updates features and resolves known
`issues found in previous releases. Refer to Features and Enhancements for more information.
`
`G) I IMPORTANT: Because Email Security 9.0.1 is a 64-bit implementation and versions prior to 9.0 are 32-bit,
`
`SonicWall recommends a fresh deployment for Email Security 9.0 or later.
`
`Email Security 9.0.1 is supported as firmware on SonicWall Email Security appliances, as a software installation
`on Windows Server systems, and as a Virtual Appliance on VMware ESXi platforms. See the following sections
`for detailed requirements:
`
`• Supported Platforms
`
`• Software Requirements
`
`• Virtual Appliance Requirements
`
`• System Requirements for the Junk Button
`
`• System Requirements for the Send-Secure Button
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`1
`
`SonicWall-Finjan_00009996
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 3 of 12
`
`Supported Platforms
`
`Email Security 9.0.1 firmware is supported on the following SonicWall appliances:
`
`32-Bit Versions
`
`64-Bit Versions
`
`• Email Security 3300
`
`• Email Security Appliance 5000
`
`• Email Security 4300
`
`• Email Security Appliance 7000
`
`• Email Security 8300
`
`• Email Security Appliance 9000
`
`Software Requirements
`
`When installed as software, SonicWall Email Security is supported on systems that meet the following
`requirements:
`
`Requirements
`
`Definitions
`
`Processor
`
`Memory
`
`Intel Pentium: P4 or compatible CPU
`
`8 GB of RAM
`
`Hard Disk Space
`
`Additional 160 GB minimum
`
`Operating System
`
`Microsoft Hyper-V Server 2012 R2 (64-bit)
`
`Recommend installation on a separate drive. Your storage needs are based
`on your mail volume, quarantine size, archived data, and audit settings.
`
`Microsoft Hyper-V Server 2012 (64-bit)
`Microsoft Hyper-V Server 2008 (64-bit)
`
`Windows Server 2012 R2 (64 bit)
`
`Windows Server 2012 (64 bit)
`
`Windows Server 2008 R2 (64 bit) with Service Pack 1
`
`Windows Small Business Server (SBS) 2008 (64-bit) with Service Pack 2
`
`Virtual Appliance Requirements
`
`When installed as a Virtual Appliance, SonicWall Email Security is supported on systems that meet the following
`requirements:
`
`Requirements
`
`Definition
`
`Processor
`
`Memory
`
`Hard Disk Space
`
`VMware Platforms
`
`1 CPU, can be expanded to 8 CPU
`
`8 GB of RAM, can be expanded to 64 GB
`
`160 GB thick provisioned hard disk space
`
`ESXi 5.5 and newer
`
`CD NOTE: The default allocation for the OVA image of the Email Security Virtual Appliance is 160 GB on the
`virtual disk. Beginning with version 8.3, Email Security supports disk resizing, but once the disk space has
`been expanded, it cannot be reduced back to a smaller size.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`2
`
`SonicWall-Finjan_00009997
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 4 of 12
`
`System Requirements for the Junk Button
`
`The Junk Button is supported on the following platforms:
`
`Solution
`
`Platforms
`
`OS
`
`Junk Button, 32 bit Outlook 2010, 32 bit
`
`Windows 7
`
`Outlook 2013, 32 bit
`
`Windows 8.1
`
`Outlook 2016, 32 biS
`
`Windows 10
`
`Junk Button, 64 bit Outlook 2010, 64 bit
`
`Windows 7
`
`Outlook 2013, 64 bit
`
`Windows 8.1
`
`Outlook 2016, 64 bit
`
`Windows 10
`
`System Requirements for the Send-Secure Button
`
`The Send-Secure Button is supported on the following platforms:
`
`Outlook Version
`
`OS
`
`Secure Button Client
`
`Microsoft Outlook 2010, 32 bit Window 7, 32 bit
`
`SecureMai1TaggingSetup32
`
`Microsoft Outlook 2013, 32 bit Window 8.1, 32 bit
`
`Microsoft Outlook 2016, 32 bit Window 10, 32 bit
`
`Microsoft Outlook 2010, 64 bit Window 7, 64bit
`
`SecureMai1TaggingSetup64
`
`Microsoft Outlook 2013, 64 bit Window 8.1, 64 bit
`
`Microsoft Outlook 2016, 64 bit Window 10, 64 bit
`
`Features and Enhancements
`
`Email Security 9.0.1 corrects several issues that are listed in Resolved Issues. The following features and
`enhancements were made to Email Security 9.0 to the improve protection from spam, phishing, and viruses.
`Features and enhancements include:
`
`• Updated Ema il Security Appliances
`
`• Capture ATP Integration
`
`• Office 365 Support
`
`•
`
`Improved Anti-Virus Offerings
`
`• Performance Enhancements
`
`Updated Email Security Appliances
`
`The Email Security Appliances (ESA) have been refreshed with the release of Email Security 9.0. They are built
`using 64-bit architecture, offering increased memory and the option for faster, detachable disk drives. Appliance
`functionality focuses on:
`
`• Effectively scanning inbound and outbound email
`
`• Providing multi-layer protection
`
`• Managing compliance and encryption
`
`Refer to the SonicWa/1 Email Security Appliance 5000/7000/9000 for more information about the appliances.
`
`SonicWall Email Security 9.0.1 I
`Release Notes
`
`3
`
`SonicWall-Finjan_00009998
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 5 of 12
`
`Capture ATP Integration
`
`Capture Advanced Threat Protection (Capture ATP) is a cloud-based service that analyzes various types of
`content for malicious behavior, and this function is being extended to Email Security beginning with version 9.0.
`It work similar to the anti-virus engines already integrated into Email Security and does the following:
`
`• Scan suspected messages.
`
`• Render a verdict about the message.
`
`• Take action based on what the administrator configures for that verdict.
`
`NOTE: All three anti-virus options (McAfee, Kaspersky, and Cyren) and Capture ATP need to be licensed
`separately to use Capture functionality.
`
`Unlike the anti-virus engines that check against malware signatures stored locally, messages for Capture ATP are
`uploaded to the back end cloud servers for analysis. These messages are typically advanced threats that evade
`identification by traditional static filters. They need to be identified by their behavior, and thus need to be run in
`a highly instrumented environment. Capture ATP accepts a broad range of file types to analyze.
`
`To engage Capture ATP:
`
`1
`
`Inbound email is first scanned by the other anti-virus plug-ins.
`
`•
`
`•
`
`If a threat is detected, then the appropriate action is taken (discard, junk, tag, etc.).
`
`If the service is enabled, all the anti-virus plug-ins return a no threat result, and the message
`contains an eligible attachment, the email is sent to Capture ATP for analysis.
`
`2 The attachment is uploaded to the Capture server and quarantined in the Capture Box.
`
`3 Capture ATP performs the analysis and returns a verdict.
`
`4 Further analysis is performed and Email Security applies the policy based on the final disposition of the
`message.
`
`Capture ATP status and settings can be manage through the Capture command on the user interface. For
`details, refer to the Email Security 9.0 Administration Guide.
`
`Office 365 Support
`
`Beginning with the 9.0 release, organizations that use Office 365 for email can now route their email through
`their Hosted Email Security (HES) to get added protection for their messages. A path can be created based on
`both the sender domain and the source IP address so outbound mail from ISPs can be scanned while still
`maintaining the privacy of the IPS customer.
`
`(I) I NOTE: Office 365 is supported only for Hosted Email Security; it is not supported for the on-premise
`
`products.
`
`Customers are strictly limited to one ISP as the source for one outbound path. If a customer wants a second ISP
`that customer must configure a second path. Similarly, no IP addresses outside of the ISP-owned range are
`allowed on a shared-IP path. Only one path can handle email for a particular sender domain.
`
`Because upstream TLS must be negotiated before the path is selected, weak ciphers are not allowed.
`
`Improved Anti-Virus Offerings
`
`Email Security 9.0 improved its core virus filtering capability with improved Kaspersky and Cyren filtering
`engines. Email Security integrated the Kaspersky 8.5 Anti-Virus DAT and scan engine and the Cyren 5.4.25 AV
`scan engine into the Email Security gateway and backend servers. Both utilizes 64-bit specific data for both
`Windows and Linux platforms. Both engines provide improved scanning and filtering to detect malicious
`content.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`4
`
`SonicWall-Finjan_00009999
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 6 of 12
`
`Performance Enhancements
`
`Improvements have been made to the Email Security application that can lead to an improved user experience.
`Some message attributes can be sent to SonicWall for analysis. These features, when combined with other data,
`can be used to identify and track new trends in spam and other junk mail. Those trends can be used to refine
`configurations and filtering.
`
`Be aware, when opting to share this information, some of the message attributes may contain human-readable
`information. Information about the sender, recipient, subject or content is accessible by SonicWall. It is,
`however, very difficult to recover the entire message that corresponds to a specific set of attributes.
`
`Resolved Issues
`
`This section provides a list of resolved issues for the 9.0.1 patch.
`
`Administration
`
`Resolved issue
`
`MTA delivery status is not updated.
`
`Occurs on Auditing outbound paths.
`
`Capture service doe not work.
`
`Occurs when running in dual CC mode and serial number of the secondary CC is written instead
`of the serial number of the primary CC.
`
`Anti Virus
`
`Resolved issue
`
`Restarting services from the GUI causes an initialization failure and re-initialization with error
`code " ... 25c".
`
`Occurs when one of the environmental variables in asg. real is not set.
`
`Known Issues
`
`This section provides a list of known issues for the 9.0.1 patch.
`
`Administration
`
`Known issue
`
`Auditing does not list the spam, phishing, and virus mails.
`
`Occurs when the action is set to Reject with SMTP error code 550 and Auditing won't contain
`information about rejected email.
`
`Issue ID
`
`184503
`
`184448
`
`Issue ID
`
`184540
`
`Issue ID
`
`184959
`
`Under certain conditions the appliance hangs. An alert isn't sent about the condition, and the
`user can't access the appliance.
`
`183343
`
`Occurs when a mount point is no longer reachable.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`5
`
`SonicWall-Finjan_00010000
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 7 of 12
`
`Install, Update and Upgrade
`
`Known issue
`
`Apache Tomcat fails to come up on 32-bit virtual machine (VM) in larger configurations.
`
`Occurs when the VM has 8 GB of RAM and multi-core CPU. Calculating the heap size for a VM
`with 8 GB of RAM results in a heap size greater than 2 GB which can cause failure if the OS is not
`large-address aware.
`
`Workaround: Execute the following CU commands to limit the Tomcat memory allocation to
`2 GB and restart the Tomcat service to restore Email Security's user interface.
`SNWLCLI >setsearchengine -memory 2048
`SNWLCLI >restart tomcat
`
`Issue ID
`
`183771
`
`Product Licensing
`
`SonicWall Email Security components must be registered on MySonicWall to enable full functionality and the
`benefits of SonicWall security services, firmware updates, and technical support. Log in or register for a
`MySonicWall account at https://www.mysonicwal l. com /.
`
`Email Security comes with several modules that must be licensed separately. For maximum effectiveness, all
`modules are recommended. The following licenses are available:
`
`• Email Protection (Anti-Spam and Anti-Phishing): Additional license that protects against email spam and
`phishing attacks.
`
`• Email Anti-Virus (McAfee and SonicWall Time Zero): Provides updates for McAfee anti-virus definitions
`and SonicWall Time Zero technology for immediate protection from new virus outbreaks.
`
`• Email Anti-Virus (Kaspersky and SonicWall Time Zero): Provides updates for Kaspersky anti-virus
`definitions and SonicWall Time Zero technology for immediate protection from new virus outbreaks.
`
`• Email Anti-Virus (SonicWall Grid A/V and SonicWall Time Zero): Provides updates for SonicWall Grid
`anti-virus definitions and SonicWall Time Zero technology for immediate protection from new virus
`outbreaks.
`
`• Email Anti-Virus Cyren: Provides updates for Cyren anti-virus definitions and SonicWall Time Zero
`technology for immediate protection from new virus outbreaks.
`
`• Email Encryption Service: License for encryption features enabling the secure exchange of sensitive and
`confidential information. It includes predefined dictionaries to ensure proper protection.
`
`• Email Compliance Subscription: License for compliance features. It includes predefined polices for easy
`compliance, allows multiple governance policies, identifies email for compliance policy enforcement,
`and provides compliance reporting and monitoring.
`
`• Capture for Email Security: Provides analysis of threats by examining their behavior in a managed
`environment.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`6
`
`SonicWall-Finjan_00010001
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 8 of 12
`
`Upgrade and Installation Instructions
`
`The following sections describe how to prepare for and upgrade or install your Email Security solution.
`
`Topics:
`
`• Backing Up Your Existing Environment
`
`• Upgrading Your Existing Firmware
`
`• Upgrading Your Existing Software
`
`•
`
`Installing the Virtual Appliance
`
`Backing Up Your Existing Environment
`
`Before you upgrade your appliance firmware, you should back up your existing environment. This allows you to
`restore it if you decide to change back for some reason. Your backup should include the settings files, including
`User Settings. Choose the backup process appropriate for your version of software:
`
`• Backing Up an 8.3 Environment
`
`• Backing Up a Pre-8.3 Environment
`
`Backing Up an 8.3 Environment
`
`To back up your existing 8.3 version environment:
`
`1 Log into the Email Security management interface using the admin account.
`
`2
`
`In the left navigation pane under System, choose Backup/Restore> Schedule Backups.
`
`3 Click on Backup Now button.
`
`Create Backup Snapshot
`
`Select Components
`
`D Global Settings
`
`D Organization Settings
`
`D User Settings
`
`D Reports data
`
`D Juek box
`
`D Archive
`
`Backup Store
`
`D Save on the Email
`Security host
`
`Last (Days)
`
`1 Day
`
`Last (Days)
`
`1 Day
`
`Last (Days)
`
`1 Day
`
`B
`B
`
`B
`
`D Save to FTP Server
`
`Create FTP Arofile
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`7
`
`SonicWall-Finjan_00010002
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 9 of 12
`
`4 On the Create Backup Snapshot page (shown above), select the components you want to backup. At a
`minimum, select Global Settings, Organization Settings, and User Settings.
`
`5 Select whether you want the snapshot to be saved on the Email Security host or saved to an FTP server.
`
`NOTE: If no FTP profiles have been defined for remote backups, the option to Save to FTP Server is not
`active. You can set up an FTP server profile by clicking on the link for Create FTP Profile.
`
`6 Click on Start to begin the backup.
`
`On the Schedule Backup page, messages report the status of the backups, and the task appears in the
`Backup Snapshots list on the Manage Backups page.
`
`Backing Up a Pre-8.3 Environment
`
`To back up your existing environment if older than version 8.3:
`
`1 Log into the Email Security management interface using the admin account.
`
`2
`
`In the left navigation pane under System, choose Backup/Restore.
`
`Manage Bcldrups
`
`You ... y ad-G "fal:c o """""°I" c,--....:1~ 'T.mgo ,nop,to1 a-cob o !loo, ll,c&>.,IScar,ty_,,,,,. OOM-loodngo rn,psholcqxs 11,c ........ t 'Worlo,.... loc.altw..d ,h.,,
`
`r,,,.,11n11
`S.,r,r,go (ncM!co- oo< ll(el"ICttn;,)
`
`Pt<UzSe-
`~"da,.
`llri:bo.
`
`a.o.o,1891
`lOHfl)l/OS H:01,"«,
`
`Yes
`
`vnl~ • >Ml»ho of U.. ~ lf.litll rm 1k rm.,_rilV >MYff
`
`:.tt_C.-_1>:i...., .. W,~I)
`
`3 Under the heading Create a snapshot of the following data on the Email SEcurity Server, select Settings.
`
`4 Click Take Snapshot Now to create a snapshot.
`
`5 Click Download Snapshot to save the snapshot to your local file system.
`
`Upgrading Your Existing Firmware
`
`To upgrade the existing firmware on an Email Security appliance:
`
`1 Log into your MySonicWall account and download the new Email Security firmware to your management
`computer.
`
`2 Log into the Email Security management interface using the admin account.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`8
`
`SonicWall-Finjan_00010003
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 10 of 12
`
`3 Navigate to the System > Advanced page and scroll down to the Upload Patch section, under
`Miscellaneous Settings.
`
`Upl0ad Patch
`
`Upload a new copy of a previously -downloaded version of Email Security to the server and install it.
`
`Patch file:
`
`I App~ Patch I
`
`[ Choo,se File [ No file chosen
`
`(DJ
`
`4 Click Choose File to locate the Email Security firmware file on your local file system, and then click Apply
`Patch.
`
`As part of the upgrade process, the Email Security appliance does reboot. The upgrade process could
`take quite a lot of time, depending on the size of your solution. All the settings and data are preserved.
`6 CAUTIO
`. Your ES8300 appliance is equipped with a battery backup unit on the RAID Controller Card,
`which allows the appliance to write volatile memory to disk in the event of a loss of power. This battery
`backup unit must be charged for 24 hours. When deploying your ES8300 appliance, follow the startup
`and registration instructions detailed in the ES8300 Getting Started Guide, and then allow the battery
`backup in the unit to charge for 24 hours. If the battery is not fully charged, some RAID features are
`turned off, and the appliance performance is temporarily impaired until the battery is fully charged.
`
`Upgrading Your Existing Software
`
`The full installer for Email Security Software includes installation of Apache Tomcat, the Java Runtime
`Environment (JRE), Firebird, and MySQL as well as the base Email Security software.
`
`CD I NOTE: Before upgrading Email Security on a Windows server, be sure the server has the latest updates and
`
`service packs installed.
`
`To upgrade your existing Email Security installation:
`
`1 Log into your MySonicWall account and download the new Email Security Software installation file to the
`server running Email Security.
`
`2 On the server running Email Security, double-click the Email Security installation file.
`
`3 Click Run in the dialog box.
`
`If you do not have direct access to the server, use a remote desktop connection to connect to the server
`and run the installation file on the server.
`
`4
`
`In the Welcome page of the installation wizard, click Next.
`
`5 Read the License Agreement and then click Next to accept the agreement.
`
`6 SonicWall recommends that Asian language packs be installed, and an alert is displayed if they are
`missing.
`
`• To proceed with the Email Security installation and install Asian language packs later, click Next.
`
`• To install Asian language packs prior to proceeding, click Cancel.
`CD NOTE: Installing Asian language packs is optional; however, the spam prevention capabilities of
`SonicWall Email Security may be diminished without them. Asian language packs can be installed
`before or after Email Security Software installation.
`
`7 On the Destination Folder page, click Browse to select an alternate folder, or click Next to accept the
`default location.
`
`CD I NOTE: This folder should not be scanned by an anti-virus engine.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`9
`
`SonicWall-Finjan_00010004
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 11 of 12
`
`8 On the Choose Data Folder page, click Browse to select an alternate folder, or click Next to accept the
`default location.
`
`If the data folder is on a different disk drive than the install directory, ensure that it has fast read/write
`access with less than 10 millisecond latency. You can test latency with the ping command.
`
`9 On the Start Installation page, click Next.
`
`10 If requested, allow the installation of Tomcat, Firebird, and the Java Runtime Environment (J2RE).
`
`If Tomcat is installed in this step, it prompts for the Apache Tomcat Web server port number. The default
`port is 80. If you are already running a Web server on port 80, you must change the port setting.
`SonicWall recommends port 8080.
`
`11 Click Next to continue.
`
`(I) I NOTE: You can change the port number and configure HTTPS access after installation by using the Server
`
`Configuration> User View Setup page of the Email Security management interface.
`
`12 After the installation finishes, click Finish in the Installation Complete page. A browser window displays
`the links to the Email Security user interface and documentation.
`
`Installing the Virtual Appliance
`
`For information about installing SonicWall Email Security as a Virtual Appliance, see the Email Security Virtual
`Appliance Getting Started Guide, available at: https ://support.sonicwa ll.com/sonicwall-email(cid:173)
`security/3300/technical-documents
`
`SonicWall Support
`
`Technical support is available to customers who have purchased SonicWall products with a valid support
`maintenance contract and to customers who have trial versions.
`
`The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a
`day, 365 days a year. To access the Support Portal, go to https://support.sonicwall.com .
`
`The Support Portal enables you to:
`
`• View knowledge base articles and technical documentation
`
`• Download software
`
`• View video tutorials
`
`• Collaborate with peers and experts in user forums
`
`• Get licensing assistance
`
`• Access MySonicWall
`
`• Learn about SonicWall professional services
`
`• Register for training and certification
`
`To contact SonicWall Support, visit https://support.sonicwa ll.com/contact-support.
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`10
`
`SonicWall-Finjan_00010005
`
`

`

`Case 5:17-cv-04467-BLF Document 320-14 Filed 12/02/20 Page 12 of 12
`
`Copyright © 2017 SonicWall Inc. All rights reserved.
`
`This product is protected by U.S. and international copyright and intellectual property laws. SonicWall is a trademark or
`registered trademark of SonicWall Inc. and/or its affiliates in the U.S.A. and/or other countries. All other trademarks and
`registered trademarks are property of their respective owners.
`
`The information in this document is provided in connection with SonicWall Inc. and/or its affiliates' products. No license,
`express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection
`with the sale of SonicWall products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE
`AGREEMENT FOR THIS PRODUCT, SONICWALL AND/OR ITS AFFILIATES ASSUME NO LIABILITY WHATSOEVER AND DISCLAIMS
`ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE
`IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT
`SHALL SONICWALL AND/OR ITS AFFILIATES BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR
`INCIDENTAL DAMAGES {INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR
`LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF SONICWALL AND/OR ITS
`AFFILIATES HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SonicWall and/or its affiliates make no
`representations or warranties with respect to the accuracy or completeness of the contents of this document and reserve the
`right to make changes to specifications and product descriptions at any time without notice . SonicWall Inc. and/or its affiliates
`do not make any commitment to update the information contained in this document.
`
`For more information, visit https://www.sonicwall .com/legal/.
`
`Legend
`
`&. I WARNING : A WARNING icon indicates a potential for property damage, personal injury, or death.
`6 [ CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.
`(D I IMPORTANT NOTE, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.
`
`Last updated: 4/5/17
`
`232-003843-00 Rev A
`
`SonicWall Email Security 9.0.1
`Release Notes
`
`11
`
`SonicWall-Finjan_00010006
`
`

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