SonicWALL Security Solutions SonicWALL Security

Transcription

1 SonicWALL Security Solutions SECURITY SonicWALL Security SonicWALL Security 6.0 Administrator's Guide Appliance Edition

2 SonicWALL Security Administrator s Guide Version 6.0 SonicWALL, Inc Borregas Avenue Sunnyvale, CA Phone: Fax: [email protected]

3 Copyright Notice 2007 SonicWALL, Inc. All rights reserved. Under the copyright laws, this manual or the software described within, can not be copied, in whole or part, without the written consent of the manufacturer, except in the normal use of the software to make a backup copy. The same proprietary and copyright notices must be affixed to any permitted copies as were affixed to the original. This exception does not allow copies to be made for others, whether or not sold, but all of the material purchased (with all backup copies) can be sold, given, or loaned to another person. Under the law, copying includes translating into another language or format. Specifications and descriptions subject to change without notice. Trademarks SonicWALL is a registered trademark of SonicWALL, Inc. MailFrontier, Inc., the MailFrontier logo, MailFrontier Self Monitoring Active Response Team (SMART) Network, and MailFrontier Software are trademarks or registered trademarks of SonicWALL, Inc. SonicWALL, Inc., the SonicWALL logo, SonicWALL Self Monitoring Active Response Team (SMART) Network, and SonicWALL Security are trademarks or registered trademarks of SonicWALL, Inc. Lotus Notes is a registered trademark and Domino is a trademark of IBM. Microsoft is a registered trademark and Microsoft Server is a trademark of Microsoft Corporation. Microsoft Windows 98, Windows NT, Windows 2000, Windows XP, Windows Server 2003, Internet Explorer, and Active Directory are trademarks or registered trademarks of Microsoft Corporation. Firefox is a trademark of the Mozilla Foundation. Netscape is a registered trademark of Netscape Communications Corporation in the U.S. and other countries. Netscape Navigator and Netscape Communicator are also trademarks of Netscape Communications Corporation and may be registered outside the U.S. Adobe, Acrobat, and Acrobat Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the U.S. and/or other countries. Other product and company names mentioned herein may be trademarks and/or registered trademarks of their respective companies and are the sole property of their respective manufacturers. Limited Warranty SonicWALL, Inc. warrants that commencing from the delivery date to Customer (but in any case commencing not more than ninety (90) days after the original shipment by SonicWALL), and continuing for a period of twelve (12) months, that the product will be free from defects in materials and workmanship under normal use. This Limited Warranty is not transferable and applies only to the original end user of the product. SonicWALL and its suppliers' entire liability and Customer's sole and exclusive remedy under this limited warranty will be shipment of a replacement product. At SonicWALL's discretion the replacement product may be of equal or greater functionality and may be of either new or like-new quality. SonicWALL's obligations under this warranty are contingent upon the return of the defective product according to the terms of SonicWALL's then-current Support Services policies. This warranty does not apply if the product has been subjected to abnormal electrical stress, damaged by accident, abuse, misuse or misapplication, or has been modified without the written permission of SonicWALL. DISCLAIMER OF WARRANTY. EXCEPT AS SPECIFIED IN THIS WARRANTY, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS, AND WARRANTIES INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTY OR CONDITION OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT, SATISFACTORY QUALITY OR ARISING FROM A COURSE OF DEALING, LAW, USAGE, OR TRADE PRACTICE, ARE HEREBY EXCLUDED TO THE MAXIMUM EXTENT ALLOWED BY APPLICABLE LAW. TO THE EXTENT AN IMPLIED WARRANTY CANNOT BE EXCLUDED, SUCH WARRANTY IS LIMITED IN DURATION TO THE WARRANTY PERIOD. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. This disclaimer and exclusion shall apply even if the express warranty set forth above fails of its essential purpose. DISCLAIMER OF LIABILITY. SONICWALL'S SOLE LIABILITY IS THE SHIPMENT OF A REPLACEMENT PRODUCT AS DESCRIBED IN THE ABOVE LIMITED WARRANTY. IN NO EVENT SHALL SONICWALL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER, INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, LOSS OF INFORMATION, OR OTHER PECUNIARY LOSS ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL, OR PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY ARISING OUT OF THE USE OF OR INABILITY TO USE HARDWARE OR SOFTWARE EVEN IF SONICWALL OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event shall SonicWALL or its suppliers' liability to Customer, whether in contract, tort (including negligence), or otherwise, exceed the price paid by Customer. The foregoing limitations shall apply even if the above-stated warranty fails of its essential purpose. BECAUSE SOME STATES OR JURISDICTIONS DO NOT ALLOW LIMITATION OR EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. NOTE: The SonicWALL Security software service is an annual subscription which is subject to the terms and conditions of SonicWALL, Inc. s applicable subscription agreement and includes: Product updates, SonicWALL threat signature updates, and standard technical support for one (1) year from the date of purchase. SonicWALL Security appliances are integrated hardware and software solutions, which include SonicWALL Security software. SonicWALL Security appliances are subject to the terms and conditions of SonicWALL, Inc. s applicable license agreement. Updates to the SonicWALL Security software, SonicWALL Spam Signature Updates, and technical support may be purchased on an annual basis. AntiVirus support is optionally available.

4 Table of Contents Table of Contents i About this Guide vii Documentation Conventions vii Documentation Overview viii Finding Online Help viii Chapter 1: Planning SonicWALL Security Deployment SonicWALL Security and Mail Threats Defining SonicWALL Security Deployment Architecture Inbound and Outbound Flow Proxy versus MTA Should You Choose an All in One or a Split Architecture? Typical SonicWALL Security Deployments SonicWALL Security as the First-Touch / Last-Touch Server SonicWALL Security not as a First-Touch / Last Touch Server Chapter 2: Getting Started Introduction Initial Configuration SonicWALL Security Master Account Logging In Change Master Account Password Quick Configuration Understanding the SonicWALL Security User Interface Automatically Download Updates for SonicWALL Security Configuring Spam, Phishing, and Virus Updates Updates Using SafeMode Chapter 3: System Introduction Setting Your Network Architecture Adding an Inbound Mail Server for All in One Architecture SonicWALL Security Administrator Guide i

5 Source IP Contacting Path Adding an Outbound Mail Server for All in One Architecture Adding a Server for Split Architecture Adding a Control Center Adding a Remote Analyzer Configuring Inbound Flow for a Remote Analyzer Configuring Outbound Flow for a Remote Analyzer Configuring Remote Analyzers to Communicate with Control Centers Deleting a Remote Analyzer from a Split Configuration Testing the Mail Servers Changing from an All in One Configuration to a Split Configuration LDAP Configuration Configuring LDAP LDAP Query Panel Advanced LDAP Settings Default Message Management Settings Junk Box Summary User View Setup Updates Web Proxy Configuration Monitoring and Alerts About Alerts Viewing Alert History Alert Suppression Schedule Connection Management Intrusion Prevention Quality of Service Manually Edit IP Address List Backup/Restore Settings Manage Backup Manage Restores Host Configuration Changing the Hostname Networking Configuring Advanced Settings Chapter 4: Anti-Spam Anti-Phishing Techniques Managing Spam Spam Identification Managing Spam through Default Settings Adding People to Allowed and Blocked Lists for the Organization Companies or Domains Mailing Lists Anti-Spam Aggressiveness Foreign Languages ii SonicWALL Security Administrator Guide

6 Black List Services (BLS) Managing Spam Submissions and Probe Accounts Managing Miscategorized Messages Probe Accounts Managing Spam Submissions Anti-Phishing What is Enterprise Phishing? Preventing Phishing Configuring Phishing Protection Use SonicWALL Security s Community to Alert Others Report Phishing and Other Enterprise Fraud to SonicWALL Security Chapter 5: Anti-Virus Techniques How Virus Checking Works Preventing Viruses and Likely Viruses in Checking for Updates Zombie and Spyware Protection Chapter 6: Auditing Auditing Searching Inbound and Outbound s Configure Auditing Message Audit Chapter 7: Policy & Compliance Standard Module vs. Compliance Module Basic Concepts for Policy Management Defining Word Usage Defining Address Matching Defining Intelligent Attachment Matching Defining Disguised Text Identification Inbound vs. Outbound Policy Filters Preconfigured Inbound Filters Preconfigured Outbound Filters Filters Language Support Managing Filters Editing a Filter Deleting a Filter Changing Filter Order Advanced Filtering Policy Groups Compliance Module Dictionaries Approval Boxes SonicWALL Security Administrator Guide iii

7 Encryption Record ID Definitions Archiving Chapter 8: User and Group Management Working with Users Searching for Users Sort Signing In as a User Resetting User Message Management Setting to Default Edit User Rights Import Export Add Remove Working with Groups About LDAP Groups SonicWALL Security Roles Setting a LDAP Group s Role Setting Spam Blocking Options for LDAP Groups User View Setup Rules and Collaborative Settings Configuring Foreign Language for Groups Managing the Junk Box Summary Spam Management Phishing Management Virus Management Assigning Delegates Chapter 9: Junk Box Junk Box - Normal Mode Junk Box - Detailed Search Mode Outbound Messages Stored in Junk Box Working with Junk Box Messages Unjunk Send Copy To Release Delete Message Details Managing Junk Summaries Chapter 10: Reports and Monitoring Monitoring SonicWALL Security System Status MTA Status iv SonicWALL Security Administrator Guide

8 Real-Time System Monitor Reporting in SonicWALL Security Generating Per-Domain Reports Overview Reports Reports Dashboard Return on Investment Bandwidth Savings Inbound Good vs Junk Outbound Good vs Junk Inbound vs Outbound Top Outbound Senders Junk Breakdown Anti-Spam Reports Spam Caught Top Spam Domains Top Spam Recipients Anti-Phishing Reports Phishing Messages Anti-Virus Reports Inbound Viruses Caught Top Inbound Viruses Outbound Viruses Caught Top Outbound Viruses Policy Management Reports Inbound Policies Filtered Top Inbound Policies Outbound Policies Filtered Top Outbound Policies Compliance Reports Inbound Messages Decrypted Inbound Messages Archived Top Inbound Approval Boxes Outbound Messages Encrypted Outbound Messages Archived Top Outbound Approval Boxes Directory Protection Reports Number of DHA Attacks Top DHA Domains Advanced Scheduled Reports Custom Reports Appendix A: SonicWALL Security TCP Port Utilization Inbound TCP Traffic Outbound TCP Traffic SonicWALL Security Administrator Guide v

9 Split Configuration TCP Port Utilization Appendix B: Command Line Interface Introduction Logging into the CLI Scripting Using the Command Line Interface Index vi SonicWALL Security Administrator Guide

10 Preface SonicWALL s threat protection solution is a dynamic, self-learning, and self-running system, providing IT departments with the protection they need for inbound and outbound . SonicWALL Security offers redundancy, comprehensive reporting and central administration across multiple data centers. The solution scales for organizations with 10 employees to enterprises with 100,000 or more employees. About this Guide This guide describes how to configure SonicWALL Security, and the SonicWALL Security appliances. Information that is specifically about SonicWALL Security appliances is indicated by a footnote at the bottom of the page. Documentation Conventions Font Bold Italic Courier Bold Courier Meaning Terms you see in a SonicWALL Security window Variable names Text on a command line Text that you type in a command line SonicWALL Security Administrator s Guide vii

11 About this Guide Documentation Overview SonicWALL Security provides the following documents to help in the installation, administration, and use of its products to protect users from phishing, spam, viruses, and to manage the security policies you define for your organization. Who Should Read this? Document Name Network Administrators SonicWALL Security s Getting Started Guide Users SonicWALL Security s Administrator Guide SonicWALL Security s User Guide Finding Online Help Click the What is this? button for in-depth online help on a specific area of the SonicWALL Security interface. Click the Help button on any UI web page for information on how to use the UI features on that page. viii SonicWALL Security Administrator s Guide

12 CHAPTER 1 Planning SonicWALL Security Deployment You must determine the appropriate architecture for SonicWALL Security before you deploy it in your network. This section discusses the different modules available in SonicWALL Security and network topology planning. Note For installation and set up instructions for your SonicWALL Security appliance, refer to the SonicWALL Security Series Getting Started Guide document. SonicWALL Security and Mail Threats SonicWALL Security determines that an fits only one of the following threats: Spam, likely Spam, Phishing, likely Phishing, Virus, likely Virus, Policy Violation, or Directory Harvest Attack (DHA). It uses the following precedence order when evaluating threats in messages: DHA Virus Policy Phishing Likely Phishing Spam Likely Spam Likely Virus For example, if a message is both a virus and a spam, the message will be categorized as a virus since virus is higher in precedence than spam. If SonicWALL Security determines that the message is not any of the above threats, it is deemed to be good and is delivered to the destination server. SonicWALL Security Administrator s Guide 1

13 Defining SonicWALL Security Deployment Architecture Defining SonicWALL Security Deployment Architecture SonicWALL Security can be configured in two ways: All in One: In this configuration, all machines running SonicWALL Security analyze , quarantine junk mail, and allow for management of administrator and user settings. See Figure 1:1 for a typical All in One configuration. Figure 1:1 All in One Architecture In an All in One configuration, you can also deploy multiple SonicWALL Security servers in a cluster setup wherein all of the gateways share the same configuration and data files. To set up such a cluster, begin by creating a shared directory, on either one of the SonicWALL Security servers or on another dedicated server (preferred) running the same operating system. This shared directory will be used to store data including user settings, quarantine , etc., from all the SonicWALL Security servers in the cluster. 2 SonicWALL Security Administrator s Guide

14 Defining SonicWALL Security Deployment Architecture Split: In a Split network configuration, there are two kinds of servers: Control Centers and Remote Analyzers. In this configuration there is typically one Control Center and multiple Remote Analyzers, but the Control Center can be set up in a cluster as well. The Split configuration is designed for organizations with remote physical data centers. The Split configuration, shown in Figure 1:2, allows you to manage SonicWALL Security so that messages are filtered in multiple remote locations through multiple Remote Analyzers. The entire setup is centrally managed from a single location through the Control Center. Control Center clusters are not supported by SonicWALL Security appliance. Figure 1:2 Split Network Architecture The Control Center, in addition to managing all data files, controls, monitors and communicates with all Remote Analyzers. The data files consist of statistical data such as how much has been received, network usage, remote hardware space used, and hourly spam statistics. The Control Center stores or quarantines junk it receives from the Remote Analyzers. It also queries LDAP servers to ensure valid users are logging in to SonicWALL Security. End users can log in to a Control Center to manage their junk mail. Remote Analyzers analyze incoming to determine whether it is good or junk. It sends junk to the Control Center where it is quarantined. It routes good mail to its destination server. Only administrators can log in to a Remote Analyzer. Note The Replicator is the SonicWALL Security component that automatically sends data updates from the Control Center to the Remote Analyzer, ensuring that these components are always synchronized. Replicator logs are stored in the Control Center s logs directory. You can review replication activity from these logs for troubleshooting purposes. SonicWALL Security Administrator s Guide 3

15 Defining SonicWALL Security Deployment Architecture Inbound and Outbound Flow SonicWALL Security can process both inbound and outbound on the same machine. In an All in One configuration, each SonicWALL Security instance can support both inbound and outbound . In a Split configuration, each Remote Analyzer can support both inbound and outbound . For inbound flow, DNS configuration and firewall rules need to be set to direct traffic to SonicWALL Security. Whereas, for outbound flow, the downstream server must be configured to send all to Security (Smart Host Configuration). Proxy versus MTA SonicWALL Security can run either as an SMTP proxy or an MTA (Mail Transfer Agent). The SMTP proxy operates by connecting to a destination SMTP server before accepting messages from a sending SMTP server. Note that SMTP proxys can only send to one server. Some benefits of the SMTP proxy are: All processing occurs in memory, significantly reducing the latency and providing higher throughput There is no queue and SonicWALL Security does not lose any messages. SonicWALL Security automatically respects your existing fail over strategies if your mail infrastructure experiences a failure. The MTA service operates by writing messages to disk and allows for routing of a message. Some benefits of the MTA are: Can route messages to different domains based on MX records or LDAP mapping. Can queue messages by temporarily storing messages on disk and retrying delivery later in case the receiving server is not ready. Allows SonicWALL Security to be the last touch mail gateway for outbound traffic Should You Choose an All in One or a Split Architecture? SonicWALL recommends the All in One configuration whenever possible because of its simplicity. Choose a Split configuration to support multiple physical data centers and if you want to centrally manage this deployment from a single location. SonicWALL strongly recommends that after you deploy the chosen architecture, you do not change the setup from a Control Center to a Remote Analyzer or vice versa, as there are no obvious advantages, and some data might be lost. Thus, it is important to make the deployment architecture decision before installing SonicWALL Security. 4 SonicWALL Security Administrator s Guide

16 Defining SonicWALL Security Deployment Architecture Typical SonicWALL Security Deployments SonicWALL Security as the First-Touch / Last-Touch Server Figure 1:3 illustrates a typical network topology when SonicWALL Security is the first-touch and last-touch server in the DMZ. In this deployment, you need to change your MX records to point to the SonicWALL Security setup. Also, all the inbound and outbound connections (typically port 25) for SonicWALL Security must be properly configured in your firewalls. Figure 1:3 SonicWALL Security as the First-Touch and Last-Touch Server in the DMZ In this configuration, SonicWALL Security can be configured on the inbound path to be either a SMTP Proxy or a MTA. On the outbound path, it must be configured to be a MTA. This setup also can be extended to a cluster with multiple SonicWALL Security servers all using a shared drive for data location. For more information on routing using Smart Host, refer to Adding an Inbound Mail Server for All in One Architecture on page 22. SonicWALL Security Administrator s Guide 5

17 Defining SonicWALL Security Deployment Architecture To configure SonicWALL Security in this configuration, you also need to: 1. Configure SonicWALL Security server with a static IP address on your DMZ. 2. In your firewall, add an inbound NAT Rules s private IP address to an Internet addressable IP address for TCP port 25 (SMTP). 3. In the public DNS server on the Internet, create an A record, mapping a name such as smtp.my_domain.com, to the Internet addressable IP address you assigned in step Update your domain s MX record to point to the new a record. You need to deploy the SonicWALL Security for each MX record. SonicWALL Security not as a First-Touch / Last Touch Server Figure 1.4 illustrates a network topology where Security is not the first-touch and last-touch SMTP server. This configuration is not recommended because security mechanisms such as SPF and Connection Management cannot be utilized. In this configuration SonicWALL Security can be configured to be either an MTA or a proxy. Figure 1:4 SonicWALL Security not as the First-Touch and Last-Touch Server 6 SonicWALL Security Administrator s Guide

18 CHAPTER 2 Getting Started Introduction This chapter describes how to configure SonicWALL Security to match your environment and user needs. Note IMPORTANT: Configure your web browser s pop-up blockers to allow pop-ups from your organization s SonicWALL Security server before using SonicWALL Security, because many of the windows are pop-up windows. Note For security purposes, SonicWALL Security terminates your session if there is no activity for 10 minutes. You must log in again if this occurs. Initial Configuration SonicWALL Security Master Account Each SonicWALL Security setup has a Master Account which is a master administrative account. You use this account to initially configure the server, configure for LDAP synchronization and assign administrative privileges to other accounts. The Master Account s user name is admin and the password is password. SonicWALL Security Administrator s Guide 7

19 Initial Configuration Logging In Log in to your SonicWALL Security as a user with administrator privileges. Example: Figure 2:1 Login window To log in with the Master Account, type: User Name: admin Password: password The first time you log in to the SonicWALL Security system, you are directly taken to the license settings screen, see Figure 2:2, where you can do the following: Change Account password Confirm license keys in the License Management section Perform Quick Configuration of the system 8 SonicWALL Security Administrator s Guide

20 Initial Configuration Change Master Account Password After you login using the Master Account, you can change the password. SonicWALL strongly recommends that you change the Master Account password. Figure 2:2 System > Administration To change password: 1. Type admin for the username. 2. Type a new password in the Password text box. 3. Type the same password in the Confirm password text box. SonicWALL Security Administrator s Guide 9

21 Initial Configuration Quick Configuration If you plan to install SonicWALL Security in an All in One Configuration for inbound and outbound message processing with only one downstream server, no SSL, and routine LDAP options, click the Quick Configuration link from the License Management window. Quick Configuration allows you to set up SonicWALL Security in a default configuration. Quick Configuration also allows you to choose whether to quarantine junk messages in the Junk Box or to pass messages through to users. However, Quick Configuration requires that you configure all modules similarly; that is, if you store spam messages in the Junk Box, you must also store messages with viruses in the Junk Box. Note If you have previously configured your SonicWALL Security with more complex settings than are supported by Quick Configuration, the following alert will appear: Figure 2:3 Quick Configuration Alert If this alert window or a similar alert window appears, you must either configure all of the modules to pass through without filtering or to store it in the Junk Box. Figure 2:4 displays the Quick Configuration window. To configure SonicWALL Security using the Quick Configuration window, select the radio buttons and enter values for the following configuration variables: 10 SonicWALL Security Administrator s Guide

22 Initial Configuration 1. Network Architecture: Enter the Inbound Destination server name or IP address and port number. Select the Inbound SMTP setup: Allow SMTP recipient addresses to all domains Only allow SMTP recipients addresses to these domains and enter the domains Click Test Mail Servers to determine that the flow of from the SonicWALL Security server to downstream mail server is able to process . Select the Outbound Path setup checkbox if the specified Inbound Destination Server will be the only server passing outbound messages to SonicWALL Security. Figure 2:4 Quick Configuration Window. SonicWALL Security Administrator s Guide 11

23 Initial Configuration 2. LDAP Configuration Add your LDAP Server name or IP address. This is the hostname or IP address of the LDAP server. Frequently, this is the name of your Exchange server or your server. Select the LDAP Server type from the drop-down list. Enter your Login name in the format indicated by the type of LDAP server. Active Directory - The login name is commonly of the form domain\username; for example: sales\john Exchange The login name is commonly of the form CN=username, for example: CN=john Note To use NTLM authentication, add the LDAP domains on the LDAP configuration page. Lotus Notes/Domino - The login name is commonly of the form username, for example: john SunOne/iPlanet - The login name can either be the exact string "CN=Directory Manager" or a user's X.400-style login. Consider both examples below: CN=Directory Manager UID=john,OU=people,O=xyz.com,O=internet For Other LDAP Servers, see the documentation that shipped with that product. Enter your password. 3. Message Management: Click the Test LDAP Login button to ensure that LDAP you can log in to your LDAP server. Click the Test LDAP Query button to ensure that LDAP you can query your LDAP server. Enter the Windows NT/NetBIOS domain name if you have an Active Directory or an Exchange 5.5 server. Select the action SonicWALL Security should take for messages identified as junk: Click Quarantine junk to cause SonicWALL Security to store all messages in the Junk Box. Click Deliver all messages to users to allow all messages to pass through to users without filtering for threats. 12 SonicWALL Security Administrator s Guide

24 Initial Configuration 4. Junk Box Summary: 5. Updates Check the Send summaries daily check box to send users daily summaries of their quarantined , if you selected Quarantine junk in step 3. Check the Users can preview their own quarantined junk mail check box to allow users to preview their junked messages. Enter the URL for the user view. This text box is filled in automatically based on your server configuration and is included in the Junk Box Summary . Click Test this Link to ensure that you have configured a link for users to connect to SonicWALL Security. Click the Test Connectivity to SonicWALL button to ensure that you can connect to the SonicWALL Security data center. Click Apply Changes to save your Quick Configuration settings. Your server is now ready to process messages and stop threats. SonicWALL Security Administrator s Guide 13

25 Initial Configuration Understanding the SonicWALL Security User Interface This section describes how to navigate the SonicWALL Security user interface. Figure 2:5 displays the basic SonicWALL Security window. Figure 2:5 SonicWALL Security User Interface Overview Left-hand navigation menu User s Role User s login Click here to send a message to SonicWALL Security Support Click here to get application information Click here to change UI language The upper right hand corner displays the role of the user logged in: Admin, Manager, Help Desk, Group Admin or User. See SonicWALL Security Roles on page 142 for more information about roles. The current login name is displayed next to the role. Use the left-hand navigation pane to select the different modules, such as spam management or server configuration. Each button brings up a unique menu on the left hand side. 14 SonicWALL Security Administrator s Guide

26 Initial Configuration Click the links on the lower margin of the window for the following information: Contact us: Click this link for a Contact Technical Support form and other support information. About: Click this link to display a window that contains information about SonicWALL Security. Sign in as any user: Click this link if you are signed in as the administrator and would like to login as a user. System host name: SonicWALL Security can run on more than one server. The lower right corner of your window displays the host name for the server to which you are currently logged in. Preferred Language: Click this drop-down box to change SonicWALL Security s user interface in any of the languages shown in Figure 2:6. By default, SonicWALL Security automatically senses the language that you have configured your Web browser. Figure 2:6 Preferred Language SonicWALL Security Administrator s Guide 15

