Best Practices Guide

revision 3.0

McAfee® Network Security Platform
version 6.0

McAfee® Network Protection
Industry-leading network security solutions

COPYRIGHT
Copyright ® 2001 - 2010 McAfee, Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form or by any means without the written permission of McAfee, Inc., or its suppliers or affiliate companies.

TRADEMARKS
ACTIVE FIREWALL, ACTIVE SECURITY, ACTIVESECURITY (AND IN KATAKANA), ACTIVESHIELD, CLEAN-UP, DESIGN (STYLIZED E), DESIGN (STYLIZED N), ENTERCEPT, EPOLICY ORCHESTRATOR, FIRST AID, FOUNDSTONE, GROUPSHIELD, GROUPSHIELD (AND IN KATAKANA), INTRUSHIELD, INTRUSION PREVENTION THROUGH INNOVATION, McAfee, McAfee (AND IN KATAKANA), McAfee AND DESIGN, McAfee.COM, McAfee VIRUSSCAN, NET TOOLS, NET TOOLS (AND IN KATAKANA), NETSCAN, NETSHIELD, NUTS & BOLTS, OIL CHANGE, PRIMESUPPORT, SPAMKILLER, THREATSCAN, TOTAL VIRUS DEFENSE, VIREX, VIRUS FORUM, VIRUSCAN, VIRUSSCAN, VIRUSSCAN (AND IN KATAKANA), WEBSCAN, WEBSHIELD, WEBSHIELD (AND IN KATAKANA) are registered trademarks or trademarks of McAfee, Inc. and/or its affiliates in the US and/or other countries. The color red in connection with security is distinctive of McAfee brand products. All other registered and unregistered trademarks herein are the sole property of their respective owners.

LICENSE AND PATENT INFORMATION License Agreement
NOTICE TO ALL USERS: CAREFULLY READ THE APPROPRIATE LEGAL AGREEMENT CORRESPONDING TO THE LICENSE YOU PURCHASED, WHICH SETS FORTH THE GENERAL TERMS AND CONDITIONS FOR THE USE OF THE LICENSED SOFTWARE. IF YOU DO NOT KNOW WHICH TYPE OF LICENSE YOU HAVE ACQUIRED, PLEASE CONSULT THE SALES AND OTHER RELATED LICENSE GRANT OR PURCHASE ORDER DOCUMENTS THAT ACCOMPANIES YOUR SOFTWARE PACKAGING OR THAT YOU HAVE RECEIVED SEPARATELY AS PART OF THE PURCHASE (AS A BOOKLET, A FILE ON THE PRODUCT CD, OR A FILE AVAILABLE ON THE WEB SITE FROM WHICH YOU DOWNLOADED THE SOFTWARE PACKAGE). IF YOU DO NOT AGREE TO ALL OF THE TERMS SET FORTH IN THE AGREEMENT, DO NOT INSTALL THE SOFTWARE. IF APPLICABLE, YOU MAY RETURN THE PRODUCT TO McAfee OR THE PLACE OF PURCHASE FOR A FULL REFUND.