27 Automatically Download Updates for SonicWALL Security Automatically Download Updates for SonicWALL Security To provide the best protection against latest threats, SonicWALL periodically releases updates to its software. SonicWALL recommends that you keep your software version up-to-date to ensure that you get the best protection available. Configuring Spam, Phishing, and Virus Updates To configure automatic software downloads for SonicWALL Security servers that run All in One configuration on Windows: 1. Click System > Updates. SonicWALL Security displays the Updates window, as shown in Figure 2:7. Figure 2:7 Configuring Updates to SonicWALL Security 2. Select the time interval from the Check for Spam, Fraud, and Virus Blocking Updates drop-down list to configure how often to receive junk-blocking updates. 3. Check the Submit unjunk thumbprints check box to send unjunked thumbprints to SonicWALL Security s Research Laboratory. Note When users unjunk a message, a thumbprint of that message can be sent to SonicWALL Security. These unjunked messages are used to improve the collaborative settings for all users, which tracks new trends in spam and other junk , and helps prevent unwanted . The thumbprints sent optionally from SonicWALL Security contain absolutely no readable information. 16 SonicWALL Security Administrator s Guide

28 Using SafeMode 4. Check the Submit generic spam blocking data check box to send spam-blocking data to SonicWALL Security s Research Laboratory. Generic spam blocking data is sent to SonicWALL Security to assist in customer support and to help improve spam blocking. No messages, content, header information or any other uniquely identifiable information is ever sent. Sample information that is sent includes the following data: Volume of messages processed and junked Success of various junking methods Number of users protected Updates When a new SonicWALL Security software update becomes available, the SonicWALL Security appliance automatically downloads the update and alerts the administrator via that it is available. Upon logging in to the SonicWALL Security administrative interface, a pop-up screen displays, prompting the administrator to either click to update now or wait to update later. Note The administrator should choose the appropriate time to complete the update while considering the delay in traffic flow. The installation will take less than ten minutes. Figure 2:8 Update Alert Once the Update Now button is selected, the update file is extracted. When the process is complete, the SonicWALL Security appliance will automatically reboot. Note SonicWALL recommends that you download and install major updates as soon as possible. Using SafeMode SafeMode is a fall back option when a normal upgrade fails to patch and the administrator wants to restore the appliance using a different image. Warning This is not a function that administrators should choose unless a patch installation from the UI has failed. SonicWALL Security Administrator s Guide 17

29 Using SafeMode To restore the appliance using SafeMode, perform the following steps: 1. Reboot the appliance to view the GRUB loader options. Either connect a console and keyboard to the appliance or use the serial port and redirect the output to another system. The GRUB menu allows the administrator to chose which firmware image to boot. Available options are the following: " Security SonicWALL MFL" - the default option which boots into current Security firmware "SonicWALL MFL [Verbose Startup Mode]" - this option boots the same firmware as above, but outputs debugging information on startup "SonicWALL Authentication Reset" - this option allows administrative credentials to reset to default values "SonicWALL Safe Mode" - boots into special firmware image, which allows a firmware update to perform, in case normal update procedure resulted in an unbootable firmware. 2. Using the arrow keys on your keyboard, select the Safe Mode option to boot into SafeMode and display the command line option to set the IP, subnet mask, and gateway. 18 SonicWALL Security Administrator s Guide

30 Using SafeMode 3. Access the SafeMode user interface by entering the URL in the browser as <IP_assigned_in_the_commandline_screen> for example The following SafeMode screen displays: 4. Use the Browse button to point to the firmware to be imaged. 5. Click the Upload button to upload the file. 6. Click the Reboot button. The system reboots and the information posts back on the web browser. SonicWALL Security Administrator s Guide 19

31 Using SafeMode 20 SonicWALL Security Administrator s Guide

32 CHAPTER 3 System Introduction In this chapter, you will learn how to configure the system more extensively and learn more about additional system administration capabilities. Setting Your Network Architecture There are different ways to configure and deploy SonicWALL Security, and the first decision to make is the choice of network architecture. See Planning SonicWALL Security Deployment on page 1 for more information on what network architecture is appropriate for your need. You must decide whether you are setting up a Split or All in One architecture, as that choice impacts other configuration options. You can change the architecture later, but if you do so, you will need to add your mail servers and reset configuration options again. To configure SonicWALL Security as your desired network architecture, click System > Network Architecture. A screen similar to Figure 3:1 appears. SonicWALL Security Administrator s Guide 21

33 Setting Your Network Architecture Adding an Inbound Mail Server for All in One Architecture Set this server to All in One configuration by choosing the radio button next to All in One. Figure 3:1 System > Network Architecture 22 SonicWALL Security Administrator s Guide

34 Setting Your Network Architecture Click the Add Path button in the Inbound Flow section. The Add Inbound Path window appears, as shown in Figure 3:2. Figure 3:2 Adding Inbound Path Window SonicWALL Security Administrator s Guide 23

35 Setting Your Network Architecture Source IP Contacting Path 1. In this section you can configure from where you accept . You can choose to Accept connections for all senders. Use of this setting can make the product an open relay. Caution SonicWALL Security strongly recommends against an open relay. Open relays can reduce the security of your network and allow malicious users to spoof your domain. Accept connections for all senders sending to the specified domains. Accept connections from the specified senders 2. Path Listens On. In this section, you can specific which IP addresses and port number the service is listening on for incoming . Listen for all IP address on this port - This is the typical setting for most environment as the service listens on the specified port using the machine s default IP address. The usual port number for incoming traffic is 25. Listen only on this IP address and port - If you have multiple IP addresses configured in this machine, you can specify which IP address and port number to listen on. 3. Destination of Path. In this section, you can specify the destination server for incoming traffic in this path. This is a proxy. Pass all to destination server - This setting configures this path to act as a proxy and relay messages to a downstream server. If the downstream server is unavailable, incoming messages will not be accepted. This is an MTA. Route using SmartHost to - This setting is the same as the above Proxy option, except that incoming messages will be accepted and queued if the downstream server is unavailable. In this instance, this path acts as a SMTP smarthost. This is an MTA. Route using SmartHost with load balancing to the following multiple destination servers - When a path is configured with this choice, messages received will be routed to multiple downstream servers as follows. If Round robin is specified, will be load-balanced by sending a portion of the flow through each of the servers specified in the text box in round-robin order. All of the servers will process all the time. If Fail over is specified, the first server listed will handle all processing under normal operation. If the first server cannot be reached, will be routed through the second server. If the second server cannot be reached, will be routed through the third server, and so on. MTA with MX record routing - This setting configures this path to route messages by standard MX (Mail Exchange) records. To use this option, your DNS server must be configured to specify the MX records of your internal mail servers that need to receive the . MTA with MX record routing (with exceptions) - This setting configures this path to route messages by standard MX (Mail Exchange) records, except for the specified domains. For the specified domains, route messages directly to the listed IP address. 24 SonicWALL Security Administrator s Guide

36 Setting Your Network Architecture Note You can specify addresses in addition to domains in this routing table. Also, hostnames can be specified instead of IP addresses. For example, if you want to route customer service s to one downstream server and the rest of the traffic to a different downstream server, you can specify something like: [email protected] mycompany.com 4. Advanced Settings internal_mailserver.mycompany.com Use this text instead of a host name in the SMTP banner - Use this text to customize the HELO banner. By default, the fully qualified domain name will be used Set the action you want to take for messages for recipients who are not listed in your LDAP server. Typically, it is a good practice to set this path to adhere to corporate settings. Enable StartTLS on this path - Check this check box if you want a secure internet connection for . If the check box is checked, SonicWALL Security uses Transport Layer Security (TLS) to provide the secure internet connection. When StartTLS is enabled, can be sent and received over a secure socket. The source and destination addresses and the entire message contents are all encrypted during transfer. Click Add to add an inbound path for this All in One server. SonicWALL Security Administrator s Guide 25

37 Setting Your Network Architecture Adding an Outbound Mail Server for All in One Architecture Click the Add button in the Outbound Flow section. The Add Outbound Path window appears, as shown in Figure 3:3. Figure 3:3 Adding an Outbound Path 1. Source IP Contacting Path. In this section, you can specify which servers within your organization can connect to this path to relay outgoing . Any source IP address is allowed to connect to this path - This setting configures this path to receive outgoing from any server. Using this option could make your server an open relay. Only these IP addresses can connect and relay - This setting configures this path to accept only from the specified IP addresses. Note You need to use this setting if you configure your SonicWALL Security installation to listen for both inbound and outbound traffic on the same IP address on port SonicWALL Security Administrator s Guide

38 Setting Your Network Architecture 2. Path Listens On. In this section, you can specify the IP addresses and port number on which this path listens for connections. Listen for all IP address on this port - This is the typical setting for most environment as the service listens on the specified port using the machine s default IP address. Listen only on this IP address and port - If you have multiple IP addresses configured in this machine, you can specify which IP address and port number to listen to. 3. Destination of Path. In this section, you can specify the destination server for outgoing traffic in this path. This is a Proxy. Pass all to destination server - Use this setting if you want this path to act as a proxy and relay messages to an upstream MTA. Enter the host name or IP address of the upstream MTA and the port on which it should be contacted. If the upstream MTA is unavailable, outgoing messages will not be accepted. This is an MTA. Route using SmartHost to - This setting is same as the Proxy option above except that outgoing messages will be accepted and queued if the upstream MTA is unavailable. This is an MTA. Route using SmartHost with load balancing to the following multiple destination servers - When a path is configured with this choice, outbound messages will be routed to multiple upstream MTAs as follows. If Round robin is specified, will be load-balanced by sending a portion of the flow through each of the MTAs specified in the text box in round-robin order. All of the MTAs will process all the time. If Fail over is specified, the first MTA listed will handle all processing under normal operation. If the first MTA cannot be reached, will be routed through the second MTA. If the second MTA cannot be reached, will be routed through the third MTA, and so on. This is an MTA. Route using MX record routing - Use this setting to configure this path to route outbound messages by standard MX (Mail Exchange) records. This is an MTA. Route using MX record routing with these exceptions - Use this setting to configure this path to route outbound messages by standard MX (Mail Exchange) records except for the specified domains. For the specified domains, route messages directly to the listed IP address. 4. Advanced Settings Use this string instead of a host name in the SMTP banner - Use this string to customize the HELO banner. By default, the fully qualified domain name will be used. SonicWALL Security Administrator s Guide 27

39 Setting Your Network Architecture Adding a Server for Split Architecture If you chose Split Architecture, you must define whether the server is the Control Center or Remote Analyzer, and then let each know about the other. 1. Go to System > Network Architecture. 2. Choose Split. Figure 3:4 Split Configuration Network Architecture Split Configuration Network Architecture 3. Click Control Center to configure the server as a Control Center or click Remote Analyzer to configure the server as a Remote Analyzer. 4. Click Apply. 28 SonicWALL Security Administrator s Guide

40 Setting Your Network Architecture Adding a Control Center To add a Control Center: 1. Click Add Server in the Control Center section of the Network Architecture window. Figure 3:5 Adding a Control Center 2. Enter the Control Center hostname. 3. If feasible, use the default port number. If not, enter a new Control Center Server Address Port Number. 4. Click Add. SonicWALL Security Administrator s Guide 29

41 Setting Your Network Architecture Adding a Remote Analyzer You must add one or more Remote Analyzers to a Split Configuration. Remote Analyzers can process inbound messages or outbound messages or both. 1. Click the Add Server button in the Inbound Remote Analyzer or Outbound Remote Analyzer section based on your need. Figure 3:6 Adding a Remote Analyzer 30 SonicWALL Security Administrator s Guide

42 Setting Your Network Architecture 2. Figure 3:7 displays. Enter the Remote Analyzer s hostname or IP address. Figure 3:7 Adding a Remote Analyzer Server 3. Enter the Remote Analyzer Server Address Port number. 4. If your network requires SSL, check the Requires SSL check box. 5. Click the Add button. Note If there is a high volume of network traffic, it might take some time before the new Remote Analyzer is displayed in the System>Network Architecture window. Any changes you make at the Control Center are propagated to the Remote Analyzers you just added. You can monitor their status on the Reports page as well. Configuring Inbound Flow for a Remote Analyzer While logged into the Control Center, Click the Add Path button next to the Inbound Remote Analyzer. An Add Inbound Path window appears. Follow the instructions in Adding an Inbound Mail Server for All in One Architecture on page 22. Configuring Outbound Flow for a Remote Analyzer While logged into the Control Center, Click the Add Path button next to the Outbound Remote Analyzer. An Add Outbound Path window appears. Follow the instructions in Adding an Outbound Mail Server for All in One Architecture on page 26. Make sure that the Control Center can connect and relay messages through this path - step 1 in the Add Outbound Path dialog. SonicWALL Security Administrator s Guide 31

43 Setting Your Network Architecture Configuring Remote Analyzers to Communicate with Control Centers After you have set up the Control Center, configure each Remote Analyzer so that it can communicate with its Control Center. 1. Log in to each server set up as a Remote Analyzer and go to Network Architecture. 2. Click the Add button to identify from which Control Center this Remote Analyzer will accept instructions. Figure 3:8 Adding the Control Server to a Remote Analyzer 3. An Add Control Center screen appears. Enter the hostname of your Control Center. If your Control Center is a cluster, you must add each individual hostname as a valid Control Center. Figure 3:9 Adding Control Center to a Remote Analyzer Note If your Control Center is a cluster, add each individual hostname as a valid Control Center by repeating steps 2-3. All other configuration options for the Remote Analyzer are managed by the Control Center. 32 SonicWALL Security Administrator s Guide

44 Deleting a Remote Analyzer from a Split Configuration Setting Your Network Architecture Before deleting a Remote Analyzer, ensure there are no messages in the queue for quarantine as follows: 1. Stop SMTP traffic to the Remote Analyzer by turning off the SonicWALL Security Service. Click Control Panel>Administrative Tools>Services>MlfASG Software> Stop. 2. After a few minutes, view the last entry in the mfe log on the Remote Analyzer log. 3. View the mfe log in the Control Center logs directory to ensure the last entry in the mfe log for the Remote Analyzer is there: this can take a few moments. Turn off the ability of the associated server to send mail to this Remote Analyzer, and/or point the associated server to another installed and configured Remote Analyzer. Testing the Mail Servers Click the Test Mail Servers button. SonicWALL Security displays a window that indicates either a successful test or an unsuccessful test. Note It takes 15 seconds for SonicWALL Security to refresh its settings. If the first test fails, try the test again. Figure 3:10 Test Mail Servers Results SonicWALL Security Administrator s Guide 33

45 Setting Your Network Architecture Changing from an All in One Configuration to a Split Configuration Configure MTA Address Rewriting There are only two situations that warrant changing your configuration: You are a current SonicWALL Security customer running All in One architecture and want to upgrade to a Split Network configuration. You are a new customer and have incorrectly configured for All in One architecture and you want to configure for Split Network, or vice versa. Click the Configure MTA button to specify several parameters for the MTA. You can limit the number of inbound and outbound connections that SonicWALL Security will accept. You can also restrict messages based on message characteristics such as message size and number of recipients. You can also specify how the MTA will handle the case where it is unable to deliver a message right away. It will retry delivery on the interval specified in the Retry interval drop-down menu, and it will stop trying and bounce the message after the length of time specified in the Bounce after drop-down menu. Use this dialog to rewrite addresses for inbound or outbound s. These operations affect only the envelope (the RFC 2821 fields): the headers are not affected in any way. For inbound , the To field (the RCPT TO field) is rewritten. For outbound , the From field (the MAIL FROM field) is rewritten. 34 SonicWALL Security Administrator s Guide

46 LDAP Configuration LDAP Configuration SonicWALL Security uses Lightweight Directory Access Protocol (LDAP) to integrate with your organization s environment. LDAP is an Internet protocol that programs use to look up users contact information from a server. As users and distribution lists are defined in your mail server, this information is automatically reflected in SonicWALL Security in real time. Many enterprise network use directory servers like Active Directory or Lotus Domino to manage user information. These directory servers support LDAP and SonicWALL Security can automatically get user information from these directories using the LDAP. You can run SonicWALL Security without access to an LDAP server as well. If your organization does not use a directory server, users cannot access their Junk Boxes, and all inbound is managed by the message-management settings defined by the administrator. SonicWALL Security uses the following data from your mail environment. Login Name and Password: When a user attempts to log into the SonicWALL Security server, their login name and password are verified against the mail server via LDAP authentication. Therefore, changes made to the user names and passwords are automatically uploaded to SonicWALL Security in real time. If your organization allows users to have multiple aliases, SonicWALL Security ensures any individual settings defined for the user extends to all the user s aliases. This means that junk sent to those aliases aggregates into the same folder. groups or distribution lists in your organization are imported into SonicWALL Security. You can manage the settings for the distribution list in the same way as a user s settings. LDAP groups allow you to assign roles to user groups and set spam-blocking options for user groups. Configuring LDAP Use the LDAP Configuration screen to configure SonicWALL Security for username and password authentication for all employees in the enterprise. Note You must complete the LDAP configuration screen to get the complete list of users who are allowed to login to their Junk Box. If a user does not appear in the User list in the User & Group screen, their is filtered, but they cannot view their personal Junk Box or change default message management settings. Enter the server information and login information so that connection to the LDAP server can be tested. 1. Check the Configure LDAP check box to enable per-user access and management check box to enable users to log into their Junk Box and change various settings. These settings are limited according to the preferences you set in the User Management pane. See the SonicWALL Security Administration Guide User View Setup in Chapter 6 for details. SonicWALL Security Administrator s Guide 35

47 LDAP Configuration 2. Enter the following information about your LDAP server: Server Name: The IP address or DNS name of your LDAP server. (Configuration checklist parameter M) Port: The TCP port running the LDAP service. The default LDAP port is 389. (Configuration checklist parameter N) SSL Connection: Check this box if your server requires a secured connection. Type of LDAP Server: Choose the appropriate type of LDAP server from the list. Allow LDAP referals: Having this option unchecked will disable LDAP referrals and speed up logins. You may choose this option if your organization has multiple LDAP servers in which LDAP server can delegate parts of a request for information to other LDAP servers which might have more information. LDAP page size: Set the maximum page size to be queried Usermap frequency: Set the number of minutes between refreshes of the list of users on the system Figure 3:11 System > LDAP Configuration 3. MDetermine the Login options for your LDAP server. 4. Anonymous Bind Login Name and Password: Enter a username and password for a regular user on the network. This typically does not have to be a network administrator. 36 SonicWALL Security Administrator s Guide

48 LDAP Configuration Note Some LDAP servers allow anybody to get a list of valid addresses out of them. This state of allowing full access to anybody who asks is called Anonymous Bind. In contrast to Anonymous Bind, most LDAP servers such as Microsoft's Active Directory require a valid username/password in order to get the list of valid addresses. (Configuration checklist parameter O and P) 5. Click the Test LDAP query button. A successful test indicates a simple connection was made to the LDAP server. If you are using anonymous bind access, be aware that even if the connection is successful, anonymous bind privileges might not be high enough to retrieve the data required by SonicWALL Security. 6. (Optional) Click the Show LDAP Query Panel button to configure advanced LDAP settings. See LDAP Query Panel below. 7. Click Apply Changes. SonicWALL Security Administrator s Guide 37

49 LDAP Configuration LDAP Query Panel To access the LDAP Query Panel settings window, click the Show LDAP Query Panel button in the LDAP Configuration window. Note SonicWALL Security does not require you to configure LDAP query information settings for most installations. Figure 3:12 LDAP Query panel. To configure advanced LDAP settings for users: 1. Enter values for the following fields: Directory node to begin search: The node of the LDAP directory to start a search for users. (Configuration checklist parameter Q). Filter: The LDAP filter used to retrieve users from the directory. User login name attribute: the LDAP attribute that corresponds to the user ID. alias attribute: The LDAP attribute that corresponds to aliases. 2. Click the Test Group Query button to verify that the configuration is correct. 3. Click the Auto-fill User Fields button to have SonicWALL Security automatically complete the remainder of this form. 38 SonicWALL Security Administrator s Guide

50 LDAP Configuration To configure LDAP Settings for Groups: 1. Enter values for the following fields: Directory node to begin search: The node of the LDAP directory to start a search for users. (Configuration checklist parameter Q). For information on how to discover your organization s primary directory node, see, LDAP. Filter: the LDAP filter used to retrieve groups from the directory. Group name attribute: the LDAP attribute that corresponds to group names. Group members attribute: the LDAP attribute that corresponds to group members. User member attribute: the LDAP attribute that specifies attribute inside each user's entry in LDAP that lists the groups or mailing lists that this user is a member of. 2. Click the Apply Changes button. Note Be aware that if you have a lot of user mailboxes, applying these changes could take a several minutes. Advanced LDAP Settings On some LDAP servers, such as Lotus Domino, some valid addresses do not appear in LDAP. This panel provides two methods of managing such addresses. This panel provides a way to add additional mappings from one domain to another. For example, a mapping could be added that would ensure s addressed to [email protected] are sent to [email protected]. It also provides a way of substituting single characters in addresses. For example, a substitution could be created that would replace all the spaces to the left of the "@" sign in an address with a "-". In this example, addressed to Leopold [email protected] would be sent to Leopold- [email protected]. Note This feature does not make changes to your LDAP system or rewrite any addresses; it makes changes to the way SonicWALL Security interprets certain addresses. To access the Advanced LDAP Settings, click the Advanced LDAP Settings button in the LDAP Configuration window. Figure 3:13 Advanced LDAP Settings To configure the advanced LDAP settings panel: 1. Click the Add LDAP Mappings button. SonicWALL Security Administrator s Guide 39

51 Default Message Management Settings 2. From the first drop-down list, choose one of the following: a. domain is - choose this to add additional mappings from one domain to another. If replace with is chosen from the second drop-down menu, then the domain is replaced. If also add is chosen from the second drop-down menu, then when first domain is found, the second domain is added to the list of valid domains. b. left hand side character is to add character substitution mappings. If replace with is chosen from the second drop-down menu, then the character is replaced in all characters to the left of the "@" sign in the address. If also add is chosen from the second drop-down menu, then a second address is added to the list of valid addresses. 3. Click the Add Mapping button. Default Message Management Settings The Default Message Settings window enables the administrator to set default settings for users messages, as shown in Figure 3:14 Figure 3:14 System > Default Message Management Settings The Default Message Settings window allows you to choose default settings for messages that contain spam, phishing, virus, and policy management issues. 1. Choose the Number of Junk Box days from the drop-down list. Set the enterprise-wide policy for the number of days messages will remain in the Junk Box before being automatically deleted. The maximum number of days is 180. This can be adjusted for an individual user by an administrator or the user, if you allow it (See Configuring the User View Setup on page 68.) 2. Choose the number of items to display in the Message Center from the drop-down list. 40 SonicWALL Security Administrator s Guide

52 Default Message Management Settings 3. Review the four check box options that allow the user to define conditions for tagging messages incoming to their inbox. Each of the tags below will be prefixed to the subject line of the message. To tag unjunked messages, check the Tag unjunked messages with this text added to the subject line checkbox, and input word(s) to be used for tagging. To tag messages which were considered as junk but will be delivered because the sender s domain is on the user s Allow list, check the Tag messages considered junk, but delivered because sender/domain/list is in Allowed list with the text added to the subject line checkbox, and input word(s) to be used for tagging. To tag messages which were considered as junk but will be delivered because of a Policy action in effect, check the Tag messages considered junk, but delivered because of a Policy action with the text added to the subject line checkbox, and input word(s) to be used for tagging. To tag all those messages that are processed by Security 6.0 Server for testing, check Tag all messages processed by Security for initial deployment testing with this text added to the subject line checkbox, and input word(s) to be used for tagging. 4. Click the click here links to manage spam, virus, phishing, and policy. 5. Click the Apply Changes button. SonicWALL Security Administrator s Guide 41

53 Junk Box Summary Junk Box Summary SonicWALL Security sends an message to users listing all the messages that have been placed in their Junk Box. The Junk Box Summary includes: Good vs Junk count (organization) Number of blocked messages (per user) Users can unjunk items listed in the Junk Box Summary by clicking links in the . When unjunking there is an option not to add a sender to the Allowed list. Figure 3:15 System > Junk Box Summary To manage the Junk Box summary: 1. Choose Frequency of Summaries from the drop-down box. 2. Choose the dates and times to receive notification. Individual users can override these settings. 3. Choose whether to include in message summary All Junk Messages or Likely Junk Only (hide definite junk). 4. Choose Language of summary s from the drop-down list. 5. Choose a plain or graphics rich summary. 6. If a delegate has been assigned to manage an user s Junk Box, select the summary for that user to be sent to the assigned delegate. 42 SonicWALL Security Administrator s Guide

54 Junk Box Summary 7. Select to send summary only to users in LDAP. Sent From The message summary can come from the individual user or another address which you enter here. Be aware that if summaries are sent because the address doesn t exist, the message summary message will bounce as well. 8. Select the name to be displayed in end user s client for the summary s. 9. Subject Enter the subject line for the Junk Box Summary URL for User View This text box is filled in automatically based on your server configuration and is included in the Junk Box Summary . Clicking on the link will allow users to unjunk messages. Test the link if you make any changes to ensure connectivity. If you have multiple SonicWALL Security deployments, enter the virtual hostname here. Test this Link Users unjunk items in the Junk Box summary by clicking links in the . To test the URL, click Test this Link. If the test fails, check that the URL is correct. (Installation checklist parameters B, C, D) 11. Click the Apply Changes button. SonicWALL Security Administrator s Guide 43