License Attributions
This product includes or may include: * Software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). * Cryptographic software written by Eric A. Young and software written by Tim J. Hudson. * Some software programs that are licensed (or sublicensed) to the user under the GNU General Public License (GPL) or other similar Free Software licenses which, among other rights, permit the user to copy, modify and redistribute certain programs, or portions thereof, and have access to the source code. The GPL requires that for any software covered under the GPL, which is distributed to someone in an executable binary format, that the source code also be made available to those users. For any such software covered under the GPL, the source code is made available on this CD. If any Free Software licenses require that McAfee provide rights to use, copy or modify a software program that are broader than the rights granted in this agreement, then such rights shall take precedence over the rights and restrictions herein. * Software originally written by Henry Spencer, Copyright 1992, 1993, 1994, 1997 Henry Spencer. * Software originally written by Robert Nordier, Copyright (C) 1996-7 Robert Nordier. * Software written by Douglas W. Sauder. * Software developed by the Apache Software Foundation (http://www.apache.org/). A copy of the license agreement for this software can be found at www.apache.org/licenses/LICENSE-2.0.txt. * International Components for Unicode ("ICU") Copyright (C) 1995-2002 International Business Machines Corporation and others. * Software developed by CrystalClear Software, Inc., Copyright (C) 2000 CrystalClear Software, Inc. * FEAD(R) Optimizer(R) technology, Copyright Netopsystems AG, Berlin, Germany. * Outside In(R) Viewer Technology (C) 1992-2001 Stellent Chicago, Inc. and/or Outside In(R) HTML Export, (C) 2001 Stellent Chicago, Inc. * Software copyrighted by Thai Open Source Software Center Ltd. and Clark Cooper, (C) 1998, 1999, 2000. * Software copyrighted by Expat maintainers. * Software copyrighted by The Regents of the University of California, (C) 1996, 1989, 1998-2000. * Software copyrighted by Gunnar Ritter. * Software copyrighted by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A., (C) 2003. * Software copyrighted by Gisle Aas. (C) 1995-2003. * Software copyrighted by Michael A. Chase, (C) 1999-2000. * Software copyrighted by Neil Winton, (C) 1995-1996. * Software copyrighted by RSA Data Security, Inc., (C) 1990-1992. * Software copyrighted by Sean M. Burke, (C) 1999, 2000. * Software copyrighted by Martijn Koster, (C) 1995. * Software copyrighted by Brad Appleton, (C) 1996-1999. * Software copyrighted by Michael G. Schwern, (C) 2001. * Software copyrighted by Graham Barr, (C) 1998. * Software copyrighted by Larry Wall and Clark Cooper, (C) 1998-2000. * Software copyrighted by Frodo Looijaard, (C) 1997. * Software copyrighted by the Python Software Foundation, Copyright (C) 2001, 2002, 2003. A copy of the license agreement for this software can be found at www.python.org. * Software copyrighted by Beman Dawes, (C) 1994-1999, 2002. * Software written by Andrew Lumsdaine, Lie-Quan Lee, Jeremy G. Siek (C) 1997-2000 University of Notre Dame. * Software copyrighted by Simone Bordet & Marco Cravero, (C) 2002. * Software copyrighted by Stephen Purcell, (C) 2001. * Software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/). * Software copyrighted by International Business Machines Corporation and others, (C) 1995-2003. * Software developed by the University of California, Berkeley and its contributors. * Software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http:// www.modssl.org/). * Software copyrighted by Kevlin Henney, (C) 2000-2002. * Software copyrighted by Peter Dimov and Multi Media Ltd. (C) 2001, 2002. * Software copyrighted by David Abrahams, (C) 2001, 2002. See http://www.boost.org/libs/bind/bind.html for documentation. * Software copyrighted by Steve Cleary, Beman Dawes, Howard Hinnant & John Maddock, (C) 2000. * Software copyrighted by Boost.org, (C) 1999-2002. * Software copyrighted by Nicolai M. Josuttis, (C) 1999. * Software copyrighted by Jeremy Siek, (C) 1999-2001. * Software copyrighted by Daryle Walker, (C) 2001. * Software copyrighted by Chuck Allison and Jeremy Siek, (C) 2001, 2002. * Software copyrighted by Samuel Krempp, (C) 2001. See http://www.boost.org for updates, documentation, and revision history. * Software copyrighted by Doug Gregor (gregod@cs.rpi.edu), (C) 2001, 2002. * Software copyrighted by Cadenza New Zealand Ltd., (C) 2000. * Software copyrighted by Jens Maurer, (C) 2000, 2001. * Software copyrighted by Jaakko Järvi (jaakko.jarvi@cs.utu.fi), (C) 1999, 2000. * Software copyrighted by Ronald Garcia, (C) 2002. * Software copyrighted by David Abrahams, Jeremy Siek, and Daryle Walker, (C) 1999-2001. * Software copyrighted by Stephen Cleary (shammah@voyager.net), (C) 2000. * Software copyrighted by Housemarque Oy <http://www.housemarque.com>, (C) 2001. * Software copyrighted by Paul Moore, (C) 1999. * Software copyrighted by Dr. John Maddock, (C) 1998-2002. * Software copyrighted by Greg Colvin and Beman Dawes, (C) 1998, 1999. * Software copyrighted by Peter Dimov, (C) 2001, 2002. * Software copyrighted by Jeremy Siek and John R. Bandela, (C) 2001. * Software copyrighted by Joerg Walter and Mathias Koch, (C) 2000-2002. * Software copyrighted by Carnegie Mellon University (C) 1989, 1991, 1992. * Software copyrighted by Cambridge Broadband Ltd., (C) 2001-2003. * Software copyrighted by Sparta, Inc., (C) 2003-2004. * Software copyrighted by Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications, (C) 2004. * Software copyrighted by Simon Josefsson, (C) 2003. * Software copyrighted by Thomas Jacob, (C) 2003-2004. * Software copyrighted by Advanced Software Engineering Limited, (C) 2004. * Software copyrighted by Todd C. Miller, (C) 1998. * Software copyrighted by The Regents of the University of California, (C) 1990, 1993, with code derived from software contributed to Berkeley by Chris Torek.

Issued JUNE 2010 / Best Practices Guide
700-2379-00/ 3.0 - English

Contents
Preface ........................................................................................................... v
Introducing McAfee Network Security Platform............................................................................. v About this Guide............................................................................................................................ v Audience .......................................................................................................................................vi Conventions used in this book ......................................................................................................vi Related Documentation................................................................................................................vii Contacting Technical Support ..................................................................................................... viii

Chapter 1 Introduction.................................................................................. 1
Pre-installation checklist................................................................................................................ 1

Chapter 2 Recommended Manager specifications.................................... 2
Manager Server specifications ...................................................................................................... 2 Manager Client specifications ....................................................................................................... 2 Determining your Database Requirements ................................................................................... 3

Chapter 3 Cabling best practices ................................................................ 4 Chapter 4 Large Sensor deployments ........................................................ 5
Staging Sensors prior to deployment ............................................................................................ 6 Recommendations for large Sensor deployment .......................................................................... 6

Chapter 5 Troubleshooting issues with Sensor ........................................ 7 Chapter 6 Configuration of Speed and Duplex settings ........................... 8
Duplex mismatches ....................................................................................................................... 8 Troubleshooting a Duplex Mismatch with Cisco Devices.............................................................. 8 Cisco PIX® Firewall ...............................................................................................................9 Cisco CSS 11000...................................................................................................................9 Cisco Catalyst® 2900XL, 3500XL Series (Hybrid).................................................................9 Cisco Catalyst 4000, 5000, 6000 Series (Native) ..................................................................9 Cisco IOS® for Catalyst 4000, 6000 Series ...........................................................................9 Auto-negotiation issues ................................................................................................................. 9 Situations that may result in Auto-negotiation issues...........................................................10 Valid Auto-negotiation and Speed Configuration settings....................................................10 Explanation of CatOS show port command counters ..........................................................11 Gigabit auto-negotiation (no link to connected device) ........................................................12

Chapter 7 Effective Policy Tuning practices ............................................ 13
Analyzing high-volume attacks.................................................................................................... 13 Managing Attack filters ................................................................................................................ 13 Learning profiles in DoS attacks.................................................................................................. 14

Chapter 8 Response Management ............................................................ 15
Sensor Response Actions ........................................................................................................... 15

Chapter 9 Creating Rule sets ..................................................................... 16

iii

Best methods for rule set creation............................................................................................... 16

Chapter 10 Port clustering on Asymmetric networks ............................. 17 Chapter 11 Access Control Lists (ACLs).................................................. 18 Chapter 12 SSL best practices .................................................................. 19
SSL only traffic - throughput........................................................................................................ 19 SSL only traffic - throughput........................................................................................................ 19 SSL traffic mixed with HTTP 1.1 traffic........................................................................................ 20 Supported SSL functionalities ..................................................................................................... 21 Supported Web servers .......................................................................................................22 Supported cipher suites .......................................................................................................22 SSLv3/TLS cipher suites......................................................................................................22 Unsupported SSL functionalities ................................................................................................. 22

Chapter 13 Sensor HTTP Response Processing deployment................ 23
Tests for enabling HTTP Response Traffic ................................................................................. 23 HTTP Response processing results for I series Sensors.....................................................24 HTTP Response processing results for M-series Sensors ..................................................24

Chapter 14 Database maintenance ........................................................... 26
Backup of data and configurations .............................................................................................. 26

Chapter 15 Alerts and Disk space maintenance ...................................... 28
Archiving alerts............................................................................................................................ 28 Scripts for disk space maintenance............................................................................................. 28 Dbtuning.bat .........................................................................................................................28 Purge.bat..............................................................................................................................29 Using File Maintenance Scheduler.............................................................................................. 29

Chapter 16 Manager Disaster Recovery (MDR) best practices .............. 30 Chapter 17 Performance issues ................................................................ 31
Sniffer trace ................................................................................................................................. 31 Data link errors ............................................................................................................................ 31 Half-duplex setting ...............................................................................................................31 Full-duplex setting ................................................................................................................31

Chapter 18 Vulnerability Assessment....................................................... 32 Chapter 19 I-series Sensor capacity by model number .......................... 33 Chapter 20 M-series Sensor capacity by model number ........................ 35 Chapter 21 Comparison Between I-1200/I-1400 and M-1250/M-1450 FE ports ............................................................................................................. 37 Index ............................................................................................................. 40

iv

and NTBA Appliance are installed and managed through a single Manager. thus complementing the NAC and IPS capabilities in a scenario in which McAfee Network Security Sensor. the supporting documents for this guide and how to contact McAfee Technical Support. and explains how this document is organized. and scalable Network Access Control (NAC). About this Guide This guide provides the recommended practices for using Network Security Platform most effectively.speed & duplex settings Policy Tuning best practices Best Practices for creating Rule sets Port clustering on asymmetric networks Tips for Access Control Lists (ACLs) SSL best practices HTTP Response processing deployment for the Sensor Database Maintenance Alerts & Disk space Maintenance issues Manager Disaster Recovery (MDR) pairs Performance issues and Vulnerability Assessment v . It also provides information such as. while providing unmatched protection against spyware and known. and encrypted attacks. network Intrusion Prevention System (IPS) and Network Threat Behavior Analysis (NTBA) for mission-critical enterprise. NAC Sensor. Best practices are provided for the following topics/issues in Network Security Platform: • • • • • • • • • • • • • • • • Hardware and software recommendations for Network Security Platform Cabling best practices Considerations for large McAfee® Network Security Sensor [formerly McAfee® IntruShield® Sensor] deployments Troubleshooting tips for the McAfee Network Security Sensor (Sensor) Sensor Deployment issues . carrier. and service provider networks. zero-day. McAfee® Network Threat Behavior Analysis Appliance provides the capability of monitoring network traffic by analyzing NetFlow information flowing through the network in real time. discusses the information in this document. accurate. Introducing McAfee Network Security Platform McAfee® Network Security Platform [formerly McAfee® IntruShield®] delivers the most comprehensive.Preface This preface provides a brief introduction to the product.

set Sensor ip <A. Type: setup and then press ENTER. Text such as syntax. Select My Company > Admin Domain > Summary.D> Caution: vi . 1. Press ENTER. Information that you must read before beginning a procedure or that alerts you to negative consequences of certain actions. click Backup.0 Preface Audience This guide is intended for use by network technicians and maintenance personnel responsible for installing. Procedures are presented as a series of numbered steps. the relationship between tasks.McAfee® Network Security Platform 6. buttons. or the commands necessary to perform particular tasks. Menu or action group selections are indicated using a right angle bracket. key words. selections. situation or environment is shown in italics. Variable information that you must Type: Sensor-IP-address and then press type based on your specific ENTER. tabs. and maintaining McAfee® Network Security Manager [formerly McAfee® IntruShield® Security Manager].C. On the Configuration tab. Parameters that you must supply are shown enclosed in angle brackets. and commands on the User Interface (UI) are shown in Arial Narrow bold font. such as loss of data is denoted using this notation. The Service field on the Properties tab specifies the name of the requested service. Conventions used in this book This document uses the following typographical conventions: Convention Example Terms that identify fields. and values that you must type exactly are denoted using Courier New font. but is not necessarily familiar with daily IPS-related tasks. Names of keys on the keyboard are denoted using UPPER CASE. configuring. options.B.

but non-critical.0 Preface Convention Example Information that you must read to prevent injury. Warning: Note: Related Documentation The following documents and on-line help are companions to this guide. Notes that provide related. information are denoted using this notation. accidents from contact with electricity. or other serious consequences is denoted using this notation.McAfee® Network Security Platform 6. Refer to Quick Tour for more information on these guides. • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Quick Tour Installation Guide Upgrade Guide Getting Started Guide IPS Deployment Guide Manager Configuration Basics Guide I-1200 Sensor Product Guide I-1400 Sensor Product Guide I-2700 Sensor Product Guide I-3000 Sensor Product Guide I-4000 Sensor Product Guide I-4010 Sensor Product Guide M-1250/M-1450 Sensor Product Guide M-1250/M-1450 Quick Start Guide M-2750 Sensor Product Guide M-2750 Quick Start Guide M-3050/M-4050 Sensor Product Guide M-3050/M-4050 Quick Start Guide M-6050 Sensor Product Guide M-6050 Quick Start Guide M-8000 Sensor Product Guide M-8000 Quick Start Guide Gigabit Optical Fail-Open Bypass Kit Guide Gigabit Copper Fail-Open Bypass Kit Guide 10 Gigabit Fail-Open Bypass Kit Guide M-8000/M-6050/M-4050/M-3050 Slide Rail Assembly Procedure M-2750 Slide Rail Assembly Procedure M-series DC Power Supply Installation Procedure Administrative Domain Configuration Guide Manager Server Configuration Guide CLI Guide vii .

and signature updates. viii .com.mcafee. PST Monday-Friday. technical bulletins. You will be provided with a user name and password for the online case submission. Phone Technical Support is available 7:00 A.0 Preface • • • • • • • • • • • • • • • • • Device Configuration Guide IPS Configuration Guide NAC Configuration Guide Integration Guide System Status Monitoring Guide Reports Guide Custom Attack Definitions Guide Central Manager Administrator's Guide Troubleshooting Guide Special Topics Guide—In-line Sensor Deployment Special Topics Guide—Sensor High Availability Special Topics Guide—Virtualization Special Topics Guide—Denial-of-Service NTBA Appliance Administrator's Guide NTBA Monitoring Guide NTBA Appliance T-200 Quick Start Guide NTBA Appliance T-500 Quick Start Guide Contacting Technical Support If you have any questions.html page. Note: McAfee requires that you provide your GRANT ID and the serial number of your system when opening a ticket with Technical Support.mcafee. In addition.McAfee® Network Security Platform 6.M. Extended 24x7 Technical Support is available for customers with Gold or Platinum service contracts.com/us/about/contact/index. contact McAfee for assistance: Online Contact McAfee Technical Support http://mysupport. Global phone contact numbers can be found at McAfee Contact Information http://www. software downloads. Registered customers can obtain up-to-date documentation. customers can also resolve technical issues with the online case submit. and quick tips on McAfee's 24x7 comprehensive KnowledgeBase. to 5:00 P.M.

Following chapters outline the best practices for Network Security Platform. built for the accurate detection and prevention of intrusions and network misuse. see Planning for installation. This can save considerable time during the installation and tuning process of the system. Troubleshooting Guide. For more information. We recommend that you follow some of the best techniques and tips to use McAfee Network Security Platform most effectively.CHAPTER 1 Introduction McAfee® Network Security Platform [formerly McAfee® IntruShield®] is a combination of network appliances and software. Pre-installation checklist There are some important tasks that you should consider before McAfee® Network Security Manager [formerly McAfee® IntruShield® Security Manager] software installation. 1 .

Many McAfee® Network Security Platform issues result from an under-powered Manager Server. to manage 40 or more McAfee® Network Security Sensors (Sensors). The larger your deployment. Manager Server specifications The following is the recommended minimum hardware configuration for a Manager Server with embedded MySQL database: Hardware Recommended Size/Speed Physical memory Processor Hard Disk 4 GB RAM 2 x 3. which provides a Web-based user interface for centralized and remote Sensor management. Because Java applets take advantage of the processor on the host from which they are being viewed.2 Pentium processors 80 GB hard disk space (or greater) Manager Client specifications The Manager client is a Java Web application. 2 . we recommend larger configurations than the hardware specifications in the release notes. For example.CHAPTER 2 Recommended Manager specifications McAfee® Network Security Manager (Manager) software runs on a dedicated Windows server. the more high-end your Manager Server should be.5 GHz or faster CPU Note: You will experience better performance in your configuration and dataforensic tasks by connecting to the Manager from a browser on the client machine. The Manager contains Java applets. we also recommend that the client hosts used to manage the Network Security Platform solution meet the requirements in the following table: Hardware Recommended Size/Speed Physical memory Processor 512 MB or more 1. Performance may be slow if you connect to the Manager using a browser on the server machine itself.

Things to consider while determining your database size requirements are: • Aggregate alert and packet log volume from all Sensors—Many Sensors amount to higher alert volume and require additional storage capacity. mostly unique to the deployment scenario. one year) will require additional storage capacity to accommodate both old and new data. Manager Server Configuration Guide. McAfee recommends archiving and deleting old alert data regularly. • Lifetime of alert and packet log data: You need to consider the time before you archive or delete an alert. Note: For more information on capacity planning. As a best practice. see Capacity Planning. These factors determine the amount of data you want to retain in the database and the time for which the data has to be retained. and attempting to keep your active database size to about 40 GB. Maintaining your data for a long period of time (for example. while a packet log is approximately 450 bytes.McAfee® Network Security Platform 6. 3 .0 Recommended Manager specifications Determining your Database Requirements The amount of space required for your database is governed by many factors. Note that an alert is roughly 200 bytes on average.

use those connections to configure the solution. and so on. or those with congestion problems. Also. only after the McAfee® Network Security Sensor (Sensor) has been fully configured. in the most security-conscious environments. a private network is often used to connect the Sensor management ports to the McAfee® Network Security Manager (Manager).CHAPTER 3 Cabling best practices It is a common practice to physically cable the monitoring ports. and only physically introduce the Sensor into the scanning process once the proper scanning policies are in place. most administrators cable the console and management ports. In other words. This is another best practice in terms of cabling the Sensors. the monitoring ports have been configured. 4 . the latest signature set has been downloaded.

at a much faster rate.5 hours to complete a signature set update. CLI Guide. So. For more information on the process of using TFTP to update your Sensor software. each Sensor must pass its alert data to the Manager when connectivity is re-established. You can schedule this process though you can’t reboot the Sensor automatically.1. prior to the deployment.1. For example. there is potential to starve Manager resources since the resulting alerts are passed to the Manager. which makes it difficult to locate the resource you require at any point of time.When the Manager starts. If the communication with the Manager is lost. Your VIDS names should also be clear and easy for everyone maintaining the network to recognize at a glance. Note that from version 3. it is required to account for the startup load on the Manager.Signature Set downloads are applied to Sensors serially. the Manager Resource Tree can become very crowded. which helps you to load concurrent images on the Sensor via the Sensor’s CLI. in a deployment with 50 Sensors. Sensor Software Updates . For releases prior to 3. Note that the resource names appear both in the Resource Tree of the Manager as well as in Alert data and Reports.Be aware of the time periods in which your scheduled processes (such as database backup or report generation) occur. not hours. A reboot can take up to 5 minutes. more data is passed into the Manager.Depending on the number of VIDS and Admin Domains defined in your deployment.1. This includes having many users logged into the system simultaneously. not • • • • • concurrently. as this can lead to process locking. 5 .” and so on. Alert Traffic . Concurrent processes . As the volume of alerting increases. before deployment. • Signature Set downloads .CHAPTER 4 Large Sensor deployments When you consider large McAfee® Network Security Sensor (Sensor) deployments. recognizable names for your Sensors and any VIDS you create. Depending on the policies deployed on your system. the process would take approximately 3 minutes per Sensor. one Sensor at-a-time. see Upgrading Sensor software via a TFTP server.All Sensor software updates do require a reboot. Start-up load on the Manager .Take note of the volume of alerting in your Sensors. The same is true for policy updates. this process has been reduced to a matter of minutes. and try not to attempt other tasks during that time period. with versions prior to 3. it will take approximately 2. At this point we would recommend that you utilize a second McAfee® Network Security Manager (Manager) to minimize the time. Usability . compare a worldwide deployment where Sensors are named “4010-1” through “4010-25” as opposed to “UK-London-sens1.But but any update from the Manager Server causes the process to take place sequentially. establishing connections with all Sensors can be time consuming as Sensors continue to collect alerts.” “India-Bangalore-sens1. For example. You must decide the point at which a signature set update process becomes time consuming. McAfee recommends that you have a good understanding on the best techniques required to accomplish these tasks in your deployment scenario. It can also lead to confusion if you have not provided unique. (where the number of Sensors deployed range from 36 to 70) there are some important tasks which should be considered. You can instead use the TFTP method for updating the Sensor image.

before shipping the Sensor to another. see Updating the configuration of a Sensor. As each new batch of Sensors provides you with more data points.0 Large Sensor deployments Staging Sensors prior to deployment With large or very large deployments. and/or if you are planning to release Sensors to various geographical regions or remote locations. you can tune your policies more effectively. Note: Very large Sensor deployments mean that the number of Sensors deployed is more than 71. McAfee provides a few recommendations for this process: • Spend time creating effective policies before actual deployment. they deploy the Sensor in a live environment. Stagger your Sensor deployment in phases. Here they test the Sensor functionality. Installation Guide. Once they are comfortable with the product. But policies like the McAfee Network Security Platform provided All-Inclusive policy can overwhelm you with data. For more information on updating the Sensor with latest software updates. Device Configuration Guide. Recommendations for large Sensor deployment Most McAfee® Network Security Platform customers begin their deployment in their lab environment. For example. if every Sensor in a large deployment is running it without any customization. Large Sensor deployments have Sensors numbering between 36 and 70. and create an initial policy. you will have to consider staging your Sensors before you release them to their final destination. Availability of more information makes the tuning process easier. and then box the configured Sensor and send it to its final destination. Or you might use the TFTP feature to load the Sensor image at one location. make sure that the Sensor is working as expected. For more information. use the McAfee® Network Security Manager (Manager) in a lab environment to push Sensor software to the Sensor. familiarize themselves with the Manager.McAfee® Network Security Platform 6. see Upgrading Sensor software via a TFTP server. • 6 . and become more aggressive in the number of Sensors you deploy in the next phase.

If a kit is attached to the Sensor. to troubleshoot a Sensor issue: • All Sensors have a Layer2 Passthru feature. This enables you to set a threshold on the Sensor that pushes the Sensor into L2 bypass mode if the Sensor experiences a specified number of errors within a specified time frame. there is no need for the external kit. to disconnect the cables and let traffic flow unimpeded. causing traffic to flow through the Sensor while bypassing the detection engine. Caution 3: Depending on the network equipment. one instinct is to physically pull it out of the path. (The layer2 mode deassert command pushes the Sensor back to detection mode. If you feel your Sensor is causing network disruption. For FE monitoring ports. this disruption should range from a couple of seconds to more than a minute with certain vendors’ devices. before you remove it from the network. if they are. which consists of a bypass switch and a controller. issue the following command: layer2 mode assert This pushes the Sensor into Layer2 Passthru (L2) mode. disabling the Sensor ports forces traffic to flow through the bypass switch. 7 . McAfee recommends that you first try the following techniques. Connect a fail-open kit.) Configure Layer2 Passthru Mode on each Sensor. to any GE monitoring port pairs on the Sensor. providing fail-open functionality. Sensors with FE ports contain an internal tap. (It does not need a reboot if the layer2 mode assert command was used to put the Sensor into L2 mode). Caution 4: A very brief link disruption might occur while the links are renegotiated to place the Sensor back in in-line mode. without passing to the detection engine. disabling the ports will send traffic through the internal tap. Check to see whether your services are still affected. Traffic then continues to flow directly through the Sensor. effectively pulling the Sensor out of the path. the problem could instead be a network issue or a configuration issue.CHAPTER 5 Troubleshooting issues with Sensor When McAfee® Network Security Sensor (Sensor) experiences problems in the in-line mode. Caution 2: A Sensor reboot breaks the link connecting the devices on either side of the Sensor and requires the re-negotiation of the network link between the two devices surrounding the Sensor. while the device is examined elsewhere. • • Caution 1: Note that the Sensor will need to reboot to move out of L2 mode only if the Sensor entered L2 mode because of internal errors. then you have eliminated certain Sensor hardware issues.

manually configure the switchport to 100 Mbps. small database queries may succeed. To troubleshoot this issue. Speed determination issues may result in no connectivity between the Sensor and its network device partners on either side. Manually setting the speed and duplex to full-duplex on only one link partner generally results in a mismatch. Contact Cisco's TAC for assistance. one end of the link in full-duplex and the other in halfduplex) may result in performance issues. intermittent connectivity. Symptoms include poor port performance and frame check sequence (FCS) errors that increment on the switch port. verify that the Sensor and the switch/routers are using a valid configuration. if a Web server is talking to a database server through an Ethernet switch with a duplex mismatch. Duplex mismatches A duplex mismatch (for example. creating the mismatch. This common issue results from disabling auto-negotiation on one link partner and having the other link partner default to a half-duplex configuration. This is the reason why speed and duplex cannot be hard-coded on only one link partner.CHAPTER 6 Configuration of Speed and Duplex settings The most common McAfee® Network Security Sensor (Sensor) deployment problems relate to configuration of the monitoring port speed and duplex settings. For example. Sometimes there are duplex inconsistencies between McAfee® Network Security Platform and the switch port. If this action resolves the connectivity problems. and loss of communication. Following sections provide you the best practices related to these issues. you may be running into this issue. If your intent is not to use auto-negotiation. you must manually set both link partners' speed and duplex settings to full-duplex. The show intfport <port> command on the Sensor CLI will help reveal errors. half-duplex. Use the following commands to verify fixed interface settings on some Cisco devices that connect to Sensor: 8 . while large ones fail due to a timeout. Troubleshooting a Duplex Mismatch with Cisco Devices When troubleshooting connectivity issues with Cisco switches or routers. It can also create subtle problems in applications.

intermittent connectivity. 6000 Series • • Router(config)# interface fastethernet slot/port Router(config-if)# speed 100 • Router(config-if)# duplex full When troubleshooting Network Security Platform performance issues with Cisco switches. for example. 9 .McAfee® Network Security Platform 6. When auto-negotiation leaves one end of the link in. view the output of the show port mod/port command. full-duplex mode and the other in half-duplex (also known as a duplex mismatch). 6000 Series (Native) • • set port speed 1/1 100 set port duplex 1/1 full Cisco IOS® for Catalyst 4000. and note the counter information. autonegotiation issues mainly result in a loss of performance. 5000. Auto-negotiation issues Auto-negotiation issues typically do not result in link establishment issues. Generally these errors are not fatal—traffic still makes it through— but locating and fixing them is a time-waster. errors and re-transmissions can cause unpredictable behavior in the network. and loss of communication. This can cause performance issues.0 Configuration of Speed and Duplex settings Cisco PIX® Firewall • interface ethernet0 100full Cisco CSS 11000 • • interface ethernet-3 phy 100Mbits-FD Cisco Catalyst® 2900XL. Instead. 3500XL Series (Hybrid) • • • interface FastEthernet0/2 duplex full speed 100 Cisco Catalyst 4000.

Network Security Platform Configuration 10/100 port Speed/Duplex Configuration of Switch Speed/Duplex Resulting Sensor Speed/Duplex Resulting Catalyst Speed/Duplex Comments 100 Mbps Full-duplex 1000 Mbps Full-duplex No Link No Link Neither side establishes link.3u for 10/100 Mbps auto-negotiation (such as auto-polarity or cabling integrity) can also lead to hardware incompatibility and other issues. Vendor-specific advanced features that are not described in IEEE 802. 100 Mbps Full-duplex 100 Mbps Full-duplex 10 Mbps Half-duplex AUTO 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Full-duplex 100 Mbps Half-duplex 1000 Mbps Full-duplex AUTO 100 Mbps Full-duplex 100 Mbps Half-duplex 10 Mbps Half-duplex 1000 Mbps Half-duplex No Link No Link 10 . and no operational issues should exist. • • Problems may arise when vendor switches/routers do not conform exactly to the IEEE specification 802. if the switch used with the Sensor adheres to IEEE 802. due to speed mismatch Duplex Mismatch 1 Correct Manual Configuration2 Link is established. hardware incapability. but switch does not see Fast Link Pulse (FLP) and defaults to 10 Mbps halfduplex.3u. Valid Auto-negotiation and Speed Configuration settings The table below summarizes all possible settings of speed and duplex for Sensor and switch ports. Neither side establishes link. or software defects. due to speed mismatch.McAfee® Network Security Platform 6.0 Configuration of Speed and Duplex settings Situations that may result in Auto-negotiation issues Auto-negotiation issues with the Network Security Platform Sensor may result from nonconforming implementation. Generally. auto-negotiation should properly negotiate speed and duplex.3u auto-negotiation specifications and all additional features are disabled.

11 . This is an indication of a half-duplex configuration. or port). This is also an indication of the receive buffer being full.McAfee® Network Security Platform 6. Single Collisions Multiple Collisions This is an indication of a half-duplex configuration. This is an indication of excessive output rates of traffic. This counter should be zero unless there is excessive traffic through the switch. or port). Single collisions are the number of times the transmitting port had one collision before successfully transmitting the frame to the media. duplex mismatch. bad hardware (NIC. FCS FCS error count is the number of frames that were transmitted or received with a bad checksum (CRC value) in the Ethernet frame. Situations such as excessive collisions and 10 Mb ports cause the transmit buffer to become full. This is also an indication of transmit buffer being full. UnderSize These are frames that are smaller than This is an indication of a bad frame 64 bytes (including FCS) and have a generated by the connected device. Xmit-Err Rcv-Err This is an indication that the receive buffer is full. the Out-Lost counter has a direct correlation to the Rcv-Err. This is an indication that the internal transmit buffer is full. or a connected device generating frames that do not end with on an octet and have a bad FCS. duplex mismatch. Increasing speed and moving the link partner to full-duplex should minimize this occurrence. The counter should only increment in situations in which the switch is unable to forward out the port at a desired rate. These are the result of collisions at half-duplex. bad hardware (NIC. cable. These frames are dropped and not propagated onto other ports. or a connected device generating frames with bad FCS. Multiple collisions are the number of times the transmitting port had more than one collision before successfully transmitting the frame to the media. cable. These are the result of collisions at half-duplex.0 Configuration of Speed and Duplex settings Explanation of CatOS show port command counters Counter Description Possible Causes Alignment Errors Alignment errors are a count of the number of frames received that do not end with an even number of octets and have a bad CRC. good FCS value. In some switches. This is an indication of excessive input rates of traffic.

If either device does not support Gigabit auto-negotiation.McAfee® Network Security Platform 6. Excessive Collisions Carrier Sense Carrier sense occurs every time an Ethernet controller wants to send data and the counter is incremented when there is an error in the process. Runts This is an indication of the result of collisions. duplex mismatch.3z1998). Gigabit auto-negotiation (no link to connected device) Gigabit Ethernet has an auto-negotiation procedure that is more extensive than that which is used for 10/100 Mbps Ethernet (per Gigabit auto-negotiation specification IEEE 802. configuration issue. Giants These are frames that are greater than This is an indication of faulty 1518 bytes and have a bad FCS hardware. The two devices that cause the late collision never see that the other is sending until after it puts the entire packet on the network. They are only detected during transmissions of packets longer than 64 bytes. or switch port). 12 . or switch port) or a duplex neither side of the connection detects mismatch. Both ends of the link must be set to the same value or the link will not connect. Excessive collisions are the number of This is an indication of over-utilization frames that are dropped after 16 of the switch port at half-duplex or attempts to send the packet resulted in duplex mismatch. dot1q. Its detection is exactly the same as it is for a normal collision.1Q (dot1q). You must either enable or disable link negotiation on both ends of the link. 16 collisions. duplex mode. The Gigabit auto-negotiation negotiates flow control. The reason for this occurrence is that the time to propagate the signal from one end of the network to another is longer than the time to put the entire packet on the network. cable. or an ISL value. and remote fault information. Late collisions are detected by the transmitter after the first time slot of the 64-byte transmit time occurs. a collision. or an Inter-Switch Link Protocol (ISL) configuration issue. cable. These are frames smaller than 64 bytes with a bad FCS value This is an indication of faulty hardware (NIC. it just happens later than it does for a normal collision.0 Configuration of Speed and Duplex settings Counter Description Possible Causes Late Collisions A late collision occurs when two This is an indication of faulty hardware devices transmit at the same time and (NIC. IEEE 802. disabling Gigabit autonegotiation forces the link up.

to use this or another McAfee Network Security Platform-provide policy as a starting point. System Status Monitoring Guide. AOL IM is allowed traffic on the network. and 13 . The “Default Inline IPS’ policy can be changed at the Root Admin level. Typically. the next decision is whether to disable the corresponding attack altogether OR apply a particular attack filter to that attack that will disable alerting for a particular IP address or range of IP addresses. Rather than disable the alert altogether. where each method is used to detect an attempt to exploit a particular vulnerability in a system. at the beginning of the tuning process. or more generic detection methods that aid in detecting unknown exploits for the vulnerability. Note: As you interact with Network Security Platform policies. you encounter the term “attack”. An appropriately tuned policy will reduce false positives.McAfee® Network Security Platform 6. thresholds. then there might not be a need to alert on AOL IM setup flows. anomaly profiles. it is a best practice to implement the latter. McAfee recommends. These signatures and checks may contain very specific means for identifying a specific known exploit of the vulnerability. but to tune these into segment-tailored custom policies. If. the following best practices can make tuning more efficient and effective.” Network Security Platform defines an attack as being comprised of one or more signatures. where appropriate. an SMS server may be generating the alert Netbios: Copy Executable file attempt during the legitimate transfer of login scripts. for instance. it will be evident that your network or security policy will affect the overall level of alerts.1. Many of the top alerts seen on the initial deployment of a Sensor will be common false positives seen in many environments. Analyzing high-volume attacks Take attacks that are generating the most alerts (use Consolidated View in Threat Analyzer) and investigate their legitimacy.0 Effective Policy Tuning practices CHAPTER 7 Effective Policy Tuning practices As of McAfee® Network Security Manager (Manager) software version 2. have the McAfee® Network Security Platform 'Default Inline IPS' policy loaded on all interfaces. Managing Attack filters When a particular alert is declared as false positive. Though each network environment has unique characteristics. For instance. see Consolidated View. These tailored policies can be either cloned versions of Network Security Platform pre-configured policies or custom-built policies that employ custom rule sets. not “signature. In almost all cases. For more information. all McAfee® Network Security Sensors (Sensors) on initial deployment. or correlation rules.

see Managing DoS Learning Mode profiles on a Sensor. The IPS Sensor configuration report will deliver reports that list attack filters that have been applied and attacks that have been otherwise customized. During this period it is not unusual to see DoS alerts associated with normal traffic flows (for example. before tuning DoS attacks. There is no need to re-learn a profile when network traffic increases or decreases naturally over time (for example. For more information on Sensor learning modes. 14 . see Managing Attack Filters and Attack Responses. The Report section can be used to assist the documentation process.0 Effective Policy Tuning practices cancel the possibility of finding a real attack of this nature. you change the CIDR block of a subinterface) that causes a significant sudden traffic change on an interface. Note: For more information on attack filters. Learning profiles in DoS attacks It is a best practice to let the Sensors learn the profiles of the particular segments they are monitoring. The learning process takes two days. IPS Configuration Guide. It is a best practice to have the Sensor re-learn the profile when there is a network change (that is. the particulars of the profile (number of SYNS.McAfee® Network Security Platform 6. since the Sensor can automatically adapt to it. This involves setting thresholds manually for the type of segment characteristics that are learned in Learning Mode. If the Sensor does not re-learn the new environment. an e-Commerce site that is getting more and more customers. it may issue false alarms or fail to detect actual attacks during a time period when it is adapting to the new network traffic conditions. and so on) can be viewed per Sensor. we recommend that you create an attack filter for the SMS server and apply it to the attack. DoS SYN flood alerts reported outbound on a firewall interface to the Internet). thus its Web traffic increases in parallel). Implementing this mode successfully is critically dependent on detailed knowledge of the segments that the particular Sensors are monitoring. IPS Configuration Guide. you move the Sensor from a lab or staging environment to a production environment) or a configuration change (that is. DoS detection can also be implemented using the Threshold Mode. so that the filter can be applied to any Exploit or Reconnaissance attack. After a profile has been learned. ACKS. It is also a best practice to document all your tuning activities. Every attack filter created is globally stored. This is Learning Mode operation.

but disable alerting. preventing DoS attacks and attacks against the firewall is crucial.CHAPTER 8 Response Management When McAfee® Network Security Sensor (Sensor) detects an activity which violates a configured security policy. Critical attacks like buffer overflows and DoS attacks require responses in real time. if you are monitoring outside of a firewall in in-line mode. Will drop a detected attack packet and all subsequent packets in the same flow. lest you enable blocking for an attack. Developing a system of actions. If the Sensor is monitoring the network outside of the firewall in in-line mode. Sensor Response Actions There are multiple Sensor actions that are available for configuration per attack. Remember that response actions are decoupled from alerting. Proper configuration of responses is crucial to maintaining effective protection. IPS Quarantine can be enabled per attack in the Policy Editors. a better understanding of the potential attack purpose can be determined. and logs based on specific attacks or attack parameters (such as severity) is recommended for effective network security. Note 2: For more information on IPS Quarantine. These include: • • Dropping Alert Packets: Only works in in-line mode. see Sensor Actions. causing the attack to be blocked without your knowledge. since McAfee® Network Security Platform can be customized to protect any zone in a network. Note 1: For more information on other Sensor actions. are best logged and analyzed as the impact is not immediate. such as scans and low-impact well-known exploits. it is important not to set the policies and responses so fine that they disrupt the flow of traffic and slow down the system. while scans and probes can be logged and researched to determine compromise potential and the source of the attack. Thus. IPS Configuration Guide. knowing what needs to be protected can help to determine the response type. For example. Other suspicious traffic intended for the internal network. IPS Quarantine: Sensor will quarantine/remediate a host as per the configurations in McAfee® Network Security Manager (Manager) and the Sensor monitoring ports. a preset response from the Sensor is integral to the protection or prevention process. alerts. IPS Configuration Guide. 15 . see IPS Quarantine settings in the IPS Sensor. In this case. Pay particular attention to this with the Recommended For Blocking (RFB) category of attacks.

Collaborative rule creation. An include rule (which should always start a rule set) is a set of parameters that encompass a broad range of well-known attacks for detection. Each include rule added. create the first rule in the set with the Exploit category. • Note: For more information on rule set creation. that are rarely or never seen in a zone of your network. Sendmail as the application. Each rule in a set is either an include rule or an exclude rule. protocols. Follow this with multiple exclusion rules that strip away protocols. The first method is general-to-specific. Each criterion must be matched in order for an alert to be triggered. After this. For example. Unix as the OS. applications and protocols. Proper creation of rule sets is essential for eliminating false positives and ensuring maximum protection on your network. combination that needs to be detected. protocol. IPS Configuration Guide. and so forth in the same manner. The second method is collaboration: Create multiple include rules within one rule set for each category. These best practices can assist while creating rules sets in the McAfee® Network Security Manager (Manager). application.CHAPTER 9 Creating Rule sets A rule set is configured based on attack category. severities. broadens the scope of the detection. create one or more exclude rules to strip away specific operating systems. operating system. Next. thus focusing the rule set on the environment where it will be enforced. operating systems. and SMTP as the protocol. et cetera. 16 . Best methods for rule set creation There are two best practice methods employed for creating rule sets. and benign trigger probability options. An exclude rule removes elements from the include rule in order to focus the policy's rule set. applications. • General-to-specific rule creation. Windows 2000. WindMail. start with an include rule for all Exploit category attacks. et cetera. et cetera. For example. severity. create another include rule for Exploit. see Managing Rule Sets. Start with an include rule that covers a broad range of operating systems.

keeping the configuration consistent.CHAPTER 10 Port clustering on Asymmetric networks Port clustering. enables multiple ports on a single McAfee® Network Security Sensor (Sensor) to be grouped together for effective traffic monitoring. 17 . and a complete transmission may be received on one segment. Thus keeping state of asymmetric transmissions is essential for successfully monitoring the traffic. All of the ports that make up the interface are configured as one logical entity. see Port clustering (interface groups). Once configured. Getting Started Guide. Interface groups normalize the impact of traffic flows split across multiple interfaces. referred to as Interface Groups in the Manager interface. Asymmetric networks are common in load balancing and active/passive configurations. It is a best practice to implement a port clustering configuration when dealing with asymmetrically routed networks. an interface group appears in the System Configuration tool's Resource Tree as a single interface node (icon) under the Sensor where the ports are located. Note: For more information on port clustering. thus maintaining state to avoid information loss. but depart on another.

IPS Configuration Guide. Protocols such as H. are not supported. are not supported. IRC. or negotiate ports that do not follow a standard.CHAPTER 11 Access Control Lists (ACLs) Note the following points while working with Access Control Lists or ACLs: • You cannot set explicit ACL permit rules for protocols that negotiate ports dynamically. For RPC services. However. such as statd and mountd. TFTP. There is a limit on the number of ACL rules that can be supported by a McAfee® Network Security Sensor (Sensor). see Access Control Lists. KaZaA. that use dynamic ports. and so on. 18 . but not its constituents. and RPC services. you can configure explicit permit and deny rules for RPC as a whole. which negotiate the data channel separately from the control channel. you can configure ACLs to explicitly deny these protocol instances by denying the fixed control port. Network Security Platform detects use of and attacks in such programs as Yahoo Messenger. with the exception of FTP. The following table specifies the rule limit for ACLs: Sensor ACL rule limit • • • • I-4010 I-4000 I-3000 I-2700 I-1400 I-1200 1000 1000 1000 400 100 50 Sensor ACL rule limit M-8000 M-6050 M-4050 M-3050 M-2750 M-1450 M-1250 1000 1000 1000 1000 400 100 50 Note: For more information. However. Protocols or services. you can explicitly deny these protocol instances by denying the fixed control port. An alternative option for denying protocols that use dynamic ports is to configure IDS policies to drop the attacks that are detected in such transmissions. such as instant messaging and peer-to-peer communication.323 and Netmeeting.

McAfee® Network Security Platform 6.0 SSL best practices CHAPTER 12 SSL best practices Note that there is a performance impact when using the SSL decryption feature. SSL Connections / Sec. Throughput 300 150 Mbps 400 200 Mbps 800 400 Mbps 800 400 Mbps 19 . Throughput 325 85 Mbps 600 155 Mbps 800 200 Mbps 1200 310 Mbps SSL only traffic . SSL only traffic .1 get page requests per TCP connection with a 5K response each 1024-bit RSA 128-bit ARC4 I-2700 I-3000 I-4000 I-4010 Max.throughput • • • • Session resumption for 4 out of 5 TCP connections 5 HTTP 1. Refer the following sections for the SSL throughput measurements and test methodologies.1 get page requests per TCP connection with a 10K response each 1024-bit RSA 128-bit ARC4 I-2700 I-3000 I-4000 I-4010 Max. SSL Connections / Sec.throughput • • • • Session resumption for 4 out of 5 TCP connections 5 HTTP 1.

SSL Connections / Sec.1 Throughput Total Throughput 400 100 Mbps 1550 Mbps 1650 Mbps 800 200 Mbps 780 Mbps 980 Mbps I-4010 Max.1 Throughput Total Throughput 200 50 Mbps 860 Mbps 910 Mbps 400 105 Mbps 475 Mbps 580 Mbps I-4000 Max.8 Gbps SSL traffic mixed with HTTP 1.0 SSL best practices M-2750 M-3050 M-4050 M-6050 M-8000 Max. SSL Throughput HTTP 1.1 get page requests per TCP connection with a 5K response each 1024-bit RSA 128-bit ARC4 I.1 traffic • • • • Session resumption for 4 out of 5 TCP connections 5 HTTP 1. SSL Connections / Sec. SSL Connections / Sec. Throughput 550 250 Mbps 1300 600 Mbps 2700 1200 Mbps 4500 2 Gbps 8500 3.McAfee® Network Security Platform 6. SSL Throughput HTTP 1. SSL Connections / Sec.1 Throughput Total Throughput 400 100 Mbps 1740 Mbps 1840 Mbps 800 200 Mbps 860 Mbps 1060 Mbps 20 . SSL Throughput HTTP 1. SSL Throughput HTTP 1.1 Throughput Total Throughput 100 25 Mbps 475 Mbps 500 Mbps 200 50 Mbps 350 Mbps 400 Mbps I-3000 Max.2700 Max. SSL Connections / Sec.

8 Gbps Supported SSL functionalities Following SSL functionalities are supported.McAfee® Network Security Platform 6. SSL Throughput HTTP 1.35 Gbps M-4050 Max. SSL Throughput HTTP 1. 21 .1 Throughput Total Throughput 220 100 Mbps 1. SSL Throughput HTTP 1.0 SSL best practices M-2750 Max. SSL Throughput HTTP 1. SSL Throughput HTTP 1.1 Throughput Total Throughput 880 440 Mbps 4 Gbps 4.7 Gbps M-6050 Max.1 Throughput Total Throughput 1750 800 Mbps 8 Gbps 8.5 Gbps 2.4 Gbps M-8000 Max. SSL Connections / Sec.2 Gbps 1. SSL Connections / Sec. SSL Connections / Sec.1 Throughput Total Throughput 440 200 Mbps 2. SSL Connections / Sec.1 Throughput Total Throughput 110 50 Mbps 500 Mbps 550 Mbps M-3050 Max. SSL Connections / Sec.

McAfee® Network Security Platform 6.0 SSL best practices Supported Web servers SSL decryption is supported for the following web servers: • • Microsoft Internet Information Server (IIS) Apache Supported cipher suites The following SSL cipher suites (as named in their respective RFCs) are supported: SSLv2 cipher suites • SSL_CK_RC4_128_WITH_MD5 • SSL_CK_RC4_128_EXPORT40_WITH_MD5 • SSL_CK_DES_64_CBC_WITH_MD5 • SSL_CK_DES_192_EDE3_CBC_WITH_MD5 SSLv3/TLS cipher suites • • • • • • • • • SSL/TLS_NULL_WITH_NULL_NULL SSL/TLS_RSA_WITH_NULL_MD5 SSL/TLS_RSA_WITH_NULL_SHA SSL/TLS_RSA_WITH_RC4_128_MD5 SSL/TLS_RSA_WITH_RC4_128_SHA SSL/TLS_RSA_WITH_DES_CBC_SHA SSL/TLS_RSA_WITH_3DES_EDE_CBC_SHA SSL/TLS_RSA_WITH_AES_128_CBC_SHA SSL/TLS_RSA_WITH_AES_256_CBC_SHA SSLv3/TLS cipher suites Unsupported SSL functionalities The following SSL functionalities are not supported: • • iPlanet Web servers Diffie-Hellman ciphers (McAfee recommends that you disable acceptance of DiffieHellman requests on the SSL Web server to ensure that Network Security Platform is able to decrypt the traffic) Compression in the SSL records (a negotiable option in SSLv3 and TLS) PCT (Microsoft's extension to SSLv2) • • 22 .

HTTP response processing typically provides little value because all HTTP response traffic is sourced from trusted servers. You are serving Web content to external clients. changes in aggregate Sensor performance will depend on the proportion of HTTP traffic to other traffic on the link being monitored. Since HTTP requests are typically <= 1/10th of the response size. and do not wish to serve attacks embedded in HTTP response traffic . The things to note about the test are given below. To minimize the potential performance impact on the McAfee® Network Security Sensor (Sensor). Usually. In these deployments. In these environments. • Tests for enabling HTTP Response Traffic The test results provided in the next two sections illustrate potential impact of enabling response processing traffic. we recommend that you enable HTTP response processing on the minimum number of ports and in only the required directions to achieve your protection goals. The test sends HTTP request continuously at maximum load.enable HTTP response processing in both directions. occasionally peaking at maximum capacity. Changing the HTTP response processing setting does not change the Sensor performance for any other protocol.enable HTTP response processing for outbound traffic only.enable HTTP response processing for inbound traffic only. • The test involves only HTTP traffic. When not running at maximum load. The test results reflect performance at sustained load. Therefore. • • • 23 . the combined HTTP request and response traffic processed by Sensors in real deployments is typically less than that shown in the tests. which do not usually transmit hostile content due to the security measures taken. customers can consider selectively enabling HTTP response processing to better optimize their network.CHAPTER 13 Sensor HTTP Response Processing deployment HTTP response processing is disabled by default. expected to occur in deployments protecting large Web server farms. Typical real-world deployments do not have equal amounts of HTTP request traffic and response traffic in both directions through the Sensor. there is significant amount of request traffic in one direction and response traffic in the opposite direction. Real-world networks are typically loaded. Some examples of HTTP response processing deployment: • • You want to protect a bunch of clients on your internal network . The test environment was created to illustrate the likely worst-case performance impact. You want to protect both internal clients as well as the Web content you are serving to external clients. the Sensor can absorb larger bursts without significant impact. The test sends equal HTTP request and response loads in both directions through the Sensor. but typically running at significantly lower throughput. You can enable it for each traffic direction on an interface pair.

HTTP Response processing results for I series Sensors Refer the following table for I-series Sensor performance numbers with HTTP response processing: I-4010 I-4000 I-3000 I-2700 I-1400 I-1200 .5 HTTP 1.1 get page requests per TCP connection with a 10K response each 2 Gbps 1. dependent on the traffic being inspected and some environments could see a reduction in performance as significant as the test results indicate.McAfee® Network Security Platform 6. The exact impact is. the impact of enabling HTTP response processing is not noticed. For Sensor performance numbers under the following conditions: • • HTTP response processing enabled/disabled and 5 HTTP 1. of course.HTTP Response Scanning Enabled for outbound direction .5 HTTP 1.1 get page requests per TCP connection with a 10K response each sent in one direction.1 get page requests per TCP connection with a 10K response each . size of a response page sent to the client by the sites or applications that are typically accessed.0 Sensor HTTP Response Processing deployment The net result of all of these factors is that in typical networks. The factors to take into account include: • • • proportion of HTTP traffic to other protocols relative amount of HTTP requests and responses in each direction and.HTTP Response Scanning Disabled .78 Gbps 1 Gbps 550 Mbps 195 Mbps 97 Mbps 1 Gbps 1 Gbps 680 Mbps 430 Mbps 160 Mbps 75 Mbps HTTP Response processing results for M-series Sensors Refer the following table for M-series Sensor performance numbers with HTTP response processing: 24 .

0 Sensor HTTP Response Processing deployment M-8000 M-6050 M-4050 M-3050 M-2750 M-1450 M-1250 .4 Gbps 2.1 get page requests per TCP connection with a 10K response each 10 Gbps 5 Gbps 3 Gbps 1.McAfee® Network Security Platform 6.8 Gbps 2 Gbps 1 Gbps 500 Mbps 200 Mbps 100 Mbps 25 .HTTP Response Scanning Disabled .5 HTTP 1.5 Gbps 600 Mbps 200 Mbps 100 Mbps 5.HTTP Response Scanning Enabled for outbound direction .1 get page requests per TCP connection with a 10K response each .5 HTTP 1.

) As the 'All Tables' and 'Audit and Alert Tables' options can be rather large in size (depending upon the amount of alert data in the database) these types of backups should be saved off the Manager server. Also note that there is no change in database SQL query behavior if online database tuning is disabled. database tuning). contact Technical Support. if you are using an agent that queries the database. • • • 26 . Your configuration tables are saved by default once a week on Saturday. alerts. your agent may attempt to interact with these tables during tuning. There is a remote chance that during the transition to the temporary tables. Warning: A database left untuned can.CHAPTER 14 Database maintenance McAfee recommends the following best practices for database backup and tuning: • Perform regular manual backups of your database using the Backup feature in the McAfee® Network Security Manager (Manager) software. Database backups are cumulative and the size of a backup file can become quite large. the SQL query will result in an error. and audits. over time. Further information on the impact of online database tuning of the Manager database will be sent to the third-party vendors that are directly accessing this database. Saving the 'All Tables' settings monthly is strongly recommended. as disk fragmentation can lead to database inefficiency. archives. simply retry the query. • • • • Backup of data and configurations For the back up of McAfee® Network Security Platform data and configurations. set a time for each that is unique and is a minimum of an hour after/before other scheduled actions. (Be sure to schedule this at a time when other processes will not be running concurrently. • Online database tuning operation causes the creation of temporary alert and packet log tables. following best practices are recommended: • • • Back up Manager data either within the Manager server (McAfee Network Security Platform\Backups folder) or preferably on external media. file maintenance. When scheduling certain Manager actions (backups. Perform regular file maintenance to prevent disk space issues. Make a regular practice of defragmenting the disk of the Manager server. Do not run scheduled actions concurrently. Note: For more information on tuning your database. lead to data corruption. see Manager Server Configuration Guide. If a SQL query error occurs. Tune your database at regular intervals using the online tuning tools. Protect backups from tampering by creating a digital fingerprint of the file using a hash function such as MD5 or SHA-1. including configurations. Back up all information. If you have any specific questions. Backing up config tables weekly is recommended. Implement a schedule for backups using the Backup scheduler.

Manager Server Configuration Guide. Save actual configurations of Sensors (not just the config tables) using the Export option under the Sensor_Name tab. The 'Config Tables' option backs up only tabled information relating to configured tasks.McAfee® Network Security Platform 6. Save actual Sensor configurations weekly. This is set within the Backup Scheduler action. Tip 2: For more information on database backup. 27 . see Database backup and Recovery.0 Database maintenance • • • Test restoration of backups periodically to ensure that a backup was successful and valid. The best way to do this is to perform a “test” restore of the backup on a secondary. This creates an XML file (no attempt to read this file should be made) that can be imported to any Sensor of the same type in the future. non-production Manager. Manager Server Configuration Guide. Tip 1: For more information on backup methods. see Backing up data and settings. This option is enabled by default to occur every Saturday night.

bat utility does the following: • • • • • Defragments tables where rows/columns are split or have been deleted Re-sorts indexes Updates index statistics Computes query optimizer statistics Checks and repairs tables 28 . Scripts for disk space maintenance If you have a large amount of data and wish to do your tuning offline. see The lifecycle of an alert. using the Alert and Packet Log Archival feature.CHAPTER 15 Alerts and Disk space maintenance Disk space maintenance is an important task that must be completed to ensure efficient running of the McAfee® Network Security Manager (Manager). Manager Server Configuration Guide. Note that there is currently a 4 GB size limitation for a single archive file. For more information.bat and dbtuning. it is a best practice to use the purge. Dbtuning. A best practice suggestion is to wait for 97 days of data and then on a recurring 7-day period run the purge.bat (force the tuning of the database) scripts. McAfee recommends that you archive your alert data monthly. use the online tools. Archiving alerts Archive your alerts and packet logs regularly. To do this you must stop the Manager and run the scripts. but ensure that you do not have another process running concurrently during the tuning. In order to develop best practices for database maintenance it is important to understand the lifecycle of an alert. To tune while the Manager is running.bat (forces the deletion of old alerts) and dbtuning.bat—this will delete alerts already marked for deletion (from the Alert Viewer) as well as alerts older than 90 days. Manager service stopped) to release the lock from the database. Getting Started Guide. and that you discard alert and packet log information from your database every 90 days to manage your database size.bat The dbtuning. see Database maintenance and tuning. Note: For more information on Disk Space Maintenance. Scripts have to be run off-line (that is.

or if they have been marked for deletion via the Threat Analyzer tool. These include Diagnostic files. as in 90 days—is entered in the “Scheduled Deletion” column for the Alert & Packet Log Data option. By setting the value to 90 days. Maintenance of this data can be accomplished automatically using the File Maintenance scheduler. Purge. Note: For more information on setting the scheduler for file maintenance. It is a best practice to schedule the deletion of the oldest of these files on an on-going basis.bat The purge. any incident reports that have been generated. Apart from the database data. see Setting a schedule for file maintenance. with all Alert and Packet logs.0 Alerts and Disk space maintenance Purge. which may affect long-term and overall database performance. This can be accomplished using the Maintenance scheduler.bat also offers to automatically start dbtuning. Manager creates a group of administration files that must be maintained regularly. If automatic File Maintenance is used to delete alert and packet log data it is recommended that a large value -such as 90. Alerts and packet logs can be deleted that are older than a specified number of days. 29 . This allows for long-term analysis of alerts and logs without overloading your database with millions of alerts.McAfee® Network Security Platform 6. Using File Maintenance Scheduler Databases can be substantially overloaded. and audit and fault logs.bat immediately after the purge is completed. Manager Server Configuration Guide. all alerts and packet logs older than 90 days are deleted at the weekly maintenance scheduler time.bat utility enables on-demand deletion of alerts and packet log data from your database. DoS files (profiles) and Data Mining files (for Trend Reporting) among others.

Note: For more information on MDR. depending on the quantity of McAfee® Network Security Sensors (Sensors).CHAPTER 16 Manager Disaster Recovery (MDR) best practices A newly created MDR pair does not synchronize for the first 15 minutes after creation. This is by design because. it takes approximately 5 to 10 minutes for the newly formed pair to finish MDRrelated tasks and become stable. 30 . Manager Server Configuration Guide. In most cases. we recommend you wait the 15 minutes and allow the new MDR pair to synchronize automatically. If you have only one or two Sensors. to force the Managers to synchronize. If you return to the user interface of the primary Manager. you can press the Retrieve Configuration button on the Manage MDR page of the secondary McAfee® Network Security Manager (Manager) soon after MDR creation. the details on the Manage MDR page validate the information seen on the secondary. see MDR communication. however.

CRC. Other possible causes of data link errors at full-duplex are bad cables. or vice versa. duplex mismatches. alignment errors. cyclic redundancy checks (CRC). FCS.CHAPTER 17 Performance issues Most performance issues are related to switch port configuration. 31 . If the link is operating at full-duplex. or runt counters are incrementing. alignment. Sniffer trace A Sniffer details packet transfer. or software or hardware issues. performance degradation may be noticeable. a one percent ratio of errors to total traffic is acceptable for half-duplex connections. and runt counters should be minimal. Half-duplex setting When operating with a duplex setting of half-duplex. In half-duplex environments. and data link errors. check for a duplex mismatch. Collisions can cause runts. and loss of connection. the collision counter is not active. If the ratio of errors to input packets is greater than two or three percent. For more information. and alignment errors. Duplex mismatch is a situation in which the switch is operating at full-duplex and the connected device is operating at half-duplex. a faulty switch port. Generally. intermittent connectivity. resulting in fragmented frames. Sniffer trace analysis reveals every packet on the wire and pinpoints the exact problem. and that it is useful to monitor (“span”) ports rather than spanning VLANs when troubleshooting switch connectivity issues. runts. Note that it may be important to obtain several Sniffer traces from different ports on different switches. alignment. link up/down situations. Full-duplex setting When operating at full-duplex. and collisions are normal. FCS. If the FCS. see also Configuration of Speed and Duplex settings (on page 8). which are caused when the frame is not completely copied to the wire. it is possible for both the switch and the connected device to sense the wire and transmit at exactly the same time. Data link errors Many performance issues may be related to data link errors. The result of a duplex mismatch is extremely slow performance. and thus a Sniffer trace analysis can help pinpoint switch and McAfee® Network Security Platform performance or connectivity issues when the issues persist after you have exhausted the other suggestions in this document. resulting in a collision. some data link errors such as FCS. Excessive errors usually indicate a problem.

consider acknowledging (or purging) all existing alerts each time you replace reports. Replacing an old report with a new one might result in similar alerts having different relevance values. This prevents the Vulnerability Manager server being denied network access. To prevent this: Create ACLs to exclude all traffic from the Vulnerability Manager server from attack inspection. it may correctly draw different conclusions for each.McAfee® Network Security Platform 6. if Network Security Platform uses an initial scanner report to analyze one alert and an updated scanner report to analyze the next. See the NAC Configuration Guide for information. This will help ensure the assessment is accurate. Replace old reports with new reports on a routine basis (weekly or monthly). IPS Configuration Guide. and render VA integration ineffective.0 Vulnerability Assessment CHAPTER 17 Vulnerability Assessment McAfee® Network Security Platform recommends the following while performing Vulnerability Assessment: • • Always use the latest signatures available for your vulnerability assessment (VA) software. To avoid confusion. 32 . This will help increase the probability that a relevancy status of "Unknown" really means that the attack is not relevant. Integration Guide. • • • Note: For more information on vulnerability assessment using Network Security PlatformMcAfee Vulnerability Manager integration. the Sensor may consider it as attack traffic and take the corresponding response action such as quarantining the Vulnerability Manager server. then add the Vulnerability Manager server to the NAC Exclusions list. reports can become obsolete quickly. Where possible. see Configuring ACL rules. For example. Given the frequency with which new attacks appear. For information on ACLs. If you have configured Network Access Control (NAC) or IPS Quarantine. If the scan traffic between the Vulnerability Manager server and the hosts being scanned passes through a Sensor monitoring port. see Integration with McAfee Vulnerability Manager. scan all hosts you expect McAfee Network Security Platform to protect.

000 30.000 64 600 Mbps 250.000 5.000 1.250 25.000 1. IPS Configuration guide.000 5.000 6.000 128.000 64 1 Gbps 500.000 1.000 100. 33 . Maximum Type I-4010 I-4000 I-3000 I-2700 I-1400 I-1200 Aggregate Performance Concurrent connections Connections established per sec.000.000 6.000.000 5.000 50 For more information on computing ACL.500 300 250.000 187.000 2.CHAPTER 19 I-series Sensor capacity by model number The following table lists McAfee® Network Security Sensor (Sensor) limitations by category and by Sensor model.000 1.000 3.000 128.000 50.000 10.000 64.000 120 64.000. see Viewing ACL descriptions using Effective ACL rules.000 400 32 64 64 40.000 100 83.000 60.000 1.000 5.000 3.000 500.000 100 300 254 100.000 100 16 32 32 20.000 128.000 750.000 64 2 Gbps 1.000 254 100.000 100.000 32.000 1.000 375.000 1.000 25.000 50.000 NA NA 100 Mbps 40.000. Concurrent SSL Flows Number of SSL keys that can be stored on the Sensor Virtual Interfaces (VIDS) per Sensor VLAN / CIDR Blocks per Sensor VLAN / CIDR Blocks per Interface Customized attacks Attack filters Default number of supported UDP Flows Supported UDP Flows DoS Profiles SYN rate (64-byte packets per second) ACL Rules (refer to note below) 2 Gbps 1.000 NA NA 1.000 25.000 64 200 Mbps 80.000 3.000 100.000 25.000 100.000 16.000 1.000 254 100.000 254 100.000 750.

0 I-series Sensor capacity by model number Note for customized attacks The signature set push from McAfee® Network Security Manager (Manager) to a Sensor will fail if the number of customized attacks on the Sensor exceeds the customized attack limit. The number of customized attacks can increase due to: • • • Modifications done to attacks on a policy by users Recommended for blocking (RFB) attacks User created asymmetric policies Example: How numerous customized attacks are created in asymmetric policies. 34 . • The All-inclusive with Audit rule set has 2204 exploit attacks. You will see that: • The File Server rule set has 166 exploit attacks. The total number of customized attacks for this policy is 2204 – 116 = 2038 customized attacks. Create a new policy. b. Set the Outbound rule set to "All-inclusive with Audit rule set".McAfee® Network Security Platform 6. Set the Inbound rule set to "File Server rule set". c. a.

500 35 .000 100.000 40.000 100.144 Sensor Default number of supported UDP Flows Supported UDP Flows 400.000 375.000 100.000 131.000 20.000 64 64 64 64 NA NA NA 1.000 20.000 2 Gbps 250.000 1.000 400.000 25.000 300 64 32 300 254 254 254 254 254 64 32 254 100.000 200.500.000 18.000 100.000 65.000 36.000 200 Mbps 80.000 30.000 4.144 50.114 100.000 750.000 100.000 187.000 Attack filters per 128.5 Gbps 750.000 100.000 10.000 1.000 VIDS Attack filters per 262.000 NA NA NA Number of SSL 64 keys that can be stored in Sensor Virtual Interfaces (VIDS) per Sensor VLAN / CIDR Blocks per Sensor VLAN / CIDR Blocks per Interface Customized attacks 1.000 NA NA NA 25.000 2.000 150.000 262.072 25.CHAPTER 20 M-series Sensor capacity by model number Maximum Type M-8000 M-6050 M-4050 M-3050 M-2750 M-1450 M-1250 N-450 Aggregate Performance Concurrent connections Connections established per sec.000 3.000.144 400.000 2.000 128.000 100.000.500 60.000 100 Mbps 40.000 262.768 5.000 100 32 16 100 3.000 75.000 262.000 1.000 187. SSL Flow count maximum 10 Gbps 5 Gbps 3 Gbps 1.500.000 3.000.000 60.000 32.000 1.000 100.000 66.000 4.000 120.536 10.000 3.000 3.000 600 Mbps 250.

000 100 200.000.000 2.000 1.000 NA NA 5.000 300 600.500.000 5.McAfee® Network Security Platform 6.0 M-series Sensor capacity by model number Maximum Type M-8000 M-6050 M-4050 M-3050 M-2750 M-1450 M-1250 N-450 DoS Profiles SYN rate (64byte packets per second) ACL Rules (refer to note below) 5.000.000 1.000 1. 36 .000 1.000 400 100 50 400 Note: SSL decryption is not supported on M-1450. The number of supported SSL flows on a Sensor directly impacts the number of TCP flows that can be processed simultaneously.000 5.000 120 250.500.000 1. M-1250 and N-450 Sensors.000 2.000 5.

inline failclose (CLI reboot or reboot due to error and watchdog on) Ports are admin disabled and put in bypass before the Sensor reboots. No negotiation with peer devices.inline failopen Port Speed/Duplex Auto negotiation Sensor Power off . Ports remain enabled fail-close. Sensor Power off .inline failclose Link Failure . Dongles not required Dongles not required for both ports to fail-close SPAN Inline fail-close Inline fail-open (Default) Inline fail-open (Active Fail-open Kit) Link Failure . Ports are not admin disabled and traffic is disrupted 10/100. Ports remain enabled fail-close.Supported with ports configured in failclose (no dongles) close (no dongles) Ports fail-close and traffic is disrupted. No negotiation with peer devices. Dongles required Dongles required on both A and B ports to fail-close External tap is supported. No traffic is disrupted. no support for internal tap. Traffic is disrupted till then.CHAPTER 18 Comparison Between I-1200/I-1400 and M-1250/M-1450 FE ports Operating Condition/Mode I-1200/I-1400 M-1250/M-1450 TAP Internal and external tap are supported.Does not require external passive Failopen Kit open Kit Supported with ports configured in fail. Warm reboot . Ports are admin disabled.) Ports are enabled and in the down state till the Sensor starts rebooting. Full/Half only for 10/100 Supported and can be configured from the the Manager Ports fail-close and traffic is disrupted. fail-open (bypass) with no dongles Ports fail-open (bypass).inline failopen (CLI reboot or reboot due to error and watchdog on) Warm reboot . traffic disruption till the Sensor is up Ports fail-close and traffic is disrupted.inline fail-close Does not require external passive Fail. and no traffic is disrupted.inline fail-open Ports fail-open. traffic disruption till the Sensor is up 37 . put into bypass. and no traffic is disrupted 10/100/1000. no traffic disrupted (must not have dongles connected. Full/Half Not supported Ports fail-close with dongles connected. put into bypass.

up Red .enabled but down Gray . No support to control fail-open/bypass Has support to control failoperation open/bypass operation I-1200 . Configurable through CLI through CLI) The color codes are: • • • • Yellow. OFF indicates down and traffic is disrupted Port link LED interpretation .0 Comparison Between I-1200/I-1400 and M-1250/M-1450 FE ports Operating Condition/Mode I-1200/I-1400 M-1250/M-1450 Resetconfig Restores to default configuration (inline fail-open) and reboots Normal is green and indicates up. OFF indicates down and not necessarily bypass OFF indicates down and traffic is disrupted Options to either restore defaults or to retain the current port configuration are available Green indicates up and inline.inline failopen Port link LED interpretation .inline fail-open Port link LED interpretation during reboot/Sensor power down .inline fail-close OFF indicates . Front panel LED for Not present Normal/Bypass operations .bypass and no traffic disrupted. Always on (green). normal operation.TAP Link Events Port density Green indicates up and inline.McAfee® Network Security Platform 6.1A/1B. OFF indicates down and traffic disrupted.up Red .inline fail-close Front panel LED for Not present Normal/Bypass operations . Always on (green). OFF indicates bypass.SPAN Front panel LED for Not present Normal/Bypass operations .link status color coding No support(Supported in I1200 and not Supported by default (not configurable in I1400). I-1400 .disabled and down The color codes are: • • • • Yellow . normal operation. OFF indicates bypass and no traffic is disrupted OFF indicates down.not active Green . normal operation. traffic is disrupted.enabled but down Gray . OFF indicates bypass.1A/1B and 2A/2B 1A/1B through 4A/4B Auto MDIX support The Manager port configuration panel .inline failclose Port link LED interpretation during reboot/Sensor power down . Always on (green).disabled and down (applicable for inline fail-open only) 38 .inline fail-open Front panel LED for Not present Normal/Bypass operations .not active Green .

inline failopen The Manager port status at Link failure .SPAN Red Gray Red Red Red Red 39 .McAfee® Network Security Platform 6.Inline/Bypass status color coding Not present Four separate bypass buttons.inline failclose The Manager port status at Link failure .0 Comparison Between I-1200/I-1400 and M-1250/M-1450 FE ports Operating Condition/Mode I-1200/I-1400 M-1250/M-1450 The Manager port config panel . one button per port pair: • • Green .inline Yellow .bypass The Manager port status at Link failure .

... 4 connectivity issues ..... 28 I in-line mode................... 35 speed and duplex settings ..................................... 7 interface groups ............................... 37 Response Management................ 32...... 25................................................. 6 Layer2 Passthru ......................................................... 23....... 35 Index A auto-negotiation issues .................................................................. 35 H half-duplex setting ........................... 7 sniffer trace .... 33 duplex mismatch .................................... 13 policy tuning practices.............................................. 16 R rule set creation best practices ...................ix V vulnerability assessment best practices. 15.................................................. 35 database management best practices ..... 24. 26 staging sensors......................... 30.............................................................. vi D data link errors ....................... 27........................................................... 8 T technical support............................................................ 19 B backup of data............................................................ 5.................... 11....... 35 HTTP .........P performance issues................................................................................. 20 L large sensor deployment...... 30 S Sensor capacity by model number....................... 8 SSL best practices ............. 37 F File Maintenance Scheduler............... 6 C cabling best practices.......... 10............................... 8 conventions ........................................................................................................... 17 sensor troubleshooting issues .............................. 7 M Manager Disaster Recovery (MDR) best practices 34 ....................... 9.............................................................. 33 full-duplex setting ......................................