55 User View Setup User View Setup Using these screens, the administrator can configure whether and how the end users of the SonicWALL Security server access the system and what capabilities of the system are exposed to the end users. To set up the user view: 1. Select one or more http settings: To enable http, select Enable http access on port checkbox and enter the port number in the field. The default port for http is 80. To enable https (SSL) access, select Enable https (SSL) access on port: checkbox and enter the port number in the field. The default port for https is 443. Click the Redirect access from http to https checkbox if you always want the users to connect through HTTPS. Figure 3:16 System > User View Setup Page 2. Check the Login enabled check box to allow users to access their junk boxes. This allows users to log into SonicWALL Security and have access to their per-user Junk Box. If you disable this, mail will still be analyzed and quarantined, but users will not have access to their Junk Box. It makes SonicWALL Security operate in a manner that is not visible to the user. 44 SonicWALL Security Administrator s Guide

56 User View Setup 3. Click Full user control over Rules and Collaboration to force users to adhere to the aggressiveness settings configured by the administrator in Rules and Collaboration. They can set their individual settings more aggressively, but cannot change settings to any less aggressive than the one that the administrator has set for the organization. 4. Check the Reports check box to allow users to view SonicWALL Security reports. Enabling reports allows users to view the Inbound Messages Processed Report, the Outbound Messages Processed Report, and the Junk Breakdown Report. Users cannot configure any reports. 5. Click the Settings check box to enable users to view their spam aggressiveness settings. 6. Click the Spam management check box to enable users to customize the actions SonicWALL Security takes on their junk . (Not all settings can be customized.) 7. Determine user download settings. Check the Show download icon to users to allow users to download Profilers and SonicWALL Security Desktop. Check the Allow Outlook Profiler download checkbox to allow users to download the Outlook Profiler. Check the Allow Lotus Notes Profiler download checkbox to allow users to download the Outlook Profiler. Check the Allow MailFrontier Desktop for Outlook and Outlook Express download check box to allow users to download SonicWALL Security Desktop. 8. Determine who can preview quarantined mail. Check the Users can preview their own quarantined junk mail check box to enable users to view their individual mail that is junked. 9. Check the following check boxes to enable the types of users who can preview quarantined junk mail for the entire organization. Administrators Help Desks 10. Enter an Optional login help URL. An administrator can specify a URL for any customized help web page for users to view on the Login screen. If no URL is entered, SonicWALL Security provides a default login help screen. If a URL is entered, that page is launched when the user clicks the Login Help link. 11. Click Apply Changes. SonicWALL Security Administrator s Guide 45

57 Updates Updates SonicWALL Security uses collaborative techniques as one of many tools in blocking junk messages. The collaborative database incorporates thumbprints of junked from MailFrontier Desktop and SonicWALL Security users. Your SonicWALL Security communicates with a data center hosted by SonicWALL (using the HTTP protocol) to download data used to block spam, phishing, virus and other evolving threats. This page is shown below. Figure 3:17 System > Updates Window SonicWALL Security recommends that you check for spam, phishing, and virus blocking updates at least every twenty minutes. Check the Submit unjunk thumbprints check box to submit thumbprints to the SonicWALL Security data center when users unjunk a message. Thumbprints sent from SonicWALL Security contribute to the collaborative community by improving junk-blocking accuracy. They contain absolutely no readable information. Check the Submit generic spam blocking data check box to send generic spam-blocking data to the SonicWALL Security data center to assist in customer support and to help improve spam blocking. No s, content, header information or any other uniquely identifiable information is ever sent. Web Proxy Configuration When your SonicWALL Security contacts the SonicWALL hosted data center to download data, it uses the HTTP protocol. If your organization routes HTTP traffic through a proxy, you can specify the proxy server here. You can also allow HTTP traffic from certain servers to bypass the proxy server. You may want to do this for data transferred between SonicWALL Security servers within your organization. If your organization routes HTTP traffic through a proxy which requires basic authentication, you can enter the username and password to configure SonicWALL Security to authenticate with the HTTP proxy server. 46 SonicWALL Security Administrator s Guide

58 Updates Test Connectivity to SonicWALL Security Test that communication through the web proxy is working. Click the Test Connectivity to SonicWALL button to ensure that SonicWALL Security has access to the SonicWALL hosted data center. Figure 3:18 illustrates the successful test response. Figure 3:18 Successful Connectivity Test SonicWALL Security Administrator s Guide 47

59 Monitoring and Alerts Monitoring and Alerts Use the Monitoring page to enter the addresses of administrators who receive emergency alerts and outbound quarantine notifications. If this field is left blank, notifications will not be sent. Figure 3:19 System > Monitoring The Monitoring page is also used to set up the postmaster for the MTA. If SonicWALL Security has been configured to be an MTA, enter the address to which postmaster notifications generated by the MTA should be sent. Notifications are not sent more than once every ten minutes. You can also enter the names or IP addresses of backup SMTP servers. If you are running SonicWALL Security in split mode, and you route outbound through SonicWALL Security, you must enter the IP addresses or fully-qualified domain names of any Remote Analyzers through which outbound is routed in this text box on the Control Center. To create a customized signature, enter text in the text box. This text appears at the bottom of all alerts. 48 SonicWALL Security Administrator s Guide

60 Monitoring and Alerts About Alerts Alerts in SonicWALL Security provide the following details: A summary of the alert Details that include the following: Host Name Two to three lines of description of an alert or trigger A trigger message if available A time stamp In local time In GMT If available, the alert will also include the following: Recommended action with possible suggestions on a next step An alerts configuration page General alert settings The following is an example of an alert: Figure 3:20 A Sample Alert SonicWALL Security Administrator s Guide 49

61 Monitoring and Alerts Viewing Alert History To view a history of alerts that have been sent, click the View Alert History button located in the topright corner of the page. The following window displays: Figure 3:21 Alert History 50 SonicWALL Security Administrator s Guide

62 Monitoring and Alerts Alert Suppression Schedule If you want to turn off alerts during a product maintenance window, you can suppress them for a period of time by clicking the Schedule Alert Suppression button. Figure 3:22 Alert Suppression Schedule To turn off alerts, perform the following steps: 1. Click the Schedule Alert Suppression button. The following window displays: Figure 3:23 Alert Suppression Window 2. Select a host from the drop-down menu. 3. Select the severity of the alerts that you wish to suppress. 4. Choose the date and the time (24-hour clock) you would like to suppress the alerts. 5. Enter a reason for suppressing the alert. 6. Select the Submit button. SonicWALL Security Administrator s Guide 51

63 Connection Management Connection Management The Connection Management section utilizes technology to slow or drop unwanted traffic. As part of Connection Management, SonicWALL Security rejects messages with and invalid MAIL FROM setting. Connection Management includes the following subsections: Intrusion Prevention Protection against Denial of Service (DoS) attacks, Directory Harvest Attacks (DHA), and invalid addresses. Quality of Service Enables a greater control over the server connection from suspicious clients. Intrusion Prevention To access the Intrusion Prevention portion of the Connection Management module, go to System > Connection Management. The window in Figure 3:24 displays. Figure 3:24 Intrusion Prevention 52 SonicWALL Security Administrator s Guide

64 Connection Management Directory Harvest Attack (DHA) Protection Spammers not only threaten your network with junk mail, they stage Directory Harvest Attacks (DHA) to get a list of all users in an organization s directory. DHA makes unprotected organizations vulnerable to increased attacks on their and other data systems. DHA can threaten your network in the following ways: Expose the users in your directory to spammers The people at your organization need their privacy in order to be effective. To expose them to malicious hackers puts them and the organization at significant risk from a variety of sources. Users whose addresses have been harvested are at risk. Once a malicious hacker knows their , users are at risk for being spoofed: someone can try to impersonate their identity. In addition, exposed users can be vulnerable to spoofing by others. IT departments routinely receive from people pretending to be providing upstream services, such as DNS services. Expose users to phishing Exposed users can be targeted to receive fraudulent . Some receive legitimate-appearing from banks or credit cards asking for personal or financial information. Some exposed users have been blackmailed; Reuters reported cases where users were told if they did not pay up, their computers would be infected with viruses or pornographic material. Expose your organization to Denial of Service Attacks DHA can lead to denial of service attacks because malicious hackers can send lots of information to valid addresses in an effort to overwhelm the capacity of your mail server. Expose your organization to viruses DHA provides a highly effective means of delivering virusinfected to users. Exposes users to fraudulent masquerading as good Directory Harvest Attacks can perpetuate fraudulent messages by giving malicious hackers the ability to target your users individually and by name. Figure 3:25 Directory Harvest Attack (DHA) Protection SonicWALL Security Administrator s Guide 53

65 Connection Management The following table outlines the available options for messages that are sent to addresses that are not configured in your LDAP server. Table 1 Action for messages sent to addresses not in the LDAP server Options Directory Harvest Attack (DHA) protection off. Process all messages the same (whether or not address is in LDAP) No action is taken on messages to invalid recipients. Permanently Delete All addressed to users not in the organization s directory is permanently deleted. Reject invalid addresses (Tarpitting) SMTP clients that specify invalid recipients will be tarpitted. Always store in Junk Box (regardless of spam rating). that is sent to an invalid address is stored in the Junk Box. SonicWALL Security does not process the to determine if it is spam or another form of unwanted . Consequences No directory protection. The sender does not receive notification about the they have sent. This option can lead to permanently deleting legitimate mail with a typographical error in the address. Responses to those invalid recipient commands are delayed for some time period to slow down the rate that they can attack an organization s mail system. Warning: Enabling tarpitting protection uses your system resources (CPU, memory) that may slow down your server. SonicWALL Security recommends this option to protect the confidentiality of your directory population. Table 2 Apply DHA protection to these recipient domains Options Apply to all recipient domains. SonicWALL recommends that most organizations choose Apply to all recipient domains. Apply only to the recipient domains listed below. Apply to all recipient domains except those listed below Consequences Applies DHA protection to all recipient domains. Applies DHA protection to the recipient domain(s) listed. Applies DHA protection to all recipient domains except for those listed. 54 SonicWALL Security Administrator s Guide

66 Connection Management Denial of Service (DoS) Attack Protection A Denial of Service attack aims at preventing authorized access to a system resource or the delaying of system operations and functions for legitimate users. Denial of Service attacks can threaten your network in the following ways: Bandwidth consumption The available bandwidth of a network is flooded with junkmail addressed to invalid recipients. Resource starvation The mail servers of an organization are overwhelmed trying to process the increased volume of messages coming from infected computers, which leads to the mail servers to run out of resources (CPU, memory, storage space). The Denial of Service Attack Protection adds an extra level of security to thwart an attack. To set this feature, perform the following steps: 1. Navigate to go to System > Connection Management. 2. Check the Enable DoS attack protection box. The following warning displays: Figure 3:26 Warning In order to use the Denial of Service Attack protection feature, your SonicWALL Security appliance must be the first destination for incoming messages. If you are routing mail to your Security appliance from an internal mail server or using a mail transfer agent, do not use Denial of Service Attack protection. Figure 3:27 Denial of Service (DoS) Attack Protection 3. Specify the trigger: specify the number of connections to allow from a given IP address 4. Specify an action to take: deferral for a set period of time completely block all further connections 5. Click the Apply Changes button. SonicWALL Security Administrator s Guide 55

67 Connection Management Quality of Service To access the Quality of Service portion of the Connection Management module, go to System > Connection Management. The window in Figure 3:28 displays, directly below the Intrusion Protection section. Figure 3:28 Quality of Service 56 SonicWALL Security Administrator s Guide

68 Connection Management Throttling (Flow control) In this section you can set specific thresholds to limit the sending ability of suspicious clients by limiting offensive IP addresses. Thresholds include: one connection per hour one message per minute for the next 24 hours ten recipients per message To set the Throttling feature, perform the following steps: 1. Navigate to System > Connection Management. 2. Check the Enable throttling box. Figure 3:29 Throttling 3. Specify the trigger: specify the number of connections, messages, or the number of recipients from a given IP address specify the percentage of invalid s to recipients. This setting only applies to recipient commands 4. Specify an action to take: deferral for a set period of time completely block all further connections limit a number of connections, messages, or recipients, for a number of minutes over a range of time 5. Click the Apply Changes button. Note Some scenarios can be implemented with either Denial of Services Attack Protection or Throttling settings. You can choose to throttle mail from clients above one threshold and choose to block clients above a second threshold. SonicWALL Security Administrator s Guide 57

69 Connection Management Connections In this section you can impose a limit on the number of simultaneous inbound and outbound connections that your SonicWALL Security server can accept. Figure 3:30 Connections On the inbound path, this value limits the number of simultaneous connections external hosts can make to SonicWALL Security. On the outbound path, this value limits the number of simultaneous connections internal hosts can make to SonicWALL Security to deliver messages.when the connections limit is exceeded SonicWALL Security will send a transient failure (421 error code). Messages In this section, you can limit messages based on message characteristics such as message size and number of recipients. Figure 3:31 Messages SonicWALL Security will return a transient failure (4xx error code) if too many recipients are received in a message and a permanent failure (5xx error code) if the message size limit is exceeded. Note For limiting message size, SonicWALL Security depends on the SMTP client to specify the message size in the ESMTP transaction. 58 SonicWALL Security Administrator s Guide

70 Connection Management Manually Edit IP Address List To access this portion of the Connection Management module, go to System > Connection Management. The window in Figure 3:32 displays, directly below the Quality of Service section. Use this window to manage the list of IP addresses you want to allow, defer, block, and throttle. When an IP address is added to the Allowed list, Security will continue to check for spam and phishing attacks in messages from that IP address. However, messages from IP addresses in the Allowed list will not be blocked, deferred, or throttled even when the IP address is affected by connection management rules that would do so. To stop checking for spam and phishing attacks in messages from a certain IP address, you can configure a policy. See Configuring a Policy Filter for Inbound on page Figure 3:32 Manually Edit IP Address List When the SMTP server receives a connection from an IP address on a blocked list, it will respond with a "554 No SMTP service here" error and reject the TCP/IP connection. In the case of a connection from a deferred IP address, the transient message is Service not available, connection deferred. and a connection from a list of throttled addresses, Service not available, too many connections due to throttling. SonicWALL Security Administrator s Guide 59

71 Backup/Restore Settings Backup/Restore Settings On the System > Backup/Restore page, the administrator can decide what and how SonicWALL Security will backup and restore collected data. Note It is not necessary to perform either of these functions. Executing these functions depends on the needs of your organization. Figure 3:33 System > Backup/Restore Setting 60 SonicWALL Security Administrator s Guide

72 Backup/Restore Settings Manage Backup In the Manage Backups section, the administrator can select from the following backup configurations: Settings -- Select this setting for backing up your user settings, such as user profiles. SonicWALL recommends that at minimum, you back up your settings, since this data loss would require a complete re-configuration of your settings. Junk Box -- Select this backup setting to enable a snapshot of your Junk box for future recovery. Enabling this backup setting requires sufficient disk space and requires 30 to 60 minutes to complete the backup snapshot. Archive -- Select this backup setting to enable a backing up the archive. This setting backs up all messages that have been archived on this server's file system. It does not back up messages that have been archived to an external SMTP server. Reports Data -- Select this backup setting to enable a snapshot of your reports data. This backup setting is the least critical of the three backup settings. Reports data does not include critical information for system recovery. Manage Restores In the Manage Restore section, the administrator can restore data from a snapshot file, from the following restore configurations: The administrator can select either to restore the data from a snapshot file from the SonicWALL Security server or to upload a snapshot from the local hard drive. Note A snapshot is saved on the computer work station and not on the SonicWALL Security appliance. The administrator can select the snapshot files by checking the boxes of what is to be restored. From the three selections of Settings, Junk box, and Reports data, the administrator has the flexibility to choose options suitable for system recovery or system management. SonicWALL Security Administrator s Guide 61

73 Host Configuration Host Configuration You can use this page to make changes to the server on which SonicWALL Security is installed. Figure 3:34 System > Host Configuration Changing the Hostname If you want to change the hostname of this server, enter the new fully-qualified hostname in the Hostname field and click the Apply Changes button. Note The system will perform a reboot upon a host name change and clicking the Apply Change button. Changing the hostname will cause a number of changes to be made to SonicWALL Security settings, configuration files, and will rename some of the directories in the SonicWALL Security installation and data directories. If you are running the SonicWALL Security appliance in split mode, you must also make changes to the hostname on the other servers. If you rename a Remote Analyzer, you must log in to the Control Center and click the System > Network Architecture page. Then remove the old Remote Analyzer hostname from any of the Control Centers with which it is associated, and add the new Remote Analyzer hostname. If you rename a Control Center, you must login to the Remote Analyzers and click the System > Network Architecture page. Then remove the old Control Center hostname and add the new one. 62 SonicWALL Security Administrator s Guide

74 Configuring Advanced Settings Networking To configure network settings, such as the IP address, use the Networking panel. If DHCP (Dynamic Host Configuration Protocol) is chosen, all the necessary settings will be automatically found from the network DHCP server. If static IP settings are chosen, additional information must be entered in the remaining fields. The More Settings panel allows you to change the date and time of the host machine, restart all the SonicWALL Security services, or reboot the host machine. Configuring Advanced Settings The Advanced Settings window enables you to configure logging levels, customize the SMTP banner, specify LDAP page size, and other advanced features including reinitialize to factory settings and download system/log files. Warning The Advanced page contains tested values that work well in most configurations. Changing these values can adversely affect performance. The following settings may be configured: 1. Log Level: Use this setting to change the log level for SonicWALL Security. By default, logging is enabled at level 3. You can set event logging from level 1, for maximum logging, to level 6, for minimum logging. Log files roll over at different sizes, or don't roll over at all. Different log files have a maximum of more or less than five revisions available at one time. Note Do not adjust the log level unless you are troubleshooting a specific problem. 2. Customize the SMTP banner. Use this setting to customize the SMTP banner. When remote SMTP servers contact SonicWALL Security to send through it, they see an SMTP header that identifies the server with whom they are communicating as a SonicWALL Security server. Some companies might want to hide this information and present their own custom SMTP banner header information. Be sure to use valid characters and syntax for an SMTP header. 3. Replace SonicWALL in Received: headers: Use this setting to replace the name in the Received: header. If you do not want to have the SonicWALL Security name in the Received headers when sending good downstream to your servers, use this field to specify another value. SonicWALL Security Administrator s Guide 63

75 Configuring Advanced Settings 4. LDAP Page Size: use this setting to change the LDAP size. Many LDAP servers, such as Active Directory, specify the maximum page size to query. If SonicWALL Security exceeds this page size, it can cause performance problems both on the LDAP server and on SonicWALL Security. Figure 3:35 System > Advanced Settings 5. Large Junk Box mode limit: (in megabytes): Use this setting to determine how to view the Junk Box. This setting does not affect the per-user Junk Box view. In the Admin Junk Box Web interface, if the Junk Box reaches a large size, SonicWALL Security presents a different view that makes more sense for large volumes of information. For example, it does not load the entire quarantine into RAM so that you can sort by column, but it does allow a more powerful search mechanism inside any one day of the quarantine. Depending on your preferences, you may want this cutoff to be lower so your Junk Box has much higher performance, or you might like the cutoff higher so you get the other small Junk Box view all the time. The default value is 5MB. 6. Click the Test Connectivity to reports database button to verify that you can access the Reports database. See the Reports and Monitoring chapter in this guide for more information on accessing and customizing reports. 7. Usermap frequency (in minutes): Use this setting to change the usermap frequency. A Usermap is a local cache of the LDAP server containing the list of aliases per user. Usermap frequency is the interval between refreshes of the list of users on SonicWALL Security. This does not affect user's ability to log on, because that is always a real-time reflection of the LDAP directory. This setting applies to the list of aliases and lists of members of groups. In most cases, 64 SonicWALL Security Administrator s Guide

76 Configuring Advanced Settings this setting is only increased to lower the load on your LDAP server. Depending on your other SonicWALL Security settings, accessing the user list once every 24 hours is acceptable and results in less load on the LDAP server. 8. DNS timeout for Sender ID: Enter the number of seconds to search for the DNS record of the sender. If SonicWALL Security cannot find the DNS record in the number of seconds you specify, it times out and does not return the DNS record of the sender. The default value is two seconds. You can set this value from 1 to 30 seconds. For more information about SPF, see About Sender ID and SPF on page Permit users to add members of their own domain to their Allowed Lists: Use this check box to enables users to add people within your domain to their Allowed List. For example, if you work at example.com and check this check box, all users at example.com can be added to your Allowed list. As a result, their messages to internal users are not filtered by SonicWALL Security. You can either add people manually or SonicWALL Security automatically adds each person to whom users send . The default setting is On. 10. Data in the reports database will be removed when older than: Enter the number of days of data that you want to preserve for reporting information. Lowering this number means less disk space will be used, but you will not have report data older than the number of days specified. The default value is 366 days. If your organization's volume is very high, you may want to consider reducing this number. 11. Save a copy of every that enters your organization: When archiving is enabled, folders containing the entire contents of every are created in the logs directory of each SonicWALL Security server that analyzes traffic. 12. Save a copy of every that leaves your organization: When archiving is enabled, folders containing the entire contents of every are created in the logs directory of each SonicWALL Security server that analyzes traffic. 13. Save will automatically be deleted when older than: Enter the number of days of data that you want to preserve for archiving purposes. Lowering this number means less disk space will be used, but archives older than the number of days specified will not be available. The default value is 10 days. If your organization's volume is very high, you may want to consider reducing this number. SonicWALL Security Administrator s Guide 65

77 Configuring Advanced Settings Reinitialize to Factory Settings An administrator may consider this advanced feature to set the server back to factory default values. Selecting Reinitialize to Factory Settings will wipe out all the user s configured data and reconfigure the SonicWALL Security server with another IP. On selecting the button, a warning dialogue box appears on the screen, prompting the user to confirm or cancel the reinitialize process. Figure 3:36 Reinitialize to Factory Settings Upload Patch When a new SonicWALL Security software update becomes available, the SonicWALL Security appliance automatically downloads the update and alerts the administrator via that it is available. Upon logging in to the SonicWALL Security administrative interface, a pop-up screen displays, prompting the administrator to either click to update now or wait to update later. In some instances an administrator may want or need to apply a patch manually. For example, if an administrator has multiple servers running in split configuration mode (Remote Analyzer/Control Center configuration), updates must be applied manually. Note Updating servers in split mode configuration requires that the Remote Analyzer be updated first and the Control Center updated last. To apply a patch manually, perform the following steps: 1. Log into with your user name and password. 2. In the left-hand side navigation menu, click Download Center to access the list of available software. 3. Download the build onto your client machine (not to the Security appliance). 4. In SonicWALL Security, navigate to the System > Advanced page. In the Upload Patch section, click the Browse button to locate the executable file located in your client machine. Figure 3:37 Upload Patch 5. Click the Apply Patch button to upload and install the signed installer executable. 66 SonicWALL Security Administrator s Guide

78 Configuring Advanced Settings Download System/Log Files In the event that the server s hard drive is corrupted, the administrator can download the log files to archive the log files on the system. Figure 3:38 Download System/Log Files SonicWALL Security Administrator s Guide 67

79 Configuring Advanced Settings 68 SonicWALL Security Administrator s Guide

80 CHAPTER 4 Anti-Spam Anti-Phishing Techniques Managing Spam SonicWALL Security uses multiple methods of detecting spam and other unwanted . These include using specific Allowed and Blocked lists of people, domains, and mailing lists; patterns created by studying what other users mark as junk mail, and the ability to enable third-party blocked lists. You can define multiple methods of identifying spam for your organization; users can specify their individual preferences to a lesser extent. In addition, SonicWALL Security provides updated lists and collaborative thumbprints to aid in identifying spam and junk messages. Spam Identification SonicWALL Security uses a multi-prong approach to identifying spam and other unwanted . It is useful to understand the general operation so you can build your lists appropriately. When an comes in, the sender of the is checked against the various allowed and blocked lists first, starting with the corporate list, then the recipient s list, and finally the SonicWALL Securityprovided lists. If a specific sender is on the corporate blocked list but that same sender is on a user s allowed list, the message is blocked, as the corporate settings are a higher priority than a user s. Note that the more detailed lists take precedence over the more general lists. For example, if a message is received from [email protected] and your organization s Blocked list includes domain.com but a user s Allowed list contains the specific address [email protected], the message is not blocked because the sender s full address is in an Allowed list. After all the lists are checked, if the message has not been identified as junk based on the Allowed and Blocked lists, SonicWALL Security analyzes messages headers and contents, and use collaborative thumbprinting to block that contains junk. SonicWALL Security Administrator s Guide 69

81 Spam Identification Managing Spam through Default Settings Use the Default Spam Management window shown in Figure 4:1 to select options for dealing with spam and likely spam. The default setting for spam and likely spam will quarantine the message in the user s junk box. Figure 4:1 Anti-Spam, Anti-Phishing > Default Spam Management 70 SonicWALL Security Administrator s Guide

82 Spam Identification To manage messages marked as spam or likely spam: 1. Choose one of the following responses for messages marked as definite spam and likely spam. Table 1 Action for messages marked as Definite Spam or Likely Spam Response Definite Spam filtering off Permanently Delete Bounce Back to Sender Store in Junk Box (default setting) Send to Effect SonicWALL Security does not filter messages for spam. All messages are passed through to the recipient. The message is permanently deleted. CAUTION: If you select this option, your organization risks losing wanted . The message is returned to sender with a message indicating that it was not deliverable. The message is stored in the Junk Box. It can be unjunked by users and administrators with appropriate permissions. This option is the recommended setting. Enter the address of the person to receive this . Tag With The is tagged with a term in the subject line, for example, [JUNK] or [Possible Junk?]. Selecting this option allows the user to have control of the and can junk it if it is unwanted. 2. Check the Accept Automated Allowed List check box to accept automated lists that are created by User Profilers. User Profilers analyze your outbound traffic and automatically populate per user white lists. This helps reduce the false positives. Note If this check box is unchecked in the Corporate, Group, or User windows, User Profilers have no effect. 3. Check the Skip spam analysis for internal to exclude internal s from spam analysis. 4. Check the Allow users to delete junk to allow users to control the delete button on individual junk boxes. Caution When you go on vacation, deselect this box so that your vacation-response reply does not automatically place all recipients on your Allowed list. 5. Click Apply Changes. SonicWALL Security Administrator s Guide 71

83 Spam Identification Adding People to Allowed and Blocked Lists for the Organization You can add specific people s addresses to organization-wide Allowed or Blocked lists. Use the window displayed in Figure 4:2. If the sender-id check fails, the Allowed list entry will be ignored. Figure 4:2 Anti-Spam, Anti-Phishing > People This window displays the address of senders on the organization s Allowed or Blocked lists. The source of the address is shown in the right-hand column. If you attempt to add your own address or your organization s domain, SonicWALL Security will display a warning. Note These settings apply to the entire organization. Individual users can add or block people for their personal lists by clicking Anti-Spam Techniques > People in their SonicWALL Security user accounts. To see an individual user s lists, you must log in as that user. For more information, see Signing In as a User on page SonicWALL Security Administrator s Guide

84 Spam Identification Search To search for an address, enter all or part of the address. For example, entering sale displays as well as Add To add people to the Allowed or Blocked lists: 1. Choose the Allowed or Blocked tab. 2. Click the Add button 3. Enter one or more addresses, separated by carriage returns, to add to the chosen list. addresses are case-insensitive; SonicWALL Security converts the address to lowercase. SonicWALL Security will warn you if you attempt to add your own address or your own organization. Note You cannot put an address in both the Allowed and Blocked list simultaneously. If you add an address in one list that already exists on the other, it is removed from the first one. SonicWALL Security will ignore any entries to the Allowed list if the sender-id (SPF) check fails. For more information on SPF, see Effects of SPF on Security Behavior on page 78. Companies or Domains You can allow and block messages from entire domains. If you do business with certain domains regularly, you can add the domain to the Allowed list; SonicWALL Security allows all users from that domain to send . Similarly, if you have a domain you want to block, enter it here and all users from that domain are blocked. Note SonicWALL Security does not support adding top-level domain names such as.gov or.abc to the Allowed and Blocked lists. Add To add domains to the Allowed or Blocked lists: 1. Choose the Allowed or Blocked tab. 2. Click the Add button. 3. Enter one or more domains, separated by carriage returns. Domain names are case-insensitive and are converted to lowercase. Note A domain cannot be on both the Allowed and Blocked list at the same time. If you add a domain to one list and it already exists on the other, it is removed from the first list. SonicWALL Security Administrator s Guide 73

85 Spam Identification Mailing Lists SonicWALL Security enables you to add mailing lists, such as listserv lists, to your Allowed list, as shown in Figure 4:3. Figure 4:3 Anti-Spam, Anti-Phishing > Lists Mailing list messages are handled differently than individuals and domains because SonicWALL Security looks at the recipient s address rather than the sender s. Because many mailing list messages appear spam-like, entering mailing list addresses prevents misclassified messages. Add To add mailing lists: 1. Click the Add button 2. Enter one or more addresses, separated by carriage returns. addresses are case-insensitive; the message is converted to lowercase. 74 SonicWALL Security Administrator s Guide

86 Spam Identification Anti-Spam Aggressiveness The Anti-Spam Aggressiveness window, as shown in Figure 4:4, allows you to tailor SonicWALL Security to your organization s preferences. Configuring this window is optional. SonicWALL Security recommends using the default setting of Medium (or 3) unless you require different settings for specific types of spam blocking. Figure 4:4 Anti-Spam, Anti-Phishing > Anti-Spam Aggressiveness Configuring SMART Network Aggressiveness Settings SMART Network refers to SonicWALL Security user community. Every that is junked by an user in SMART Network is summarized in the form of thumbprints. A thumbprint is an anonymous record of the junked that contains no information about the user who received the mail or the contents of the mail. You can adjust SMART Network settings to customize the level of influence community input has on spam blocking for your organization. Updates are provided to your gateway server at defined intervals. To adjust your settings, click one of the radio buttons from Mild (1) to Strong (5). A setting of 5 indicates that you are comfortable with the collective experience of the SonicWALL Security user community, and do not want to see more . A setting of 1 or 2 indicates that want to judge more for yourself and rely less on the collective experience of SonicWALL Security's user community. SonicWALL Security Administrator s Guide 75

87 Spam Identification Configuring Adversarial Bayesian Aggressiveness Settings The Adversarial Bayesian technique refers to SonicWALL Security s statistical engine that analyzes messages for many of the spam characteristics. This is the high-level setting for the Rules portion of spam blocking and lets you choose where you want to be in the continuum of choice and volume of . This setting determines the threshold for how likely an message is to be identified as junk . Use this settings to specify how stringently SonicWALL Security evaluates messages. If you choose Mild (check box 1 or 2), you are likely to receive more questionable in your mailbox and receive less in the Junk Box. This can cause you to spend more time weeding unwanted from your personal mailbox. If you choose Medium (check box 3), you accept SonicWALL Security s spam-blocking evaluation. If you choose Strong (check box 4 or 5), SonicWALL Security rules out greater amounts of spam for you. This can create a slightly higher probability of good messages in your Junk Box. For example, in Figure 4:4 the administrator has set aggressiveness to Strong (5), to rule out greater amounts of spam. Determining Amounts and Flavors of Spam You can determine how aggressively to block particular types of spam, including sexual content, offensive language, get rich quick, gambling, and advertisements. For each of the spam flavors: Choose Mild (check box 1) to be able to view that contains terms that relate to these topics. Choose Medium (check box 2 through 4) to cause SonicWALL Security to tag this as likely junk. Choose Strong (check box 5) to make it more likely that with this content is junked. For example, in Figure 4:4, the administrator has determined that they want to receive no with sexual content by selecting Strong (5). They are less concerned about receiving advertisements, and selected Mild (1). You can also choose whether to allow users to unjunk specific flavors of spam. Authenticating the Sender s Domain via Sender ID Check the Consider Sender ID in statistical evaluation check box, as shown in Figure 4:4. 76 SonicWALL Security Administrator s Guide

88 Spam Identification About Sender ID and SPF Many senders of junk messages spoof addresses to make their appear more legitimate and compelling. When you send an message, the contains information about the domain from which the message was sent. Sender ID, sometimes called Sender Policy Framework (SPF) is a system that checks the sender s DNS records. SonicWALL Security determines whether the IP address from which the message was sent matches the purported domain. Many organizations publish their list of IP addresses that are authorized to send so that recipient s MTAs can authenticate the domain of messages that claim to be from that address. SonicWALL Security uses the following system to determine if the sender is authorized to send from the purported address: 1. Stores the IP address of the SMTP client that delivered the message, which is the Source IP address. 2. Finds the sender of the message, and stores the domain that the message claims to be from. 3. Using the Domain Name System (DNS), queries the domain for its Sender ID record, if it is published. Those records are published by many domain owners, and create a list of IP addresses that are authorized to send mail for that domain. 4. Validates that the domain authorizes the Source IP address in its SPF record. Below is a simple example: Sender ID or SPF Implementation Notes SonicWALL Security receives a message from In the message, SonicWALL Security finds From: [email protected] so it uses example.com as the domain. SonicWALL Security queries example.com for its SPF record The SPF record published at example.com lists as a system that is authorized to send mail for example.com, so SonicWALL Security gives this message an SPF = pass result. This information is taken into account by SonicWALL Security in the determination of spam. To use Sender ID or SPF effectively, SonicWALL Security must be the first-touch server. SonicWALL Security factors each message s SPF score as a portion of information used by its spam- detection engine. SonicWALL Security needs the Source IP address of the SMTP client sending messages. Thus, if your SonicWALL Security is downstream from another MTA, for example, Postfix or SendMail, this check will not provide useful information, since all of the messages will come from the IP Address of your Postfix or SendMail server. Note SonicWALL Security performance might vary if you enable Sender ID because each is placed on hold while the DNS server is being queried. SonicWALL Security Administrator s Guide 77

89 Spam Identification Effects of SPF on Security Behavior SonicWALL Security relies on SPF to help define a message as spam or likely spam. As implemented, SPF can return a soft failure or a hard failure when validating the sender s MAIL FROM field. A hard failure causes the message to be marked as likely spam even when no other test confirms it. With confirmation from another Security plug-in, the message can be marked as definite spam. A soft failure by SPF lends weight to the classification of a message as spam or likely spam, but is not enough to mark the message by itself. If the sending domain does not publish SPF records, Security does not use SPF to take any action. In cases where a certain domain is on a user s Allowed list, an SPF soft or hard failure will still prevent spam based on spoofed use of the allowed domain. Once Security determines that a domain has been spoofed in an incoming message, it disables checking of the Allowed list. Publishing Your SPF Record SonicWALL strongly recommends that you publish your SPF records to prevent spammers from spoofing your domain. When spammers spoof your domain, your domain can receive a high volume of bounced messages due to fraudulent or junk that appears to come from your domain. Implementing SPF prevents your company s branding from being diluted. For assistance in setting up your SPF records, go to To see an example of an SPF record, you can use a tool such as nslookup from your favorite shell. As an example, to query SPF records for AOL, type: nslookup -query=txt aol.com 78 SonicWALL Security Administrator s Guide

90 Spam Identification Foreign Languages You can allow, block, or enter no opinion on in foreign language character sets. If you enter No opinion, SonicWALL Security judges the content of the message based on the SonicWALL Security modules that are installed. Figure 4:5 Anti-Spam, Anti-Phishing > Foreign Languages Note Some spam messages are seen in English with a background encoded in different character sets such as Cyrillic, Baltic, or Turkish. This is done by spammers to bypass the anti-spam mechanism that only scans for words in English. In general, unless used, it is recommended to exclude these character sets. Common languages such as Spanish and German are normally not blocked. SonicWALL Security Administrator s Guide 79

91 Spam Identification Black List Services (BLS) Public and subscription-based black list services, such as the Mail Abuse Prevention System (MAPS), Real-time Blackhole List (RBL), Relay Spam Stopper (RSS), Open Relay Behavior-modification Systems (ORBS) and others, are regularly updated with domain names and IP addresses of known spammers. SonicWALL Security can be configured to query these lists and identify spam originating from any of their known spam addresses, as shown in Anti-Spam, Anti-Phishing > Black List Services on page 80. Note SonicWALL Security performance may vary if you add Black List Services because each is placed on hold while the BLS service is queried. Figure 4:6 Anti-Spam, Anti-Phishing > Black List Services Add Click Add and enter the server name of the black list service, for example list.dsbl.org. Each black list service is automatically enabled when you add it. that Arrives from Sources on the Black Lists Services Check the Treat all that arrives from sources on Black List Services as Likely Spam check box to prevent users from receiving messages from known spammers. If you check this box, SonicWALL Security displays the following message, as shown in Figure 4:7. Figure 4:7 Warning about Real-time Black List Servers 80 SonicWALL Security Administrator s Guide

92 Spam Identification Managing Spam Submissions and Probe Accounts Use the Spam Submissions page, shown in Figure 4:8, to manage that is miscategorized and to create probe accounts to collect spam and catch malicious hackers. Managing miscategorized and creating probe accounts increases the efficiency of SonicWALL Security s spam management. This page enables administrators and users to forward the following miscategorized messages to their IT groups, create probe accounts, and accept automated allowed lists to prevent spam. Figure 4:8 Anti-Spam, Anti-Phishing > Spam Submission Window SonicWALL Security Administrator s Guide 81

93 Spam Identification Managing Miscategorized Messages The following diagrams illustrate the process of junk submissions. They show how junk that was missed by SonicWALL Security (also known as false negatives) is sent to SonicWALL Security s Research Laboratory for analysis. They also show how good that was junked by the SonicWALL Security (also known as false positives) is sent to SonicWALL Security s Collaborative laboratory for analysis. Figure 4:9 Submitting missed and miscategorized messages What Happens to Miscategorized Messages The following happens when an message is miscategorized: For false negatives, SonicWALL Security adds the sender address of the junked to the user s Blocked List so that future messages from this sender are blocked. (The original sender is blacklisted for the original recipient.) For false positives, SonicWALL Security adds the addresses of good senders that were unjunked to the user s Allowed List. (The original sender is whitelisted for the original recipient.) These messages are sent to the global collaborative database. Good mail that was unjunked is analyzed to determine why it was categorized as junk. 82 SonicWALL Security Administrator s Guide

94 Spam Identification Forwarding Miscategorized to SonicWALL Security You must set up your system so that sent to the and passes through SonicWALL Security. Note The addressed to and must pass through SonicWALL Security so that it can be operated on. The same domain as the domain that is used to forward s to. Using a domain that does not route, such as fixit.please.com, is recommended. Configuring Submit-Junk and Submit-Good Accounts Mail is considered miscategorized if SonicWALL Security puts wanted (good) in the Junk Box or if SonicWALL Security delivers unwanted in the user s inbox. If a user receives a miscategorized , they can to update their personal Allowed list and Blocked list to customize their filtering effectiveness. This system is similar to the benefits of running MailFrontier Desktop in conjunction with SonicWALL Security, and clicking Junk or Unjunk messages, but does not require SonicWALL Security Desktop to be installed. The administrator can define two addresses within the appropriate configuration page in SonicWALL Security, such as [email protected]_domain.comand [email protected]_domain.com. As SonicWALL Security receives sent to these addresses, it finds the original , and appropriately updates the user s personal Allowed and Blocked list. Note Users must forward their miscategorized directly to these addresses after you define them so that SonicWALL Security can learn about miscategorized messages. Problem with Forwarding Miscategorized to SonicWALL Security for Analysis A problem can arise if the user sends an to [email protected]_domain.com, and the local mail server (Exchange, Notes, or other mail server) is authoritative for this domain, and does not forward it to SonicWALL Security. There are a few ways around this problem; the most common solution is included below as an example. To forward the missed to SonicWALL Security for analysis: 1. Add the this_is_spam and not_spam addresses as [email protected]_domain.com and [email protected]_domain.com into the SonicWALL Security Junk Submission text boxes. Note Create an A and an MX record in your internal DNS that resolves es.your_domain.com to your SonicWALL Security server's IP address. 2. Tell users to forward mail to [email protected]_domain.com or [email protected]_domain.com. The mail goes directly to the SonicWALL Security servers. SonicWALL Security Administrator s Guide 83

95 Spam Identification Probe Accounts Probe accounts are accounts that are established on the Internet for the sole purpose of collecting spam and tracking hackers. SonicWALL Security suggests that you use the name of a past employee as the name in a probe account, for example, [email protected]. Configure the Probe Account fields to cause any sent to your organization to create fictitious accounts from which mail is sent directly to SonicWALL, Inc. for analysis. Adding this junk to the set of junk messages that SonicWALL Security blocks enhances spam protection for your organization and other users. Note If you configure probe accounts, the contents of the will be sent to SonicWALL, Inc. for analysis. Managing Spam Submissions To manage spam submissions: 1. Click Anti-Spam Techniques > Spam Submissions. The Spam Submission window appears, as shown in Figure 4:8. 2. Enter an address in Submitting Missed Spam. For example, you might address all missed spam to mailto:submitmissedspam@your_domain.com. 3. Enter an address in Submitting Junked Good Mail. For example, you might address all misplaced good to mailto:submitgood@your_domain.com. 4. Establish one or more Probe Accounts. Enter the address of an account you want to use to collect junk . The address does not have to be in LDAP, but it does have to be an address that is routed to your organization and passes through SonicWALL Security. For example, you might create a probe account with the address mailto:probeaccount1@your_domain.com. Caution A probe account should NOT contain an address that is used for any purpose other than collecting junk . If you enter an address that is in use, the owner of that address will never receive another - good or junk - again, because all sent to that address will be redirected to the SonicWALL corporation s data center. 5. Click the Apply Changes button. 84 SonicWALL Security Administrator s Guide

96 Anti-Phishing Anti-Phishing SonicWALL Security s Anti-Spam Anti-Phishing module protects organizations against containing fraudulent content. There are two audiences for fraud: the consumer and enterprise users. SonicWALL Security focuses on preventing fraud that enters the enterprise via . is an entry point for malicious hackers. What is Enterprise Phishing? There are numerous types of enterprise phishing. Consumer phishers try to con users into revealing personal information such as social security numbers, bank account information, credit card numbers, and driver s license identification. This is known as identity theft. Recouping from having a phisher steal your identity can take many hours and can cost consumers many dollars. Being phished can bring your life to a virtual standstill as you contact credit card companies, banks, state agencies, and others to regain your identity. Enterprise phishers attempt to trick users into revealing the organization s confidential information. This can cost thousands of executive and legal team hours and dollars. An organization s electronicinformation life can stop abruptly if hackers deny services, disrupt , or infiltrate sensitive databases. Phishing aimed at the IT group in the organization can take the following forms: that appears to be from an enterprise service provider, such as a DNS server, can cause your organization s network to virtually disappear from the Web. Hacking into your web site can cause it to be shut down, altered, or defaced. might request passwords to highly sensitive databases, such as Human Resources or strategic marketing information. The might take the form of bogus preventive maintenance. Other information inside the organization s firewall, such as Directory Harvest Attacks (DHA) to monitor your users. Phishing can also take the form of malicious hackers spoofing your organization. is sent that appears to come from your organization can damage your community image and hurt your customers in the following ways: Spoofed can ask customers to confirm their personal information. Spoofed can ask customers to download new software releases, which are bogus and infected with viruses. Preventing Phishing Phishing harms organizations and consumers by raising the price of doing business, which raises the cost of goods and services. SonicWALL Security prevents phishing through: Adapting SonicWALL Security s spam-fighting heuristics to phishing Divergence Detection TM ensures that all contact points are legitimate. Contact points include addresses, URLs, phone numbers, and physical addresses. Sender ID or Sender Policy Framework (SPF) a system that attempts to validate that a message is from the domain from which it purports to be. Sender ID authenticates that the domain from which the sender s message reports matches one of the IP addresses published by that domain. SonicWALL Security factors Sender ID pass or fail into its junk algorithm. For more information about Sender ID, see Authenticating the Sender s Domain via Sender ID on page 76. SonicWALL Security Administrator s Guide 85

97 Preventing Phishing Configuring Phishing Protection To configure SonicWALL Security to screen for phishing: 1. Navigate to the Anti-Phishing page. The window in Figure 4:10 appears. Figure 4:10 Anti-Spam, Anti-Phishing > Anti-Phishing 2. Click the radio button to choose which action to take for messages that contain Phishing. 3. Click the radio button to choose which action to take for messages that contain Likely Phishing. 4. Check the Allow users to unjunk phishing messages checkbox if you want to allow users to unjunk fraudulent messages. 5. Enter one or more addresses of people designated to receive proactive phishing alerts. 6. To send copies of fraudulent messages to a person or people designated to deal with them, enter the recipients addresses in the Send copies of s containing phishing attacks to the following addresses text box. 7. Click Apply Changes. 86 SonicWALL Security Administrator s Guide

98 Preventing Phishing Use SonicWALL Security s Community to Alert Others Phishing is continuously evolving and adapting to weaknesses in the organization s network. Malicious hackers use any known weakness to infiltrate the corporate firewall. SonicWALL Security has tuned and enhanced their spam-management techniques to prevent phishing. SonicWALL Security also collects incidences of phishing and summarizes the addresses, text, phone numbers, and domains of phishing perpetrators in a database, which stores the thumbprints of the phishing message. Report Phishing and Other Enterprise Fraud to SonicWALL Security SonicWALL Security alerts organizations to phishing attacks. SonicWALL Security needs you to report fraudulent messages to mailto:[email protected]. Reporting phishing enables SonicWALL Security to alert other users to the phishing attacks you experienced. SonicWALL Security Administrator s Guide 87

99 Preventing Phishing 88 SonicWALL Security Administrator s Guide

100 CHAPTER 5 Anti-Virus Techniques SonicWALL Security s Anti-Virus modules enable you to protect your organization from inbound -borne viruses and prevent your employees from sending viruses with outbound . Once SonicWALL Security has identified the message or attachment that contains a virus or likely contains a virus, you choose how to manage the virus-infected . Virus-protection is available as optional modules and can be enabled by the SonicWALL Security administrator for the entire organization. How Virus Checking Works The Anti-Virus modules use virus-detection engines to scan messages and attachments for viruses, Trojan horses, worms and other types of malicious content. The virus-detection engines receive periodic updates to keep them current with the latest definitions of viruses. SonicWALL Security supports McAfee and Kaspersky virus-detection engines. You can choose to buy and deploy one or both virusdetection engines supported by SonicWALL Security. Messages determined to be dangerous by McAfee or Kaspersky engine are categorized as Viruses. When any one of the virus-detection engines is activated, you also get the benefit of SonicWALL Security s Time Zero Virus Technology. This technology uses heuristic statistical methodology and virus outbreak responsive techniques to determine the probability that a message contains a virus. If the probability meets certain levels, the message is categorized as Likely Virus. This technology complements virus-detection engines and enabling this technology provides the greatest protection for time zero viruses, the first hours that a virus is released, when major anti-virus companies have not yet modified their virus definitions to catch it. SonicWALL Security Administrator s Guide 89

101 . How Virus Checking Works Preventing Viruses and Likely Viruses in To configure anti-virus protection: 1. Navigate to the Anti-Virus Techniques page. The Anti-Virus window appears, as shown in Figure 5:1. Figure 5:1 Anti-Virus Techniques If you have licensed more than one virus-detection engines, both will work in tandem. Licensed virus-detection engines can be used on both inbound and outbound paths. 90 SonicWALL Security Administrator s Guide

102 How Virus Checking Works The following table explains the options for dealing with -bourne Viruses or Likely Viruses, as shown in Figure 5:1, and the consequences of these actions Table 1 Actions to take when a Virus or Likely Virus is Detected Action Consequence Additional Information Virus Filtering Off Permanently Delete Bounce Back to Sender Store in Junk Box (default setting) Send To Tag with [VIRUS] or [LIKELY VIRUS] SonicWALL Security passes this through to users without stripping the viruses or likely viruses. SonicWALL Security permanently deletes this message. SonicWALL Security bounces back to the sender with the virus removed. SonicWALL Security stores in the Junk Box. If you click the Allow Users to Unjunk button, users can unjunk the message. SonicWALL Security sends to a specified address SonicWALL Security delivers to the addressee and strips the virus. The subject is tagged with [VIRUS], or [LIKELY VIRUS] or another administratorspecified term. This choice provides no screening for viruses or likely viruses. This is a secure option for the enterprise because the virus or likely virus is permanently deleted. However, neither the receiver nor the sender knows that the message contained a virus or likely virus, and once the message is deleted, you cannot retrieve it. The sender is notified of the virus or likely virus in the . Mail is stored in Junk Box. If you click the Allow Users To Unjunk button users can receive the message, with the virus or likely virus removed. NOTE: SonicWALL Security recommends this option because you can retrieve the message after SonicWALL Security strips the virus. Option allows messages to be copied to a specific address You can enter another tag in the text box or use the default [VIRUS] or [LIKELY VIRUS]. 2. Determine how to treat messages that contain Viruses or Likely Viruses and select the action to take. 3. Click the Allow Unjunk checkbox to allow users to view messages with viruses from Junk Box. Note SonicWALL Security removes the virus from the message before the user retrieves it. 4. Click Apply Changes. SonicWALL Security Administrator s Guide 91

103 How Virus Checking Works Checking for Updates To determine how frequently you want to check for virus definition updates: 1. Click System > Updates. The Updates window, shown in Figure 5:2, appears. Figure 5:2 System > Updates 2. Choose a time interval from the dropdown list adjacent to Check for Spam, Phishing, and Virus Blocking Updates. You can choose every 5 minutes to every 2 hours. 3. Click the Apply Changes button 92 SonicWALL Security Administrator s Guide

104 Zombie and Spyware Protection Zombie and Spyware Protection It is possible that unauthorized software is running on a computer within your organization sending out junk - spam, phishing, virus or other unauthorized content - messages. This scenario could happen if your organization was subjected to a virus attack called Trojans or a user downloaded something from the web and unauthorized software got installed without user s knowledge. These unauthorized software programs that send out malicious content are called Zombies or Spyware. SonicWALL Security's Zombie and Spyware Protection technology brings the same high standard of threat protection available on the inbound path to messages leaving your organization through the outbound path. To enable Zombie and Spyware Protection, navigate to the Anti-Virus Techniques page, click on the Outbound tab and check the box Enable Zombie and Spyware Protection. Figure 5:3 Enable Zombie and Spyware Protection. SonicWALL Security Administrator s Guide 93

105 Zombie and Spyware Protection Table 2 Actions to Enable Zombie and Spyware Protection Action Action for messages identified as Definite Viruses leaving your organization: Action for messages identified by SonicWALL s Time Zero Virus Technology as Likely Viruses leaving your organization: Enable Zombie and Spyware Protection to block spam, phishing attacks, and virus zombies and to alert administrators immediately when a zombie has infected your organization: Description Select one of the following settings: Definite Virus filtering off (deliver message to users) Virus filtering is disabled and messages are delivered to users without stripping the viruses or likely viruses. Permanently delete The message is permanently deleted. Bounce back to sender The message is sent back to the sender with the virus removed. Store in Junk box (recommended for most configurations) Identified messages that contain viruses are stripped of the virus attachment and stored in the Junk Box. If you click the Allow Users to Unjunk button, users can receive the message with the virus or likely virus removed. Send to Enter a designated address. SonicWALL's Time Zero Virus Technology uses a combination of Predictive and Responsive techniques to identify messages with a possible virus. This technology is most useful when a virus first appears and before a virus signature is available to identify, stop and clean the virus. Select one of the following settings: Likely Virus filtering off (deliver message to users) Virus filtering is disabled and messages are delivered to users without stripping the viruses or likely viruses. Permanently delete The message is permanently deleted. Bounce back to sender The message is sent back to the sender with the virus removed. Store in Junk box (recommended for most configurations) Identified messages that contain viruses are stored in the Junk Box. If you click the Allow Users to Unjunk button, users can receive the message with the virus or likely virus removed. Send to Enter a designated address. This feature is not enabled by default. Select this checkbox to enable Zombie and Spyware Protection. Once the Zombie and Spyware Protection is selected, the fields in the three sections below become active. 94 SonicWALL Security Administrator s Guide

106 Zombie and Spyware Protection Action Monitoring for Zombie and Spyware Activity: Actions to take when s are sent by Zombies: Specify senders that will not trigger alerts or actions: Description These settings do not take any action other than alerting the administrator of a potential zombie infection. Select any of the check boxes to send and alert to the administrator if: is sent from an address not in the LDAP within the last hour. More than (select a number) messages are identified as possible threats within the last hour. More than (select a number) messages are sent by one user within an hour. These settings can affect flow leaving your organization. Choose actions for messages leaving your organization that are identified as a threat and also to choose to activate/deactivate Outbound Safe Mode. Outbound Safe Mode, when enabled, blocks all s with potentially dangerous attachments from leaving your organization. Outbound Safe Mode, when enabled, minimizes the possibility of new virus outbreaks spreading through your outbound traffic. This setting is most useful when a virus first appears and before a virus signature is available to identify, stop and clean the virus. Enter addresses in this box you want exempt from Zombie Protection. (This list might include any addresses that are not in LDAP and addresses that are expected to send a lot of messages.) SonicWALL Security Administrator s Guide 95

107 Zombie and Spyware Protection 96 SonicWALL Security Administrator s Guide

108 CHAPTER 6 Auditing SonicWALL Security s Auditing module enables the user to monitor all s, both inbound and outbound, that pass through SonicWALL Security. This allows the user to monitor where s have filtered into or locate the destination of a particular . Auditing The Auditing window can track the path of any message that passes through SonicWALL Security. In the Auditing window is a search display that the administrator uses to search inbound or outbound s, using the following parameters: Search: Select day: Recipient s address: Show containing: Show in locations: Select One day or Over many days. Select day is displayed when the One day button is selected. Today is displayed with the option to navigate to the date previous or day after. This is displayed when the Over many days button is selected. The field is left blank to insert key words you are searching for in the subject, to, or from headings. Specifies the location of where the search takes place. More than one location can be selected simultaneously. Note If your SonicWALL Security appliances are configured in split mode, you may see a delay in the auditing data, due to the time it takes to move the data from the Remote Analyzer to the Control Center. SonicWALL Security Administrator s Guide 97

109 Auditing Searching Inbound and Outbound s Inbound s processed by SonicWALL Security are those that originate from outside of your organization including the total number of junk messages and good messages. Below the search section, as in Figure 6:1, a list of s is displayed with the following information: the recipient of the where the is located the subject heading of the the sender of the the date of the from the header Figure 6:1 Inbound s Outbound s processed by SonicWALL Security are those that come from the recipients of your organization. This includes both junk s and good s. 98 SonicWALL Security Administrator s Guide

110 Configure Auditing Configure Auditing The Configure Auditing window as shown in Figure 6:2 allows you to tailor SonicWALL Security to your organization s preferences for auditing s. Configuration in this window is optional. SonicWALL Security sets the default in the on positions with a default of 30 days for keeping auditing files. Figure 6:2 Configure Auditing Window To turn on Configure Auditing, perform the following steps: 1. Navigate to the Auditing module. 2. Click the Configure Auditing button located in the upper-left corner of the Auditing page. 3. Select the radio button(s) in the On position for the following: Auditing for inbound Auditing for outbound Index auditing files per address 4. Select the length of time from the drop-down list to audit messages. Time ranges from one day to seven years. 5. Click the Apply button. SonicWALL Security Administrator s Guide 99

111 Message Audit Message Audit SonicWALL Security enables you to diagnose why an failed through the Message Audit window. To activate the window, click on the desired address which is displayed in the inbound or outbound tab. SonicWALL Security displays the message audit as shown in Figure 6:3. Figure 6:3 Message Audit When the message audit window is open, data is displayed about the actions of the , such as the IP address of the computer that sent the , and also the details about the itself, such as the subject heading and message size. The following tables below list the message actions and message details with their descriptions. Table 1 Arrived into gateway from: Direction: Arrival notes: Audit trails: Message Actions Shows the IP address from the computer that sent the . The date and time are taken from the header. The is either inbound or outbound. Additional information about the arrival of the , e.g. if the arrived encrypted. Provides information on what happens to the on a per recipient basis Table 2 Message Details Subject From To Date Received Message Size Threat Category Attachment Subject title of the Sender s address Recipient s address Date and time, taken from the header Message size Identifies the threat status of the Identifies the subtype of spam the is categorized with Attachment 100 SonicWALL Security Administrator s Guide

112 CHAPTER 7 Policy & Compliance SonicWALL Security s Policy Management module enables you to write policies to filter messages and their contents as they enter or exit your organization. Policies can be defined only by an administrator. Typical use of policies include capturing messages that contain certain business terms, such as trademarked product names, company intellectual property and dangerous file attachments. Standard Module vs. Compliance Module The SonicWALL Security Policy & Compliance Module is divided into two subsections: 1. Standard Module This module comes activated through the Security Base License Key that deploys with SonicWALL Security and includes access to the following features in the left-hand navigation menu: Filters on page 109 Policy Groups on page Compliance Module This module is accessible through the optional purchase of a Compliance Subscription License Key. The module contains the following features in the left-hand navigation menu: Dictionaries on page 127 Approval Boxes on page 129 Encryption on page 132 Record ID Definitions on page 133 Archiving on page 135 SonicWALL Security Administrator s Guide 101

113 Basic Concepts for Policy Management Basic Concepts for Policy Management Policy Management enables you to filter based on message contents and attachments. You can filter for specific terms that you want, such as terms in your product or terms you do not want in your organization s . You manage policy by creating filters in which you specify the words to search for in content, senders, or other parts of the . After filtering for specified characteristics, you can choose from a list of actions to apply to the message and its attachments. Defining Word Usage In the context of Policy Management, a word is a series of alphabetic characters and numbers with no spaces. Table 1, Word Usage in Policy Management, on page 102 explains the punctuation rules for words. Table 1 Word Usage in Policy Management Punctuation Character Example Slash / Punctuation allowed as first or last character but not in the middle. Character value All other punctuation is used as word separators to split words. Punctuation included in this category includes the following characters: ~! # ^ * + = { } [ ] ; " < >,? \ `()" For example, X~Y is treated as two words, X and Y. Example Dollar sign $ $100 Percent sign % 100% Punctuation allowed in the middle but not as first or last character Period Character value. Example is allowed..mail or mail. are not allowed. at [email protected] Ampersand & AT&T Colon : Hyphen - xxx-yyy 102 SonicWALL Security Administrator s Guide

114 Basic Concepts for Policy Management Defining Address Matching Policy Management can do intelligent matching for addresses in the From and To/CC/BCC fields. The following table illustrates with examples how address matching works. Table 2 Intelligent Address Matching Address field Matching strings jdoe company.com [email protected] [email protected] Match Match Match [email protected] No Match Match No Match [email protected] Match No Match No Match SonicWALL Security Administrator s Guide 103

115 Basic Concepts for Policy Management Defining Intelligent Attachment Matching When you create a policy to detect attachments based on file extension, by default, SonicWALL Security will do simple matching based on the specified file extension. If the attachment has been renamed to have a different file extension, this simple matching will not detect that. To accurately detect attachments without relying on the file extension, select Intelligent Attachment Matching checkbox. For example, an executable attachment renamed to.txt extension can be matched as an executable. SonicWALL Security supports Intelligent Attachment Matching for the following file extensions listed in Table 3. Table 3 Intelligent Matching File Types File Format File Type File Extension Image Bitmap format.bmp Image FITS format.fits Image GIF format.gif Image Graphics Kernel System.gks Image IRIS rgb format.rgb Image ITC (CMU WM) format.itc Image JPEG File Interchange Format.jpg Image NIFF (Navy TIFF).nif Image PM format.pm Image PNG format.png Image Postscript format.[e]ps Image Sun Rasterfile.ras Image Targa format.tga Image TIFF format (Motorola - big endian).tif Image TIFF format (Intel - little endian).tif Image X11 Bitmap format.xbm Image XCF Gimp file structure.xcf Image Xfig format.fig Image XPM format.xpm Compressed Bzip.bz Compressed Compress.Z Compressed gzip format.gz Compressed pkzip format.zip Archive TAR (pre-posix).tar Archive TAR (POSIX).tar Executable MS-DOS, OS/2 or MS Windows.exe 104 SonicWALL Security Administrator s Guide

116 Basic Concepts for Policy Management Executable Miscellaneous Miscellaneous Miscellaneous Miscellaneous Unix elf pgp public ring pgp security ring pgp security ring pgp encrypted data Defining Disguised Text Identification SonicWALL Security provides disguised text identification to prevent users in your organization from sending or receiving messages with unwanted words with substituted, inserted, constructed, or deleted characters. Using traditional word matching or spell checking finds exact matches or known frequent misspellings, such as hte for the. Disguised text identification is as simple and intuitive as traditional word matching; and is more powerful than using regular expressions to find specific words or terms. In addition, it is far easier to use and less potentially dangerous than regular expressions. Disguised text identification provides the following types of matches: Table 4 shows a few of the multitude of variations.. Variations Table 4 Constructed characters Inserted characters Substituted characters Deleted characters Imaginative spelling Variations matched Resulting Words or Phrases \ / for V, or \./\/ for W, for example, \/\/ork at home - or _, for example, c-o-m-m-e-n-t or for a or 1 for i, for example, p@ntyhose or Sat1sfact10n wnderful opprtunty Purrfection or garunteeed suxess Note Disguised text identification might result in false positives due to unexpected conditions, and can be computationally intensive. Disguised text identification is not meant to be a spam catcher. SonicWALL Security has developed extensive heuristic statistical techniques for catching spam. Instead, this feature allows you to detect terms that are important to your organization and build policies based on them. You can use this feature to capture specific terms, for example, route incoming messages with your product s name with appropriate trademarks for your sales departments. It can also be used to filter outgoing mail. As an example, if your organization prohibits sending source code outside of the company, you could use various programming keywords as search terms and route messages with those terms to the appropriate manager. SonicWALL Security Administrator s Guide 105

117 Inbound vs. Outbound Policy Filters Inbound vs. Outbound Policy Filters Organizations can create policies to deal with both inbound and outbound messages. To create inbound policies select Inbound tab and click on Add New Filters. Policies created on the inbound path can not be shared with the outbound path and vice versa. Figure 7:1 is a view of the Inbound filters with the preconfigured filters that come already installed in SonicWALL Security. Figure 7:1 Inbound Policy To create outbound policies, select Outbound tab and click on Add New Filter. Figure 7:2 Outbound Policy See the Managing Filters section on page 116 for examples of adding inbound and outbound policies. 106 SonicWALL Security Administrator s Guide

118 Inbound vs. Outbound Policy Filters Preconfigured Inbound Filters New installations of SonicWALL Security ship with preconfigured filters. These preconfigured filters are not enabled by default. Figure 7:3 Preconfigured Inbound Filters Strip Potentially Dangerous File Attachments This filter, Strip Potentially Dangerous File Attachments, strips all attachments from the incoming messages that triggered the filter conditions. Enable and edit this rule if you want to allow some of these attachments and not others. Junk s with Attachments over 4MB This filter, Junk s with Attachments Over 4MB, stores all incoming messages over 4MB in size in the Junk Box. Strip Picture and Movie Attachments This filter, Strip Picture and Movie Attachments, strips all attachments from the incoming messages that triggered the filter conditions. Enable and edit this rule if you want to allow some of these attachments and not others. Detect Personal Financial Information (PFI) Records in Inbound Mails This filter, Detect Personal Financial Information (PFI) Records in Inbound Mails, detects personal financial information by using the Record ID definitions feature as an identifying tool looking for mails that match Social Security Number and Credit Card Number formats. Detect Personal Health Information (PHI) Records in Inbound Mails This filter, Detect Personal Health Information (PFI) Records in Inbound Mails, detects personal health information by utilizing the Medical Drug Names pre-defined dictionary as an identifying tool. Detect Corporate Financial Information in Inbound Mails This filter, Detect Corporate Financial Information in Inbound Mails, detects corporate financial information in the subject line or body of an by utilizing the Financial Terms predefined dictionary as an identifying tool. SonicWALL Security Administrator s Guide 107

119 Inbound vs. Outbound Policy Filters Preconfigured Outbound Filters New installations of SonicWALL Security ship with preconfigured filters. These preconfigured filters are not enabled by default. Figure 7:4 Preconfigured Outbound Filters Detect Personal Financial Information (PFI) Records in Outbound Mails This filter, Detect Personal Financial Information (PFI) Records in Outbound Mails, detects personal financial information by using Record ID definitions feature as an identifying tool looking for mails that match Social Security Number and Credit Card Number formats. Detect Personal Health Information (PHI) Records in Outbound Mails This filter, Detect Personal Health Information (PFI) Records in Outbound Mails, detects personal health information by utilizing the Medical Drug Names pre-defined dictionary as an identifying tool. Detect Corporate Financial Information in Outbound Mails This filter, Detect Corporate Financial Information in Outbound Mails,detects corporate financial information in the subject line or body of an by utilizing the Financial Terms predefined dictionary as an identifying tool. 108 SonicWALL Security Administrator s Guide

120 Filters Filters A Policy Filter is an action or actions you want SonicWALL Security to take on messages that meet the conditions you define. SonicWALL's Policy Management module enables you to filter as it enters or exits your organization. Policy Management is a tool only for administrators: policies cannot be managed individually and are not user-configurable. To create and manage policy filters, select Filters link under Policy Management module. Figure 7:5 Policy Filters SonicWALL Security Administrator s Guide 109

121 Filters Select the Inbound or Outbound tab to create filters for inbound or outbound messages respectively. 1. Click the Add New Filter button. The Add Filter window appears, as shown in Figure 7:6. Figure 7:6 Adding a Filter Note The fields in the window will change based on the action you choose. 2. The Enable this Filter checkbox is checked by default. Uncheck the checkbox to create rules that do not go into effect immediately. 3. Choose whether the filter matches All of the conditions or Any of the conditions Match All Any Action Causes to be filtered when any of the filter conditions apply (logical AND) Causes to be filtered when any of the conditions apply (logical OR) 110 SonicWALL Security Administrator s Guide

122 Filters 4. Choose the part of the message to filter. Figure 7:7 Select filter drop-down list The Select filter conditions are described in the table below: Select Judgement From To/Cc/Bcc Subject Body Subject or Body Subject, Body, or Attachments Message header Attachment name Attachment contents Size of message Number of recipients RFC 822 Byte Scan Definition The server s assessment of a categorized message threat Filter by the sender s name Filter by the names in the To: cc: or bcc: fields Filter by words in the subject Filter based on information in the body of the Filter based on information in the subject and body of the Filter based on information in the subject, body, and attachments of the Filter by the RFC822 information in the message header fields, which includes information including the return path, date, message ID, received from, and other information Filter attachments by name Filter based on information in the attachments Filter messages based on the size of the message Filter messages based on the number of recipients Scan the entire message SonicWALL Security Administrator s Guide 111

123 Filters 5. Choose the matching operation. The choices for matching operation vary with the message part being matched against. The following table describe the matching operations available. Type Explanation Example With Specific Word Without Specific Word With Specific Phrase Without Specific Phrase Starts With Ends With Is Is Not Equivalent to Find the whole word only Not equivalent to Find the whole word only Search for the word Mail from the subject line This is Mail will match. Search for the word Mail from the subject line This is MailFrontier will not match. Equivalent to Find complete phrase Search for the words is Mail from the subject line This is Mail will match. Not equivalent to Find complete phrase The message part being searched for should start with the search value The message part being searched for should end with the search value Only the search criteria should exist (exact match). Only the search criteria should not exist Search for the word is Mail from the subject line This is MailFrontier will not match. Search for This from the subject line This is Mail will match. Search for is Mail from the subject line This is Mail will match. Search for the word Mail from the subject line This is Mail will not match. Search for is Mail from the subject line is Mail will match. Search for the phrase is Mail from the subject line This is MailFrontier, will match. Contains Substring search Search for is Mail from the subject line This is Mail will match. Does not Contain Substring search does not match Enter the words or phrase that you want to filter in the Search Value text box. Select the appropriate check boxes. Match Case Intelligent Attachment Matching Disguised Text Identification Filters a word or words sensitive to upper and lower case. Filters attachment names, such as.exe or.zip. Filters disguised words through the sequence of its letters, for example Vi@gr@. Note Disguised Text Identification cannot be used together with Match Case and can be selected only for Body and Subject message parts. 112 SonicWALL Security Administrator s Guide

124 Filters If the Compliance Module is active, the administrator has additional filtering conditions that can be set. The Use Dictionary option of using terms from a dictionary can be selected, as well as the Use Record Match option which looks for numbers such as telephone numbers or social security numbers. 6. Click the plus sign (+) to add another layer of filtering. See Junk s with Attachments over 4MB on page 107. You can add up to 20 filters. Filters are similar to rock sifters. Each additional filter adds further screens that test for additional conditions. 7. Choose the response action from the Action drop-down list. SonicWALL Security Administrator s Guide 113

125 Filters The following table describes the different actions and the effect they have on the message. Action Log as event Permanently delete Store in Junk Box Table 5 Store in Approval Box Bounce back to sender Deliver and bounce Deliver and skip Spam and Phishing Analysis Route to Deliver and route to Tag subject with Strip all attachments Append text to message Issue notification Add X-header to message Remove X-header from message Route to IP Deliver and Route to IP Route Copy to Archive Filter Responses to Messages that Trigger Policy Alerts Effect The message is logged. No further processing in Policy management occurs (default). This option stores a log of all messages so that the administrator has a record and can analyze traffic patterns. The log is in the mfe log. NOTE: Policy management logs all messages as events regardless of the action specified. The message is permanently deleted and no further processing occurs in any SonicWALL Security module occurs. This option does not allow the user to review the and can cause good to be lost. The message is stored in the Junk Box. It can be unjunked by users and administrators with appropriate permissions. The user has the option of unjunking the . The message is stored in the Approval Box. It will not be delivered until an administrator approves it for delivery. The message is returned to sender with an optional message indicating that it was not deliverable. The message is delivered to the recipient and is bounced back to the sender with an optional message. The message is delivered without spam or phishing analysis. The message is routed to the specified address. The message can be routed to only one address. Deliver to the recipients and also route to the specified address. The message can be routed to only one address The subject of the is tagged with a the specified term. Remove all the attachments from the . The specified text is appended to the message body. Sends an notification to the recipients of the that triggered the rule. Adds an X-header to the . Removes an X-header from an . The message is routed to the specified IP address. The message can be routed to only one IP address. Deliver to the recipients and also route to the specified IP address. The message can be routed to only one IP address A copy of the message is routed to the archive. 114 SonicWALL Security Administrator s Guide

126 Filters Table 5 Filter Responses to Messages that Trigger Policy Alerts (continued) Action Encrypt Decrypt When no additional filtering is required on a message, select the and stop processing policy filters checkbox. This checkbox is automatically selected and grayed out when you have selected a terminal action.if additional actions need to be performed on the same message, select the plus sign (+) to the right. You cannot add the same action more than once to a specific filter rule. As a result, once an action has been selected, it will not be available in the drop-down list for further selection within the current filter rule. 8. Type a descriptive name in the Filter Name text box. 9. Select a policy group you want to apply this filter to. By default, All Groups will be selected and this filter will apply to all messages. 10. Click Save This Filter. Effect Message is sent to the encryption center for encryption. This action is used for outbound messages. The administrator must provide a name or IP address of SMTP server for encryption at the Policy & Compliance > Encryption page. Message is sent to the decryption center for decryption. This action is used for inbound messages. The administrator must provide a name or IP address of SMTP server for encryption at the Policy & Compliance > Encryption page. Language Support Policy management supports filtering messages based on non-english terms in the Search Value. For example, you can search for a Japanese word or phrase in the body of a message. However, SonicWALL Security does not support adding text strings to messages in languages other than English and does not support foreign language filter names. Note To view messages in Asian languages, you might need to install East Asian Language Packs on the server where you run SonicWALL Security (for Windows only). This applies to deployments using the SonicWALL Security Software Edition. SonicWALL Security Administrator s Guide 115

127 Managing Filters Managing Filters The main Policy Management UI,Figure 7:5, lists all the filters created in the system for the Inbound and Outbound path. From this view, you can Add New Filter, Change the order of filters, Edit or Delete filters. Filters that have been enabled are indicated with a green tick mark. Editing a Filter To change a filter that has been saved: 1. Click the Edit button adjacent to the filter to be changed. Figure 7:8 is an example of the Edit Filter window. Figure 7:8 Edit Filter 2. Change any of the filter conditions. 3. Click Save This Filter. Deleting a Filter To delete a filter, click the Delete button adjacent to the filter. 116 SonicWALL Security Administrator s Guide

128 Managing Filters Changing Filter Order Filters are processed in the order they appear. To change the order of the filters, use the up and down arrow icons to the left of the filters. Advanced Filtering Creating a multi-layered Filter You can create filters with multiple conditions chained together and multiple actions to be performed on the message, if the specified conditions are met. For an example, if the message is sent from NASA and the body contains the word Mars then take the following actions: Tag the subject with the term [Mars Update from NASA] and Route the message to engineering. To create a multi-layered filter: 1. Click the Add New Filter button from the Policy & Compliance > Filters > Inbound module. Figure 7:9 Add New Filter Button 2. Select All conditions to be met 3. With Specific Words operation, search for nasa.org in the message part From. 4. Select the + button to the right to add another condition SonicWALL Security Administrator s Guide 117

129 Managing Filters 5. With Specific Words operation, search for Mars in the message part Body. Enable Match Case to get an exact case match. Figure 7:10 Select, Matching and Search Values 6. Select the action Tag Subject With. Set the Tag field to [Mars Update from NASA]. Make sure and stop processing policy filters checkbox is not enabled. 7. Select the + button to the right to add another action 8. Select the action Route To and set the To field to [email protected]. Select and Stop Processing Policy Filters checkbox to stop further policy filtering on this message. 9. Select the Save This Filter button. Figure 7:11 Perform the Following Actions 118 SonicWALL Security Administrator s Guide

130 Managing Filters Configuring a Policy Filter for Outbound to Include a Company Disclaimer Message This section provides a configuration example for Policy Filters. Here is an example of how you would add a company disclaimer to the end of each outgoing message from your organization. If an is sent from anyone at sonicwall.com then take the following actions: Append text to the end of the message, This is my company disclaimer To create the outbound policy filter perform the following steps: 1. In the Security management interface, browse to the Policy & Compliance > Filters screen and click the Outbound tab. 2. Click the Add New Filter button. Figure 7:12 Add New Filter 3. Select All conditions to be met. 4. Select From in the Select drop-down list, and select contains in the Matching drop-down list. 5. In the Search Value field, type sonicwall.com. 6. To protect against internal spammers or zombies, click the plus sign icon to add another condition. 7. Select Judgement in the Select drop-down list, and select is good in the Matching drop-down list. Figure 7:13 Select, Matching, and Search Values 8. Select the action Append text to message. SonicWALL Security Administrator s Guide 119

131 Managing Filters 9. In the Message text write: This is my company disclaimer Figure 7:14 Perform the Following Actions 10. Name the filter Outbound Disclaimer 11. Select Apply to Everyone from the dropdown menu in the Apply this filter to: section. 12. Click the Save This Filter button. Figure 7:15 Filter Name 120 SonicWALL Security Administrator s Guide

132 Managing Filters Configuring a Policy Filter for Inbound This is another example of how you would filter messages sent to your organization that are not judged as spam but contain the words job application in the subject or body of the message: If an is Not judged as spam The subject or body of the contains the words job application then take the following actions: route the to [email protected] To create the inbound policy filter: 1. Select Add New Inbound Filter button. Figure 7:16 Select Add New Filter Button 2. Select All conditions to be met. 3. Judgement operation, matching is not spam. SonicWALL Security Administrator s Guide 121

133 Managing Filters 4. Select the + button to the right to add another condition. 5. With specific phrase operation, search for job application in the message part Subject or Body. Figure 7:17 Select, Matching, and Search Value 6. Select the action Route to and enter the address [email protected] in the To: field. Figure 7:18 Perform the Following Actions 7. Name the filter Resume Routing. 8. Select Apply to Everyone from the dropdown menu in the Apply this filter to: section. 9. Select the Save This Filter button. Figure 7:19 Filter Name Exclusive Actions The action named Permanently delete is an exclusive action and is terminal in nature and no further policy filtering will be possible after this action has been performed. The Stop Processing Policy Filters checkbox will be automatically enabled and grayed out if an exclusive action is selected. 122 SonicWALL Security Administrator s Guide

134 Managing Filters Parameterized Notifications SonicWALL Security supports parameterized notifications wherein you can use pre-defined parameters in the text fields for the Issue Notification action. These parameters will get substituted with corresponding values when the message is processed. You can use these parameters in either the Subject or Message Text fields of the Issue Notification action. The parameters can be used multiple times and are substituted each time they are used. Each parameter entered should start and end with % symbol. The following table lists the supported policy notification parameters and shows the value of these parameters. Table 6 Parameter %SUBJECT% %FROM% %ATTACHMENT_NAMES% %FILTER_NAME% %MATCHED_RECORDID% %MATCHED_TERM% Policy Notification Parameters Value the Subject: content from the triggering the From: content from the triggering a comma-separated list of attachment names from the triggering the name of the policy filter which took the action on the triggering the Record ID file name which has a matching pattern in the triggering the Dictionary term which matched in the triggering Figure 7:20 is an example of a parameterized notification. Figure 7:20 Parameterized Notification Filter SonicWALL Security Administrator s Guide 123

135 Policy Groups Policy Groups In some cases, it may be appropriate to associate a policy filter to a group of users rather than the entire organization. For example, you may want a policy filter to be applied to all incoming messages sent to your sales team and no one else in your organization. If you want policy filters you create to be applied to particular group of users, you first have to create policy groups from LDAP. Policy groups, once created, can be associated with either inbound or outbound policies. To manage policy groups, select Policy Groups link under Policy & Compliance module as shown in Figure 7:21. From this screen, you can manage all policy groups for your SonicWALL Security setup. Figure 7:21 Policy Groups 124 SonicWALL Security Administrator s Guide

136 Policy Groups To add a new policy group, select the Add New Group button. The window below displays. Figure 7:22 Add Group From the pull down menu, select one of three methods to locate a desired group equal to (fast) starting with (medium) containing (slow) search using the actual name search using the first few characters search using a substring of characters Once the list of group names is displayed, select the checkbox of the group you wish to add. Click on the Add Group button. To remove a group, check the group(s) to be removed and select the Remove Group button. You can view the members of a group by selecting that group and clicking on the List Group Members button. SonicWALL Security Administrator s Guide 125

137 Compliance Module If a user is present in more than one group, that user is treated to be a member of the group that is listed highest in the list. You can change group ordering, by clicking on the arrows to the left of listed groups. To change the order in which groups are listed, use the up and down arrow icons to the left of the groups. Figure 7:23 Groups For example in the above illustration, if [email protected] is listed under both SalesEngineering and Sales, the policy filter that is associated with SalesEngineering will be applied to messages for [email protected]. Compliance Module This module is accessible through the optional purchase of a Compliance Subscription License Key and enables organizations to make efforts in ensuring that complies with relevant regulations and/or corporate policies. Once the Compliance Module is activated, the network administrator has access to the new Encryption and Archiving features in addition to features such as additional filtering tools that enhance the Standard Module. Note When the Compliance Module license expires, filters that were created during the valid license period will continue to work, taking advantage of the advanced features. However, the administrator will not be able to add any new filters to use licensed features until a license to the module is obtained. 126 SonicWALL Security Administrator s Guide

138 Compliance Module Dictionaries A dictionary is a convenient collection of set of words or phrases that you can group together for use in policy filters. A dictionary can be specified as a search value in a policy filter. Dictionaries can be created or modified either manually or by importing from a file in the file system. A predefined dictionary is a group of words or phrases all belonging to a specific theme such as medical or financial terms, which can be used as a database of words that filters can look for. By default, SonicWALL Security provides two pre installed dictionaries: Financial Terms Medical Drug Names These dictionaries may be modified by clicking the edit button. Figure 7:24 Dictionaries To import a dictionary from a file on the file system, perform the following steps: 1. Click on the Import Dictionary button. 2. Choose to name a new dictionary or to replace an existing dictionary by selecting the appropriate radio button next to your selection. 3. Find the import file by browsing to the correct location. The imported file should contain one word or phrase per line and each line should be separate by <CR>. SonicWALL Security Administrator s Guide 127

139 Compliance Module 4. Click the Import button. Figure 7:25 Importing a Dictionary To manually add a dictionary, perform the following tasks: 1. Click on the Add New Dictionary button. Figure 7:26 Add a Dictionary 2. Enter a word or phrase under Dictionary Terms and click Add Term. Repeat for all the terms you want to add to the dictionary. 3. Give your dictionary a name. 4. Click Save Dictionary. You will automatically be returned to the Policy & Compliance > Dictionaries module. 128 SonicWALL Security Administrator s Guide

140 Compliance Module Approval Boxes An Approval Box is a list of stored messages that are waiting for an administrator to take action. They will not be delivered until an administrator approves them for delivery. The View Approval Box for drop-down list allows you to have two different views of Approval Boxes: the Manager view and the individual approval box view. To see a list of the Approval Boxes that have been created, select Approval Box Manager from the pulldown menu in the View box from this list. The Approval Box Manager view allows you to edit or delete existing Approval Boxes, and to create new Approval Boxes. Figure 7:27 Approval Box Manager View SonicWALL Security Administrator s Guide 129

141 Compliance Module To see the contents of a particular Approval Box, choose the desired Approval Box name from the View Approval Box for drop-down list. This page allows you to search the messages stored in that Approval Box and to take action on any of those messages. Note Only users who have administrative rights can see the contents of an approval box. See Chapter 8, "User and Group Management" for managing user rights and privileges. Figure 7:28 Individual Approval Box View for Bounces 130 SonicWALL Security Administrator s Guide

142 Compliance Module To store messages in an Approval Box, you must first create the Approval Box by clicking the Add New Approval Box button in the Summary view page. Then, go to the Policy Management > Filters page and create a policy filter that has Store in Approval Box as its Action, and choose the desired Approval Box for messages caught by that filter. Figure 7:29 Add New Approval Box 1. Enter a name for this Approval Box. This name will appear in the page that shows the list of approval boxes and in the drop-down list that allows you to select the detailed view of individual approval boxes. 2. From the Default action pull-down menu, select an action to be taken. This action will automatically be taken on the message waiting for approval if the administrator does not respond to the notification within the period of time specified. None Approve & Deliver Delete Bounce Back to Sender No action is taken. The remains in the Approval Box. The is passed to the recipient. The is deleted. The will automatically be bounced back to the sender and removed from the approval box after the specified length of time elapses. It will not be delivered to the intended recipients. 3. Enter a list of recipients in the text box. Separate multiple addresses with a carriage return. Note Make sure that the recipients you enter are users that have administrative rights to the SonicWALL Security appliance. If they do not have administrative access, they will not be able to view the approval boxes when they receive notification. SonicWALL Security Administrator s Guide 131

143 Compliance Module 4. Select a notification frequency for this approval box. Approval box notification s for this approval box will be sent according to the schedule you choose here. 5. Write the subject line for this notification. 6. Click the Apply Changes button to save your changes to this approval box notification. Encryption This section is used to configure the servers used to encrypt and decrypt messages. Once configured, you may create a policy filter for which the action is to encrypt or decrypt messages. A policy action of encrypt can be used to direct confidential outbound messages to the encryption server. A policy action of decrypt can be used to direct confidential inbound messages to the decryption server. Figure 7:30 Policy & Compliance > Compliance Module > Encryption 132 SonicWALL Security Administrator s Guide

144 Compliance Module Record ID Definitions A Record ID Definition can be used to detect specific IDs described by a series of generic patterns. This section allows the administrator to predefine a cluster or clusters of letters and numbers into logical sets of groups such as social security numbers, patient medical record numbers, or credit card numbers. When these patterns are discovered, compliance actions can be taken to ensure that the organization's privacy and security regulations are met. The filter will stop processing a message after it finds the first matching Record ID Definition. By default, SonicWALL Security provides the following Record ID Definitions pre installed: ABA Bank Routing Number Canadian Social Security Number Credit Card Number Date Phone Number Social Security Number Zip Code Figure 7:31 Policy & Compliance > Compliance Module > Record ID Definitions SonicWALL Security Administrator s Guide 133

145 Compliance Module To add a new record ID definition, perform the following steps: 1. Click the Add New Record ID Definition button. The Add Record ID Definition window displays, as shown in Figure 7:32 Figure 7:32 Add Record ID Definition 2. Name the Record ID you are creating. 3. Enter a term including correct spacing, dashes or other symbols. Use the key to set values to the sets of characters 4. Select Add Term to add the term to the Record ID. 5. Repeat adding terms for each Record ID as necessary. 134 SonicWALL Security Administrator s Guide

146 Compliance Module Archiving This section is used to configure how messages are archived. Once configured, you may create a policy filter for which the action is Route copy to archive. Messages can be archived either to a remote archive server or to a file system. Figure 7:33 Policy & Compliance > Compliance Module > Archiving To have messages archived to a remote server, click the External SMTP Server radio button, and enter the IP address of the server to which messages should be routed for archiving in the Route to Archive Address field. To have messages archived to a file system, perform the following steps: 1. Click the File System radio button. 2. Choose from the archive settings for both inbound and outbound s. 3. Select a length of time for s to be archived. 4. Click the Apply Changes button. SonicWALL Security Administrator s Guide 135

147 Compliance Module 136 SonicWALL Security Administrator s Guide

148 CHAPTER 8 User and Group Management The User and Group Management function allows you to: Manage the list of users who can log in to the SonicWALL Security Assign roles to individual users or groups of users Set spam blocking options for groups of users This chapter also describes how to assign a delegate to manage your Junk Box. For more information, see Assigning Delegates on page 148. Note To manage users and groups from within this module, you need to have configured your SonicWALL Security setup to synchronize with your organization s LDAP server. You can configure LDAP settings and queries on the System > LDAP Configuration page. Note SonicWALL Security queries your corporate LDAP server every hour to update users and groups. Changes made to some settings in this section may not be reflected immediately on SonicWALL Security, but are updated within an hour. SonicWALL Security Administrator s Guide 137

149 Working with Users Working with Users To manage users in SonicWALL Security: 1. Click the User & Group Management icon. SonicWALL Security displays the Users and Groups window, as shown in Figure 8:1. 2. Select the Users link. Figure 8:1 Users & Groups > Users From this screen, you can sign in as an user, set their message management settings to corporate default and edit their privileges in the system. Searching for Users If there are too many users to display in a window, select the search option from the drop down menu (equal, starts with, or contains), enter the search parameter in the blank field, and click Go. The search speed varies according to the search parameter. Sort Click User Name or Primary to sort the list of users by that column. Signing In as a User Administrators can sign in as any user, see their Junk Box, and change the settings for that user. In addition, you can sign in as a particular user to manage their delegates for them. 138 SonicWALL Security Administrator s Guide

150 Resetting User Message Management Setting to Default Working with Users Select one or more users and click Set Message Management to Default to restore all settings to the defaults. Be aware that this overrides all individual user preferences the user might have set. Edit User Rights Administrators can assign different privileges to different users in the system by assigning them predefined roles. To assign a role to an user, select the user and click on Edit User Rights button. See SonicWALL Security Roles on page 142 for more information. Import The administrator can add multiple non-ldap users by importing a list of names. The list is made up of the primary addresses followed by the corresponding aliases of the users. The imported file can be appended to the existing names, or overwrite them. The format of the file is tab-delimited. One may use an Excel spreadsheet to generate a user list and save it as a tab-delimited file. To import the list, click the browse button to locate the file and click Import. Export The administrator can download a tab-delimited list by clicking this button. The file generated lists multiple non-ldap users and can later be imported using the Import feature. Add The administrator can add individual non-ldap users. Fill out the Primary Address and Alias fields and click Add. Add an existing user with an alias and the user will have that alias added to them. This is not dependent on LDAP status. Note Users added in this way remain non-ldap users. Their User Rights cannot be changed. Their source will be listed as Admin. Users can edit their Junk Box setting only if the administrator sets the Junk Box setting, Enable "Single Click" viewing of messages to "Full Access" in the System > Junk Box Summary page. Remove The administrator can remove individual non-ldap users. First select a non-ldap user by using the checkbox in front of the name, then click the Remove button to delete the name from the list. SonicWALL Security Administrator s Guide 139

151 Working with Groups Working with Groups About LDAP Groups This section describes how SonicWALL Security lets you query and configure groups of users managed by an LDAP server. Most organization create LDAP groups on their Exchange server according to the group functions, for example: a group configured on their Exchange server called support represents the technical support groups in Exchange. You must first configure LDAP groups on your corporate LDAP server before configuring the rights of users and groups on SonicWALL Security in the User and Group Management screen. Figure 8:2 Users & Groups > Groups SonicWALL Security allows you to assign roles and set spam-blocking options for user groups. Though a user can be a member of multiple groups, SonicWALL Security assigns each user to the first group it finds when processing the groups. Each group can have unique settings for the aggressiveness for various spam prevention. You can configure each group to use the default settings or specify settings on a per-group basis. Updates to groups settings in this section do not get reflected immediately. The changes will be reflected the next time SonicWALL Security synchronizes itself with your corporate LDAP server. If you want to force an update, click on the Refresh From LDAP button. 140 SonicWALL Security Administrator s Guide

152 Working with Groups Add a New Group To add a new group, Click Add New Group button. The Add Group window appears, as shown in Figure 8:3 with a list of all the groups to which you can assign roles. You can also add new groups in this window. Figure 8:3 Add Group To find a group: 1. Search for the group you want by entering the name in the text box. Choose the search mechanism and search speed: equals (fast), starts with (medium), or contains (slow). Click Go to begin the search. or Removing a Group Listing Group Members Scroll through the list of groups to locate the group you want to add. 2. Click the checkbox to include the group. 3. Click Add Group. A message appears stating that the group was added successfully. 1. Click the checkbox adjacent to the group(s) to remove. 2. Click the Remove Group button. A message stating the group was successfully removed appears. 1. Click the checkbox adjacent to the group to list. 2. Click the List Group Members button. Users belonging to that group will be listed in a pop-up window. SonicWALL Security Administrator s Guide 141

153 SonicWALL Security Roles SonicWALL Security Roles Roles are a set of privileges that you can grant any individual user or group of users in the SonicWALL Security. There are five defined roles that can be assigned to any user or group. Admin: An administrator role has full rights over the system. Administrators are taken to the system status page after logging in. They can log in as any user to change individual settings and view Junk Boxes, manage the corporate Junk Box, and configure everything. Help Desk: A Help Desk role can sign in as any user in the system, change their settings and address books, or operate on the Junk Box. This role is not allowed to change any corporate-wide settings and other server configurations. Group Admin: A group administrator role is similar to the Help Desk role except that this role s privileges are limited to users for the group they are specified to administer. Group Admin role is always associated with one or more groups added to the Spam Blocking Options for Groups section. Manager: A manager role has access to only system reports. User: Using the user role, you can allow users in your organization to log in to SonicWALL Security. SonicWALL Security displays their Junk Box as the opening window. In addition, you can also allow them access to other areas such as reports, message management, and lists. Setting a LDAP Group s Role All members of a group get the role assigned to the group. To set the role of a group: 1. Click the checkbox adjacent to the group to edit. 2. Click Edit Role A window appears with the group s name and current role. 3. Click the radio button for the appropriate role that you want to assign to the group. 4. Click Apply Changes. A message appears stating that the group was changed successfully. Figure 8:4 Edit Group Role 142 SonicWALL Security Administrator s Guide

154 Setting Spam Blocking Options for LDAP Groups Setting Spam Blocking Options for LDAP Groups All members of a group get the spam blocking options assigned to the group. To set spam blocking options for an LDAP group: 1. Click the checkbox adjacent to the group that you want to edit. 2. Click the Edit Junk Blocking Options button. The Edit Spam Blocking Options for Group window appears. Figure 8:5 Edit Junk Blocking Options Note The Adhere to Corporate/Group Defaults box is checked by default. By opening this screen, you are now editing the spam blocking options for this one group. There is an Adhere to Corporate Defaults check box at the very top of each sub-page in this dialog, this check box only applies to the values on one page and for the current group only. For example, you can adhere to the corporate defaults for the two pages User View Setup and Rules and Collaboration, and uncheck the box and set custom settings for this one group for Foreign Language and then uncheck the box for and set custom settings for this group for Spam Management. To enable the specified group to have special privileges, deselect the Adhere to Corporate/Group Defaults box. SonicWALL Security Administrator s Guide 143

155 Setting Spam Blocking Options for LDAP Groups User View Setup This controls what options are available to the users in this group when they login to server using their user name and password. You can change the settings on the following items: Login Enabled enables users in this group to log into their Junk Box Allow/Block People, Companies, Lists, Foreign Languages, Rules Allows or blocks specified people, companies, foreign languages, and rules as these were configured in the user setup. Reports let users in this group look at their Spam reports Settings enables users in this group to view their settings Click the Allow the following types of user downloads from the SonicWALL Security check box to enable users in this group to preview quarantined junk mail. Click Apply. Rules and Collaborative Settings You can configure rules and collaborative settings for groups. Choose the appropriate Collaborative level for this group. You can adjust collaborative settings to customize the level of influence community input has on enterprise spam blocking. Choose the appropriate Aggressiveness level this group. For each category of spam, determine level and whether members of the group are allowed to unjunk their Junk Boxes. Click Apply Changes. 144 SonicWALL Security Administrator s Guide

156 Configuring Foreign Language for Groups You can determine the foreign language that groups can receive. Setting Spam Blocking Options for LDAP Groups Figure 8:6 Foreign Languages Select Allow All to allow all users in a group to receive in the specified language. Select Block All to block all users in a group from receiving in the specified language. Click No opinion to permit to be subject to the spam and content filtering of SonicWALL Security. Click Apply Changes. SonicWALL Security Administrator s Guide 145

157 Setting Spam Blocking Options for LDAP Groups Managing the Junk Box Summary You can manage the way in which you receive the Junk Box summary of s. Figure 8:7 Editing Junk Box Summary options for a Group To manage the Junk Box for groups: Choose the default frequency users to receive notification of junk . Choose the time of day to receive junk . Choose the day of the week to receive junk . Choose a plain or graphics rich summary. Choose if sending the junk box summary to a delegate or delegates. Click Apply Changes. 146 SonicWALL Security Administrator s Guide

158 Setting Spam Blocking Options for LDAP Groups Spam Management You can manage how groups deal with spam through the Spam Management window. Figure 8:8 Editing Spam Blocking for Groups To manage messages marked as Spam or Likely Spam for this group: Choose what you want done with messages: Spam Filtering Off passes all messages to users without filtering. Permanently Delete Bounce back to sender send the message back to the sender. Caution: in cases of self-replicating viruses that engage the sender s address book, this can inadvertently cause a denial of service to a non-malicious user. Send to you must specify an address for the recipient. Tag with label the to warn the user. The default is [JUNK]. Click Apply Changes. SonicWALL Security Administrator s Guide 147

159 Setting Spam Blocking Options for LDAP Groups Phishing Management The phishing management window gives you the option of managing phishing and likely phishing settings at a group level. Just like spam management options, it allows to you deal with phishing differently for different groups. However, unlike spam management options, these settings cannot be altered for individual users. Virus Management The virus management window gives you the option to manage virus and likely virus settings at a group level. Just like spam management options, it allows to you deal with viruses and likely viruses differently for different groups. However, unlike spam management options, these settings can not be altered for individual users. Assigning Delegates Delegates are people who have full access to your individual Junk Box. This includes the ability to change your Junk Box settings and manage the messages in your Junk Box. The most common use of delegates is for an administrative assistant to act as a delegate of the CEO of a company. The assistant frequently has access to all of the CEO's , so the assistant now would have access to the CEO's Junk Box and Junk Box settings as well. Figure 8:9 Assigning a Delegate To assign a delegate to manage your Junk Box: 1. Sign in to your individual user account; click the Sign in as any user link at the bottom of most SonicWALL Security windows and sign in with your username and password. 2. Go to Settings > Delegate. 148 SonicWALL Security Administrator s Guide

160 Setting Spam Blocking Options for LDAP Groups 3. To add a delegate, click the Add button. The Add New Delegate screen appears, as shown in Figure 8:10. Figure 8:10 Adding a Delegate 4. Enter the address of the delegate in the text box. 5. Click Go. A group of people who match the address appear. 6. Click the checkbox adjacent to the preferred delegate. 7. Click Add Delegate. To remove a delegate, click the Remove button on the Delegate window. SonicWALL Security Administrator s Guide 149

161 Setting Spam Blocking Options for LDAP Groups 150 SonicWALL Security Administrator s Guide

162 CHAPTER 9 Junk Box The Junk Box allows you to review and process messages that have been flagged as junk, virusinfected, organization policy violations, or phishing. You can unjunk or release a falsely identified message. When you or the recipient unjunks an incoming message, SonicWALL Security adds the sender of the message to the recipient s Allowed list and delivers the to the recipient. The size of the junk box can grow rapidly. By default, the messages are stored in junk box for 30 days and deleted after that. You may need to customize this setting depending on your organization s policies and storage capacity on the shared data directory for messages are stored. To change this setting, go to System > Default Message Management > Store in Junk Box and delete after and choose a value between 1 and 180 days. Messages in junk box can be quickly sorted and viewed by threat types. Messages that contain definite spam, phishing, and viruses have red asterisks (*) adjacent to them. Messages that contain likely spam, phishing, and viruses do not have any marks, as shown in Table 1, Message Threat Type, on page 152. SonicWALL Security Administrator s Guide 151

163 Junk Box - Normal Mode Table 1 Type of Message Spam (definite) Likely Spam Phishing (definite) Likely Phishing Virus (definite) Likely Virus Message Threat Type Display *Spam Spam *Phishing Phishing *Virus Virus There are two junk box views - normal mode and detailed search mode. When the size of all the messages in the junk box exceed 5MB, the application automatically switches from normal mode to detailed search mode. This size can be configured on the System > Advanced page. Junk Box - Normal Mode Figure 9:1 displays a corporate Junk Box in normal mode. Figure 9:1 Junk Box - normal mode 152 SonicWALL Security Administrator s Guide

164 Junk Box - Detailed Search Mode At the top of screen, the number of days messages will be stored in junk box will be displayed. The window also displays the all the messages that have been categorized as the selected threats. You can sort the messages displayed by clicking on the various column headings. To reduce the number of messages displayed, you can Search for messages containing specific strings in the following fields: To, Subject, or From. Search is not case sensitive. Display messages from a specific day. You can enter date formats as mm/dd/yy or mm/dd/ yyyy. Search for specific threats by selecting various threat checkboxes. For example, you can limit your search to phishing messages only by selecting the *Phishing and Likely Phishing check boxes only. Junk Box - Detailed Search Mode If the size of the junk box exceeds approximately 5MB in size, SonicWALL Security switches to the detailed search mode as shown in Figure 9:2. Figure 9:2 Junk Box - detailed search mode In this mode, you have additional search options to further reduce the number of messages that are displayed. SonicWALL Security Administrator s Guide 153

165 Outbound Messages Stored in Junk Box Outbound Messages Stored in Junk Box To display the outbound messages in junk box, click on the Outbound tab as shown in Figure 9:3. Outbound message management detects messages sent by users in your organization that contain viruses, likely viruses, and message that trigger policy alerts. Figure 9:3 Outbound Junk Box 154 SonicWALL Security Administrator s Guide

166 Working with Junk Box Messages Working with Junk Box Messages Unjunk This button is available only on the inbound junk box. Select Unjunk to forward the selected messages to the recipient and add the sender of each message to the recipient s Allowed list. Unjunking a message removes it from the Junk Box. Send Copy To Select Send Copy To to forward a copy of the messages (including attachments, if any) to the specified address. The message will still remain in the Junk Box. This button will only be available to members of administrative group and only if they are allowed to view the messages in the Junk Box. Release This button is available only on the outbound junk box. Select Release to release the selected messages from the queue and forward them to the recipients. The message will be removed from the Junk Box. Delete Deletes the selected messages. Messages are automatically deleted after a set number of days, so there is no need to do this on a regular basis. Set the number of days messages are kept in the junk box through the System > Default Message Management > Number of days to store messages in the Junk Box field. SonicWALL Security Administrator s Guide 155

167 Working with Junk Box Messages Message Details You can scroll through the messages and click the Subject field to view more information about the message in plain text. Depending on your user access set up, you might see the content of the messages. To control who is allowed to preview the content of messages, go to System > User View Setup. Figure 9:4 illustrates a junked message shown in text-view mode. Figure 9:4 Text View Mode of Blocked Message Click Raw Mode to view the header information as well as the message, as shown in Figure 9:5. Figure 9:5 Raw Mode Header and Message Details 156 SonicWALL Security Administrator s Guide

168 Managing Junk Summaries Managing Junk Summaries Both administrators and users receive Junk Box summaries listing the incoming that SonicWALL Security has classified as junk. From these messages, users can choose to view or unjunk an if the administrator has configured these permissions. Figure 9:6 displays the Junk Box summary. Figure 9:6 Junk Box Summary From the Junk Box Summary window, users can determine the language, frequency, content, and format of Junk Box summaries. To configure Junk Box Summaries: 1. Select the timing and frequency for summaries. 2. Select the language for Junk Box summaries from the Language of summary list, as shown in Figure 9:7. Figure 9:7 Languages for Junk Box Summaries SonicWALL Security Administrator s Guide 157

169 Managing Junk Summaries 158 SonicWALL Security Administrator s Guide

170 CHAPTER 10 Reports and Monitoring Monitoring SonicWALL Security SonicWALL Security allows you to view system status and data through the Reports and Monitoring module. You can view statistics for different time periods on the local system or the mail transfer agent (MTA). You can also monitor the flow of traffic passing through Security in real time. For a description of the different monitoring methods available in SonicWALL Security, see the following sections: System Status on page 160 MTA Status on page 161 Real-Time System Monitor on page 162 SonicWALL Security Administrator s Guide 159

171 Monitoring SonicWALL Security System Status The System Status window shows the status of SonicWALL Security and the status of connections with other systems that it needs to communicate with, as shown in Figure 10:1. A green check indicates the system is functioning as expected and a red X indicates it is not. Figure 10:1 Reports & Monitoring > Monitoring > System Status The lower half of the System Status window in the Control Center Status section shows system statistics, including the disk space used b the Junk Box, free disk space on the data drive, and free disk space on the install drive. 160 SonicWALL Security Administrator s Guide

172 Monitoring SonicWALL Security MTA Status The MTA status page gives details on the status of the mail transfer agent (MTA) if one or more paths have been configured to act as MTAs Figure 10:2 Reports & Monitoring > Monitoring > MTA Status. The following options are available on this screen: MTA Status One or more paths are configured to be MTAs - Will be set to Yes if one or more paths have been configured to act as MTAs; will be set to No otherwise. MlfMTA service is running - If the MTA is running as expected, this field will show a checkmark in a green circle. If the MTA is not running as expected, the field will show an X in a red circle. MTA Totals by Host If one or more paths are configured to act as MTAs, this section will provide additional information about their host. Host - This column shows the name of the host(s). Number of messages delivered in last hour - This column shows the number of messages delivered by the MTA in the last hour. Number of message recipients in all queues combined - This column shows the sum of the messages in the queues of all the MTAs. SonicWALL Security Administrator s Guide 161

173 Monitoring SonicWALL Security MTA Status on Inbound/Outbound Paths If one or more paths are configured to act as MTAs, these two sections will provide additional information about the paths. The columns and the values they represent are: Host (src/listen/dest) - This column shows the various paths you configured in the Network Architecture section. src is the source IP contacting path: the IP address of a machine that is allowed to connect to and relay through this path. listen is the IP address and port on which this path listens for connections. dest is the destination to which this path routes . Path is configured to be an MTA - This column shows whether the listed path is configured to be a proxy or an MTA. Number of message recipients in queue - This column lists the number of messages in the queue if the path is an MTA. If it is a proxy, messages are not queued and this column will indicate N/A. To see details about the messages in a queue, click the Show Details link for that queue. To see details for messages on a particular server, you must log in to SonicWALL Gateway on that server. Real-Time System Monitor The Real-Time System Monitor page provides real-time information on the flow of passing through SonicWALL Security. Figure 10:3 Reports & Monitoring > Monitoring > Real-Time System Monitor The Message Throughput History graph shows the number of s processsed by this server per second. The Message Bandwidth History graph shows the total bandwidth used for in bytes per second. The bandwidth is the sum of the sizes of all the messages passing through this SonicWALL Security server per second. 162 SonicWALL Security Administrator s Guide

174 Reporting in SonicWALL Security Reporting in SonicWALL Security SonicWALL Security provide many types of reports. All reports allow you to optionally download the data in CSV format. You can also create custom reports by specifying a time period for the data, and download the report for analysis or the report. Per-domain reports are available for custom and scheduled reports. See Generating Per-Domain Reports on page 163. SonicWALL Security also provides several reports for Managed Service Provider (MSP) related data, including the following: breakdown (custom/scheduled report only) Bandwidth (custom/scheduled report only) Good v Junk per domain (custom/scheduled report only) Note By default, SonicWALL Security retains 366 days of reporting information in the database. You can change this setting in System > Advanced > Data in reports database will be removed after field. Lowering this number means less disk space will be used, but you will not have report data older than the number of days specified. If your organization's volume is very high, you may want to consider lowering this number. For descriptions of the different report types, see the following sections: Overview Reports on page 164 Anti-Spam Reports on page 169 Anti-Phishing Reports on page 170 Anti-Virus Reports on page 170 Policy Management Reports on page 171 Compliance Reports on page 172 Directory Protection Reports on page 173 Advanced on page 174 Generating Per-Domain Reports When SonicWALL Security is being used as an server for several different organizations, you can generate reports that are specific to each domain. This is especially useful in a Managed Service Provider (MSP) environment. For example, you could generate reports that show data only for sonicwall.com or only for mailfrontier.net. Security provides a way for administrators to specify the domain for which data should be displayed. Only administrators can configure the per-domain setting. It is disabled for managers or other roles. Per-domain reporting is supported for the following seven report types: Inbound Good versus Junk Junk Breakdown Spam Caught Messages Identified as Phishing SonicWALL Security Administrator s Guide 163

175 Overview Reports Inbound Viruses Caught Inbound Policy Messages Filtered Number of Attacks Per-domain reporting is not available for dashboard reports or static reports. In per-domain reporting, sub-domains are not considered to be separate domains. For example, sent to and will all be included in reports for sonicwall.com. Overview Reports The following report types are available in the Overview Reports section of the Security management interface. See the following sections: Reports Dashboard on page 165 Return on Investment on page 167 Bandwidth Savings on page 168 Inbound Good vs Junk on page 168 Outbound Good vs Junk on page 168 Inbound vs Outbound on page 169 Top Outbound Senders on page 169 Junk Breakdown on page SonicWALL Security Administrator s Guide

176 Overview Reports Reports Dashboard SonicWALL Security displays the Dashboard window, as shown in Figure 10:4on administrator login. The Dashboard provides a lot of information about SonicWALL Security at a glance. These charts are updated hourly and display the statistics for the last 24 hours. Figure 10:4 Reports & Monitoring > Overview Reports > Dashboard Good vs Junk Displays the number of good messages versus junk messages. Junk message count includes spam, likely spam, phishing, likely phishing, viruses, likely viruses, Directory Harvest Attacks (DHA), and messages that trigger policy events. Spam Caught Displays the number of messages that are definitely spam and the number of messages that are likely spam. You can also find this information in the Spam Caught on page 169. SonicWALL Security Administrator s Guide 165

177 Overview Reports Junk Breakdown Top Spam Recipients Displays the number of junk messages broken down into the following categories: Spam Virus Phishing Policy Directory Harvest Attack (DHA) You can also find this information in Junk Breakdown on page 169. Displays the total number of spam received by the top 12 recipients in your organization in the last 24 hours. You can also find this information in Top Spam Recipients on page 169. Inbound vs Outbound Displays the number of inbound messages compared to the number of outbound messages. Top Outbound Senders Displays the number of outbound messages sent by the top 12 senders in your organization in the last 24 hours. 166 SonicWALL Security Administrator s Guide

178 Overview Reports Return on Investment SonicWALL Security provides a tool to help determine the Return on Investment (ROI) for your organization s investment in SonicWALL Security. You can customize this tool to reflect your organization s costs of doing business. Figure 10:5 Reports & Monitoring > Overview Reports > Return on Investment You can determine your organization s return on investment on a daily, weekly, or monthly basis from using the SonicWALL Security product. ROI numbers are computed from a formula and data accumulated by SonicWALL Security s mlfupdater and the usermap.xml file is input into the formula. SonicWALL Security Administrator s Guide 167

179 Overview Reports Determining the ROI for your Organization To determine the savings from preventing unwanted , click the Change Assumptions button to enter figures that reflect your organization. An input window appears with default values, as shown in Figure 10:6. To change the values so that they match your organization s experience: 1. Enter the appropriate values for your organization for salary, number of users, and other factors that contribute to the cost of dealing with unwanted . Figure 10:6 Enter Your Own ROI Values 2. Click the Recalculate Report button after you enter your values; a revised ROI report appears. Bandwidth Savings The Bandwidth Savings report displays the number of megabytes of bandwidth that SonicWALL Security saves your organization. SonicWALL Security lowers your organization's network costs through the following actions: Removing the high volume of junk messages that go through your network. Quarantining junk messages in the Junk Box. Deleting junk messages before they enter your network. Inbound Good vs Junk This report displays the total number of inbound messages processed by SonicWALL Security along with the total number of junk messages and good messages. Outbound Good vs Junk This report displays the total number of outbound messages processed by SonicWALL Security along with the total number of junk messages and good messages. 168 SonicWALL Security Administrator s Guide

180 Anti-Spam Reports Inbound vs Outbound the number of inbound and outbound messages processes by SonicWALL Security. This report is available only if outbound module is licensed. Top Outbound Senders the number of outbound messages sent by the top 12 senders in your organization. This report is available only if outbound module is licensed. Junk Breakdown This report gives a percentage and numeric breakdown of the various categories of junk received, including Spam, Likely Spam, Viruses, Likely Viruses, Phishing, Likely Phishing, Policy events, and Directory Harvest Attacks (DHA). Anti-Spam Reports SonicWALL Security provides the following anti-spam reports: Spam vs Likely Spam Top Spam Origination Domains Top Spam Recipients SonicWALL Security Desktop Statistics Spam Caught This report displays the total number and percentage breakdown of spam and likely spam messages. Top Spam Domains This report displays the alleged domains that sent your organization the most spam s during the time period you select. Note Most spam messages use spoofed addresses, hence the domains listed in this report may not be the actual originators of the spam. Top Spam Recipients This report displays the users in your organization who receive the most spam. SonicWALL Security Administrator s Guide 169

181 Anti-Phishing Reports Anti-Phishing Reports SonicWALL Security provides the following Anti-Phishing report: Phishing Messages Phishing Messages This report lists the total number messages identified as phishing. Anti-Virus Reports If you have licensed the Anti-Virus module, you can view the number of viruses detected by the SonicWALL Security and the names of the most prevalent viruses detected. Inbound Viruses Caught This report lists the number of viruses detected by SonicWALL Security in the inbound traffiic. Top Inbound Viruses This report lists the names of viruses detected by SonicWALL Security in the inbound traffic. Outbound Viruses Caught This report lists the number of viruses detected by SonicWALL Security in the outbound traffiic. Top Outbound Viruses This report lists the names of viruses detected by SonicWALL Security in the outbound traffic. 170 SonicWALL Security Administrator s Guide

182 Policy Management Reports Policy Management Reports If you have created policy filters in SonicWALL Security to manage traffic, the following policy reports provides statistics on messages that triggered the policy filters. Inbound Policies Filtered This report lists the total number of inbound messages that SonicWALL Security has filtered based on policies that you have configured. Top Inbound Policies This report lists the inbound policies by name that were triggered by inbound traffic. Outbound Policies Filtered This report lists the total number of outbound messages that SonicWALL Security has filtered based on policies that you have configured. Top Outbound Policies This report lists the outbound policies by name that were triggered by outbound traffic. SonicWALL Security Administrator s Guide 171

183 Compliance Reports Compliance Reports The set of Compliance Reports are accessible upon licensing of the Compliance Module. Inbound Messages Decrypted This report lists the total number of inbound messages decrypted. The report can be viewed on a daily, weekly, or monthly basis. Inbound Messages Archived This report lists the total number of inbound messages archived. The report can be viewed on a daily, weekly, or monthly basis. Top Inbound Approval Boxes This report lists the top inbound approval boxes by name. The report lists the approval boxes with data viewed on a daily, monthly, or yearly basis. Outbound Messages Encrypted This report lists the total number of outbound messages encrypted. The report can be viewed on a daily, weekly, or monthly basis. Outbound Messages Archived This report lists the total number of outbound messages archived. The report can be viewed on a daily, weekly, or monthly basis. Top Outbound Approval Boxes This report lists the top outbound approval boxes by name. The report lists the approval boxes with data on a daily, weekly, or monthly basis. 172 SonicWALL Security Administrator s Guide

184 Directory Protection Reports Directory Protection Reports SonicWALL Security provides protection against directory attacks. Following directory protection reports are available to give more information on the directory attacks your organization is subjected to: Number of DHA Attacks Top DHA Domains Number of DHA Attacks This report lists the total number of incoming messages that had incorrect addresses. Top DHA Domains This report lists the alleged domains from which the most frequent Directory Harvest Attacks (DHA) originate. Note Most junk messages use spoofed addresses, hence the domains listed in this report may not be the actual originators of the message. SonicWALL Security Administrator s Guide 173

185 Advanced Advanced Scheduled Reports SonicWALL Security allows you to schedule delivery of reports. You can choose the type of report, a time span the data covers, the list of recipients, etc. Data in scheduled reports is displayed in the time zone of the server on which SonicWALL Security stores data (either an All in One or a Control Center), just like the reports in the Reports & Monitoring section of the UI. Scheduled report s are sent according to the time zone on that computer as well. Figure 10:7 Add Scheduled Report Dialog To schedule delivery of a report: 1. Select the type of report from the Which Report drop-down list. 2. Select the frequency of the report from the drop-down list. 3. Select the time of day at which you would like to receive the report . This will be in the time zone of the server on which SonicWALL Security stores data (either an All in One or a Control Center), just like the reports in the Reports & Monitoring section of the user interface. 4. Select the day of the week on which you would like to receive the report Select the language in which you would like to receive the report SonicWALL Security Administrator s Guide

186 Advanced 6. Select the time span the report will cover. For example, suppose the report frequency is 3 Days, the time span selected is 7 Days, and the report is sent at 10 AM every day. A report sent on April 24th at 10 AM will cover roughly the time period starting April 21 at 10 AM and ending April 24 at 10 AM. 7. Select the time period by which you want to see results listed. This is the unit of time to use in the bar graph. For example, if Hour is chosen, a bar line will be shown for each hour in the specified timespan. 8. Specify the name of the sender of report s. This is a human-readable name that will appear in your mail client as the sender of the report . This does not need to be a real name. Examples: Charles Nelson Really, My Daily Scheduled Report, SonicWALL Security Administrator, Joe Bloggs Please use only 7-bit ASCII text. 9. Specify the address from which this report is sent. 10. Enter a list of recipients in the text box. Separate multiple addresses with a comma. 11. Enter a name for this scheduled report. This name will appear in the page that shows the list of scheduled reports. It will also be the subject line for the message when the scheduled report is sent. SonicWALL Security Administrator s Guide 175

187 Advanced Custom Reports SonicWALL Security allows you to customize reports. You can choose the type of report, a range of dates for the data, or a number of hours for the data. You can also the reports to another user. Figure 10:8 Custom Report Window To customize reports: 1. Select the type of report from the Report Name drop-down list. 2. Select the Start and End Dates from the Date Range. 3. Select Hourly, Daily, or Monthly from the Breakdown drop-down list. You can select a period of up to 48 hours for hourly reports. 4. Select either the Display or the to radio button. To run a report now, select Display and click the Generate This Report link. To a report, select to and enter the recipients addresses in the text box. Separate each address with a comma. You can optionally enter a subject in the subject text box. Note The Custom Reports page displays the generated report in a new window. If you have configured a popup blocker for your web browser, it may interfere with displaying the window with the data. Configure your browser to allow popup windows from your organization's SonicWALL Security site. 176 SonicWALL Security Administrator s Guide

188 Advanced Configuring a Custom Report for Inbound Good versus Junk This section provides a configuation sample for Custom Reports. Here is an example of how you would create a specific report and have it delivered to an address. Figure 10:9 Custom Report for Inbound Good versus Junk To create a Custom Report for Inbound Good vs Junk , perform the following steps: 1. Select the Inbound Good vs Junk report from the Report Name drop-down list. 2. Select the Start and End Dates from the Date Range. 3. Select Hourly, Daily, or Monthly from the Breakdown drop-down list. You can select a period of up to 48 hours for hourly reports. 4. Select either the to radio button and enter a valid address where the report will be delivered to. SonicWALL Security Administrator s Guide 177

189 Advanced 5. Enter the name and address from where the reports are sent from. 6. Enter text that will show in the subject heading of the Click Generate This Report. Figure 10:10Generated Report for Inbound Good versus Junk 178 SonicWALL Security Administrator s Guide

190 Appendix A SonicWALL Security TCP Port Utilization The SonicWALL Security uses a variety of TCP ports that it uses to communicate with other network services. Each of these ports needs special attention if your organization filters TCP traffic. Note Generally, DMZ traffic is heavily filtered by multiple firewalls. Ensure that all the inbound and outbound ports SonicWALL Security requires are open for SonicWALL Security to communicate. Inbound TCP Traffic SMTP (configurable port, usually 25) SonicWALL Security is an SMTP proxy server. It receives to be analyzed for characteristics of spam on SMTP port 25. HTTP (configurable port, usually 80) or HTTPS, port 443 SonicWALL Security hosts a Web server, HTTP port 80, which is used to administer SonicWALL Security s Web interface. In addition, users log in to this Web server to view their personal Junk Box and configure their anti-junk settings. Outbound TCP Traffic HTTP (port 80) SonicWALL Security server installed in your organization communicates with SonicWALL Security Anti-Spam Lab s data center via HTTP port 80. SonicWALL Security Anti-Spam Data Center is available on the Internet. HTTP requests are made via port 80 to the data center requesting anti-spam updates. If an update is available, the HTTP response returns it. LDAP (configurable port, usually port 389) or LDAPS, (configurable port 636) SonicWALL Security server installed in your datacenter communicates with a LDAP server inside your organization on TCP port 389 or 636. SonicWALL Security Administrator s Guide 179

191 Split Configuration TCP Port Utilization DNS, port 53 SonicWALL Security needs to communicate with DNS server to look up information if it is configured to check for senders SPF records. Port 53 is the default port used for DNS queries. SMTP (configurable port, usually 25)If SonicWALL Security determines an message is not spam, it needs to be delivered to the next mail server in your SMTP mail flow. SonicWALL Security sends these messages via SMTP port 25 Split Configuration TCP Port Utilization Here are some additional changes that you must make if you are running Split Architecture. Port 2599 SMTP configurable (Remote Analyzer to Control Center, bad mail routing) SonicWALL Security Remote Analyzer communicates with Control Center for routing quarantine through port Port 80 HTTP or port 443 HTTPS configurable (Control Center to Remote Analyzer communication) Control center keeps all Remote Analyzers up to date with latest configuration information by communicating via port 80 or 443. Figure A:1 illustrates these ports and protocols used between components of SonicWALL Security and other parts of the network. 180 SonicWALL Security Administrator s Guide

192 Split Configuration TCP Port Utilization Figure A:1 Ports and Protocols used in SonicWALL Security Connections SonicWALL Security Administrator s Guide 181

193 Split Configuration TCP Port Utilization 182 SonicWALL Security Administrator s Guide

194 Appendix B Command Line Interface Introduction To provide flexibility to our customers, the SonicWALL Security (SonicWALL ES) includes a command-line interface (CLI). The SonicWALL ES CLI can make it easier to setup new SonicWALL appliances and do repetitive tasks. However, it requires a strong familiarity with using a command-line interface and SonicWALL ES. We recommend caution when using this tool. Note The CLI can not replace the GUI in all its functionality. The CLI is meant for initial configuration, automating repetitive tasks, and for debugging purposes. Note The CLI is installed only on the Security appliances. The CLI can not be used on the software version of Security. Refer to the SonicWALL Security Administrator Guide to assign CLI permission to users. This chapter describes how to log into the command line interface (CLI) and how to execute commands in a script format. SonicWALL Security Administrator s Guide 183

195 Introduction Logging into the CLI To access the CLI, you will need to SSH into the appliance and log in. Follow these steps: Note SSH access is enabled by default on the Security appliance. However, it can be disabled. If SSH is disabled, the CLI will not be available. Although the CLI is not available if SSH is disabled, it is still accessible via direct console. 1. Open a SSH client. 2. Input the IP address of your SonicWALL Security appliance: 3. At the first login: login as snwlcli. 4. Use proper administrator credentials to login. The credentials are the same as for the standard GUI on the Security appliance. 5. Perform any of the commands described in Using the Command Line Interface on page To exit from the SonicWALL ES CLI, enter the following command: SNWLCLI> quit Scripting The following example shows a standard script. The example logs into the CLI, runs the tsr command, and exits the CLI, and records all output to a file. Refer to this example to script CLI apis: (echo -e 'admin\npassword'; sleep 1; echo tsr; sleep 2;exit;sleep 1) ssh snwlcli@ [ > outputfile] Substitute admin, password with your own id and password, with your own host address, and outputfile with the target file you wish to record the tsr report in. 184 SonicWALL Security Administrator s Guide

196 Introduction Using the Command Line Interface This section describes how to use the command line interface. It describes each CLI command, detailing its syntax and arguments. The commands are listed in alphabetic order. There are two types of commands: executable and system variables. Calling a system variable by itself will have the CLI return the current value of the variable. To update a variable, call it followed with a proper value. Some executable commands take an argument, but most do not. cleanupdcdatabase SNWLCLI> cleanupdcdatabase This command will restart the appliance and delete the following: PluginDefault/collab/thumbprint.db (the Updater services will download the thumbprint data from the datacenter and import it into the database.) PluginDefault /collab/data/*.tld PluginDefault/crbl/crbl.db PluginDefault /crbl/data/*.crbl Arguments: none Defaults: none Type: Executable clearperusercache SNWLCLI> clearperusercache <directory name> This function will clear the peruser cache for a given quarantine directory. If no parameter is provided, it will clear all of the peruser caches under quarantine. Arguments: <directory name>: Name of the directory to be cleared of its peruser cache. Defaults: <directory name>: quarantine directory Type: Executable configurehttps SNWLCLI> configurehttps <on port <generic selfsign domain> off> This function configures the https protocol. Use this command to place the Web interface on a different port. Arguments: <port>: Three digit port HTTPS will use. <domain>: Domain name HTTPS will use instead of generic. Defaults: none Type: Executable SonicWALL Security Administrator s Guide 185

197 Introduction createreportdb SNWLCLI> createreportdb Run this command to create a new, empty database. The start and stop of the operation will be logged to MlfMfelmportSetup.log, along with how long it took. Arguments: none Defaults: none Type: Executable date SNWLCLI> date This variable displays the date on an appliance. Arguments: none Defaults: none Type: System Variable Related Commands: time deletebookmarks SNWLCLI> deletebookmarks Run this command to delete all report bookmarks. Arguments: none Defaults: none Type: Executable deletelastnotifiedfiles SNWLCLI> deletelastnotifiedfiles This command will delete the lastnotified.xml and lastnotified_race.xml files. Use this command to solve issues related to junk mail notification not being sent out. This command will not force all notification s to be resent. Arguments: none Defaults: none Type: Executable 186 SonicWALL Security Administrator s Guide

198 Introduction deletereportdb SNWLCLI> deletereportdb Run this command to delete the whole report database. Arguments: none Defaults: none Type: Executable dig SNWLCLI> dig <name> <type> SNWLCLI> dig <-h> This is the standard dig command from the bind-tools package. Use this command to troubleshoot DNS related issues such as: Connectivity to DNS server Outbound s being queued Arguments: <-h>: brief summary of the dig command s arguments and options. Defaults: none Type: Executable dns SNWLCLI> dns [--nameserver <ip>]... [--search <domain>]... This variable controls the DNS configuration settings on an appliance. Called with no arguments it will return the current configuration. Arguments: <ip>: IP address to be assigned to the server <domain>: Domain name to be searched for Defaults: <ip>: current configuration <domain>: current configuration Type: System Variable SonicWALL Security Administrator s Guide 187

199 Introduction esdu SNWLCLI> esdu <directory name> This function returns the disk usage of directories related to Security. Specific directories that can be called include: logs, reports, quarantine, and peruser. Arguments: <directory name>: Applicable directories are: logs, reports, quarantine, peruser. Defaults: none Type: executable eshostname SNWLCLI> eshostname <newname> This variable stores the appliance hostname. Calling it with no argument will return the current name. Passing it a new name will overwrite the current one and update all related directories. Arguments: <newname>: The new host name that will overwrite the current one. Defaults: <newname>: current name Type: System Variable esps SNWLCLI> esps This command ps -ef output for ES processes Arguments: none Defaults: none Type: Executable exit SNWLCLI> exit This function will exit out of the CLI. Arguments: none Defaults: none Type: Executable 188 SonicWALL Security Administrator s Guide

200 Introduction fdatadisk SNWLCLI> fdatadisk This function returns the amount of free hard disk space allocated for the data directory in megabytes. Arguments: none Defaults: none Type: Executable fetchurl SNWLCLI> fetchurl [-q]<url> This function sends an HTTP request and dumps it to standard output. Arguments: <URL>: The URL being requested. -q: quiet -S: dump header in addition to response body Defaults: none Type: Executable get SNWLCLI> get <arg> [arg] This function will retrieve configuration parameters including ntp information, ntp server information, SYSLOG server information, and timezone information. Arguments: [arg]: Valid arguments that can be retrieved: ntp, ntpservers, syslogservers, tz Defaults: none Type: Executable SonicWALL Security Administrator s Guide 189

201 Introduction gms SNWLCLI> gms <interval> This variable stores the interval time between GMS heartbeat messages. Heartbeat messages allow GMS to monitor the Security appliance. Arguments: <interval>: time in seconds between GMS heartbeat messages. Defaults: none Type: System Variable help SNWLCLI> help <command> This function will print help messages describing available commands from the CLI. Calling it with no arguments will print out a list of available commands. It can take a command name as an argument and will print out more detailed explanation of the given command. Arguments: <command>: name of a valid CLI command. Defaults: none Type: Executable interface SNWLCLI> interface <ifname <ip / bits ip netmask>> <media <<10 100> / <FD HD>> auto> This variable controls the configuration of interfaces. With no arguments, it will return the configuration of all available interfaces. Passing it an interface name as the only argument will return all data related to the given interface. Passing it an interface name and an IP address will overwrite the current configuration. The media keyword covers both the speed and duplex and is set to auto-detect by default. Arguments: <ifname>: name of interface to be configured <ip>: new IP address to be assigned to interface <bits>: bit rate to be assigned to interface <netmask>: netmask to be assigned to interface Defaults: <ifname>: none <ip> / <bits> / <netmask>: current configuration of interface media: auto-detected Type: System Variable Example: SNWLCLI> interface eth SNWLCLI> interface eth0 media 100/HD 190 SonicWALL Security Administrator s Guide

202 Introduction iostat SNWLCLI> iostat [options...] [<interval> [<count>]] This is the standard iostat command. Refer to Linux documentation for more information. Arguments: see Linux help for details. Defaults: none Type: Executable mlfdnstest SNWLCLI> mlfdnstest This function is a diagnostic tool that tests the effectiveness of your DNS. Arguments: none Defaults: none Type: Executable mlfmta SNWLCLI> mlfmta [status version] This system variable holds information about the version and status of the appliance Mail Transfer Agent (MTA). This variable can not be manually edited, and must be passed an argument. Arguments: [status]: Displays status of appliance. [version]: Displays version of appliance. Defaults: none Type: System Variable ns SNWLCLI> ns This function is a build-in system command identical to netstat -a. It is used to determine the number of active connections. ES will support a finite number of open connections. Arguments: none Defaults: none Type: Executable SonicWALL Security Administrator s Guide 191

203 Introduction ntp SNWLCLI> ntp <on off> [<default servers <server> [<server>]...>] This variable controls the NTP (Network Time Protocol) on an appliance. With no arguments, it will print out the current NTP configuration. In order to change NTP configuration pass on or off as a first argument and then list of NTP servers to use. Use this command to synchronize the time with an NTP time server. Arguments: <on>: Enables NTP using currently configured NTP servers <off>: Turn off NTP <default servers>: Enables NTP and resets list of servers to the built-in defaults <server>: specifies a server to be set in NTP list Defaults: Current configuration Type: System Variable ping SNWLCLI> ping [-c COUNT] [-s SIZE] [-q] host This function is the standard ping function. Use this command to test connectivity. It also tests the appliance s DNS lookup values. Arguments: host: target of ping <count>: number of packets being sent out <size>: size of packets being sent out Defaults: none Type: Executable quit SNWLCLI> quit Exits out of the CLI. Arguments: none Defaults: none Type: Executable 192 SonicWALL Security Administrator s Guide

204 Introduction raidadd SNWLCLI> raidadd This function adds a new drive to the RAID array. Arguments: none Defaults: none Type: Executable Related Commands: raidremove, raidrebuild, raidverify raiddrives SNWLCLI> raiddrives This function prints out various information about the RAID devices in the box. Arguments: none Defaults: none Type: Executable Related Commands: raidinfo, raidports raidinfo SNWLCLI> raidinfo This function prints out various information about the RAID devices in the box. Arguments: none Defaults: none Type: Executable Related Commands: raiddrives, raidports, raidstatus raidports SNWLCLI> raidports This function prints out information about the RAID ports in the Security appliance. Arguments: none Defaults: none Type: Executable Related Commands: raiddrives, raidinfo SonicWALL Security Administrator s Guide 193

205 Introduction raidrebuild SNWLCLI> raidrebuild [<--start <m:h:d now> [--drive <drive>] --remove<job>>] This function will rebuild a drive within the raid array. With no arguments, it will display the rebuild status and scheduled jobs. Scheduling rebuilding operations is recommended as they can take a lengthy amount of time. SonicWALL recommends setting aside a full night for it. Arguments: <m:h:d>: scheduled rebuild start time using an optional specified drive or the first available spare. Specify starting time using the crontab standard from Linux. Defaults: none <drive>: drive to be rebuilt <job>: rebuild job to be removed. Type: Executable Related Commands: raidremove, raidstatus, raidverify raidremove SNWLCLI> raidremove This function removes a defective drive from the RAID array. It takes the name of the drive to be removed as an argument. Arguments: none Defaults: none Type: Executable Related Commands: raidrebuild, raidstatus, raidverify raidstatus SNWLCLI> raidstatus This function prints out information about the status of the RAID devices in the box. Arguments: none Defaults: none Type: Executable Related Commands: raiddrives, raidinfo 194 SonicWALL Security Administrator s Guide

206 Introduction raidverify SNWLCLI> raidverify [<--start <m:h:d now> --stop<m:h:d now> --remove<job>>] This function will verify the raid array. With no arguments, it will display the verification status and scheduled jobs. Scheduling verifying operations is recommended as they can take a lengthy amount of time. SonicWALL recommends setting aside a full night for it. Arguments: <m:h:d>: scheduled rebuild start or stop time using an optional specified drive or the first available spare. Specify starting time using the crontab standard from Linux. Defaults: none <job>: rebuild job to be removed. Type: Executable Related Commands: raidadd, raidrebuild reboot SNWLCLI> reboot This function will reboot the appliance. Arguments: none Defaults: none Type: Executable rebuildreplicatorindex SNWLCLI> rebuildreplicatorindex Run this command to rebuild the replicator gsn.idx file. The command will output the new content of the gsn.idx file. Arguments: none Defaults: none Type: Executable rebuildwebroot SNWLCLI> rebuildwebroot Run this command to rebuild the webapps ROOT. This command will delete the ROOT directory, then restart tomcat. Use this command if the Web interface becomes corrupted or unavailable. Arguments: none Defaults: none Type: Executable SonicWALL Security Administrator s Guide 195

207 Introduction recreatereportdb SNWLCLI> recreatereportdb Run this command to make a new empty report database and to reset the report bookmark files to the oldest mfe logs on system. The start and stop of the operation will be logged to MlfMfelmportSetup.log, along with how long it took. Arguments: none Defaults: none Type: Executable redirecthttp SNWLCLI> redirecthttp <on off> To have the appliance redirect HTTP calls to HTTPS, turn this variable on; otherwise turn it off. Arguments: none Defaults: on Type: System Variable Usage Example: SNWLCLI> redirecthttp on In a browser, enter in the address bar, user will be directed to <ip_of_appliance>:<https_port_number> SNWLCLI> redirecthttp off In a browser, enter in the address bar, user will not be directed to <ip_of_appliance> reinitializetofactorysettings SNWLCLI> reinitializetofactorysettings Run this command to reset the appliance to a its original settings. A warning message will be shown before this command is executed. Arguments: none Defaults: none Type: Executable 196 SonicWALL Security Administrator s Guide

208 Introduction repairdb SNWLCLI> repairdb <level number> Run this command to repair the report database. The command takes the level number as an argument. The levels indicate how the time and effectiveness of the repair. Level 1 is quicker while level 2 is more thorough. A message will be printed to stderr detailing how long the operation took. The start and stop of the operation will be logged to MlfMfelmportSetup.log, along with how long it took. Arguments: <level number>: 1 or 2. Level 1 is quicker while level 2 is more thorough Defaults: none Type: Executable reportdbalert SNWLCLI> reportdbalert <on off> This system variable controls whether or not the Security appliance will generate reporting alerts. Arguments: none Defaults: on Type: System Variable reportdbupdate SNWLCLI> reportdbupdate <on off> This system variable enables the automatic report database updates. It can be turned on or off. Arguments: none Defaults: on Type: System Variable reportdbupdatetocurver SNWLCLI> reportdbupdatetocurver This function will have the Security appliance upgrade to the newest available firmware. Arguments: none Defaults: none Type: Executable SonicWALL Security Administrator s Guide 197

209 Introduction restart SNWLCLI> restart This function manages running services. It takes a service name as an argument. The list of services is application-specific, except for the special name allservices which will cause application startup scripts to be used. Arguments: none Defaults: none Type: Executable Related Commands: stop, start route SNWLCLI> route <--add <target> --destination <destination> --remove <route>> This function acts like a system variable. With no argument, it will display stored routes. It can add routes if provided with an interface name or a gateway IP, or remove an existing route. Use this command to troubleshoot routing problems. Arguments: <target>: an IP address, net as IP/CIDR, or default to be added as a target to the new route <destination>: an interface name or a gateway IP <route>: path to be removed Defaults: none Type: Executable sethostinheader SNWLCLI> sethostinheader <on off> This system variable controls whether or not Security will mask the header of an . This variable can only be modified from the CLI. Arguments: none Defaults: off Type: System Variable 198 SonicWALL Security Administrator s Guide

210 Introduction setlog SNWLCLI> setlog <size in MB> <count> This system variable controls the size and number of MlfAsgSMTP log files while in debug mode. Values are updated in the server.xml file. Arguments: <size in MB>: max size of each log. Ranges from 1 to 100 MB. <count>: number of logs. Ranges from 1 to 20. Defaults: <size in MB>: 50 <count>: 6 Type: System Variable snmp SNWLCLI> snmp <on off> This variable holds the SNMP status. It can be turned on or off. Arguments: none Defaults: on Type: System Variable sshd SNWLCLI> sshd <on off> This variable holds the sshd status. This controls whether or not the appliance accepts SSH connections. It can be turned on or off. Warning: Setting this variable to off will terminate your CLI session as access to the Security appliance is through SSH. Although the CLI is not available if SSH is disabled, it is still accessible via direct console. Arguments: none Defaults: on Type: System Variable SonicWALL Security Administrator s Guide 199

211 Introduction start SNWLCLI> start <service> This function manages running services. It takes a service name as an argument. The list of services is application-specific, except for the special name allservices which will cause application startup scripts to be used. Arguments: <service>: service to start Defaults: none Type: Executable Related Commands: stop, restart stop SNWLCLI> stop <service> This function manages running services. It takes a service name as an argument. The list of services is application-specific, except for the special name allservices which will cause application shutdown scripts to be used. Arguments: <service>: service to stop Defaults: none Type: Executable Related Commands: restart, start testdbspeed SNWLCLI> testdbspeed <line number> This function is a diagnostic tool. Its argument is a positive integer signifying the number of lines it will write to test the speed of the report database. Arguments: <line number>: the number of lines to be written to test the speed of the database. Defaults: none Type: Executable 200 SonicWALL Security Administrator s Guide

212 Introduction telnet SNWLCLI> telnet <host> [<port>] This functions just like the interactive network communication program with the same name. It takes a host and a port as arguments. Use this tool to establish connectivity issues with an SMTP server. You can also use telnet to check if outbound SMTP rules on a firewall are well configured Arguments: <host>: hostname of telnet target <port>: port number Defaults: none Type: Executable time SNWLCLI> time <YYYY/MM/DD hh:mm> <timezone> This variable displays or sets the date, time, and the time zone. Arguments: <YYYY>: year <MM>: month <DD>: day <hh>: hours <mm>: minutes <timezone>: timezone Defaults: none Type: System Variable Related commands: date traceroute SNWLCLI> traceroute <host> This function operates like traceroute. It takes a host or IP address as an argument. Use this command to troubleshoot routing problems. Arguments: <host>: hostname to be traced to. Defaults: none Type: Executable SonicWALL Security Administrator s Guide 201

213 Introduction tsr SNWLCLI> tsr This function outputs an internal system state report. It does not take any arguments. Arguments: none Defaults: none Type: Executable validatedb SNWLCLI> validatedb Run this command to validate the database. A message will be printed to stderr detailing the time it took to perform the operation. The start and stop of the operation will be logged to MlfMfelmportSetup.log, along with how long it took. Arguments: none Defaults: none Type: Executable 202 SonicWALL Security Administrator s Guide

214 Glossary Term All-in-One Architecture Allowed List (Whitelist) Anti-Virus Blocked List (also known as Black Lists) Collaborative Settings Control Center Dashboard Cluster Directory Harvest Attack (DHA) DMZ Definition An architecture for the SonicWALL Security where one server manages all protection that receives all enterprise . See also Split Architecture on page 205. Lists of users, domains, and mailing lists that are allowed to send to users in your organization. Software that detects viruses in message bodies and attachments. Lists of users, domains, or mailing lists from whom you or your users do not want to receive . SonicWALL Security administers its own content-based signature network with a collaborative community of users and junk mailboxes worldwide. You can select collaborative settings to customize the level of influence community input has on enterprise spam blocking. Manages all data files; it controls and communicates with one or more of the remote analyzers. It stores or quarantines mail it receives from the remote analyzer, and queries LDAP servers to ensure valid users can log in to SonicWALL Security. A high level overview of the system statistics. A group of SonicWALL Security servers that act like a single system and enable high availability and, in some cases, load balancing and parallel processing. Spammers stage Directory Harvest Attacks (DHA) to get lists of all users in an organization s directory. DHA makes organizations vulnerable to increased attacks, spam, and fraudulent messages. The logical space between two firewalls where an gateway typically resides. This term was derived from De-Militarized Zone, an area between two warring countries where tanks were not permitted. Envelope Information in RFC-821 format, which includes the address from which the mail came and the receipt-to address. SonicWALL Security Administrator s Guide 203

215 Term First-touch server Honeypot Definition (continued) A configuration where s arriving into your organization are delivered the Security server first, as opposed to going through another MTA. The purpose of configuring Security as your firsttouch server is to capture the sender s IP address. A specially equipped system deployed by security professionals to lure hackers and track their every move. Internet Message Access Protocol (IMAP) Keystore Junk Box Junk Box Summary Lightweight Directory Access Protocol (LDAP) LDAP Groups LDAPS Master Account Mail Transfer Agent (MTA) Phishing Post Office Protocol Version 3 (POP3) Policy Management Profiler Probe Account Quarantine A method of accessing electronic mail messages that are kept on a mail server. IMAP permits a client program to access remote message stores as if they were local. The keystore file contains your public and private keys. A Web page interface that displays all quarantined . A daily sent to users summarizing messages that have been quarantined because they contained spam, viruses, or other undesired mail content. An Internet protocol that programs use to look up contact information from a server. Allow you to assign roles to user groups and set spam-blocking options for user groups. This is an optional configuration that enables you to finetune user access by group. LDAP run over SSL provides a secure LDAP connection The initial account you log in to when configuring SonicWALL Security. This is also the master administrative account. software that runs on an outward-facing server that delivers mail to an organization. Sending or creating a replica of an existing Web page to fool a user into submitting personal, financial, or password data. In the enterprise, phishers seek enterprise passwords and sensitive information. Phishers might use enterprise to send fraudulent information to customers and business partners. A protocol used to retrieve from a server. A customizable module that enables the administrator to filter the content of messages and attachments that enter SonicWALL Security. A software component that collects users outgoing addresses, which can optionally be stored as known good addresses. The Profiler can be configured to work with each supported client. Similar to a Honeypot, an account that is established on the Internet for the sole purpose of collecting spam and tracking hackers. A means of containing suspect messages in a Junk Box. 204 SonicWALL Security Administrator s Guide

216 Term Realtime Blackhole List. (RBL) Remote Analyzer Privilege Roles Sender ID Simple Mail Transfer Protocol (SMTP) Secure Socket Layer (SSL) Spam SPF Split Architecture STARTTLS Tarpitting Time Zero Virus Thumbprint Transport Layer Security (TLS) Usermap User Profile Definition (continued) A list of Internet TCP/IP addresses known to send spam, or by hosts considered friendly to spam. An SMTP proxy placed in the flow, and performs a spam analysis to determine whether is good or junk. It sends junk mail to the control center where it is quarantined, and routes good mail to its destination server. Users can be assigned privileges so that they can administer all , log in as another person or for a helpdesk role, can view SonicWALL Security reports, or view their own Junk Box. A mechanism that determines whether the alleged domain address of each is authentic, which is one factor SonicWALL Security uses to determine whether the message is junk. A protocol designed to transfer mail reliably and efficiently. A protocol for transmitting private documents via the Internet. SSL uses a private key to encrypt data that is transferred over the SSL connection. Any unsolicited commercial that a user does not want. Spam frequently contains false advertising, get-rich-quick schemes, and other offensive material. Sender Policy Framework (SPF) is an extension to the Simple Mail Transfer Protocol (SMTP). SPF allows software to identify and reject forged addresses in the SMTP MAIL FROM (Return-Path), a typical nuisance in spam. Architecture for networks with multiple physical data centers, the functions of SonicWALL Security can be split across different servers in different locations. The keyword used to initiate a secure SMTP connection between two servers using Transport Layer Security (TLS). Protects your enterprise from spammers trying to spam your mail server accounts through Directory Harvest attacks (DHA). A term for the first hours that a virus is released, when major anti-virus companies have not yet modified their virus definitions to catch it. Checksums that uniquely identify from junk messages. The thumbprint contains absolutely no readable information. Thumbprints are sent the collaborative community to block new types of junk. TLS is the successor to the Secure Sockets Layer (SSL) protocol. The terms SSL and TLS are often used interchangeably since they are very similar protocols. A local cache of the LDAP Server containing the list of aliases per user. An optional program that creates per-user allowed lists based on the information in address books and sent items, and then uses the HTTP protocol to post these allowed lists in an XML format to the SonicWALL Security. SonicWALL Security Administrator s Guide 205

217 Term Unjunk Virus Definition (continued) Removing messages from the Junk Box as enabled by the administrator. Message content that contains malicious and self-replicating code. A virus in can infect the user s computer and then use to propagate itself to other computers. 206 SonicWALL Security Administrator s Guide

218 Index A A record in your internal DNS 83 accept automated allowed list 71 Active Directory server 12 add filter window 110 adding Control Center 34 mailing lists 74 to allowed and blocked lists 73 adding a mail server split architecture 28 adding blocked list services 80 address conflicts 73 administrator 8, 142 administrator account 7, 9 alert suppression 51 alias LDAP 39 alias attribute LDAP 38 aliases 35, 38 all in one architecture description 2 allowed and blocked lists 69 adding domains 73 adding entries 73 deleting entries 73 allowed lists 69, 72, 151, 155 anonymous bind login for LDAP 37 appliance vii, 3 Approval Box 129 archiving 135 auditing searching inbound s 97 searching outbound s 97 authenticate domains 77 B backup/restore settings 52 bad address Directory Harvest Attacks 54 Bayesian configuring settings 76 blocked list services 80 blocked lists 69, 72 C categories of junk 169 changing filter order 117 Changing the Hostname 62 cluster 32 collaborative community 203 collaborative thumbprints 69 complex 10 Compliance Module 101, 126 Compliance Subscription License Key 101 Configure MTA 34 Connection Management 52 Control Centers 28, 32 corporate allowed lists 151, 155 corporate junk box 151 D dangerous file attachments 107 default spam management window 70 defaults restoring message management settings 139 delegates 148 deleting SonicWALL Security Administrator Guide 207

219 blocked list services 80 entries from allowed and blocked lists 73 junk box messages 155 Remote Analyzer 33 Denial of Service (DoS) attack protection 55 detecting spam 69 dictionaries 127 predefined 127 Directory Harvest Attack (DHA) protection 53 Directory Harvest Attacks 53, 85, 203 personalized masquerades 53 distribution lists 35 divergence detection 85 DNS 6 domain authentication 77 Domain Name System (DNS) 77 domains adding to allowed and blocked lists 73 E Address Rewriting 34 aliases 35, auditing 97 notification action 123 policy 123 encryption 132 Enterprise Gateway administrator account 7, 9 master account 7, 9 Enterprise Gateway Appliance vii enterprise phishing 85 Exchange 5.5 server. 12 F factory settings 66 file extension matching 104 filter action taken 114 part of message 111 policy 109 filter order 117 filter words or phrase policy 112 firewall 6 first touch server 5 first-touch server for SPF 77 foreign language 79 fraud personalized masquerades 53 send proactive fraud notification 86 fraud protection 86 fraudulent Directory Harvest Attacks 53 G good that was junked 82 H help customized help URL 45 Host Configuration 21 hostile word matching 105 I identity theft 85 inbound mail flow 23, 26 Intelligent Address Matching J junk box 138, 151 number of days to delete s 40 Junk Box summaries 157 junk box summary default frequency 42 from address 43 send only to LDAP users 42 subject line 43 URL for user view 43 junk that was missed 82 junk submissions 81 L language of summary 157 languages 79 LDAP autofill 38 configuration 35 Directory Harvest Attacks 54 directory node alias attribute filter query 38 testing 37 user login name attribute SonicWALL Security Administrator Guide

220 LDAP server 12, 36 LDAP Server Type 12 License key Compliance Subscription 101 likely fraud 86 lists allowed and blocked 72 logging in 8 M mail servers testing 33 mail transfer agent status 161 mailing lists 74 adding entries 74 master account 7, 9 master account password 9 messages resetting defaults in message management 139 messages identified as fraud 170 miscategorized 83 miscategorized messages 82 Monitoring 48 MTA status 161 MX records 6 N Networking 63 nslookup 78 NTLM authentication 12 O Other LDAP Servers 12 P patch update 66 policy notification 123 Policy Filters 106 policy management 101 policy notification parameters 123 policy variables 123 Postfix 77 probe accounts 84 propagating changes to Remote Analyzers 31 publish your SPF records 78 punctuation rules for words 102 Q quarantine junk messages 10 query LDAP 38 Quick Configuration 10 R real-time system monitor 162 record ID 133 regular expressions 105 Remote Analyzer description 3 Remote Analyzers 28, replication 3 report all fraudulent 87 rules and collaborative settings settings rules and collaborative 75 S SafeMode 17 Scheduled Reports 176 search value field 115 searching corporate junk box 153 lists 73 secured connection 36 Sender ID 77 Sender ID in statistical evaluation 76 Sender Policy Framework (SPF) 77 SendMail 77 server configuration changes 34 shared directory 2 signing in as any user 139 SMTP proxy service 4 SMTP setup 11 SonicWALL Security data center 13 SonicWALL Security s community fraud 87 spam detecting 69 techniques to block 69 spam collection probe accounts 84 SPF records 78 split architecture adding a mail server 28 description 3 static IP address 6 SonicWALL Security Administrator Guide 209

221 store in Junk Box and delete after 151, 155 system status 160 system/log files 67 T TCP inbound traffic 179 outbound traffic 179 Test Connectivity to SonicWALL Security 47 Test LDAP Login 12 Test LDAP Query 12 testing LDAP 37 mail servers 33 URL for user view in junk box summary 43 Throttling 57 thumbprint 75 time-zero virus 89 top junk mail origination domains 169 U unjunk 151, 155 update patch 66 Updates 46 upload patch 66 User Profilers 51 Usermap import 139 users finding 138 login enabled 44 roles 142 signing in as 139 who can log in 137 Users can preview their own quarantined junk mail 13 V variables policy 123 W Web proxy configuration 46 Windows NT/NetBIOS domain name 12 word matching traditional 105 X X SonicWALL Security Administrator Guide

222 SonicWALL, Inc Borregas Avenue T Sunnyvale CA F PN: Rev B 2007 SonicWALL, Inc. is a registered trademark of SonicWALL, Inc. Other product names mentioned herein may be trademarks and/or registered trademarks of their respective companies. Specifications and descriptions subject to change without notice. G035.4_GMS.GSG.v1