Sourcefire 3D System Administrator Guide

Version 4.9.1

Intellectual Property Notices, Disclaimers, and Terms of Use Applicable to the User Documentation. The legal notices, disclaimers, terms of use, and other information contained herein (the “terms”) apply only to Sourcefire, Inc. appliance discussed in the Documentation (“Documentation”) and your use of it. The terms do not apply to or govern the use of Sourcefire's web site or Sourcefire's appliance discussed in the Documentation. Sourcefire appliances are available for purchase and subject to a separate license containing very different terms of use. Terms Of Use and Copyright and Trademark Notices The copyright in the Documentation is owned by Sourcefire, Inc., and is protected by copyright pursuant to US copyright law, international conventions, and other laws. You may use, print out, save on a retrieval system, and otherwise copy and distribute the documentation solely for non-commercial use, provided that (i) you do not modify the documentation in any way and (ii) you always include Sourcefire's copyright, trademark, and other notices, as well as a link to, or print out of, the full contents of this page and its terms. No part of the documentation may be used in a compilation or otherwise incorporated into another work, or be used to create derivative works, without the express prior written permission of Sourcefire, Inc. Sourcefire, Inc. reserves the right to change the Terms at any time, and your continued use of the Documentation shall be deemed an acceptance of those terms. Sourcefire, the Sourcefire logo, Snort, the Snort logo, 3D Sensor, Intrusion Sensor, Intrusion Agent, Realtime Network Awareness, RNA Sensor, Defense Center, Master Defense Center, Success Pack, and 3D System, are trademarks or registered trademarks of Sourcefire, Inc. All other trademarks are property of their respective owners. © 2004 - 2010 Sourcefire, Inc. All rights reserved. Liability Disclaimers THE DOCUMENTATION AND ANY INFORMATION AVAILABLE FROM IT MAY INCLUDE INACCURACIES OR TYPOGRAPHICAL ERRORS. SOURCEFIRE, INC. MAY CHANGE THE DOCUMENTATION FROM THE TIME TO TIME. SOURCEFIRE, INC. MAKES NO REPRESENTATIONS OR WARRANTIES ABOUT THE ACCURACY OR SUITABILITY OF THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND/OR ANY APPLIANCE OR INFORMATION. SOURCEFIRE, INC. PROVIDES THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND ANY APPLIANCE OR INFORMATION “AS IS” AND SOURCEFIRE, INC. DISCLAIMS ANY AND ALL EXPRESS OR IMPLIED WARRANTIES, INCLUDING BUT NOT LIMITED TO WARRANTIES OF TITLE OR THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SOURCEFIRE, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES (INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF DATA, LOSS OF PROFITS, AND/OR BUSINESS INTERRUPTIONS), ARISING OUT OF OR IN ANY WAY RELATED TO THE SOURCEFIRE, INC. WEB SITE, THE DOCUMENTATION, AND/OR ANY SOFTWARE OR INFORMATION, NO MATTER HOW CAUSED AND/OR WHETHER BASED ON CONTRACT, STRICT LIABILITY, NEGLIGENCE OR OTHER TORTUOUS ACTIVITY, OR ANY OTHER THEORY OF LIABILITY, EVEN IF SOURCEFIRE, INC. IS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. The Documentation may contain “links” to sites on the Internet that are not created by, or under the control of Sourcefire, Inc. Sourcefire, Inc. provides such links solely for your convenience, and assumes no responsibility for the availability or content of such other sites. 2010-Jul-12 13:56

Table of Contents

Chapter 1:

Introduction to the Sourcefire 3D System............................. 14
Components of the Sourcefire 3D System......................................................... Real-time Network Awareness (RNA).................................................... Intrusion Prevention System (IPS) ......................................................... Real-time User Awareness (RUA) .......................................................... PEP Traffic Management ....................................................................... Defense Centers.................................................................................... Master Defense Centers ....................................................................... Intrusion Agents..................................................................................... RNA for Red Hat Linux........................................................................... RNA and IPS for Crossbeam Systems................................................... eStreamer .............................................................................................. 15 15 16 17 17 17 19 19 20 20 20

Logging into the Appliance ................................................................................. 21 Logging into the Appliance to Set Up an Account .............................................. 23 Logging Out of the Appliance ............................................................................. 24 Last Successful Login......................................................................................... 25 Specifying Your User Preferences ...................................................................... Changing Your Password ....................................................................... Configuring Event View Settings ........................................................... Setting Your Default Time Zone ............................................................. Specifying Your Home Page................................................................... Specifying Your Default Dashboard........................................................ 25 25 27 34 35 35

Using the Context Menu .................................................................................... 36 Documentation Resources ................................................................................. 37

Version 4.9.1

Sourcefire 3D System Administrator Guide

3

Table of Contents

Documentation Conventions .............................................................................. 38 Platform Requirements Conventions ..................................................... 38 Access Requirements Conventions ....................................................... 39 IP Address Conventions...................................................................................... 41

Chapter 2:

Performing the Initial Setup .................................................... 43
Setting Up 3D Sensors ....................................................................................... 44 Setting up Defense Centers ............................................................................... 47 Communication Ports ......................................................................................... 50 What’s Next? ...................................................................................................... Administrator User Tasks....................................................................... Maintenance User Tasks........................................................................ Policy & Response Administrator User Tasks ........................................ RNA Event Analyst User Tasks .............................................................. Intrusion Event Analyst User Tasks........................................................ 52 53 54 55 56 57

Chapter 3:

Using Dashboards..................................................................... 59
Understanding Dashboard Widgets.................................................................... 60 Understanding Widget Availability ......................................................... 61 Understanding Widget Preferences ...................................................... 64 Understanding the Predefined Widgets ............................................................. Understanding the Appliance Information Widget................................. Understanding the Appliance Status Widget......................................... Understanding the Compliance Events Widget..................................... Understanding the Current Interface Status Widget ............................. Understanding the Current Sessions Widget ........................................ Understanding the Custom Analysis Widget......................................... Understanding the Disk Usage Widget ................................................. Understanding the Interface Traffic Widget ........................................... Understanding the Intrusion Events Widget.......................................... Understanding the Network Compliance Widget .................................. Understanding the Product Licensing Widget ....................................... Understanding the Product Updates Widget......................................... Understanding the RSS Feed Widget .................................................... Understanding the System Load Widget............................................... Understanding the System Time Widget .............................................. Understanding the White List Events Widget ....................................... Working with Dashboards .................................................................................. Creating a Custom Dashboard............................................................... Viewing Dashboards .............................................................................. Modifying Dashboards........................................................................... Deleting a Dashboard ............................................................................ 65 66 67 67 68 69 69 80 81 81 82 84 85 86 87 87 88 89 89 91 93 97

Version 4.9.1

Sourcefire 3D System Administrator Guide

4

Table of Contents

Chapter 4:

Using the Defense Center........................................................ 99
Management Concepts .................................................................................... 100 The Benefits of Managing Your Sensors.............................................. 100 What Can Be Managed by a Defense Center? .................................... 101 Understanding Software Sensors ........................................................ 105 Beyond Policies and Events .................................................................. 111 Using Redundant Defense Centers ..................................................... 112 Working in NAT Environments.......................................................................... 112 Working with Sensors ...................................................................................... 113 Understanding the Sensors Page ........................................................ 115 Adding Sensors to the Defense Center ................................................ 117 Deleting Sensors ................................................................................. 121 Resetting Management of a Sensor .................................................... 122 Managing a 3Dx800 Sensor................................................................. 125 Adding Intrusion Agents ...................................................................... 130 Sensor Attributes - Intrusion Agent Page............................................. 130 Managing Sensor Groups ................................................................................. Creating Sensor Groups....................................................................... Editing Sensor Groups ......................................................................... Deleting Sensor Groups....................................................................... Editing a Managed Sensor’s System Settings .................................................. Viewing a Sensor’s Information Page .................................................. Stopping and Restarting a Managed Sensor ....................................... Managing Communication on a Managed Sensor............................... Setting the Time on a Managed Sensor .............................................. 131 131 132 133 133 135 137 138 139

Managing a Clustered Pair ................................................................................ 140 Establishing a Clustered Pair ............................................................... 142 Separating a Clustered Pair.................................................................. 144 Configuring High Availability ............................................................................. Using High Availability.......................................................................... Guidelines for Implementing High Availability ..................................... Setting Up High Availability .................................................................. Monitoring the High Availability Status ................................................ Disabling High Availability and Unregistering Sensors......................... Pausing Communication between Paired Defense Centers ................ Restarting Communication between Paired Defense Centers ............ 145 145 149 150 152 153 154 154

Chapter 5:

Using the Master Defense Center........................................ 156
Understanding Event Aggregation.................................................................... Aggregating Intrusion Events............................................................... Aggregating Compliance Events.......................................................... Limitations on Event Aggregation........................................................ 157 158 158 159

Version 4.9.1

Sourcefire 3D System Administrator Guide

5

Table of Contents

Understanding Global Policy Management....................................................... Managing Global Intrusion Policies ...................................................... Using RNA Detection Policies on a Master Defense Center ............... Using Health Policies on a Master Defense Center............................. Using System Policies on a Master Defense Center ........................... Master Defense Center Policy Management Limitations .................... Adding and Deleting Defense Centers ............................................................. Adding a Master Defense Center ........................................................ Adding a Defense Center..................................................................... Deleting a Defense Center .................................................................. Resetting Management of a Defense Center ...................................... Editing Settings for a Managed Defense Center .............................................. Viewing the Defense Center Information Page ................................... Editing the Event Filter Configuration .................................................. Editing or Disabling Remote Management Communications .............. Managing the Health Blacklist ............................................................. Managing High Availability Defense Centers ....................................... Managing Appliance Groups............................................................................. Creating Appliance Groups .................................................................. Editing Appliance Groups..................................................................... Deleting Appliance Groups .................................................................. Editing Master Defense Center System Settings ............................................. Listing Master Defense Center Information ........................................ Viewing a Master Defense Center License ......................................... Configuring Network Settings.............................................................. Shutting Down and Restarting the System.......................................... Configuring Remote Management Networking................................... Setting System Time............................................................................ Blacklisting Health Policies...................................................................

161 161 162 162 162 163 164 165 168 171 171 175 175 176 178 178 178 179 180 180 181 181 182 182 182 182 183 183 184

Using the Appliances Page ............................................................................... 173

Chapter 6:

Using Detection Engines and Interface Sets...................... 185
Understanding Detection Engines .................................................................... 186 Understanding Detection Resources and 3D Sensor Models ............. 189 Understanding Default Detection Engines .......................................... 191 Managing Detection Engines............................................................................ Creating a Detection Engine ................................................................ Editing a Detection Engine .................................................................. Deleting a Detection Engine ................................................................ Using Detection Engine Groups ....................................................................... Creating Detection Engine Groups ...................................................... Editing Detection Engine Groups......................................................... Deleting Detection Engine Groups ...................................................... 193 193 194 197 197 197 198 199

Version 4.9.1

Sourcefire 3D System Administrator Guide

6

Table of Contents

Using Variables within Detection Engines ........................................................ Assigning Values to System Default Variables in Detection Engines... Creating New Variables for Detection Engines .................................... Deleting and Resetting Variables ......................................................... Configuring Custom Variables in Detection Engines ........................... Using Portscan-Only Detection Engines .............................................. Using Interface Sets ......................................................................................... Understanding Interface Set Configuration Options............................ Creating an Interface Set ..................................................................... Creating an Inline Interface Set ........................................................... Editing an Interface Set ....................................................................... Deleting an Interface Set ..................................................................... Using Interface Set Groups .............................................................................. Creating Interface Set Groups ............................................................. Editing Interface Set Groups................................................................ Deleting Interface Set Groups .............................................................

199 200 202 203 204 205 207 207 213 216 221 223 223 224 224 225

Inline Fail Open Interface Set Commands ........................................................ 225 Removing Bypass Mode on Inline Fail Open Fiber Interfaces ............. 225 Forcing an Inline Fail Open Interface Set into Bypass Mode ............... 226 Using Clustered 3D Sensors............................................................................. Using Detection Engines on Clustered 3D Sensors ............................ Understanding Interface Sets on Clustered 3D Sensors ..................... Managing Information from a Clustered 3D Sensor ............................ 227 228 229 230

Chapter 7:

Working with Event Reports.................................................. 232
Working with Event Reports............................................................................. 234 Working with Report Profiles............................................................................ 234 Generating Reports from Event Views ............................................................. 235 Managing Generated Reports........................................................................... Viewing Generated Reports................................................................. Downloading Generated Reports......................................................... Deleting Generated Reports ................................................................ Moving Reports to a Remote Storage Location................................... Running Remote Reports .................................................................... Understanding Report Profiles.......................................................................... Understanding the Predefined Report Profiles .................................... Modifying a Predefined Report Profile................................................. Creating a Report Profile...................................................................... 237 238 238 239 239 240 241 242 246 246

Working with Report Information ..................................................................... 248 Using Report Types.............................................................................. 250 Defining Report Information ................................................................ 254

Version 4.9.1

Sourcefire 3D System Administrator Guide

7

Table of Contents

Working with Report Sections .......................................................................... Using Summary Reports...................................................................... Including an Image File ........................................................................ Defining the Report Sections............................................................... Using a Report Profile ....................................................................................... Generating a Report using a Report Profile ......................................... Editing Report Profiles ......................................................................... Deleting Report Profiles.......................................................................

255 255 257 258 260 261 263 263

Working with Report Options ........................................................................... 258

Chapter 8:

Managing Users ...................................................................... 264
Understanding Sourcefire User Authentication ................................................ Understanding Internal Authentication ................................................ Understanding External Authentication ............................................... Understanding User Privileges ............................................................ Managing Authentication Objects .................................................................... Understanding LDAP Authentication ................................................... Creating LDAP Authentication Objects ................................................ LDAP Authentication Object Examples ............................................... Editing LDAP Authentication Objects .................................................. Understanding RADIUS Authentication ............................................... Creating RADIUS Authentication Objects............................................ RADIUS Authentication Object Examples ........................................... Editing RADIUS Authentication Objects .............................................. Deleting Authentication Objects .......................................................... Managing User Accounts ................................................................................. Viewing User Accounts........................................................................ Adding New User Accounts................................................................. Managing Externally Authenticated User Accounts............................. Managing User Password Settings...................................................... Configuring User Roles........................................................................ Modifying User Privileges and Options ............................................... Modifying Restricted Event Analyst Access Properties....................... Modifying User Passwords.................................................................. Deleting User Accounts ....................................................................... User Account Privileges....................................................................... 264 266 266 267 269 269 269 281 286 287 287 295 298 298 299 299 300 302 303 304 306 307 311 312 312

Chapter 9:

Managing System Policies .................................................... 320
Creating a System Policy .................................................................................. 321 Editing a System Policy..................................................................................... 323 Applying a System Policy .................................................................................. 324 Deleting System Policies .................................................................................. 325

Version 4.9.1

Sourcefire 3D System Administrator Guide

8

Table of Contents

Configuring the Parts of Your System Policy..................................................... Configuring the Access List for Your Appliance ................................... Configuring Audit Log Settings ............................................................ Configuring Authentication Profiles ..................................................... Configuring Dashboard Settings .......................................................... Configuring Database Event Limits ..................................................... Configuring Detection Policy Preferences ........................................... Configuring DNS Cache Properties...................................................... Configuring a Mail Relay Host and Notification Address ..................... Configuring Intrusion Policy Preferences ............................................. Specifying a Different Language .......................................................... Adding a Custom Login Banner ........................................................... Configuring RNA Settings .................................................................... Configuring RNA Subnet Detection Settings ....................................... Configuring RUA Settings .................................................................... Synchronizing Time .............................................................................. Mapping Vulnerabilities for Services....................................................

325 325 327 329 331 332 336 337 338 339 340 341 342 349 352 354 358

Chapter 10:

Configuring System Settings ................................................. 360
Viewing and Modifying the Appliance Information ........................................... 362 Understanding Licenses ................................................................................... Understanding Feature Licenses ......................................................... Verifying Your Product License ............................................................ Managing Your Feature Licenses ......................................................... 364 366 368 370

Configuring Network Settings........................................................................... 377 Editing Network Interface Configurations......................................................... 380 Shutting Down and Restarting the System....................................................... 382 Configuring the Communication Channel ......................................................... 383 Setting Up the Management Virtual Network...................................... 384 Editing the Management Virtual Network............................................ 385 Configuring Remote Access to the Defense Center ........................................ 386 Setting the Time Manually ................................................................................ 389 Blacklisting Health Modules.............................................................................. 391 Specifying NetFlow-Enabled Devices ............................................................... 392 Managing Remote Storage............................................................................... Using Local Storage ............................................................................. Using NFS for Remote Storage ........................................................... Using SSH for Remote Storage ........................................................... Using SMB for Remote Storage .......................................................... 393 393 394 395 396

Version 4.9.1

Sourcefire 3D System Administrator Guide

9

Table of Contents

Chapter 11:

Updating System Software.................................................... 398
Installing Software Updates.............................................................................. Updating a Defense Center or Master Defense Center ...................... Updating Managed Sensors ................................................................ Updating Unmanaged 3D Sensors ...................................................... 400 402 404 406

Uninstalling Software Updates ......................................................................... 409 Updating the Vulnerability Database................................................................. 410

Chapter 12:

Using Backup and Restore .................................................... 413
Creating Backup Files ....................................................................................... 414 Creating Backup Profiles ................................................................................... 418 Performing Sensor Backup with the Defense Center ....................................... 419 Uploading Backups from a Local Host .............................................................. 420 Restoring the Appliance from a Backup File ..................................................... 421

Chapter 13:

Scheduling Tasks .................................................................... 425
Configuring a Recurring Task ............................................................................ 426 Automating Backup Jobs .................................................................................. 428 Automating Software Updates ......................................................................... Automating Software Downloads ........................................................ Automating Software Pushes .............................................................. Automating Software Installs............................................................... Automating Vulnerability Database Updates .................................................... Automating VDB Update Downloads................................................... Automating VDB Update Pushes......................................................... Automating VDB Update Installs ......................................................... 430 431 433 435 437 438 440 442

Automating SEU Imports.................................................................................. 444 Automating Intrusion Policy Applications.......................................................... 446 Automating Reports.......................................................................................... 448 Automating Nessus Scans................................................................................ 450 Preparing Your System to Run a Nessus Scan..................................... 450 Scheduling a Nessus Scan................................................................... 451 Synchronizing Nessus Plugins .......................................................................... 452 Automating Nmap Scans .................................................................................. 454 Preparing Your System for an Nmap Scan ........................................... 454 Scheduling an Nmap Scan ................................................................... 455 Automating Recommended Rule State Generation.......................................... 456

Version 4.9.1

Sourcefire 3D System Administrator Guide

10

Table of Contents

Viewing Tasks ................................................................................................... 458 Using the Calendar .............................................................................. 459 Using the Task List............................................................................... 460 Editing Scheduled Tasks ................................................................................... 461 Deleting Scheduled Tasks ................................................................................. 461 Deleting a Recurring Task .................................................................... 462 Deleting a One-Time Task.................................................................... 462

Chapter 14:

Monitoring the System ........................................................... 463
Viewing Host Statistics..................................................................................... 464 Monitoring System Status and Disk Space Usage ........................................... 468 Viewing System Process Status ....................................................................... 468 Understanding Running Processes................................................................... 471 Understanding System Daemons ........................................................ 471 Understanding Executables and System Utilities ................................ 473 Viewing IPS Performance Statistics.................................................................. 476 Generating IPS Performance Statistics Graphs ................................... 476 Saving IPS Performance Statistics Graphs .......................................... 478 Viewing RNA Performance Statistics................................................................ 478 Generating RNA Performance Statistics Graphs ................................. 479 Saving RNA Performance Statistics Graphs ........................................ 481

Chapter 15:

Using Health Monitoring ........................................................ 482
Understanding Health Monitoring .................................................................... Understanding Health Policies ............................................................. Understanding Health Modules ........................................................... Understanding Health Monitoring Configuration ................................. Configuring Health Policies ............................................................................... Predefined Health Policies ................................................................... Creating Health Policies ....................................................................... Applying Health Policies....................................................................... Editing Health Policies ......................................................................... Deleting Health Policies ....................................................................... 483 484 485 489 489 490 497 528 530 533

Using the Health Monitor Blacklist ................................................................... 534 Blacklisting Health Policies or Appliances ............................................ 535 Blacklisting a Health Policy Module ..................................................... 537

Version 4.9.1

Sourcefire 3D System Administrator Guide

11

Table of Contents

Configuring Health Monitor Alerts .................................................................... Preparing to Create a Health Alert ....................................................... Creating Health Monitor Alerts ............................................................ Interpreting Health Monitor Alerts....................................................... Editing Health Monitor Alerts .............................................................. Deleting Health Monitor Alerts ............................................................

539 540 540 542 543 544

Chapter 16:

Reviewing Health Status........................................................ 545
Using the Health Monitor ................................................................................. 545 Interpreting Health Monitor Status ...................................................... 547 Using Appliance Health Monitors ..................................................................... Interpreting Appliance Health Monitor Status ..................................... Viewing Alerts by Status...................................................................... Running All Modules for an Appliance ................................................. Running a Specific Health Module....................................................... Generating Health Module Alert Graphs.............................................. Generating Appliance Troubleshooting Files........................................ Working with Health Events ............................................................................. Understanding Health Event Views ..................................................... Viewing Health Events......................................................................... Understanding the Health Events Table............................................... Searching for Health Events................................................................. 547 549 549 550 551 553 554 555 556 556 561 563

Chapter 17:

Auditing the System................................................................ 566
Managing Audit Records .................................................................................. Viewing Audit Records......................................................................... Suppressing Audit Records.................................................................. Understanding the Audit Log Table...................................................... Searching Audit Records...................................................................... 566 567 570 574 575

Viewing the System Log ................................................................................... 578 Filtering System Log Messages .......................................................... 579 Using Four-Digit Year Formats on the 3D3800 ..................................... 581

Version 4.9.1

Sourcefire 3D System Administrator Guide

12

................................................................... 584 584 585 585 586 586 588 588 588 589 590 Importing Objects ............ 602 Glossary ........... Exporting an RNA Detection Policy.............................................. 600 Managing the Task Queue .......................................................................... Exporting a Custom Table .....................................................................................................9... Exporting a System Policy................................................1 Sourcefire 3D System Administrator Guide 13 .......... Exporting Multiple Objects ................... 598 Viewing the Status of Long-Running Tasks ............................ Exporting a User-Defined RNA Detector............ 603 Index ..................................................................................................... Exporting a Health Policy ................................. 583 Exporting Objects ................................................................................ Exporting an Intrusion Policy................................................. 593 Appendix B: Appendix C: Purging the RNA and RUA Databases................................................................................................. Exporting a PEP Policy ............................................. Exporting a Custom Workflow........................ 629 Version 4........................................................................................................................................................................................................................................................ Exporting a Dashboard..................................................... 600 Viewing the Task Queue ........................................................................................................................Table of Contents Appendix A: Importing and Exporting Objects ..................................................

Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface.1 Sourcefire 3D System Administrator Guide 14 . Logging into the Appliance on page 21 explains how to access the web interface on your appliance and log in using one of the user accounts. Sourcefire 3D System has the tools you need to: • • • discover the changing assets and vulnerabilities on your network determine the types of attacks against your network and the impact they have to your business processes defend your network in real time The topics that follow introduce you to the Sourcefire 3D System and describe some of the key components that contribute to its value as a part of any security strategy for your network. Logging into the Appliance to Set Up an Account on page 23 explains how to set up an association between a external user account and a set of credentials on the appliance. • • • Version 4. such as the home page. and event viewing preferences.9. account password.Introduction to the Sourcefire 3D System Chapter 1 Administrator Guide tn The Sourcefire 3D System™ provides you with real-time network intelligence for real-time network defense. time zone. Logging Out of the Appliance on page 24 explains how to log out of the web interface. • • • Components of the Sourcefire 3D System on page 15 provides descriptions of each of the components that may be in your Sourcefire 3D System. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account. dashboard.

Components of the Sourcefire 3D System The topics that follow introduce you to the Sourcefire 3D System and describe some of the key components that contribute to its value as a part of any security strategy for your network. Documentation Conventions on page 38 explains typeface conventions used throughout the guide to convey specific types of information visually. compliance white lists. You must use a Defense Center to manage a 3D Sensor if it is running RNA. RNA monitors traffic on your network. IP Address Conventions on page 41 explains how the Sourcefire 3D System treats IP address ranges specified using Classless Inter-Domain Routing (CIDR) notation.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 • • • Documentation Resources on page 37 explains where to locate specific information about using the Defense Center. and traffic profiles to protect your company’s infrastructure by monitoring network traffic for unusual patterns or behavior and automatically responding as needed. it compiles the following information: • • • the number and types of network devices running on your network the operating systems running on monitored network devices the active services and open ports on monitored network devices Version 4. You can set up compliance policies. listening to the network segments you specify.1 Sourcefire 3D System Administrator Guide 15 . As RNA passively observes traffic.9. using information from detected packets to build a comprehensive map of the devices on the network. • • • • • • • • • Real-time Network Awareness (RNA) on page 15 Intrusion Prevention System (IPS) on page 16 Real-time User Awareness (RUA) on page 17 Defense Centers on page 17 Master Defense Centers on page 19 Intrusion Agents on page 19 RNA for Red Hat Linux on page 20 RNA and IPS for Crossbeam Systems on page 20 eStreamer on page 20 Real-time Network Awareness (RNA) Sourcefire Real-time Network Awareness (also called RNA) is one of the components of the Sourcefire 3D System that you can use on your 3D Sensor.

system. For packet-based events. 3D Sensors with IPS run preprocessors against detected network traffic to normalize traffic and detect malicious packets. You can also create custom intrusion rules tuned to your environment. services. time. and contextual information about the source of the attack and its target. and sensor statistics to the Defense Center so you can see a consolidated view of events. integrity. Intrusion Prevention System (IPS) The Sourcefire Intrusion Prevention System (also called IPS) is one of the components of the Sourcefire 3D System that you can run on the 3D Sensor. and preprocessors to look for the broad range of exploits that attackers have developed. and assigned host attributes. which are records of active sessions involving monitored network devices including the frequency and size of the session. In addition. In a Sourcefire 3D System deployment that includes 3D Sensors with IPS and a Defense Center. 3D Sensors running RNA transmit the network map. and intrusion policies to your sensors.1 Sourcefire 3D System Administrator Guide 16 . a copy of the packet or packets that triggered the event is also recorded. and protocols. see What Can Be Managed by a Defense Center? on page 101. You can choose to enable rules that would detect the attacks you think most likely to occur on your network. if applicable. the sensors transmit events and sensor statistics to the Defense Center where you can view the aggregated data and gain a greater understanding of the attacks against your network assets.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 • • the vulnerabilities and exploits to which monitored network devices may be susceptible flow data. The Defense Center can also push health. decoders. By placing 3D Sensors on key network segments. Each 3D Sensor uses rules. RNA assigns vulnerabilities to the host based on the operating system vendor and version detected for the host.The Defense Center can also push health. RNA builds a host profile for each host it detects. You can push vulnerability database (VDB) and software updates from the Defense Center as well. the client application and URL involved in the session You can access event views and graphs to analyze this collected data. and RNA detection policies to your sensors. it generates an intrusion event. event and flow data.9. You can access host profiles by browsing the network map or through one of the workflows Sourcefire provides to aid your analysis. For more information. containing host details such as detected operating system. as well as the service and protocol used and. or confidentiality of hosts on the network. the type of exploit. system. 3D Sensors that are licensed to use IPS include a set of intrusion rules developed by the Sourcefire Vulnerability Research Team (VRT). which is a record of the date. IPS allows you to monitor your network for attacks that might affect the availability. You can push software Version 4. When a 3D Sensor identifies a possible intrusion. you can examine the packets that traverse your network for malicious activity.

9. Sourcefire recommends that you use only the Defense Center’s web interface to interact with the sensor and its data. You can apply these policies and rules across the Sourcefire 3D System. You must manage these models with a Defense Center. PEP traffic management enhances the sensor’s efficiency by allowing you to pre-select traffic to cut through or to drop instead of analyzing. analyze. departments. Defense Centers The Defense Center provides a centralized management interface and database repository for the Sourcefire 3D System. If you have software sensors or Intrusion Agents on your network. Note that if you do manage your 3D Sensors with a Defense Center.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 updates from the Defense Center to sensors as well. or other user characteristics. PEP Traffic Management PEP is a technology based on the hardware capabilities of the 3D9900 Sensors. If your 3D Sensor is running IPS. The network protocol used by your organization to provide user authentication largely determines the amount of data and efficiency of RUA. You can analyze and respond to events from all your sensors consistently by doing the analysis through an interface where you can see all the data collected by the managed sensors. PEP allows you to create rules to block. you must use the Defense Center to manage them. 3D Sensor 6800. see What Can Be Managed by a Defense Center? on page 101. As a result. Real-time User Awareness (RUA) The Real-time User-Awareness component (also called RUA) allows you to create policies and response rules that are user-based. For more information. IMPORTANT! The Sourcefire 3D Sensor 3800. you can configure your 3D Sensor to drop or replace packets that you know to be harmful. you can also use a local web interface to create intrusion policies and review the resulting intrusion events. If you deploy your 3D Sensor inline on your network and create what is called an inline detection engine. or send traffic directly through the 3D9900 with no further inspection. Note that a 3D Sensor running Version 4. You can also push policies created on the Defense Center and software updates to managed sensors. and 3D Sensor 9800 models (usually referred to a the 3Dc800 sensors) do not have a web interface. See Using Sourcefire RUA in the Analyst Guide for more information about RUA.1 Sourcefire 3D System Administrator Guide 17 . RUA enables you to implement and enforce policies specific to individuals.

You can configure a DC3000 as a Master Defense Center during the initial setup. the Defense Center correlates intrusion events from IPS with host vulnerabilities from RNA and assigns impact flags to the intrusion events. You can rack mount a DC1000 and collect data from a large number of 3D Sensors.2 million default and 10 million maximum DC1000 You can use DC1000 Defense Centers in most environments. attacks. you must manage the sensor with a Defense Center.1 million default and 10 million maximum RNA Flow Summaries . The DC500 receives data at an aggregate rate of up to 100 intrusion events or 900 flow events per second.1 million default and 10 million maximum RNA Flow Summaries . DC500 You can use the DC500 model of the Defense Center in managed services environments to collect data from up to three 3D Sensors. endpoint.5 million maximum RNA Flows . Key DC500 database limits are: • • • Intrusion Events .2 million default and 10 million maximum DC3000 You can use DC3000 Defense Centers in high-demand environments. or network vulnerabilities.1 Sourcefire 3D System Administrator Guide 18 .9. IMPORTANT! You cannot use DC500s in high availability configurations. You can use either DC1000s or DC3000s in high availability configurations. Version 4. Key DC1000 database quantities are: • • • Intrusion Events .1 million default and 10 million maximum RNA Flows . A DC3000 allows you to use higher database quantities. Impact correlation lets you focus in on attacks most likely to damage high priority hosts. DC500s also have an RNA host limit of 1000. and network intelligence with user identity information so that you can identify the source of policy breaches. but if you want to use RNA on the sensor.500 thousand default and 2. the Defense Center correlates threat. If you use your Defense Center to manage 3D Sensors that run RNA and IPS (either on the same sensor or different sensors that monitor the same network segments). If you deploy Real-time User-Awareness (RUA).Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 the IPS component includes its own local web interface.

1 million default and 10 million maximum RNA Flows .2 million default and 10 million maximum Master Defense Centers The Sourcefire Master Defense Center is a key component in the Sourcefire 3D System. You cannot use a Virtual Defense Center in high availability configurations or as a Master Defense Center. For more information. you can view the current status of the Defense Centers across your enterprise from a single web interface. you can install an Intrusion Agent to forward intrusion events to a Defense Center. Although you cannot manage policies or rules for an Intrusion Agent from the Defense Center.2 million default and 100 million maximum Virtual Defense Center Virtual Defense Centers are hosted on VMware’s ESX/ESXi or Xen virtual machines.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 Key DC3000 database quantities are: • • • Intrusion Events . and white list events from up to ten Defense Centers within your Sourcefire 3D System deployment. If the network map on the Defense Center has entries for the target host in a given event. you can do analysis and reporting on those events. Intrusion Agents If you have an existing installation of Snort®. You can manage up to 25 physical and Virtual 3D Sensors with a Virtual Defense Center. You can use the Master Defense Center to aggregate and analyze intrusion events. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide. See Using the Master Defense Center on page 156 for more information about managing your Defense Centers with a Master Defense Center. the Defense Center Version 4. Key Virtual Defense Center database quantities are: • • • Intrusion Events . In this way.1 Sourcefire 3D System Administrator Guide 19 . The Master Defense Center can also aggregate events related to the health of the Defense Centers it is managing. You can then analyze the events detected by Snort alongside your other data. compliance events.1 million default and 100 million maximum RNA Flows .1 million default and 100 million maximum RNA Flow Summaries .1 million default and 10 million maximum RNA Flow Summaries .9.

RNA and IPS for Crossbeam Systems The Sourcefire 3D System currently supports software-only versions of RNA and IPS for Crossbeam Systems X-Series security switches. you could write a program to retrieve host criticality or vulnerability data from the Defense Center and add that information to your display.9. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place. register all Intrusion Agents to the primary Defense Center. Version 4. eStreamer integration requires custom programming. See the eStreamer Integration Guide for more information. RNA data received by a Defense Center from the server is treated in a similar way to RNA data received from a 3D Sensor that is running RNA. If. you display network host data within one of your network management applications. eStreamer You can access event data within your own applications through the eStreamer Application Programming Interface (API). IMPORTANT! You must have a Defense Center in your Sourcefire 3D System deployment to use RNA for Red Hat Linux. RNA for Red Hat Linux The Sourcefire 3D System currently supports a software-only version of the RNA component on your server hardware running Red Hat Enterprise Linux 5 (RHEL5) or CentOS 5. you must use a Defense Center to manage it. Separate installation and configuration guides are available for the 3D Sensor Software for X-Series.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 assigns impact flags to the events.1 Sourcefire 3D System Administrator Guide 20 . IMPORTANT! Because the 3D Sensor Software for X-Series does not have a web interface. for example. but allows you to request specific data from a Defense Center. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. RNA and IPS data received by a Defense Center from a Crossbeam-based software sensors is treated in a similar way to data received from a 3D Sensor. See the Sourcefire RNA Software on Red Hat Linux Configuration Guide for more information.

You must use the Defense Center’s web interface to manage these sensors. If you are the first user to log into the appliance after it is installed. If this occurs.Introduction to the Sourcefire 3D System Logging into the Appliance Chapter 1 Logging into the Appliance Requires: Any The Defense Center and many 3D Sensor models have a web-based interface that you can use to perform administrative. The initial setup process is described in Setting Up 3D Sensors on page 44. Version 4.1 Sourcefire 3D System Administrator Guide 21 . and Virtual 3D Sensors) do not have a web interface. Browser Requirements Browser Firefox 3.0 Microsoft Internet Explorer 8. there is a limited web interface that you can use to perform the initial appliance setup and to register the sensor with a Defense Center. If your 3D Sensor is not licensed for IPS.5.0 TIP! Some processes that take a significant amount of time may cause your web browser to display a message that a script has become unresponsive. If your 3D Sensor is licensed for IPS. The current version of the web interface supports the browsers listed in the following table.9. management. Intrusion Agents. and analysis tasks. Note that 3Dx800 and software sensors (Crossbeam-based software sensors. you are presented with a more complete web interface that you can use to perform additional configuration and event analysis. you must log in using the admin user account. RNA for Red Hat Linux. make sure you allow the script to continue until it finishes. You can access the web interface by logging into the appliance using a web browser.x Required Enabled Options and Settings JavaScript cookies Secure Sockets Layer (SSL) v3 JavaScript cookies Secure Sockets Layer (SSL) v3 128-bit encryption Active scripting security setting JavaScript cookies Secure Sockets Layer (SSL) v3 128-bit encryption Active scripting security setting Compatibility View Microsoft Internet Explorer 7 .

You must have already generated your SecurID pin before you can log into the Sourcefire 3D System. However. where hostname corresponds to the host name of the appliance. append the token to your SecurID pin and use that as your password to log in. the features that you can access are controlled by the privileges granted to your user account. type 1111222222. you should use this account. append the SecurID token to the end of your SecurID pin and use that as your password when you log in. IMPORTANT! Because the Defense Center and the 3D Sensor audit user activity based on user accounts. Version 4. To log into the appliance: Access: Any 1. In the Username and Password fields. The Login page appears.9. After you create other user accounts as described in Adding New User Accounts on page 300. The first time you log into the appliance. unless you are viewing a page (such as an unpaused dashboard) that periodically communicates with the web server on the appliance. if your pin is 1111 and the SecurID token is 222222. the procedures for logging into and out of the appliance remain the same. 2. you and other users should use those accounts to log into the appliance.Introduction to the Sourcefire 3D System Logging into the Appliance Chapter 1 After you log into the appliance.5 hours of inactivity. For example. When the appliance was installed. If your organization uses SecurID® tokens when logging in. type your user name and password. Direct your browser to https://hostname/. Your session automatically logs you out after 3. the user who performed the installation created a single administrative user account and password. you should make sure that users log into the system with the correct account.1 Sourcefire 3D System Administrator Guide 22 . IMPORTANT! If your company uses SecurID.

Shell access is controlled entirely through the shell access filter or PAM login attribute set for an LDAP server or the shell access list on a RADIUS server. Note that when a shell access user logs into the appliance. You can either select a different option from the available menus or click Back in your browser window. Click Login. use the Defense Center’s web interface to manage policies and view events. If this is the case. LDAP usernames can include underscores (_). the first time you log into the Defense Center or 3D Sensor using your external user credentials. The permissions for that local user record can then be modified. You (or your system administrator) can then change the permissions to grant the appropriate access to user functionality.Introduction to the Sourcefire 3D System Logging into the Appliance to Set Up an Account Chapter 1 3.). If you selected a new home page for your user account. Instead. Shell users should log in using usernames with all lowercase letters. The default start page appears. IMPORTANT! The 3Dx800 sensor models do not have a web interface. the links on the default home page include options that span the range of user account privileges. The menus and menu options that are available to you at the top of the page are based on the privileges for your user account. and hyphens (-) but otherwise only alphanumeric characters are supported. type 1111222222. the appliance associates those credentials with a set of permissions by creating a local user record. externally authenticated users can log into the appliance using their external account credentials without any additional configuration by the system administrator. Version 4. it does not create a local user account.9. If an account is externally authenticated and by default receives no access privileges. If you click a link that requires different privileges from those granted to your account. See Specifying Your Home Page on page 35 for more information. you can log in but cannot access any functionality. For example. if your pin is 1111 and the SecurID token is 222222. However. then that page is displayed instead. unless they are granted through group or list membership. Logging into the Appliance to Set Up an Account Requires: Any Some user accounts may be authenticated through an external authentication server. append the token to your SecurID pin and use that as your password to log in. periods (.1 Sourcefire 3D System Administrator Guide 23 . If your organization uses SecurID tokens when logging in. If the default role for external user accounts is set to a specific access role. This activity has been logged. the following warning message is displayed: You are attempting to view an unauthorized page.

However. Version 4. 3. please contact the system administrator.1 Sourcefire 3D System Administrator Guide 24 . append the SecurID token to your SecurID pin and use that as your password when you log in. IMPORTANT! If your company uses SecurID. The Login page appears. Direct your browser to https://hostname. Logging out ends your web session and ensures that no one can use the appliance with your credentials. Click Login. The page that appears depends on the default access role for external authentication: • If a default access role is selected in the authentication object or the system policy. • If no default access role is selected. 4. the default start page appears. 2. For more information. the links on the default home page include options that span the range of user account privileges. even if you are only stepping away from your web browser for a short period of time.Introduction to the Sourcefire 3D System Logging Out of the Appliance Chapter 1 To create an externally authenticated account on the appliance: Access: Any 1. If you do not have access. the Login page re-appears. If you continue to have difficulty accessing this device.9. In the Username and Password fields. The menus and menu options that are available to you at the top of the page are based on the privileges for your user account. type your user name and password. If you click a link that requires different privileges from those granted to your account. See Specifying Your Home Page on page 35 for more information. then that page is displayed instead. If you selected a new home page for your user account. This activity has been logged. see Modifying User Privileges and Options on page 306. Logging Out of the Appliance Requires: Any Make sure you log out of the appliance. contact your system administrator and ask them to modify your account privileges or login as a user with Administrator access and modify the privileges for the account. where hostname corresponds to the host name of the appliance. You can either select a different option from the available menus or click Back in your browser window. the following warning message is displayed: You are attempting to view an unauthorized page. with the following error message: Unable to authorize access.

see Changing an Expired Password on page 26. event viewing preferences. Setting Your Default Time Zone on page 34 explains how to set the time zone for your user account and describes how that affects the time stamp on the events that you view.Introduction to the Sourcefire 3D System Last Successful Login Chapter 1 Note that your session automatically logs you out after 3.9. Specifying Your Default Dashboard on page 35 explains how to choose which of the dashboards you want to use as your default dashboard.1 Sourcefire 3D System Administrator Guide 25 . Specifying Your User Preferences Requires: Any Users can specify certain preferences for their user account. To log out of the appliance: Access: Any Click Logout on the toolbar. you can view information about the last login session for the appliance. month. including passwords. and home page preferences. Version 4. unless you are viewing a page (such as an unpaused dashboard) that periodically communicates with the web server on the appliance.5 hours of inactivity. this is the first page you see upon logging into the appliance. Specifying Your Home Page on page 35 explains how to use one of the existing pages as your default home page. and depending on the settings for your user account. date and year of your last login the appliance-local time of your last login in 24-hour notation host and domain name last used to access the appliance. Last Successful Login Requires: Any The first time you visit the appliance home page during a web session. You can change your password at any time. Configuring Event View Settings on page 27 describes how the event preferences affect what you see as you view events. time zone settings. See the following sections for more information: • • • Changing Your Password on page 25 explains how to change the password for your user account. After setting this value. You can see the following information about that user account last login: • • • day of the week. you may have to change your password periodically. • • Changing Your Password Requires: Any All user accounts are protected with a password.

If your password has exired. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. In the Current Password field. 5. you must change your password.1 Sourcefire 3D System Administrator Guide 26 .Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Note that if password strength-checking is enabled. 2. IMPORTANT! If you are an LDAP or a RADIUS user. the Password Expiration Warning page appears.9. A success message appears on the page when your new password is accepted by the system. To change your password: Access: Any 1. In the toolbar. Note that the password expiration time period is set when your account is created and cannot be changed. In the New Password and Confirm fields. type your new password. To respond to the password expiration warning: Access: Any You have two choices: • Click Change Password to change your password now. Version 4. type your current password and click Change. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters. Also. click Preferences. The User Preferences page appears. 3. if password strength-checking is enabled. your password can expire. Click Change Password. If you have zero warning days left. Click Change. Passwords cannot be a word that appears in a dictionary or include consecutive repeating characters • Click Skip to change your password later. passwords must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. Changing an Expired Password Requires: DC/MDC or 3D Sensor Depending on the settings for your user account. you cannot change your password through the web interface. The Change Password page appears. 4.

1 Sourcefire 3D System Administrator Guide 27 .9. Configure default workflows.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Configuring Event View Settings Requires: Any Use the Event View Settings page to configure characteristics of event views in the Sourcefire 3D System. Click Save. For more information. The User Preferences page appears. For more information. 3. Click Event View Settings. 4. see Default Time Windows on page 29. 5. The Event View Settings page appears. To configure event preferences: Access: Any 1. Configure the default time window or windows. 6. Event Preferences Use the Event Preferences section of the Event View Settings page to configure basic characteristics of event views in the Sourcefire 3D System. For more information. In the toolbar. see Default Workflows on page 32. click Preferences. Version 4. 2. Configure the basic characteristics of event views. Your changes are implemented. see Event Preferences on page 27.

Expand Packet View Allows you to configure how the packet view for intrusion events appears. Note also that for this setting to take effect.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 The Event Preferences table describes the settings you can configure. Rows Per Page Controls how many rows of events per page you want to appear in drill-down pages and table views. Resolve IP Addresses Whenever possible. Event Preferences Setting Confirm ‘All’ Actions Description Controls whether the appliance forces you to confirm actions that affect all events in an event view. • None .collapse all subsections of the Packet Information section of the packet view • Packet Text . For more information on the packet view. For example. you must confirm that you want to delete all the events that meet the current constraints (including events not displayed on the current page) before the appliance will delete them from the database. see Using the Packet View in the Analyst Guide. By default. allows the appliance to display host names instead of IP addresses in event views. Note that an event view can be slow to display if it contains a large number of IP addresses and you have enabled this option.9. Any IPS or DC/MDC + IPS IPS or DC/MDC Requires Any Version 4. the appliance displays a collapsed version of the packet view. if this setting is enabled and you click Delete All on an event view.expand only the Packet Text subsection • Packet Bytes .expand all sections Regardless of the default setting.1 Sourcefire 3D System Administrator Guide 28 . you can always manually expand the sections in the packet view to view detailed information about a captured packet. see Configuring Network Settings on page 377. you must have a DNS server configured in the system settings.expand only the Packet Bytes subsection • All .

sometimes called the time range. imposes a time constraint on the events in any event view.a single link that deactivates the standard text rule in all the locally defined custom intrusion policies • Current Policy . • Ask . Requires Any Statistics Refresh Interval IPS or DC/MDC Deactivate Rules IPS or DC/MDC + IPS Default Time Windows Requires: Any The time window. When you log out and then log back in. in minutes. time windows are reset to the Version 4.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Event Preferences (Continued) Setting Refresh Interval Description Sets the refresh interval for event views. you can always manually change the time window for individual event views during your event analysis. Sets the refresh interval for event summary pages such as the Intrusion Event Statistics and RNA Statistics pages. Entering zero disables the refresh option.1 Sourcefire 3D System Administrator Guide 29 . your user account must have either Administrator access or both Intrusion Event Analyst and Policy & Response Administrator access. Also keep in mind that time window settings are valid for only the current session.9.links for each of these options To see these links on the packet view. Controls which links appear on the packet view for intrusion events generated by standard text rules. Entering zero disables the refresh option.a single link that deactivates the standard text rule in only the currently applied intrusion policy. Note that regardless of the default time window setting. The following graphic shows the Defense Center version of the page. Note that this interval does not apply to dashboards. • All Policies . Note that this interval does not apply to dashboards. Use the Default Time Windows section of the Event View Settings page to control the default behavior of the time window. Note that you cannot deactivate rules in the default policies.

For more information. white list events. the time window expands and new events are added to the event view sliding. as time moves forward. which displays all the events generated from a specific start time to a specific end time expanding. which displays all the events generated from a specific start time (for example. remediation status events. • Requires: IPS or DC/MDC The Events Time Window sets a single default time window for (depending on the appliance) intrusion events. Administrators. Requires: Any The Audit Log Time Window sets the default time window for the audit log. the SEU import log. compliance events.1 Sourcefire 3D System Administrator Guide 30 . vulnerabilities. • • You can only set time windows for event types your user account can access. RUA events. and IPS event analysts can set health monitoring time windows. which displays all the events generated from a specific start time to the present. or white list violations. Administrators and maintenance users can set audit log time windows. Note that because not all event views can be constrained by time. maintenance users. flow data.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 defaults you configured on this page. as time moves forward. RUA users. RNA events. see Setting Event Time Constraints in the Analyst Guide. the settings for the three types of time window disappear and a new Global Time Window setting appears. the time window “slides” so that you see only the events for the range you configured (in this example. client applications. You can either use Multiple time windows. services. for the last day) • Version 4. If you use a single time window. RNA event analysts. There are three types of events for which you can set the default time window. host attributes. and event views for custom tables that can be constrained by time. time window settings have no effect on event views that display RNA hosts. There are three types of time window: • • static.9. one for each of these types of events. one day ago) to the present. All user types can set event time windows. Requires: DC/MDC The Health Monitoring Time Window sets the default time window for health events. or you can use a Single time window that applies to all events.

As you change event views. Time Window Settings Setting Show the Last Sliding Description This setting allows you to configure a sliding default time window of the length you specify. Show the Last Static/Expanding This setting allows you to configure either a static or expanding default time window of the length you specify. The appliance displays all the events generated from a specific start time (for example. the appliance displays all the events generated from a specific start time (for example. As you change event views. 2038 (UTC).9. the time window “slides” so that you always see events from the last hour. the time window stays fixed so that you see only the events that occured during the static time window. the appliance displays all the events generated from a specific start time (for example. to the present. 1 hour ago). IMPORTANT! The maximum time range for all time windows is from midnight on January 1. For static time windows (enable the Use End Time check box).1 Sourcefire 3D System Administrator Guide 31 . For expanding time windows (disable the Use End Time check box). 1 hour ago) to the present. Version 4. the time window expands to the present time. to the time when you first viewed the events. 1 hour ago). 1970 (UTC) to 3:14:07 AM on January 19. As you change event views.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 The Time Window Settings table explains the kinds of default time windows you can configure.

The current day begins at midnight. As you change event views. Current Week Static/Expanding This setting allows you to configure either a static or expanding default time window for the current week. the appliance displays the Events by Priority and Classification workflow. The appliance is configured with a default workflow for each event type. For static time windows (enable the Use End Time check box). For example. For example. depending on the type of analysis you are performing. each of which presents intrusion event data in a different way. For each event type. Note that if your analysis continues for over 24 hours before you log out. the time window expands to the present time. the appliance displays all the events generated from midnight to the time when you first viewed the events. the appliance displays all the events generated from midnight Sunday to the present.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Time Window Settings (Continued) Setting Current Day Static/Expanding Description This setting allows you to configure either a static or expanding default time window for the current day. As you change event views. As you change event views. based on the time zone setting for your current session. This means whenever you view intrusion events (including reviewed intrusion events). For static time windows (enable the Use End Time check box). this time window can be more than 1 week. the appliance displays all the events generated from midnight to the present. based on the time zone setting for your current session.9. the time window stays fixed so that you see only the events that occured during the static time window. the Events by Priority and Classification workflow is the default for intrusion events. this time window can be more than 24 hours.1 Sourcefire 3D System Administrator Guide 32 . For expanding time windows (disable the Use End Time check box). As you change event views. For expanding time windows (disable the Use End Time check box). the time window expands to the present time. Version 4. the time window stays fixed so that you see only the events that occured during the static time window. The current week begins at midnight on the previous Sunday. you can choose between ten different intrusion event workflows. the appliance ships with at least one predefined workflow. Default Workflows Requires: Any A workflow is a series of pages displaying data that analysts use to evaluate events. Note that if your analysis continues for over 1 week before you log out. the appliance displays all the events generated from midnight to the time when you first viewed the events.

you can only configure the default workflow for the audit log.9. on a 3D Sensor without an IPS license. As another example. For general information on workflows. intrusion event analysts cannot set default RNA workflows. The following graphic shows the Defense Center version of the Default Workflows section. but also on your user role. see Understanding and Using Workflows in the Analyst Guide. Keep in mind that the default workflows you are able to configure depend not only on the appliance you are using. on the Defense Center. however. Version 4.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 You can. For example.1 Sourcefire 3D System Administrator Guide 33 . change the default workflow for each event type using the Default Workflows sections of the Event View Settings page.

South America.9. Click Save. The time zone is set. you would select New York after selecting America in the first time zone box. select the continent or area that contains the time zone you want to use. Version 4. From the box on the right. you must change it back to UTC time in order to view accurate local time on the appliance. The Time Zone Preference page appears. For more information about time synchronization between the Defense Center and the sensors. When you configure a time zone. click Preferences. For example. In the toolbar. The User Preferences page appears. it applies only to your user account and is in effect until you make further changes to the time zone. or Canada. if you want to use a time zone standard to North America. 5. Click Time Zone Settings. To change your time zone: Access: Any 1. For example. From the box on the left. see Synchronizing Time on page 354.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Setting Your Default Time Zone Requires: Any You can change the time zone used to display events from the standard UTC time that the appliance uses. if you want to use Eastern Standard Time. WARNING! The Time Zone function assumes that the default system clock is set to UTC time.1 Sourcefire 3D System Administrator Guide 34 . select America. 2. 3. select the zone (city name) that corresponds with the time zone you want to use. If you have changed the system clock on the appliance to use a local time zone. 4.

the Dashboard List page appears. The options in the drop-down list are based on the access privileges for your user account. The default home page is the dashboard (Analysis & Reporting > Event Summary > Dashboards). If you do not have a default dashboard defined. The default dashboard appears when you select Analysis & Reporting > Event Summary > Dashboards. see Using Dashboards on page 59. In the toolbar. click Preferences. user accounts with Policy & Response Administrator access have different options from accounts with Intrusion or RNA Event Analyst full or read-only access. who use the Welcome page.1 Sourcefire 3D System Administrator Guide 35 . The User Preferences page appears. 4. 2. The User Preferences page appears. For general information on dashboards. except for user accounts with Restricted Event Analyst access. Click Save. Maintenance access. In the toolbar. 3. IMPORTANT! User accounts with Restricted Event Analyst access cannot use the dashboard and therefore cannot specify a default dashboard.Introduction to the Sourcefire 3D System Specifying Your User Preferences Chapter 1 Specifying Your Home Page Requires: Any You can specify a page within the web interface as your home page for the appliance. Specifying Your Default Dashboard Requires: Any You can specify one of the dashboards on the appliance as the default dashboard. Restricted Event Analyst full or read-only access. Your home page preference is saved.9. To specify your home page: Access: Any 1. or Administrator access. Click Home Page. The Home Page page appears. Select the page you want to use as your home page from the Opening Screen drop-down list. That is. To specify your default dashboard: Access: Any 1. click Preferences. Version 4.

and thresholding the rule. You can also view the rule documentation and edit the rule. As the name implies. if you access the menu while viewing an RNA event. certain pages in the web interface support a pop-up context menu that you can use as a shortcut for accessing other features in the Sourcefire 3D System. hover your pointer over one of the hotspots. To access the context menu: Access: Any 1.9. 4. You can access the context menu on the following pages. Using the Context Menu Requires: Any For your convenience. The Dashboard Settings page appears. Click Save. disabling. Version 4. On one of the hotspot-enabled pages in the web interface. You can then select a dashboard to view. if you access the context menu while viewing an intrusion event that was triggered by an intrusion rule. The Rule Editor page for intrusion rules contains a hotspot over each intrusion rule.Introduction to the Sourcefire 3D System Using the Context Menu Chapter 1 2. Note that if you try to access the context menu for a web page or location that doesn’t support the Sourcefire-specific menu. • • Event pages (drill-down pages and table views) contain hotspots over each event. If you select None. Click Dashboard Settings. the contents of the menu depend on the context where you access it. when you select Analysis & Reporting > Event Summary > Dashboards. Your default dashboard preference is saved. However.1 Sourcefire 3D System Administrator Guide 36 . For example. the context menu provides you with the option to view the event in a separate browser window. the Dashboard List page appears. you have a range of options that includes enabling. 3. suppressing. Select the dashboard you want to use as your default from the Default Dashboard drop-down list. A “Right-click for menu” message appears. the normal context menu for your browser appears.

sourcefire. A pop-up context menu appears with options that are appropriate for the hotspot. In this guide you will find information about managing Master Defense Centers. configuring system settings and system policies. analyzing RNA. but in an easy-to-print format. 3. managing user accounts.Introduction to the Sourcefire 3D System Documentation Resources Chapter 1 2. and using event reports. which includes information about installing the appliance as well as hardware specifications and safety information. Right-click your pointing device. system management. Select one of the options by left-clicking the name of the option. scheduling tasks. RUA.com/). RNA Event Analysts. In this guide you will find information about managing RNA and IPS policies. the following menu appears if you right-click over an intrusion event. and monitoring the health of your appliances. Defense Centers. Version 4. The online help includes information about the tasks you can complete on the web interface. which together include the same content as the online help. The CD also contains copies of various API guides and supplementary material. You can reach the online help in two ways: • • by clicking the context-sensitive help links on each page by selecting Operations > Help > Online. The Analyst Guide contains information for Intrusion Event Analysts. The Documentation CD also contains copies of the Defense Center Installation Guide and the 3D Sensor Installation Guide. and 3D Sensors. and Policy & Response Administrators.1 Sourcefire 3D System Administrator Guide 37 .9. Documentation Resources The Sourcefire 3D System documentation set includes online help and PDF files. including procedural and conceptual information about user management. For example. The Documentation CD contains a PDF version of the Sourcefire 3D System Administrator Guide and the Sourcefire 3D System Analyst Guide. You can access the most up-to-date versions of the documentation on the Sourcefire Support web site (https://support. A new browser window opens based on the option you selected. and intrusion data. and IPS and RNA analysis. The Administrator Guide contains information specifically for administrators and maintenance users.

or DC3000 appliance used as a Defense Center Version 4. Virtual Defense Center. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Documentation Conventions This documentation includes information about which Sourcefire 3D System components are required for each feature and which user roles have permission to complete each procedure. All platform information is formatted with an orange typeface. DC1000. The following table defines the abbreviations used to indicate each different platform requirement: Platform and Licensing Requirement Abbreviations Requires Acronym 3D Sensor Indicates One of the following Series 1 or Series 2 sensors: • 3D500 • 3D1000 • 3D2000 • 3D2100 • 3D2500 • 3D3500 • 3D4500 • 3D6500 • 3D9900 This acronym on its own indicates that the task in question can be performed on any of these sensors even if an IPS license is not applied on the sensor and the sensor is not managed. Any DC Any appliance with any combination of licenses A DC500. Platform requirement information for specific aspects of a feature is provided where needed. Platform Requirements Conventions The Requires statement at the beginning of each section in this documentation indicates the combination of appliance platform and licenses you need to use the feature described in the section.1 Sourcefire 3D System Administrator Guide 38 . Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section.9.

Access Requirements Conventions The Access statement at the beginning of each procedure in this documentation indicates the access role required to use the feature described in the section. For example. to manage a Defense Center with a Master Defense Center.Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Platform and Licensing Requirement Abbreviations (Continued) Requires Acronym DC/MDC IPS RNA RUA Indicates A DC3000 appliance used as a Defense Center or a Master Defense Center A 3D Sensor licensed with the IPS technology An RNA license An RUA license An or conjunction indicates that the task or feature is available on either of the indicated platforms. you need both a Defense Center and a Master Defense Center. The following table defines the abbreviations used to indicate each different platform requirement: Access Requirement Abbreviations Requires Acronym Admin Any Any Analyst Any except Restricted Indicates User must have the Administrator role User can have any role User can have any analyst role User can have any role except Restricted Analyst or Restricted Analyst (Read Only) Version 4.9. All access information is formatted with a green typeface. so the Changing an Expired Password topic has a Requires statement of DC/MDC or 3D Sensor.1 Sourcefire 3D System Administrator Guide 39 . so the Adding a Master Defense Center topic has a Requires statement of MDC + DC. you can change an expired password on a Defense Center or Master Defense Center or on a 3D Sensor. A “+” conjunction indicates that the platforms are required in combination. In contrast.

a user must have the RNA Event Analyst or RNA Event Analyst (Read Only) role or the Restricted Event Analyst or Restricted Event Analyst (Read Only) role with RNA Hosts Data set to Show All Data or to show a specific search. to view the Hosts network map. A “+” conjunction indicates that the platforms are required in combination. Rule thresholding in the packet view provides an example of required combined access roles. The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin.1 Sourcefire 3D System Administrator Guide 40 .Introduction to the Sourcefire 3D System Documentation Conventions Chapter 1 Access Requirement Abbreviations (Continued) Requires Acronym Any Analyst except Restricted Any IPS Indicates User can have any analyst role except Restricted Analyst or Restricted Analyst (Read Only) User must have the Intrusion Event Analyst role or Intrusion Event Analyst (Read Only) role or the Restricted Event Analyst role or Restricted Event Analyst (Read Only) role with rights to that function User must have the Intrusion Event Analyst role or Restricted Event Analyst role with rights to that function User must have the Intrusion Event Analyst (Read Only) role or Restricted Event Analyst (Read Only) role with rights to that function User must have the Maintenance role User must have the Policy & Response Administrator role User must have the RNA Event Analyst or RNA Event Analyst (Read Only) or Restricted Event Analyst or Restricted Event Analyst (Read Only) with rights to that function User must have the RNA Event Analyst role or Restricted Event Analyst role with rights to that function User must have the RNA Event Analyst (Read Only) role or Restricted Event Analyst (Read Only) role with rights to that function IPS IPS-RO Maint P&R Admin Any RNA RNA RNA-RO A “/” conjunction indicates that the task or feature is available to users with one or more of the indicated platforms. You must have the Administrator role or have the Policy & Response Administrator role in combination with the Intrusion Event Analyst role or the Restricted Event Analyst role with Intrusion Events Data set to Show All Data or to show a specific search to access the packet view and set thresholding for a rule Version 4. For example.9.

the following table lists the private IPv4 address spaces in CIDR notation. For example.0/12 192.0. and standard text rules PEP CIDR notation uses a network IP address combined with a bit mask to define the IP addresses in the specified range.255 172.0.255.240.0.0 255.0 255.0.0/16 IP Addresses in CIDR Block 10.9.0.1 Sourcefire 3D System Administrator Guide 41 .048.255.2.255 Subnet Mask 255. For example. the Sourcefire 3D System uses 10.0/8 172.0.0. As a result.0.0.0. without changing your user input. CIDR Notation Syntax Examples CIDR Block 10.3/8.0 Number of IP Addresses 16.255.168.777 .0/8.255. IP Address Conventions Requires: Any You can use Classless Inter-Domain Routing (CIDR) notation to define IP address ranges in many places in the Sourcefire 3D System.2. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.31.168.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.16.168.255 192.255.0.0. if you type 10. variables.1.0 10.576 65. the Sourcefire 3D System uses only the masked portion of the network IP address you specified. but the web interface continues to display 10.16.536 When you use CIDR notation to specify a range of IP addresses.0.0 172.216 1.0.0 192.1.3/8. Version 4. including but not limited to the following: • • • • • • • • RNA detection policies custom topologies auto-assigned networks for user-defined host attributes traffic profiles compliance rules and white lists active scan targets intrusion policies.

the Sourcefire 3D System does not require it.1 Sourcefire 3D System Administrator Guide 42 . although Sourcefire recommends the standard method of using a network IP address on the bit boundary when using CIDR notation.9. Version 4.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 In other words.

9. Consult your original documentation or contact Sourcefire Support for information about performing the initial setup on those sensor models. you are presented with a series of start-up pages. See the following sections for more information: • • • Setting Up 3D Sensors on page 44 explains how to complete the setup process for Series 2 3D Sensors. Version 4. you may have a Series 1 3D Sensor. Newer models of the 3D Sensor. called Series 2 sensors. What’s Next? on page 52 provides detailed lists of the next tasks to be performed by each type of user. Note that if you purchased your sensor prior to 2008.1 Sourcefire 3D System Administrator Guide 43 . Setting up Defense Centers on page 47 explains how to complete the setup process for Defense Centers. provide a rapid set up feature and a status page. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide.Performing the Initial Setup Chapter 2 Administrator Guide After installing your Defense Center or 3D Sensor as described in the Installation Guide and logging into the web interface for the first time. To perform the initial setup of a Virtual 3D Sensor.

and logging into the 3D Sensor’s web interface (as described in the 3D Sensor Installation Guide). If the initial setup is interrupted or if a second user logs in while it is underway.9. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. TIP! The initial change to the admin user password changes the root password for the shell account. Avoid using words that appear in a dictionary. the results can be unpredictable. To complete the initial setup: Access: Admin 1. enter a new password for the admin user account and for the root password for the shell account. After physically installing the 3D Sensor.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 Setting Up 3D Sensors Requires: 3D Sensor Newer models of the 3D Sensor (that is. Version 4. Under Change Password. Series 2 sensors) provide a simple web form to collect information about your network environment and how you intend to deploy the sensor. the Install page appears so that you can continue the setup process. The same password is used for both accounts. Use the command line interface on the appliance for subsequent changes to the root password. in the New Password and Confirm fields. These sensors include the following models: • • • • • • • • • 3D500 3D1000 3D2000 3D2100 3D2500 3D3500 3D4500 3D6500 3D9900 You can view illustrations of each model in the 3D Sensor Installation Guide to determine your sensor model. setting up the IP address for the management interface.1 Sourcefire 3D System Administrator Guide 44 . WARNING! Prepare for the initial setup and complete it promptly after you begin. Defense Centers use the setup process in Setting up Defense Centers on page 47.

Note that if you use an NTP server to set the time. this step is unnecessary as the current software will synchronize automatically. you can specify the Defense Center as the sensor’s NTP server. You have two options: • • If you deployed the sensor as an inline IPS using paired sensing interfaces.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 2. IMPORTANT! If both your Defense Center and your sensors are running current software. Note that if you are managing the sensor with a Defense Center and the Defense Center itself is set up as an NTP server. under Time Settings.9. select Passive Mode. You can use the IP address of the Defense Center or. Under Remote Management. indicate whether you want to manage the 3D Sensor with a Defense Center. its hostname.1 Sourcefire 3D System Administrator Guide 45 . resulting in unexpected network behavior. Under Network Settings. If your sensor and Defense Center are separated by a network address translation (NAT) device. indicate how you want to set the time for the 3D Sensor. Version 4. enter the settings that you want to use for the management IP address. Under Detection Mode. Note that if you used the configure-network script before logging into the web interface. if your Defense Center is running current software and your sensors are running earlier software. 3. if you specify a DNS server. Optionally. you must also specify the primary and secondary DNS servers. WARNING! If you select Inline with Failopen Mode when the sensor is deployed passively. 4. Refer to Working in NAT Environments on page 112 and Adding Sensors to the Defense Center on page 117 for more information. 5. and gateway fields are pre-populated with your settings. The registration key is a single-use. If you deployed the sensor as a passive IDS on your network. the IP address. user-created string that you will also use from within the Defense Center’s web interface when you complete the sensor registration process. netmask. specify how you want to deploy the 3D Sensor. You can set the time manually or via network time protocol (NTP) from an NTP server. you may cause your network to be bridged. select Inline with Failopen Mode. defer Defense Center management until after you complete the initial setup.

you do not need to add a product license. For detailed information on adding new rules to custom policies in the default state or in the disabled rule state.com/. To queue an immediate update from the Sourcefire support site. Under License Settings. The activation key was previously emailed to the contact person identified on your support contract. Note that you will be prompted for the license key and an activation key. Version 4. indicate whether you want to add a product license to the 3D Sensor.1 Sourcefire 3D System Administrator Guide 46 .9. enter the license key in the license key field.Performing the Initial Setup Setting Up 3D Sensors Chapter 2 6. select Update Now. Select the state for adding new rules to intrusion policies as disabled or in the predefined default state. • To use IPS functionality (either by itself or with RNA or RUA functionality). you must add a product license to the 3D Sensor. You have two options: • To use only the RNA or RUA functionality without IPS. You can also instruct the system to reapply intrusion policies after the SEU import completes. 7. You control licensing for RNA or RUA through the Defense Center managing the sensor. Skip to step 8. To obtain a product license. click the link to navigate to https:// keyserver. You will automatically create an RNA detection engine without a policy. check the Enable Recurring SEU Imports check box to configure automatic SEU imports and specify the update frequency. switch to a host that can and navigate to the keyserver web page. Under Recurring SEU Imports. If your current host cannot access the Internet. refer to Using Recurring SEU Imports in the Analyst Guide. Follow the on-screen instructions to generate an email containing the license file and paste it into the License field. To add a product license.sourcefire. and click Add/Verify.

the results can be unpredictable. The appliance logs you out. After physically installing the Defense Center. The 3D Sensor is configured according to your selections. You can check the task progress at Operations > Monitoring > Task Status.Performing the Initial Setup Setting up Defense Centers Chapter 2 8. If you agree to abide by its provisions. Version 4. WARNING! Prepare for the initial setup and complete it promptly after you begin. select the check box and click Apply. the Install page appears so that you can continue the setup process. TIP! Applying a default policy to detection engines can take several minutes. A dashboard page appears after you log back in. TIP! If you used the option to connect through the management port to perform the initial setup. See Using Dashboards on page 59 for more information.9. remember to connect the cable to the protected management network. Setting up Defense Centers Requires: DC/MDC The first time you log in to the web interface. which indicates the appliance is now operational.1 Sourcefire 3D System Administrator Guide 47 . and logging into the Defense Center’s web interface (as described in the Defense Center Installation Guide). read the agreement carefully. Defense Centers and Master Defense Centers provide a simple web form to collect information about your network environment and how you intend to deploy the appliance. If the initial setup is interrupted or if a second user logs in while it is underway. Under End User License Agreement. You will see no intrusion events until it completes. See What’s Next? on page 52 for some suggestions about how to proceed after you complete these initial startup pages. setting up the IP address for the management interface.

you can set the appliance to operate as a Defense Center or a Master Defense Center. 3. For more information on the differences between the features provided by a Master Defense Center and a Defense Center. defer remote management until after you complete the initial setup. Under Network Settings. Version 4. Under Remote Management. 2. user-created string that you will also need to use when you register the Defense Center through the Master Defense Center’s web interface. The same password is used for both accounts.9. Avoid using words that appear in a dictionary. See Working in NAT Environments on page 112 and Adding a Master Defense Center on page 165 for more information. netmask. You can use the IP address of the Master Defense Center or. The registration key is a single-use. its hostname.Performing the Initial Setup Setting up Defense Centers Chapter 2 To complete the initial setup: Access: Admin 1. see Master Defense Center and Defense Center Functional Comparison on page 159. enter the settings that you want to use for the management IP address. IMPORTANT! If your Defense Center and Master Defense Center are separated by a network address translation (NAT) device. IMPORTANT! A Master Defense Center can manage only Defense Centers. in the New Password and Confirm fields. 4. under Operational Mode. Use the command line interface on the appliance for subsequent changes to the root password. the Remote Management section becomes unnecessary and is hidden from the form. and not 3D Sensors.1 Sourcefire 3D System Administrator Guide 48 . the IP address. if you specify a DNS server. enter a new password for the admin user account and the root password shell account. Skip to step 5. If you select the Master Defense Center mode. Under Change Password. Defense Center capabilities are not a subset of a Master Defense Center. and gateway fields are pre-populated with your settings. TIP! The initial change to the admin user password changes the root password for the shell account. indicate whether you want to manage the Defense Center with a Master Defense Center. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. Note that if you used the configure-network script before logging into the web interface. If you are installing a DC3000.

under Sensor Registration. If you are installing a DC3000 and your operational mode is Master Defense Center. Under Time Settings. you should defer remote management until after you complete the initial setup. If your 3D Sensor and Defense Center are separated by a network address translation (NAT) device. 6. Master Defense Center and all sensors are running current software. the Defense Center Registration portion of the form is visible. The registration key is the single-use. On Defense Centers. You can set the time manually or via network time protocol (NTP) from an NTP server. its hostname. You can use the IP address of the Defense Center or. IMPORTANT! If your Defense Center. user-created string you used in the Defense Center’s web interface when you configured remote management. defer remote management until after you complete the initial setup. if you specify a DNS server. its hostname. See Working in NAT Environments on page 112 and Adding a Defense Center on page 168 for more information. indicate how you want to set the time for the Defense Center. if you specify a DNS server. you must also specify the primary and secondary DNS servers. Version 4. 7. IMPORTANT! If your Defense Center and Master Defense Center are separated by a network address translation (NAT) device. IMPORTANT! Use this function only if you have previously installed 3D Sensors that are pending registration with this Defense Center. The registration key is the single-use. indicate whether you want to apply default policies. this step is unnecessary as the current software will synchronize automatically. You can use the IP address of the 3D Sensor or. you can specify the Master Defense Center as the Defense Center’s NTP server. Note that if you use an NTP server to set the time. Note that if you are managing the Defense Center with a Master Defense Center and the Master Defense Center itself is set up as an NTP server. user-created string used in the 3D Sensor’s web interface when you configured remote management for the sensor. Click Add to register each newly listed 3D Sensors with this Defense Center. Use these fields only to register Defense Centers where you have already configured remote management by this Master Defense Center.Performing the Initial Setup Setting up Defense Centers Chapter 2 5. Refer to Working in NAT Environments on page 112 and Adding Sensors to the Defense Center on page 117 for more information.1 Sourcefire 3D System Administrator Guide 49 .9.

Under End User License Agreement. The activation key was previously emailed to the contact person identified on your support contract. switch to a host that can and navigate to the keyserver web page. and to enable Version 4. Under Recurring SEU Imports. check the Enable Recurring SEU Import check box to configure automatic SEU imports and specify the update frequency. 9. To queue an immediate update from the Sourcefire support site. remember to connect the cable to the protected management network. Communication Ports The Sourcefire 3D System requires the use of specific ports to communicate internally and externally.Performing the Initial Setup Communication Ports Chapter 2 8.If you agree to abide by its provisions. which indicates the appliance is operational. If your current host cannot access the Internet. The Defense Center or Master Defense Center is configured according to your selections.9. between Defense Centers and sensors. TIP! If you used the option to connect through the management port to perform the initial setup. Note that you will be prompted for the license key and an activation key. Under License Settings.1 Sourcefire 3D System Administrator Guide 50 .sourcefire. See What’s Next? on page 52 for some suggestions about how to proceed after you complete these initial startup pages. select Update Now. A dashboard page appears after you log back in. To obtain a product license. For detailed information on adding new rules to custom policies in the default state or in the disabled rule state see Using Recurring SEU Imports in the Analyst Guide. 10. read the agreement carefully. Follow the on-screen instructions to generate an email containing the license file and paste it into the License field. Select the state for adding new rules to intrusion policies as disabled or in the predefined default state.com/.The appliance logs you out. add a product license and any required feature licenses to the Defense Center. click the link to navigate to https:// keyserver. You can also instruct the system to reapply intrusion policies after the SEU import completes. select the check box and click Apply. See Using Dashboards on page 59 for more information.

Open this port for communications between the Defense Center and Intrusion Agents. Refer to the Required Open Ports table for more information on functions and their associated ports. Open this port only if you are using a remote syslog server.Performing the Initial Setup Communication Ports Chapter 2 certain functionality within the network deployment. Open this port when you connect to a remote web server through the RSS widget. Open this port for communicatiosn between the Defense Center and RUA Agents.1 Sourcefire 3D System Administrator Guide 51 . 636 443 514 1241 1660 1812 and 1813 3306 8301 Description ftp ssh/ssl telnet smtp dns dhcp http snmp ldap https syslog Nessus Nmap FreeRADIUS RUA Agent Intrustion Agent Note that you must open both ports to ensure that FreeRADIUS functions correctly. Notes Version 4. 80 162 389.9. Required Open Ports Ports 20. 21 22 23 25 53 67 68 .

See Managing Users on page 264 for more information about user roles. or Requires: RUA.Performing the Initial Setup What’s Next? Chapter 2 Required Open Ports (Continued) Ports 8302 8305 18183 Description eStreamer Management Virtual Network OPSEC SAM Open this port for communications between the Defense Center and v. Maintenance user. • Administrator User Tasks on page 53 describe the steps that you must complete before Policy & Response Administrator users and analyst users can begin their tasks. or RNA Event Analyst user) and what appliance you are using. you can perform much of the process on the Defense Center itself.x 3D Sensors. Policy & Response Administrator user. Review the tasks in the following sections. RNA. Maintenance User Tasks on page 54 explain some of the steps in the process that Maintenance users can perform after Administrator users finish their required tasks. your next steps depend on the role assigned to your user account (Administrator user. For standalone 3D Sensor deployments (that is. • • Version 4. or RUA. a user with Administrator access must perform the first steps.1 Sourcefire 3D System Administrator Guide 52 . tasks that require a Defense Center are preceded with Requires: DC. Requires: RNA. the task is preceded with Requires: IPS.8. Policy & Response Administrator User Tasks on page 55 describe some of the policies and custom rules that Policy & Response Administrator users can create and apply so that analyst users receive useful data for their analyses. deployments that do not include a Defense Center and do not use RNA). For deployments that include a Defense Center. Similarly. which are based on the user account privileges required for the task. if your Defense Center or 3D Sensor must be licensed for IPS. Intrusion Event Analyst user. 4. IMPORTANT! Tasks that must be completed on specific hardware or software platforms are indicated by special text: For example.9. Notes What’s Next? Requires: Any After you complete the initial setup for the Sourcefire 3D System.

but you cannot use high availability mode directly on the Master Defense Center itself.9.1 Sourcefire 3D System Administrator Guide 53 . you must create an authentication object for that server as described in Creating LDAP Authentication Objects on page 269. Sourcefire recommends that you use the Defense Center’s web interface rather than the sensor’s web interface to manage the sensor and view the events that it generates. 2. See Configuring Remote Access to the Defense Center on page 386 for information about setting up management links between your sensors and the Defense Center. Requires: DC If you want to authenticate users using an external authentication server. TIP! After you set up management. If you want to manage your 3D Sensors with a Defense Center but did not enable remote management as part of the initial setup on the sensor. Intrusion Event Analyst User Tasks on page 57 describe the features that Intrusion Event Analyst users can use to learn about the kinds of attacks that are launched against assets on your network. Administrator User Tasks Requires: Any Administrator users have a superset of tasks. Version 4. 3. set up high availability as explained in Configuring High Availability on page 145. In most network environments. the sensors you add to the primary Defense Center are automatically added to the secondary Defense Center.Performing the Initial Setup What’s Next? Chapter 2 • • RNA Event Analyst User Tasks on page 56 describe the features that RNA Event Analyst users can use to learn about the assets on your network. You must complete the steps outlined in Working with Sensors on page 113 on the Defense Center and on the sensors to complete the process. The first steps for the Administrator user are as follows: Access: Admin 1. TIP! You can use high availabilty mode on Defense Centers which are managed by a Master Defense Center. Tasks essential to initial setup are listed below. Requires: DC If you are deploying two Defense Centers in high availability mode. you should set it up now.

you need to enable it in a system policy on the Defense Center and apply that policy to any appliances where users will authenticate to the external server. and Security Enhancement Updates (SEUs) and apply them to your Defense Center where required. Maintenance User Tasks. By default. Apply any available software patches or vulnerability database updates to managed sensors where required. you should configure one that meets the needs of your network and security environment. The auditing feature records events based on the user account name. If you did not already set up a system policy as part of the initial setup. Create new user accounts that match the roles you want to assign to your users. The next section. Check for any available software patches. Note that a Maintenance user can also set up health policies. See Using Health Monitoring on page 482 for more information. vulnerability database updates. if you want to use external authentication. See Managing Users on page 264 for more information. Note that. Maintenance User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. you must modify the default detection engine. See Managing System Policies on page 320 for more information. a Maintenance user or an Administrator user can perform the following tasks: Version 4. Requires: DC Set up health monitoring policies and apply them to your managed sensors and to the Defense Center itself. so it is much better to have an account for each user rather than allowing multiple users to access the appliance from one or two accounts. 5. See Importing SEUs and Rule Files in the Analyst Guide and Updating System Software on page 398 for more information.1 Sourcefire 3D System Administrator Guide 54 . The health monitoring feature includes a range of modules that you can enable or disable based on the needs of your network environment. You can also create different policies on your Defense Center and apply them to the managed sensors where it is appropriate.Performing the Initial Setup What’s Next? Chapter 2 4. 6. To take advantage of the multiple detection engine feature. See Using Detection Engines and Interface Sets on page 185 for more information about examining traffic on multiple network segments with a single sensor. Patches and updates are available on the Sourcefire Support site.9. 8. describes the steps that a user with Maintenance access can perform. each 3D Sensor has a single detection engine that encompasses all of the available sensing interfaces (or all of the available fast-packetenabled interfaces) on the sensor. 7.

Maintenance users can: Access: Maint/Admin 1. Develop a backup and restore plan. See Managing Intrusion Rules in the Analyst Guide and Using Advanced Settings in an Intrusion Policy in the Analyst Guide for more in-depth information about configuring intrusion policies. sending a notification by email or SNMP or simply generating a syslog alert. See Using Backup and Restore on page 413 for details about backing up configurations as well as event data. Requires: IPS Create and apply intrusion policies to the IPS-related detection engines on your 3D Sensor. Policy & Response Administrator users can: Access: P&R Admin/ Admin 1. Compliance policies can contain rules based on nearly any kind of network activity that your 3D Sensor can detect. Requires: DC If a user with Administrator privileges has not configured health monitoring. responses. 3. See Scheduling Tasks on page 425 for more information. Requires: RNA If a compliance policy violation occurs. For more information on .Performing the Initial Setup What’s Next? Chapter 2 To continue the initial setup. 2. describes the steps that a user with Policy & Response Administrator access can perform. you can set up and apply health policies on your managed sensors and the Defense Center. Note that you can also schedule regular backups of your appliance. 2. The next section. Requires: IPS Part of the process for creating an intrusion policy includes enabling the appropriate intrusion rules and fine-tuning the preprocessors and packet decoders to match your network traffic. Policy & Response Administrator User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. including anomalous network traffic patterns. See Configuring Compliance Policies and Rules in the Analyst Guide. 4. 3. Version 4. you can specify that the Defense Center automatically respond to it in one of several ways.1 Sourcefire 3D System Administrator Guide 55 . See Using Health Monitoring on page 482 for more information. including blocking a suspect host at the firewall or router.9. a Policy & Response Administrator user or an Administrator user can perform the following tasks: To continue the initial setup. Requires: RNA Set up compliance policies to determine when prohibited activity occurs on your network. see Configuring Responses for Compliance Policies in the Analyst Guide. Set up scheduled tasks for any jobs that you want to perform on a regular basis. Policy & Response Administrator User Tasks. See Using Basic Settings in an Intrusion Policy in the Analyst Guide for more information.

RNA Event Analyst users can: Access: Any RNA/ Admin 1. or via SNMP) if a specific intrusion rule is triggered. See Viewing RNA Event Statistics in the Analyst Guide for more information. or Restricted Event Analyst access can perform. describe the steps that a user with Intrusion Event Analyst. See Using Host Profiles in the nAnalyst Guide for more information. RNA Event Analyst. The next sections. If your network environment includes an OPSEC-compliant firewall. To continue the initial setup. unknown hosts. you may want to write your own rules to meet the unique needs of your network. which can provide you with a high-level view of the activity and events taking place on your network. Requires: IPS To ensure that your intrusion event analysts are informed as soon as possible regarding attacks against your most valuable network assets. Version 4. an RNA Event Analyst user or an Administrator user can perform the tasks listed below. which is an expandable tree view of all the hosts and services reported by RNA. and services that are prohibited by your security policies. 6. RNA Event Analyst User Tasks and Intrusion Event Analyst User Tasks. RNA Event Analyst (Read Only) users can perform any of these tasks. You can also use the host profile to set host criticality and to learn about the vulnerabilities reported for the operating system and services running on each host. 2. Similarly. Restricted Event Analyst users can perform most of these tasks. The network map provides you with an overview of your network and is a good tool for locating rogue access points. via email.Performing the Initial Setup What’s Next? Chapter 2 5.1 Sourcefire 3D System Administrator Guide 56 .9. you can also send SAM-based responses to the firewall. RNA Event Analyst User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. 3. The policies and rules that you create as a Policy & Response Administrator user determine the kinds of events that are seen by the RNA Event Analyst and Intrusion Event Analyst users on your appliance. but their event views are limited to specific IP address ranges. consider setting up automated notifications (that can be sent to the syslog. Begin by reviewing the summary statistics. Requires: RNA If you locate unknown hosts on the network map. RNA Event Analyst (Read-Only). Requires: IPS As you gain more experience with the intrusion rules provided by Sourcefire. See Configuring External Responses to Intrusion Events in the Analyst Guide for more information. See Understanding and Writing Intrusion Rules in the Analyst Guide and Rule-Writing Examples and Tips in the Analyst Guide to learn more about using the rule editor to write your own intrusion rules. Intrusion Event Analyst (Read-Only). See Using the Network Map in the Analyst Guide for more information. use the host profile feature to learn more about them. Requires: RNA Review the information in the network map.

Intrusion Event Analyst User Tasks Requires: Any After a user with Administrator privileges performs the initial configuration as described in Setting Up 3D Sensors on page 44. 6. 5. investigate. Most of these can be performed by Restricted Event Analyst users also. See Understanding and Using Workflows in the Analyst Guide for more information. you may want to create your own workflows. an Intrusion Event Analyst user or an Administrator user can perform the tasks listed below. client applications.1 Sourcefire 3D System Administrator Guide 57 . See Working with RNA Events in the Analyst Guide for more information. For example. Use any of the predefined workflows to view. then determine which might be behaving abnormally. Version 4.9. but their event views are limited to specific IP address ranges. Use the report designer to create CSV. You can review information for network hosts. See Working with Event Reports on page 232 for more information. services. Note that flow data is collected by your sensors only if the flow data option is enabled in the RNA detection policy. and host attributes. vulnerabilities. Requires: RNA Use flow data and traffic profiles to gain a different kind of insight into the activity on your network. See Working with Flow Data and Traffic Profiles in the Analyst Guide for more information. See Scheduling Tasks on page 425. As you grow more experienced with the Sourcefire 3D System. you can review the information collected by RNA’s traffic monitoring features and identify hightraffic hosts. and act on the events generated by your sensors.Performing the Initial Setup What’s Next? Chapter 2 4. Requires: RNA Use the RNA event workflows to review the activity that has occurred on your network over time. or PDF-based event and incident reports. and you can create and save report profiles to use later. 7. You can use the scheduler to automate reporting. You can also use the extensive search capability to define and save your own search criteria that you can use as part of your regular analysis. Note that the kinds of RNA events that are logged to the database are determined by the system policy on the managing Defense Center. HTML. You can automatically email a report when it is complete.

See Viewing Intrusion Event Statistics in the Analyst Guide for more information. See Working with Event Reports on page 232 for more information. As you grow more experienced with the Sourcefire 3D System. intrusion events are correlated with any available RNA data to generate an impact flag. which can provide you with a high-level view of the activity and events taking place on your network. HTML. Requires: IPS Use the incident handling feature to collect information about your investigation of possible intrusions on your network. See Handling Incidents in the Analyst Guide for more information. and you can create and save report profiles to use later. See Working with Intrusion Events in the Analyst Guide for more information. 3. 4. 5.9. You can use an incident to record details about your investigation. Begin by reviewing the summary statistics. You can automatically email a report when it is complete. Events with high impact are more likely to indicate that an attack is targeted against a vulnerable host on your network. See Understanding and Using Workflows in the Analyst Guide for more information. or PDF-based event and incident reports. and the appliance automatically records the amount of time you have the incident open. See Scheduling Tasks on page 425. You can also add intrusion event data that you believe might be important to your investigation of the incident. and act on the events generated by your sensors. 2. Requires: IPS Use the intrusion event views to determine which hosts on your network are the targets of attacks and the types of attacks that are attempted against them. Note that the events that you see are limited by the options that are enabled in the intrusion policy that is applied to your sensors.1 Sourcefire 3D System Administrator Guide 58 . investigate. You can use the scheduler to automate reporting. Version 4. Requires: RNA Note that on the Defense Center. you may want to create your own workflows. Intrusion Event Analyst users can: Access: Any IPS/ Admin 1. Use any of the predefined workflows to view. Use the report designer to create CSV.Performing the Initial Setup What’s Next? Chapter 2 To continue the initial setup. See Using Impact Flags to Evaluate Events in the Analyst Guide for more information.

or 3D Sensor.1 Sourcefire 3D System Administrator Guide 59 . Version 4. named Default Dashboard. You can change the time range to reflect a period as short as the last hour or as long as the last year.9. the Appliance Information widget tells you the appliance name. Each dashboard has one or more tabs. This dashboard provides the casual user with basic event and system status information for your Sourcefire 3D System deployment. Widgets are small. each of which can display one or more widgets in a three-column layout. Each dashboard has a time range that constrains its widgets.Administrator Guide Sourcefire 3D System dashboards provide you with at-a-glance views of current system status. and its remote manager. self-contained components that provide insight into different aspects of the Sourcefire 3D System.Using Dashboards Chapter 3 . as well as information about the status and overall health of the appliances in your deployment. model. The Sourcefire 3D System is delivered with several predefined widgets. Note that because not all widgets are useful for all types of appliances. current version of the Sourcefire 3D System software running on the appliance. For example. including data about the events collected and generated by the Sourcefire 3D System. Defense Center. the default dashboard differs depending on whether you are using a Master Defense Center. Each type of appliance is delivered with a default dashboard.

and system status data. You can share custom dashboards among all users of an appliance. • The Detailed Dashboard provides advanced users with detailed information about your Sourcefire 3D System deployment. you can access dashboards by selecting Analysis & Reporting > Event Summary > Dashboards. see Viewing Dashboards on page 91. or you can create a custom dashboard solely for your own use. and includes multiple widgets that summarize collected IPS.Using Dashboards Understanding Dashboard Widgets Chapter 3 By default. modify the predefined dashboards. Note that Restricted Event Analysts use the Flow Summary page instead of the Flow Summary Dashboard. You can also set a custom dashboard as your default dashboard. For more information. compliance. each of which can display one or more widgets in a three-column layout. including pages that are not dashboard pages.1 Sourcefire 3D System Administrator Guide 60 .9. see Viewing the Flow Summary Page in the Analyst Guide for more information. see the following sections: • • • Understanding Dashboard Widgets on page 60 Understanding the Predefined Widgets on page 65 Working with Dashboards on page 89 Understanding Dashboard Widgets Requires: Any Each dashboard has one or more tabs. or create a custom dashboard to suit your needs. RNA. although you can configure your appliance to display a different default home page. In addition to the default dashboard. the Defense Center is delivered with two other predefined dashboards: • The Flow Summary dashboard uses flow data to create tables and charts of the activity on your monitored network. each of which provides insight into a Version 4. see Understanding Flow Data in the Analyst Guide. You can use the predefined dashboards. the home page for your appliance displays the default dashboard. The Sourcefire 3D System is delivered with several predefined dashboard widgets. TIP! If you change the home page. For more information. for more information on flow summary data.

1 Sourcefire 3D System Administrator Guide 61 . the Appliance Information widget is available on all appliances for all user roles. Widgets are grouped into three categories: • • • Analysis & Reporting widgets display data about the events collected and generated by the Sourcefire 3D System. An unauthorized widget is one that you cannot view because you do not have the necessary account privileges. while the Compliance Events widget is available only on the Defense Center for users with Administrator. the Master Defense Center cannot access flow data. if you import a dashboard created either on a different kind of appliance or by a user with different access privileges. In addition. RUA events. the widget displays an error message.Using Dashboards Understanding Dashboard Widgets Chapter 3 different aspect of the Sourcefire 3D System.9. or RNA Event Analyst account privileges. see: • • • • Understanding Widget Availability on page 61 Understanding Widget Preferences on page 64 Understanding the Predefined Widgets on page 65 Working with Dashboards on page 89 Understanding Widget Availability Requires: Any The Sourcefire 3D System is delivered with several predefined dashboard widgets. add and remove widgets from tabs. that dashboard may contain unauthorized or invalid widgets. Although you cannot add an unauthorized or invalid widget to a dashboard. Operations widgets display information about the status and overall health of the Sourcefire 3D System. For example. If you import a dashboard onto a Master Defense Center that contains a Custom Analysis widget configured to display one of those data types. RNA events. These widgets are disabled and display error messages that indicate the reason why you cannot view them. Currently the only widget in this category displays an RSS feed. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role. Version 4. For more information. as well as rearrange the widgets on a tab. each dashboard has a set of preferences that determines its behavior. For example. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role: • • An invalid widget is one that you cannot view because you are using the wrong type of appliance. Intrusion Event Analyst. Miscellaneous widgets display neither event data nor operations data. and so on. You can minimize and maximize widgets. Also note that widgets cannot display data to which an appliance has no access.

keeping in mind that modifying a widget on a shared dashboard modifies it for all users of the appliance. as well as widgets that display no data. For example. Note than any content generated in table format can be sorted by clicking on the table column header. the content of a widget can differ depending on the type of appliance you are using. Sourcefire Appliances and Dashboard Widget Availability Widget Appliance Information Appliance Status Compliance Events Current Interface Status Current Sessions Custom Analysis Disk Usage Interface Traffic Intrusion Events Network Compliance Product Licensing Product Updates RSS Feed X X Master Defense Center X X X X X X X X X Defense Center X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 3D Sensor with IPS (and RNA) X 3D Sensor with RNA (only) X Version 4. You can delete or minimize unauthorized and invalid widgets. the Current Interface Status widget on a 3D Sensor displays the status of its sensing interfaces.9.1 Sourcefire 3D System Administrator Guide 62 . but on Defense Centers and Master Defense Centers the widget displays only the status of the management interface.Using Dashboards Understanding Dashboard Widgets Chapter 3 Similarly. see Minimizing and Maximizing Widgets on page 97 and Deleting Widgets on page 97. An X indicates that the appliance can display the widget. For more information. The Sourcefire Appliances and Dashboard Widget Availability table lists the valid widgets for each appliance.

IMPORTANT! dashboards.9.Using Dashboards Understanding Dashboard Widgets Chapter 3 Sourcefire Appliances and Dashboard Widget Availability (Continued) Widget System Load System Time White List Events Master Defense Center X X X Defense Center X X X 3D Sensor with IPS (and RNA) X X 3D Sensor with RNA (only) X X The User Roles and Dashboard Widget Availability table lists the user account privileges required to view each widget.1 Sourcefire 3D System Administrator Guide 63 . An X indicates the user can view the widget. User accounts with Restricted Event Analyst access cannot use User Roles and Dashboard Widget Availability Widget Appliance Information Appliance Status Compliance Events Current Interface Status Current Sessions Custom Analysis Disk Usage Interface Traffic Intrusion Events Network Compliance Product Licensing Administrator X X X X X X X X X X X X X X X X X X X X X X X X X Maintenance X X P&R Admin X IPS Analyst X X X X RNA Analyst X X X X Version 4.

You can only configure the update frequency for this widget. which displays the current status of the network interfaces for the appliance. Widget preferences can be simple. the following graphic shows the preferences for the Custom Analysis widget. To modify a widget’s preferences: Access: Any except Restricted 1. On the title bar of the widget whose preferences you want to change. Version 4. The preferences section for that widget appears. For example.Using Dashboards Understanding Dashboard Widgets Chapter 3 User Roles and Dashboard Widget Availability (Continued) Widget Product Updates RSS Feed System Load System Time White List Events Administrator X X X X X Maintenance X X X X P&R Admin X X X X X X X X X X X X IPS Analyst RNA Analyst Understanding Widget Preferences Requires: Any Each widget has a set of preferences that determines its behavior. which is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System.1 Sourcefire 3D System Administrator Guide 64 . Widget preferences can also be more complex.9. click the show preferences icon ( ). For example. the following graphic shows the preferences for the Current Interface Status widget.

On the widget title bar. For detailed information on the widgets delivered with the Sourcefire 3D System.9. can provide you with at-a-glance views of current system status. 3. Version 4. click the hide preferences icon ( preferences section. For information on the preferences you can specify for individual widgets. see Understanding the Predefined Widgets on page 65. including data about the events collected and generated by the Sourcefire 3D System. For more information. Make changes as needed. Your changes take effect immediately. see the following sections: • • • • • • • • • • • • • • • • Understanding the Appliance Information Widget on page 66 Understanding the Appliance Status Widget on page 67 Understanding the Compliance Events Widget on page 67 Understanding the Current Interface Status Widget on page 68 Understanding the Current Sessions Widget on page 69 Understanding the Custom Analysis Widget on page 69 Understanding the Disk Usage Widget on page 80 Understanding the Interface Traffic Widget on page 81 Understanding the Intrusion Events Widget on page 81 Understanding the Network Compliance Widget on page 82 Understanding the Product Licensing Widget on page 84 Understanding the Product Updates Widget on page 85 Understanding the RSS Feed Widget on page 86 Understanding the System Load Widget on page 87 Understanding the System Time Widget on page 87 Understanding the White List Events Widget on page 88 IMPORTANT! The dashboard widgets you can view depend on the type of appliance you are using and on your user role.Using Dashboards Understanding the Predefined Widgets Chapter 3 2. when used on dashboards.1 Sourcefire 3D System Administrator Guide 65 . ) to hide the Understanding the Predefined Widgets Requires: Any The Sourcefire 3D System is delivered with several predefined widgets that. see Understanding Widget Availability on page 61. as well as information about the status and overall health of the appliances in your deployment.

model. and model of the appliance the versions of the Sourcefire 3D System software. see Understanding Widget Preferences on page 64. The widget provides: • • the name. operating system. For more information. Snort. Version 4.1 Sourcefire 3D System Administrator Guide 66 .Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Appliance Information Widget Requires: Any The Appliance Information widget provides a snapshot of the appliance. and vulnerability database (VDB) installed on the appliance for managed appliances. as well as how recently the Defense Centers made contact • • You can configure the widget to display more or less information by modifying the widget preferences to display a simple or an advanced view. module pack. SEU. the name. the name and status of the communications link with the managing appliance for Defense Centers in a high availability pair.9. rule pack. the preferences also control how often the widget updates. and Sourcefire 3D System software and operating system versions of the peer Defense Center. management interface IP address.

see Using the Health Monitor on page 545. Understanding the Compliance Events Widget Requires: DC/MDC The Compliance Events widget shows the average events per second by priority. The preferences also control how often the widget updates. For more information. see Understanding Widget Preferences on page 64. over the dashboard time range. Note that because the Defense Center does not automatically apply a health policy to managed sensors.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Appliance Status Widget Requires: DC/MDC The Appliance Status widget indicates the health of the appliance and of any appliances it is managing. You can configure the widget to display appliance status as a pie chart or in a table by modifying the widget preferences. For more information.9. Version 4. You can click a section on the pie chart or one of the numbers on the appliance status table to go to the Health Monitor page and view the compiled health status of the appliance and of any appliances it is managing. you must manually apply a health policy or their status appears as Disabled.1 Sourcefire 3D System Administrator Guide 67 .

9. or 10Mb half duplex) of the interface Version 4. accessing compliance events via the dashboard changes the events (or global) time window for the appliance. or click the All graph to view all compliance events. see Viewing Compliance Events in the Analyst Guide.1 Sourcefire 3D System Administrator Guide 68 . Select Show All to display an additional graph for all compliance events. represented by a green ball (up) or a gray ball (down) the link mode (for example. Select one or more Priorities check boxes to display separate graphs for events of specific priorities. Note that only 3D Sensors have interface types other than the management interface. You can click a graph to view compliance events of a specific priority. inline. For more information on compliance events. as well as to select a linear (incremental) or logarithmic (factor of ten) scale. Understanding the Current Interface Status Widget Requires: Any The Current Interface Status widget shows the status of the network interfaces for the appliance. For each interface. In either case. passive. and unused.Using Dashboards Understanding the Predefined Widgets Chapter 3 You can configure the widget to display compliance events of different priorities by modifying the widget preferences. grouped by type: management. including events that do not have a priority. the events are constrained by the dashboard time range. see Understanding Widget Preferences on page 64. 100Mb full duplex. regardless of priority. The preferences also control how often the widget updates. For more information. the widget provides: • • • the name of the interface the link state of the interface.

1 Sourcefire 3D System Administrator Guide 69 . see Understanding Widget Preferences on page 64. Version 4. that is. The user that represents you. that is.9. The presets serve as examples and can provide quick access to information about your deployment. see Managing User Accounts on page 299 click the host icon ( ) next to any IP address to view the host profile for that computer. copper or fiber the amount of data received (Rx) and transmitted (Tx) by the interface The widget preferences control how often the widget updates. On the Current Sessions widget. Understanding the Current Sessions Widget Requires: Any The Current Sessions widget shows which users are logged into the appliance.Using Dashboards Understanding the Predefined Widgets Chapter 3 • • the type of interface. For more information. You can use these presets or you can create a custom configuration. you must select which table and individual field you want to display. the IP address of the machine where the session originated. see Understanding Widget Preferences on page 64. as well as the aggregation method that configures how the widget groups the data it displays. and the last time each user accessed a page on the appliance (based on the local time for the appliance). The Custom Analysis widget is delivered with several presets. When you configure the widget preferences. the user currently viewing the widget. Understanding the Custom Analysis Widget Requires: Any The Custom Analysis widget is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System. For more information. you can: • • click any user name to manage user accounts on the User Management page. is marked with a user icon and is rendered in bold type. see Viewing Audit Records on page 567 • The widget preferences control how often the widget updates. see Using Host Profiles in the nAnalyst Guide (Defense Center with RNA only) click any IP address or access time to view the audit log constrained by that IP address and by the time that the user associated with that IP address logged on to the web interface. which are groups of configurations that are predefined by Sourcefire.

and so on). how many unique versions of Linux. if you are using Sourcefire RNA as part of your deployment.Using Dashboards Understanding the Predefined Widgets Chapter 3 For example. you can further constrain the widget using a saved search. either one of the predefined searches delivered with your appliance or a custom search that you created. you can configure the Custom Analysis widget to display which operating systems are running on the hosts in your organization by configuring the widget to display OS data from the RNA Hosts table. Optionally. Microsoft Windows.1 Sourcefire 3D System Administrator Guide 70 . On the other hand. aggregating by Unique OS tells you how many unique versions of each operating system are running on the same hosts (for example. Mac OS X.9. For example. Aggregating this data by Count tells you how many hosts are running each operating system. constraining the first example (operating systems Version 4.

the widget can display one of three icons to indicate any additions or movement from the most recent results: • • The new event icon ( ) signifies that the event is new to the results.Using Dashboards Understanding the Predefined Widgets Chapter 3 aggregated by Count) using the Local Systems search tells you how many hosts within one hop of your 3D Sensors are running each operating system. The widget updates with a frequency that depends on the dashboard time range. For example. The direction icon ( ) indicates and controls the sort order of the display. click the icon. such as one that displays the total number of intrusion events generated in your deployment over Version 4. You can also configure the widget to display the most frequently occurring events or the least frequently occurring events. the widget updates every five minutes. A downward-pointing icon indicates descending order. based on the local time of the appliance. you should read the bars from right to left. You can change the color of the bars as well as the number of rows that the widget displays. hover your pointer over the Last updated notice in the bottom left corner of the widget.9. The colored bars in the widget background show the relative number of occurrences of each event. On the other hand. The down-arrow icon ( ) indicates that the event has moved down in the standings since the last time the widget updated. A number indicating how many places the event has moved up appears next to the icon. the widget updates once a week. if you set the dashboard time range to a year. The up-arrow icon ( ) indicates that the event has moved up in the standings since the last time the widget updated. • The widget displays the last time it updated.1 Sourcefire 3D System Administrator Guide 71 . if you set the dashboard time range to an hour. an upwards-pointing icon indicates ascending order. A number indicating how many places the event has moved down appears next to the icon. you can configure the Custom Analysis widget to display a line graph. To determine when the dashboard will update next. If you want information on events or other collected data over time. Next to each event. To change the sort order.

Finally. workflows) that provide detailed information about the events displayed in the widget. you can choose the time zone that the widget uses as well as the color of the line. Custom Analysis widgets can place a drain on an appliance’s resources. If the widget continues to stay red over time. A different set of preferences appears depending on whether you configure the widget to show relative occurrences of events (that is. show the preferences as described in Understanding Widget Preferences on page 64. For more information. To configure a Custom Analysis widget. a red-shaded Custom Analysis widget indicates that its use is harming system performance. From Custom Analysis widgets. For graphs over time.Using Dashboards Understanding the Predefined Widgets Chapter 3 time. the Custom Analysis widget has preferences that determines its behavior. you should remove the widget. you can invoke event views (that is.1 Sourcefire 3D System Administrator Guide 72 . a line graph). you can choose a custom title for the widget. a bar graph). or you configure the widget to show a graph over time (that is. Version 4. IMPORTANT! Depending on how they are configured.9. see the following sections: • • • Configuring the Custom Analysis Widget on page 72 Viewing Associated Events from the Custom Analysis Widget on page 78 Custom Analysis Widget Limitations on page 79 Configuring the Custom Analysis Widget Requires: Any As with all widgets.

To configure the widget to show a line graph.. The following table describes the various preferences you can set in the Custom Analysis widget. If you do not specify a title.. Title To control.9. For a detailed list of presets. select Time from the Field drop-down list.Using Dashboards Understanding the Predefined Widgets Chapter 3 To configure the widget to show a bar graph. select any value except Time from the Field drop-down list.1 Sourcefire 3D System Administrator Guide 73 . the appliance uses the configured event type as the widget title. the title of the widget.. as shown in the following graphic.. Preset the preset for the widget. see the Custom Analysis Widget Presets table on page 75. Version 4. as shown in the following graphic. You can use these presets or you can create a custom configuration. The Custom Analysis widget is delivered with several presets. which are groups of configurations that are predefined by Sourcefire. Custom Analysis Widget Preferences Use this preference. The presets serve as examples and can provide quick access to information about your deployment.

. Show Movers Time Zone whether you want to display the icons that indicate additions or movement from the most recent results. The aggregation method configures how the widget groups the data it displays.. Show Results whether you want to display the most frequently occurring events (Top) or the least frequently occurring events (Bottom). Color the color of the bars in the widget background that show the relative number of occurrences of each result. TIP! To display a graph over time. although some presets use predefined searches. the table of events which contains the event data the widget displays. which time zone you want to use to display results. if any. Aggregate the aggregation method for the widget. The time zone appears whenever you select a time-based field. the default aggregation criterion is Count. in increments of five. It also indicates which.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Preferences (Continued) Use this preference. The following table describes the available presets for the Custom Analysis widget. You can display from 10 to 25 result rows. For most event types..1 Sourcefire 3D System Administrator Guide 74 . Search the saved search you want to use to further constrain the data that the widget displays. select Time. Defense Center predefined dashboard uses Version 4. Table Field To control. You do not have to specify a search. the number of results rows you want to display. the specific field of the event type you want to display..9.

9. (The predefined dashboards on the Master Defense Center and 3D Sensor do not include Custom Analysis widgets. based on the number of detected flows. based on the number of flows where the host was the responder in the session. Custom Analysis Widget Presets Preset All Intrusion Events Description Displays a graph of the total number of intrusion events on your monitored network over the dashboard time range. by classification. Displays the most active hosts on your monitored network. Displays the most active hosts on your monitored network. Predefined Dashboards Default Dashboard Detailed Dashboard Detailed Dashboard Requires IPS or DC/MDC + IPS All Intrusion Events (Not Dropped) IPS or DC/MDC + IPS Client Applications Detailed Dashboard DC + RNA Dropped Intrusion Events Default Dashboard IPS or DC/MDC + IPS Flows by Initiator IP Flow Summary DC + RNA Flows by Port Flow Summary DC + RNA Flows by Responder IP Flow Summary DC + RNA Flows by Service Flow Summary DC + RNA Version 4. where the packet was not dropped as part of the event. by application type. by classification. based on the number of detected flows. where the packet was dropped. Displays the most active services on your monitored network.1 Sourcefire 3D System Administrator Guide 75 . Displays the most active ports on your monitored network.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. Displays counts for the most frequently occurring intrusion events.) . Displays the most active client applications on your monitored network. Displays the most frequently occurring types of intrusion events. based on the number of flows where the host initiated the session.

Displays the most common RNA service vendors. Displays the most common operating system. based on the number of intrusion events where the host was the targeted host in the flow that caused the event.9. based on event classification. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. based on frequency of intrusion events. Displays the most frequently occurring types of intrusion events.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Flows over Time Description Displays a graph of the total number of flows on your monitored network. Predefined Dashboards Flow Summary Requires DC + RNA Intrusion Events Requiring Analysis Intrusion Events by Hour Intrusion Events to High Criticality Hosts Detailed Dashboard DC/MDC + IPS + RNA IPS or DC/MDC + IPS DC/MDC + IPS + RNA none Detailed Dashboard Operating Systems Detailed Dashboard DC + RNA Services Detailed Dashboard DC + RNA Top Attackers Default Dashboard IPS or DC/MDC + IPS Top Targets Default Dashboard IPS or DC/MDC + IPS Version 4. Displays the most active hours of the day.1 Sourcefire 3D System Administrator Guide 76 . Displays a count of intrusion event requiring analysis. Displays the most active hosts on your monitored network. based on the number of hosts running each operating system within your network. based on the number of intrusion events occurring on high criticality hosts. based on the number of hosts on the network running services made by that vendor. over the dashboard time range. Displays the most active hosts on your monitored network.

based on the number of kilobytes per second of data received by the hosts. based on the number of kilobytes per second of data transmitted by the service. Predefined Dashboards Detailed Dashboard Flow Summary Requires DC + RNA Traffic by Initiator User Detailed Dashboard DC + RNA + RUA Traffic by Port Flow Summary DC + RNA Traffic by Responder IP Detailed Dashboard Flow Summary DC + RNA Traffic by Service Detailed Dashboard Flow Summary DC + RNA Traffic over Time Detailed Dashboard Flow Summary DC + RNA Version 4. Displays the most active responder ports on your monitored network. based on the total number of kilobytes of data received by the hosts where those users are logged in. Displays a graph of the total kilobytes of data transmitted on your monitored network over the dashboard time range. Displays the most active RUA users on your monitored network. Displays the most active hosts on your monitored network. based on the number of kilobytes per second of data transmitted by the hosts. Displays the most active services on your monitored network.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Traffic by Initiator IP Description Displays the most active hosts on your monitored network. based on the number of kilobytes per second of data transmitted via the port.1 Sourcefire 3D System Administrator Guide 77 .9.

depending on how many time windows you have configured and on what type of event you are trying to view. Displays the number of unique intrusion event types associated with each impact flag level.9. a workflow) that provides detailed information about the events displayed in the widget. When you invoke an event view from the dashbaord. if you configure multiple time windows on your Defense Center and then access health events from a Custom Analysis widget. you can invoke an event view (that is. the events appear in the default workflow for that event type. constrained by the dashboard time range. Version 4.Using Dashboards Understanding the Predefined Widgets Chapter 3 Custom Analysis Widget Presets (Continued) Preset Unique Intrusion Events by Destination IP Unique Intrusion Events by Impact White List Violations Description Displays the most active targeted hosts. This also changes the appropriate time window for the appliance. by violation count? Predefined Dashboards none Requires IPS or DC/MDC + IPS none DC/MDC + IPS + RNA DC + RNA Detailed Dashboard Viewing Associated Events from the Custom Analysis Widget Requires: Any Depending on the kind of data that a Custom Analysis widget is configured to display.1 Sourcefire 3D System Administrator Guide 78 . For example. see Default Time Windows on page 29 and Specifying Time Constraints in Searches in the Analyst Guide. if you configure a single time window and then access any type of event from the Custom Analysis widget. As another example. based on the number of unique intrusion events per targeted host. the events appear in the default workflow for that event type. and the global time window changes to the dashboard time range. the events appear in the default health events workflow. For more information on time windows. Displays the hosts with the most white list violations. and the health monitoring time window changes to the dashboard time range.

• For information on working with specific event types. as well as by that event. see the following sections: • • • • • • • • • • • • • • • • • Viewing Audit Records on page 567 Viewing Intrusion Events in the Analyst Guide Viewing RNA Network Discovery and Host Input Events in the Analyst Guide Viewing Hosts in the Analyst Guide Viewing Host Attributes in the Analyst Guide Viewing Services in the Analyst Guide Viewing Client Applications in the Analyst Guide Viewing Vulnerabilities in the Analyst Guide Viewing Flow Data in the Analyst Guide Viewing RUA Users in the Analyst Guide Viewing RUA Events in the Analyst Guide Viewing Compliance Events in the Analyst Guide Viewing White List Events in the Analyst Guide Viewing White List Violations in the Analyst Guide Viewing the SEU Import Log in the Analyst Guide Working with Active Scan Results in the Analyst Guide Understanding Custom Tables in the Analyst Guide Custom Analysis Widget Limitations Requires: Any There are some important points to keep in mind when using the Custom Analysis widget. Similarly.1 Sourcefire 3D System Administrator Guide 79 . If you are configuring the widget on a shared dashboard. constrained by the widget preferences. remember that not all users can view data of all event types. For Version 4.9. remember that not all appliances have access to data of all event types. bar graphs). constrained by the widget preferences. You can also click the View All icon in the lower right corner of the widget to view all associated events. Intrusion Event Analysts cannot view RNA events. depending on how you configured the widget: • On widgets configured to show relative occurrences of events (that is. click the View All icon in the lower right corner of the widget to view all associated events. depending on the user’s account privileges. For example.Using Dashboards Understanding the Predefined Widgets Chapter 3 To view associated events from the Custom Analysis Widget: Access: Any except Restricted You have two options. On widgets configured to show flow data over time. click any event to view associated events constrained by the widget preferences. if you are using a dashboard imported from another appliance.

If you want to make sure that this does not happen. Version 4. save the dashboard as private.Using Dashboards Understanding the Predefined Widgets Chapter 3 example. The widget preferences also control how often the widget updates. however. Note. If your dashboard includes a Custom Analysis widget that displays data that you cannot see. It also shows the capacity of each partition. see Configuring Dashboard Settings on page 331. If you configure the widget on a shared dashboard and constrain its events using a private search. You enable or disable the Custom Analysis widget from the Dashboard settings in your system policy. For more information.9. see Understanding Widget Preferences on page 64. as well as whether it displays the current disk usage or collected disk usage statistics over the dashboard time range. the widget resets to not using the search when another user logs in.1 Sourcefire 3D System Administrator Guide 80 . the widget indicates that you are unauthorized to view the data. If you want to make sure that this does not happen. or even delete the widget. or you can show these plus the /boot partition usage by modifying the widget preferences. save the dashboard as private. Understanding the Disk Usage Widget Requires: Any The Disk Usage widget indicates the percentage of space used on each partition of the appliance’s hard drive. For more information. that you (and any other users who share the dashboard) can modify the preferences of the widget to display data that you can see. the Master Defense Center does not store flow data. You can configure the widget to display just the root (/) and /volume partition usage. This affects your view of the widget as well. Remember that only you can access searches that you have saved as private.

Note that only 3D Sensors have interfaces other than the management interface. you can configure the widget to display intrusion events of different impacts by modifying the widget preferences. On the 3D Sensor.9. this includes statistics on intrusion events of different impacts.1 Sourcefire 3D System Administrator Guide 81 . The widget preferences control how often the widget updates. For more information. all intrusion events. On the 3D Sensor. Understanding the Intrusion Events Widget Requires: IPS or DC/ MDC + IPS The Intrusion Events widget shows the rate of intrusion events that occurred over the dashboard time range. you must enable local event storage or the widget will not have any data to display. On the Defense Center and Master Defense Center. the widget can display statistics for dropped intrusion events. the widget only displays the traffic rate for interfaces that belong to an interface set). see Understanding Widget Preferences on page 64. On the Defense Center and Master Defense Center.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the Interface Traffic Widget Requires: Any The Interface Traffic widget shows the rate of traffic received (Rx) and transmitted (Tx) on the appliance’s interfaces over the dashboard time range. Note that for managed 3D Sensors. On 3D Sensors. you cannot configure the widget to display Version 4. the preferences also control whether the widget displays the traffic rate for unused interfaces (by default. or both.

For more information on intrusion events. see Viewing Intrusion Events in the Analyst Guide. The following graphic shows the Defense Center version of the widget preferences. you can display dropped events. the widget displays a pie chart that shows the Version 4. you can: • • • Requires: DC/MDC click a graph corresponding to a specific impact to view intrusion events of that impact click the graph corresponding to dropped events to view dropped events click the All graph to view all intrusion events Note that the resulting event view is constrained by the dashboard time range. Understanding the Network Compliance Widget Requires: DC The Network Compliance widget summarizes your hosts’ compliance with the compliance white lists you configured (see Using RNA as a Compliance Tool in the Analyst Guide). select All to display an additional graph for all intrusion events. For more information.9. On the Intrusion Events widget.Using Dashboards Understanding the Predefined Widgets Chapter 3 intrusion events by impact. see Using Impact Flags to Evaluate Events in the Analyst Guide select Show to choose Events per second or Total events select Vertical Scale to choose Linear (incremental) or Logarithmic (factor of ten) scale • • The preferences also control how often the widget updates. On either appliance.1 Sourcefire 3D System Administrator Guide 82 . you can: • Requires: DC/MDC select one or more Event Flags check boxes to display separate graphs for events of specific impacts. By default. accessing intrusion events via the dashboard changes the events (or global) time window for the appliance. regardless of impact or rule state. see Understanding Widget Preferences on page 64. In the widget preferences.

or for a specific white list. Version 4. Note that if you choose to display network compliance for all white lists. the widget considers a host to be non-compliant if it is not compliant with any of the white lists on the Defense Center. including white lists that are no longer in active compliance policies. For more information. non-compliant.Using Dashboards Understanding the Predefined Widgets Chapter 3 number of hosts that are compliant.1 Sourcefire 3D System Administrator Guide 83 . You can click the pie chart to view the host violation count. for all compliance white lists that you have created. You can configure the widget to display network compliance either for all white lists. see Viewing White List Violations in the Analyst Guide.9. and that have not been evaluated. To bring these hosts into compliance. by modifying the widget preferences. non-compliant. which lists the hosts that violate at least one white list. The Network Compliance style (the default) displays a pie chart that shows the number of hosts that are compliant. and that have not been evaluated. You can also use the widget preferences to specify which of three different styles you want to use to display network compliance. delete the unused white lists.

Understanding the Product Licensing Widget Requires: DC The Product Licensing widget shows the feature licenses currently installed on the Defense Center. see Understanding Widget Preferences on page 64. The preferences control how often the widget updates. For example.1 Sourcefire 3D System Administrator Guide 84 . one of which is a permanent license and Version 4. You can check the Show Not Evaluated box to hide events which have not been evaluated. The top section of the widget displays all of the feature licenses installed on the Defense Center. The Network Compliance over Time style displays a line graph that shows the number of hosts that are compliant. while the Temporary Licenses section displays only temporary and expired licenses. over the dashboard time range. over the dashboard time range. For more information. including temporary licenses. non-compliant. and that have not yet been evaluated. non-compliant.9. if you have two feature licenses for RNA Hosts. It also indicates the number of items (such as hosts or users) licensed and the number of remaining licensed items allowed. and that have not yet been evaluated.Using Dashboards Understanding the Predefined Widgets Chapter 3 The Network Compliance over Time (%) style displays a stacked area graph showing the relative proportion of hosts that are compliant.

see Managing Your Feature Licenses on page 370. For more information. see Understanding Widget Preferences on page 64. or all the features that you can license.1 Sourcefire 3D System Administrator Guide 85 . see Understanding Widget Preferences on page 64. or install software updates. For more information. The widget also provides you with links to pages where you can update the software. For more information. see Scheduling Tasks on page 425. but not yet installed. Note that the widget displays Unknown as the latest version of the software unless you have configured a scheduled task to download. You can configure the widget to hide the latest versions by modifying the widget preferences. the widget uses scheduled tasks to determine the latest version. you should read the bars from right to left. The bars in the widget background show the percentage of each type of license that is being used. the Defense Center version of the widget provides you with similar links so you can update the software on your managed sensors. the top section of the widget displays an RNA Hosts feature license with 1500 licensed hosts. for that software. by modifying the widget preferences. Understanding the Product Updates Widget Requires: Any The Product Updates widget provides you with a summary of the software (Sourcefire 3D System software. The preferences also control how often the widget updates. Expired licenses are marked with a strikethrough. You can configure the widget to display either the features that are currently licensed. For more information.Using Dashboards Understanding the Predefined Widgets Chapter 3 allows 750 hosts. Version 4. and another that is temporary and allows an additional 750 hosts.9. and VDB) currently installed on the appliance as well as information on available updates that you have downloaded. while the Temporary Licenses section displays an RNA Hosts feature license with 750 hosts. push. The preferences also control how often the widget updates. Note that you cannot update the VDB on a sensor or a Master Defense Center. SEU. You can click any of the license types to go to the License page of the System Settings and add or delete feature licenses.

or VDB by clicking either the latest version or the Unknown link in the Latest column. When you configure the widget. the widget shows a feed of Sourcefire company news. SEU. keep in mind that not all RSS feeds use descriptions.9. see Updating System Software on page 398 and Importing SEUs and Rule Files in the Analyst Guide create a scheduled task to download the latest version of the Sourcefire 3D System software. see Scheduling Tasks on page 425 • Understanding the RSS Feed Widget Requires: Any The RSS Feed widget adds an RSS feed to a dashboard.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the Product Updates widget.1 Sourcefire 3D System Administrator Guide 86 . SEU. or you can create a custom connection to any other RSS feed by specifying its URL in the widget preferences. as well as whether you want to show descriptions of the stories along with the headlines. Version 4. you can also choose how many stories from the feed you want to show in the widget. You can also configure the widget to display a preconfigured feed of Sourcefire security news. Feeds update every 24 hours (although you can manually update the feed) and the widget displays the last time the feed was updated based on the local time of the appliance. you can: • manually update an appliance by clicking the current version of the Sourcefire 3D System software. By default. Keep in mind that the appliance must have access to the Sourcefire web site (for the two preconfigured feeds) or to any custom feed you configure. or VDB.

see Understanding Widget Preferences on page 64. Understanding the System Time Widget Requires: Any The System Time widget shows the local system time. The preferences also control how often the widget updates. For more information. The preferences also control how often the widget synchronizes with the appliance’s clock. you can: • • • click one of the stories in the feed to view the story click the more link to go to the feed’s web site click the update icon ( ) to manually update the feed Understanding the System Load Widget Requires: Any The System Load widget shows the CPU usage (for each CPU).Using Dashboards Understanding the Predefined Widgets Chapter 3 On the RSS Feed widget. memory (RAM) usage. uptime. Version 4. see Understanding Widget Preferences on page 64. measured by the number of processes waiting to execute) on the appliance. both currently and over the dashboard time range.1 Sourcefire 3D System Administrator Guide 87 . You can configure the widget to show or hide the load average by modifying the widget preferences.9. and system load (also called the load average. and boot time for the appliance. For more information. You can configure the widget to hide the boot time by modifying the widget preferences.

see Understanding Widget Preferences on page 64. For more information.9. You can configure the widget to display white list events of different priorities by modifying the widget preferences. you can: • • • select one or more Priorities check boxes to display separate graphs for events of specific priorities. the events are constrained by the dashboard time range. see Viewing White List Events in the Analyst Guide.1 Sourcefire 3D System Administrator Guide 88 . In the widget preferences. over the dashboard time range. Version 4. regardless of priority select Vertical Scale to choose Linear (incremental) or Logarithmic (factor of ten) scale The preferences also control how often the widget updates. or click the All graph to view all white list events. In either case. For more information on white list events. You can click a graph to view white list events of a specific priority.Using Dashboards Understanding the Predefined Widgets Chapter 3 Understanding the White List Events Widget Requires: DC/MDC The White List Events widget shows the average events per second by priority. accessing white list events via the dashboard changes the events (or global) time window for the Defense Center. including events that do not have a priority select Show All to display an additional graph for all white list events.

1 Sourcefire 3D System Administrator Guide 89 . view. for example. you can make the changes at a local computer. Optionally.Using Dashboards Working with Dashboards Chapter 3 Working with Dashboards Requires: Any You manage dashboards on the Dashboard List page (see Viewing Dashboards on page 91).9. Note that you do not need to refresh the entire dashboard to see data updates. the user who created it) and whether a dashboard is private. you can create a blank new dashboard by choosing not to base your dashboard on any pre-existing dashboards. or on any user-defined dashboard. unless you have Admin access. modify. You can create. Refreshing the entire dashboard allows you to see any preference or layout changes that were made to a shared dashboard by another user. in a network operations center (NOC) where a dashboard is displayed at all times. These settings determine how often the dashboard cycles through its tabs and how often the entire dashboard page refreshes. the dashboard in the NOC automatically refreshes at the interval you specify and displays your changes without you having to manually refresh the dashboard in the NOC. for more information. the page indicates the owner (that is. For each dashboard. individual widgets update according to their preferences. If you want to make changes to the dashboard. For more information on working with dashboards. and delete dashboards. Note that. export. This can be useful. you can modify this copy to suit your needs. Then. including the Sourcefire default dashboard. see Specifying Your Default Dashboard on page 35. the page indicates which dashboard is the default. you can only see your own private dashboards. You specify the default dashboard in your user preferences. Finally. or that you made to a private dashboard on another computer. you cannot view or modify private dashboards created by other users. since the last time the dashboard refreshed. This makes a copy of the pre-existing dashboard. you can choose to base it on any pre-existing dashboard. Version 4. You must also specify (or disable) the tab change and page refresh intervals. see: • • • • • Creating a Custom Dashboard on page 89 Viewing Dashboards on page 91 Modifying Dashboards on page 93 Deleting a Dashboard on page 97 Exporting a Dashboard on page 585 Creating a Custom Dashboard Requires: Any When you create a new dashboard.

you can choose to associate the new dashboard with your user account by saving it as a private dashboard. save it as private. You can then edit the imported dashboard to suit your needs.1 Sourcefire 3D System Administrator Guide 90 . disabled widgets. Keep in mind that because not all user roles have access to all dashboard widgets. You should also keep in mind that any user. it appears. If you do not have a default dashboard defined. Note that the dashboard widgets you can view depend on the type of appliance you are using and on your user role. 2.Using Dashboards Working with Dashboards Chapter 3 Finally. select None (the default) to create a blank dashboard. The New Dashboard page appears. see Importing and Exporting Objects on page 583. In either case. all other users of the appliance can view it. Type a name and optional description for the dashboard. users with fewer permissions viewing a dashboard created by a user with more permissions may not be able to use all of the widgets on the dashboard. Optionally. you can export a dashboard from another appliance and then import it onto your appliance. Select Analysis & Reporting > Event Summary > Dashboards. a dashboard created on the Defense Center and imported onto a 3D Sensor or Master Defense Center may display some invalid. regardless of role. Use the Copy Dashboard drop-down list to select the dashboard on which you want to base the new dashboard. for example. 4. If you choose not to save the dashboard as private.9. 3. they are disabled. If you have a default dashboard defined. Version 4. If you want to make sure that only you can modify a particular dashboard. click New Dashboard. the Dashboard List page appears. Although the unauthorized widgets still appear on the dashboard. You can select any predefined or user-defined dashboard. TIP! Instead of creating a new dashboard. For more information. can modify shared dashboards. To create a new dashboard: Access: Any except Restricted 1.

including pages that are not dashboard pages. You can also change the default dashboard. although refreshing the dashboard page resets the update interval on individual widgets. the home page shows the Dashboard List page. this setting advances your view to the next tab at the interval you specify. Click Save. Unless you pause the dashboard or your dashboard has only one tab. Your dashboard is created and appears in the web interface. This value must be greater than the Change Tabs Every setting. Each dashboard has a time range that constrains its widgets. see Modifying Dashboards on page 93. TIP! You can configure your appliance to display a different default home page. In the Refresh Page Every field. widgets will update according to their individual preferences even if you disable the Refresh Page Every setting. For more information. You can now tailor it to suit your needs by adding tabs and widgets (and. To disable the periodic page refresh.9. 6. by rearranging and deleting widgets). this setting will refresh the entire dashboard at the interval you specify. Viewing Dashboards Requires: Any By default. the widgets that can be constrained by time automatically update to reflect the new time range. enter 0 in the Refresh Page Every field. Note that not all widgets can be constrained by time. Unless you pause the dashboard.1 Sourcefire 3D System Administrator Guide 91 . select the Save As Private check box to associate the dashboard with your user account and to prevent other users from viewing and modifying the dashboard. 7. For example. if you based it on a pre-existing dashboard. where you can choose a dashboard to view. the dashboard time range has no effect on the Appliance Information widget. which provides Version 4. For more information. specify (in minutes) how often the current dashboard tab should refresh with new data. Optionally. see Specifying Your Home Page on page 35 and Specifying Your Default Dashboard on page 35. 8.Using Dashboards Working with Dashboards Chapter 3 5. To disable tab cycling. Note that this setting is separate from the update interval available on many individual widgets. enter 0 in the Change Tabs Every field. When you change the time range. To view the details of all available dashboards. You can change the time range to reflect a period as short as the last hour (the default) or as long as the last year. the home page for your appliance displays the default dashboard. In the Change Tabs Every field. If you do not have a default dashboard defined. click Dashboards from the Dashboard toolbar. specify (in minutes) how often the dashboard should change tabs.

Version 4. dashboard tabs resume cycling and the dashboard page resumes refreshing according to the settings you specified in the dashboard properties. all appropriate widgets on the page update to reflect the new time range. The dashboard you selected appears. depending on how often newer events replace older events.9.Using Dashboards Working with Dashboards Chapter 3 information the includes the appliance name.5 hours of inactivity. changing the time range to a long period may not be useful for widgets like the Custom Analysis widget. Unless the dashboard is paused. you can unpause the dashboard. regardless of the Cycle Tabs Every setting in the dashboard properties.1 Sourcefire 3D System Administrator Guide 92 . Dashboard pages stop refreshing. which allows you to examine the data provided by the widgets without the display changing and interrupting your analysis. To view a different dashboard. Unpausing the dashboard causes all the appropriate widgets on the page to update to reflect the current time range. Dashboard tabs stop cycling. the Dashboard List page appears. To view a dashboard: Access: Any except Restricted Select Analysis & Reporting > Event Summary > Dashboards. regardless of any Update Every widget preference. You have two options. this will not happen while you are viewing a dashboard. regardless of the Refresh Page Every setting in the dashboard properties. choose a dashboard time range. When you are finished with your analysis. depending on whether you have a default dashboard defined: • • If you have a default dashboard defined. use the Dashboards menu on the toolbar. Pausing a dashboard has the following effects: • • • • Individual widgets stop updating. If you do not have a default dashboard defined. and current version of the Sourcefire 3D System software. Changing the time range has no effect. IMPORTANT! Although your session normally logs you out after 3. In addition. unless the dashboard is paused. To change the dashboard time range: Access: Any except Restricted From the Show the Last drop-down list. it appears. Click View next to the dashboard you want to view. You can also pause a dashboard. Keep in mind that for enterprise deployments of the Sourcefire 3D System. model.

which include its name and description.1 Sourcefire 3D System Administrator Guide 93 . make sure to set it as a private dashboard in the dashboard properties. If you want to make sure that only you can modify a particular dashboard. regardless of role. Each tab can display one or more widgets in a three-column layout. the tab cycle and page refresh intervals. Version 4. and whether you want to share the dashboard with other users. Modifying Dashboards Requires: Any Each dashboard has one or more tabs. To unpause the dashboard: Access: Any except Restricted On the time range control of a paused dashboard. You can also change the basic dashboard properties. Note that you cannot change the order of dashboard tabs. delete.9. IMPORTANT! Any user. add and remove widgets from tabs. ). You can add. For more information. see the following sections • • • • • • • • Changing Dashboard Properties on page 93 Adding Tabs on page 94 Deleting Tabs on page 95 Renaming Tabs on page 95 Adding Widgets on page 95 Rearranging Widgets on page 97 Minimizing and Maximizing Widgets on page 97 Deleting Widgets on page 97 Changing Dashboard Properties Requires: Any Use the following procedure to change the basic dashboard properties. click the pause icon ( The dashboard is paused until you unpause it. and rename tabs.Using Dashboards Working with Dashboards Chapter 3 To pause the dashboard: Access: Any except Restricted On the time range control. You can minimize and maximize widgets. which include its name and description. as well as rearrange the widgets on a tab. click the play icon ( The dashboard is unpaused. can modify shared dashboards. and whether you want to share the dashboard with other users. the tab cycle and page refresh intervals. ).

prompting you to name the tab. Version 4. For more information. If you do not have a default dashboard defined.1 Sourcefire 3D System Administrator Guide 94 . 4. 2. or simply click OK to accept the default name.Using Dashboards Working with Dashboards Chapter 3 To change a dashboard’s properties: Access: Any except Restricted 1. click Dashboards. see Viewing Dashboards on page 91. The Dashboard List page appears. The dashboard is changed. Adding Tabs Requires: Any Use the following procedure to add a tab to a dashboard. skip to step 3. You can now add widgets to the new tab. Note that you can rename the tab at any time. To the right of the existing tabs. View the dashboard where you want to add a tab.9. Make changes as needed and click Save. Type a name for the tab and click OK. If you have a default dashboard defined. To add a tab to a dashboard: Access: Any except Restricted 1. A pop-up window appears. The Edit Dashboard page appears. For more information. 3. click the add tab icon ( ). See Creating a Custom Dashboard on page 89 for information on the various configurations you can change. 2. On the toolbar. Select Analysis & Reporting > Event Summary > Dashboards. 3. Click Edit next to the dashboard whose properties you want to change. continue with the next step. see Renaming Tabs on page 95. it appears. the Dashboard List page appears. The new tab is added. see Adding Widgets on page 95.

see Viewing Dashboards on page 91. If all columns have an equal number of widgets. You cannot delete the last tab from a dashboard. View the dashboard where you want to delete a tab. the new widget is added to the left-most column. click the delete icon ( 3. You can add a maximum of 15 widgets to a dashboard tab. 3. When you add a widget to a tab. each dashboard must have at least one tab. A pop-up window appears. 4. see Viewing Dashboards on page 91.Using Dashboards Working with Dashboards Chapter 3 Deleting Tabs Requires: Any Use the following procedure to delete a dashboard tab and all its widgets. For more information. 2. For more information. TIP! After you add widgets. ).1 Sourcefire 3D System Administrator Guide 95 . Click the tab you want to rename. Type a name for the tab and click OK. Confirm that you want to delete the tab. For more information. prompting you to rename the tab. To add a widget to a dashboard: Access: Any except Restricted 1. see Rearranging Widgets on page 97. To rename a tab: Access: Any except Restricted 1. you can move them to any location on the tab. The tab is deleted. For more information.9. Version 4. Renaming Tabs Requires: Any Use the following procedure to rename a dashboard tab. The tab is renamed. move widgets from tab to tab. 2. you must first decide to which tab you want to add the widget. however. the appliance automatically adds it to the column with the fewest widgets. View the dashboard where you want to add a widget. You cannot. Adding Widgets Requires: Any To add a widget to a dashboard. To delete a tab from a dashboard: Access: Any except Restricted 1. On the tab you want to delete. Click the tab title. see Viewing Dashboards on page 91. View the dashboard where you want to rename a tab.

or you can view all widgets by clicking All Categories. The Add Widgets page indicates how many widgets of each type are on the tab. including the widget you just added. The Add Widgets page appears. you may want to add multiple RSS Feed widgets. The widget is immediately added to the dashboard. The tab where you added the widgets appears again. TIP! To add multiple widgets of the same type (for example. They are organized according to function: Analysis & Reporting. Click Add next to the widgets you want to add. click Add again.Using Dashboards Working with Dashboards Chapter 3 2. and Miscellaneous. Optionally. You can view the widgets in each category by clicking on the category name. 5. reflecting the changes you made. 3. Operations. Select the tab where you want to add the widget. 4.9. when you are finished adding widgets. click Done to return to the dashboard. Click Add Widgets. or multiple Custom Analysis widgets).1 Sourcefire 3D System Administrator Guide 96 . Version 4. The widgets that you can add depend on the type of appliance you are using and on your user role.

however. Confirm that you want to delete the widget. Deleting Widgets Delete a widget if you no longer want to view it on a tab. continue with the next step. the Dashboard List page appears. Select Analysis & Reporting > Event Summary > Dashboards. If you do not have a default dashboard defined. then drag it to its new location. you must define a new default or the appliance will force you to select a dashboard to view every time you attempt to view a dashboard. Note. The widget is deleted from the tab. If you delete your default dashboard. 2. To delete a dashboard: Access: Any except Restricted 1.9. For more information. that you cannot move widgets from tab to tab. it appears. Version 4. To move a widget: Access: Any except Restricted Click the title bar of the widget you want to move. see Specifying Your Default Dashboard on page 35. Deleting a Dashboard Requires: Any Delete a dashboard if you no longer need to use it.Using Dashboards Working with Dashboards Chapter 3 Rearranging Widgets Requires: Any You can change the location of any widget on a tab. To delete a widget: Access: Any except Restricted 1.1 Sourcefire 3D System Administrator Guide 97 . Click the close icon ( ) in the title bar of the widget. skip to step 3. If you have a default dashboard defined. Minimizing and Maximizing Widgets Requires: Any You can minimize widgets to simplify your view. If you want a widget to appear on a different tab. then maximize them when you want to see them again. ) in a widget’s title bar. To minimize a widget: Access: Any except Restricted Access: Any except Restricted Requires: Any Click the minimize icon ( To maximize a widget: Click the maximize icon ( ) in a minimized widget’s title bar. you must delete it from the existing tab and add it to the new tab.

1 Sourcefire 3D System Administrator Guide 98 . On the toolbar. The dashboard is deleted. The Dashboard List page appears. click Dashboards. Version 4. Confirm that you want to delete the dashboard. 3. 4.9.Using Dashboards Working with Dashboards Chapter 3 2. Click Delete next to the dashboard you want to delete.

and respond to the threats they detect on your network. You must use a Defense Center if your deployment includes any of these products. Version 4. The Defense Center aggregates and correlates intrusion events. In addition. By using the Defense Center to manage sensors.Using the Defense Center Chapter 4 Administrator Guide The Sourcefire Defense Center is a key component in the Sourcefire 3D System. 3Dx800 sensors. network discovery information. and Crossbeam-based software sensors) do not provide a web interface that you can use to view events or manage policies. You can also push health policies to your managed sensors and monitor their health status from the Defense Center. making it easier to change configurations.9. and to aggregate. and sensor performance data. analyze. you can configure policies for all your sensors from a single location.1 Sourcefire 3D System Administrator Guide 99 . Intrusion Agents. allowing you to monitor the information that your sensors are reporting in relation to one another and to assess the overall activity occurring on your network. RNA Software for Red Hat Linux. You can use the Defense Center to manage the full range of sensors that are a part of the Sourcefire 3D System. IMPORTANT! Some of the components in the Sourcefire 3D System (such as the Virtual 3D Sensors. you can push various types of software updates to sensors.

Managing a Clustered Pair on page 140 describes how to create a clustered pair of 3D9900s and how to remove 3D9900s from clusters. You can only use a single Defense Center to manage your sensor unless you are using a second Defense Center as a part of a high availability pair. This saves you from having Version 4. Working with Sensors on page 113 describes how to establish and disable connections between sensors and your Defense Center. delete.9. and change the state of managed sensors and how to reset management of a sensor. Editing a Managed Sensor’s System Settings on page 133 describes the sensor attributes you can edit and explains how to edit them. • • • • • Management Concepts Requires: DC You can use a Defense Center to manage nearly every aspect of a sensor’s behavior. Working in NAT Environments on page 112 describes the principles of setting up the management of your sensors in Network Address Translation environments. First.1 Sourcefire 3D System Administrator Guide 100 . It also explains how to add.Using the Defense Center Management Concepts Chapter 4 See the following sections for more information about using the Defense Center to manage your sensors: • • Management Concepts on page 100 describes some of the features and limitations involved with managing your sensors with a Defense Center. For example. Configuring High Availability on page 145 describes how to set up two Defense Centers as a high availability pair to help ensure continuity of operations. you can create an intrusion policy on the Defense Center and apply it to all your managed 3D Sensors with IPS. you can use the Defense Center’s web interface to accomplish nearly any task on any sensor it manages. Managing Sensor Groups on page 131 describes how to create sensor groups as well as how to add and remove sensors from groups. you can use the Defense Center as a central point of management. • • • • • The Benefits of Managing Your Sensors on page 100 What Can Be Managed by a Defense Center? on page 101 Understanding Software Sensors on page 105 Beyond Policies and Events on page 111 Using Redundant Defense Centers on page 112 The Benefits of Managing Your Sensors Requires: DC There are several benefits to using a Defense Center to manage your sensors. Instead of managing each sensor using its own local web interface. The sections that follow explain some of the concepts you need to know as you plan your Sourcefire 3D System deployment.

You can also generate reports based on events from multiple sensors. Second. Fourth. What Can Be Managed by a Defense Center? Requires: DC You can use your Defense Center as a central management point in a Sourcefire 3D System deployment to manage the following devices: • • Sourcefire 3D Sensors RNA Software for Red Hat Linux Version 4.9. all the intrusion events and RNA events are automatically sent to the Defense Center. The Defense Center can then assign impact flags to each intrusion event. so you must use the Defense Center to manage it. when you manage a sensor with a Defense Center. There is a similar savings when you create and apply RNA appliance and detection policies to managed 3D Sensors with RNA. You can also create and apply system policies to your managed sensors. By pushing a system policy with configured authentication objects to your sensor. Finally. Third. You can also apply a health policy to the Defense Center to monitor its health. Because most of the sensors in your deployment are likely to have similar settings in the system policy. which can be a laborious task depending on how many of the thousands of intrusion rules you want to enable or disable. if your Defense Center manages sensors with IPS and RNA. The impact flag indicates how likely it is that an intrusion attempt will affect its target. A system policy controls several appliance-level settings such as the login banner and the access control list. External authentication cannot be managed on the sensor.1 Sourcefire 3D System Administrator Guide 101 .Using the Defense Center Management Concepts Chapter 4 to replicate the intrusion policy on each sensor. You can take advantage of health monitoring by applying health policies to each of your managed sensors and then reviewing the health data that they send back to the Defense Center. you can use your Defense Center to configure external authentication through an Lightweight Directory Access Protocol (LDAP) or Remote Authentication Dial In User Service (RADIUS) server. you push the external authentication object to the sensor. you can create the policy on the Defense Center and push it to the appropriate sensors instead of replicating it locally. You can view the events from a single web interface instead of having to log into each sensor’s interface to view the events there. then the Defense Center can correlate the intrusion events it receives with the information about hosts that RNA provides. and those sensors view the same network traffic. You can use user information from an external server to authenticate users on your Sourcefire 3D System appliances. the Defense Center includes a feature called health monitoring that you can use to check the status of critical functionality across your Sourcefire 3D System deployment.

information is transmitted between the Defense Center and the sensor over a secure. If you apply a policy on a sensor before you begin managing it with a Defense Center.1 Sourcefire 3D System Administrator Guide 102 . Note that the types of events and policies that are sent between the appliances are based on the sensor type. When you manage a sensor (or a software sensor).Using the Defense Center Management Concepts Chapter 4 • • 3D Sensor Software for Crossbeam Systems X-Series Intrusion Agents on various platforms IMPORTANT! Sourcefire recommends that you manage no more than three 3D Sensors with the DC500 model Defense Center. For details on DC500 database limitations see Database Event Limits on page 333. you can see a read-only version of the policy on the Defense Center’s web interface. The following illustration lists what is transmitted between a Sourcefire Defense Center and its managed sensors. SSL-encrypted TCP tunnel. as well as intrusion agents and RNA software on approved platforms.9. You can also use a DC500 to manage Sourcefire 3D Sensor software on approved platforms. Version 4.

The following graphics illustrate this process.Using the Defense Center Management Concepts Chapter 4 Similarly. after you set up communications with a Defense Center and apply policies from the Defense Center to your sensor. First. each appliance has its own policies: Version 4.9. before you set up sensor management. you can see a read-only version of the running policies on the sensor’s web interface.1 Sourcefire 3D System Administrator Guide 103 .

example.1 Sourcefire 3D System Administrator Guide 104 . after communications are set up. If you want to edit a policy. read-only versions of running policies (represented by the dotted lines) are available: The appliance where you originally create a policy is the policy’s “owner” and is identified that way if you view the policy on a different appliance. For example. Version 4. Sourcefire recommends that you use only the Defense Center’s web interface to view events and manage policies for your managed sensors. TIP! After you set up management with a Defense Center. The Sample Intrusion Policy that is currently applied to the sensor’s two detection engines was created on the Defense Center (pine.Using the Defense Center Management Concepts Chapter 4 Then. the following graphic shows the Detection Engine page on a 3D Sensor with IPS. you must do it on the appliance where the policy was created.com).9.

see Managing 3D Sensor Software with IPS for Crossbeam on page 110 • Version 4. if you delete an intrusion event from the Defense Center. 3D3800.1 Sourcefire 3D System Administrator Guide 105 . RNA Software for Red Hat Linux . and 3D9800 sensors .for more information. see Managing 3Dx800 Sensors on page 107. see Managing Intrusion Agents on page 106 3D5800. Understanding Software Sensors Requires: DC Several of the sensors you can manage with a Defense Center are softwarebased sensors. they are automatically shared with managed 3D Sensors with RNA. Similarly.for more information. see Managing RNA Software for Red Hat Linux on page 109 3D Sensor Software with RNA for Crossbeam X-Series .for more information. see Managing 3D Sensor Software with RNA for Crossbeam on page 110 3D Sensor Software with IPS for Crossbeam X-Series . A software-based sensor is a software-only installation of Sourcefire 3D System sensor software. the event remains on the sensor that discovered it. Also note that operations you perform on data on one appliance are not transmitted to other appliances.Using the Defense Center Management Concepts Chapter 4 The following user-created data and configurations are retained locally on the sensor and are not shared with the Defense Center: • • • • • • • • • • • user accounts user preferences bookmarks saved searches custom workflows report profiles audit events syslog messages reviewed status for intrusion events (IPS only) contents of the clipboard (IPS only) incidents (IPS only) If you create custom fingerprints on the Defense Center.9. For example.for more information. deleting an intrusion event from a sensor does not delete it from the Defense Center.for more information. The following Sourcefire 3D System sensors are software-based: • • • • Intrusion Agents for various platforms .

Managing Intrusion Agents Requires: DC The Sourcefire Intrusion Agent transmits events generated by open source Snort sensor installations to the Sourcefire Defense Center. You must tune your Snort rules and options manually on the computer where the Intrusion Agent resides. In addition. Also. register all Intrusion Agents to the primary Defense Center. For some software-based sensors.Using the Defense Center Management Concepts Chapter 4 Software-based sensors do not have a user interface on the sensor. Version 4. These events can then be viewed along with data from 3D Sensors with IPS so you can easily analyze all the intrusion information gathered on your network. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. they can only be managed from a Defense Center.9. The Defense Center cannot apply intrusion policies to the Intrusion Agent.1 Sourcefire 3D System Administrator Guide 106 . high availability is not supported on Intrusion Agents. some of the functionality in the Defense Center interface cannot be used with software-based sensors. certain aspects of functionality are managed through the operating system or other features on the appliance.

Using the Defense Center Management Concepts Chapter 4 See the Supported Features for Intrusion Agents table for more information.conf files • Process management • Registration of remote manager • Rules tuning Not Supported • Detection engine management • Event storage on sensor • Health policy apply • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply • Network interface management • Network settings • Performance Statistics • Remote backup and restore • Remote reports • Sensor information management (System Settings) • SEU updates • Software updates • System policy apply • Time settings Managing 3Dx800 Sensors Requires: DC + 3D Sensor Sourcefire 3D Sensor 3800. because these models do not have a web interface and because configuration and event data cannot be stored on the sensors. However. Version 4.1 Sourcefire 3D System Administrator Guide 107 .9. and 3D Sensor 9800 models (usually referred to as the 3Dx800 sensors) provide many of the features found on other 3D Sensors. 3D Sensor 5800. Supported Features for Intrusion Agents Supported through Defense Center • Intrusion event collection and management • Licensing • Reports generated on the Defense Center Supported through CLI and .

Using the Defense Center Management Concepts Chapter 4 certain features cannot be used with these sensors. Supported Features for 3Dx800 Sensors Supported through Defense Center All 3Dx800 models: • Detection engine management • Health policy apply • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply (no OPSEC support) • Intrusion event collection and management • Licensing • Performance Statistics (may be underreported because of multiple detection resources) • Process management • Reports generated on the Defense Center • Sensor information management (System Settings) • SEU updates • Software updates • System policy apply • Time settings 3D3800 and 3D5800 only: • Compliance policy apply • RNA and compliance event collection and management • RNA detection policy apply • VDB updates Supported through CLI • Network interface management • Network settings • Registration of remote manager Not Supported • Custom fingerprinting • Event storage on sensor • Remote backup and restore • Remote reports Version 4. See the Supported Features for 3Dx800 Sensors table for more information.1 Sourcefire 3D System Administrator Guide 108 .9.

However.1 Sourcefire 3D System Administrator Guide 109 . See the Supported Features for RNA Software for Red Hat Linux table for more information. not all of the features function in the same manner.9.Using the Defense Center Management Concepts Chapter 4 Managing RNA Software for Red Hat Linux Requires: DC RNA Software for Red Hat Linux provides many of the features found on 3D Sensors with RNA. Supported Features for RNA Software for Red Hat Linux Supported through Defense Center • Compliance policy apply • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Licensing • Performance Statistics • Reports generated on the Defense Center • RNA and compliance event collection and management • RNA detection policy apply • Sensor information management (System Settings) • Software updates • VDB updates Supported through CLI • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Version 4.

not all of the features function in the same manner.1 Sourcefire 3D System Administrator Guide 110 . because the Crossbeam sensors do not have a user interface and because configuration and event data cannot be stored on Version 4. However. However. Supported Features for RNA on Crossbeam Supported through Defense Center Supported through Crossbeam X-Series CLI • Backup and restore • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Compliance policy apply • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Licensing • Performance Statistics • Reports generated on the Defense Center • RNA detection policy apply • RNA and compliance event collection and management • Sensor information management (in System Settings) • Software updates • VDB updates • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Managing 3D Sensor Software with IPS for Crossbeam Requires: DC 3D Sensor Software with IPS for Crossbeam provides many of the features found on 3D Sensors with IPS.9.Using the Defense Center Management Concepts Chapter 4 Managing 3D Sensor Software with RNA for Crossbeam Requires: DC 3D Sensor Software with RNA for Crossbeam provides many of the features found on 3D Sensors with RNA. See the Supported Features for RNA on Crossbeam table for more information.

Using the Defense Center Management Concepts Chapter 4 the sensors. This is particularly useful if you want to generate a report for the audit events on a managed sensor. Backing Up a Sensor If you are storing event data on your sensor in addition to sending it to the Defense Center.9.1 Sourcefire 3D System Administrator Guide 111 . Running Remote Reports You can create a report profile on the Defense Center and run it remotely using the data on a managed sensor. Audit events are stored locally Version 4. you can also perform other sensor-related tasks on the Defense Center. Supported Features for IPS on Crossbeam Supported through Defense Center Supported through Crossbeam X-Series CLI • Backup and restore • Network interface management • Network settings • Process management • Registration of remote manager • Time settings Not Supported • Detection engine management • High availability synchronization • Host Statistics • Interface set management • Intrusion policy apply • Intrusion event collection and management • Licensing • Performance Statistics • Reports generated on the Defense Center • SEU updates • Sensor information management (in System Settings) • Software updates • Custom fingerprinting • Event storage on sensor • Health policy apply • Remote backup and restore • Remote reports • System policy apply Beyond Policies and Events Requires: DC In addition to applying policies to sensors and receiving events from them. See Performing Sensor Backup with the Defense Center on page 419 for more information. See the Supported Features for IPS on Crossbeam table for more information. you can use the Defense Center’s web interface to back up those events from the sensor. certain features cannot be used with this software.

For the registration key. and more are shared between the two Defense Centers. Sourcefire releases updates to the Sourcefire 3D System. but you can design a report on the Defense Center. See Working with Event Reports on page 232 for more information. select a managed sensor. the two required pieces of common information during registration are the registration key and the unique NAT ID.9. use the Defense Center’s fully qualified domain name maple. the two required pieces of common information during registration are the registration key and the unique IP address or the fully qualified domain name of the host. Typical applications using NAT enable multiple hosts on a private network to use a single public IP address to access the public network. See Configuring High Availability on page 145 or more information. Using Redundant Defense Centers Requires: DC You can set up two Defense Centers as a high availability pair. In the example diagram. When you add an appliance. If you establish that communication in an environment with NAT. Policies.com as its host name.Using the Defense Center Working in NAT Environments Chapter 4 and are not sent to the Defense Center.1 Sourcefire 3D System Administrator Guide 112 . user accounts. including: • Security Enhancement Updates (SEUs). If you set up the report so that it is automatically emailed to you. Working in NAT Environments Requires: Any Network address translation (NAT) is a method of transmitting and receiving network traffic through a router that involves reassigning the source or destination IP address as the traffic passes through the router. when you set up the remote office 3D Sensors connections to the home office. Updating Sensors From time to time. Events are automatically sent to both Defense Centers. because the registration key does not have to Version 4. which can contain new and updated intrusion rules. This ensures redundant functionality in case one of the Defense Centers fails. and run the report.company. If you establish that communication in an environment without NAT. as well as new and updated preprocessors and protocol decoders vulnerability database updates software patches and updates • • You can use the Defense Center to push an update to the sensors it manages and then automatically install the update. you can use snort when adding either sensor. you do not even need a user account on the sensor to read the resulting report. you establish connections between appliances and register the appliances with one another.

However. you set up a two-way. you must use a unique NAT ID when adding the New York 3D Sensor to the Defense Center. it generates events and sends them to the Defense Center using the same channel. Each NAT ID has to be unique among all NAT IDs used to register sensors on the Defense Center.Using the Defense Center Working with Sensors Chapter 4 be unique. SSL-encrypted communication channel between the Defense Center and the sensor. and then use a different unique NAT ID when adding the Miami 3D Sensor. The Defense Center uses this channel to send information (in the form of policies) to the sensor about how you want to analyze your network traffic. You can create the following policies on your Defense Center and apply them to managed sensors: • • • health policies system policies RUA policies Version 4.1 Sourcefire 3D System Administrator Guide 113 . As the sensor evaluates the traffic. Working with Sensors Requires: DC + 3D Sensor When you manage a sensor.9.

which controls the networks that 3D Sensors with RNA monitor. Note that the system policy applied to the Defense Center controls the types of RNA events that are logged to the database. (Deleting Sensors on page 121 explains how to remove a sensor from the Defense Center. Refer to the configuration guides for those products for more information.1 Sourcefire 3D System Administrator Guide 114 . See Adding Sensors to the Defense Center on page 117 for more information. RNA Software for Red Hat Linux. See What is an RNA Detection Policy? in the Analyst Guide for more information. See Viewing Intrusion Event Statistics in the Analyst Guide and Viewing RNA Event Statistics in the Analyst Guide for more information. Begin by setting up a communications channel between the two appliances. and the Intrusion Agents are slightly different. Many sensor management tasks are performed on the Sensors page and are described in Understanding the Sensors Page on page 115. Confirm that you are receiving the events generated by your sensors. See Configuring Health Policies on page 489 for more information.9. You can also create and apply system policies. This is a two-step process. Version 4. • • • 3. RNA detection engines require an RNA detection policy. TIP! The process for setting up communications between the Defense Center and other products such as the Crossbeam-based software sensors.Using the Defense Center Working with Sensors Chapter 4 • • RNA detection policies intrusion policies There are several steps to managing a sensor with a Defense Center: The procedure for managing a 3Dx800 sensor differs from the procedure for managing other sensors. See Managing System Policies on page 320 for more information. See Using Intrusion Policies in the Analyst Guide for more information. See Managing a 3Dx800 Sensor on page 125 for more information. which control certain appliance-level features on your sensors. • IPS detection engines require an intrusion policy that determines which types of attacks 3D Sensor with IPS detect. Create the appropriate policies on the Defense Center and apply them to the sensor or to the appropriate detection engines on the sensor. 1. You can create and apply health policies that allow you to monitor the processes and status of your sensors.) 2. with procedures that you need to perform on each side of the communications channel.

see Managing Sensor Groups on page 131) Model (that is. Health Policy The next column lists the health policy for the sensor. Sort-by Drop-Down List Use this drop-down list to sort the Sensors page according to your needs. You can click the folder icon next to the name of the category to expand and contract the list of sensors. For details about Virtual 3D Sensors. You can sort by: • • Group (that is. and software version for each sensor. they are designated in the sensor list by a peer icon.1 Sourcefire 3D System Administrator Guide 115 . the sensor model) Sensor List The first column lists the hostname. sensor type. You can click the name of the health policy to view a read-only version of the policy. if one has been applied.9. and sensor groups. If you use clustered 3D9900 sensors. See Editing Health Policies on page 530 for information about modifying an existing health policy. sensor group. sensor model. see the Virtual Defense Center and 3D Sensor Installation Guide. When you hover over the peer icon. Virtual Sensor Count When you manage Virtual 3D Sensors from the Defense Center. The following sections describe some of the features on the Sensors page. intrusion agents. you can see which sensors are paired and if you configured the sensor as a master or a slave. Version 4.Using the Defense Center Working with Sensors Chapter 4 Understanding the Sensors Page Requires: DC + 3D Sensor The Sensors page (Operations > Sensors) provides you with a range of information and options that you can use to manage your sensors (including software-based sensors). the field for a Virtual Sensor count appears above the sensor list on the Sensors page.

See Managing System Policies on page 320 for more information.1 Sourcefire 3D System Administrator Guide 116 . See Editing a Managed Sensor’s System Settings on page 133 for more information. The icon and the name of the policy in the bottom row indicate that the version applied to the sensor is up to date. If you sort your Sensors page by sensor group. If the Defense Center has not received a communication from a sensor within the last two minutes. If a policy has a different icon and its name is in italics. If you hover your cursor over the icon. Status Icons The status icons indicate the state of a sensor. and access to the processes for stopping and restarting the sensor or its software.Using the Defense Center Working with Sensors Chapter 4 System Policy The next column lists the currently applied system policy. If your network is constrained in bandwidth. that indicates the policy was modified after it was applied to the sensor. See Editing Sensor Groups on page 132 for more information. The red exclamation point icon indicates that the Defense Center has not received communications from the sensor in the last three minutes. you can contact technical support to change the default time interval. a pop-up window indicates the amount of time (in hours. The green check mark icon indicates that the sensor and the Defense Center are communicating properly. it sends a two-byte heartbeat packet to establish contact and ensure that the communications channel is still running. The system settings include the storage settings for the sensor. you can click the name of the system policy to view a read-only version. Note that this is the case for any policy that you create and apply from the Defense Center. Edit and Delete Icons Click the Edit icon next to a sensor if you want to change the sensor’s current system settings. you can click the Edit icon next to the name of a sensor group to modify the list of sensors that belong to the group. Version 4.9. the remote management configuration. The policy name and the icon for the system policy in the top row highlight a special feature of the Sensors page. As with the health policy. the time. and seconds) since the last contact. minutes.

If you sort your Sensors page by sensor group. which monitor the health of your managed sensors Note that before you add sensors to a Defense Center. and custom login banners RNA detection policies. Adding Sensors to the Defense Center Requires: DC + 3D Sensor When you manage a sensor. see Adding Intrusion Agents on page 130 and the Sourcefire Intrusion Agent Configuration Guide. As the sensor evaluates the traffic. which control RNA data-gathering behavior and determine which networks are monitored which detection engines intrusion policies. You can create the following policies on your Defense Center and apply them to managed sensors: • • • • system policies.9. which control how protocol decoders and preprocessors are configured and which intrusion rules are enabled health policies. you can click the Delete icon next to the name of a sensor group to remove the sensor group from the Defense Center. You can also add Intrusion Agents to the Defense Center. you must delete and re-register the sensor. IMPORTANT! If you registered a Defense Center and 3D Sensor using IPv4 and want to convert them to IPv6.1 Sourcefire 3D System Administrator Guide 117 . which control appliance-level configurations such as database limits. Version 4.Using the Defense Center Working with Sensors Chapter 4 Click the Delete icon next to a sensor if you no longer want to manage the sensor with the Defense Center. See Deleting Sensor Groups on page 133 for more information. SSL-encrypted communication channel between the Defense Center and the sensor. This is usually completed as part of the installation process. The Defense Center uses this channel to send information about how you want to analyze your network traffic (in the form of policies) to the sensor. you set up a two-way. For more information. but you can refer to Configuring Network Settings on page 377 for details. you must make sure that the network settings are configured correctly on the sensor. DNS cache settings. it generates events and sends them to the Defense Center using the same channel. See Deleting Sensors on page 121 for more information.

1 Sourcefire 3D System Administrator Guide 118 . Select Operations > System Settings. Three fields are provided for setting up communications between appliances: • • • Management Host .for a unique alphanumeric ID. 2. The Information page appears.for registration key. Management Host. and Unique NAT ID used on the Defense Center. Registration Key . To add a sensor to a Defense Center: Access: Admin 1. Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. Registration Key. Unique NAT ID . you need: • the sensor’s IP address or hostname (in the connection context “hostname” is the fully qualified domain name or the name that resolves through the local DNS to a valid IP address) the Defense Center’s IP address or hostname to decide if you want to store the events generated by the sensor only on the Defense Center. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. Version 4. You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor.Using the Defense Center Working with Sensors Chapter 4 To add a sensor. Registration Key.9.for the hostname or IP address. Valid combinations include: • • • IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliances. or on both the Defense Center and the sensor • • TIP! Set up the managed appliance first. Refer to Working in NAT Environments on page 112 for more information. Log into the web interface of the sensor you want to add.

In the Management Host field. type a unique alphanumeric ID that you want to use to identify the sensor.1 Sourcefire 3D System Administrator Guide 119 . use both the Registration Key and the Unique NAT ID fields.9. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 5. the Pending Registration status appears. type the IP address or the host name of the Defense Center that you want to use to manage the sensor. After the sensor confirms communication with the Defense Center. The Add Remote Management page appears. In that case. 7. Click Save. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. in the Unique NAT ID field. The Remote Management page appears. 8. 4. 6. Click Remote Management. Optionally.Using the Defense Center Working with Sensors Chapter 4 3. Click Add Manager. Version 4. TIP! You can leave the Management Host field empty if the management host does not have a routable address. In the Registration Key field.

data is stored only on the Defense Center and not on the sensor. enter the same registration key that you used in step 6. You must store events on the Defense Center. By default. see Understanding Software Sensors on page 105. Type the IP address or the hostname of the sensor you want to add in the Host field. IMPORTANT! If you elect to prohibit sending packets and you do not store events on the 3D Sensor. 11. In the Registration Key field. 10. Packet data is often important for forensic analysis. The Add New Sensor page appears. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. For more information on supported functionality for software-based sensors. If you used a NAT ID in step 7.Using the Defense Center Working with Sensors Chapter 4 9. and select Operations > Sensors. 15. You can store data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. IMPORTANT! Software-based sensors such as the 3D Sensor Software for Crossbeam cannot store data locally. packet data is not retained.1 Sourcefire 3D System Administrator Guide 120 . 13. Click New Sensor. You can prevent packet data from leaving a sensor by enabling the Prohibit Packet Transfer to the Defense Center check box. The Sensors page appears. Version 4.9. Log into the Defense Center’s web interface using a user account with Admin access. 12. 14. enter the same ID in the Unique NAT ID (optional) field.

Log into the Defense Center web interface and select Operations > Sensors. To add the sensor to a group.9. you should delete the managed sensor from the Defense Center and then re-add it rather than try to delete the non-communicative detection engine. You can view the sensor’s status on the Sensors page (Operations > Sensors). To keep the sensor from trying to reconnect to the Defense Center. Contact technical support for more information. The sensor is added to the Defense Center. you may need to use the Add Manager feature a second time to add the secondary Defense Center. To manage the sensor again at a later date.Using the Defense Center Working with Sensors Chapter 4 16. To delete a sensor from the Defense Center: Access: Admin 1. For more information about groups. if the sensor is down or the network interface card is damaged). This interval ensures that the high availability pair re-synchronizes so that both Defense Centers recognize the deletion. The Sensors page appears. you can delete it from the Defense Center. 2.1 Sourcefire 3D System Administrator Guide 121 . you must re-add it to the Defense Center. Sourcefire recommends that you wait at least five minutes before re-adding it. Deleting a sensor severs all communication between the Defense Center and the sensor. 17. Click Delete next to the sensor you want to delete. Communication between the sensor and the Defense Center is discontinued and the sensor is deleted from the Sensors page. If you do not wait five minutes. Version 4. Deleting Sensors Requires: DC + 3D Sensor If you no longer want to manage a sensor. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. select the group from the Add to Group list. see Managing Sensor Groups on page 131. you should also delete the manager on the sensor. IMPORTANT! If you delete a sensor from a Defense Center configured in a high availability pair and intend to re-add it. Click Add. it may take more than one synchronization cycle to add the sensor to both Defense Centers. TIP! If you can no longer communicate with a detection engine on a managed sensor (for example. IMPORTANT! In some high availability deployments where network address translation is used.

Click Delete next to the Defense Center where you want to reset management.9. Select Operations > Sensors. You must first delete the manager on the sensor and delete the sensor on the Defense Center. For more information on resetting management on a Crossbeam-based software sensor. see Managing Communication on a Managed Sensor on page 138. The Information page appears. You can then re-add the manager on the sensor and then add the sensor to a Defense Center. Select Operations > System Settings. The Remote Management page appears. To reset management: Access: Admin 1. Click Remote Management. Using a user account with Admin access. you can reset management of the sensor. For more information on resetting management on a 3Dx800 sensor. 4. 5. TIP! To temporarily disable communications between appliances without having to reset management. If you want to manage a sensor with a different Defense Center. Resetting Management of a Sensor Requires: DC + 3D Sensor If communications fail between the Defense Center and one of your sensors. you must also reset management before adding the sensor to another Defense Center. Log into the web interface of the Defense Center where you want to reset communications. 6. The procedures for resetting management on the 3Dx800 sensors and on Crossbeam-based software sensors differ from the procedure for other sensors. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. see Resetting Communications on the 3Dx800 on page 128.Using the Defense Center Working with Sensors Chapter 4 3. For more information. you can disable the manager on the sensor. time management.1 Sourcefire 3D System Administrator Guide 122 . log into the web interface of the sensor you want to delete. Version 4. 2. If the sensor has a system policy that causes it to receive time from the Defense Center via NTP the sensor reverts to local . The manager is removed. The Sensors page appears.

The Add Remote Management page appears.example. 3. The Information page appears. Click Delete next to the Defense Center where you want to reset management. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. To delete management on the sensor: Access: Admin 1. If your sensor is no longer communicating with the Defense Center. maple. you can delete the management on the sensor. 2. Log into the web interface of the sensor where you want to reset communications. You can leave the Management Host field empty if the management host does not have a routable address.Using the Defense Center Working with Sensors Chapter 4 3. 4. In the Registration Key field. Click Delete next to the sensor you want to delete. The Remote Management page appears. Select Operations > System Settings. Click Remote Management. If you attempt to delete management on the sensor while it is communicating with the Defense Center you will receive an error similar to: Delete failed. In the Management Host field. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 3. Log into the web interface of the sensor where you want to reset communications and click Add Manager. Communication between the sensor and the Defense Center is discontinued and the sensor is deleted from the Sensors page. 2. type the IP address or the host name of the Defense Center that you want to use to manage the sensor. The manager is removed.com. use both the Registration Key and the Unique NAT ID fields. In that case.1 Sourcefire 3D System Administrator Guide 123 . Version 4.9. To re-add the sensor to the Defense Center: Access: Admin 1. You must delete the appliance from its manager.

6. 10. packet data is not retained. and select Operations > Sensors. Click New Sensor. The Add New Sensor page appears. 7. Click Save. After the sensor confirms communication with the Defense Center. In the Registration Key field. Type the IP address or the hostname of the sensor you want to add in the Host field. The Sensors page appears. 9.9. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. If you elect to prohibit sending packets and you do not store events on the 3D Sensor. Packet data is often important for forensic analysis. type a unique ID that you want to use to identify the sensor. Version 4. 11. Optionally.Using the Defense Center Working with Sensors Chapter 4 4. 12. type the same value in the Unique NAT ID field. By default. data is stored only on the Defense Center and not on the sensor. type the same one-time use registration key that you used in step 3. You can store data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. Log into the Defense Center’s web interface using a user account with Admin access. If you used a unique NAT ID in step 4. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box.1 Sourcefire 3D System Administrator Guide 124 . 8. in the Unique NAT ID field. the Pending Registration status appears. 5.

To manage a 3Dx800 sensor with a Defense Center: Access: Admin 1. select the group from the Add to Group list. 14. 3D Sensor 5800. you may need to use the Add Manager feature a second time to add the secondary Defense Center. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. To add the sensor to a group.domain [admin] Version 4. see Managing Sensor Groups on page 131. Managing a 3Dx800 Sensor Requires: DC + 3D Sensor Because the Sourcefire 3D Sensor 3800.Using the Defense Center Working with Sensors Chapter 4 13. In some high availability deployments where network address translation is used. Log into the 3D Sensor using the admin account. The CLI prompt appears. Click Add. This procedure assumes that you have completed the setup steps described in the sensor’s Installation Guide. Contact technical support for more information. and 3D Sensor 9800 (usually called the 3Dx800 sensors) do not have their own web interfaces.9. For more information about groups. The sensor is added to the Defense Center.1 Sourcefire 3D System Administrator Guide 125 . sensor. You can view the sensor’s status on the Sensors page (Operations > Sensors). you must add them to a Defense Center as managed sensors so that you can perform procedures such as: • • • • creating and applying intrusion and RNA detection policies viewing events generating reports uploading and installing software updates The following sections explain how to manage 3Dx800 sensors with a Defense Center: • • • Managing 3Dx800 Sensors with a Defense Center on page 125 Deleting a 3Dx800 Sensor from the Defense Center on page 127 Resetting Communications on the 3Dx800 on page 128 Managing 3Dx800 Sensors with a Defense Center Requires: DC + 3D Sensor Setting up communications between a 3Dx800 sensor and a Defense Center is a two-step process that involves setting up the sensor and then adding the sensor to the Defense Center.

the sensor may be managed by another Defense Center. and nat_id is a unique alphanumeric string. Select Operations > Sensors. reg_key is a unique single-use alphanumeric registration key. 5. If you changed the management port on the Defense Center. 8. enter the following command: [admin:sensor] set management enable NONE reg_key nat_id where NONE is a placeholder for the unresolvable IP address of the Defense Center.9. Use the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 7. In either case. Version 4. enter the following command: [admin:sensor] set management enable ip_address reg_key where ip_address is the IP address of the Defense Center and reg_key is a unique single-use alphanumeric registration key. Use one of the following commands to enable management on the 3D Sensor: • If you are deploying your sensor in a network that does not use network address translation. 6. 4. The Sensors page appears.1 Sourcefire 3D System Administrator Guide 126 . Using a user account with Admin access. log into the web interface of the Defense Center where you want to add the sensor. a message appears indicating that remote management is enabled.Using the Defense Center Working with Sensors Chapter 4 2. See Resetting Communications on the 3Dx800 on page 128 for information about deleting the sensor from the other Defense Center and preparing it for new management. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. Enter the following at the CLI prompt: [admin] configure sensor 3. Use the following command to determine whether remote management is already enabled: [admin:sensor] show management If management is already enabled. you must change it on the 3Dx800 also: [admin:sensor] set management port port_number where port_number is the same port number you used on the Defense Center. • If you are deploying your sensor in a network that does use network address translation. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center.

type the same value in the Unique NAT ID field. make sure the Store Events and Packets Only on the Defense Center check box is selected.Using the Defense Center Working with Sensors Chapter 4 9. If you prohibit sending packets to the Defense Center. In the Host field. The Add New Sensor page appears. to manage it with a different Defense Center). IMPORTANT! Because 3Dx800 sensors do not have any local storage for events. Click New Sensor. 14. type the IP address or the hostname of the sensor you want to add. see Managing Sensor Groups on page 131. type the same one-time use registration key that you used on the sensor. For more information about groups.9. Click Add. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box. 13. you must complete a two-step process to disable remote management and then delete it from the Defense Center. 15. is not retained anywhere. 11. 10. select the name of the group from the Add to Group list. In the Registration Key field. Deleting a 3Dx800 Sensor from the Defense Center Requires: DC + 3D Sensor If you want to delete a 3Dx800 sensor from a Defense Center (for example. which is often important for forensic analysis. If you used a NAT ID in step 4. 12. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. To add the sensor to a group. packet data. Version 4. The 3Dx800 is added to the Defense Center.1 Sourcefire 3D System Administrator Guide 127 .

6. The Sensors page appears. Click Delete next to the sensor that is no longer communicating with the Defense Center. 3. 7. 4. Log into the web interface of the Defense Center where you want to delete the sensor. The sensor is deleted. see the next section. Log into the web interface of the Defense Center that manages the sensor. The CLI prompt appears. On the sensor.1 Sourcefire 3D System Administrator Guide 128 . access the command prompt and use the admin account to log in. On the sensor.9. Select Operations > Sensors. you can manually reset communications on the sensor. Select Operations > Sensors. sensor. Click Delete next to the sensor you want to delete.domain [admin] 2. The sensor is deleted. you must re-enable remote management and then add the sensor to the Defense Center. The Sensors page appears. For more information. Enter the following command to disable remote management: [admin:sensor] set management disable A message appears indicating that remote management is disabled. access the command prompt and use the admin account to log in. Enter the following at the CLI prompt: [admin] configure sensor 2. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit To add the sensor to either the same or a different Defense Center. Resetting Communications on the 3Dx800 Requires: DC + 3D Sensor If communication fails between a 3Dx800 sensor and the Defense Center that manages it. 3. Version 4. The CLI prompt appears.domain [admin] 5.Using the Defense Center Working with Sensors Chapter 4 To delete a 3Dx800 sensor from a Defense Center: Access: Admin 1. To reset communications between the sensor and the Defense Center: Access: Admin 1. 4. Resetting Communications on the 3Dx800. sensor.

The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center. In the Host field. Use one of the following commands to enable remote management. • If your sensor is in a network that does not use network address translation.9. type the IP address or hostname of the sensor and make sure the Store Events and Packets Only on the Defense Center check box is selected. and nat_id is a unique alphanumeric string. 8. enter the following command: [admin:sensor] set management enable NONE reg_key nat_id where NONE is a placeholder for the unresolvable IP address of the Defense Center.1 Sourcefire 3D System Administrator Guide 129 . 7. Communications are restarted and the sensor is re-added to the Defense Center. 10. Enter the following at the CLI prompt: [admin] configure sensor 6. Enter the following command to disable remote management: [admin:sensor] set management disable Remote management is disabled. On the Defense Center’s Sensors page. reg_key is a unique single-use alphanumeric registration key. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. 11. • If your sensor is in a network that does use network address translation. The Sensors page appears. In either case.Using the Defense Center Working with Sensors Chapter 4 5. remote management is enabled again. enter the following command: [admin:sensor] set management enable ip_address reg_key where ip_address is the IP address of the Defense Center and reg_key is a unique single-use alphanumeric registration key. Version 4. Click Add. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 9. re-add the sensor by clicking New Sensor.

Version 4. 5. event view pages. The Intrusion Agent is added and the page reloads. and reports. Access the Defense Center web interface and select Operations > Sensors.Intrusion Agent Page Requires: DC + Intrusion Agent The Sensor Attributes page for Intrusion Agents allows you to view basic information about the Intrusion Agent and allows you to download authentication credentials. enter the IP address granted by the NAT device. Click Download Auth Credentials and save them for later use on the Intrusion Agent. For information on the requirements for the intrusion agent side of the connection. In the Hostname or IP Address field. Click Add Agent. type the Intrusion Agent’s host name (if DNS resolution is enabled on the Defense Center) or IP address. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. During configuration. It will appear on the event summary. Sensor Attributes . see the Sourcefire Intrusion Agent Configuration Guide. 2. To add an Intrusion Agent: Access: Admin 1. see Sensor Attributes . The Agent Administration page appears. you copy this file to the Intrusion Agent appliance to allow the Intrusion Agent to authenticate with the Defense Center.Using the Defense Center Working with Sensors Chapter 4 Adding Intrusion Agents Requires: DC + Intrusion Agent The Add Agent page allows you to add an Intrusion Agent. The Managed Sensors page appears. register all Intrusion Agents to the primary Defense Center. type an identifying name for the agent. 6. you should the IP address that the Defense Center will “see” when the Intrusion Agent attempts to communicate with it. 4. Click New Agent. WARNING! If your Intrusion Agent sensor resides behind a NAT device. that is. To download authentication credentials.1 Sourcefire 3D System Administrator Guide 130 . displaying a link that allows you to download authentication credentials.9. In the Name Of Agent field. This is the name that the Defense Center uses to identify the Intrusion Agent.Intrusion Agent Page on page 130. 3.

The Managed Sensors page appears. Click Download Credential File. and update multiple sensors with new software updates at the same time.Using the Defense Center Managing Sensor Groups Chapter 4 Authentication credentials are unique to each Intrusion Agent appliance and Defense Center and cannot be copied from one appliance to another. Access the Defense Center web interface and select Operations > Sensors.9. To create a sensor group and add sensors to it: Access: Admin 1. To download authentication credentials from the Sensor Attributes page: Access: Admin 1. 3. For more information about copying the credentials. see the Sourcefire Intrusion Agent Configuration Guide. Click Edit next to the Intrusion Agent. select Operations > Sensors. For information about Defense Center groups. Version 4. Managing Sensor Groups Requires: DC + 3D Sensor The Defense Center allows you to group sensors so that you can easily apply policies and install updates on multiple sensors.1 Sourcefire 3D System Administrator Guide 131 . The System Settings page for the Intrusion Agent appears. Deleting Sensor Groups on page 133 explains how to delete a sensor group. Editing Sensor Groups on page 132 explains how to modify the list of sensors in a sensor group. You are prompted to download the credentials to your local computer. Creating Sensor Groups Requires: DC + 3D Sensor Grouping managed sensors allows you to configure multiple sensors with a single system or health policy. On the Defense Center. see Managing Appliance Groups on page 179. The Sensors page appears. 2. See the following sections for more information: • • • Creating Sensor Groups on page 131 explains how to create a sensor group on the Defense Center.

5. The sensors are added to the group. TIP! You must remove a sensor from its current group before you can add it to a new group. See Applying an Intrusion Policy in the Analyst Guide for details. Editing Sensor Groups Requires: DC + 3D Sensor You can change the set of sensors that reside in any sensor group. Click Save. 3. To add sensors to the group. Version 4. you must apply a new policy to the sensor or sensor group. To edit a sensor group: Access: Admin 1. Select the IP addresses or hostnames of the sensors you want to add from the Available Sensors list and click the arrow to move them into sensor group. The Sensors page appears. The Sensor Group Edit page appears.9. To change the sensor’s policy. Click Create New Sensor Group. On the Defense Center. select Operations > Sensors. Click Save. 4. 6. In the Group Name field. The Create Sensor Group page appears. 7. type the name of the group you want to create. return to the Sensors page (Operations > Sensors) and click Edit next to the name of the sensor group.1 Sourcefire 3D System Administrator Guide 132 . Moving a sensor to a new group does not change its policy to the policy previously applied to the group.Using the Defense Center Managing Sensor Groups Chapter 4 2. The group is added.

To remove a sensor from a group. 2. On an unmanaged sensor you can use the sensor’s web interface to modify the settings as needed.1 Sourcefire 3D System Administrator Guide 133 . They are not deleted from the Defense Center. 3. Editing a Managed Sensor’s System Settings Requires: DC or 3D Sensor Each sensor has a number of system settings. Click Delete next to the group you want to delete. The Sensor Group Edit page appears. Click Done. Deleting Sensor Groups Requires: DC + 3D Sensor If you delete a group that contains sensors. The Sensors page appears. Click Edit next to the sensor group you want to edit.9. 4. Select the sensor you want to move and click the arrow to add or remove it from the group. • • To add a sensor to the group. When you Version 4. the sensors are moved to Ungrouped on the Sensors page. To delete a sensor group: Access: Admin 1. select it from the Available Sensors list and click the arrow pointing toward the group you are editing.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. Select Operations > Sensors. select it from the list in the group you are editing and click the arrow pointing to the Available Sensors list.

modify the default settings for each network interface on the managed sensor. 3. see Stopping and Restarting a Managed Sensor on page 137. From the System Settings page. you can: • • view detailed information about the sensor. For more information. For more information. IMPORTANT! You cannot edit the network settings or add a license file to a sensor through the Defense Center’s web interface. See Configuring System Settings on page 360 for more information about system settings.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 manage one or more sensors with a Defense Center. You must perform those tasks on the sensor’s web interface (generally before you begin to manage the sensor with the Defense Center). To edit the system settings for a managed sensor: Access: Admin 1. see Viewing a Sensor’s Information Page on page 135. Click Edit next to the name of the sensor where you want to edit the system settings. 2.9. On the Defense Center. you can modify their system settings through the Defense Center’s web interface.1 Sourcefire 3D System Administrator Guide 134 . Version 4. The Sensors page appears. It is possible to select a setting that makes it difficult to access the web interface. see Editing Network Interface Configurations on page 380. select Operations > Sensors. The Appliance page appears and includes a list of links on the left side of the page that you can use to navigate between pages. WARNING! Do not modify the settings for the management interface unless you have physical access to the appliance. For more information. • reboot or restart the processes on the managed sensor.

For more information.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 • manage communications between the sensor and the Defense Center. Enable this check box to prevent the managed sensor from sending packet data with the events. the fields are slightly different. Product Model Software Version Store Events Only on Defense Center Prohibit Packet Transfer to the Defense Center Operating System Operating System Version VDB Version IPv4 Address Version 4. see Managing Communication on a Managed Sensor on page 138. blacklist individual health policy modules on the managed sensor. • • Viewing a Sensor’s Information Page Requires: DC or 3D Sensor The Information page for a managed sensor includes the fields described in the Sensor Information table. see Setting the Time on a Managed Sensor on page 139. The version of the software currently installed on the managed sensor. Note that is the name of the sensor in the Defense Center web interface. Clear this check box to store event data on both appliances. The IPv4 address of the managed sensor. The version level of the vulnerability database currently loaded on the managed sensor. Sensor Information Field Name Description The assigned name for the managed sensor. see Blacklisting a Health Policy Module on page 537. not the hostname.9. For more information. but not the managed sensor. The version of the operating system currently running on the managed sensor. The operating system currently running on the managed sensor.1 Sourcefire 3D System Administrator Guide 135 . See Editing Settings for a Managed Defense Center on page 175. Enable this check box to store event data on the Defense Center. For more information. When you view the Information page for a managed Defense Center from the Master Defense Center’s web interface. manage time settings on the managed sensor. The model name for the managed sensor. Clear this check box to allow packet data to be stored on the DC with events.

• The name of the current system policy is listed under System. Model Number Current Group The model number for the sensor. Select Operations > Sensors.9. The appliance-level policies currently applied to the managed sensor. • The name of the current health policy is listed under Health. and seconds) since the sensor communicated with the Defense Center. If a policy has been updated since it was last applied. To edit a managed sensor’s settings: Access: Admin 1. The Sensors page appears. Version 4.1 Sourcefire 3D System Administrator Guide 136 . Status An icon showing the current status of the managed sensor. if you applied one from the Defense Center that manages the sensor. the name of the policy appears in italics.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 Sensor Information (Continued) Field IPv6 Address Current Policies Description The IPv6 address of the managed sensor. If you hover your cursor over the icon. a pop-up message indicates how long it has been (in hours. This number can be important for troubleshooting. See Creating Sensor Groups on page 131 for more information. The sensor group that the sensor belongs to. if any. You can click Refresh to update the Status icon and its accompanying pop-up message. minutes.

you can reboot or restart the processes on a managed sensor using the Defense Center’s web interface.9. 3. See the Sensor Information table on page 135 for a description of each field. 4. and Intrusion Agents. You must use the command line interface (CLI) to manage processes on Crossbeam-based software sensors. You can edit the following: • • • the sensor’s hostname where events generated by the sensor are stored the group in which the sensor resides WARNING! Sensor host names must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. Stopping and Restarting a Managed Sensor Requires: DC For 3D Sensors. Click Edit next to the name of the sensor whose system settings you want to edit. RNA Software for Red Hat Linux.1 Sourcefire 3D System Administrator Guide 137 . The updated sensor attributes are saved. Version 4. Click Save. The Information page for that sensor appears. Change the sensor’s attributes as needed.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2.

Managing Communication on a Managed Sensor Requires: DC + 3D Sensor For most 3D Sensors. You must use the command line interface (CLI) to manage communication on 3Dx800 sensors. click Run Command next to Restart Appliance Console. the process shuts down the operating system on the appliance. To disable communications between the Defense Center and the sensor: Access: Admin 1. click Run Command next to Reboot Appliance. The Sensors page appears. RNA Software for Red Hat Linux. 4. Click Edit next to the name of the sensor that you want to restart.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 To shut down or restart a managed sensor: Access: Admin 1. If you want to reboot the sensor.1 Sourcefire 3D System Administrator Guide 138 . The Information page for that sensor appears. click Run Command next to Restart Detection Engines. you can manage communications between a managed sensor and the Defense Center managing it using the Defense Center’s web interface. you must press the power button on the appliance. 3. Select Operations > Sensors. If you want to restart the software processes on the sensor. WARNING! If you shut down the appliance. To shut off power. Select Operations > Sensors. If you want to restart the Snort and RNA processes. and Intrusion Agents. 2. Crossbeam-based software sensors. Specify what command you want to perform: • • • • If you want to shut down the sensor. The Sensors page appears. click Run Command next to Shutdown Appliance.9. Version 4. but does not physically shut off power. The Process page appears for your managed sensor. Click Process in the list to the left of the page.

Click Disable next to the name of the sensor. Click Edit next to the name of the sensor where you want to set the time. However. 4. you can manage time settings on a managed sensor using the Defense Center’s web interface. Click Edit next to the name of the sensor that you want to manage. then you can change it as part of the system settings.9. You must use the command line interface (CLI) to manage time settings on Crossbeam-based software sensors and RNA Software for Red Hat Linux. Select Operations > Sensors.Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. For 3D Sensors. Setting the Time on a Managed Sensor Requires: DC or 3D Sensor If your managed sensor is receiving its time from an NTP server. The Information page for that sensor appears. Communications between the two appliances are interrupted. 3. For information about editing the remote management communications from a sensor see Configuring Remote Access to the Defense Center on page 386. Click Remote Management in the list to the left of the page. The Remote Management page appears. TIP! To enable communications between the two appliances again.1 Sourcefire 3D System Administrator Guide 139 . See the NTP Status table on page 390 for a description of the values you are likely to see for a sensor that is synchronized with an NTP server. The Information page for that sensor appears. click Enable. if the system policy applied to the managed sensor allows you to set the time manually. The Sensors page appears. You cannot manage time settings on Intrusion Agents. which is the recommended setting for a managed sensor and its Defense Center. then you cannot change the time manually. 2. To set the time for a managed sensor: Access: Admin 1. Version 4.

shared configuration. after the time zone setting is saved. Changing the time zone with this option is equivalent to changing the time zone using the Time Zone Settings option in the user preferences. 7. When you connect the two 3D9900 sensors you determine which is the master. 4. click the time zone link located next to the date and time. Click Apply. this time zone option changes the time setting your user account uses on the Defense Center web interface. use a Defense Center to establish the clustered pair relationship between the two sensors and manage their joint resources. The time is updated. When you establish a clustered pair configuration. In other words.Using the Defense Center Managing a Clustered Pair Chapter 4 3. A pop-up window appears.9. Managing a Clustered Pair Requires: DC + 3D9900 You can increase the amount of traffic inspected on a network segment by connecting two fiber-based 3D9900 sensors in a clustered pair. The Time page appears showing the current time. you combine the 3D9900 sensors resources into a single. Select your time zone and click Save and.1 Sourcefire 3D System Administrator Guide 140 . 6. click Close to close the pop-up window. If you want to change the time zone. Click Time in the list to the left of the page. select the following: • • • • • year month day hour minute 5. Version 4. After you do the cabling. From the Set Time drop-down lists. You connect the master to the network segment you wish to analyze. This setting does not affect the time zone setting on the managed sensor.

9. and data from a clustered pair.Using the Defense Center Managing a Clustered Pair Chapter 4 After you establish the relationship between the two sensors. and local management is blocked on the shared portion of the clustered pair. interface set. For information on the detection engines. they act like two separate sensors with a single. see: • • • Using Detection Engines on Clustered 3D Sensors on page 228 Understanding Interface Sets on Clustered 3D Sensors on page 229 Managing Information from a Clustered 3D Sensor on page 230 The Defense Center manages the clustered pair. shared detection configuration.1 Sourcefire 3D System Administrator Guide 141 . see the Cluster Interconnect table. For information about the connections between the master and slave 3D9900 sensors. The following diagram shows interfaces on the master and slave sensors. Cluster Interconnect Master Interface ethb2 RX ethb2 TX Slave Interface ethb0 TX ethb0 RX Version 4.

see the Sourcefire 3D Sensor Installation Guide.8. IMPORTANT! If you apply an RNA detection policy to the RNA detection engines on two different 3D9900 sensors and then establish clustering with those two sensors. Connect the master’s ethb2 and ethb3 pair to the slave’s ethb0 and ethb1 pair as shown in the Cluster Interconnect table. Version 4.Using the Defense Center Managing a Clustered Pair Chapter 4 Cluster Interconnect Master Interface ethb3 RX ethb3 TX Slave Interface ethb1 TX ethb1 RX You connect the master to the network and the slave to the master. IMPORTANT! You cannot connect the slave’s ethb2 and ethb3 pair when you establish the clustered pairing. you must: • • • decide which unit will be the master have SEU 2. Before you begin.9. You determine the master/slave designation by the way you cable the pair. the detection engines and interface set are combined on the two sensors. see: • • Establishing a Clustered Pair on page 142 Separating a Clustered Pair on page 144 Establishing a Clustered Pair Requires: DC + 3D9900 You can group two fiber-based 3D9900 sensors in a clustered pair to increase throughput. you cannot change which sensor is the master or slave unless you break and reestablish the relationship using the Defense Center. For more information about cabling. After you establish the relationship. you must edit and reapply your detection policy after you establish clustering.1 Sourcefire 3D System Administrator Guide 142 . After you establish the master/slave relationship. For more information.6 or later loaded on your 3D9900 and Defense Center cable the units properly prior to designating the master/slave relationship Connect the master’s ethb0 and ethb1 pair to the network.

Clustering is established and a confirmation message appears.com. The Sensor page appears. If you attempt to manage the combined detection engines and interface set on the paired 3D9900 sensors. They are managed from the Defense Center. under status.Using the Defense Center Managing a Clustered Pair Chapter 4 There is one detection engine and interface set shared over the paired 3D9900 sensors. TIP! If you edit a 3D9900 that is not cabled as the master. you cannot perform the next series of steps.example. Select Operations > Sensors on your Defense Center. For example.com.example. Version 4. To establish 3D9900 clustered pairing: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 143 . select Clustered with birch. In the Clustering field. 3.9. The System Settings page appears and there is a Clustering field at the bottom. instead of the 3D9900 sensors. select the sensor you want to form a cluster with. 2. if the other member of your pair is birch. The Click Edit next to the 3D9900 sensor that you cabled for master operation. the following message is displayed.

the field reads: Status Clustered and Role Slave • 3D9900 clustering is established. 3. the field reads: Status Clustered sensor_name. 5. Click OK to confirm the Master/Slave pairing. 6. Review the confirmation message. Review the confirmation message and confirm the correct the Master/Slave pairing.9. Select Break Cluster in the Clustering field. If the system determines that the cabling is correct.Using the Defense Center Managing a Clustered Pair Chapter 4 4. Use the managing Defense Center to establish the cluster’s detection configurations for the interface set and detection engines. The 3D9900 sensors separate and the confirmation message disappears. Click Save. Separating a Clustered Pair Requires: DC + 3D9900 If you no longer need to use the two 3D9900 sensors as a clustered pair.1 Sourcefire 3D System Administrator Guide 144 . On the slave. detection engines) from the slave. where sensor_name is the name of the sensor you designated as the slave in step 3 and Role Master. IMPORTANT! While system verifies the cabling configuration. Version 4. the sensing traffic is interrupted. Select Operations > Sensors on your Defense Center. To separate a 3D9900 clustered pair: Access: Admin 1. verify that the Clustering field changes to indicate the correct state. The System Settings page appears with the Clustering field at the bottom. For example: 4. After clustering is established. 5. 2. • On the master. it removes detection configurations (interface sets. Note the Master/Slave pairing and click OK to confirm the Master/Slave that you want to separate the clustered pair. you can use the Defense Center to break the cluster. The Sensor page appears. Click Edit next to the 3D9900 sensor that you designated as the maser sensor when you connected the pair’s cables.

That is. Disabling High Availability and Unregistering Sensors on page 153 explains how to permanently remove the link between linked Defense Centers. Pausing Communication between Paired Defense Centers on page 154 explains how to pause communications between linked Defense Centers. Event data streams from managed sensors to both Defense Centers and certain configuration elements are maintained on both Defense Centers. Sourcefire strongly recommends that both Defense Centers in an HA pair be the same model. Guidelines for Implementing High Availability on page 149 outlines some guidelines you must follow if you want to implement high availability. If one Defense Center fails. RUA events.9. you can monitor your network for intrusion events. • • • • • • • Using High Availability on page 145 list the items that are and are not duplicated when you implement high availability. Monitoring the High Availability Status on page 152 explains how to check the status of your linked Defense Centers.Using the Defense Center Configuring High Availability Chapter 4 Configuring High Availability Requires: DC To ensure the continuity of operations. The DC500 model of the Defense Center and the Virtual Defense Center do not support high availability. Setting Up High Availability on page 150 explains how to specify primary and secondary Defense Centers. Restarting Communication between Paired Defense Centers on page 154 explains how to restart communications between linked Defense Centers. and compliance events without interruption using the second Defense Center. See the following sections for more information about setting up high availability. WARNING! Sourcefire recommends that you change configurations only on the primary Defense Center and that you keep your secondary Defense Center as a backup. RNA events. Version 4. the high availability feature allows you to designate redundant Defense Centers to manage 3D Sensors. do not attempt to set up high availability between a Defense Center 1000 and a Defense Center 3000. Using High Availability Requires: DC The DC1000 and DC3000 models of the Defense Center support high availability configurations.1 Sourcefire 3D System Administrator Guide 145 .

• • RNA detection policies RNA custom service detectors Version 4. where events generated by the sensor are stored. see Understanding High Availability on page 148 Sensor Configurations and User Information Requires: DC Defense Centers in a high availability pair (also called an HA pair) share the following sensor attributes and user information: • user account attributes and authentication configurations WARNING! Before you establish a high availability. • • • • • • • • • • custom dashboards authentication objects for Sourcefire 3D System user accounts custom workflows custom tables sensor attributes.9.1 Sourcefire 3D System Administrator Guide 146 . make sure you remove duplicate user accounts from one of the Defense Centers.Using the Defense Center Configuring High Availability Chapter 4 For more information on: • • • • sensor attributes and user information shared in a high availability pair. see Feature Licenses on page 148 details of high availability pair operation. see Health and System Policies on page 147 feature license operation in a high availability pair. and the group in which the sensor resides intrusion. see Sensor Configurations and User Information on page 146 health and system policies shared in a high availability pair. you must make sure that the admin account uses the same password on both Defense Centers. make sure you register all intrusion agents to the primary Defense Center. if you have any user accounts with the same name on both Defense Centers. and RUA detection engines intrusion policies and their associated rule states local rules custom intrusion rule classifications variable values and user-defined variables IMPORTANT! If your deployment includes intrusion agents and you are also using a Master Defense Center to manage your linked Defense Centers. Also. RNA. such as the sensor’s host name. because both Defense Centers must have an admin account.

For more information. the NTP function does not automatically switch. For 3D Sensors. the deletion of hosts. you can point to one Defense Center as your first NTP server and the other Defense Center as your second NTP server.9. TIP! If you employ an HA paired Defense Center as a NTP server. apply the policy after it synchronizes. blacklists. see Creating Compliance Policies in the Analyst Guide and Configuring Remediations in the Analyst Guide. you should quickly associate your compliance policies with the appropriate responses and remediations on the secondary Defense Center to maintain continuity of operations. you can synchronize time with multiple alternative NTP servers. if you created associations between rules or white lists and their responses and remediations on the secondary Defense Center. Version 4.1 Sourcefire 3D System Administrator Guide 147 . see Synchronizing Time on page 354. If you want identical system policies on both Defense Centers. However. and networks from the network map. If the primary Defense Center fails. modules. Defense Centers do not share the associations between the policies and their responses and remediations. Although system policies are shared by Defense Centers in a high availability pair. For more information.Using the Defense Center Configuring High Availability Chapter 4 • • • • activated custom fingerprints host attributes traffic profiles RNA user feedback. services. make sure you remove the associations so responses and remediations will only be generated by the primary Defense Center. and the deactivation or modification of vulnerabilities compliance policies and their associated rules compliance white lists • • To avoid launching duplicate responses and remediations when compliance policies are violated. they are not automatically applied. including notes and host criticality. is synchronized on a newly activated Defense Center. When you restore your primary Defense Center after a failure. Health and System Policies Requires: DC Health and system policies for Defense Centers and 3D Sensors are shared in high availability pairs.You must upload and install any custom remediation modules and configure remediation instances on your secondary Defense Center before remediations are available to associate with compliance policies. Allow enough time to ensure that 3D Sensor information about health policies.

1 Sourcefire 3D System Administrator Guide 148 . and NetFlow licenses: • • Both Defense Centers must have RNA host licenses if you want to manage 3D Sensors with RNA with the high availability pair. In an high-availability environment. if you want to use NetFlow data to supplement the data gathered by your 3D Sensors with RNA. if the primary Defense Center fails. • While RUA LDAP authentication objects are shared. so changes appear within two five-minute Version 4.Using the Defense Center Configuring High Availability Chapter 4 Defense Centers in an HA pair share the following system and health policy information: • • • • • • system policies system policy configurations (what policy is applied where) health policies health monitoring configurations (what policy is applied where) which appliances are blacklisted from health monitoring which appliances have individual health monitoring policies blacklisted Feature Licenses Requires: DC Defense Centers in an HA pair do not share RNA. see Configuring an RUA Agent on an Active Directory Server in the Analyst Guide. If one Defense Center does not have a NetFlow license. (Each Defense Center has a five-minute synchronization cycle. RUA. TIP! Both Defense Centers in a high-availability pair must have NetFlow licenses for at least the number of NetFlow-enabled devices you are using. you can make policy or other changes to either Defense Center. For more information. it will not receive data from your NetFlow-enabled devices. While NetFlow data and devices are shared.9. IMPORTANT! An RUA Agent can only connect to one Defense Center at a time. but the cycles themselves could be out of sync by as much as five minutes. both Defense Centers must have RUA licenses if you want to manage 3D Sensors with RUA with the high availability pair. the two Defense Centers must have enough NetFlow licenses to merge the list of devices on each. Understanding High Availability Requires: DC Although Defense Centers in high availability mode are named “primary” and “secondary. and any change you make to one Defense Center should be applied on the other Defense Center within ten minutes. you must make sure that your RUA Agents can communicate with the secondary Defense Center. ” Defense Centers periodically update each other on changes to their configurations.

rules. You cannot configure a recurring task schedule on the inactive Defense Center. Because the sensor has a policy applied to it that the secondary Defense Center does not recognize. nor have you previously managed any sensors with it.Using the Defense Center Configuring High Availability Chapter 4 cycles. managed sensors. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active. For example. nor created any new rules. Both Defense Centers must be running the same SEU version. Defense Centers configured as a high availability pair do not need to be on the same trusted management network. • By default. policies may appear incorrectly on the other Defense Center. nor do they have to be in the same geographic location. both Defense Centers can be configured with policies. if you make conflicting policy or other changes to both Defense Centers within the same window between Defense Centers syncs. Regardless of their designations as primary and secondary. For more information.) However. during this ten-minute window. and so on before you set up high availability. the secondary Defense Center displays a new policy with the name “unknown” until the Defense Centers synchronize. start with the secondary Defense Center in its original state. Also. regardless of the designations of the Defense Center as primary and secondary. Both Defense Centers must be running the same software version. The Defense Center software version must be the same or newer than the software version of managed 3D Sensors. Note that this also deletes event and configuration data from the Defense Center. • • • Version 4. That is. the sensor could contact the secondary Defense Center before the Defense Centers contact each other. if you create a policy on your primary Defense Center and apply it to a sensor that is also managed by your secondary Defense Center. the last change you make takes precedence. To make sure the secondary Defense Center is in its original state. see Guidelines for Implementing High Availability on page 149. you must follow these guidelines. use the Restore CD to remove changed settings. the Defense Centers use port 8305/tcp for communications.1 Sourcefire 3D System Administrator Guide 149 . Guidelines for Implementing High Availability Requires: DC To take advantage of high availability. You can change the port as described in Configuring the Communication Channel on page 383.9. TIP! To avoid confusion. you have not created or modified any policies. • You must designate one Defense Center as the primary Defense Center and one as the secondary.

then set up high availability as detailed in Setting Up High Availability on page 150.Using the Defense Center Configuring High Availability Chapter 4 • • All RNA software sensors managed by Defense Centers in high availability mode must be the same software version. Version 4. For information about editing the remote management communications between the two appliances. The High Availability page appears. To set up high availability for two Defense Centers: Access: Admin 1. but each of the Defense Centers must be able to communicate with the other and with the sensors they share.9. add the primary Defense Center and the secondary Defense Center is automatically added. TIP! To add an existing high availability pair of Defense Centers to a Master Defense Center. Before you configure high availability. set up remote management between each Defense Center and the Master Defense Center as detailed in Adding and Deleting Defense Centers on page 164. see Synchronizing Time on page 354. For details on setting time. WARNING! Sourcefire recommends that you change configurations only on the primary Defense Center and that you use your secondary Defense Center as a backup. In addition. That is. The two Defense Centers do not need to be on the same network segment. • Setting Up High Availability Requires: DC To use high availability. and vice versa.1 Sourcefire 3D System Administrator Guide 150 . Select Operations > Configuration > High Availability. 2. Log into the Defense Center that you want to designate as the secondary Defense Center. the primary Defense Center must be able to contact the secondary Defense Center at the IP address on the secondary Defense Center’s own management interface. For information about adding a Defense Center to a Master Defense Center. If you use a Master Defense Center to manage a high-availability pair of Defense Centers. use this sequence to establish communications between the three of them: First. either each Defense Center must be able to contact the sensors it manages or the sensors must be able to contact the Defense Center. see Editing the Management Virtual Network on page 385. you must designate one Defense Center as the primary and another Defense Center of the same model as the secondary. make sure you synchronize time settings between the Defense Centers you want to link. see Adding a Master Defense Center on page 165.

5. See Working in NAT Environments on page 112 for more information. The High Availability page appears. 9. 11. A success message appears. Type the hostname or IP address of the secondary Defense Center in the Secondary DC Host text box. Type a one-time-use registration key in the Registration Key text box 6. in the Unique NAT ID field. Type the hostname or IP address of the primary Defense Center in the Primary DC Host text box. Using an account with Admin access. Click the secondary Defense Center option. type a unique alphanumeric registration ID that you want to use to identify the primary Defense Center. The Secondary Defense Center Setup page appears. and the Peer Manager page appears. log into the Defense Center that you want to designate as the primary. You can leave the Primary DC Host field empty if the management host does not have a routable address. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. Click the primary Defense Center option.1 Sourcefire 3D System Administrator Guide 151 . 10. Optionally. use both the Registration Key and the Unique NAT ID fields. In that case. 4. Click Register. The Primary Defense Center Setup page appears. Version 4. 7.9. 8. Select Operations > Configuration > High Availability. showing the current state of the secondary Defense Center.Using the Defense Center Configuring High Availability Chapter 4 3.

You can also monitor the Task Status to see when the process completes. 13.9. Monitoring the High Availability Status Requires: DC Once you have identified your primary and secondary Defense Centers. Click Register. 14.1 Sourcefire 3D System Administrator Guide 152 . Select Operations > Configuration > High Availability. and the Peer Manager page appears. A success message appears.Using the Defense Center Configuring High Availability Chapter 4 12. 2. Log into one of the Defense Centers that you linked using high availability. it may take up to 10 minutes before all the rules and policies appear on both Defense Centers. you can use one of them to view status information about the other. type the same registration ID that you used in step 6 in the Unique NAT ID text box. including: • • • • • IP address product model operating system operation system version time the Defense Centers last synchronized To check high availability status: Access: Admin 1. showing the current state of the primary Defense Center. You can view the High Availability page to check the status of the link between the two Defense Centers. See Monitoring the High Availability Status on page 152. The High Availability page appears. Depending upon the number of policies and custom standard text rules they have. Type the same one-time-use registration key in the Registration Key text box you used in step 5. Version 4. If you used a unique NAT ID on the secondary Defense Center.

1 Sourcefire 3D System Administrator Guide 153 . it is automatically shared with the other Defense Center within 5 minutes. If you do not wait five minutes. This interval ensures that the high availability pair re-synchronizes first. You can view the following information: • • • the IP address of the other Defense Center in the HA pair the status. you must first disable the high availability link between them. The two Defense Centers automatically synchronize within ten minutes (five minutes for each Defense Center) after any action that affects a shared feature. However. see Editing the Management Virtual Network on page 385. Disabling High Availability and Unregistering Sensors Requires: DC If you want to remove one of the Defense Centers from a high availability pair. Under High Availability Status.9. Sourcefire recommends that you wait at least five minutes before adding the sensor back. it may take more than one synchronization cycle to add the sensor to both Defense Centers. Version 4. Click Peer Manager in the toolbar. if you want to synchronize the policy immediately. 5. of the communications link the state. registered or unregistered. For example. of the HA pair For information about editing the remote management communications between the two appliances. enabled or disabled. if you create a new policy on one Defense Center. IMPORTANT! If you delete a sensor from a Defense Center configured in a high availability pair and intend to re-add it. click Synchronize. The Peer Manager page appears.Using the Defense Center Configuring High Availability Chapter 4 3. you can view the following information about the other Defense Center in the high availability pair: • • • • • the IP address the model name the software version the operating system the length of time since the last contact between the two Defense Centers 4.

Using the Defense Center Configuring High Availability Chapter 4 To disable a high availability pair: Access: Admin 1. Click Disable to disable the communications channel between the two Defense Centers. high availability is disabled and any managed sensors are deleted from the Defense Centers according to your selection. Restarting Communication between Paired Defense Centers Requires: DC If you temporarily disabled high availability. 3. 2. you can enable the communications channel between the Defense Centers to restart high availability. Pausing Communication between Paired Defense Centers Requires: DC If you want to temporarily disable high availability. The Peer Manager page appears. 2. you can disable the communications channel between the Defense Centers. 4. select Unregister sensors on both peers. After you answer the prompt Do you really want to Disable High Availability? by selecting OK. You can enable high availability with a different Defense Center as described in Setting Up High Availability on page 150. Click Disable HA. To disable the communications channel for a high availability pair: Access: Admin 1. To control all the managed sensors with the other Defense Center. see Editing the Management Virtual Network on page 385. select Unregister sensors on this peer. Version 4. To stop managing the sensors altogether. select Unregister sensors on the other peer. Select Operations > Configuration > High Availability.1 Sourcefire 3D System Administrator Guide 154 . Click Peer Manager. Log into one of the Defense Centers in the HA pair.9. Select one of the following options from the Handle Registered Sensors dropdown list: • • • To control all the managed sensors with the Defense Center where you are accessing this page. For information about editing the remote management communications between the two appliances. The High Availability page appears.

The Peer Manager page appears. see Editing the Management Virtual Network on page 385.9. 2.1 Sourcefire 3D System Administrator Guide 155 .Using the Defense Center Configuring High Availability Chapter 4 To enable the communications channel for a high availability pair: Access: Admin 1. Version 4. For information about editing the remote management communications between the two appliances. Click Enable to disable the communications channel between the two Defense Centers. Click Peer Manager.

and white list events from up to ten Defense Centers within your Sourcefire 3D System deployment. compliance events. You can use the Master Defense Center to aggregate and analyze intrusion events.1 Sourcefire 3D System Administrator Guide 156 .Using the Master Defense Center Chapter 5 Administrator Guide The Sourcefire Master Defense Center is a key component in the Sourcefire 3D System.9. Version 4.

Managing Appliance Groups on page 179 explains how to use appliance groups to aid in managing 3D Sensors and Defense Centers. When you apply intrusion policies from a Master Defense Center.9. the Sourcefire 3D System checks the SEU on the managing Defense Center. you can view the current status of the Defense Centers across your enterprise from a web interface. Understanding Global Policy Management on page 161 explains which policies you can send from your Master Defense Center to 3D Sensors and Defense Centers. You can configure a Defense Center to send intrusion events based on their flag. it updates the managing Defense Center’s SEU. The following sections explain more about using a Master Defense Center in your Sourcefire 3D System deployment. The settings on the Filter Configuration page determine which events are forwarded from the Defense Center to the Master Defense Center. The Master Defense Center can also aggregate events related to the health of managed Defense Centers. See the following sections for more information: • • • Aggregating Intrusion Events on page 158 Aggregating Compliance Events on page 158 Limitations on Event Aggregation on page 159 Version 4. You can set up a different configuration for each Defense Center. • • • • Understanding Event Aggregation Requires: MDC A Master Defense Center can aggregate intrusion events and compliance events (including white list events) from up to ten Defense Centers.1 Sourcefire 3D System Administrator Guide 157 . You can also choose whether to include the packet data collected with the intrusion events. If it finds an older SEU.Using the Master Defense Center Understanding Event Aggregation Chapter 5 You can use the Master Defense Center to build and dispatch global detection and intrusion policies. Adding and Deleting Defense Centers on page 164 explains how to configure a Defense Center to communicate with a Master Defense Center. • Understanding Event Aggregation on page 157 explains which types of events you can send from your Master Defense Centers to your Master Defense Center. although most deployments will use the same configuration across the enterprise. Editing Settings for a Managed Defense Center on page 175 explains how to change some of the settings for a Defense Center from the Master Defense Center’s web interface. In this way. IMPORTANT! The Product Compatibility section of the release notes for each version describes which versions of the Defense Center you can manage with a Master Defense Center.

If you do not deploy 3D Sensors with RNA on your network. any packets captured for the event are not sent. you may want to limit the intrusion events on the Master Defense Center to only those with the greatest impact.Using the Master Defense Center Understanding Event Aggregation Chapter 5 Aggregating Intrusion Events Requires: MDC An intrusion event is generated by IPS when it analyzes network traffic and finds one or more packets that violate the currently applied intrusion policy. The conditions that can trigger a compliance rule include intrusion events.The intrusion events specified in the Flags section are forwarded to the Master Defense Center. that is. Aggregating Compliance Events Requires: MDC A compliance event is generated by a Defense Center when the conditions for a compliance rule in an active compliance policy are met. you can choose one of the following options: • • Do Not Send . preprocessors. you may also want to send intrusion events with the black inline result flag.9. then intrusion events are limited to gray impact flags to indicate unknown impact. Version 4. and anomalous network traffic. If your 3D Sensors are deployed inline and you are using intrusion rules set to Drop and Generate Events. you can greatly reduce the number of events sent from a Defense Center by excluding events with the blue or gray impact flags. along with any related packets. IMPORTANT! You must deploy both RNA and IPS on your network to generate intrusion events with meaningful impact flags. the red impact flag. For example. Packet decoders. however. Events and Packet Data . You can also use flag settings to reduce the number of intrusion events that are sent to the Master Defense Center in deployments where large numbers of intrusion events are being generated from your 3D Sensors. flow data.1 Sourcefire 3D System Administrator Guide 158 . and intrusion rules are all able to generate intrusion events. RNA events. • You can use the Flags section of the Filter Configuration page to forward only the intrusion events that are important to your analysis.The intrusion events specified in the Flags section. Events Only . When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center.Intrusion events are not forwarded to the Master Defense Center. For example. are forwarded to the Master Defense Center.

compliance events. remediation status. network interfaces. health events. and NetFlow. audit log. RNA events. interface sets. allows you search for intrusion events. scan results. vulnerabilities. health events. users. SEU import log. there are certain limitations that you should take into consideration when you design your Master Defense Center deployment. RNA and RUA feature licenses allows you to configure detection engines. The Master Defense Center and Defense Center Functional Comparison table compares and contrasts Defense Center and Master Defense Center functional areas. However. white list events.9.Using the Master Defense Center Understanding Event Aggregation Chapter 5 When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center. Analysis and reporting search Version 4. audit log. Master Defense Center and Defense Center Functional Comparison Function License provisions Master Defense Center provides product license Defense Center provides product license. client applications. SEU import log. white list events. services. 3D Sensor configuration allows you to configure detection engines allows you to search for intrusion events. host attributes. and RUA events. flow data. white list violations. you can choose to send or not send compliance events.1 Sourcefire 3D System Administrator Guide 159 . See the following sections for more information: • • Adding a Defense Center on page 168 Editing the Event Filter Configuration on page 176 Limitations on Event Aggregation Requires: MDC The Master Defense Center is a powerful tool for analyzing the potential malicious activity across your enterprise’s network. hosts. compliance events.

This means that if your Defense Centers are accepting events from their 3D Sensors up to the rate limit.1 Sourcefire 3D System Administrator Guide 160 . and not sending the packet data. For example. However. You can also limit the amount of data transferred between a Defense Center and its Master Defense Center by sending only intrusion event data.Using the Master Defense Center Understanding Event Aggregation Chapter 5 Master Defense Center and Defense Center Functional Comparison (Continued) Function Network scans Global policies Master Defense Center does not provide for Nessus and Nmap scans. In addition. you can gain insight into RNA-detected activity across your enterprise. you might want to adjust the filter to send only intrusion events with red impact flags. in cases where the intrusion event rate is high. you must adjust the event filter on the Master Defense Center so that only the most important events are forwarded from the Defense Centers. because you can forward compliance events and white list events from your managed Defense Centers to your Master Defense Center.9. To take advantage of this. allows you to build intrusion policies and to distribute them through connected Defense Centers to their managed 3D Sensors throughout the enterprise allows for collection of events from up to ten Defense Centers Defense Center provides Nessus and Nmap scans and results. on your Defense Centers you need to build compliance rules and policies that are triggered by the RNA events that interest you and forward the resulting compliance events to the Master Defense Center. Intrusion Agents Intrusion events generated by intrusion agents are not forwarded to the Master Defense Center. the Master Defense Center does not build a network map or host data for the hosts on your network. Event Rate The event rate limit for the Master Defense Center is the same rate limit on Defense Centers. Version 4. policies are normally downloaded only to their managed 3D Sensors Event consolidation events are collected only from managed 3D Sensors Data Generated by RNA The Master Defense Center cannot aggregate RNA events or flow data generated by RNA and forwarded to a Defense Center.

Existing RNA policies are available for viewing so that you can determine: • • • • RNA policy name and description Detection policy settings such as update interval. however if a newer SEU resides on the Master Defense Center than on a Defense Center in the path. system.1 Sourcefire 3D System Administrator Guide 161 . if client application are being detected. then the downstream SEU is updated.9.Using the Master Defense Center Understanding Global Policy Management Chapter 5 Understanding Global Policy Management Requires: MDC You can use the Master Defense Center to generate global intrusion policies and coordinate them with potential vulnerabilities detected by RNA policies. delete and export RNA on a Master Defense Center. if banners and HTTP URLs are captured. This ensures that a global intrusion policies utilize the latest SEU. which networks and NetFlow-enabled devices are monitored by NetFlow. apply edit. Defining IP Addresses and Ports for Your Network in the Analyst Guide provides the syntax used to specify IP addresses and port numbers within the variables and rules in your policy. Editing an Intrusion Policy in the Analyst Guide explains how to modify existing intrusion policies. The Master Defense Center sends the policy through a Defense Center to a 3D Sensor’s detection engine. Master Defense Center generated policies are not accessible on an intermediate Defense Center. Global intrusion policies are beneficial in rapid response scenarios and during enterprise-wide intrusion policy updates. Which networks and ports are monitored by the RNA policy If NetFlow is used to generate host information. Applying an Intrusion Policy in the Analyst Guide explains how to apply a new or updated intrusion policy to the appropriate IPS detection engines. RNA compares the data it collects and analyzes with its vulnerability database to determine the potential vulnerabilities on the detected host. Managing Global Intrusion Policies Requires: MDC Refer to the following sections for information about managing intrusion policies: • • • • Creating an Intrusion Policy in the Analyst Guide explains how to create an intrusion policy. • Version 4. For information on creating and applying as well as deleting RNA policies. as well as intrusion. and health policies. custom service decoders. see What is an RNA Detection Policy? in the Analyst Guide. see Importing and Exporting Objects on page 583. Managing Variables in the Analyst Guide explains how to create and manage variables that you can use within intrusion policies. You can also import and export compliance policies and rules. For information on import and export functions. and so on. You can build.

Refer to the following. delete. Note that SEUs can also contain new and updated decoders and preprocessors. and apply default health policies to the Master Defense Center and to connected Defense Centers.Using the Master Defense Center Understanding Global Policy Management Chapter 5 • Managing Intrusion Rules in the Analyst Guide explains how to enable and disable intrusion rules within an intrusion policy.1 Sourcefire 3D System Administrator Guide 162 . For information about health policies see the following: • • • • • • • Understanding Health Monitoring on page 483 Configuring Health Policies on page 489 Using the Health Monitor Blacklist on page 534 Configuring Health Monitor Alerts on page 539 Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555 See Health Policies on page 164 to distinguish the health policy modules that are useful on a Master Defense Center or Defense Center from those that are not. This section also explains how to configure rules in inline intrusion policies so that they drop malicious packets. delete. Using System Policies on a Master Defense Center Requires: MDC System policies allow you to manage the following functions on your Defense Centers or Master Defense Center: • • access configuration authentication profiles (Defense Center only) Version 4. Importing SEUs and Rule Files in the Analyst Guide explains how to download and import Security Enhancement Updates (SEUs) that contain new intrusion rules. edit. export. • Using RNA Detection Policies on a Master Defense Center Requires: MDC You can create. and for brief descriptions of those modules that are used.9. and apply RNA detection policies from a Master Defense Center. for information on the following RNA detection policy functions: • • • • Creating RNA Detection Policies in the Analyst Guide Applying an RNA Detection Policy in the Analyst Guide Editing an RNA Detection Policy in the Analyst Guide Deleting an RNA Detection Policy in the Analyst Guide Using Health Policies on a Master Defense Center Requires: MDC You can edit.

9. You cannot apply a non-filtered policy from a Defense Center then add filters to it from a managing Master Defense Center. Therefore. The Sourcefire 3D System bases intrusion policies on SEUs residing on the appliance where the policy is built. You can apply one or more custom intrusion policies filtered to monitor VLAN or subnetwork traffic on the network monitored by the detection engine where you apply the policy.Using the Master Defense Center Understanding Global Policy Management Chapter 5 • • • • • • • database limits DNS cache settings the mail relay host and a notification address for database prune messages language selection (English or Japanese) login banner the kinds and amount of RNA data stored in the database (Defense Center only) time synchronization settings See Managing System Policies on page 320 for information about system policy usage. Master Defense Center Policy Management Limitations Requires: MDC There are several types of policies including detection and prevention. and apply intrusion detection and prevention policies from a Master Defense Center. If it finds SEUs older than those on the Master Defense Center. a warning message with a check box appears. export. delete. RUA detection.1 Sourcefire 3D System Administrator Guide 163 . The Defense Center and Master Defense Center do not handle these policies in the same manner. if your Version 4. listing RNA hosts and events. However. edit. the Sourcefire 3D System checks for any older SEUs on Defense Center(s) managing those detection engines. you must apply a non-filtered policy to the detection engine from the same Defense Center or Master Defense Center. Detection and Prevention Policies You can create. and health policies. the Apply button activates. they are updated. TIP! Before applying a filtered policy. RNA Detection Policies RNA analysis and reporting functions such as using the network map. RNA detection. When you apply an intrusion policy to a 3D Sensor’s detection engines from a Master Defense Center. and listing client applications and vulnerabilities are performed on Defense Centers and not on Master Defense Centers. After you acknowledge the message by clicking its check box.

SSL -encrypted communication channel between the appliances. only the generic Default Health Policy is available for editing and application to appliances.Default Health Policy table on page 494. see the Enabled Defense Center Health Modules . Adding and Deleting Defense Centers Requires: MDC + DC When you manage a Defense Center with your Master Defense Center. you can view host profiles from event views by clicking the host profile icon ( ) next to an IP address. For a listing of the health policy modules that apply to Master Defense Centers. Default IPS. Default 3D Sensor. RUA Detection Policies There are currently no Real-Time User Awareness functions on a Master Defense Center. For a listing of the health policy modules that apply to Defense Centers.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 deployment includes RNA. System Policies System policies are applied only to Master Defense Centers and Defense Centers from a Master Defense Center. • • • Adding a Defense Center on page 168 Deleting a Defense Center on page 171 Resetting Management of a Defense Center on page 171 Version 4. Policies that are not applicable are implicitly disabled when there is an attempt to apply them to a Defense Center or an Master Defense Center. The Defense Center uses this channel to send events to the Master Defense Center. it should send to the Master Defense Center using the same channel. Health Policies The Master Defense Center monitors its health and the health of connected Defense Centers.Default Health Policy table on page 493. Default IPS (3Dx800 only). As the Defense Center receives events from its sensors. see Editing Health Policies on page 530. you set up a two-way. it evaluates which events. see the Enabled MDC Health Modules . Currently. RUA functions are available only on properly licensed Defense Centers. Master Defense Centers apply health policies only to Master Defense Centers and Defense Centers. and Default RNA Health Policies are not used on the Master Defense Center. based on filter configuration. For details about editing appropriate health policies.9.1 Sourcefire 3D System Administrator Guide 164 .

Select Operations > System Settings. you need to determine which events on the Defense Center you want to forward to the Master Defense Center. you must make sure that the network settings are configured correctly on both appliances. Log into the web interface of the Defense Center you want to add.1 Sourcefire 3D System Administrator Guide 165 . TIP! Set up the managed appliance first. and Unique NAT ID used on the Master Defense Center Management Host. add the remote management then at the managing Master Defense Center. add the primary Defense Center and the secondary Defense Center is automatically added. TIP! To add an existing high availability pair of Defense Centers to a Master Defense Center. and Unique NAT ID used on the Defense Center with Registration Key and Unique NAT ID used on the Master Defense Center IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliance. This is usually completed as part of the installation process. The Information page appears. At a Defense Center. See Working in NAT Environments on page 112 for more information. Valid combinations include: • • • Management Host or Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the Defense Center with Host.for the hostname or IP address. Registration Key. 2. Registration Key. To add a Master Defense Center. however before you do. but you can see Configuring Network Settings on page 377 for details.9. Version 4. Three fields are provided for setting up communications between appliances: • • • Management Host or Host. To add a Master Defense Center to a Defense Center: Access: Admin 1.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 Adding a Master Defense Center Requires: MDC + DC You can add a Master Defense Center connection to your Defense Center.for a unique alphanumeric ID.registration key Unique NAT ID (optional) . add the Defense Center. Registration Key .

You can leave the Management Host field empty if the management host does not have a routable address. 7. 5.1 Sourcefire 3D System Administrator Guide 166 . 8. Log into the Master Defense Center’s web interface using a user account with Admin access.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 3. the Pending Registration status appears. use both the Registration Key and the Unique NAT ID fields 6. Click Save. Optionally. The Add Remote Management page appears. Version 4.9. in the Unique NAT ID field. After the Defense Center confirms communication with the Master Defense Center. and select Operations > Appliances. In the Registration Key field. Click Remote Management. Click Add Manager. type the one-time use registration key that you want to use to set up a communications channel between the Master Defense Center and the Defense Center. 4. In the Management Host field. The Defense Centers page appears. In that case. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. The Remote Management page appears. 9. type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.

1 Sourcefire 3D System Administrator Guide 167 . use both the Registration Key and the Unique NAT ID fields 12. Note that if you select intrusion events. See Editing the Event Filter Configuration on page 176 for more information. The New Defense Center page appears. Type the IP address or the hostname of the Defense Center you want to add in the Host field. IMPORTANT! You must select at least one type of flag if you want to send intrusion events. Click New Defense Center. Under Filter Configuration. Version 4. identify the types of events you want to forward from the Defense Center to the Master Defense Center. type the same value in the Unique NAT ID (optional) field. In that case. you can send events or events and packet data. If you used an unique NAT ID in step 6. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 11. In the Registration Key field. You can also filter which intrusion events are forwarded based on their impact flag.9.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 10. type the same one-time use registration key that you used in step 6. 14. You can leave the Host field empty if the host does not have a routable address. 13. If you chose to send compliance events to the Master Defense Center. white list events are also sent.

Version 4.9. This is usually completed as part of the installation process. Registration Key. Adding a Defense Center Requires: MDC + DC Before you add a Defense Center to a Master Defense Center. IMPORTANT! If you registered a Master Defense Center and Defense Center using IPv4 and want to convert them to IPv6. then at the managing Master Defense Center add the Defense Center.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 15.for the hostname or IP address. Valid combinations include: • • • Management Host or Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the Defense Center with Host. and Unique NAT ID used on the Master Defense Center Management Host. You can view the status on the Defense Centers page (Operations > Appliances). Registration Key . add the remote management.for a unique alphanumeric ID. you must delete and re-register the Defense Center.one-time use registration key Unique NAT ID (optional) . The Defense Center is added to the Master Defense Center. Click Add. and Unique NAT ID used on the Defense Center with Registration Key and Unique NAT ID used on the Master Defense Center IMPORTANT! The Management Host or Host field (hostname or IP address) must be used on at least one of the appliance. TIP! Set up the managed appliance first. Three fields are provided for setting up communications between appliances: • • • Management Host or Host. Registration Key. It can take up to two minutes for the Defense Center to establish communication with the Master Defense Center. See Working in NAT Environments on page 112 for more information.1 Sourcefire 3D System Administrator Guide 168 . After communications between the two appliances are established. you must make sure that the network settings are configured correctly on both appliances. At a Defense Center. continue with the procedure in Adding a Defense Center. 16. For more information see Configuring Network Settings on page 377.

type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. The Information page appears. Optionally. The Add Remote Management page appears. To add a Defense Center to a Master Defense Center: Access: Admin 1. In that case. 2. Click Add Manager. the Pending Registration status appears.1 Sourcefire 3D System Administrator Guide 169 . type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. you need to predetermine which events on the Defense Center you want to forward to the Master Defense Center. use both the Registration Key and the Unique NAT ID fields. In the Registration Key field. in the Unique NAT ID field. Click Save. Select Operations > System Settings. Version 4. Click Remote Management. log into the web interface of the Defense Center you want to add. 4. After the Defense Center confirms communication with the Master Defense Center. In the Management Host field. TIP! You can leave the Management Host field empty if the management host does not have a routable address. type the one-time use registration key that you want to use to set up a communications channel between the Master Defense Center and the Defense Center. Using a user account with Admin access. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 7. 3. 8. 5.9. 6.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 To add a Defense Center. The Remote Management page appears.

Note that if you select intrusion events. See Editing the Event Filter Configuration on page 176 for more information. white list events are also sent. 14. If you used a NAT ID in step 7. 13. If you chose to send compliance events to the Master Defense Center.1 Sourcefire 3D System Administrator Guide 170 . In the Registration Key field.9. Under Filter Configuration. identify the types of events you want to forward from the Defense Center to the Master Defense Center. Click New Defense Center. 10. IMPORTANT! You must select at least one type of flag if you want to send intrusion events. You can also filter which intrusion events are forwarded based on their impact flag. type the same one-time use registration key that you used in step 6. The Defense Centers page appears. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 9. 11. and select Operations > Appliances. Version 4. Type the IP address or the hostname of the Defense Center you want to add in the Host field. Log into the Master Defense Center’s web interface using a user account with Admin access. you can send events or events and packet data. type the same value in the Unique NAT ID (optional) field. The New Defense Center page appears. 12.

Log into the Master Defense Center web interface. The manager is removed. 4.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 15. you must re-add it to the Master Defense Center. It can take up to two minutes for the Defense Center to establish communication with the Master Defense Center. 2. Deleting a Defense Center Requires: MDC + DC If you no longer want to manage a Defense Center. and select Operations > Appliances. You can view the status on the Defense Centers page (Operations > Appliances). The Defense Center is added to the Master Defense Center. Click Delete next to the Master Defense Center that was managing the Defense Center. Deleting a Defense Center severs all communication between the Defense Center and the Master Defense Center. you can reset management of the Defense Center. Click Delete next to the Defense Center you want to delete. To manage the Defense Center again at a later date. If you want to manage a Defense Center with a different Master Defense Center. Resetting Management of a Defense Center Requires: MDC + DC If communications fail between the Master Defense Center and one of your Defense Centers. Click Add. Click Remote Management.1 Sourcefire 3D System Administrator Guide 171 . you should also delete the manager on the Defense Center. To delete a Defense Center from the Master Defense Center: Access: Admin 1. you must also reset management before adding the Defense Center to the another Master Defense Center. You can then re-add the Master Defense Center on the Defense Center and then add the Defense Center to a Master Defense Center. 5. Version 4. The Information page appears. To keep the Defense Center from trying to reconnect to the Master Defense Center. To do this. 6. you must first delete the manager on the Defense Center and delete the Defense Center on the Master Defense Center. The Remote Management page appears. Communication between the Master Defense Center and the Defense Center is discontinued and the Defense Center is deleted from the Defense Centers page. Select Operations > System Settings. Log into the web interface of the Defense Center you want to delete.9. you can delete it from the Master Defense Center. The Defense Centers page appears. 3.

The Remote Management page appears. 3. use both the Registration Key and the Unique NAT ID fields Version 4. Click Delete next to the Defense Center you want to delete. 3. Click Delete next to the Master Defense Center where you want to reset management. 2. The manager is removed.9. Log into the web interface of the Defense Center where you want to reset communications and click Add Manager. The Information page appears. Select Operations > Appliances. 2. Log into the web interface of the Master Defense Center where you want to reset communications. In the Management Host field. 2. To delete management on the Defense Center: Access: Admin 1. The Remote Management page appears. 4. In that case. type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. The Defense Centers page appears.1 Sourcefire 3D System Administrator Guide 172 . Communication between the Defense Center and the Master Defense Center is discontinued and the Defense Center is deleted from the Defense Centers page. To re-add the Defense Center to the Master Defense Center: Access: Admin 1.Using the Master Defense Center Adding and Deleting Defense Centers Chapter 5 To reset management from a Master Defense Center: Access: Admin 1. Click Remote Management. Log into the web interface of the Defense Center where you want to reset communications. Select Operations > System Settings. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. TIP! You can leave the Management Host field empty if the management host does not have a routable address.

8. See Working in NAT Environments on page 112 for more information.1 Sourcefire 3D System Administrator Guide 173 . Optionally. Click New Defense Center. 7. 6. If you used an alphanumeric NAT ID in step 4.Using the Master Defense Center Using the Appliances Page Chapter 5 3. type the same value in the Unique NAT ID (optional) field. The following sections describe the features on the Appliances page. 12. type the same one-time use registration key that you used in step 3. Type the IP address or the hostname of the Defense Center you want to add in the Host field. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. After the Defense Center confirms communication with the Master Defense Center. 10. the Pending Registration status appears. In the Registration Key field. Click Save. type the one-time use registration key that you want to use to set up a communications channel between the Defense Center and the Master Defense Center. The Add New Defense Center page appears. Version 4.9. The Defense Centers page appears. For more information about Defense Center groups. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. see Managing Appliance Groups on page 179. You can view the Defense Center’s status on the Defense Centers page (Operations > Appliances). 9. To add the Defense Center to a group. 11. In the Registration Key field. 5. Using the Appliances Page Requires: MDC + DC The Appliances page (Operations > Appliances) provides you with a range of information and options that you can use to manage your Defense Centers. in the Unique NAT ID field. select the group from the Add to Group list. The Defense Center is added to the Master Defense Center. 4. It can take up to two minutes for the Master Defense Center to verify communication with the Defense Center. Click Add. Log into the Master Defense Center’s web interface and select Operations > Appliances.

Using the Master Defense Center Using the Appliances Page Chapter 5 Sort-by Drop-Down List Use this drop-down list to sort the Appliances page according to your needs. The red exclamation point icon indicates that the Master Defense Center has not received communications from the Defense Center in the last three minutes. the remote management configuration. which sorts by Appliance group (see Managing Appliance Groups on page 179) TIP! High availability Defense Center pairs are automatically listed as an appliance group. If your network is constrained in bandwidth.1 Sourcefire 3D System Administrator Guide 174 . which sorts by the Defense Center then the 3D Sensor connected to it. An HA pair is listed as a group named with the name of the active Defense Center. a pop-up window indicates the amount of time (in hours. Model. See Editing Settings for a Managed Defense Center on page 175 for more information. and the high availability settings. and seconds) since the last contact. If you hover your cursor over the icon. it sends a two-byte heartbeat packet to establish contact and ensure that the communications channel is still running. See Deleting a Defense Center on page 171 for more information. which sorts by appliance model number. The system settings include the filter configuration for the Defense Center. 3D Sensor 2100. Click the Delete icon next to a Defense Center if you no longer want to manage the Defense Center with the Master Defense Center. minutes. Edit and Delete Icons Click the Edit icon next to a sensor if you want to change the Defense Center’s current system settings. the health blacklist settings. the Defense Center 1000 and the Defense Center 3000. that is. The green check mark icon indicates that the Master Defense Center and the Defense Center are communicating properly. If the Master Defense Center has not received a communication from a Defense Center within the last two minutes. Status Icons The status icons indicate the state of a Defense Center. • • Manager. You can sort by: • Group. Version 4.9. you can contact technical support to change the default time interval. and so on.

you can use the Master Defense Center web interface to view and edit the configuration of the Defense Center. The version of the software currently installed on the managed Defense Center. then click Edit next to the Defense Center. See the following sections for more information. not the hostname.9. Product Model Software Version Operating System Operating System Version VDB Version IP Address Version 4.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 Editing Settings for a Managed Defense Center Requires: MDC + DC After you configure management of a Defense Center by a Master Defense Center. select Appliances from the Operations menu. Defense Center Information Field Name Description The assigned name for the Defense Center.1 Sourcefire 3D System Administrator Guide 175 . The operating system currently running on the managed Defense Center. The model name for the managed Defense Center. • • • • • Viewing the Defense Center Information Page on page 175 Editing the Event Filter Configuration on page 176 Editing or Disabling Remote Management Communications on page 178 Managing the Health Blacklist on page 178 Managing High Availability Defense Centers on page 178 Viewing the Defense Center Information Page Requires: MDC + DC To access the system settings information page for a managed Defense Center. The IP address of the managed Defense Center. The Vulnerability Database version on the managed Defense Center. Note that this is the name of the Defense Center in the Master Defense Center web interface. The version of the operating system currently running on the managed Defense Center. The Information page for a managed Defense Center includes the fields described in the Defense Center Information table.

This number can be important for troubleshooting. a pop-up message indicates how long it has been (in hours. See the Impact Flags table in the Analyst Guide for an explanation of what each impact Version 4. 2. If you want to send intrusion events (with or without packet data). you can also specify which intrusion events are sent based on their impact flag. Your options are to send intrusion events. and compliance events. and seconds) since the Defense Center communicated with the Master Defense Center.9. Editing the Event Filter Configuration Requires: MDC The settings on the Filter Configuration page control which events are sent from the Defense Center to the Master Defense Center that manages it. The group that the Defense Center belongs to. To edit a managed Defense Center’s settings: Access: Admin 1. intrusion events and related packet data. The updated Defense Center attributes are saved. You can edit the following: • • the name of the Defense Center the group in which the Defense Center resides WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. If you hover your cursor over the icon. Click Save. Change the Defense Center’s attributes as needed. You can click Refresh to update the Status icon and its accompanying pop-up message. if any.1 Sourcefire 3D System Administrator Guide 176 . Model Number Current Group The model number for the Defense Center. minutes.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 Defense Center Information (Continued) Field Status Description An icon showing the current status of the managed Defense Center.

4. Note that you must deploy both RNA and IPS as part of your Sourcefire 3D System deployment to generate meaningful impact flags. To modify the event filter configuration: Access: Admin 1. Version 4. The options are Do Not Send. and Events and Packet Data. Next to the Defense Center whose filter configuration you want to change. click Edit. On the Master Defense Center’s web interface. 2. If you want to send intrusion events to the Master Defense Center. If you indicated that you want to send intrusion events. The Filter Configuration page appears. then you must specify which events you want to send based on their impact flag. select Operations > Appliances.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 flag means. 3. then packet data is not forwarded to the Master Defense Center. In the Intrusion Events area. The Appliances page appears. TIP! If you set up the 3D Sensor so it does not send packet data to the intermediate Defense Center. Events Only. then all the options are immediately selected.9. then you must select at least one impact flag option. The Flags options are: • • • • • • • All Black (or Drop) Red (or Vulnerable) Orange (or Potentially Vulnerable) Yellow (or Currently Not Vulnerable) Blue (or Unknown Target) Gray (or Unknown) TIP! If you select All.1 Sourcefire 3D System Administrator Guide 177 . use the drop-down list to indicate whether you want to forward intrusion events to the Master Defense Center.

1 Sourcefire 3D System Administrator Guide 178 . You cannot edit the Management Virtual Network field of a Master Defense Center. click Enable. See the following sections for more information: • • Using Redundant Defense Centers on page 112 Setting Up High Availability on page 150 Version 4. To disable communications between the Defense Center and the Master Defense Center: Access: Admin Click Disable next to the name of the Defense Center. In the Compliance Events area.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. see Using the Health Monitor Blacklist on page 534. For information on using the blacklisting function.0. For more information about editing the Management Virtual Network. The field is filled with 0. Editing or Disabling Remote Management Communications Requires: MDC + DC You can manage communications between a managed Defense Center and its Master Defense Center using the Master Defense Center’s web interface.Using the Master Defense Center Editing Settings for a Managed Defense Center Chapter 5 5. Managing the Health Blacklist Requires: MDC + DC You can blacklist individual health policy modules on Defense Centers. disable.9. see Editing the Management Virtual Network on page 385. Managing High Availability Defense Centers Requires: MDC + DC You can configure. monitor. For example. use the drop-down list to indicate whether you want to forward compliance events to the Master Defense Center. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network. if a Defense Center is no longer responding. you can temporarily disable communications between the Defense Center and its Master Defense Center. pause and restart Defense Center High Availability from a Defense Center.0. To enable communications between the two appliances again. The options are Do Not Send and Send. Communications between the two appliances are interrupted. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. Click Save. 6. Your settings are saved and the Defense Center begins forwarding the events you specified to the Master Defense Center that manages it.

TIP! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. you can activate Defense Center High Availability from a Master Defense Center. The System Settings page for that Defense Center appears. The high availability page appears with the paired Defense Centers. Managing Appliance Groups Requires: MDC The Master Defense Center allows you to group appliances so that you can easily search for events based on whether they were forwarded by one of a specific group of appliances. An HA pair is listed as a group with the name of the active Defense Center. Click Activate to activate the redundant Defense Center.1 Sourcefire 3D System Administrator Guide 179 . TIP! A light bulb icon shows which of the high availability paired Defense Centers is currently active. TIP! High availability Defense Center pairs are automatically listed as an appliance group.9. 4. To activate a redundant Defense Center: Access: Admin 1. Select Operations > Appliances. The Appliances page appears.Using the Master Defense Center Managing Appliance Groups Chapter 5 • • • • Monitoring the High Availability Status on page 152 Disabling High Availability and Unregistering Sensors on page 153 Pausing Communication between Paired Defense Centers on page 154 Restarting Communication between Paired Defense Centers on page 154 If High Availability is configured. 3. register all Intrusion Agents to the primary Defense Center. Click Edit next to the appropriate Defense Center. The redundant Defense Center is activated. Click High Availability. Version 4. 2.

3. 6. Select the IP addresses or hostnames of the appliances you want to add from the Available Appliances list and click the arrow to move them into the group. 4. The Appliances page appears. To create an appliance group and add appliances to it: Access: Admin 1. The Appliance Group Edit page appears.9. Creating Appliance Groups Requires: MDC Grouping managed appliances allows you to use the group name as a search criterion when you search for specific compliance or intrusion events. select Operations > Appliances. Deleting Appliance Groups on page 181 explains how to delete a Defense Center group. The Create Appliance Group page appears. Moving an appliance to a new group does not change any of its policies or configurations. Version 4. Click Save. Editing Appliance Groups Requires: MDC You can change the set of appliances that reside in any appliance group.Using the Master Defense Center Managing Appliance Groups Chapter 5 See the following sections for more information: • • • Creating Appliance Groups on page 180 explains how to create a Defense Center group on the Master Defense Center. Click Create New Appliance Group.1 Sourcefire 3D System Administrator Guide 180 . TIP! You must remove an appliance from its current group before you can add it to a new group. Editing Appliance Groups on page 180 explains how to modify the list of Defense Centers in a Defense Center group. In the Group Name field. The group is added. The appliances are added to the group and the Appliances page appears again. Click Save. On the Master Defense Center. type the name of the group you want to create. To add appliances to the group. 7. 5. 2. return to the Appliances page (Operations > Appliances) and click Edit next to the name of the group.

select Operations > Appliances. Click Edit next to the Appliance group you want to edit.9. Deleting Appliance Groups Requires: MDC If you delete a group that contains appliances. On the Master Defense Center. 2. the appliances are moved to Ungrouped on the Appliances page. the Master Defense Center system settings are the same as those of a Defense Center. To delete an appliance group: Access: Admin 1. Click Delete next to the group you want to delete. 3. Select Operations > Appliances. See the following sections for information on each of the listed system settings: IMPORTANT! NetFlow-enabled devices cannot currently be added to a Master Defense Center. To remove an appliance from a group. They are not deleted from the Master Defense Center. 4. The Appliances page appears. select it from the Available Appliances list and click the arrow pointing toward the group you are editing.1 Sourcefire 3D System Administrator Guide 181 . The appliances group is removed from the Master Defense Center. The Appliances page appears. 2.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To edit an appliance group: Access: Admin 1. Select the appliance you want to move and click the arrow to add or remove it from the group. Click Save. • • To add an appliance to the group. • • • • Listing Master Defense Center Information on page 182 Viewing a Master Defense Center License on page 182 Configuring Network Settings on page 377 Shutting Down and Restarting the System on page 182 Version 4. Editing Master Defense Center System Settings Requires: MDC With a few exceptions. select it from the list in the group you are editing and click the arrow pointing to the Available Appliances list. The Appliance Group Edit page appears.

a Master Defense Center cannot manage the licenses of Defense Centers or 3D Sensors. see Configuring Network Settings on page 377. The Information page appears. The License page appears. To view information about the Master Defense Center license: Access: Admin 1.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 • • Setting System Time on page 183 Blacklisting Health Policies on page 184 Listing Master Defense Center Information Requires: MDC For details on information listed under the Master Defense Center system settings. 2. WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. Viewing a Master Defense Center License Requires: MDC Unlike a Defense Center. You can: • • • shut down the appliance reboot the appliance restart the appliance Version 4.1 Sourcefire 3D System Administrator Guide 182 . The updated Master Defense Center attributes are saved. see Defense Center Information on page 175. Select Operations > System Settings.9. Change the name of the Master Defense Center attributes as needed. Configuring Network Settings Requires: MDC The network settings are identical to those of the Defense Center. Click License. 2. To edit a Master Defense Center’s settings: Access: Admin 1. Click Save. Shutting Down and Restarting the System Requires: MDC You have several options for controlling the processes on your Master Defense Center. For information on configuring the Master Defense Center network settings.

0. Version 4.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To shut down or restart your appliance: Access: Admin 1. click Run Command next to Shutdown Master Defense Center. If you want to reboot the system. Click Process. Note that restarting the Defense Center may cause deleted hosts to reappear. If you want to restart the Defense Center.0/24 to disable the Management Virtual Network. The Information page appears. 3. On the Time Synchronization page you can choose to serve time from the Master Defense Center by selecting Enabled in the Serve Time via NTP field. The field is filled with the address range 0. their real IP network is used to serve time. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network. click Run Command next to Restart Master Defense Center Console. Configuring Remote Management Networking Requires: MDC A Master Defense Center’s Management Virtual Network is disabled. 2. Select Operations > System Settings. Specify the command you want to perform: • • • If you want to shut down the Master Defense Center. The Appliance Process page appears. TIP! Because Master Defense Centers do not currently use Management Virtual Networks. Setting System Time Requires: MDC The system time is set and synchronized in accordance with the system policy. click Run Command next to Reboot Master Defense Center.1 Sourcefire 3D System Administrator Guide 183 .0.9. You cannot edit the Management Virtual Network field if the Defense Center is in the Master Defense Center operational mode.

Version 4. if DNS is enabled.1 Sourcefire 3D System Administrator Guide 184 . For more information about setting system time. you should configure your DHCP server to set the same NTP server.Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To specify how the Master Defense Center clock is set: Access: Admin You have two options: • • To set the time manually. To receive time through NTP from a different server. in the text box. select Manually in the System Settings. Blacklisting Health Policies Requires: MDC You can blacklist health policy modules when required. the DHCP-provided NTP server will be used instead. type the IP address of the NTP server or. The Master Defense Center supports the following health policy modules: • • • • • • • • Appliance Heartbeat CPU Usage Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Status Memory Usage For more information on blacklisting a health policy. type the fully qualified host and domain name. see Synchronizing Time on page 354. WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. To avoid this situation. see Blacklisting a Health Policy Module on page 537.9. select Via NTP Server from and.

However. In addition. and the third for RUA. Most 3D Sensor models have at least three detection resources available and can support at least three detection engines: one for IPS.9. Version 4.1 Sourcefire 3D System Administrator Guide 185 .Using Detection Engines and Interface Sets Chapter 6 Administrator Guide To give you increased flexibility in your deployment choices. one for RNA. The number of detection engines per sensor is limited by the number of detection resources that are available. You can think of a detection engine as a collection of one or more sensing interfaces (called an interface set) on a 3D Sensor plus a portion of the sensor’s computing resources (called a detection resource). 3D Sensors support three types of detection engines: • • • IPS RNA RUA TIP! You cannot use the RUA feature on Crossbeam-based software sensors. you can combine the data from those sensors with RUA or RNA on a Defense Center. you cannot use RUA or RNA on 3D9800 sensors. the Sourcefire 3D System provides a feature called the detection engine. See the Detection Resources by Model table on page 190 for more information.

Using Clustered 3D Sensors on page 227 explains how to use detection engines and interface sets in a clustered 3D9900 sensor pairing. Using Interface Set Groups on page 223 describes how to create and use interface sets groups. The Available Detection Engines page appears. and delete detection engines. Version 4. detection engine type. Managing Detection Engines on page 193 explains how to create.1 Sourcefire 3D System Administrator Guide 186 .9. The figure below shows the Defense Center version of the page. or interface set type. Using Detection Engine Groups on page 197 explains how to create and use detection engine groups. To list the available detection engines: Access: Admin Select Operations > Configuration > Detection Engines > Detection Engines. policy. edit. Using Interface Sets on page 207 describes how to create interface sets and how to use them with detection engines. • • • • • • • Understanding Detection Engines Requires: DC or 3D Sensor A detection engine is the mechanism on a 3D Sensor that is responsible for analyzing the traffic on the network segment where the sensor is connected. including some of the limitations based on the sensor model. sensor. You can sort the available detection engines by group.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 The following sections describe the detection engines and interface set features and how you can use them in your Sourcefire 3D System deployment: • Understanding Detection Engines on page 186 explains detection engines in more detail. Using Variables within Detection Engines on page 199 explains how to use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure. This section also describes how default detection engines are configured. Inline Fail Open Interface Set Commands on page 225 explains how to force an interface set in and out of bypass mode when using an inline fiber fail open interface set.

although a sensing interface can belong to only one interface set at a time. but the interface options available to you depend on the type of sensor and the capabilities of its sensing interfaces. The Sourcefire 3D System supports three types of interface sets. RNA. (The exception is on 3D9900s. 3D Sensors can support three types of detection engines: IPS.1 Sourcefire 3D System Administrator Guide 187 . see Using PEP to Manage Traffic in the Analyst Guide.9. A detection engine has two main components: • • an interface set. and RUA. which is a portion of the sensor’s computing resources For information about detection engines and detection resources. Note that you must use paired fail-open interfaces on the sensor’s network interface cards for an inline with fail open interface set. see Understanding Detection Resources and 3D Sensor Models on page 189 PEP Policy Only 3D9900 sensors provide the PEP feature. and Interface Set Depending on which components are licensed on the sensor. Note that you can use any two of the non-fail-open interfaces on the sensor’s network interface cards as part of an inline interface set. Inline with Fail Open Version 4. Set Type An interface set refers to a grouping of one or more sensing interfaces on a sensor. For more information on the PEP feature. which can include one or more sensing interfaces a detection resource. Use an inline interface set if you deployed the sensor inline on your network and the sensing interfaces do not support automatic fail-open capabilities.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Detection Engine Type. The three interface types are described in the Interface Set Types table. Resources. where pairs are pre-determined). Interface Set Types Type Passive Inline Description Use a passive interface set if you deployed the sensor out of band from the flow of network traffic. Use an inline with fail open interface set if you deployed the sensor inline on your network and the sensing interfaces do support automatic fail-open capabilities.

You can determine what the name and state of IPS and RNA policies from the following information in the policy column: • If you change an IPS and RNA policy and have not applied it to the detection engine since the change. you must either configure an IPS detection engine that uses that interface set.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 You can use RNA or RUA to monitor the traffic that passes through any of the three types of interface sets. then the icon has an exclamation point and the name is italicized. or configure the interface set in tap mode. See Using Interface Sets on page 207 for more information about creating and editing interface sets.1 Sourcefire 3D System Administrator Guide 188 .9 you have the advantage of the following listed features. or RNA. Policy 3D Sensors have different capabilities and limitations depending on whether you licensed IPS. as well as apply an intrusion policy to that detection engine. For more information see Viewing an Intrusion Policy Report in the Analyst Guide. TIP! After you upgrade your sensor to version 4. • You can click the name of an IPS policy to see details about the running policy. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts.9. RUA. if you plan to use RNA to monitor either an inline or inline with fail open interface set. Otherwise. the RNA detection engine monitoring that interface set will not see any traffic. If you are monitoring the same inline interface set with both IPS and RNA or RUA. Neither RNA nor RUA are supported on the 3D9800 sensor. IMPORTANT! On a 3D3800 or 3D5800 sensor. and the IPS detection engine fails for any reason. Version 4.

9. or delete variables associated with a detection engine’s IPS or RNA policy. if you plan to use the 3D3500 sensor in inline mode. • Sensor The sensor column provides the name of the sensor where the policy is applied. It also provides the following capabilities: • If you want to edit or delete a detection engine. For example. the Available Detection Engines page does not indicate that the filtered or base intrusion policy is deleted. If you want to list. it has a predefined detection engine that you can choose to modify to meet your needs. click the delete icon ( ) next to the intrusion policy name. click Reapply All.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 • If there is a network or VLAN filter applied to the IPS policy. edit. If you want to reapply all policies for the detection engine. use one detection resource per application per core on your appliance. If you hover above the name you can view the network or VLAN range of the filter. The delete icon only appears next to the base policy when there are no network or VLAN filters applied. click Variables. As a best practice. See Understanding Default Detection Engines for more information. If you want to remove the currently applied IPS policy from the detection engine. IMPORTANT! Initially. Select Monitor > Task Status to track the progress of the deletion process. you could assign two detection resources to your detection engine to allow processing of more events per second. add. See Using Variables within Detection Engines on page 199 for more information. Understanding Detection Resources and 3D Sensor Models Requires: DC or 3D Sensor 3D Sensors with IPS can use multiple detection resources per detection engine. • • For more information see Understanding Detection Resources and 3D Sensor Models on page 189 When you configure a new sensor. Different sensor models have different Version 4. If you want to remove the currently applied filter from the IPS policy.1 Sourcefire 3D System Administrator Guide 189 . you can click More or the down icon ( ) and view the type (Net for network or VLAN for virtual LAN) filter. click Edit or Delete next to its sensor name. which takes approximately 30 seconds. See Editing a Detection Engine on page 194 and Deleting a Detection Engine on page 197 for more information. which allows you to use more computing resources when network traffic is high. then OK to confirm. reset. click the delete icon ( ) next to the filter name.

RNA and RUA.1 Sourcefire 3D System Administrator Guide 190 . It also indicates the maximum number of detection resources you can assign a single detection engine. can be any type Maximum of two. The Maximum column indicates the total number of detection resources available on the sensor. • The Optimal column indicates the per-sensor total number of detection resources you should use if you want to maximize the performance of the sensor.9. • • Detection Resources by Model Model 3D500 3D1000 3D2000 3D2100 3D2500 3D3000 3D3500 3D3800 3D4500 3D5800 3D6500 3D9800 3D9900 Optimal per Sensor 1 1 1 2 2 2 2 2 4 6 8 12 7 Maximum per Sensor 2 2 2 3 4 4 6 2 8 6 12 12 12 Combination Restrictions Maximum of one IPS and either one RNA or one RUA Maximum of two. can be any type No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions No restrictions Version 4.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 numbers of detection resources available as shown in the Detection Resources by Model table. 3D Sensors can run combinations of IPS. The Combination Restrictions column indicates the permitted combinations of detection resources that you can allocate to detection engines on the same sensor.

current Crossbeam System hardware and software support. As with other 3D Sensors. After initial installation can modify interface sets and detection engines.1 Sourcefire 3D System Administrator Guide 191 .Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Detection Resources by Model (Continued) Model Virtual 3D Sensor Crossbeambased software sensors Optimal per Sensor 3 Maximum per Sensor 3 Combination Restrictions No restrictions Refer to Crossbeam-based Software Sensor Considerations on page 191 General Recommendations with Two or More Detection Resources For improved 3D Sensor performance on sensors with optimal detection resources of two or greater. Understanding Default Detection Engines Requires: DC or 3D Sensor When you install a new 3D Sensor. you can use initial interface sets and default detection engines to quickly begin evaluating network traffic. Crossbeam-based Software Sensor Considerations Depending upon the capabilities of your X-Series and the products you are licensed to use. you can reduce latency by distributing your network traffic across all available interfaces on the sensor. Version 4. Refer to the Sourcefire 3D Sensor Software for X-Series Installation Guide for information on deployment scenarios. you have several deployment options for 3D Sensor Software. The number of detection resource depends on the Crossbeam System hardware. then distribute the detection engines and detection resources across all operative interfaces on the sensor. the maximum number of detection engines that you can create is equal to the number of available detection resources. and detection resources available on Crossbeam System hardware. Consider how your network is configured and how you want to deploy the Sourcefire 3D System within it.9.

on some of the older models. for example. Passive that builds a single passive interface set for all 3D Sensor interfaces. Choose from these initial interface sets based on how you deployed the sensor. the default that builds paired fail-open interface sets on all 3D Sensor interfaces. that is automatically included in the default detection engine. a 3D2000 Sensor uses eth1 and eth2 as one inline fail-open interface set and it uses eth3 and eth4 as another inline fail-open interface set. Version 4. Second On-Board Interface Some Sourcefire sensors have a second on-board interface. Select Passive Mode if the sensing interfaces are not cabled inline. Default Detection Engines Default detection engines are configured with the optimal (rather than maximum) number of detection resources as described in the Detection Resources by Model table on page 190. If you want to change either the number of detection resources or the interfaces assigned to the default detection engine. the second on-board interface cannot support the same high-performance standards as the interfaces on the network interface cards. IMPORTANT! For the 3D3000 on the IBM xSeries 346 appliance. Depending on the 3D Sensor. the detection engine may not provide optimum performance.Using Detection Engines and Interface Sets Understanding Detection Engines Chapter 6 Initial Interface Sets The initial interface sets for 3D Sensors are: • • Inline with Fail-Open. Select Inline with Fail-Open Mode if you cabled the sensing interfaces inline on your network as an IPS. However. With this configuration. less the management interface. see Editing a Detection Engine on page 194. note that the default detection engine does not include the second on-board interface.1 Sourcefire 3D System Administrator Guide 192 . less the management interface. Sourcefire recommends that you remove the second on-board interface from the detection engine for improved performance. usually near the management interface. If you modify the default detection engine to include it. typically you pair adjacent interfaces. you can connect any of the non-management interfaces to your network and apply the appropriate policy to the detection engine and begin analyzing your network. and you have deployed it in a high-bandwidth environment where the traffic load is likely to reach the design limits of the appliance. If your appliance has one of these extra interfaces.9.

Select Operations > Configuration > Detection Engines > Detection Engines. edit. The figure below shows the Defense Center version of the page.9. and delete detection engines. 2. when they are available on your 3D Sensor. punctuation. The Detection Engines page appears. You can use interface sets that include multiple inline interface pairs. 3.1 Sourcefire 3D System Administrator Guide 193 . You can use alphanumeric characters. and spaces. enter a name and description for the new detection engine. Version 4. To create a detection engine: Access: Admin 1.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 Managing Detection Engines Requires: DC/MDC or 3D Sensor See Understanding Detection Engines on page 186 and Using Interface Sets on page 207 for more information about the capabilities of detection engines and the interface sets they depend on. Click Create Detection Engine. The Create Detection Engine page appears. The following sections explain how to create. • • • Creating a Detection Engine on page 193 Editing a Detection Engine on page 194 Deleting a Detection Engine on page 197 Creating a Detection Engine Requires: DC or 3D Sensor You can create a detection engine if you have an available interface set and at least one available detection resource. In the Name and Description fields.

or 3D3800.9. 8. IMPORTANT! For most 3D Sensors with inline interface sets. a software bridge is automatically set up to transport packets when the sensor restarts. Although some packets are transmitted without inspection during this time. the detection engine does not restart and interrupt traffic inspection when the policy is applied. RNA. you can only use one of the two detection resources for IPS.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 4. 5. Editing a Detection Engine Requires: DC or 3D Sensor In some circumstances. See Using Detection Engine Groups on page 197 for information on creating and modifying detection engine groups. which can cause a short pause in processing. 9. The second detection resource is available only if you want to create a second detection engine for RNA or RUA. 6. you can select Inspect Traffic During Policy Apply. or RUA. no packets are lost. However. if this option is employed. See the Detection Resources by Model table on page 190 for more information. IPS. if you are creating an IPS detection engine and if you are using a 3D Sensor other than a 3D500. IMPORTANT! On the 3D500. 3D1000. Optionally.1 Sourcefire 3D System Administrator Guide 194 . add the detection engine to an existing detection engine group. Select the type of detection engine that you want to create from the Type drop-down list. Click Save. See Using Interface Sets on page 207 for information about creating and modifying interface sets. 7. The detection engine is created. TIP! This option may degrade performance when you apply a policy and may result in longer policy-apply periods. Select the interface set that you want to assign to this detection engine. The following sections describe some of the cases where a detection engines is affected by changes to the detection engines and interface sets: Version 4. Select the number of detection resources for this detection engine. editing an interface set or detection engine can cause the detection engines on the sensor to restart. Optionally.

the interface set type. IMPORTANT! If you have an 3Dx800 health policy applied to a 3D9800 sensor when you change the number of detection resources. If you create an interface set. When you create a detection engine. nothing is restarted. If you change the number of detection resources allocated to a detection engine. or interface set type. If you change the name or description of an interface set or detection engine.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 3Dx800 Sensors • If you change the number of network interfaces.9. If you change a detection engine’s interface set. A restart occurs only when you assign a detection engine to the interface set. nothing is restarted. all the detection engines on the sensor are restarted because the total number of allocated resources has changed. all detection engines assigned to that interface set are restarted. If you delete a detection engine or interface set. If you change the number of detection resources. all the detection engines using that interface set are restarted. If you change the detection engine type for a detection engine. If you create an interface set. or the detection engine type. nothing is restarted. • • • Version 4. If you change the name or description of an interface set or detection engine. If you change an interface set’s transparent mode setting. only that detection engine is restarted (although other CPUs may be restarted to rebalance the processing load). • • • • If you create a detection engine. that detection engine is restarted. all detection engines on the sensor are restarted. all the detection engines on the sensor are restarted. Contact Sourcefire Support for information about how to clear those hardware alarms. it will generate hardware alarms. all detection engines on the sensor are restarted. only that detection engine is started (although other CPUs may be restarted to rebalance the processing load). all the detection engines on the sensor are restarted. which interface set is used. nothing is restarted. If you delete a detection engine or interface set. or the setting for tap mode or transparent mode for an interface set. all detection engines on the sensor are restarted. • Other Sensors • • • • • • If you change which network interfaces are used by an interface set.1 Sourcefire 3D System Administrator Guide 195 .

For more information. In the case of an IPS detection engine you can also select if traffic is inspected while a policy is being applied. To edit an existing detection engine: Access: Admin 1.9. Version 4. Click Edit next to the detection engine you want to modify. You cannot modify the detection engine type. If you need to change the detection engine type. Click Save. description. see the Sourcefire 3D Sensor Software for X-Series Installation Guide.Using Detection Engines and Interface Sets Managing Detection Engines Chapter 6 Make sure you plan these actions for times when they will have the least impact on your deployment. You can modify the name. and number of detection resources for the detection engine. TIP! The Inspect Traffic During Policy Apply option is not available on 3D500. Your changes are saved. you must delete the detection engine and create a new one. group. The Detection Engines page appears. or 3D3800 sensors. 3D1000. Select Operations > Configuration > Detection Engines > Detection Engines. TIP! On your 3D Sensor Software for Crossbeam Systems X-Series. you may want to remove any affected VAPs from the load-balanced list until the associated detection engines restart. The Edit Detection Engine page appears.1 Sourcefire 3D System Administrator Guide 196 . then reinstate the VAPs. 3. 2.

The Detection Engines page appears. 3. see Modifying a Rule in the Analyst Guide. Select Operations > Configuration > Detection Engines > Detection Engines. At the prompt. a record of the detection engine is retained so that events generated by that detection engine are viewable. See the following sections for more information: • • • Creating Detection Engine Groups on page 197 Editing Detection Engine Groups on page 198 Deleting Detection Engine Groups on page 199 Creating Detection Engine Groups Requires: DC/MDC or 3D Sensor Access: Admin The following procedure explains how to create a detection engine group. The detection engine is deleted. To create a detection engine group: 1. Also. Click Delete next to the detection engine you want to delete.Using Detection Engines and Interface Sets Using Detection Engine Groups Chapter 6 Deleting a Detection Engine Requires: DC or 3D Sensor Use the following procedure to delete a detection engine. Select Operations > Configuration > Detection Engines > Detection Engines. These groups make it easier to apply policies to detection engines that have similar purposes. Version 4. To delete a detection engine: Access: Admin 1. you should first delete (or modify) the constraint in all rules in which it is used. you should not delete a detection engine that is used as a constraint in one or more compliance rules. The Detection Engines page appears. confirm that you want to delete the detection engine. however.1 Sourcefire 3D System Administrator Guide 197 . 2. WARNING! Do not delete a detection engine that is in use. For information on modifying compliance rules.9. Using Detection Engine Groups Requires: DC/MDC or 3D Sensor You can use detection engine groups to combine similar detection engines.

4. The Detection Engine Group Edit page appears. Click Save. Type a name for the detection engine group in the Group Name field. You must create a detection engine group before you can edit it. 2. To edit a detection engine group: Access: Admin 1. Select available detections engines and to move them to the detection engine group with the arrow buttons. The Detection Engine page appears again. on the Edit Detection Engine page. Editing Detection Engine Groups Requires: DC/MDC or 3D Sensor The following procedure explains how to edit a detection engine group.Using Detection Engines and Interface Sets Using Detection Engine Groups Chapter 6 2. See Creating Detection Engine Groups on page 197. The Available Detection Engines page appears. You can add detection engines to this group by clicking Edit next to a detection engine name and. Select Operations > Configuration > Detection Engines > Detection Engines. The Detection Engines page appears. 4. Version 4. adding the detection engine to the group and clicking Update.9. You can also move detection engines out of the detection engine group. The Create Detection Engine Group page appears. Click Save to add the selected detection engines to the detection engine group.1 Sourcefire 3D System Administrator Guide 198 . Click Edit for the detection engine group. 3. 3. Click Create Detection Engine Group.

However.90. The detection engine group is deleted. 2. Click Delete next to the name of the detection engine group. The Detection Engines page appears. they are not deleted. which are specific to the policy in which they are created.10. IPS can use the value of the detection engine-specific variable in rules you enable in your policy to monitor network traffic and generate events.0/24) and another monitors a different class (for example. see Creating New Policy-Specific Variables in the Analyst Guide.10. Using Variables within Detection Engines Requires: IPS or DC/MDC + IPS A system default variable sets a variable value on your Sourcefire 3D Sensor or Defense Center that IPS uses by default unless it is overridden by a policy-specific or detection engine-specific value for the same variable. For information on policy-specific variables.10. For example. hosts in your network’s DMZ in the range 10.0/24 In the detection engine named DE_ACCT: HOME_NET = 10. 10.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 Deleting Detection Engine Groups Requires: DC/MDC or 3D Sensor When you delete a detection engine group.30. You can define HOME_NET in your system default variable to encompass your internal address range (for example. In the system default variable used in the intrusion policy: HOME_NET = 10. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure.90.9. you can use the system default Version 4. if you have created your detection engines so that one detection engine monitors one class of hosts (in this example. To delete a detection engine group: Access: Admin 1.10.0/24 If you later create another detection engine that monitors the rest of your network. You can associate a system default variable with a specific detection engine and give the resulting detection engine-specific variable an explicit value for that detection engine. the intrusion rules in an intrusion policy take advantage of certain system default variables such as HOME_NET and EXTERNAL_NET to look for exploits that originate outside your network and are targeted against hosts within your network.1 Sourcefire 3D System Administrator Guide 199 . any detection engines in the group are automatically ungrouped.10. which includes a mixed address space.0. Select Operations > Configuration > Detection Engines > Detection Engines.0/24).0/16 In the detection engine named DE_DMZ: HOME_NET = 10.30.0/16).10.0. When you apply an intrusion policy to that detection engine. hosts in your accounting department in the address range 10.

you can modify the variable in the intrusion policies and detection engines where it is added automatically to give it a specific definition. If you disable a variable defined on the Variable List page by resetting the variable. see Creating New Variables in the Analyst Guide. Creating a detection engine-specific variable from the detection engine Variable List page also creates a corresponding system default variable with the value set to any. You can also create new variables for use only within the context of the detection engine.1 Sourcefire 3D System Administrator Guide 200 . a detection engine-specific variable value takes precedence over a policy-specific or system default value for the same variable. see the following sections: • • • • • Assigning Values to System Default Variables in Detection Engines on page 200 Creating New Variables for Detection Engines on page 202 Deleting and Resetting Variables on page 203 Configuring Custom Variables in Detection Engines on page 204 Using Portscan-Only Detection Engines on page 205 Assigning Values to System Default Variables in Detection Engines Requires: IPS or DC/MDC + IPS You can assign detection engine-specific values to system default variables. Variables use the same syntax and must follow the same guidelines regardless of whether you create or define them from within intrusion policies or from the detection engine Variable List page. You can view the explicit detection engine-specific value you configured in the list of variables for the detection engine within each policy. You can create detection engine-specific variables and set detection engine-specific values for system default variables within an intrusion policy or from the detection engine Variable List page. or on the detection engine Variable List page for the detection engine. Version 4. which means that the value specified in the policy will be used when you apply the policy. When they exist. IMPORTANT! You cannot use variables with RNA detection engines. See Creating New Variables in the Analyst Guide and Modifying Variables in the Analyst Guide for more information.9. You can view the corresponding new system default variable in the list of system default variables within each policy. Configuration details in this section relate to the detection engine Variable List page. For more information. For an explanation see Using Variables within Detection Engines on page 199. the definition reverts to the definition in the intrusion policy the next time you apply the policy. Optionally. and on the Variable list page for all other detection engines where it is listed with the value set to Policy Defined. For configuration details related to setting detection engine-specific variables within an intrusion policy.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 variable value rather than creating another detection engine-specific value for HOME_NET.

Version 4. The value for each of the variables defaults to the value within the intrusion policy that is applied to the detection engine. as described in Applying an Intrusion Policy in the Analyst Guide. 4.9. Click Edit next to the variable you want to define.1 Sourcefire 3D System Administrator Guide 201 . Enter a value for the variable and click Save. The Variable Binding page appears. The Variable List page appears again and shows the new value for the variable.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 To assign a detection engine-specific value to a system default variable: Access: Admin 1. 3. 2. Select Operations > Configuration > Detection Engines > Detection Engines. Click Variables next to the detection engine where you want to define a variable value. The variable takes effect the next time you apply an intrusion policy to the detection engine. See Creating New Variables in the Analyst Guide for information about variable syntax. The Variable List page appears. The Detection Engines page appears.

2. Click Add Variable. From the Variable Type drop-down list.9. select IP Port. To create a new variable for a detection engine: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 202 . Select Operations > Configuration > Detection Engines > Detection Engines. The Detection Engines page appears. • • • See Defining IP Addresses in Variables and Rules in the Analyst Guide for more information if you are defining a IP address-based variable. enter a name for the variable. Version 4. .Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 Creating New Variables for Detection Engines Requires: IPS or DC/MDC + IPS When you create an intrusion policy. or Custom. 4. The Variable List page appears. For an explanation see Using Variables within Detection Engines on page 199. 5. In the Variable Name field. See Defining Ports in Variables and Rules in the Analyst Guide for more information if you are defining a port-based variable. you can associate detection engine-specific variable definitions with the policy. 3. See Understanding Custom Variables in the Analyst Guide if you are defining a special-purpose custom variable with one of the reserved variable names described in the Custom Variables table in the Analyst Guide. The Variable page appears. Click Variables next to the detection engine where you want to define a variable value.

Select Operations > Configuration > Detection Engines > Detection Engines. The variable takes effect the next time you apply an intrusion policy to the detection engine. To delete or reset variables on a detection engine: Access: Admin 1. The Detection Engines page appears. The Variable List page appears again and shows the new variable and its value. meaning that the value specified in the policy will be used when you apply the policy.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 6. See Creating New Variables in the Analyst Guide for information about the syntax for variables. as described in Applying an Intrusion Policy in the Analyst Guide. It is listed in the variable list for the detection engine in all intrusion policies with the explicitly set value. IMPORTANT! Each new detection engine variable adds a system variable with a value of any that is accessible in all your intrusion policies. Version 4. You can also delete variables that you created within the context of the detection engine. but only if they are not used in any active or inactive rule within the system. the value any will be used. You cannot delete predefined system variables within an intrusion policy.1 Sourcefire 3D System Administrator Guide 203 . enter a value for the variable and click Save. Creating the new detection engine variable also lists the description Policy Defined for all other IPS detection engines on the Variable List page.9. You can delete predefined system variables on the detection engine Variable List page. The variable is created and is accessible to all policies as a system default variable. and listed for all other detection engines on the Variable List page with a value of Policy Defined. In any intrusion policy that you apply to a different detection engine and do not explicitly set a policy-defined or detection engine-specific variable to override the value of the system variable. Deleting and Resetting Variables Requires: IPS or DC/MDC + IPS You can reset the value of a variable on the Variable List page and the variable reverts to the value defined in the intrusion policy the next time you apply the intrusion policy to the detection engine. In the Value field.

• To delete a locally created variable. For more information. The variable is reset and Policy Defined appears in the Value column. The Variable List page appears. or by creating a variable using a specific reserved name. Version 4.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 2. The variable is deleted from the detection engine the next time you apply an intrusion policy to the detection engine. Click Variables next to the detection engine where you want to delete or reset a variable value.1 Sourcefire 3D System Administrator Guide 204 . Configuring Custom Variables in Detection Engines Requires: IPS or DC/MDC + IPS Custom variables allow you to configure special IPS features that you cannot otherwise configure via the web interface. click Reset next to the name of the variable. You create a detection engine-specific custom variable by setting an explicit value for a reserved predefined system variable. click Delete next to the name of the variable. see Understanding Custom Variables in the Analyst Guide. You can add a new USER_CONF detection engine variable using the reserved name USER_CONF . You then define the variable value with a set of instructions appropriate to the function the variable provides. You can set an explicit detection engine value for the predefined SNORT_BPF custom system variable.9. 3. You have two options: • To disable the variable value defined in the IPS detection engine and revert to the variable value defined in the policy.

see Assigning Values to System Default Variables in Detection Engines on page 200. Remember that the portscan-only detection engine can use only one detection resource. Internal logic on the sensor ensures that packets belonging to the same session are directed to the same resource for analysis. Multiple detection engines will use this interface set. Depending on the traffic mix on your network. Using the Defense Center’s web interface. However. a portion of the traffic that the 3D Sensor sees is directed to each detection resource for processing. Using Portscan-Only Detection Engines Requires: IPS or DC/MDC + IPS If you configure a sensor to use multiple detection resources within a single IPS detection engine. IMPORTANT! A portscan-only intrusion policy is able to process up to three times more traffic than a more complex intrusion policy because it uses fewer CPU resources. Create an IPS portscan-only detection engine and assign one detection resource to it. the sensor can process more packets with greater efficiency. In this way. Create another IPS detection engine that uses up to the remaining number of detection resources and the interface set that you created in step 1. The interface set can be passive. you can create a portscan-only intrusion policy and apply it to a portscan-only detection engine on the sensor. To overcome this issue.9.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 To configure the SNORT_BPF custom variable for a detection engine: Access: P&R Admin/Admin To set an explicit detection engine-specific value for SNORT_BPF using the existing system default variable. Sourcefire recommends that you monitor the performance of your sensor to make sure that the portscan-only detection engine is able to keep up with the multi-resource detection engine. The following steps outline the process you can use to configure your sensor to detect portscans in addition to other exploits against your network assets. Make sure you use the interface set that you created in step 1. create an interface set that includes the network interfaces you want to use on the sensor.1 Sourcefire 3D System Administrator Guide 205 . 1. which is a requirement for the portscan preprocessor. 3. One downside to using multiple detection resources is that no single resource sees all the traffic on a network segment. or inline with fail open depending on how your sensor is deployed. you may need to adjust the number of resources in the multi-resource detection engine. Version 4. 2. Engines on page 202. To configure the USER_CONF custom variable for a detection engine: Access: P&R Admin/Admin To create USER_CONF as a new detection engine-specific variable using the reserved name USER_CONF see Creating New Variables for Detection . inline.

Review the resulting intrusion events to ensure that you are receiving the events you expect. or Rule Processing Configuration. you must enable rules on the Rules page with generator ID (GID) 122 for enabled portscan types for the portscan detector to generate portscan events. Create and apply an intrusion policy for the multi-resource detection engine. and Applying an Intrusion Policy in the Analyst Guide for more information): • Select the No Rules Active Base Policy and make sure the Protection Mode is Passive. make sure you disable portscan detection in this policy. Enable Portscan Detection and configure it for your network environment. 5. The policy should inherit or be set to the following settings in the layer in your intrusion policy where you enable portscan detection (See Creating an Intrusion Policy in the Analyst Guide. See Selecting the Base Policy in the Analyst Guide for more information. See Detecting Portscans in the Analyst Guide for more information. Version 4. Make sure you match the type of intrusion policy to the type of interface set that you created in step 1. Make sure portscan rules are enabled for the types of portscans you configure. Ensure that the DCE/RPC Configuration preprocessor. Working with Layers. • • • • • • IMPORTANT! Note that when portscan detection is enabled.1 Sourcefire 3D System Administrator Guide 206 . items listed under Performance Statistics. Also. the SMTP Configuration preprocessor (under Application Layer Preprocessors). Create and apply an intrusion policy to the portscan-only detection engine.9. the HTTP Configuration preprocessor.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 4. Enable IP Defragmentation (under Transport/Network Layer Preprocessors) and make sure it is configured for your environment (using the Hosts option) See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. You do not need to set up variables for this policy. Note that all rules are disabled on the Rules page. You should not change the default settings for Checksum Verification or Packet Decoding (under Transport/Network Layer Preprocessors). and Back Orifice Detection (under Specific Threat Detection) are disabled. 6. Ensure that OPSEC Configuration (under External Responses) is disabled. See the Portscan Detection SIDs (GID:122) table in the Analyst Guide for more information.

Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Using Interface Sets Requires: DC or 3D Sensor An interface set is a collection of one or more sensing interfaces on your appliance. you can set up any of your 3D Sensor interfaces in passive. You can also set interfaces on most sensors in transparent inline mode. or PEP policy. Sensors with Gigabit Ethernet interfaces can employ jumbo frames. • With the exception of the Virtual 3D Sensor. inline. Some installations require that the link state be propagated and most sensor interfaces provide that option. You can sort the available interface sets by group. Only 3D9900 sensors provide the PEP feature.1 Sourcefire 3D System Administrator Guide 207 . or inline with fail-open mode. 3D Sensors deployed in networks that are highly sensitive to latency can use the automatic application bypass option. set type. To list the available interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets. • • • • • • • Version 4. The Virtual 3D Sensor supports only passive mode operation. sensor. For more information on the PEP feature. On selected sensors you can set interfaces to tap mode. see Using PEP to Manage Traffic in the Analyst Guide. Only 3D9900 sensors provide a fail-safe option that works with inline interface sets.9. See the following sections for more information about interface sets: • • • • • • • Understanding Interface Set Configuration Options on page 207 Creating an Interface Set on page 213 Creating an Inline Interface Set on page 216 Editing an Interface Set on page 221 Deleting an Interface Set on page 223 Inline Fail Open Interface Set Commands on page 225 Using Clustered 3D Sensors on page 227 Understanding Interface Set Configuration Options Requires: DC or 3D Sensor There are a number of configuration variables to consider when you configure interface sets.

Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 See the following table for a list of 3D Sensors and each of their applicable interfaces features.9.1 Sourcefire 3D System Administrator Guide 208 . Supported Features by 3D Sensor Model 3D Sensor Model Virtual 3D Sensor 3D500 3D1000 3D2000 3D2100 3D2500 3D3000 3D3500 3D3800 3D4500 3D5800 3D6500 3D9800 3D9900 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Transparent Inline Mode Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Link State Propagation Mode Tap Mode Jumbo Frames Automatic Application Bypass Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Enable Fail-safe PEP See the following sections for more information: • • • • • • • Types of Interface Sets on page 209 Transparent Inline Mode on page 209 Tap Mode on page 210 Link State Propagation Mode on page 211 Jumbo Frames on page 212 Automatic Application Bypass on page 212 Enabling Fail-Safe on page 213 Version 4.

Note that interface pairs on the same fiber-based NIM will act as fail open interfaces even if you assign them to an inline interface set. The interfaces do not have to be on the same network cards. one for an IPS and the other for RNA. an inline interface set on a 3D3800 or 3D5800 sensor can include up to four interface pairs. the appliance’s performance could be degraded. and an inline interface set on a 3D9800 sensor can include up to the total number of interface pairs on the sensor. and an inline with fail open interface set on a 3D9800 sensor can include up to the total number of interface pairs on the sensor. That is. an inline with fail open interface set on a 3D3800 or 3D5800 sensor can include up to four interface pairs. which only supports a single IPS detection engine. if the power fails or the Snort process halts. Version 4. For example. This allows the sensor to act as a “bump in the wire” and means that the sensor forwards all the network traffic it sees regardless of its source and destination. network traffic continues to flow through the sensor as it would for an inline with fail open interface set. then apply different policies to the detection engines. However. except on the 3D9800 sensor. If you choose the Inline or Inline with Fail Open option. • Inline For most sensors. or in addition to. an inline interface set can include any two interfaces. an inline with fail open interface set must include exactly one interface pair. You can set up multiple detection engines to use a single interface set. you could create a single passive interface set and create two detection engines. you can choose one of three types: • Passive A passive interface set can encompass any number of the available sensing interfaces on a sensor.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Types of Interface Sets When you create an interface set. interfaces on the network cards). but you should avoid using an on-board interface. except for the 3D500 and the Virtual 3D Sensor. It is not available on the 3D500 and available but not a default configuration on the Virtual 3D Sensor. • Inline with Fail Open For most sensors. Transparent Inline Mode Transparent inline mode is a feature for inline interface sets and is not available for Passive interface sets.1 Sourcefire 3D System Administrator Guide 209 . the Transparent Inline Mode option is enabled by default. IMPORTANT! If you include an on-board sensing interface (instead of.9. However.

For example. consider the following diagram. the sensor learns which hosts are on which side of the inline interface. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. Over time. Tap Mode Tap mode is available for the 3D3800. Only traffic between Host A and Host C or between Host B to Host C is allowed to pass. if your sensor includes a detection engine with an inline interface set) and the Transparent Inline Mode option is selected. With tap mode. but instead of the packet flow passing through the sensor.9. If your sensor is deployed inline (or more precisely. rules that you set to Drop and rules that use the replace keyword do not affect the packet stream.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 If you disable this option. However. If the sensor is inline and you are not using transparent inline mode. and forwards packets accordingly. when the sensor sees traffic from Host A to Host B. Because you are working with copies of packets rather than the packets themselves. the sensor is deployed inline. Version 4.1 Sourcefire 3D System Administrator Guide 210 . 3Dx800 sensors run in transparent inline mode. a sensor acts as a bridge. it does not allow the traffic to pass through the interface to the side of the network with Host C. and on later versions of 3D9800 3D Sensor when you create an inline or inline with fail open interface set. it allows the traffic to pass through the interface even though Host A and Host B are on the same side of the sensor. Keep in mind that if you create an inline interface set but do not use transparent inline mode. and you cannot disable it. rules of these types do generate intrusion events when they are triggered. then if the sensor sees network traffic from Host A to Host B. 3D9900. a copy of each packet is sent to the sensor and the network traffic flow is undisturbed. 3D5800. you must be especially careful not to create loops in your network infrastructure.

or configure the interface set in tap mode. Version 4. you can set up the cabling between the sensor and the network as if the sensor were inline and analyze the kinds of intrusion events the sensor generates. see Removing Bypass Mode on Inline Fail Open Fiber Interfaces on page 225. IMPORTANT! Crossbeam-based software sensors and 3D9800 sensors do not support link state propagation. Link State Propagation Mode Link state propagation mode is a feature for interface sets in the inline fail-open mode so both pairs of an inline pair track state. if you plan to use RNA to monitor either an inline or inline with fail open interface set. IMPORTANT! On a 3D3800 or 3D5800 sensor. the link state of the other interface is changed automatically to match it. you can modify your intrusion policy and add the drop rules that best protect your network without impacting its efficiency. you can disable tap mode and begin dropping suspicious traffic without having to reconfigure the cabling between the sensor and the network. It is also available on 3D9900s in both the inline and inline fail-open mode. It is not available for passive interface sets. the RNA detection engine monitoring that interface set will not see any traffic. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts. Based on the results. other than those on 3D9900s must be in hardware bypass mode for link state propagation to function correctly.9. For more information about fiber interface sets and hardware bypass. the second interface automatically comes back up. When you are ready to deploy the sensor inline. Link state propagation mode automatically brings down the second interface in the interface pair when one of the interfaces in an inline interface set goes down. When the downed interface comes back up. if the link state of one interface changes. Otherwise. you must either configure an IPS detection engine that uses that interface set. too.1 Sourcefire 3D System Administrator Guide 211 . In other words. Link state propagation is available for both copper and fiber fail-open NIMs. For example. IMPORTANT! Fiber interface sets configured as inline fail-open. If you are monitoring the same inline interface set with both IPS and RNA or RUA. Neither RNA nor RUA are supported on the 3D9800 sensor. as well as apply an intrusion policy to that detection engine.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 There are benefits to using tap mode with sensors that are deployed inline. and the IPS detection engine fails for any reason.

a core file is automatically generated for potential troubleshooting by Sourcefire Support. The feature functions with both passive and inline interface sets. Jumbo Frames Jumbo frames are Ethernet frames with a frame size greater than the standard 1518 bytes. RNA. however. 3D Sensor that support jumbo frames include: • • • 3D6500 3D9800 (9018-byte jumbo frames are always accepted) 3D9900 Note that since the 3D9800 is set to always accept the maximum size frame.000 ms. If a detection engine is bypassed. Version 4. Typical maximum sized jumbo frames are 9018 bytes. If the application bypass triggers repeatedly. see Configuring Automatic Application Bypass Monitoring on page 502.1 Sourcefire 3D System Administrator Guide 212 . 3D Sensors generate a health monitoring alert. You can change the bypass threshold if the option is selected. The valid range is from 250 ms to 60.9. For more information on the health monitoring alert. it is most valuable in inline deployments. You can apply automatic application bypass on an interface set basis. The default setting is 750 milliseconds (ms). Most gigabit Ethernet network interface cards support jumbo frames to increase efficiency. WARNING! If a detection engine is bypassed. The automatic application bypass option is off by default. you do not need to set it in the Create Interface Set page.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Link state propagation is especially useful in resilient network environments where routers are configured to reroute traffic automatically around network devices that are in a failure state. Note also that frames larger than the configured maximum frame size are silently dropped by the sensor. see the Supported Features by 3D Sensor Model table on page 208. excessive numbers of core files can result in disk usage health alerts. Automatic Application Bypass The automatic application bypass feature allows you to balance packet processing delays with your network’s tolerance for packet latency. or RUA detection engine and allows packets to bypass the detection engine if the time is exceeded. set the maximum frame size for the interface using the Create Interface Set page. If your 3D Sensor and interface supports jumbo frames. To see a list of which 3D Sensors you can use Automatic Application Bypass Monitoring on. Automatic application bypass limits the time allowed to process packets through an IPS.

TIP! Some sensors do not support every interface set type. You can use alphanumeric characters and spaces. To create an interface set: Access: Admin 1. The Interface Sets page appears. from the Interface Set Type drop-down list. Creating an Interface Set Requires: DC or 3D Sensor An interface set is a collection of one or more sensing interfaces on your appliance.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 Enabling Fail-Safe The Create Interface Set page includes an additional option for 3D9900 sensors: the Enable Fail-Safe option. Passive. For more information. IMPORTANT! The procedure for creating an inline interface set for 3Dx800 sensors is slightly different. 3.9. Type a name and description for the new interface set in the Name and Description fields. Inline. see Using Interface Sets on page 207. traffic is allowed to bypass detection and continue through the sensor. The Enable Fail-Safe option is only available on inline interface configurations. 4. When you enable the Enable Fail-Safe option. or Inline with Fail Open. 2. 3D9900 sensors monitor internal traffic buffers and bypass detection engines if those buffers are full. Creating an Inline Interface Set. For information about their use. The Create Interface Set page appears. Version 4. Select Operations > Configuration > Detection Engines > Interface Sets. Click Create Interface Set. see the next section.1 Sourcefire 3D System Administrator Guide 213 . Select the type of interface you want to create.

Version 4. 9. you can select the Enable Fail-safe check box to enable traffic pass-though during application bypass. you can select a Bypass Threshold in milliseconds (ms). Optionally. then optionally.9. clear the Transparent Inline Mode check box to disable transparent mode. When the option selected. however. 7. select an existing interface set group or select Create New Group to create a new interface set group. Optionally.000 ms. Optionally. and if you are configuring an inline interface set on a 3D9900. You can.1 Sourcefire 3D System Administrator Guide 214 . The default setting is 750 ms and the valid range is from 250 ms to 60. select Link State Propagation Mode.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 5. if you selected the Inline or Inline with Fail Open option. 8. set jumbo frame options on the Crossbeam CLI. See Using Interface Set Groups on page 223 for more information. select Automatic Application Bypass if your network is sensitive to latency. Automatic Application Bypass is most useful in inline applications. If you selected either the Inline or Inline with Fail Open option and you are not configuring a Crossbeam-based software sensor. 6. This option is especially useful if the routers on your network are able to re-route traffic around a network device that is down. IMPORTANT! Link state propagation and automatic application bypass are not supported on Sourcefire 3D Sensor Software for X-Series platforms. Optionally.

You can also select the ungrouped sensors. including a list of ungrouped sensors. a list of sensor groups appears. The following shows a 3D9900 interface set. Defense Center Only Select one of the sensors from the list. inclusive. You can set any jumbo frame size between 1518 and 9018 bytes. On the Defense Center only. A list of network interfaces on the sensor appears. and if you are configuring an interface set on a 3D6500 or 3D9900 type a maximum frame size for your IP traffic in the Maximum Frame Size field. 12. 11. Defense Center Only Select the sensor group containing the sensors where you want to create the interface set. Optionally. A list of sensors appears. Version 4.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10.9.1 Sourcefire 3D System Administrator Guide 215 .

e0 corresponds to the leftmost interface on the network interface module (NIM) in I/O Slot 0 on the back of your appliance. For example. For 3Dx800 sensors.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 13. you can include all of the available interfaces in a passive interface set. This is the default behavior during 3D Sensor installations. make sure you reapply intrusion policies to the IPS detection engines on the affected sensor. the names that appear in the Available Interfaces list correspond to the slot number and interface location. Using one interface set that includes all available inline interface pairs.9. and so on). Select the interfaces that you want to add from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list. Remember to reconnect the network cable when you are finished. 14. your sensor may not provide optimum performance. eth2. • • For more information. you can apply a single policy and rapidly complete your initial Version 4. For example. see the Installation Guide for your sensor or sensor software. Creating an Inline Interface Set Requires: DC or 3D Sensor You can add multiple interface pairs to an inline interface set on 3D Sensors and Crossbeam-based software sensors. You can use the Shift and Ctrl keys to select multiple interfaces at once. s0. but inline interface sets must contain exactly two interfaces (except on 3Dx800 sensors). Determining which interface name corresponds with a physical interface on your sensor depends on the model: • For most 3D Sensors. Different types of interface sets have different requirements. IMPORTANT! If you select an on-board interface rather than an interface on a network card. TIP! After you create an interface set. Click Save. Inline with fail open interface sets must contain one pair of interfaces from the same fail-open network card. the names that appear in the Available Interfaces list correspond to the device names you assigned to the circuits you created on the X-Series.1 Sourcefire 3D System Administrator Guide 216 . A message appears on the console indicating the name of the interface (eth1. log into the console and disconnect the network cable from the interface. For 3D Sensor Software for Crossbeam Systems X-Series. The interface set is created.

Your network may be set up to route traffic between a host on your network and external hosts through different interface pairs depending on whether the traffic is inbound or outbound. you can refine policies for specific connected network segments and their requirements. the sensor might not correctly analyze your network traffic because a detection engine might see only half of the traffic. as shown in the following graphic.9. Version 4.1 Sourcefire 3D System Administrator Guide 217 .Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3D Sensor deployment. If you include only one interface pair in an interface set. in many cases you can improve performance by modifying the interface set to include only the inline interface pairs your network requires. You can also use multiple interface pairs when your network employs asynchronous routing. Later. TIP! Although the default interface set on 3D Sensors includes all the available inline interface pairs.

Type a name and description for the new interface set in the Name and Description fields. 4.9. and the IPS detection engine fails for any reason. IMPORTANT! On a 3D3800 or 3D5800 sensor. Although some packets are transmitted without inspection during this time. Otherwise. 2. choose Inline from the Interface Set Type drop-down list. select an existing interface set group or select Create New Group to create a new interface set group. The Interface Sets page appears. 5. 3. See Using Interface Set Groups on page 223 for more information. a software bridge is automatically set up to transport packets when the sensor restarts. Select Operations > Configuration > Detection Engines > Interface Sets. choose either Inline or Inline with Fail Open. including a list of ungrouped sensors. • • For an 3Dx800 sensor. You can use alphanumeric characters and spaces. Optionally. Select the type of inline interface you want to create. if you plan to use RNA to monitor either an inline or inline with fail open interface set. the RNA or RUA detection engine monitoring that interface set will not see any traffic until the IPS detection engine restarts. as well as apply an intrusion policy to that detection engine. you must either configure an IPS detection engine that uses that interface set. For Crossbeam-based software sensors. Version 4. Click Create Interface Set.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 For most 3D Sensors with inline interface sets. the RNA detection engine monitoring that interface set will not see any traffic. from the Interface Set Type drop-down list. The Create Interface Set page appears. no packets are lost. Neither RNA nor RUA are supported on the 3D9800 sensor.1 Sourcefire 3D System Administrator Guide 218 . or configure the interface set in tap mode. If you are monitoring the same inline interface set with both IPS and RNA or RUA. A list of sensor groups appears. To create an inline interface set: Access: Admin 1.

The default setting is 750 ms and the valid range is from 250 ms to 60. Optionally. You can set any jumbo frame size between 1518 and 9018 bytes.000 ms. you can select the Enable Fail-safe check box to enable traffic pass-though during application bypass.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 6. 7. The following shows a 3D9900 interface set. If you are creating an inline interface set. a list of sensor groups appears. set jumbo frame options on the Crossbeam CLI. a list of network interfaces on the sensor appears. 8. and if you are configuring an interface set on a 3D6500 or 3D9900 type a maximum frame size for your IP traffic in the Maximum Frame Size field. including a list of ungrouped sensors. When the option selected. IMPORTANT! Link state propagation and automatic application bypass are not supported on Sourcefire 3D Sensor Software for X-Series platforms. select Automatic Application Bypass if your network is sensitive to latency. however.9. On the Defense Center only. you can select a Bypass Threshold in milliseconds (ms). Select one of the sensors from the list. Optionally. Version 4. Optionally. You can. a list of paired network interfaces on the sensor’s fail-open cards appears.1 Sourcefire 3D System Administrator Guide 219 . 9. If you are creating an inline with fail open interface set. and if you are configuring an interface set on a 3D9900. inclusive.

11.1 Sourcefire 3D System Administrator Guide 220 . select the Enable Tap Mode check box to use tap mode. • If you are creating an inline interface set. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. For 3D Sensor Software for Crossbeam Systems X-Series. • For more information.e0 corresponds to the leftmost interface on the network interface module (NIM) in I/O Slot 0 on the back of your appliance. inline and inline with fail open interface sets can include up to the total number of interface pairs on the sensor. You can configure inline interface sets on 3D3800 and 3D5800 sensors to contain up to four pairs of interfaces. the names that appear in the Available Interfaces list correspond to the slot number and interface location. select two interfaces that you want to designate as an inline pair from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list. Version 4. Inline with fail open interface sets on 3D3800 and 3D5800 sensors can also contain up to four pairs of interfaces. but each pair must reside on a single fail-open network card. Optionally. • Use the Shift and Ctrl keys to select multiple interfaces or interface pairs at once. Note that 3D Sensor Software for Crossbeam Systems X-Series does not support inline with fail open interface sets. s0. select at least one interface pair from the Available Interfaces list and click the arrow button to add the interface to the Selected Interfaces list. Add the interfaces to your interface set.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. If you are creating an inline with fail open interface set. Determining which interface name corresponds with a physical interface on your sensor depends on the model: • For 3Dx800 sensors. On the 3D9800 sensor. for a 3DX800 or 3DX900 sensor. see the Installation Guide for your sensor or sensor software. For example.9. the paired interface names that appear in the Available Interfaces list correspond to the device names you assigned to the transparent bridge-mode bridge circuits you created on the X-Series. Repeat to add additional interface pairs.

Although some packets are transmitted without inspection during this time. This option is especially useful if the routers on your network are able to re-route traffic around a network device that is down. for a 3D3800 or 3D5800 sensor. editing an interface set or detection engine can cause the detection engines on the sensor to restart. TIP! The link lights on fiber fail-open NIMs remain lighted even when the link state is down on 3D3800 or 3D5800 sensors with link state propagation enabled. Click Save. select Link State Propagation Mode. a software bridge is automatically set up to transport packets when the sensor restarts. IMPORTANT! Note that link state propagation is not available for Crossbeambased software sensors or 3D9800 sensors. 13. Optionally.1 Sourcefire 3D System Administrator Guide 221 . make sure you reapply intrusion policies to the IPS detection engines on the affected sensor. TIP! After you create an interface set.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 12. The following sections describe some of the cases where a detection engine is affected by changes to the detection engines and interface sets: Version 4.9. which can cause a short pause in processing. Editing an Interface Set Requires: DC or 3D Sensor In some circumstances. IMPORTANT! For most 3D Sensors with inline interface sets. no packets are lost. The interface set is created.

If you change the detection engine type for a detection engine. only that detection engine is restarted (although other CPUs may be restarted to rebalance the processing load). If you create an interface set. If you delete a detection engine or interface set. The Sourcefire 3D System checks the 3D9800 firmware version and displays the optional tap mode check box in the Create Interface Set page when appropriate. that detection engine is restarted. If you change which network interfaces are used by the interface set. all detection engines assigned to that interface set are restarted. If you change an interface set’s transparent mode setting or interface set type. or the detection engine type. which interface set is used. If you change an interface set’s tap mode setting. If you change a detection engine’s interface set. all detection engines assigned to that interface set are restarted. or transparent mode for an interface set.9. all the detection engines on the sensor are restarted because the total number of allocated resources has changed. • • • • • Other Sensors • • • • • • • Version 4. When you create a detection engine. all the detection engines on the sensor are restarted. the interface set type. nothing is restarted. If you delete a detection engine or interface set. all detection engines on the sensor are restarted. If you change the name or description of an interface set or detection engine. all detection engines on the sensor are restarted. If you change the number of detection resources allocated to a detection engine. all detection engines on the sensor are restarted.1 Sourcefire 3D System Administrator Guide 222 .Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3Dx800 Sensors • If you change the number of network interfaces. If you create a detection engine. • If you change the number of detection resources. only that detection engine is started (although other CPUs may be restarted to rebalance the processing load). all the detection engines using that interface set are restarted. all the detection engines on the sensor are restarted. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. nothing is restarted.

A restart occurs only when you assign a detection engine to the interface set. To delete an interface set: Access: Admin 1. Make sure you plan these actions for times when they will have the least impact on your deployment. Your changes are saved. Select Operations > Configuration > Detection Engines > Interface Sets. 2. If you change the name or description of an interface set or detection engine. nothing is restarted. nothing is restarted. See the following sections for more information: • • Creating Interface Set Groups on page 224 Deleting Interface Set Groups on page 225 Version 4. 2.1 Sourcefire 3D System Administrator Guide 223 . Make any changes to the interface set and click Update.Using Detection Engines and Interface Sets Using Interface Set Groups Chapter 6 • • If you create an interface set. Using Interface Set Groups Requires: DC You can use interface set groups to combine similar interface sets. The Interface Sets page appears. confirm that you want to delete the interface set. TIP! After you edit an interface set used by an IPS detection engine. To edit an interface set: Access: Admin 1. For more information on PEP policies. make sure you reapply your intrusion policy on the affected sensor. Click Delete next to the interface set that you want to delete. Deleting an Interface Set Requires: DC You cannot delete an interface set that is being used by a detection engine. The Create Interface Set page appears. The interface set is deleted. These groups make it easier to apply PEP policies to interface sets that have similar purposes. at the prompt. 3. Click Edit next to the interface set that you want to modify.9. see Understanding PEP Traffic Management in the Analyst Guide. You must delete the detection engine before you can delete the interface set. and. Select Operations > Configuration > Detection Engines > Interface Sets. The Interface Sets page appears.

To edit an interface set group: Access: Admin 1. Click Edit for the interface set group. You must create an interface set group before you can edit it. on the Interface Group Edit page. Select Operations > Configuration > Detection Engines > Interface Sets. Click Save. Editing Interface Set Groups Requires: DC/MDC or 3D Sensor The following procedure explains how to edit an interface set group. The Available Interface Sets page appears. Type a name for the interface set group in the Group Name field. See Creating Interface Set Groups on page 224. The Interface Set page appears again. Click Create Interface Set Group or click Create Interface Set then click Create New Group in the Group field. The Interface Group Edit page appears. Select Operations > Configuration > Detection Engines > Interface Sets. Version 4. 2. adding available interfaces to the group and clicking Save. To create a interface set group: Access: Admin 1. 3. 2.9.1 Sourcefire 3D System Administrator Guide 224 .Using Detection Engines and Interface Sets Using Interface Set Groups Chapter 6 Creating Interface Set Groups Requires: DC The following procedure explains how to create an interface set group. You can add interface sets to an interface set group by clicking Edit next to a interface set group name and. The Create Interface Set Group page appears.

Select available interface sets and to move them to the interface set group with the arrow buttons. 4. You can use a command line tool to force the interface set out of bypass mode. Removing Bypass Mode on Inline Fail Open Fiber Interfaces Requires: 3D Sensor When link state propagation is enabled on a sensor with an inline fail open interface set and the sensor goes into bypass mode. Inline Fail Open Interface Set Commands Requires: 3D Sensor When you use fiber inline fail open interfaces sets and the interface set goes into bypass. you can force the interface out of bypass mode.Using Detection Engines and Interface Sets Inline Fail Open Interface Set Commands Chapter 6 3. Click Delete next to the name of the interface set group. they are not deleted. The interface set group is deleted. most fiber inline fail open interface sets do not return from bypass automatically. Deleting Interface Set Groups Requires: DC When you delete an interface set group. all network traffic passes through the interface pair without being analyzed. The Available Interface Sets page appears. Version 4. See Forcing an Inline Fail Open Interface Set into Bypass Mode on page 226. It is not necessary to use this tool on inline with fail open copper interface pairs or to use this tool with 3D9900 sensors. You can also move interface sets out of the interface set group. Click Save to add the selected interfaces to the interface set group.1 Sourcefire 3D System Administrator Guide 225 . See Removing Bypass Mode on Inline Fail Open Fiber Interfaces. 2. You can force a copper or fiber inline fail open interface in or out of bypass. The Interface Sets page appears.9. To delete a interface set group: Access: Admin 1. any interface sets in the group are automatically ungrouped. IMPORTANT! Make sure you contact Technical Support if you are having issues with the fail open interfaces on your sensor. Select Operations > Configuration > Detection Engines > Interface Sets. TIP! This tool works on most 3D Sensors with inline with fail open fiber interface pairs. When the links restore.

it goes into bypass mode. 2. Open a terminal window on your 3D Sensor and enter the command su and the root password to switch to the root user. 3. IMPORTANT! Make sure you contact Technical Support if you are having issues with the fail open interfaces on your sensor. at the prompt.sh 2. /var/sf/bin/unbypass_cards. Version 4. The Selected Interfaces column displays the names of the interfaces in the interface set. TIP! Note that this tool works only with inline with fail open interface pairs. The Interface Sets page appears.1 Sourcefire 3D System Administrator Guide 226 .Using Detection Engines and Interface Sets Inline Fail Open Interface Set Commands Chapter 6 To force a fiber inline fail open interface set out of bypass mode: Access: Admin 1. Enter the following at the command line: 3.9. a state where all network traffic passes through the interface pair without being analyzed. The Create Interface Set page appears. or if the interface card does not fail open on its own. a message in syslog indicates the 3D Sensor is analyzing traffic. You cannot use it with non-fail open inline interface sets. On the appliance’s web interface. select Operations > Configuration > Detection Engines > Interface Sets. To force an inline fail open interface set into bypass mode: Access: Admin 1. If you are troubleshooting an interface set. you can use a command line tool to force the interface set into bypass mode. Log in as root onto the sensor and. click Edit next to the inline with fail open interface set you are investigating. you must know which two interfaces are included in the interface set. enter the correct password. For example: Fiber pair has been reset by un_bypass Forcing an Inline Fail Open Interface Set into Bypass Mode Requires: 3D Sensor When the sensor with an inline fail open interface set fails. You can determine this information on the Interface Sets page. Under Available Interface Sets. When the interfaces switch out of bypass mode. To force an inline fail open interface set into bypass mode.

pl open eth2:eth3 The following message appears: NOTE: You must already have a failopen interface set and detection engine configured on the pair you are forcing open or closed for this utility to work.. shared configuration. 2. enter the following: failopen_pair.pl close eth2:eth3 The following message appears: Mode changed for interfaces eth2:eth3 The interfaces return to normal mode and the traffic flowing through the detection engines on the interface set is analyzed as you would expect. To return an inline fail open interface set to normal mode: Access: Admin 1. if the interfaces in the interface set are eth2 and eth3. Enter the following at the command line: failopen_pair.1 Sourcefire 3D System Administrator Guide 227 . if the interfaces in the interface set are eth2 and eth3. Log in as root onto the sensor and. Then. If you did not specify the correct interfaces. Enter the following at the command line: failopen_pair. For information on establishing and separating clustered pairs. if you specified the correct interfaces. enter the correct password.9. see Managing a Clustered Pair on page 140. the following message appears: Mode changed for interfaces eth2:eth3 The interfaces switch to bypass mode and the traffic is no longer analyzed.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 4. the following message appears: No failopen interface set configured for interfaces eth2:eth3. at the prompt. After the cluster is established.pl close eth#:eth# For example.pl open eth#:eth# For example. Using Clustered 3D Sensors Requires: DC + 3D9900 You can increase the amount of traffic inspected on a network segment by connecting two fiber-based 3D9900 sensors in a clustered pair.. Select Operation > Sensors and note that clustered sensors have a peer icon. Version 4. you combine the 3D9900 sensors resources into a single. When you establish a clustered pair configuration. you can identify them on the Sensor list page. enter the following: failopen_pair.

and list the detection engines of paired 3D Sensors.com). and which sensor it is paired with. both sensors are listed in the interface set.example.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 You can see if the sensor is a master or slave. birch. Version 4. You cannot manage detection engines on the local GUI of a paired 3D Sensor. when you hover over the peer icon. In a clustered pair. and fir. edit. You use the combined detection engines as a single entity except when viewing information from the clustered pair. For more information. The format is DetectionEngineName (MasterSensorName. you can only manage them from a Defense Center and not from one of the clustered sensors. see: • • • Using Detection Engines on Clustered 3D Sensors on page 228 Understanding Interface Sets on Clustered 3D Sensors on page 229 Managing Information from a Clustered 3D Sensor on page 230 Using Detection Engines on Clustered 3D Sensors Requires: DC + 3D9900 For information about using detection engines with clustered 3D9900s.com is the name of the slave in the pair of 3D9900 sensors. a clustered 3D Sensors detection engine could be: Z inline DE (birch. you can combine their detection engines.example. fir. When you create a detection for a clustered pair. SlaveSensorName).example. where Z inline DE is the name of the detection engine. When you combine two 3D9900 sensors as a clustered pair. the Edit page is replaced with an informational page. Because the detection engines and interface sets are combined.9. For example. see: • • • Managing Clustered 3D Sensor Detection Engines Requires: DC + 3D9900 Use the managing Defense Center to create. see: • • • Managing Clustered 3D Sensor Detection Engines on page 228 Using Clustered 3D Sensor Detection Engines in Policies on page 229 Managing Information from a Clustered 3D Sensor on page 230 Creating a Detection Engine on page 193 Editing a Detection Engine on page 194 Deleting a Detection Engine on page 197 For information about how to manage detection engines.1 Sourcefire 3D System Administrator Guide 228 . the slave’s ethb0 and ethb1 connect to the master and the its ethb2 and ethb3 are not connected.com.com is the name of the master in the pair. Both 3D9900 sensors are listed as a part of the detection engine formed by the clustered 3D Sensors. By combining two 3D9900 sensors as a clustered pair. the Defense Center displays the single interface set of the master sensor.example.

Understanding Interface Sets on Clustered 3D Sensors Requires: DC + 3D9900 After you set up the clustered pair.com is the name of the master in the pair. The slave’s ethb2 and ethb3 pair are not functional and must not be connected when you establish the clustered pairing. The master’s ethb0 and ethb1 pair are used for sensing connections. those pages are replaced with an informational page.com is the name of the slave in the pair of 3D9900 sensors.example. Clustered 3D Sensors detection engines present their names in the form DetectionEngineName (MasterSensorName.com). Version 4. where Z inline DE is the name of the detection engine. a master/slave relationship is established between the two 3D9900 sensors.example. IMPORTANT! You cannot use the Policy & Response menu on the local GUI of a paired 3D Sensor.9. fir.com. Using Clustered 3D Sensor Detection Engines in Policies Requires: DC + 3D9900 Use the managing Defense Center to manage policies and responses of paired 3D Sensors. the detection resources are listed as from both sensors. SlaveSensorName) when you use them in: • • • • IPS policies PEP policies RNA detection policies compliance rules For example. a clustered 3D Sensors detection engine could be: Z inline DE (birch. and fir.example.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 When you create or edit a detection engine formed by the clustered 3D Sensors.1 Sourcefire 3D System Administrator Guide 229 .example. birch. The master’s ethb2 and ethb3 pair connect to the slave’s ethb0 and ethb1 pair.

example. Managing Information from a Clustered 3D Sensor Requires: DC + 3D9900 Clustered sensors report information from each of the sensors. Analysis & Reporting tools display the information from each half of the detection engine independently.com).com is the master sensor. and fir. the clustered 3D Sensors detection engine could be: Z inline DE (birch.com is the slave sensors. The Interface Sets page appears.com. birch.example. fir.example.example. When you examine information from the clustered pair. A Select Detection Engines list from the Intrusion Event Statistics page is show below. A clustered pair interface set displays both the master and the slave in the Sensor column.example. add data from both sensor of the detection engine to measure the total.example. see Using Detection Engines on Clustered 3D Sensors on page 228.1 Sourcefire 3D System Administrator Guide 230 . For information about using interface sets in the detection engines of clustered 3D9900s. For example.9. it is listed as from both Z inline DE / birch.Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 To view the clustered pair interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets. These reports include: • • • intrusion event statistics intrusion events event graphs Version 4. Do not attempt to change the interface settings while a clustered sensor is paired. where Z inline DE is the detection engine. IMPORTANT! If you collect statistics from clustered 3D9900s. in the form DetectionEngineName/MasterSensorName and DetectionEngineName/SlaveSensorName.com and from Z inline DE / fir.com.

Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 • • • • dashboards RNA statistics network map searches IMPORTANT! If you use eStreamer to stream event data from a clustered pair of 3D9900s to an external client application.1 Sourcefire 3D System Administrator Guide 231 . Version 4. The eStreamer settings are not automatically synchronized over the pair. collect the data from both 3D9900s and ensure that you configure each 3D9900 identically.9.

1 Sourcefire 3D System Administrator Guide 232 . The Report Types table describes the reports you can create and the components required for producing them. and you must configure the RNA component for that sensor to collect RNA events. You must have an RNA host license on the Defense Center managing your 3D Sensor.Working with Event Reports Chapter 7 Sourcefire 3D System Administrator Guide The Sourcefire 3D System provides a flexible reporting system that you can use to generate a variety of event reports. Similarly. For example. the RNA Events report appears under the RNA report category on the Report Designer page. the Intrusion Events report appears under the IPS report category and requires the IPS component on a 3D Sensor. Report Types Report Intrusion Events with Destination Criticality Intrusion Events with Source Criticality Intrusion Events SEU Import Log Host Attributes Report Category IPS or RNA IPS or RNA IPS IPS RNA Requires DC + RNA + IPS DC + RNA + IPS DC + IPS DC + IPS DC + RNA Version 4. Event reports include the data that you see on the event view pages for each type of event presented in a report format. You can run the report on the 3D Sensor or on the Defense Center that manages the sensor.9.

Version 4. For more information on how to create and save report profiles.9.Working with Event Reports Chapter 7 Report Types (Continued) Report RNA Hosts Scan Results RNA Client Applications RNA Events RNA Services Vulnerabilities Hosts with Services Flow Data RUA Events Users White List Violations Compliance Events White List Events Remediation Status Health Events Audit Log Events Report Category RNA RNA RNA RNA RNA RNA RNA RNA RUA RUA Compliance Compliance Compliance Compliance Health Monitoring Audit Log Requires DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RUA DC + RUA DC + RNA DC + RNA DC + RNA DC + RNA DC Any You can use a predefined report profile to generate your report. You can create a new report profile through the use of the Report Designer. see Editing Report Profiles on page 263. For information on modifying a predefined or existing report profile.1 Sourcefire 3D System Administrator Guide 233 . or use it as a template for an event report profile which can be customized by modifying field settings as appropriate and saving the report with the new values. see Understanding Report Profiles on page 241.

see Managing Generated Reports on page 237. For information on how to generate a report from a report profile view. see Managing Remote Storage on page 393. see Generating Reports from Event Views on page 235. download. For information on how to modify a report profile.Working with Event Reports Working with Event Reports Chapter 7 See the following sections for more information: • • • • • • • • Working with Event Reports on page 234 Working with Report Profiles on page 234 Managing Generated Reports on page 237 Understanding Report Profiles on page 241 Working with Report Information on page 248 Working with Report Sections on page 255 Working with Report Options on page 258 Using a Report Profile on page 260 Working with Event Reports Requires: IPS or DC/ MDC You can generate reports manually or automatically on any subset of events in an event view. NFS. as well as move reports to a remote storage location. You can use a predefined report profile as a template for an event report which can be customized by modifying field settings as appropriate and saving the report with the new values. You can create a new report profile through the use of the Report Designer. see Running Remote Reports on page 240. You can also specify which detection engine to use when generating the report. see Creating a Report Profile on page 246. For more information on how to manage your reports. For more information on how to create and save report profiles. You can run reports remotely from the Defense Center using the data on the sensors for the report. For more information on how to configure a Defense Center to store reports in a remote location using SSH. see Using a Report Profile on page 260. see Editing Report Profiles on page 263. if you use a Defense Center to manage your sensors. For information on how to generate a report for the data that appears in an event view.9. Version 4. You can view.1 Sourcefire 3D System Administrator Guide 234 . or delete previously generated reports. or SMB. You can store reports locally or remotely. For more information on how to how to generate reports on managed sensors and view the results on the Defense Center. Working with Report Profiles Requires: IPS or DC/ MDC You can use a predefined report profile to generate your report.

Version 4. values (CSV). For details on using workflows and constraining events within a workflow. Generating Reports from Event Views Requires: IPS or DC/ MDC You can generate reports on any subset of events in an event view. and include custom options such as a corporate logo or footers. For details on using the event search. see Understanding and Using Workflows in the Analyst Guide. You can generate reports in PDF HTML or comma-separated value (CSV) formats. For more information on each of the summary reports. see Understanding Report Profiles on page 241. You can also specify how you want the report formatted: PDF HTML. .Working with Event Reports Generating Reports from Event Views Chapter 7 You can include a summary report for intrusion events and RNA events by selecting the appropriate radio button in your report profile. For more information. you can also create a report profile and then either use it to generate a report or save it to use later. and a short description of the report. or as comma-separated . see Working with Report Options on page 258. see Using Summary Reports on page 255.9. see Searching for Events in the Analyst Guide. For information on how to incorporate these options into your reports. Drill down through a workflow until you have the proper events in your event view. To generate a report for a specific set of events: Access: Any Analyst/ Admin 1. Populate an event view with the events you want to include in the report. as described in this section.1 Sourcefire 3D System Administrator Guide 235 . You can do this several ways: • Use an event search to define the type of events you want to view. • TIP! In addition to generating reports in an event view.

The following graphic shows the Defense Center version of the page. Click Report Designer in the toolbar. TIP! If you need to go back to the drill-down page where you opened the Report Designer. 5. 3. Click Generate Report. HTML. 4. Select the check boxes next to the output options you want in the report: PDF . click Return to Calling Page at the bottom of the Report Designer page. Version 4. or CSV.Working with Event Reports Generating Reports from Event Views Chapter 7 2. The settings on the page reflect the parameters that you selected for the search or through the drill-down pages. Change any of the parameters as necessary to meet your needs. see Creating a Report Profile on page 246. For details on the parameters for a report.9.1 Sourcefire 3D System Administrator Guide 236 . Note that you may select more than one format. The Report Designer page appears.

if you change the remote storage location. Version 4.1 Sourcefire 3D System Administrator Guide 237 . The report appears. for scheduled tasks). NFS. who generated it. Note that only Series 2 Defense Centers support remote storage of reports. Each report is listed with the report name as defined in the report profile plus the date and time the report was generated. then click the report name on the Reporting page that appears. To view the report. or delete reports.Working with Event Reports Managing Generated Reports Chapter 7 6. click Reports in the toolbar.pdf for PDF reports .csv for comma-separated value reports . You can enable or disable remote storage using the Enable Remote Storage for Reports check box. The report profile is saved and the report generates in the output formats you selected. the appliance provides the disk usage of the storage device. you can move reports to a remote storage location. which indicates whether it has yet to be generated (for example. the Defense Center hides any previously generated remotely stored reports. In addition. The default location for report storage is listed at the top of the page.zip for HTML reports (HTML reports are zipped along with the necessary graphics) Finally. Click OK to confirm that you want to save the current parameters as a report profile. You can view. and whether it is stored locally or remotely. Each report has one of the following file extensions appended to the report name: • • • . for local. or whether the generation failed (for example. click Remote Storage on the toolbar. For more information.9. and SMB storage. it has already been generated. To configure remote storage. see Managing Remote Storage on page 393. due to lack of disk space). Managing Generated Reports Requires: IPS or DC/ MDC Manage previously generated reports on the Reporting page. If you disable remote storage. download. If you are using a Series 2 Defense Center. the Defense Center hides reports not stored in the new location. the appliance lists the status of each of the reports. 7.

Select Analysis & Reporting > Report Profiles.Working with Event Reports Managing Generated Reports Chapter 7 For information on managing reports. 2. You have two options: • • Enable the check box next to the report you want to view. click Reports. see the following topics: • • • • • Viewing Generated Reports on page 238 Downloading Generated Reports on page 238 Deleting Generated Reports on page 239 Moving Reports to a Remote Storage Location on page 239 Running Remote Reports on page 240 Viewing Generated Reports Requires: IPS or DC/ MDC Use the following procedure to view generated reports. Downloading Generated Reports Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to download generated reports. On the toolbar. For more information. Downloading Generated Reports. see the next section.9. other users can only view reports that they generated themselves. Note that users with Admin access can view all reports generated on the appliance. The Reporting page appears. the report opens. In either case. You can view one report at a time. then click View. The Report Profiles page appears. TIP! You can also save reports locally. 3. Click the name of the report. To view a generated report: Access: Any Analyst/ Admin 1. Version 4. To download generated reports: 1. click Reports. 2. The Report Profiles page appears. On the toolbar. The Reporting page appears. Select Analysis & Reporting > Report Profiles.1 Sourcefire 3D System Administrator Guide 238 .

you can move locally stored reports to a remote storage location. you cannot move it back.1 Sourcefire 3D System Administrator Guide 239 . Confirm that you want to delete the reports. The reports are deleted. TIP! Enable the check box at the top left of the page to delete all reports on the page. Version 4. On the toolbar. 2.Working with Event Reports Managing Generated Reports Chapter 7 3. a second check box appears that you can enable to download all reports on all pages. Select Analysis & Reporting > Report Profiles. The Reporting page appears. click Reports. To delete generated reports: 1. For information on configuring a remote storage location and enabling remote storage of reports. a second check box appears that you can enable to delete all reports on all pages. Note that after you move a report to a remote location. 3. Enable the check boxes next to the reports you want to delete. TIP! Enable the check box at the top left of the page to download all reports on the page. Enable the check boxes next to the reports you want to download. Follow your browser’s prompts to download the reports. 4. The reports are downloaded in a single . Moving Reports to a Remote Storage Location Requires: DC/MDC On Series 2 Defense Centers. The Reporting page appears. see Managing Remote Storage on page 393. If you have multiple pages of reports. 4. The Report Profiles page appears. If you have multiple pages of reports. Deleting Generated Reports Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete generated reports.zip file. click Reports. then click Download. then click Delete. 2. The Report Profiles page appears. Select Analysis & Reporting > Report Profiles.9. To move generated reports: Access: Any Analyst/ Admin 1. On the toolbar.

if you use your Defense Center to manage a 3D Sensor with IPS. There are several limitations that you need to keep in mind: • • If you do not store data on the sensor. You cannot run remote reports on 3Dx800 or Crossbeam-based software sensors. Select Analysis & Reporting > Report Profiles. The Report Profiles page appears. Click Create Report Profile. The reports are moved. a second check box appears that you can enable to move all reports on all pages. Click OK. A prompt appears asking you to confirm that you want to run the report remotely. For example. you have the option of running reports remotely from the Defense Center using the data on the sensors. Enable the check boxes next to the reports you want to move.1 Sourcefire 3D System Administrator Guide 240 . then the remote report will be empty. 4. From the drop-down list at the bottom of the page. 3. If your report uses a logo or image file. and you store IPS data on the sensor in addition to sending it automatically to the Defense Center. 4. Running Remote Reports Requires: DC + 3D Sensor If you use a Defense Center to manage your sensors.Working with Event Reports Managing Generated Reports Chapter 7 3. The Report Designer page appears. TIP! Enable the check box at the top left of the page to move all reports on the page. You cannot run incident reports remotely on managed 3D Sensors with IPS.9. Confirm that you want to move the reports. • • To run a remote report: Access: Any Analyst/ Admin 1. you can run the report on the data that is resident on the sensor. See Generating Reports from Event Views on page 235 for details. 5. The report is run on the sensor that you selected. If you have multiple pages of reports. select the sensor where you want to run the report and click Run Remote Report. 2. Create the report that you want to run on the managed sensor. then click Move. the logo or image file must exist on both the Defense Center and the managed sensor where you run the report. Version 4.

listing the report you just generated on the managed sensor. click Reports. inserts a logo. see Working with Report Options on page 258. Report Sections identifies which sections to include in the report. or use as a template for a new report profile by modifying field settings as appropriate and saving the report with the new values. TIP! You can also use report profiles as the basis for remote reports by creating a profile as described in Creating a Report Profile on page 246. comma-separated (CSV format). The Reporting page appears. and provides an option to email the report. Additionally. Note that remote. For more information. Depending upon your choices. all report profiles contain the same three configurable areas: Report Information. For more information. In the toolbar. and workflow. or . You can then manually run these reports or schedule them to run automatically (for information about scheduling tasks. Note that not all options are available for all categories or types. table view of events. Report Information defines the basic nature of the report profile by first giving the report profile a name. see Scheduling Tasks on page 425). a new report profile can be created through the use of the Report Designer. See the following sections for more information: • • • • Understanding the Predefined Report Profiles on page 242 Modifying a Predefined Report Profile on page 246 Creating a Report Profile on page 246 Working with Report Information on page 248 Version 4. or the inclusion of an image file. Report Options specifies the outputs of the report format (PDF HTML. and then selecting the report category and type. When you run the report. such as detection engine. adds a custom footer. see Working with Report Information on page 248. see Working with Report Sections on page 255. and Report Options. search query. Whether you use a predefined report profile or create your own. make sure you select the name of the sensor and click Run Report Remotely.Working with Event Reports Understanding Report Profiles Chapter 7 6.1 Sourcefire 3D System Administrator Guide 241 . such as a drill down of events. You can use a predefined report profile to either generate your report.9. Understanding Report Profiles Requires: IPS or DC/ MDC Report profiles provide the structure for the generated report. You can view or download the remote report as you would with any other locally generated report. 7. For more information. you will have other options to define.is prepended to the name of the report. Reports Sections.

save the report with the new values. you can use a predefined report profile as a template for an event report. You can modify field settings as appropriate.Working with Event Reports Understanding Report Profiles Chapter 7 • • • • • Working with Report Sections on page 255 Working with Report Options on page 258 Using a Report Profile on page 260 Generating a Report using a Report Profile on page 261 Deleting Report Profiles on page 263 Understanding the Predefined Report Profiles Requires: IPS or DC/ MDC A predefined report profile provides you with predefined setting for event reports. and run the report manually or automatically.9. As with custom report profiles that you create (see Creating a Report Profile on page 246). Version 4.1 Sourcefire 3D System Administrator Guide 242 .

The following graphic shows the Blocked Events report profile on the Defense Center version of the page. you must save the report profile with a new name to preserve your new settings.9. High Priority Events. Note that if you modify the default settings. and Host Audit. Version 4.Working with Event Reports Understanding Report Profiles Chapter 7 Predefined reports are provided by the Sourcefire system: Blocked Events. The following tables provide the default settings for each of the predefined report profiles. The Report Options area is not included in these charts. you have created a new report profile.1 Sourcefire 3D System Administrator Guide 243 .

9. sliding time window Quick Enabled Enabled Enabled Enabled Disabled Disabled The High Priority Events report profile provides information on intrusion events as well as the host criticality of hosts involved in the intrusion events for the past Version 4. Default Settings for the Blocked Events Report Profile Field Report Category Report Type Detection Engine Search Query Workflow Setting IPS Intrusion Events All Blocked Events Impact and Priority (on the Defense Center) Destination Port (on the 3D Sensor) Time Add Summary Report Impact Based Event Summary (on the Defense Center) Drill Down of Source and Destination IPS (on the Defense Center) Drill Down of Destination Port (on the 3D Sensor) Drill Down of Events (on the 3D Sensor) Table View of Events Packets (limit 50 pages) Last day.Working with Event Reports Understanding Report Profiles Chapter 7 The Blocked Events report profile provides information on blocked intrusion events for all detection engines for the past twenty-four hours. This report profile is available on the Defense Center or on a 3D Sensor with IPS.1 Sourcefire 3D System Administrator Guide 244 .

9.1 Sourcefire 3D System Administrator Guide 245 .Working with Event Reports Understanding Report Profiles Chapter 7 twenty-four hours. This report profile is available only on a Defense Center that manages 3D Sensors with RNA and IPS. Default Settings for the Host Audit Report Profile Field Report Category Report Type Detection Engine Search Query Setting RNA RNA Hosts All Local Systems Version 4. Default Settings for the High Priority Events Report Profile Field Report Category Report Type Detection Engine Search Query Workflow Time Add Summary Report Impact to Criticality Summary Source Destination Drill Down Intrusion Events with Destination Criticality Packets (limit 50 pages) Setting IPS Intrusion Events with Destination Criticality All High Priority Events Events by Impact. sliding time window Quick Enabled Enabled Enabled Disabled The Host Audit report profile provides operating system details for the past week on systems less than two network hops away from 3D Sensors with RNA. and Host Criticality Last day. Priority. This report profile is available only on the Defense Center that manages 3D Sensors with RNA.

9. and which workflows to examine. in the IPS report category. second.1 Sourcefire 3D System Administrator Guide 246 . For example. table view of events. selecting the Intrusion Events with Source Criticality report type does not provide that option. and workflows to apply. but not all options are available for all reports. selecting the Intrusion Events report type gives you the option to select which detection engines to search. finally. and saving the report with the new values. or an image file. For more information on how to modify a predefined report profile. and. save the report profile. You perform three steps to create the a report profile: first. configure the options in each of three report areas (Report Information. the criteria for the search. . see Editing Report Profiles on page 263. Report Sections. Not all options are available for all reports. Version 4. and Report Options).Working with Event Reports Understanding Report Profiles Chapter 7 Default Settings for the Host Audit Report Profile (Continued) Field Workflow Time Add Summary Report Summary of OS Names Summary of OS Versions OS Details with IP NetBIOS. such as a drill down of events. Criticality Table View of Events Packets (limit 50 pages) Setting Operating System Summary Last week. Working with Report Sections on page 255 explains how to specify which the sections to be included in the report. Creating a Report Profile Requires: IPS or DC/ MDC You can create the report profile by defining category and type. Note that all reports contain the option for a summary report and an image file. queries. sliding time window summary Enabled Enabled Enabled Disabled Disabled Modifying a Predefined Report Profile Requires: IPS or DC/ MDC You can use a predefined report profile as a template to create a new report profile by modifying the field settings as appropriate. create the report profile in the system. and then specifying which detection engines to search. Working with Report Information on page 248 explains how to set the type of report and how to specify which detection engines.

Select Analysis & Reporting > Report Profiles. adds a custom . TIP! You can also reach the Report Designer page from any event view by clicking Report Designer on the toolbar. To create a report profile: Access: Any Analyst/ Admin 1. footer or logo. The Report Profiles page appears. Click Create Report Profile.Working with Event Reports Understanding Report Profiles Chapter 7 Working with Report Options on page 258 section explains how to set the output of the report (PDF HTML or comma-separated value (CSV) format). 3.9. 2. Continue with Defining Report Information on page 254. Version 4. The Report Designer page appears.1 Sourcefire 3D System Administrator Guide 247 . and how to use the option which emails the report. The following graphic shows the Defense Center version of the page.

dashes. search query. such as detection engine. and workflow.1 Sourcefire 3D System Administrator Guide 248 . and then selecting the report category and type. periods. parentheses. Note that not all options are available for all categories or types. you will have other options to define. The Report Name can be any name using 1-80 alphanumeric characters. Depending upon your choices.9. Version 4. and spaces. The following graphic is an example of the Report Information section.Working with Event Reports Working with Report Information Chapter 7 Working with Report Information Requires: IPS or DC/ MDC You define the basic nature of the report profile by first giving the report profile a name.

.. Compliance Health Monitoring Audit Log Version 4. or white list events. see RNA Category Report Types on page 252. you can create a report which searches selected detection engines for RNA client applications. have an IPS license and you want to report on intrusion events with or without source or destination criticality.Working with Event Reports Working with Report Information Chapter 7 The Report Category defines which system feature is examined in the report. remediation status. RNA services. such as the Compliance or Audit Log report categories. RNA hosts. you can create a report which searches selected detection engines for RUA events.. The Report Type is a subset of the Report Category and provides a greater level of detail to the report. RUA are using a Defense Center with an RUA host license and you want to search one or more detection engines to examine the RUA Events and users. IPS If you. For more information on RNA Report Type options. See Using Report Types on page 250 for more information. RNA are using a Defense Center with an RNA host license and you want to report on host attributes.1 Sourcefire 3D System Administrator Guide 249 . or the SEU import log. are using a Defense Center with an RNA host license and you want to report on white list violations.. or scan results. Select from the Report Categories table . For example. see IPS Category Report Types on page 251. compliance events. you can create a report which searches for IP-specific high impact intrusion events on a specified detection engine. Use this option to select a workflow on one or more detection engines to search for blocked events. In many cases. Report Categories Select. For information on IPS Report Type options. For example. For example. and generate a report which can include sections with a Table View of Events and Users. hosts with services. public or private addresses only. However IPS and RNA report types options are extensive and provide detailed options for defining your report profile. intrusion events with source criticality.For example. report types are limited and self-explanatory. RNA events. are using a Defense Center and you want to report on the health of your sensors. RNA client applications. or various services. or exploits that target client/server issues. you can create a report which searches a selected detection engine for RNA compliance events. Options vary depending upon Report Type.9. want to report on audit log events. vulnerabilities. high impact or high priority events. common concerns. Use this option to search hosts for blocked or high priority events.

The Time option allows you to define the period of time for which the report is generated. RNA. and can include a list of exploits (such as Sasser Worm Search or non-standard service attempts) or areas of concern such as IRC Events or Kerberos Client/Server issues. or sliding time frame. See the following sections for more information: • • Using Report Types on page 250 Defining Report Information on page 254 Using Report Types Requires: IPS or DC/ MDC The Report Type is a subset of the Report Category and provides a greater level of detail to the report. expanding. white list. client applications. However.9. such as the Compliance or Audit Log report categories. and Search Query. host attributes. Some report categories. and can include such options as Network Services by Count or Host Violations. have limited report types and are self-explanatory. Options vary depending upon which options you selected for Report Type.Working with Event Reports Working with Report Information Chapter 7 The Detection Engine allows you to select which detection engines are to be searched for the report. The Search Query identifies the search criteria for the report.1 Sourcefire 3D System Administrator Guide 250 . This option is available when searching for events. see Setting Event Time Constraints in the Analyst Guide. and IP-Specific or Impact and Priority. Options for the report type vary depending upon which Report Category is selected. For more information. such a intrusion. Click in the current time field to open a pop-up window from which you can select a static. See the following sections for more information: • • IPS Category Report Types on page 251 RNA Category Report Types on page 252 Version 4. or when searching the network for RNA hosts. Detection Engine. or compliance events. Options vary depending upon Report Type. the report types available to the IPS and RNA report categories are extensive and provide detailed options for defining your report profile. and health monitoring. The Workflow allows you to select which workflow to examine.

Working with Event Reports Working with Report Information

Chapter 7

IPS Category Report Types
You can choose from the following IPS Category Report Types
:

IPS Category Report Types Select... Intrusion Events To... search one or more detection engines using user-specified search queries and workflows to generate a report which can include sections with a drill down of the destination port and events, a table view of events, and the packets. Search queries include: Blocked Events, Bootstrap Client/Server, Common Concerns, DNS Service, DirectX Service, FTP Service, Finger Service, High Impact Events, High Priority Events, IRC Events, Impact1/Not Dropped Events, Kerberos Client/Server, LDAP Services, Mail Services, Oracle Service, Private Addresses Only, Public Addresses Only, RPC Services, and Reserved Port TCP Scan. Workflows include: Destination Port, Event-Specific, Events by Priority and Classification, Events to Destinations, IP-Specific, Impact and Priority, Impact and Source, Impact to Destination, Source Port, and Source and Destination. Intrusion Events with Source Criticality search using the Blocked Events or High Priority events search queries to generate a report on the Intrusion Events with Source Criticality default workflow which can include sections on Intrusion Events with Source Criticality, and the packets. search using the Blocked Events or High Priority Events search queries on your choice of three workflows: Events by Impact, Priority, and Host Criticality, which can include sections on Impact to Criticality Summary, Source Destination Drill Down, Intrusion Events with Destination Criticality, and the packets. Events with Destination, Impact, and Host Criticality, which can include sections on Current Events Monitor, Intrusion Events with Destination Criticality, and the packets. Intrusion Events with Destination Criticality default workflow, which can include sections on Intrusion Events with Destination Criticality, and the packets. SEU Import Log generate a report on the SEU Detail View workflow.

Intrusion Events with Destination Criticality

Version 4.9.1

Sourcefire 3D System Administrator Guide

251

Working with Event Reports Working with Report Information

Chapter 7

RNA Category Report Types
You can choose from the following RNA Category Report Types: RNA Category Report Types Select... Host Attributes To... search one or more detection engines to examine the Attributes workflow, and generate a report which can include sections with a table view of host attributes and the packets. search one or more detection engines to examine the Client Application Summaries or RNA Client Applications workflows, and generate a report which can include sections with a table view of client applications and the packets. examine the Vulnerabilities workflow and generate a report which can include sections with a table view of vulnerabilities, vulnerabilities on the network, and the packets. search using the Blocked Events or High Priority events search queries on the Intrusion Events with Source Criticality default workflow, and generate a report which can include sections on Intrusion Events with Source Criticality, and the packets. examine the Hosts with Services Default Workflow or the Service and Host Details, and generate a report which can include sections on Hosts with Services and the hosts. search one or more detection engines to examine the operating system summary or RNA hosts for local, remote, unidentified, or unknown systems, and generate a report which can include sections with a Summary of Operating System Names, Summary of Operating System Versions, Operating System Details with IP NetBIOS Criticality, Table View of Hosts, and Hosts. , generate a report on the Scan Results workflow. search one or more detection engines using the NetSky.S Worm Search, New Events, Sasser Worm Search, Subseven Trojan Search, Timeout Events, and Update Events, and generate a report which can include sections with a Table View of Events, and Hosts.

RNA Client Applications

Vulnerabilities

Intrusion Events with Source Criticality

Host with Services

RNA Hosts

Scan Results RNA Events

Version 4.9.1

Sourcefire 3D System Administrator Guide

252

Working with Event Reports Working with Report Information

Chapter 7

RNA Category Report Types (Continued) Select... RNA Services To... search one or more detection engines for non-standard service events (such as non-standard HTML, non-standard mail, non-standard SSH) in Network Services by Count, Network Services by Hit, and RNA Services workflows, and to generate a report which can include sections with Active Services, Service Application Activity, Service Version Audit, Service by Host, and Hosts. search using the Blocked Events, Events to High Criticality Hosts, or High Priority Events search queries, and generate a report on your choice of three workflows: Events by Impact, Priority, and Host Criticality, which can include sections on Impact to Criticality Summary, Source Destination Drill Down, Intrusion Events with Destination Criticality, and the packets. Events with Destination, Impact, and Host Criticality, which can include sections on Current Events Monitor, Intrusion Events with Destination Criticality, and the packets. Intrusion Events with Destination Criticality default workflow, which can include sections on Intrusion Events with Destination Criticality, and the packets. Flow Data search one or more detection engines using user-specified search queries and workflows, and generate a report which can include sections with the Top Ten workflows, Table View of Flow Summary Data, Table View of Flow Data drill down of the destination port and events, a table view of events, and the packets. Search queries include: Possible Database Access, Standard HTTP Standard , Mail, Standard SSL, and Unauthorized SMTP . Workflows include: Flow Summaries, Flows by Detection Engine, Flows by Initiator, Flows by Port, Flows by Responder, Flows by Service, Flows Over Time, RNA Flows, Traffic by Detection Engine, Traffic by Initiator, Traffic by Port, Traffic by Responder, Traffic by Service, Traffic Over Time, Unique Initiators by Responder, and Unique Responders by Initiator.

Intrusion Events with Destination Criticality

Version 4.9.1

Sourcefire 3D System Administrator Guide

253

Working with Event Reports Working with Report Information

Chapter 7

Defining Report Information
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin After you have determined which options you need for your report, use the following procedure to define the report information options. To define the Report Information: 1. From the Report Category drop-down list, select the report category for which you want to create a report.

You can choose from: • • • • • • IPS (with an IPS license) RNA (on a Defense Center with an RNA host license) RUA (on a Defense Center with an RUA host license) Compliance (on a Defense Center with an RNA host license) Health Monitoring (on a Defense Center) Audit Log

2. From the Report Type drop-down list, select the type of report you want to create. 3. Optionally, if the report type you selected includes the Detection Engine option, select a specific Detection Engine on which to report. 4. Requires: DC Optionally, if you are reporting on health events, select a specific sensor or sensor group from the Sensor drop-down list. 5. From the Search Query drop-down list, either use the Use Current Query option (which retains any query parameters you specified on the search page or event page) or select one of the existing search queries. Note that if you did not previously specify a search query, the Use Current Query option places no constraints on the events. 6. From the Workflows list, select the workflow you want to use to build the report. For information on workflows, see Understanding and Using Workflows in the Analyst Guide.

Version 4.9.1

Sourcefire 3D System Administrator Guide

254

Working with Event Reports Working with Report Sections

Chapter 7

7.

Specify the time range for the report. Depending on your default time window, the time range matches either the time window for the event view you are using to building the report profile, or the global time window. You can change time range by clicking it and using the Date/Time pop-up window to select a new time range. For more information, see Setting Event Time Constraints in the Analyst Guide.

8. Continue with Defining the Report Sections on page 258. IMPORTANT! For report profiles that you plan to use multiple times, such as in scheduled tasks, Sourcefire strongly recommends that you use a sliding time range. If you create a report profile with a static time range, the appliance will generate a report using the same time range (and therefore the same events) every time you use the report profile.

Working with Report Sections
Requires: IPS or DC/ MDC The Report Sections area is populated based on the workflow you selected. Select the check box for each report section you want to include in the report. Reports can include up to 10,000 records for each report section you select. See the following sections for more information: • • • Using Summary Reports on page 255 Including an Image File on page 257 Defining the Report Sections on page 258

Using Summary Reports
Requires: IPS or DC/ MDC Depending on the components you are licensed to use in your Sourcefire 3D System deployment, you can include summary reports for intrusion events and RNA events. You can append these summary reports to the beginning of any report by selecting the appropriate radio button in the report profile. Intrusion event reports require the IPS component. If your deployment includes IPS, you can include either a Quick Summary or a Detail Summary report in your report profile definition.

Version 4.9.1

Sourcefire 3D System Administrator Guide

255

Working with Event Reports Working with Report Sections

Chapter 7

The Comparison of Quick Summary and Detail Summary Reports table shows which information is included in the reports
.

Comparison of Quick Summary and Detail Summary Reports Report Information Pie chart showing the percentage of events in each event type (which maps to the rule category for the rule that generated the event) List of the 10 most active and 10 least active events Graph showing the number of events over time Pie charts showing the percentage of events by protocol (for example, TCP , UDP or ICMP) and event classification (which maps to the value for the , classtype keyword in the rule that generated the event) Tables listing the 50 most active and least active events Tables listing the 50 most active source and destination ports Tables listing the 25 most active source and destination hosts and host combinations. Tables listing the 25 most active source and destination hosts as well as the 25 most active source and host combinations Tables listing the most active events for each of the 25 most active destination hosts Tables listing the most active events for the 25 most active source and destination host combinations Quick Summary X X X X Detail Summary X X X X

X X X

X X X X X X

IMPORTANT! On the Defense Center, the report includes summary information for all the managed 3D Sensors with IPS that you include in the report. RNA-related event reports require the RNA component. If your deployment includes 3D Sensors with RNA and a Defense Center that manages the sensors,

Version 4.9.1

Sourcefire 3D System Administrator Guide

256

Working with Event Reports Working with Report Sections

Chapter 7

you can add the RNA Summary to RNA event, host, client application, service, and flow data reports. The RNA Summary includes: • RNA event statistics including total number of events, events in the last day and hour, total services, total hosts, total routers, total bridges, and host limit usage a list of events divided by event type with counts for the last hour and total number within the report range pie charts showing the percentage of events by protocol (for example, TCP , UDP or ICMP), service, and operating system ,

• •

Including an Image File
Requires: IPS or DC/ MDC You can add an image to your report which will be displayed after the summary report and before the drill down or table views. This can be useful for providing information best displayed in a visual, non-graphical format, or simply as a break between sections. You can use JPEG, PNG, and TIFF files as image files, but only JPEG and PNG graphics are supported in most browsers.

Version 4.9.1

Sourcefire 3D System Administrator Guide

257

Working with Event Reports Working with Report Options

Chapter 7

Defining the Report Sections
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin After you have determined which options you need for your report, use the following procedure to define the report section options. To define the Report Sections: 1. If a summary is available for the report type you selected, specify whether you want to include it as part of your report.

To include a summary with intrusion event-based reports, select quick or detailed. For a full description of the information provided in Quick and Detailed summaries, see Using Summary Reports on page 255. On a Defense Center with an RNA host license, to include a summary with an RNA-based report, select summary. For a full description of the information provided in the RNA summary, see Using Summary Reports on page 255. To exclude the summary, select none, which is the default.

2. If you want to include an image in the report, type the path to the image in the Include Image File text box, or navigate to a JPEG, PNG, or TIFF file. 3. Select the check boxes next to the sections of the workflow you want to include in the report. The options in this section depend on the workflow you selected in step 6. 4. Continue with Working with Report Options on page 258. TIP! Note that if you select a table view of events, the report is limited to 10,000 records as noted in step 6, regardless of the number of events.

Working with Report Options
Requires: IPS or DC/ MDC Report Options define the look of the report, and provide the option to email the report You can generate a report in PDF HTML or comma-separated value (CSV) format. , You can also generate the same report in multiple formats. Note that graphics are not available in the CSV format.

Version 4.9.1

Sourcefire 3D System Administrator Guide

258

Working with Event Reports Working with Report Options

Chapter 7

You can include a logo on your report. In PDF formats, the logo is included on every page. In HTML formats, the logo is included at the top of the report. You can add a description which will be included on the front page summary of the report. Access: Any Analyst/ Admin To define the report options: 1. Select the check boxes next to one or more output options for your report: PDF HTML, or CSV. ,

2. Optionally, for PDF and HTML reports, select a logo from the list of image files that were previously added to the system. See Including an Image File on page 257 for information about how to make more logos available to the report designer. 3. Optionally, for PDF and HTML reports, type a description in the Description field. You can use alphanumeric characters and spaces. The description appears in the report header. 4. Optionally, for PDF reports, type the text you want to include as the footer in the Custom Footer field. You can use 1 - 80 alphanumeric characters and spaces. 5. Optionally, you can specify that reports are automatically emailed after they are generated. To email a report, type one or more email addresses in a comma-separated list in the Email to field. IMPORTANT! You must make sure that the mail host is identified: Click Not available. You must set up your mail relay host. The System Policy page appears. Click Edit in the row for the system policy you want to modify. Click Email Notification. Type the name of your mail server in the Mail Relay Host field and click Save. Click Apply in the row for the system policy you changed and apply it to the appliance. The report is emailed from host_name@domain_name, where host_name is the host name of the appliance and domain_name is the name of the domain where you deployed the appliance.

Version 4.9.1

Sourcefire 3D System Administrator Guide

259

Working with Event Reports Using a Report Profile

Chapter 7

6. You have the following options: • To save the report profile, click Save Report Profile. When prompted, follow the instructions for your browser to save the report profile. The report profile is saved with the name you specified in the Report Name field. • To generate the report and save the report profile, click Generate Report. When prompted, follow the instructions for your browser to generate the report and save the report profile. • To see a PDF preview of your report, click Preview Report. When prompted, follow the instructions for your browser to display a PDF version of the report in the browser window. • On a Defense Center, to generate the report remotely, select the sensor where you want to run the report and click Run Remote Report. When prompted, follow the instructions for your browser to generate the report and save the report profile. IMPORTANT! The PDF HTML, and CSV selections for Output Options apply to , generated reports, not to report previews. When you click Preview Report, you see a PDF version of the report.

Using a Report Profile
Requires: IPS or DC/ MDC You can use report profiles to generate reports that contain the information that is important to you and your evaluation of the events generated for your network. You can use an predefined or existing report profile as a template for a new report profile. For information on editing a report profile, see Editing Report Profiles on page 263. If you want to generate a report for a specific set of events or a specific time period, populate the event view with the events you want to see in your report before opening the report designer. For details on using the event view, see the following sections: • • • • • • Viewing RNA Network Discovery and Host Input Events in the Analyst Guide Viewing Hosts in the Analyst Guide Viewing Services in the Analyst Guide Viewing Client Applications in the Analyst Guide Working with Flow Data and Traffic Profiles in the Analyst Guide Working with Intrusion Events in the Analyst Guide

Version 4.9.1

Sourcefire 3D System Administrator Guide

260

Working with Event Reports Using a Report Profile

Chapter 7

See the following sections for more information: • • • Generating a Report using a Report Profile on page 261 Editing Report Profiles on page 263 Deleting Report Profiles on page 263

Generating a Report using a Report Profile
Requires: IPS or DC/ MDC Access: Any Analyst/ Admin You can use report profiles to generate reports that contain the information that is important to you and your evaluation of the events generated for your network. To generate a report using a report profile: 1. Select Analysis & Reporting > Report Profiles. The Report Profiles page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

261

Working with Event Reports Using a Report Profile

Chapter 7

2. Click the name of the report profile you want to use. The Report Designer page loads the parameters defined for that selected report.

3. If necessary, click the time range to change it to include the events you want in your report. For more information, see Setting Event Time Constraints in the Analyst Guide. 4. Click Generate Report. The system generates the report. 5. Click Reports in the toolbar to display the Reporting page. The Reporting page appears, listing the report that you generated as well as any other previously generated reports. For information on managing generated reports, see Managing Generated Reports on page 237.

Version 4.9.1

Sourcefire 3D System Administrator Guide

262

Click Edit next to the profile that you want to delete.1 Sourcefire 3D System Administrator Guide 263 . Make changes to the report areas as needed.Working with Event Reports Using a Report Profile Chapter 7 Editing Report Profiles Requires: IPS or DC/ MDC You can create a new report profile by using a predefined or existing report profile as a template for a new report profile. Click Delete next to the profile that you want to delete. The report profile is deleted. The report profile is saved with the name you specified in the Report Name field. To delete a report profile: 1. Access: Any Analyst/ Admin To edit a report profile: 1. You can also edit a report profile to make changes to the resulting report. See the following sections for information: • • • Working with Report Information on page 248 Working with Report Sections on page 255 Working with Report Options on page 258 IMPORTANT! If you are creating a new report profile from a predefined or existing report profile. 3. Select Analysis & Reporting > Report Profiles. 4. Click Save Report Profile. The Report Designer page appears and contains the current settings for the report profile. and saving the report with the new values. follow the instructions for your browser to save the report profile. remember to change the name of the report profile in the Report Name field. modifying the field settings as appropriate. 2. 2. Use the following procedure to edit a report profile. Deleting Report Profiles Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete a report profile.9. Version 4. Select Analysis & Reporting > Report Profiles. When prompted. The Report Profiles page appears. The Report Profiles page appears.

you can manage the user accounts that can access the web interface on your Defense Center or 3D Sensor. you can also set up user authentication via an external authentication server. the process checks the local database to see if the user exists there and. rather than through the internal database. On the Defense Center. If the user’s account uses internal authentication. the appliance looks for a match for the user name and password in the local list of users. see the following sections: • • • Understanding Sourcefire User Authentication on page 264 Managing Authentication Objects on page 269 Managing User Accounts on page 299 Understanding Sourcefire User Authentication Requires: DC/MDC or 3D Sensor When a user logs into the web interface. For more information. if the user is not found locally. There are two kinds of authentication: internal and external. the authentication process checks the local database for this list. such as a Lightweight Directory Version 4. This process is called authentication. it queries an external server.Managing Users Chapter 8 Administrator Guide If your user account has Administrator access.1 Sourcefire 3D System Administrator Guide 264 . If the account uses external authentication.9.

9.Managing Users Understanding Sourcefire User Authentication Chapter 8 Access Protocol (LDAP) directory server or a Remote Authentication Dial In User Service (RADIUS) authentication server. you can control user permissions. or based on the default user access role you set in the server authentication object or in a system policy on the managing Defense Center. Users with external authentication receive the permissions either for the group or access list they belong to. for a list of users. Version 4. unless you change the user permissions manually. For users with either internal or external authentication.1 Sourcefire 3D System Administrator Guide 265 .

When any externally authenticated user logs in. you must configure an authentication object for each external authentication server where you want to request user information. the Sourcefire 3D System uses internal authentication to check user credentials when a user logs in. Internal authentication occurs when the username and password are verified against records in the internal Sourcefire 3D System database. you set the access settings when you create the user and you do not need to set default settings. If you want to use external authentication.9. Once an internally authenticated user converts to an externally authenticated user.1 Sourcefire 3D System Administrator Guide 266 . you cannot revert to internal authentication for that user. LDAP authentication and RADIUS authentication are types of external authentication. The authentication object contains your settings for connecting to and retrieving user data from that server.Note that you can only use one form of external authentication for an appliance. Understanding External Authentication Requires: DC External authentication occurs when the Defense Center or managed sensor retrieves user credentials from an external repository. the user credentials are managed in the internal database. Version 4. see the following sections: • • • Understanding Internal Authentication on page 266 Understanding External Authentication on page 266 Understanding User Privileges on page 267 Understanding Internal Authentication Requires: DC/MDC or 3D Sensor By default. in the order the servers are listed in the system policy. such as an LDAP directory server or RADIUS authentication server. You can then enable that object in a system policy on the managing Defense Center and apply the policy to an appliance to enable authentication. the same username exists for the user on the external server. the web interface checks each authentication server to see if that user is listed. If you do not enable external authentication when you create a user. and the user logs in using the password stored for that user on the external server. Because you manually create each internally authenticated user. IMPORTANT! Note that an internally authenticated user is converted to external authentication if you enable external authentication.Managing Users Understanding Sourcefire User Authentication Chapter 8 For more information.

You can push a system policy to a managed 3D Sensor to enable external authentication on that sensor. If you apply a local system policy (created on the sensor) to the sensor itself. the access rights for users are based on their membership in LDAP groups. but you cannot control the authentication object from the sensor’s web interface. If you want to disable external authentication on a managed 3D Sensor. see the following sections: • • Understanding LDAP Authentication on page 269 Understanding RADIUS Authentication on page 287 Understanding User Privileges The Sourcefire 3D System lets you allocate user privileges based on the user’s role. For more information on specific types of external authentication. but might never require access to administrative functions for the Sourcefire 3D System itself. external authentication is also disabled. They receive the Version 4. you set the access rights when you create them.9. the authentication objects are exported with the policy. You can grant Intrusion Event Analyst and RNA Event Analyst access privileges for analysts and reserve the Administrator role for the network administrator managing the Sourcefire 3D System. When you export a policy with external authentication enabled. You can then import the policy and object on another Defense Center. you can specify whether that user is internally or externally authenticated. If you do not modify the user’s rights. you can add or remove access rights for that user on the User Management page. Because you create internally authenticated users manually.Managing Users Understanding Sourcefire User Authentication Chapter 8 When you create a user. or Crossbeambased software sensors. For example. disable it in the system policy on the managing Defense Center and re-apply the policy to the sensor. you set a default access role for all users who are externally authenticated. After an externally authenticated user logs in for the first time. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. If you configured management of access rights through LDAP groups. The only configuration of external authentication on the sensor occurs when you select the type of authentication for a new user. 3Dx800 sensors. Intrusion Agents. TIP! You can use the Import/Export feature to export system policies. the user has only the rights granted by default. an analyst typically needs access to event data to analyze the security of monitored networks. Do not import policies with authentication objects onto 3D Sensors. In the system policy on the Defense Center.1 Sourcefire 3D System Administrator Guide 267 .

and view (but not delete or modify) health events.1 Sourcefire 3D System Administrator Guide 268 . except that they cannot delete events. unless one or more of those roles are mutually incompatible. They can also create incidents. Policy & Response (P&R) Administrator. and delete network change events. Restricted analysts can also be assigned the Policy & Response Administrator or Maintenance User roles. Users with the Administrator role also have Intrusion Event Analyst. generate reports. • • • • • Version 4. client applications.9. analyze. Intrusion Event Analysts can view. If the user does not belong to any lists and you have configured a default access role in the authentication object. If you configure default access in the authentication object. The Sourcefire 3D System supports the following user roles. but cannot be assigned the Intrusion Event Analyst or RNA Event Analyst roles. the user receives all assigned roles. review. RNA Event Analyst. analyze. and Maintenance access rights. and delete intrusion events and compliance and RUA events. If they do not belong to any groups and you have configured group access. those settings override the default access setting in the system policy. except that they cannot delete events. RNA Event Analysts can view. services. and RUA events. Intrusion Event Analysts (Read Only) have all the same rights as Intrusion Event Analysts. Restricted Event Analysts have the combined privileges of Intrusion Event Analysts and RNA Event Analysts. they receive the default user access rights configured in the authentication object for the LDAP server. hosts. but users are limited to subsets of that data. RNA analysts can also generate reports and view (but not delete or modify) health events. configure system policies and system settings. If you configure group access. depending on the features you have licensed: • Administrators can set up the appliance’s network configuration. Similarly. vulnerabilities. RNA Event Analysts (Read Only) have all the same rights as RNA Event Analysts. those settings override the default access setting in the system policy. the user receives the role that has the highest level of access. manage user accounts. compliance events. host attributes. listed in order of precedence. If a user is on the lists for two mutually incompatible roles. Note that on the Defense Center you cannot select Restricted Event Analyst as the default user role in the system policy. if you assign a user to specific user role lists in a RADIUS authentication object. the user receives that role.Managing Users Understanding Sourcefire User Authentication Chapter 8 default access rights for the group that they belong to that has the highest level of access. but you can modify a user’s settings via the User Management page to grant this level of access.

When you create an authentication object. Managing Authentication Objects Requires: DC Authentication objects are server profiles for external authentication servers. you define settings that let you connect to an authentication server. rather than having to change them on the local appliances as well as on any other application that uses them. policies. directory on your network that organizes objects. in a centralized location. host statistics. allows you to set up a . Note that maintenance administrators do not have access to the functions in the Policy & Response menu and can only access the dashboard from the Analysis & Reporting menu. you can configure shell access authentication.1 Sourcefire 3D System Administrator Guide 269 . Maintenance Administrators can access monitoring functions (including health monitoring. and responses. You also select the directory context and search criteria you want to use to retrieve user data from the server.Managing Users Managing Authentication Objects Chapter 8 • • Policy & Response Administrators can manage intrusion rules. you can change them in one place. and system logs) and maintenance functions (including task scheduling and backing up the system). policies. Creating LDAP Authentication Objects Requires: DC You can create LDAP authentication objects to provide user authentication services for an appliance. as well as compliance rules. containing connection settings and authentication filter settings for those servers. See the following sections for details on these tasks: • • • • • • • • Understanding LDAP Authentication on page 269 Creating LDAP Authentication Objects on page 269 LDAP Authentication Object Examples on page 281 Editing LDAP Authentication Objects on page 286 Creating RADIUS Authentication Objects on page 287 RADIUS Authentication Object Examples on page 295 Editing RADIUS Authentication Objects on page 298 Deleting Authentication Objects on page 298 Understanding LDAP Authentication LDAP or the Lightweight Directory Access Protocol. such as user credentials. If you ever need to change a user's credentials. and delete authentication objects on the Defense Center. Version 4. manage. You can create. performance data. and responses.9. Multiple applications can then access those credentials and the information used to describe them. Optionally.

Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. For none or TLS. If you select SSL encryption. Select Operations > Configuration > Login Authentication. 6. see Configuring Administrative Shell Access on page 278.Managing Users Managing Authentication Objects Chapter 8 Note that to create an authentication object. you first specify the primary and backup server and server port where you want the local appliance (3D Sensor or Defense Center) to connect for authentication. you need TCP/IP access from your local appliance to the authentication server where you want to connect. Version 4. the port uses the default value of 389. For more information. see Configuring Access Settings by Group on page 275. For more information. 5. If you are using a Microsoft Active Directory server or if your LDAP server uses a UI access attribute or a shell access attribute other than uid.1 Sourcefire 3D System Administrator Guide 270 . see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. 3. 4. Identifying the LDAP Authentication Server Requires: DC When you create an authentication object. Your changes are saved. Click Create Authentication Object. 8. To create an authentication object: Access: Admin 1. the port resets to the default value. configure authentication settings for shell access. see Configuring Attribute Mapping on page 274.9. Optionally. Test your configuration by entering the name and password for a user who can successfully authenticate. For more information. the port uses the default of 636. For more information. 2. For more information. see Identifying the LDAP Authentication Server on page 270. Note that if you change the encryption method after specifying the port. For more information. Configure authentication settings to build a search request that retrieves the users you want to authenticate. see Configuring LDAP Authentication Settings on page 271. Optionally. see Testing User Authentication on page 280. Specify a user name template to format the usernames that users enter on login. 7. The Create Authentication Object page appears. configure LDAP groups to use as the basis for default access role assignments. specify the appropriate attributes for your server. The Login Authentication page appears. For more information. Identify the authentication server where you want to retrieve user data for external authentication.

2. IPv6 addresses are not supported. however. Version 4. If. Continue with Configuring LDAP Authentication Settings. the host name in the certificate must match the host name used in this field. modify the port used by the primary authentication server in the Primary Server Port field. In addition. Optionally.9. you can set a timeout for the connection attempt to the primary server. Optionally. the failover to the backup server does not occur. the appliance would query the backup server. the primary server has LDAP disabled. 6. If the number of seconds indicated in the Timeout field (or the timeout on the directory server) elapses without a response from the primary authentication server. 5. Configuring LDAP Authentication Settings Requires: DC If you specify a backup authentication server. for example. 3. the appliance then queries the backup server. type the IP address or host name for the backup server where you want to obtain authentication data in the Backup Server Host Name/IP Address field. 4. Select LDAP from the Authentication Method drop-down list. modify the port used by the primary authentication server in the Backup Server Port field.Managing Users Managing Authentication Objects Chapter 8 To identify an LDAP authentication server: Access: Admin 1. Optionally. If LDAP is running on the port of the primary LDAP server and for some reason refuses to service the request (due to misconfiguration or other issues). IMPORTANT! If you are using a certificate to connect via TLS or SSL. Type a name and description for the authentication server in the Name and Description fields. 7.1 Sourcefire 3D System Administrator Guide 271 . Type the IP address or host name for the primary server where you want to obtain authentication data in the Primary Server Host Name/IP Address field.

the user login request is authenticated. to refer to a user object. you can use the address specification syntax documented in the Internet RFC 822 (Standard for the Format of ARPA Internet Text Messages) specification when referencing a user name that contains a domain.Managing Users Managing Authentication Objects Chapter 8 To allow an appliance to connect to the LDAP server. For the authentication method specific parameters. you might type JoeSmith@security. periods (. the base DN will have a basic structure indicating the company domain and operational unit. Remember that the distinguished name for the user you specify must be unique to the directory information tree for the directory server. or base DN.example. see Testing User Authentication on page 280. Typically.10. you can use the LDAP naming standards and filter and attribute syntax defined in the RFCs listed in the Lightweight Directory Access Protocol (v3): Technical Specification. filter (cn=F*). that the local appliance should search by providing a base distinguished name. the local appliance queries using the base filter to test it and indicates whether or not the filter appears to be correct. or directory tree. To allow the local appliance to access the user objects.). For example.9.ou=security. For example. When the local appliance searches the LDAP directory server to retrieve user information on the authentication server. the connection fails.dc=com when using Microsoft Active Directory Server. if you enter 10.com in the certificate. If one of the objects has a matching username and password. the local appliance checks the uid attribute value for each object in the directory tree indicated by the base DN you set. Changing the name of the server in the authentication profile to computer1. The base filter focuses your search by only retrieving objects in the base DN that have the attribute value set in the filter.example. and hyphens (-) but otherwise only alphanumeric characters are supported. it needs a starting point for that search. Examples of syntax are provided throughout this procedure.com causes the connection to succeed.1 Sourcefire 3D System Administrator Guide 272 . Enclose the base filter in parentheses. or Secure Sockets Layer (SSL) encryption.dc=com. you need to select the encryption method for the connection. Version 4. When you save the authentication object. You can also add a base filter that sets a specific value for a specific attribute. dc=example. RFC 3377 . For example. you must supply user credentials for a user with appropriate rights to the authentication objects you want to retrieve. If your LDAP Server uses a Pluggable Authentication Module (PAM) login attribute of uid. You can choose no encryption.10. to filter for only users with a common name starting with F use the . Transport Layer Security (TLS). To test your base filter more specifically by entering a test username and password. the Security organization of the Example company might have a base DN of ou=security. You can specify the namespace.250 as the server and computer1.dc=example. Note that when you set up an authentication object to connect to a Microsoft Active Directory Server. LDAP usernames can include underscores (_). For example. the name of the LDAP server in the certificate must match the name that you use to connect.com rather than the equivalent user distinguished name of cn=JoeSmith.example. Note that if you are using a certificate to authenticate when connecting via TLS or SSL.

IMPORTANT! Note that if you change the encryption method after specifying a port. Version 4. select None. Select one of the following encryption modes: • • • To connect using Secure Sockets Layer (SSL).9. Type the number of seconds that should elapse before rolling over to the backup connection in the Timeout field.1 Sourcefire 3D System Administrator Guide 273 . if you selected TLS or SSL encryption and you want to use a certificate to authenticate. For example.dc=example. To connect using Transport Layer Security (TLS). to set a user name template for the Security organization of the Example company. For example.Managing Users Managing Authentication Objects Chapter 8 Selecting a user name template lets you indicate how user names entered on login should be formatted. to authenticate names in the Security organization at the Example company. When a user enters a user name into the login page. 2. 4. you reset the port to the default value for that method. by mapping the string conversion character (%s) to the value of the shell access attribute for the user. the port uses the default value of 389. To connect without encryption. A message appears. the name is substituted for the string conversion character and the resulting distinguished name is used to search for the user credentials. To configure the authentication method for a server: Access: Admin 1. If you select SSL encryption. click Browse to browse to the location of a valid TLS or SSL certificate or type the path to the certificate in the SSL Certificate Upload Path field. For none or TLS. type ou=security. indicating a successful certificate upload.example.dc=com. Type the base distinguished name for the LDAP directory you want to access in the Base DN field. The user name template is the format for the distinguished name used for authentication. the port uses the default of 636. 3. you would enter %s@security. select SSL. Optionally. select TLS.com.

into the User Name Template field. Version 4. 6. if you are connecting to an OpenLDAP Server where user objects have a uid attribute and the object for the administrator in the Security division at our example company has a uid value of NetworkAdmin. You can use any attribute. 9. type the attribute type.1 Sourcefire 3D System Administrator Guide 274 . you do not need to specify a UI access attribute. the local appliance (3D Sensor or Defense Center) checks the value of the uid attribute for each user record on the LDAP Server to see if it matches the user name.9. 7.com. For a Microsoft Active Directory server. the local appliance checks the user name entered on login against the attribute value of uid. with the string conversion character (%s) in place of the shell access attribute value. Configuring Attribute Mapping Requires: DC If your LDAP Server uses a default UI access attribute of uid. If your LDAP server uses uid. you must explicitly set the Shell Access Attribute to match the attribute value. Type the user distinguished name. in the Base Filter field. Continue with Configuring Attribute Mapping. type (physicalDeliveryOfficeName=NewYork).dc=example. a comparison operator. to authenticate all users who work in the Security organization of our example company by connecting to an OpenLDAP server where the shell access attribute is uid. and the attribute value you want to use as a filter. Re-type the password in the Confirm Password field.dc=com. For example. For example. when a user logs in. you can map a different attribute for the local appliance to search. Valid user names are unique. Setting a UI access attribute tells the local appliance to match the value of that attribute rather than the value of the uid attribute.ou=security.dc=example. If you want to filter on uid. you would type uid=%s. Type the distinguished name and password for the user whose credentials should be used to validate access to the LDAP directory in the User Name and Password fields. if the user objects in a directory tree have a physicalDeliveryOfficeName attribute and users in the New York office have an attribute value of NewYork for that attribute. 8.ou=security.example. enclosed in parentheses. you could type %s@security. If the shell access attribute for a server is something other than uid. For example. and do not begin with a numeral. if the value of the attribute is a valid user name for either the Sourcefire 3D System web interface or for shell access. to retrieve only users in the New York office. The Pluggable Authentication Module (PAM) login attribute of your LDAP Server acts as a shell access attribute. However. you would type uid=NetworkAdmin. have no spaces and no periods in them.dc=com in the User Name Template field. To set a filter that retrieves only specific objects within the namespace you specified as the Base DN.Managing Users Managing Authentication Objects Chapter 8 5.

Configuring Access Settings by Group Requires: DC If you prefer to base default access settings on a user’s membership in an LDAP group. 2. you have two choices: • • If you want to configure user default roles based on LDAP group membership. you may want to use the UI Access Attribute to retrieve users. use the 3. To retrieve users for shell access. Any group you reference must exist on the LDAP server. For the next step. and dynamic LDAP groups are groups where membership is determined by creating an LDAP search that retrieves group users based on user object attributes. For example. sAMAccountName shell access attribute to retrieve shell access users by typing sAMAccountName in the Shell Access Attribute field. the Sourcefire 3D System dynamically checks the LDAP directory and assigns default access rights according to the user’s current group membership. Group access settings for a role only affect users who are members of the group. type the attribute type you want to filter on in the Shell Access Attribute field. If you are not using LDAP groups for authentication. you can specify distinguished names for existing groups on your LDAP server for each of the access roles used by your Sourcefire 3D System. type the attribute type in the UI Access Attribute field. Instead. on a Microsoft Active Directory Server.9. For example. To retrieve users based on an attribute instead of the Base DN and Base Filter. You can reference static LDAP groups or dynamic LDAP groups.1 Sourcefire 3D System Administrator Guide 275 . When you do so. because there may not be a uid attribute on Active Directory Server user objects.Managing Users Managing Authentication Objects Chapter 8 To configure attribute mapping for a server: Access: Admin 1. you can configure a default access setting for those users detected by LDAP that do not belong to any specified groups. continue with Configuring Access Settings by Group. you can search the userPrincipalName attribute by typing userPrincipalName in the UI Access Attribute field. Version 4. When a user logs in. continue with Configuring Administrative Shell Access on page 278. Static LDAP groups are groups where membership is determined by group object attributes that point to specific users. on a Microsoft Active Directory Server.

For this reason. the default access role defined in the Group Controlled Access Roles section is granted to the user. the Authentication Method column on the User Management page provides a status of External . IMPORTANT! If you use a dynamic group. the Sourcefire 3D System limits the number of recursions of a search to four to prevent search syntax errors from causing infinite loops. When you modify the access rights for an externally authenticated user. You can. the user receives the access role for the group with the highest access as a minimum access role. If you configure any group settings. • • • You cannot remove the minimum access rights for users assigned an access role because of LDAP group membership through the Sourcefire 3D System user management page. however.1 Sourcefire 3D System Administrator Guide 276 . new users belonging to specified groups inherit the minimum access setting for the groups where they are members. the LDAP query is used exactly as it is configured on the LDAP server.Locally Modified. assign additional rights. Version 4. the Sourcefire 3D System authenticates the user against the LDAP server and then grants user rights based on the default minimum access role set in the system policy. the user is assigned the default minimum access role specified in the Group Controlled Access Roles section of the authentication object. If a user’s group membership is not established in those recursions. If a new user does not belong to any specified groups.9. when a new user logs in. If a user belongs to more than one configured group.Managing Users Managing Authentication Objects Chapter 8 The access rights granted when a user logs into the Sourcefire 3D System depends on the LDAP configuration: • If no group access settings are configured for your LDAP server.

type cn=itgroup.Managing Users Managing Authentication Objects Chapter 8 To base access defaults on LDAP group membership: Access: Admin 1. rule and policy configuration. to authenticate names in the Security organization at the Example company. For example. 3. 2.ou=groups. 4. dc=example.dc=example. Type the distinguished name for the LDAP group containing users who should at minimum have access to analysis and reporting features. Type the distinguished name for the LDAP group containing users who should at minimum have access to rules and policy configuration in the Policy & Response Administrator Group DN field. dc=com.ou=groups. system management. For example. to authenticate names in the information technology organization at the Example company. dc=example. type cn=itgroup. to authenticate names in the Intrusion Event Analyst group at the Example company.9. Type the distinguished name for the LDAP group containing users who should at minimum have access to monitoring and maintenance features in the Maintenance Group DN field. Version 4.ou=groups. to authenticate names in the information technology organization at the Example company. dc=com.dc=com.dc=example. type cn=securitygroup.ou=groups. and all maintenance features in the Administrator Group DN field. For example. Type the distinguished name for the LDAP group containing users who should at minimum have access to IPS analysis features in the Intrusion Event Analyst Group DN field.1 Sourcefire 3D System Administrator Guide 277 . For example.dc=com. type cn=ipsanalystgroup.

see Configuring Authentication Profiles on page 329. Type the distinguished name for the LDAP group containing users who should at minimum have access to RNA analysis features in the RNA Event Analyst Group DN field. Type the distinguished name for the LDAP group containing users who should at minimum have access to RNA analysis features in the RNA Event Analyst Group DN (Read Only) field. For more information on user access roles. For example. type the LDAP attribute that contains the LDAP search string used to determine membership in a dynamic group in the Group Member URL Attribute field. type member. Version 4. see Adding New User Accounts on page 300. 6. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role list. For example. if the member attribute is used to indicate membership in the static group you reference for default Policy & Response Administrator access. Type the distinguished name for the LDAP group containing users who should at minimum have access to IPS analysis features in the Intrusion Event Analyst Group DN (Read Only) field.9. Specify a search filter that will retrieve entries for users you want to grant shell access. 7. or Crossbeam-based software sensors. 9. 11. type memberURL. Intrusion Agents. Configuring Administrative Shell Access Requires: DC You can also use the LDAP directory server to authenticate accounts for shell access on your local appliance (3D Sensor or Defense Center). For more information on managing authentication object order. 10.Managing Users Managing Authentication Objects Chapter 8 5. 8. 3Dx800 sensors. Type the LDAP attribute that designates membership in a static group in the Group Member Attribute field. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. Note that you can only configure shell access for the first authentication object in your system policy.1 Sourcefire 3D System Administrator Guide 278 . if the memberURL attribute contains the LDAP search that retrieves members for the dynamic group you specified for default Admin access. Continue with Configuring Administrative Shell Access on page 278. Optionally.

the shell is reset. if all network administrators have a manager attribute which has an attribute value of shell. a warning displays when you save the authentication object to confirm that you meant to leave the filter blank.9. a comparison operator. Make sure that you restrict the list of users with shell access appropriately. Normally. The Same as Base Filter check box allows you to search more efficiently if all users qualified in the base DN are also qualified for shell access privileges. in the Shell Access Filter field. To set a filter to retrieve administrative user entries based on attribute value. the same query would be run twice. the LDAP query to retrieve users combines the base filter with the shell access filter. IMPORTANT! If you choose not to specify a shell access filter. using the same home directory. Continue with Testing User Authentication. If the shell access filter was the same as the base filter. which is unnecessarily time-consuming. or select Same as Base Filter to use the same filter you specified when configuring authentication settings. Addition and deletion of shell access users occurs only on the LDAP server. even after they log in. you can set a base filter of (manager=shell). the directory remains. If the user then is re-enabled. enclosed in parentheses. 2. Note that a home directory for each shell user is created on login. WARNING! All shell users have sudoers privileges. and when an LDAP shell access user account is disabled (by disabling the LDAP connection).Managing Users Managing Authentication Objects Chapter 8 With the exception of the root account. Version 4. and the filter you set here determines which set of users on the LDAP server can log into the shell. but the user shell is set to /bin/false in /etc/password to disable the shell. Shell users should log in using usernames with all lowercase letters. You can use the Same as Base Filter option to run the query only once for both purposes.1 Sourcefire 3D System Administrator Guide 279 . shell access is controlled entirely though the shell access attribute you set. For example. and the attribute value you want to use as a filter. To configure shell account authentication: Access: Admin 1. Shell users are not configured as local users on the appliance. type the attribute type.

type JSmith. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. use the value for that attribute as the user name. TIP! If you mistype the name or password of the test user. you must apply a system policy with that object enabled to the appliance. In the User Name and Password fields. the test fails even if the server configuration is correct. you can enter the value for the uid attribute for the user you want to test with. For the user name. Test the server configuration without the additional test parameters first.9. To view details of test output. 4. If that succeeds supply a user name and password to test with the specific user. If the test succeeds. To test user authentication: Access: Admin 1. Note that testing the connection to servers with more than 1000 users only returns 1000 users because of UI page size limitations. The Login Authentication page appears. either indicating success of the test or detailing what settings are missing or need to be corrected.1 Sourcefire 3D System Administrator Guide 280 . you can specify user credentials for a user who should be able to authenticate to test those settings.Managing Users Managing Authentication Objects Chapter 8 Testing User Authentication Requires: DC After you configure LDAP server and authentication settings. Click Test. You can also specify a fully-qualified distinguished name for the user. To enable LDAP authentication using the object on an appliance. A message appears. 2. with the new object listed. 3. Version 4. select Show Details. For more information. to test to see you can retrieve the JSmith user credentials at our example company. click Save. For example. If you are connecting to a Microsoft Active Directory Server and supplied a shell access attribute in place of uid in Configuring Attribute Mapping on page 274. type the uid value or shell access attribute value and password for the user whose credentials should be used to validate access to the LDAP directory.

see the following sections: • • • OpenLDAP Example on page 281 Microsoft Active Directory Server Example on page 282 Sun Directory Server Example on page 284 OpenLDAP Example Requires: DC The following figures illustrate parts of a sample LDAP login authentication object for an OpenLDAP directory server with an IP address of 10. with a backup server that has an IP address of 10.3. • OU=security. This example illustrates important aspects of LDAP configuration. Version 4.1 Sourcefire 3D System Administrator Guide 281 .9.10.DC=example.10.4.DC=com for the security organization in This example shows a connection using a base distinguished name of the information technology domain of the Example company.3.DC=it.5. Note that the connection uses port 389 for access and that connections to the server time out after 30 seconds of disuse.Managing Users Managing Authentication Objects Chapter 8 LDAP Authentication Object Examples Requires: DC For sample configurations showing how different configuration options might be used for connections to specific directory server types.

to indicate the template used to format user names retrieved from the server.5.11. Note that all objects in the directory are checked because no base filter is set. the connection uses port 389 for access and connections to the server time out after 30 seconds of disuse (or the timeout period set on the LDAP server).1 Sourcefire 3D System Administrator Guide 282 . no UI access attribute is specified.3.Managing Users Managing Authentication Objects Chapter 8 • Because this is an OpenLDAP server that uses CN as a part of each user’s name. followed by the base distinguished name for the server directory. Version 4. with a backup server that has an IP address of 10. Microsoft Active Directory Server Example Requires: DC The following figure illustrates a sample LDAP login authentication object for a Microsoft Active Directory Server with an IP address of 10. the CN attribute is set as the shell access attribute. the user name template for the connection uses CN=%s. Aspects of this example illustrate important differences in this LDAP configuration from the configuration discussed in the OpenLDAP Example on page 281. A shell access filter has been applied to this configuration. • • • To support shell access.4. Like the OpenLDAP server.11.9.3. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account. The Sourcefire 3D System checks the uid attribute of each object in the directory indicated by the distinguished name against the username for each user who logs into the system. Because the user names to be retrieved are contained in the default uid attribute.

DC=it. Note that the configuration includes a UI Access Attribute of userPrincipalName. • • In addition. the Sourcefire 3D System checks the userPrincipalName attribute for each object for matching user names when a user attempts to log into the Sourcefire 3D System. a Shell Access Attribute of sAMAccountName causes each sAMAccountName attribute to be checked for all objects in the directory for matches when a user logs into a shell account on the appliance. As a result. the Sourcefire 3D System checks attributes for all objects in the directory indicated by the base distinguished name. because this server is a Microsoft Active Directory server. this example shows a connection using a base distinguished name of OU=security. Again. because no base filter is applied to this server. the user name template for the connection uses address specification syntax documented in RFC 822 rather than the typical LDAP naming syntax.1 Sourcefire 3D System Administrator Guide 283 .DC=com for the security organization in the information technology domain of the Example company. it uses the userPrincipalName attribute to store user names rather than the uid attribute.DC=example. Version 4. However.9. • Because this is a Microsoft Active Directory Server.Managing Users Managing Authentication Objects Chapter 8 • Like the OpenLDAP server.

12.4. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account. a shell access attribute value of sAMAccountName must be set for shell access to work on a Microsoft Active Directory server. • As in the OpenLDAP server.DC=example. as noted above. However. a shell access filter has been specified for this server.3.12. Version 4.DC=com.5.DC=it.9.3. Sun Directory Server Example Requires: DC The following figure illustrates a sample LDAP login authentication object for a Sun Directory Server with an IP address of 10.Managing Users Managing Authentication Objects Chapter 8 • This example also has group settings in place. The maintenance role is automatically assigned to all members of the group with a member group attribute and the base domain name of CN=maintenance. with a backup server that has an IP address of 10.1 Sourcefire 3D System Administrator Guide 284 .

However. Using Same as Base Filter allows a more efficient search query if and only if all users qualified in the base DN are also qualified for shell access privileges. The filter restricts the users retrieved from the server to those with a common name ending in smith.DC=it.DC=com for the security organization in the information technology domain of the Example company. • To allow shell access on the server. Version 4. • • The user name template shown uses the uid attribute value as the user name. the Server Port is set to 636. allowing all users with a common name ending in smith to log in using a shell account as well.1 Sourcefire 3D System Administrator Guide 285 . A certificate has been uploaded to allow the SSL connection. • This example shows a connection using a base distinguished name of OU=security. Because user names can be retrieved from the uid attribute on this server. the uid attribute is named as the Shell Access Attribute and the Same as Base Filter option for the shell access filter is set. no UI access attribute is specified.DC=example.Managing Users Managing Authentication Objects Chapter 8 Settings in the example illustrate important differences in this LDAP configuration from the configuration discussed in Microsoft Active Directory Server Example on page 282: • Because the Encryption for the connection is set to SSL.9. Note that all objects in the directory are checked because no base filter is set. note that this server does have a base filter of (cn=*smith). The Sourcefire 3D System checks the uid attribute of each object in the directory indicated by the distinguished name against the user name for each user who logs into the system.

Click Edit next to the object you want to edit. see the following topics: • • • • • Creating LDAP Authentication Objects on page 269 Configuring LDAP Authentication Settings on page 271 Configuring Attribute Mapping on page 274 Configuring Administrative Shell Access on page 278 Testing User Authentication on page 280 IMPORTANT! If you previously uploaded a certificate and want to replace it. 3. For more information.9.1 Sourcefire 3D System Administrator Guide 286 . Select Operations > Configuration > Login Authentication.Managing Users Managing Authentication Objects Chapter 8 Editing LDAP Authentication Objects Requires: DC You can edit an existing authentication object. 2. The Login Authentication page appears. To edit an authentication object: Access: Admin 1. Version 4. upload the new certificate and re-apply the system policy to your appliances to copy over the new certificate. The Create Authentication Object page appears. If the object is in use in a system policy. the settings in place at the time the policy was applied stay in effect until you re-apply the policy. Modify the object settings as needed.

Note that to create an authentication object. The Create Authentication Object page appears. Click Save. and account for user access to network resources. You can modify a user’s roles. Creating RADIUS Authentication Objects Requires: DC When you create a RADIUS authentication object. you need TCP/IP access from your local appliance to the authentication server where you want to connect. or failing that. You also grant user roles to specific and default users. Select Operations > Configuration > Login Authentication. Optionally. The Sourcefire 3D System implementation of RADIUS supports the use of SecurID® tokens. you define settings that let you connect to an authentication server. 2. unless the settings are granted through the user lists in the authentication object. As long as SecurID is configured correctly to authenticate users outside the Sourcefire 3D System. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. you need to define those custom attributes. the user receives the roles specified for that user in the authentication object. authorize. if needed. those users can log into a Sourcefire 3D System appliance using their pin plus the SecurID token without any additional configuration on the appliance. When you configure authentication by a server using SecurID. Your changes are saved and the Login Authentication page re-appears. Version 4. To create an authentication object: Access: Admin 1. the default access role you selected in the authentication object. the system policy. For more information. When a user authenticated on a RADIUS server logs in for the first time.Managing Users Managing Authentication Objects Chapter 8 4. you can also configure shell access authentication. Click Create Authentication Object.1 Sourcefire 3D System Administrator Guide 287 . You can create an authentication object for any RADIUS server that conforms to RFC 2865. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. or if the user is not listed for any of the user roles. If your RADIUS server returns custom attributes for any users you plan to authenticate. Understanding RADIUS Authentication Requires: DC The Remote Authentication Dial In User Service (RADIUS) is an authentication protocol used to authenticate. users authenticated against that server append the SecurID token to the end of their SecurID pin and use that as their password when they log into a Sourcefire appliance.9. The Login Authentication page appears.

Test your configuration by entering the name and password for a user who should successfully authenticate. For more information. define those attributes. see Configuring RADIUS User Roles on page 290. 7. Identify the primary and backup authentication servers where you want to retrieve user data for external authentication and set timeout and retry values. 6. see Configuring RADIUS Connection Settings on page 288. If you specify a backup authentication server. Optionally. see Configuring Administrative Shell Access on page 292. the appliance then re-queries the primary server. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. configure administrative shell access. For more information. IMPORTANT! For FreeRADIUS to function correctly. If the number of seconds indicated in the Timeout field (or the timeout on the directory server) elapses without a response from the primary authentication server. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. Configuring RADIUS Connection Settings Requires: DC When you create a RADIUS authentication object. Optionally. If. Set the default user role. the primary server has RADIUS disabled. If the profiles for any of the users to authenticate return custom RADIUS attributes.9. 4. 5. Your changes are saved. the appliance would query the backup server. For more information. the appliance then rolls over to the backup server. For more information. see Defining Custom RADIUS Attributes on page 293. After the appliance re-queries the primary authentication server the number of times indicated by the Retries field and the number of seconds indicated in the Timeout field again elapses without a response from the primary authentication server. see Testing User Authentication on page 294.1 Sourcefire 3D System Administrator Guide 288 . specify the users or user attribute values for users that you want to receive specific Sourcefire 3D System access roles. For more information.Managing Users Managing Authentication Objects Chapter 8 3. For more information. If RADIUS is running on the port of the primary RADIUS server and for some reason refuses to service the request (due to Version 4. you can set a timeout for the connection attempt to the primary server. for example. you need to open both ports 1812 and 1813 on your firewall and on the FreeRADIUS server. you first specify the primary and backup server and server port where you want the local appliance (3D Sensor or Defense Center) to connect for authentication.

the failover to the backup server does not occur. Type the IP address or host name for the primary RADIUS server where you want to obtain authentication data in the Primary Server Host Name/IP Address field. 6. Type the secret key for the backup RADIUS authentication server in the RADIUS Secret Key field. Type the IP address or host name for the backup RADIUS authentication server where you want to obtain authentication data in the Backup Server Host Name/IP Address field. 5. Version 4. IMPORTANT! IPv6 addresses are not supported. 4. however. Type the secret key for the primary RADIUS authentication server in the RADIUS Secret Key field. Type the number of seconds that should elapse before retrying the connection in the Timeout field. 8. modify the port used by the backup RADIUS authentication server in the Backup Server Port field. Optionally. To identify a RADIUS authentication server: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 289 .Managing Users Managing Authentication Objects Chapter 8 misconfiguration or other issues). Type a name and description for the authentication server in the Name and Description fields. Select RADIUS from the Authentication Method drop-down list. 9. 3. 2. modify the port used by the primary RADIUS authentication server in the Primary Server Port field.9. 7. Optionally.

if you know all users who should be RNA Analysts have the value Analyst for their User-Category attribute. and you must remove the assigned user right on the user management page. You can assign a default user role (or roles) to be assigned to any users that are authenticated externally but not listed for a specific role. you can type User-Category=Analyst in the RNA Analyst List field to grant that role to those users. Note that you need to define any custom attributes before you use them to set user role membership.9. however. that user receives all assigned access roles. assign additional rights. You can select multiple roles on the Default User Role list. For more information on the user roles supported by the Sourcefire 3D System. see Configuring User Roles on page 304. you can also configure a default access setting for those users detected by RADIUS that are not specified for a particular role. you must not only move the user from one list to another in the RADIUS Specific Parameters section or change the user’s attribute on the RADIUS server. For example. to identify users who should receive a particular user role. For more information. WARNING! If you want to change the minimum access setting for a user. • • You can also use attribute-value pairs. You cannot remove the minimum access rights for users assigned an access role because of RADIUS user list membership through the Sourcefire 3D System user management page. the user is assigned those access roles. When you do so. when a new user logs in.1 Sourcefire 3D System Administrator Guide 290 . When a user logs in. the Sourcefire 3D System checks the RADIUS server and grants access rights depending on the RADIUS configuration: • If specific access settings are not configured for a user and a default access role is not selected. you must reapply the system policy. rather than usernames.Managing Users Managing Authentication Objects Chapter 8 10. 11. Type the number of times the primary server connection should be tried before rolling over to the backup connection in the Retries field. Continue with Configuring RADIUS User Roles. Version 4. If a new user is not specified on any lists and default access roles are selected in the Default User Role list of the authentication object. If you add a user to the list for one or more specific role. Configuring RADIUS User Roles Requires: DC You can specify the access roles for existing users on your RADIUS server by listing the user names for each of the access roles used by your Sourcefire 3D System. see Defining Custom RADIUS Attributes on page 293. You can. the Sourcefire 3D System authenticates the user against the RADIUS server and then grants user rights based on the default access role (or roles) set in the system policy.

jdoe in the Administrator List field. 3. For example. type jsmith. who should at minimum receive access to monitoring and maintenance features in the Maintenance List field. separated by commas. separated by commas. 2. to grant the Administrator role to the users jsmith and jdoe. who should at minimum receive access to analysis and reporting features. system management. separated by commas. Type the name of each user or each identifying attribute-value pair. Type the name of each user or each identifying attribute-value pair. Type the name of each user or each identifying attribute-value pair. Type the name of each user or each identifying attribute-value pair. 5.1 Sourcefire 3D System Administrator Guide 291 . separated by commas.who should at minimum receive access to rules and policy configuration in the Policy & Response Administrator List field. 4. Type the name of each user or each identifying attribute-value pair. who should at minimum receive access to IPS analysis features in the Intrusion Event Analyst List field. separated by commas. rule and policy configuration. and all maintenance features in the Administrator List field. type User-Category=Maintenance For example. Version 4. who should at minimum receive access to IPS analysis features in the Intrusion Event Analyst (Read Only) List field. to grant the Maintenance role to all users with a in the Maintenance List field.Managing Users Managing Authentication Objects Chapter 8 To base access on user lists: Access: Admin 1.9. User-Category value of Maintenance.

the directory remains. 9.9. using the same home directory. 8. but the user shell is set to /bin/false in / etc/password to disable the shell. see Configuring Authentication Profiles on page 329. the shell is reset. 7. separated by commas. the shell access list you set on the RADIUS authentication object entirely controls shell access on the appliance. For more information on user access roles. For more information on managing authentication object order. WARNING! All shell users have sudoers privileges. Shell users should log in using usernames with all lowercase letters. Make sure that you restrict the list of users with shell access appropriately. Note that you can only configure shell access for the first authentication object in your system policy. and when an RADIUS shell access user account is disabled (by disabling the RADIUS connection). Version 4. Continue with Configuring Administrative Shell Access. With the exception of the root account. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. see Configuring User Roles on page 304.1 Sourcefire 3D System Administrator Guide 292 . separated by commas. Type the name of each user or each identifying attribute-value pair.Managing Users Managing Authentication Objects Chapter 8 6. Note that a home directory for each shell user is created on login. Type the name of each user or each identifying attribute-value pair. Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role list. who should at minimum receive access to RNA analysis features in the RNA Event Analyst List field. If the user then is re-enabled. Specify user names for users you want to grant shell access. Shell users are configured as local users on the appliance when the system policy is applied. Configuring Administrative Shell Access Requires: DC You can also use the RADIUS server to authenticate accounts for shell access on your local appliance (3D Sensor or Defense Center). who should at minimum receive access to RNA analysis features in the RNA Event Analyst (Read Only) List field.

Managing Users Managing Authentication Objects

Chapter 8

To configure shell account authentication: Access: Admin 1. Type the usernames, separated by commas, in the Administrator Shell Access User List field. IMPORTANT! If you choose not to specify a shell access filter, a warning displays when you save the authentication object to confirm that you meant to leave the filter blank. 2. Continue with Defining Custom RADIUS Attributes on page 293.

Defining Custom RADIUS Attributes
Requires: DC
dictionary file in /etc/radiusclient/ and you plan to use those attributes to

If your RADIUS server returns values for attributes not included in the

set user roles for users with those attributes, you need to define those attributes in the login authentication object. You can locate the attributes returned for a user by looking at the user’s profile on your RADIUS server. When you define an attribute, you provide the name of the attribute, which consists of alphanumeric characters. Note that words in an attribute name should be separated by dashes rather than spaces. You also provide the attribute ID, which should be an integer and should not conflict with any existing attribute IDs in the etc/radiusclient/dictionary file. You also specify the type of attribute: string, IP address, integer, or date. As an example, if a RADIUS server is used on a network with a Cisco router, you might want to use the Ascend-Assign-IP-Pool attribute to grant a specific role to all users logging in from a specific IP address pool. Ascend-Assign-IP-Pool is an integer attribute that defines the address pool where the user is allowed to log in, with the integer indicating the number of the assigned IP address pool. To declare that custom attribute, you create a custom attribute with an attribute name of Ascend-IP-Pool-Definition, an attribute ID of 218, and an attribute type of integer. You could then type Ascend-Assign-IP-Pool=2 in the Intrusion Event Analyst (Read Only) field to grant read-only intrusion event analyst rights to all users with an Ascend-IP-Pool-Definition attribute value of 2. When you create a RADIUS authentication object, a new dictionary file for that object is created on the Sourcefire 3D System appliance in the /var/sf/ userauth directory. Any custom attributes you add to the authentication object are added to the dictionary file.

Version 4.9.1

Sourcefire 3D System Administrator Guide

293

Managing Users Managing Authentication Objects

Chapter 8

To define a custom attribute: Access: Admin 1. Click the arrow to expand the Define Custom RADIUS Attributes section. The attribute fields appear.

2. Type an attribute name consisting of alphanumeric characters and dashes, with no spaces, in the Attribute Name field. 3. Type the attribute ID, in integer form, in the Attribute ID field. 4. Select the type of attribute from the Attribute Type drop-down list. 5. Click Add to add the custom attribute to the authentication object. TIP! You can remove a custom attribute from an authentication object by clicking Delete next to the attribute. 6. Continue with Testing User Authentication on page 294.

Testing User Authentication
Requires: DC After you configure RADIUS connection, user role, and custom attribute settings, you can specify user credentials for a user who should be able to authenticate to test those settings. For the user name, you can enter the user name for the user you want to test with. Note that testing the connection to servers with more than 1000 users only returns 1000 users because of UI page size limitations. TIP! If you mistype the name or password of the test user, the test fails even if the server configuration is correct. To verify that the server configuration is correct, click Test without entering user information in the Additional Test Parameters first. If that succeeds supply a user name and password to test with the specific user.

Version 4.9.1

Sourcefire 3D System Administrator Guide

294

Managing Users Managing Authentication Objects

Chapter 8

To test user authentication: Access: Admin 1. In the User Name and Password fields, type the user name and password for the user whose credentials should be used to validate access to the RADIUS server. For example, to test to see you can retrieve the jsmith user credentials at our example company, type jsmith.

2. Select Show Details and click Test. A message appears, either indicating success of the test or detailing what settings are missing or need to be corrected. 3. If the test succeeds, click Save. The Login Authentication page appears, with the new object listed. To enable RADIUS authentication using the object on an appliance, you must apply a system policy with that object enabled to the appliance. For more information, see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324.

RADIUS Authentication Object Examples
Requires: DC This section provides examples of RADIUS server authentication objects to show how Sourcefire 3D System RADIUS authentication features can be used. See the following sections for more information: • • Authenticating a User using RADIUS on page 295 Authenticating a User with Custom Attributes on page 296

Authenticating a User using RADIUS
Requires: DC The following figure illustrates a sample RADIUS login authentication object for a server running freeRadius with an IP address of 10.10.10.98. Note that the connection uses port 1812 for access and that connections to the server time out after 30 seconds of disuse and will retry three times before attempting to connect to a backup authentication server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

295

Managing Users Managing Authentication Objects

Chapter 8

This example illustrates important aspects of RADIUS user role configuration: • Users ewharton and gsands are granted administrative access to Sourcefire 3D System appliances where this authentication object is enabled. The user jaustin is granted Intrusion Event Analyst access to Sourcefire 3D System appliances where this authentication object is enabled. The user cbronte is granted RNA Event Analyst access to Sourcefire 3D System appliances where this authentication object is enabled. The user ewharton can log into the appliance using a shell account.

• • •

The following graphic depicts the role configuration for the example:

Authenticating a User with Custom Attributes
Requires: DC You can use an attribute-value pair to identify users who should receive a particular user role. If the attribute you use is a custom attribute, you must define the custom attribute.

Version 4.9.1

Sourcefire 3D System Administrator Guide

296

Managing Users Managing Authentication Objects

Chapter 8

The following figure illustrates the role configuration and custom attribute definition in a sample RADIUS login authentication object for the same freeRadius server as in the previous example. In this example, however, the MS-RAS-Version custom attribute is returned for one or more of the users because a Microsoft remote access server is in use. Note the MS-RAS-Version custom attribute is a string. In this example, all users logging in to RADIUS through a Microsoft v. 5.00 remote access server should receive the Intrusion Event Analyst (Read Only role), so you type the attribute-value pair of MS-RAS-Version=MSRASV5.00 in the Intrusion Event Analyst (Read Only) field.

Version 4.9.1

Sourcefire 3D System Administrator Guide

297

Managing Users Managing Authentication Objects

Chapter 8

Editing RADIUS Authentication Objects
Requires: DC You can edit an existing authentication object. If the object is in use in a system policy, the settings in place at the time the policy was applied stay in effect until you re-apply the policy. To edit an authentication object: Access: Admin 1. Select Operations > Configuration > Login Authentication. The Login Authentication page appears. 2. Click Edit next to the object you want to edit. The Create Authentication Object page appears. 3. Modify the object settings as needed. For more information, see the following topics: • • • • • Creating RADIUS Authentication Objects on page 287 Configuring RADIUS Connection Settings on page 288 Configuring RADIUS User Roles on page 290 Configuring Administrative Shell Access on page 292 Testing User Authentication on page 294

4. Click Save. Your changes are saved and the Login Authentication page re-appears. Remember that you have to apply a system policy with the object enabled to an appliance before the authentication changes take place on that appliance. For more information, see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324.

Deleting Authentication Objects
Requires: DC You can delete an authentication object if it is not currently enabled in a system policy. To delete an authentication object: Access: Admin 1. Select Operations > Configuration > Login Authentication. The Login Authentication page appears. 2. Click Delete next to the object you want to delete. The object is deleted and the Login Authentication page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

298

Managing Users Managing User Accounts

Chapter 8

Managing User Accounts
If you have Admin access, you can use the web interface to view and manage user accounts on a Defense Center or a 3D Sensor, including adding, modifying, and deleting accounts. User accounts without Admin access are restricted from accessing management features. The navigation menu differs in appearance for each type of user. See the following sections for more information about managing user accounts: • Viewing User Accounts on page 299 explains how to access the User Management page, where you can add, activate, deactivate, edit, and delete user accounts. Adding New User Accounts on page 300 describes the different options you can use when you add a new user account. Managing Externally Authenticated User Accounts on page 302 explains how externally authenticated users are added and what aspects of the user configuration you can manage within the Sourcefire 3D System. Modifying User Privileges and Options on page 306 explains how to access and modify an existing user account. Modifying Restricted Event Analyst Access Properties on page 307 explains how to restrict the data available to a user account with restricted data access. Deleting User Accounts on page 312 explains how to delete user accounts. User Account Privileges on page 312 contains tables that list the menus and options each type of user account can access.

• •

• •

• •

Viewing User Accounts
Requires: DC/MDC or 3D Sensor From the User Management page, you can view, edit, and delete existing accounts. You can determine the type of authentication for a user from the Authentication Method column. The Password Lifetime column indicates the days remaining on each user’s password. The Action column allows you to set users active or inactive. Note that for externally authenticated users, if the authentication object for the server is disabled, the Authentication Method column displays External (Disabled). To access the User Management page: Access: Admin Select Operations > User Management. The User Management page appears, showing each user, with options to activate, deactivate, edit, or delete the user account.

Version 4.9.1

Sourcefire 3D System Administrator Guide

299

Managing Users Managing User Accounts

Chapter 8

See the following sections for information about the actions you can perform on the User Management page: • • • • • Adding New User Accounts on page 300 Modifying User Privileges and Options on page 306 Modifying Restricted Event Analyst Access Properties on page 307 Modifying User Passwords on page 311 Deleting User Accounts on page 312

Adding New User Accounts
Requires: DC/MDC or 3D Sensor When you set up a new user account, you can control which parts of the system the account can access. To add a new user: Access: Admin 1. Select Operations > User Management. The User Management page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

300

Managing Users Managing User Accounts

Chapter 8

2. Click Create User. The Create User page appears.

3. In the User Name field, type a name for the new user. New user names must contain alphanumeric or hyphen characters with no spaces, and must be no more than 32 characters. 4. Requires: DC/MDC If you want this user to authenticate to an external directory server on login, select Use External Authentication Method. IMPORTANT! If you select this option, the password management options below disappear. Configure access settings and click Add User to complete configuration of the externally authenticated user. You must also create an authentication object for the external authentication server you want to use for authentication on your Defense Center, and apply a system policy with authentication enabled to your appliance before users can log in using credentials from an external server. For more information, see Managing Authentication Objects on page 269 and Configuring Authentication Profiles on page 329.

Version 4.9.1

Sourcefire 3D System Administrator Guide

301

Managing Users Managing User Accounts

Chapter 8

5. In the Password field, type a password (up to 32 alphanumeric characters). If you enable password strength checking, the password must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. It cannot be a word that appears in a dictionary or include consecutive repeating characters. 6. In the Confirm Password field, type the password again. 7. Configure the remaining password user account options. For more information, see the User Account Password Options table on page 304. 8. Select user roles to grant to the user. For more information, see the User Roles table on page 305. 9. Optionally, for users with event analyst roles, click Restrict Deletion Rights - User Cannot Delete Bookmarks, Searches, Reports, Report Profiles, Custom Workflows or Custom Tables Created by Other Users to restrict the user to deletion of reports, report profiles, searches, bookmarks, custom tables, and custom workflows created by the user. 10. Click Add User. A message appears, indicating that the user was added. The username appears on the User Management page. IMPORTANT! Click Deactivate next to the name of an internally authenticated user on the User Management page to disable that user login without deleting it. To reactivate a user, click Activate next to the username.

Managing Externally Authenticated User Accounts
Requires: DC/MDC or 3D Sensor When an externally authenticated user logs into an appliance that has external authentication enabled, the appliance grants the user the default access role you set by specifying group membership in the authentication object. If you did not configure access group settings, the appliance grants the default user role you set in the system policy. However, if you add users locally before they log into the appliance, the user privileges you configure on the User Management page override the default settings. An internally authenticated user is converted to external authentication when all of the following conditions exist: • • • You enable LDAP or RADIUS authentication. The same username exists for the user on the LDAP or RADIUS server. The user logs in using the password stored for that user on the LDAP or RADIUS server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

302

Managing Users Managing User Accounts

Chapter 8

Once an internally authenticated user converts to an externally authenticated user, you cannot revert to internal authentication for that user. For more information on selecting a default user role, see Configuring Authentication Profiles on page 329 and Understanding User Privileges on page 267. Note that you can only enable external authentication in a system policy on a Defense Center. You must use the Defense Center to apply the policy to managed sensors if you want to use external authentication on them. For more information on associating an external user with a set of permissions on your appliance, see Logging into the Appliance to Set Up an Account on page 23. For more information on modifying user access, see Modifying User Privileges and Options on page 306. Note that you cannot manage passwords for externally authenticated users or deactivate externally authenticated users through the Sourcefire 3D System interface. For externally authenticated users, you cannot remove the minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values. On the Edit User page for an externally authenticated user, rights granted because of settings on an external authentication server are marked with a status of Externally Modified. You can, however, assign additional rights. When you modify the access rights for an externally authenticated user, the Authentication Method column on the User Management page provides a status of External - Locally Modified.

Managing User Password Settings
You can also control how and when the password for each user account is changed, as well as when user accounts are disabled. The User Account

Version 4.9.1

Sourcefire 3D System Administrator Guide

303

Managing Users Managing User Accounts

Chapter 8

Password Options table describes some of the options you can use to regulate passwords and account access. IMPORTANT! After you enable Use External Authentication Method, password options no longer appear. Use the external authentication server to manage password settings. User Account Password Options Option Use External Authentication Method Description Select this option if you want this user's credentials to be externally authenticated. IMPORTANT! If you select this option for the user and the external authentication server is unavailable, that user can log into the web interface but cannot access any functionality. Enter an integer, without spaces, that determines the maximum number of times each user can try to log in after a failed login attempt before the account is locked. The default setting is five tries; use 0 to allow an unlimited number of failed logins. Enter the number of days after which the user’s password will expire. The default setting is 0, which indicates that the password never expires. Enter the number of warning days users have to change their password before their password actually expires. The default setting is 0 days. WARNING! The number of warning days must be less than the number of days before the password expires Force Password Reset on Login Check Password Strength Select this option to force the user to change his password the first time the user logs in. Select this option to require strong passwords. A strong password must be at least eight alphanumeric characters of mixed case and must include at least one numeric character. It cannot be a word that appears in a dictionary or include consecutive repeating characters.

Maximum Number of Failed Logins

Days Until Password Expiration Days Until Expiration Warning

Configuring User Roles
The User Roles table contains a synopsis of each access type. For a full list of the menus available to each access type, see User Account Privileges on page 312.

Version 4.9.1

Sourcefire 3D System Administrator Guide

304

including event views. RNA Event Analysts see the main toolbar and RNA analysis-related options on the Analysis & Reporting and Operations menus. you must not only move the user from one list to another in the authentication object or change the user's attribute value or group membership on the external authentication server. Provides access to RNA analysis features. In addition. You cannot remove minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values .Managing Users Managing User Accounts Chapter 8 Note that you cannot change the authentication type for a user after you create the user account. custom tables. WARNING! If you want to change the minimum access setting for a user. services. Administrator users see the main toolbar as well as all the menu options. you must reapply the system policy. and all maintenance features. You can. client applications. Maintenance users see the main toolbar and maintenancerelated options on the Operations top-level menu. and reports. and reports. Note that you can restrict an event analyst user’s deletion rights to only allow deletion of report profiles. vulnerabilities. searches. Note that you should limit use of the Administrator role for security reasons.User Cannot Delete Items Created by Other Users to restrict the user’s deletion rights. assign additional rights. and custom workflows created by that user. including event views. externally authenticated users cannot authenticate unless the external authentication server is available. services. network maps. incidents. system management. network maps. rule and policy configuration. Provides read-only access to analysis features. RNA Event Analysts see the main toolbar and analysisrelated options on the Analysis & Reporting and Operations menus. bookmarks. User Roles User Role Administrator Access Privileges Provides access to analysis and reporting features. host profiles. however. and you must remove the assigned user right on the user management page. RNA Event Analyst (Read Only) Access Version 4.1 Sourcefire 3D System Administrator Guide 305 . Maintenance User Access RNA Event Analyst Access Provides access to monitoring and maintenance features. host profiles.9. Select Restrict Deletion Rights . client applications. vulnerabilities.

You can restrict access by allowing access to only for those events that match specified search criteria or you can turn off access for an entire category of events. You can. and reports. however.Managing Users Managing User Accounts Chapter 8 User Roles (Continued) User Role Intrusion Event Analyst Access Intrusion Event Analyst (Read Only) Access Restricted Event Analyst Access Privileges Provides access to IPS analysis features. You manage those settings on the external server. you must configure access rights for all accounts. Note that password management options do not apply to users who authenticate to an external directory server. See Modifying Restricted Event Analyst Access Properties on page 307 for more information. or passwords at any time. Policy & Response Administrator Access Modifying User Privileges and Options Requires: DC/MDC or 3D Sensor After adding user accounts to the system. assign additional rights. Policy & Response Administrators have access to the main toolbar and rule and policy-related options on the Policy & Response and Operations menus. Note that if you change the authentication for a user from externally authenticated to internally authenticated. the Authentication Method column on the User Management page provides a status of External . including those that are externally authenticated. Version 4. Provides read-only access to IPS analysis features.Locally Modified. Restricted event analyst users see only the main toolbar and analysis-related options on the Analysis & Reporting and Operations menus. incidents. and reports. you must supply a new password for the user. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. you cannot remove the minimum access rights through the Sourcefire 3D System user management page for users assigned an access role because of LDAP group or RADIUS list membership or attribute values. For externally authenticated users.1 Sourcefire 3D System Administrator Guide 306 . However. you can modify access privileges. Provides access to the same features as Intrusion Event Analyst or RNA Event Analyst access. Provides access to rules and policy configuration. including intrusion event views. including intrusion event views. incidents. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. account options.9. When you modify the access rights for an externally authenticated user.

See Configuring User Roles on page 304 for more information on configuring roles to grant access for Sourcefire 3D System functions. See Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users. • • • Modifying Restricted Event Analyst Access Properties Requires: DC/MDC or 3D Sensor User accounts with Restricted Event Analyst access use saved searches to specify which events a user can view. You can specify this information only after the user is added. Version 4. Modify the account or accounts as needed: • See Managing Externally Authenticated User Accounts on page 302 for a description of how users can be authenticated through external servers. select or clear the Only delete items created by user option to manage the user’s ability to delete of items not created by that user. 3. for users with event analyst roles. The Edit User page appears. Select Operations > User Management.Managing Users Managing User Accounts Chapter 8 To modify user account privileges: Access: Admin 1.9.1 Sourcefire 3D System Administrator Guide 307 . 2. The User Management page appears. See Adding New User Accounts on page 300 for information about adding new user accounts. Click Edit next to the user you want to modify. Optionally.

included in the base set of rights for the restricted analyst role Version 4...1 Sourcefire 3D System Administrator Guide 308 . Restricted Event Analyst Settings To allow the restricted event analyst to. DC + RNA Set this data set or data sets to Show All or to a specific search One or more of the following: • Host Attributes Data • RNA Client Applications Data • RNA Hosts Data • RNA Services Data • Vulnerabilities Data view network discovery events view hosts view host attributes view services view vulnerabilities view client applications view flow data view compliance events view white list events view white list violations view users or user events view intrusion events use the clipboard DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RNA DC + RUA IPS IPS RNA Events Data RNA Hosts Data Host Attributes Data RNA Services Data Vulnerabilities Data RNA Client Applications Data Flow Data Compliance Events Data White List Events Data White List Violations Data Users Data Intrusion Events Data N/A .Managing Users Managing User Accounts Chapter 8 Restricted event analyst users have access to only a few sections of the web interface. The Restricted Event Analyst Settings table shows the correlation between platform and access requirements for the restricted event analyst...9. view the network map When these platforms are present.

Managing Users Managing User Accounts Chapter 8 Restricted Event Analyst Settings (Continued) To allow the restricted event analyst to.9. and then apply each saved search to the account as described in the following procedure. IMPORTANT! You must have saved private searches available before you can add restricted event analyst values to a user account. IPS IPS DC/MDC or 3D Sensor Set this data set or data sets to Show All or to a specific search All data sets for which the user will generate reports All data sets for which the user will create incident reports N/A . custom tables create and manage bookmarks view events from a custom table When these platforms are present. 2. and event view settings create custom workflows and. Click Edit next to the user to whom you want to grant restricted event analyst rights.included in the base set of rights for the restricted analyst role DC/MDC or 3D Sensor All data sets for which the user will create custom workflows DC/MDC or 3D Sensor Platforms required to view custom table All data sets for which the user will need to create or access bookmarks All data sets for the applicable custom tables If you want to ensure that a user only sees data for a specific subnet. If they are saved as public. generate (but not view) reports create (but not modify) incident reports change user-specific preferences such as the account password. Select Operations > User Management. time zone. To restrict event analyst access to events: Access: Admin 1. See Searching for Events in the Analyst Guide for more information.1 Sourcefire 3D System Administrator Guide 309 . one for each of the event types. on the Defense Center. Searches must be private. restricted event analyst users could delete the searches and enhance their access privileges. create multiple private saved searches.. Version 4.... The User Management page appears.

1 Sourcefire 3D System Administrator Guide 310 . For each row. select Hide Data. To grant access to events that match a specific saved search. you have three choices: • • • To grant access to all events for a category. Intrusion Event Analyst. IMPORTANT! If you created any custom tables on the Defense Center. 4. select Show All Data. The Restrictions section of the page appears. RNA Event Analyst. select Restricted Event Analyst. select the search that you want to use to restrict the user account.9. The Defense Center version of the page is shown below. they appear on this page.Managing Users Managing User Accounts Chapter 8 3. IMPORTANT! You cannot select Restricted Event Analyst if Administrator. 5. Version 4. or RNA Event Analyst (Read Only) access is enabled. If the user you want to modify does not already have the Restricted Event Analyst option enabled. Intrusion Event Analyst (Read Only). Click Save to save your changes and return to the User Management page. To deny access to all events in a category.

1 Sourcefire 3D System Administrator Guide 311 . 3. click Reset Password next to the user account on the User Management page. The User Management page appears. click Edit. Select Operations > User Management. To change a user’s password: Access: Admin 1. 2. TIP! If you want to force a user to change the password on the next log-in. In the Password field. Version 4.9. type the new password (up to 32 alphanumeric characters). Next to the user name. The Edit User page appears. Note that you must manage externally authenticated user passwords on the LDAP or RADIUS server.Managing Users Managing User Accounts Chapter 8 Modifying User Passwords Requires: DC/MDC or 3D Sensor You can modify user passwords from the User Management page for internally authenticated users.

see Configuring User Roles on page 304. To delete a user account: Access: Admin 1. see Managing User Password Settings on page 303. 5. 2. • • • • Analysis & Reporting Menu on page 313 Policy & Response Menu on page 316 Operations Menu on page 317 Toolbar Options on page 319 Version 4. with the exception of the admin account. click Delete.9. In the Confirm Password field. For more information on user roles. 6. Select Operations > User Management. For more information on the access notations used in the tables that follow and throughout this documentation.1 Sourcefire 3D System Administrator Guide 312 . see Access Requirements Conventions on page 39. It cannot be a word that appears in a dictionary or contain consecutive repeating characters. which cannot be deleted.Managing Users Managing User Accounts Chapter 8 4. the password must have at least eight alphanumeric characters of mixed case. Deleting User Accounts Requires: DC/MDC or 3D Sensor You can delete user accounts from the system at any time. IMPORTANT! If password strength checking is enabled for the user account. User Account Privileges Requires: DC/MDC or 3D Sensor The following sections provide a list of the menus and toolbar options in Sourcefire 3D System and the user account privileges required to access them. re-type the new password. Make any other changes you want to make to the user configuration: • • For more information on password options. The password is changed and any other changes saved. Click Save. The User Management page appears. Next to the user whose account you want delete. The account is deleted. with at least one number.

An X indicates that the user can access the option.9.Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu Requires: IPS or DC/ MDC The Analysis & Reporting Menu table lists the user account privileges required to access each option on the Analysis & Reporting menu. Users with only Rules or Maintenance access cannot see the Analysis & Reporting menu at all. Analysis & Reporting Menu Menu Admin Maint RNA/ RNA-RO Event Analyst X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Restricted Event Analyst P&R Admin Event Summary Intrusion Event Statistics Event Graphs Dashboards RNA Statistics Flow Summary IPS Events Reviewed Events Clipboard Incidents RNA Network Map | Hosts Network Map | Network Devices Network Map | Services Network Map | Vulnerabilities Network Map | Host Attributes X X X X X X X X X X X X X X X X X X Version 4.1 Sourcefire 3D System Administrator Guide 313 .

Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X X X X IPS/ IPS-RO Event Analyst Restricted Event Analyst P&R Admin RNA Events Hosts Host Attributes Services Client Applications Flow Data Vulnerabilities RUA Users RUA Events Compliance Compliance Events White List Events White List Violations Custom Tables Searches Audit Log Client Applications Compliance Events Flow Data Health Events X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.9.1 Sourcefire 3D System Administrator Guide 314 .

Managing Users Managing User Accounts Chapter 8 Analysis & Reporting Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X IPS/ IPS-RO Event Analyst Restricted Event Analyst P&R Admin Host Attributes Hosts Intrusion Events Remediation Status RNA Events RUA Events Scan Results Services SEU Import Log Users Vulnerabilities White List Events White List Violations Custom Workflows Bookmarks Report Profiles X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.9.1 Sourcefire 3D System Administrator Guide 315 .

or Maintenance access can not see the Policy & Response menu at all. Users with Intrusion Event Analyst. An X indicates that the user can access the option.9.Managing Users Managing User Accounts Chapter 8 Policy & Response Menu Requires: IPS or DC/ MDC The Policy & Response Menu table lists the user account privileges required to access each option on the Policy & Response menu. Event Analyst P&R Admin IPS Intrusion Policy SEU Rule Editor Email OPSEC RNA Detection Policy Host Attributes RNA Detectors Custom Fingerprinting Custom Product Mappings User 3rd Party Mappings Network Map | Custom Topology Compliance Policy Management Rule Management X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4. Policy & Response Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. RNA Event Analyst.1 Sourcefire 3D System Administrator Guide 316 .

An X indicates that the user can access the option. Event Analyst P&R Admin White List Traffic Profiles Responses Alerts Impact Flag Alerts RNA Event Alerts Remediations Groups X X X X X X X X X X X X X X X X Operations Menu Requires: DC/MDC or 3D Sensor The Operations Menu table lists the user account privileges required to access each option on the Operations menu. Operations Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. All users can access at least some options on the Operations menu.1 Sourcefire 3D System Administrator Guide 317 .9. Event Analyst P&R Admin Configuration RNA/RUA Event Purge Detection Engines High Availability eStreamer Login Authentication X X X X X X X Version 4.Managing Users Managing User Accounts Chapter 8 Policy & Response Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.

Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. Event Analyst P&R Admin RUA Sensors User Management System Settings System Policy Update Monitoring Statistics Performance | IPS Performance | RNA Audit Task Status Syslog Health Tools Scheduling Backup/Restore Import/Export Whois Scan Results Scanners X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.1 Sourcefire 3D System Administrator Guide 318 .9.

An X indicates that the user can access the option.9.Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X IPS/ IPS-RO Event Analyst X X X X X Res. All users can access at least some of the options on the toolbar. Toolbar Options Menu Admin Maint RNA/ RNA-RO Event Analyst X X X X X X X X X X X X IPS/ IPS-RO Event Analyst X X X X X X X X X X X X X X X X X X X X X Res. Event Analyst P&R Admin Health Preferences Preferences | Home Page Preferences | Event View Settings Preferences | Change Password Preferences | Time Zone Settings Help Logout X X X X X X X X X X X Version 4. Event Analyst X X X X X P&R Admin Help About Online Email Support Support Site X X X X X X X X X X X X X X X Toolbar Options Requires: DC/MDC or 3D Sensor The Toolbar Options table lists the user account privileges required to access each option on the toolbar and its sub-menus.1 Sourcefire 3D System Administrator Guide 319 .

including multiple fingerprint and subnet detection settings RUA settings synchronizing time serving time from the Defense Center mapping vulnerabilities for services You can use a system policy to control the aspects of your Defense Center that are likely to be similar for other Sourcefire 3D System appliances in your deployment.9. your organization’s security policies may require that Version 4.Managing System Policies Chapter 9 Administrator Guide A system policy allows you to manage the following on your Defense Center or 3D Sensor: • • • • • • • • • • • • • • • • access control lists audit log settings authentication profiles dashboard settings database event limits detection policy preferences DNS cache properties the mail relay host and notification address tracking intrusion policy changes specifying a different language custom login banners RNA settings. For example.1 Sourcefire 3D System Administrator Guide 320 .

see Importing and Exporting Objects on page 583.9. you can create several system policies and switch between them rather than editing a single policy. You can then edit the imported policy to suit your needs before you apply it. Version 4. Contrast a system policy. you configure the various aspects of the policy. or if you want to test different database limits. See Configuring System Settings on page 360 for more information. if you have different mail relay hosts that you use under different circumstances. For more information. you can set the login banner once in a system policy on a Defense Center and then apply the policy to all the sensors that it manages. See the following sections for more information: • • • • Creating a System Policy on page 321 Editing a System Policy on page 323 Applying a System Policy on page 324 Deleting System Policies on page 325 Creating a System Policy Requires: Any When you create a system policy. For example. you assign it a name and a description. each of which is described in its own section.Managing System Policies Creating a System Policy Chapter 9 your appliances have a “No Unauthorized Use” message when a user logs in.1 Sourcefire 3D System Administrator Guide 321 . Next. with system settings. which are likely to be specific to a single appliance. Instead of creating a new policy. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. With system policies. You can also benefit from having multiple policies on a 3D Sensor. which controls aspects of an appliance that are likely to be similar across a deployment. you can export a system policy from another appliance and then import it onto your appliance.

9. The Applied To column indicates the number of appliances where the policy is applied and a count of out-of-date appliances where the previously applied policy has changed and should be reapplied. 3. For information about configuring each aspect of the system policy. 5. Select Operations > System Policy. 2. Your system policy is saved and the Access List page appears. Click Save. Type a name and description (up to 40 alphanumeric characters and spaces each) for your new policy. 4. The Policy Name column includes its description. The Create page appears.1 Sourcefire 3D System Administrator Guide 322 .Managing System Policies Creating a System Policy Chapter 9 To create a system policy: Access: Admin 1. From the drop-down list. select an existing policy to use as a template for your new system policy. The System Policy page appears. see one of the following sections: • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Version 4. Click Create Policy.

see one of the following sections: • • • • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Version 4.1 Sourcefire 3D System Administrator Guide 323 .Managing System Policies Editing a System Policy Chapter 9 • • • • • Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 Editing a System Policy Requires: Any You can edit a system policy that is currently in use. Click Edit next to the system policy that you want to edit. With the Policy Name and Policy Description fields at the top. To edit an existing system policy: Access: Admin 1. including a list of the existing system policies. 2. The System Policy page appears. the first section of the system policy. You can change the policy name and description. appears. but remember to re-apply the policy as explained in Applying a System Policy on page 324. Select Operations > System Policy. For information about configuring each aspect of the system policy. Access List.9.

model. the Defense Center itself. the system policy is applied. Version 4. 3. Applying a System Policy Requires: Any After you create or edit a system policy. Click Apply next to the system policy that you want to apply.1 Sourcefire 3D System Administrator Guide 324 . or previously applied policy. where you want to apply the system policy. On the Defense Center. your settings do not take effect until you apply it. Click Apply. type of sensor. select the sensors.9. Select Operations > System Policy. See Applying a System Policy on page 324. The System Policy page appears. 2. the name of the policy appears in italics. To apply a system policy: Access: Admin 1. and. You can also select an entire group. If a policy has been updated since it was applied. TIP! You can sort the sensors by sensor group. if required.Managing System Policies Applying a System Policy Chapter 9 • • Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 IMPORTANT! If you are editing the current system policy. A message appears indicating that the task is added to the task queue. On the 3D Sensor. including a list of the existing system policies. make sure you apply the updated policy when you are finished. On the Defense Center. 4. the Apply page appears. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents.

9. The policy is deleted. By default. port 443 (Hypertext Transfer Protocol Version 4.Managing System Policies Deleting System Policies Chapter 9 Deleting System Policies Requires: Any You can delete a system policy even if it is in use. Select Operations > System Policy. To delete a system policy: Access: Admin 1. For information about configuring each aspect of the system policy.1 Sourcefire 3D System Administrator Guide 325 . The System Policy page appears. If the policy is still in use. Default system policies cannot be deleted. including a list of the existing system policies. Click Delete next to the system policy that you want to delete. it is used until a new policy is applied. 2. Configuring the Parts of Your System Policy Requires: Any You can change various parts of your system policy. see one of the following sections: • • • • • • • • • • • • • • • • • Configuring the Access List for Your Appliance on page 325 Configuring Audit Log Settings on page 327 Configuring Authentication Profiles on page 329 Configuring Dashboard Settings on page 331 Configuring Database Event Limits on page 332 Configuring Detection Policy Preferences on page 336 Configuring DNS Cache Properties on page 337 Configuring a Mail Relay Host and Notification Address on page 338 Configuring Intrusion Policy Preferences on page 339 Specifying a Different Language on page 340 Adding a Custom Login Banner on page 341 Configuring RNA Settings on page 342 Configuring RNA Subnet Detection Settings on page 349 Configuring RUA Settings on page 352 Synchronizing Time on page 354 Serving Time from the Defense Center on page 357 Mapping Vulnerabilities for Services on page 358 Configuring the Access List for Your Appliance Requires: Any The Access List page allows you to control which computers can access your appliance on specific ports.

the access list does not take effect until you apply the system policy. To delete one of the current settings. Select Operations > System Policy. and click Save. access to the appliance is not restricted. In either case. click Create Policy. To configure the access list: Access: Admin 1. consider adding access to the appliance for specific IP addresses and then deleting the default any option. To operate the appliance in a more secure environment. click Edit next to the system policy. 2. the Access List page appears. or SSH). are enabled for any IP address. You have two options: • • To modify the access list in an existing system policy.1 Sourcefire 3D System Administrator Guide 326 .Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Secure. Provide a name and description for the system policy as described in Creating a System Policy on page 321. or HTTPS). Version 4. click Delete. The setting is removed. In either case. The access list is part of the system policy. which is used to access the command line.9. WARNING! If you delete access for the IP address that you are currently using to connect to the appliance interface (and if there is no entry for “IP=any port=443”). which is used to access the web interface and port 22 (Secure Shell. 3. To configure the access list as part of a new system policy. The System Policy page appears. WARNING! By default. you will lose access to the system when you apply the policy. You can specify the access list either by creating a new system policy or by editing an existing policy.

168.1. a severity. The appliance does not send the audit log until you apply the system policy. In the IP Address field. and an optional tag. 192. 192.1 Sourcefire 3D System Administrator Guide 327 . • any. The Access List page appears again.101) an IP address range using CIDR notation (for example. Select SSH.168. IMPORTANT! You must ensure that the external host is functional and accessible from the appliance sending the audit log. see IP Address Conventions on page 41. Your changes do not take effect until you apply the system policy. reflecting the changes you made. click Add. Configuring Audit Log Settings Requires: Any You can configure the system policy so that the appliance streams an audit log to an external host. To add access for one or more IP addresses. TIP! You can click Add to add access for additional IP addresses or click Delete to remove access from other IP addresses. use the following syntax depending on the IP addresses you want to add: • • an exact IP address (for example. The system policy is updated. HTTPS.1/24) For information on using CIDR in the Sourcefire 3D System. 7. Version 4. The Add IP Address page appears. 5.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 4. then click Add.9. Click Save Policy and Exit. The name of the sending host is part of the sent information and you can further identify the audit log stream with a facility. or both to specify which ports you want to enable for these IP addresses. to designate any IP address 6. See Applying a System Policy on page 324 for more information.1.

Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. 5. [Action] where the local date.9. Operations > Monitoring. Click Audit Log Settings. and hostname precede the bracketed optional tag.1. You have two options: • • To modify the audit log settings in an existing system policy. The System Policy Page appears. Optionally. and click Save. insert a reference tag in the TAG field. Click Save Policy and Exit. The default for Severity is INFO. the appliance may the send audit log to the host. In either case.1 Sourcefire 3D System Administrator Guide 328 . 4. After you apply a policy with this feature enabled and your destination host is configured to accept the audit log. you can select any of the standard syslog facility and severity settings. Version 4. 2. Select Operations > System Policy.1. time. The following is an example of the output structure: Date Time Host [Tag] Sender: [User_Name]@[User_IP]. the syslog messages are sent. 7. However. Otherwise. 3. [Subsystem]. click Create Policy. WARNING! The computer you configure to receive an audit log must be set up to accept remote messages. Designate the destination host for the audit information by using the IP address or the fully qualified name of the host in the Host field. The default setting is Disabled. the Access List page appears. click Edit next to the system policy. but it will not be accepted. The default port (514) is used.2. Select Enabled next to Send Audit Log to Syslog. See Applying a System Policy on page 324 for more information. For example: Mar 01 14:45:24 localhost [TAG] Dev-DC3000: admin@10. 6. The system policy is updated. and the sending device name precedes the audit log message. Provide a name and description for the system policy as described in Creating a System Policy on page 321. The default for Facility is USER. To configure the audit log settings as part of a new system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 To configure the audit log settings: Access: Admin 1. Page View 8. Label the audit data that you are sending with a facility and severity.

if a user has internal authentication enabled and the user credentials are not found in the internal database. you may set the default user role to include both the Intrusion Event Analyst role and the RNA Event Analyst so users can access collected event data without any additional user configuration on your part. as long as those roles can be combined. The Authentication Profiles page only displays in the system policy on a Defense Center. if you create an authentication object referencing an external authentication server. you can set the default user role for any user whose account is externally authenticated. see Modifying User Privileges and Options on page 306. however. See Configuring Attribute Mapping on page 274 for more information. the appliance does not revert to checking the local database. all passwords across all servers work. You can enable authentication in a system policy on your Defense Center and then push that policy to managed sensors. the appliance verifies the user credentials by comparing them to a user account stored in the Defense Center or managed sensor’s local database. you can set a filter search attribute to specify the set of users who can successfully authenticate against the LDAP server.9. For example. the appliance then checks the external server for a set of matching credentials. If no access role is selected. When you apply a policy with authentication enabled to an appliance. You can select multiple roles. where you can edit the account settings to grant additional permissions. However.1 Sourcefire 3D System Administrator Guide 329 . if you set up an authentication profile that retrieves only users in the Network Security group in your company.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Configuring Authentication Profiles Requires: DC/MDC Normally. Note. For more information on modifying a user account. see Logging into the Appliance to Set Up an Account on page 23. you can apply the system policy to let users logging into the Defense Center or managed sensor authenticate to that server rather than using the local database. Note that when you create an LDAP authentication object on your Defense Center. any user accounts created before the modification retain the first user role until you modify or delete and recreate them. In addition. For more information on available user roles. users can log in but cannot access any functionality. that if authentication fails on the available external authentication servers. When you enable authentication. Once you apply the policy to a Version 4. if your authentication profile retrieves records for other personnel in addition to the security group. then later modify the policy to use different default user roles and re-apply. However. If a user has the same username on multiple systems. when a user logs into a Sourcefire 3D System Defense Center or managed sensor. you would probably want to leave the default role unselected. If you configure the system policy to use one user role and apply the policy. For a complete procedure for logging in initially as an externally authenticated user. After a user attempts to log in. the appliance verifies the user credentials against users on an LDAP or RADIUS server. their account is listed on the User Management page. see Understanding User Privileges on page 267.

the appliance checks the username and password against the external database. Note that you can only enable external authentication on Defense Centers and 3D Sensors. If the login fails. If an external user attempts to log in. If the user exists.9. However. you have to modify the policy on the Defense Center and then push it to the sensor again. and click Save. the user logs in successfully. Version 4. To configure the authentication profile settings as part of a new system policy. Enabling external authentication by applying a system policy is not supported on the following sensor types: • • • • 3Dx800 sensors Crossbeam-based software sensors Intrusion Agents RNA Software for Red Hat Linux If a user with internal authentication attempts to log in. the appliance then checks the username and password against the local database. 2. If the login fails. External users cannot authenticate against the user list in the local database. you can either disable it in a system policy on the Defense Center and push that to the sensor or apply a local system policy (which cannot contain authentication profile settings) on the sensor. To disable authentication on a managed sensor. eligible externally authenticated users can log into the sensor.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 sensor. click Create Policy. If the username and password match results from an external server. In either case. the appliance changes the user to an external user with the default privileges for that authentication object. You have two options: • • To modify the authentication profile settings in an existing system policy. To enable authentication of users on external servers: Access: Admin 1. Provide a name and description for the system policy as described in Creating a System Policy on page 321. If the user is a new external user. select Operations > System Policy. so you cannot manage them on the sensor itself. the user login attempt is rejected. The System Policy page appears. however. the Access List page appears. To make changes to the authentication profile settings. If a match is found. the appliance first checks if that user is in the local user database. an external user account is created in the local database with the default privileges for the external authentication object. On the Defense Center. the system policy on the sensor does not display authentication profile settings. the user logs in successfully. the appliance checks the user against each external authentication server in the authentication order shown in the system policy. click Edit next to the system policy. and external authentication is enabled.1 Sourcefire 3D System Administrator Guide 330 . If a match is found.

Click Save Policy and Exit. select Enabled. Configuring Dashboard Settings Requires: Any You can configure the system policy so that Custom Analysis widgets are enabled on the dashboard. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. Remember that shell access users can only authenticate against the server whose authentication object is highest in the profile order. 6. From the Default User Role drop-down list.9. The Authentication Profiles page appears. 5. use the up and down arrows to change the order in which authentication servers are accessed when an authentication request occurs. only the analyst role is applied. Optionally. 4. The system policy is updated. If you want to use the external server to authenticate shell access accounts as well. select a user role to define the default permissions you want to grant to users authenticated externally. See Applying a System Policy on page 324 for more information.1 Sourcefire 3D System Administrator Guide 331 . click Enable next to the object. To enable use of an authentication object. Click Authentication Profiles. 9. TIP! Press Ctrl before selecting roles to select multiple default user roles. 8. Dashboards provide you with at-a-glance views of current Version 4.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. 7. From the Status drop-down list. IMPORTANT! You must enable at least one authentication object to enable external authentication. Note that although you can select both an event analyst role and the corresponding read-only event analyst role. select Enabled from the Shell Authentication drop-down list.

1 Sourcefire 3D System Administrator Guide 332 . Provide a name and description for the system policy as described in Creating a System Policy on page 321. The Dashboard Settings page appears. self-contained components that provide insight into different aspects of the Sourcefire 3D System.9. 4. 3.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 system status through the use of widgets: small. See Understanding the Custom Analysis Widget on page 69 for more information on how to use custom widgets. In either case. Select Operations > System Policy. Click Save Policy and Exit. See Deleting System Policies on page 325for more information. the Access List page appears. To improve performance. To configure the dashboard settings as part of a new system policy. you should try to tailor the database event limit to the number of events you regularly work with. clear the check box to prohibit users from using those widgets. The Custom Analysis widget allows you to create a visual representation of events based on a flexible. and click Save. Select the Enable Custom Analysis Widgets check box to allow users to add Custom Analysis widgets to dashboards. in the case of the compliance violation history database. The System Policy page appears. Click Dashboard. Custom Analysis widget use is enabled 5. You have two options: • • To modify the dashboard settings in an existing system policy. In most cases. one day’s history). for some databases. However. Version 4. click Edit next to the system policy. user-configurable query of the events in your appliance's database. The system policy is updated. By default. the minimum number of records you can store in any database is one record (or. you can choose not to store any events. 2. To enable Custom Analysis widgets: Access: Admin 1. click Create Policy. Your changes do not take effect until you apply the system policy. Configuring Database Event Limits Requires: Any You can use the Database page to specify the maximum number of events you want to store on an appliance.

or DC1000 100 million events on the DC3000 10 million events on the DC500.. and health events. any health alert limits you set in the policy have no effect on the sensors.. if you use the Defense Center to apply the same system policy to itself and the 3D Sensors it manages. flow summaries. Virtual Defense Center. For example.. or DC1000 100 million events on the DC3000 1 million events RNA Flow Summary Database Compliance & White List Event Database Health Event Database RNA flow summaries (aggregated RNA flows) on a Defense Center compliance events and white list events on a Defense Center or Master Defense Center health events on a Defense Center or Master Defense Center 1 million events Version 4. The Database Event Limits on page 333 below describes the maximum number of records you can store in the databases on your appliance. intrusion events on a Defense Center or on a Master Defense Center (which is always a DC3000) intrusion events on a 3D Sensor And can store up to. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. if you specify 100 million intrusion events and apply that policy to a 3D Sensor).5 million events on the DC500 10 million events on the Virtual Defense Center or the DC1000 100 million events on the DC3000 2 million events RNA network discovery events on a Defense Center RNA flows on a Defense Center 10 million events 10 million events on the DC500.9. Intrusion Event Database (Defense Center or Master Defense Center) Intrusion Event Database (3D Sensor) RNA Event Database RNA Flow Database Is the database that stores.. the maximum limit for the appliance is silently enforced. Note that if you apply a system policy to an appliance that does not support the maximum limit you specify (for example.. Database Event Limits The.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 These databases include those that store RNA and RUA events.1 Sourcefire 3D System Administrator Guide 333 . as well as flow events. database limits that do not apply to a particular appliance are silently ignored.. 2. Virtual Defense Center. In addition.

2.. Audit Event Database Remediation Status Event Database White List Violation History Database RUA Event Database RUA History Database SEU Import Log Database Is the database that stores. unified files are deleted from the system. To configure the maximum number of records in the database: Access: Admin 1. Provide a name and description for the system policy as described in Creating a System Policy on page 321. click Edit next to the system policy..9. You have two options: • • To modify the database settings in an existing system policy.1 Sourcefire 3D System Administrator Guide 334 .. In addition. The System Policy page appears. See Configuring a Mail Relay Host and Notification Address on page 338 for information about generating automated email notifications when events are automatically pruned.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Database Event Limits (Continued) The. To configure the database settings as part of a new system policy. Version 4. the oldest events and packet files are pruned until the database is back within limits. beginning with the oldest files...000 records 10 million events a 30-day history of violations 10 million events 10 million user login records 1 million records Note that if the number of events in the intrusion event database exceeds the maximum. see Purging the RNA and RUA Databases on page 598. on a Defense Center RUA events on a Defense Center RUA storage of user logins on a Defense Center SEU import log records And can store up to.. click Create Policy. Select Operations > System Policy. and click Save. 100. audit records remediation status events on a Defense Center the white list violation history of the hosts on your network. In either case. For information on manually pruning the RNA and RUA databases. the Access List page appears. if the /volume disk partition reaches 85% of its capacity.

The following graphic shows the Database page on a DC1000 Defense Center. 4. For information on how many records each database can maintain.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. see Database Event Limits on page 333. Click Database.1 Sourcefire 3D System Administrator Guide 335 . Version 4.9. enter the number of records you want to store. The Database page appears. For each of the databases.

Click Save Policy and Exit. To configure detection policy preferences: Access: Admin 1. To configure the detection policy preferences as part of a new system policy. See Applying a System Policy on page 324 for more information.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. the Access List page appears. The appliance also warns you if the detection engine has a different policy applied to it than the one you are attempting to apply. 5. click Edit next to the system policy. select Yes from the drop-down list. See Applying a System Policy on page 324 for more information. Click Save Policy and Exit. 2. Provide a name and description for the system policy as described in Creating a System Policy on page 321.1 Sourcefire 3D System Administrator Guide 336 . In either case. Select Operations > System Policy. If you enable this setting. and click Save.9. Your changes do not take effect until you apply the system policy. The system policy is updated. If no. The Detection Policy Preferences page appears. Your changes do not take effect until you apply the system policy. Version 4. whenever you apply an RNA detection policy or an intrusion policy to one or more detection engines. Do you want to confirm your action when you apply RNA detection policies and intrusion policies? • • If yes. click Create Policy. 4. the appliance prompts you to confirm that you want to apply the policy. 3. select No from the drop-down list. You have two options: • • To modify the detection policy preferences in an existing system policy. Click Detection Policy Preferences. The system policy is updated. Configuring Detection Policy Preferences Requires: Any The Detection Policy Preferences page allows you to configure whether you must confirm your action when you apply RNA detection policies and intrusion policies. The System Policy page appears.

you can also configure basic properties for DNS caching performed by the appliance. Select Operations > System Policy. This can reduce the amount of traffic on your network and speed the display of event pages when IP address resolution is enabled. and click Save. Click DNS Cache. 2. Version 4. The DNS Cache page appears. As an administrator. Next to DNS Resolution Caching. 4. click Edit next to the system policy. The default setting is 300 minutes (five hours).1 Sourcefire 3D System Administrator Guide 337 . To configure the DNS cache properties: Access: Admin 1. enter the number of minutes a DNS entry remains cached in memory before it is removed for inactivity.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Configuring DNS Cache Properties Requires: Any If you have a DNS server configured on the Network page.9. users must also select Event View Settings from the User Preferences menu. To configure IP address resolution on a per-user-account basis. In either case. the Access List page appears. You have two options: • • To modify the DNS cache settings in an existing system policy. 3. For information about configuring event preferences. To configure the DNS cache settings as part of a new system policy. Configuring DNS caching allows you to identify IP addresses you previously resolved without performing additional lookups. For information about configuring DNS servers. click Create Policy. In the DNS Cache Timeout field. enable Resolve IP Addresses. and then click Save. Provide a name and description for the system policy as described in Creating a System Policy on page 321. The System Policy page appears. see Configuring Network Settings on page 377. 5. select Enabled to enable caching or Disabled to disable it. see Configuring Event View Settings on page 27. you can configure the appliance to resolve IP addresses automatically on the event view pages. IMPORTANT! DNS resolution caching is a system-wide setting that allows the caching of previously resolved DNS lookups.

1 Sourcefire 3D System Administrator Guide 338 . the Access List page appears.requires IPS) use email for health event alerting (Defense Center only) you must configure a mail host. Configuring a Mail Relay Host and Notification Address Requires: Any If you plan to: • • • • • email event-based reports email status reports for scheduled tasks use email for RNA event.requires RNA) use email for intrusion event alerting (Defense Center only . The System Policy page appears. WARNING! Although DNS caching is enabled for the appliance.9. 2. Your changes do not take effect until you apply the system policy. Version 4. click Create Policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. Click Save Policy and Exit. and compliance event alerting (Defense Center only . IP address resolution is not enabled on a per-user basis unless it is configured on the Events page accessed from the User Preferences menu. In addition. To configure the email settings as part of a new system policy. impact flag.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. click Edit next to the system policy. you can configure an email address that will receive notifications when intrusion events and audit logs are pruned from the database. and click Save. You have two options: • • To modify the email settings in an existing system policy. In either case. The system policy is updated. Select Operations > System Policy. To configure a mail relay host: Access: Admin 1. See Applying a System Policy on page 324 for more information.

click Edit next to the system policy. 6. and click Save. In either case. To configure the intrusion policy preferences as part of a new system policy. You can also track all changes to intrusion policies in the audit log. Select Operations > System Policy. See Applying a System Policy on page 324 for more information. Configuring Intrusion Policy Preferences Requires: Any You can allow or require comments to be added to the audit log when an intrusion policy changes. Click Email Notification. The Intrusion Policy Preferences page appears. type the hostname or IP address of the mail server you want to use.1 Sourcefire 3D System Administrator Guide 339 . in the Data Pruning Notification Address field. 5. Version 4. Click Intrusion Policy Preferences. Click Save Policy and Exit. Your changes do not take effect until you apply the system policy. click Create Policy. enter the email address you want to receive notifications when intrusion events and audit logs are pruned from the appliance’s database. 4. You have two options: • • To modify the intrusion policy preferences in an existing system policy. the Access List page appears. 3. The System Policy page appears. In the Mail Relay Host field. Optionally.9. IMPORTANT! The mail host you enter must allow access from the appliance. To configure intrusion policy change tracking: Access: Admin 1. 2. The system policy is updated. The Configure Email Notification page appears.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 3. Provide a name and description for the system policy as described in Creating a System Policy on page 321.

Select Disabled. or Required from the Comments on policy change drop-down list.9. Specifying a Different Language Requires: Any You can use the Language page to specify a different language for the web interface. Click Language. See Applying a System Policy on page 324 for more information. and click Save. To configure the language settings as part of a new system policy. 2. Select the language you want to use. click Edit next to the system policy. a Description of Changes text box appears when you commit your intrusion policy changes. 5. Version 4. 6. The System Policy page appears. click Create Policy. To select a different language for the user interface: Access: Admin 1. In either case. Optionally. if you want to track changes to intrusion policies. Your changes do not take effect until you apply the system policy.1 Sourcefire 3D System Administrator Guide 340 . You have two options: • • To modify the language settings in an existing system policy. The Language page appears. Provide a name and description for the system policy as described in Creating a System Policy on page 321. WARNING! The language you select here is used for the web interface for every user who logs into the appliance. The system policy is updated. select Write changes in Intrusion Policy to audit log. Select Operations > System Policy. If you select Optional or Required. 3. the Access List page appears.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 4. Click Save Policy and Exit. 4. Optional.

3. Custom login banners are part of the system policy. The System Policy page appears. Version 4. the login banner is not used until you apply the system policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. In either case. See Applying a System Policy on page 324 for more information. Click Save Policy and Exit. Adding a Custom Login Banner Requires: Any You can create a custom login banner that appears when users log into the appliance using SSH and on the login page of the web interface. To configure the login banner as part of a new system policy. Click Login Banner.9. In the Custom Login Banner field. and click Save. In either case. The Login Banner page appears. click Edit next to the system policy. 4. To add a custom banner: Access: Admin 1.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. click Create Policy. You can specify the login banner either by creating a new system policy or by editing an existing policy. Select Operations > System Policy. enter the login banner that you want to use with this system policy. Your changes do not take effect until you apply the system policy.1 Sourcefire 3D System Administrator Guide 341 . You have two options: • • To modify the login banner in an existing system policy. the Access List page appears. 2. The system policy is updated. Banners can contain any printable characters except the less-than symbol (<) and the greaterthan symbol (>).

and the priority of active sources of identity data. as described in the following table. For more information. The default setting is 10080 minutes (7 days).Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. These settings also control how long data is retained in the network map. Version 4. make sure that the service timeout value is longer than the update interval in the RNA detection policy. before RNA drops a host from the network map due to inactivity. For more information. before RNA drops a service from the network map due to inactivity. in minutes. and therefore determine the data that other parts of the Sourcefire 3D System can use. in minutes.9. make sure that the host timeout value is longer than the update interval in the RNA detection policy. control the kinds of RNA data stored in the database. Service Timeout The amount of time that passes. IMPORTANT! To avoid premature timeout of services. whether identity conflict events are logged. The system policy is updated. For more information. The default setting is 10080 minutes (7 days). See Applying a System Policy on page 324 for more information. Click Save Policy and Exit. which vulnerability types to use for impact assessment. RNA Data Storage Settings Field Host Timeout Description The amount of time that passes. see Creating RNA Detection Policies in the Analyst Guide. Configuring RNA Settings Requires: DC/ MDC + RNA You can configure several aspects of RNA behavior through the system policy. Your changes do not take effect until you apply the system policy. including how RNA stores data.1 Sourcefire 3D System Administrator Guide 342 . IMPORTANT! To avoid premature timeout of hosts. see the following sections: • • • • Understanding RNA Data Storage Settings on page 342 Understanding Vulnerability Impact Assessment Settings on page 345 Understanding Multiple Fingerprint Settings on page 345 Configuring Settings for RNA on page 347 Understanding RNA Data Storage Settings Requires: DC/ MDC + RNA RNA data storage settings. what RNA and host input events are logged. whether operating system and service identity conflicts are automatically resolved. see Creating RNA Detection Policies in the Analyst Guide.

the table view contains no information. see Creating RNA Detection Policies in the Analyst Guide. The Defense Center will combine flow summaries involving a host on your monitored network and one or more external hosts if the flows use the same port. see Combining Flow Summaries from External Responders in the Analyst Guide as well as Configuring RNA Detection Policy Settings in the Analyst Guide. However. Event views. However. This can reduce the space required to store flow data and can also speed up the rendering of flow data graphs. The default setting is 10080 minutes(7 days). Drop New Hosts When Host Limit Reached Combine Flows for Out-Of-Network Responders Select this check box if you want new hosts rather than old hosts dropped when the Defense Center reaches its host limit and the network map is full. in minutes. For more information. and if they were detected by the same detection engine (for flows detected by 3D Sensor) or were exported by the same NetFlow-enabled device and were processed by the same detection engine. For more information. service. Version 4. keep in mind that setting this option in the RNA detection policy requires that you set your flow data mode to Summary. protocol. This option is especially valuable if you want to prevent spoofed hosts from taking the place of valid hosts in the network map. which can reduce the number of events sent to the Defense Center.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA Data Storage Settings (Continued) Field Client Application Timeout Description The amount of time that passes. graphs. before RNA drops a client application from the network map due to inactivity. Select this check box if you want you want to combine flow summaries involving external hosts. Enabling this option treats flow summary data from IP addresses that are not in your list of monitored networks (as defined by your RNA detection policy) as coming from a single host. if you enable this option and you attempt to drill down to the table view of flow data (that is. IMPORTANT! Make sure that the client application timeout value is longer than the update interval in the RNA detection policy. and reports use external to indicate the hosts outside your monitored network. access data on individual flows) for a flow summary that involves an external responder. which prevents your 3D Sensors from transmitting individual flows to the Defense Center and therefore prevents you from taking advantage of any feature that requires data from individual flows. Note that you can also use the RNA detection policy to force your 3D Sensors to combine flow summaries involving external hosts before they transmit the data to the Defense Center.1 Sourcefire 3D System Administrator Guide 343 . instead of an individual IP address.9.

Duplicate flow events can also be created if you overlap network segment coverage with your RNA detection engines in your RNA detection policy. Duplicate flow events can be created if you use two RNA detection policies. Duplicate NetFlow events can be created.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA Data Storage Settings (Continued) Field Drop Duplicate RNA Flow Events Description Select this check box if you want the Defense Center to drop duplicate flow events generated by 3D Sensors with RNA. not following best practices can degrade performance as the Defense Center attempts to resolve the conflicts. Version 4.1 Sourcefire 3D System Administrator Guide 344 . Note that best practices are to use only one detection policy and to not overlap network segment coverage.9. if two NetFlow-enabled devices export information about the same session. only the reporting detection engine for the flow initiator generates a flow event. each detection engine generates a flow event when RNA detects that a connection is terminated between a monitored host on one of the networks and a monitored host on the other network. Drop Duplicate NetFlow Events Select this check box if you want the Defense Center to drop duplicate flow events that are based on NetFlow data. best practices are to avoid creating duplicate NetFlow events. Just as with RNA flow events. for example. For more information. each of which is monitoring a separate network segment using separate detection engines. if you use one policy to monitor both networks. In that scenario. On the other hand. and can also use excessive bandwidth. see Drop Duplicate RNA Flow Events.

if IPS generates an intrusion event and the Sourcefire 3D System is able to use any of the methods you specified to determine that the host involved in the event is vulnerable to the attack or exploit. For more information. See Understanding RNA Network Discovery Event Types in the Analyst Guide for information about each event type Expand this section and use the check boxes to specify the types of RNA host input events that you want to log in the database. See Understanding RNA Host Input Event Types in the Analyst Guide for information about each event type.9. see Understanding Nessus Scans in the Analyst Guide or the Sourcefire 3D System Host Input API Guide.1 Sourcefire 3D System Administrator Guide 345 . You can select any or all of the check boxes in this section.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Understanding Vulnerability Impact Assessment Settings Requires: DC/ MDC + RNA The RNA vulnerability impact assessment settings. see Using Impact Flags to Evaluate Events in the Analyst Guide. • Select the Use RNA Vulnerability Mappings check box if you want to use RNA vulnerability information to perform impact flag correlation. • Select the Use Third Party Scanner Vulnerability Mappings check box if you are using an integrated scan capability or the AddScanResult host input API function and you want to use vulnerability lookups from the scanner to perform impact flag correlation. RNA collates fingerprint information from several sources. Note that if you clear all the check boxes. For more information. Vulnerability Impact Assessment Settings Field Vulnerabilities to use for Impact Assessment Requires: IPS Description Select the check boxes in this section to configure how the Sourcefire 3D System performs impact flag correlation with intrusion events. select this option to use the Nessus vulnerability mappings. Version 4. as described in the following table. For more information. if you scan using Nessus. intrusion events will never be marked with the red impact flag. For example. • Select the Third Party Vulnerability Mappings check box if you want to use third-party vulnerability references to perform impact flag correlation. see Mapping Third-Party Vulnerabilities in the Analyst Guide. Host Input Event Logging Understanding Multiple Fingerprint Settings Requires: DC + RNA RNA matches fingerprints for operating systems and services against patterns in traffic to determine what operating system and which services are running on a particular host. RNA Event Logging Expand this section and use the check boxes to specify the types of RNA network discovery events that you want to log in the database. control which vulnerability types to use for impact assessment. the intrusion event will be marked with the red (Vulnerable) impact flag. To provide the most reliable operating system and service identity information.

For more information on current identities and how RNA selects the current identity. However. By default. identity conflicts are not automatically resolved and you must resolve them through the host profile or by rescanning the host or re-adding new identity data to override the RNA identity. see Enhancing Your Network Map in the Analyst Guide. Note that adding a scanner to this page does not add the full integration capabilities that exist for the Nmap and Nessus scanners. however. Note. as indicated in the Multiple Fingerprint Settings table. If you import data from a third-party application or scanner. By default. but does allow integration of imported application or scan results. unless there is an identity conflict. but only data from the highest priority application or scanner source is used as the current identity. RNA retains one identity for each source. identity data added by a scanner or application overrides identity data detected by RNA. You can use the Multiple Fingerprinting page to rank scanner and application fingerprint sources by priority.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 RNA uses all passive data to derive operating system identities and assign a confidence value. you can set your system to always automatically resolve the conflict by keeping the passive identity or to always resolve it by keeping the active identity. or change the priority or timeout settings for existing sources.9. An identity conflict occurs when RNA detects an identity that conflicts with an existing identity that came from the active scanner or application sources listed on the Multiple Fingerprinting page or from a user. that user input data overrides scanner and application data regardless of priority.1 Sourcefire 3D System Administrator Guide 346 . remember to make sure that you map vulnerabilities from the source to the RNA vulnerabilities in the network Version 4. You can add new active sources through this page.

select Scanner or Application. select Disabled from the Automatically Resolve Conflicts drop-down list. click Add in the Multiple Fingerprints page of the system policy. Multiple Fingerprint Settings Option Generate Identity Conflict Event Automatically Resolve Conflicts Description Enable this option to generate an event when an identity conflict occurs on a host in the network map. Scanner/ Application List You have several options: • To add a new source. Version 4. • To indicate the duration of time that should elapse between the addition of an identity to the network map by this source and the deletion of that identity. For more information. or Weeks from the Timeout drop-down list and type the appropriate duration. click the down arrow next to the source name. see Mapping Third-Party Vulnerabilities in the Analyst Guide. • To demote a source and cause the operating system and service identities to be used only if there are no identities provided by sources above it in the list. select Passive from the Automatically Resolve Conflicts drop-down list. • To change the type of source. • To use the RNA fingerprint when an identity conflict occurs. select Hours. You have the following options: • To force manual conflict resolution of identity conflicts. Days. Select Operations > System Policy. • To promote a source and cause the operating system and service identities to be used in favor of sources below it in the list.9. To specify RNA settings: Access: Admin 1. select Active from the Automatically Resolve Conflicts drop-down list.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 map. The System Policy page appears. from the Type drop-down list. Type a name for the source. • To use the current identity from the highest priority active source when an identity conflict occurs. Configuring Settings for RNA Requires: DC + RNA Use the following procedure to configure RNA settings in the system policy.1 Sourcefire 3D System Administrator Guide 347 . click the up arrow next to the source name.

the Access List page appears. click Create Policy.1 Sourcefire 3D System Administrator Guide 348 . Click RNA Settings. In either case. 3. See the RNA Data Storage Settings table on page 342 for more information. Version 4. You have two options: • • To modify the RNA settings in an existing system policy. click Edit next to the system policy.9. 4. Specify the RNA data storage settings that you want for your Defense Center.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2. The RNA Settings page appears. To configure the RNA settings as part of a new system policy. Provide a name and description for the system policy as described in Creating a System Policy on page 321. and click Save.

Optionally. as a time-saving and performance-maximizing measure. The system policy is updated. See Applying a System Policy on page 324 for more information. A network administrator may modify a network configuration through routing or host changes without informing you. you can configure the Defense Center to automatically update those policies and apply the updated policies to your RNA detection engines. 8. it may be able to refine any subnet recommendations it has made for your RNA detection policies. Choosing which subnets to monitor with which detection engines is an iterative process that you should revisit from time to time. Unfortunately.9. 7. Your changes do not take effect until you apply the system policy. 6.1 Sourcefire 3D System Administrator Guide 349 . you can use the system policy to configure RNA to automatically generate subnet recommendations for your currently applied RNA detection policies on a daily basis. Optionally. Optionally. specify the RNA network discovery events that you want to log by clicking the arrow next to RNA Event Logging. See the RNA Host Input Event Types table in the Analyst Guide for more information. you may not always be kept abreast of network configuration changes. All the event types are enabled by default. This is because RNA only gathers secondary information Version 4. Configuring RNA Subnet Detection Settings Requires: DC + RNA Optimally. especially if your network configuration has been altered through routing or host changes. you must revisit the detection policy after you apply it for the first time so that you can manually evaluate and apply any subnet recommendations. your RNA detection policy specifies that each RNA detection engine is configured as the reporting detection engine for the hosts that are closest to it from a network hop standpoint. Alternately. If you do not configure the Defense Center to automatically apply subnet recommendations. See the RNA Network Discovery Event Types table in the Analyst Guide for more information. which can make it challenging to stay on top of proper RNA policy configurations.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 5. Optionally. See the Multiple Fingerprint Settings table on page 347 for more information. configure multiple fingerprint settings to manage operating system and service source priorities and identity conflict resolution settings. Subnet detection allows RNA to make recommendations about which are the best detection engines to analyze the traffic on the various network segments in your organization. Click Save Policy and Exit. As RNA continuously monitors your network traffic. specify the RNA host input events that you want to log by clicking the arrow next to Host Input Event Logging. All the event types are enabled by default.

and so on. Version 4. flow data. if you configured the Defense Center to automatically apply recommendations. To get detailed information about the hosts in a subnet. to notify you of any changes made. including operating system and service identity data.1 Sourcefire 3D System Administrator Guide 350 .9. Note that you can configure the Defense Center to notify you of subnet recommendations via email so that you can make the changes manually. The following diagram illustrates the automated subnet detection process. or.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 (hops and MAC address data) about hosts in subnets that are set to autodetect. you must explicitly assign an RNA detection engine to monitor that subnet.

2. enter the email address where you want to receive notifications of new subnet recommendations. If your RNA deployment includes even one legacy (pre-Version 4. and click Save. in the Mail Notifications To field. To configure RNA subnet detection settings: Access: Admin 1.9 and later 3D Sensors. Click RNA Subnet Detection Settings. select the time when you want RNA to automatically generate daily subnet recommendations for all applied RNA detection policies. The System Policy page appears. select Disabled. Provide a name and description for the system policy as described in Creating a System Policy on page 321.1 Sourcefire 3D System Administrator Guide 351 . You have two options: • • To modify the RNA subnet detection settings in an existing system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 For more information on subnet detection. The RNA Subnet Detection Settings page appears. In either case. you must configure a valid mail relay host. see Configuring a Mail Relay Host and Notification Address on page 338. Optionally. For more information. 3. Select Operations > System Policy. click Edit next to the system policy. see Introduction to Sourcefire RNA in the Analyst Guide. see Manually Generating Subnet Recommendations in the Analyst Guide.9) 3D Sensor. To configure the RNA subnet detection settings as part of a new system policy. 5.9. RNA only automatically generates recommendations for RNA deployments running on Version 4. IMPORTANT! For performance reasons. you must manually generate and apply recommendations for your RNA detection policies. To disable daily generation of subnet recommendations. click Create Policy. From the Generate Recommendations Daily At drop-down list. Version 4. the Access List page appears. TIP! To receive email notifications. 4.

Your changes do not take effect until you apply the system policy. Configuring RUA Settings Requires: DC + RUA You can use the RUA settings in the system policy to filter which types of network activity cause RUA to add users to the database. Oracle. visitors. The system policy is updated. Version 4. This is because these logins are not associated with any of the user metadata that RUA obtains from an LDAP server. AIM. Note that this option has no effect unless you enable daily recommendations. obtaining usernames through protocols such as AIM. POP3. After you reach your licensed limit. In addition. and SIP logins always create duplicate user records. Enable the Automatically Apply Daily Recommendations check box to automatically update and apply your RNA detection policies after RNA generates subnet recommendations. and other guests. RUA can add users to the database using the following types of detected protocols: • • • • • • LDAP AIM POP3 IMAP Oracle SIP (VoIP) Note that although RUA detects SMTP logins. Restricting RUA helps minimize username clutter and preserve RUA licenses. 7. an RUA user is added to the Defense Center user database. the Defense Center does not record them unless there is already a user with a matching email address in the database. For example.9. RUA stops adding new users to the Defense Center database. The RUA feature license on the Defense Center (see Licensing RUA in the Analyst Guide) specifies the number of users you can monitor with RUA. Click Save Policy and Exit. See Applying a System Policy on page 324 for more information.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6.1 Sourcefire 3D System Administrator Guide 352 . When RUA detects a user login for a user who is not already in the database. RUA users are not added to the database based on SMTP logins. and IMAP can introduce usernames not relevant to your organization due to network access from contractors. Sourcefire RUA (see Using Sourcefire RUA in the Analyst Guide) is an optional component of the Sourcefire 3D System that allows you to correlate network activity with user identity information.

5. In either case. The system policy is updated. the Access List page appears. 2. Click Save Policy and Exit. Provide a name and description for the system policy as described in Creating a System Policy on page 321. The System Policy page appears. By default.1 Sourcefire 3D System Administrator Guide 353 . Select the check boxes that correspond to the types of logins that will create RUA users. 4. click Edit next to the system policy. For more information on RUA Agents and 3D Sensors with RUA. See Applying a System Policy on page 324 for more information. filtering non-LDAP logins has no effect. Therefore. see How Do I Choose an RUA Implementation? in the Analyst Guide.9. 3. unless your RUA implementation includes 3D Sensors with RUA. Your changes do not take effect until you apply the system policy. click Create Policy. Version 4. Click RUA Settings. You have two options: • • To modify the RUA settings in an existing system policy. IMPORTANT! Sourcefire RUA Agents installed on Microsoft Active Directory LDAP servers collect only LDAP user login information. Select Operations > System Policy. all login types cause RUA to add users to the database.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 nor are they associated with any of the information contained in the other types of login that your 3D Sensors detect. To configure the RUA settings as part of a new system policy. To filter RUA users based on network activity type: Access: Admin 1. The RUA Detection Settings page appears. and click Save.

if enabled).1 Sourcefire 3D System Administrator Guide 354 . You manage time settings on an Intrusion Agent through the operating system. For more information on configuring settings for RNA Software for Red Hat Linux. In either case. the time setting is not used until you apply the system policy. such as command line interfaces or the operating system interface. • • You can synchronize the appliance’s time with an external time server. Connections to NTP servers do not use configured proxy settings. Version 4. If you specify a remote NTP server. You must use native applications.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Synchronizing Time Requires: Any You can manage time synchronization on the appliance using the Time Synchronization page. The procedure for synchronizing time differs slightly depending on whether you are using the web interface on a Defense Center or a 3D Sensor. The System Policy page appears. your appliance must have network access to it. to manage time settings for software sensors: • For more information on configuring settings for Crossbeam Systems Switches. see Serving Time from the Defense Center on page 357. Sourcefire recommends that you synchronize your virtual appliances to a physical NTP server. In addition. Select Operations > System Policy. Do not synchronize your 3D Sensors (virtual or physical) to a Virtual Defense Center. To synchronize time on the Defense Center: Access: Admin 1. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide. but are stored on the appliance itself using UTC time. Each procedure is explained separately below.9. Note that time settings are displayed on most pages on the appliance in local time using the time zone you set on the Time Zone page (America/New York by default). see the Sourcefire 3D Sensor Software for X-Series Installation Guide. You can specify the time settings either by creating a new system policy or by editing an existing policy. the current time appears in UTC at the top of the Time Synchronization page (local time is displayed in the Manual clock setting option. You can choose to synchronize the time: • • manually using one or more NTP servers (one of which can be a Defense Center) Time settings are part of the system policy. To use the Defense Center as an NTP server.

in the Serve time via NTP drop-down list. select Via NTP Server from and. and click Save.1 Sourcefire 3D System Administrator Guide 355 . • WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. To receive time through NTP from a different server. the DHCP-provided NTP server will be used instead. Only Defense Centers can act as NTP servers. select Enabled.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2. See Setting the Time Manually on page 389 for information about setting the time after you apply the system policy. click Create Policy. 3. you should configure your DHCP server to set the same NTP server. Version 4. type a comma-separated list of IP addresses for the NTP servers you want to use or. Note that if you set this option to Enabled and then apply the system policy to a sensor rather than a Defense Center. If you want to serve time from the Defense Center to your managed sensors. Click Time Synchronization. 5. In either case.9. this value is ignored. the Access List page appears. To configure the time settings as part of a new system policy. in the text box. 4. click Edit next to the system policy. select Manually in the System Settings. Provide a name and description for the system policy as described in Creating a System Policy on page 321. You have two options for specifying how the time is synchronized on the appliance: • To set the time manually. The Time Synchronization page appears. To avoid this situation. You have two options: • • To modify the time settings in an existing system policy. if DNS is enabled. type the fully qualified host and domain names.

To configure the time settings as part of a new system policy. You have two options: • • To modify the time settings in an existing system policy. The system policy is updated.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6.1 Sourcefire 3D System Administrator Guide 356 . the Access List page appears. The System Policy page appears. Your changes do not take effect until you apply the system policy. click Create Policy. and click Save. IMPORTANT! It may take a few minutes for the appliance to synchronize with the configured NTP servers. You have two options for specifying how time is synchronized on the 3D Sensor: Version 4. Select Operations > System Policy. The Time Synchronization page appears. Click Time Synchronization. 2. In either case. 4. click Edit next to the system policy. To synchronize time on a 3D Sensor: Access: Admin 1. See Applying a System Policy on page 324 for more information. 3.9. Click Save Policy and Exit. Provide a name and description for the system policy as described in Creating a System Policy on page 321.

9. • 5. before configuring the Defense Center to serve time using NTP If you need to .1 Sourcefire 3D System Administrator Guide 357 . Serving Time from the Defense Center Requires: DC/MDC You can configure the Defense Center as a time server using NTP and then use it to synchronize time between the Defense Center and managed 3D Sensors. if DNS is enabled. Version 4. On the Defense Center. IMPORTANT! If you configure the Defense Center to serve time using NTP and . the NTP service on managed sensors will still attempt to synchronize time with the Defense Center. if you are synchronizing the 3D Sensor to a Defense Center that is configured as an NTP server. See Setting the Time Manually on page 389 for information about setting the time after you apply the system policy. type a comma-separated list of IP addresses of the NTP servers or. change the time manually after configuring the Defense Center as an NTP server. select Via NTP Server from and. it may take some time for the time to synchronize. then later disable it. disable the Via NTP option and click Save.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 • To set the time manually. To receive time through NTP from different servers. The system policy is updated. To configure the Defense Center as an NTP server: Access: Admin 1. you should do so . The System Policy page appears. in the text box. You must disable NTP from the managed sensors’ web interfaces to stop the synchronization attempts. change the time manually and click Save. select Manually in the System Settings. and the Defense Center itself is configured to use an NTP server. select Operations > System Policy. In addition. IMPORTANT! It may take a few minutes for the 3D Sensor to synchronize with the configured NTP servers. See Applying a System Policy on page 324 for more information. TIP! You cannot set the time manually after configuring the Defense Center to serve time using NTP If you need to manually change the time. and then enable Via NTP and click Save. Click Save Policy and Exit. Your changes do not take effect until you apply the system policy. type the fully qualified host and domain names. This is because the Defense Center must first synchronize with its configured NTP server before it can serve time to the 3D Sensor.

Managing System Policies Configuring the Parts of Your System Policy Chapter 9 2. The system policy is updated. click Create Policy. 3. From the Serve Time via NTP drop-down list. all vulnerabilities associated with SMTP applications are added to the host profile for the host. 5. In the Set My Clock option for the sensors. select Enabled. many services do not include vendor and version information. Provide a name and description for the system policy as described in Creating a System Policy on page 321. You have two options: • • To modify the NTP server settings in an existing system policy. then apply that policy to the Defense Center managing the sensor that detects the traffic. Version 4. Click Save Policy and Exit. select Via NTP from Defense Center. 4. the Access List page appears. when the service has a service ID in the RNA database and the packet header for the traffic includes a vendor and version. To configure the NTP server settings as part of a new system policy. The Time Synchronization page appears. In either case. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. Mapping Vulnerabilities for Services Requires: DC/MDC RNA automatically maps vulnerabilities to a host for any service traffic received or sent by the host. IMPORTANT! It may take a few minutes for the Defense Center to synchronize with its managed sensors. If you enable the SMTP service on the Vulnerability Mapping page of a system policy. the service information will not be used for vulnerability mapping because you cannot specify a vendor or version for a custom service and cannot select the service for vulnerability mapping in the system policy. click Edit next to the system policy. However. and click Save. a host receives SMTP traffic that does not have a vendor or version in the header. See Applying a System Policy on page 324 for more information. you can configure whether RNA associates vulnerabilities with service traffic for vendor and versionless services. 6. For the services listed in the system policy.1 Sourcefire 3D System Administrator Guide 358 . Click Time Synchronization.9. For example. Note that although RNA detectors collect service information and add it to host profiles.

The System Policy page appears.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 To configure vulnerability mapping for services: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 359 . and click Save. 5. • TIP! You can select or clear all check boxes at once using the check box next to Enable. 2. Version 4. In either case. The system policy is updated. Select Operations > System Policy. You have two options: • • To modify active fingerprint source settings in an existing system policy. See Applying a System Policy on page 324 for more information. Your changes do not take effect until you apply the system policy to the Defense Center and its managed sensors. the Access List page appears. 3. To cause vulnerabilities for a service to be mapped to hosts that receive service traffic without vendor or version information. clear the check box for that service. Provide a name and description for the system policy as described in Creating a System Policy on page 321. click Edit next to the system policy. To configure active fingerprint source settings as part of a new system policy. select the check box for that service. Click Save Policy and Exit. 4. You have two options: • To prevent vulnerabilities for a service from being mapped to hosts that receive service traffic without vendor or version information.9. Click Vulnerability Mapping. The Vulnerability Mapping page appears. click Create Policy.

Contrast the system settings. See Managing System Policies on page 320 for more information. which are likely to be specific to a single appliance. with a system policy. which controls aspects of an appliance that are likely to be similar across a deployment. Version 4.Configuring System Settings Chapter 10 Administrator Guide The system settings include a series of linked pages that you can use to view and modify settings on your appliance.1 Sourcefire 3D System Administrator Guide 360 .9.

Remote Management On the 3D Sensor. Allows you to view and modify the settings for the network interfaces on your appliance. then you can use this page to change the time. See Configuring the Communication Channel on page 383 for more information. enables you to establish communications with a Defense Center from the sensor. Time Displays the current time. See Configuring Network Settings on page 377 for more information.1 Sourcefire 3D System Administrator Guide 361 . If the time synchronization settings in the current system policy for the appliance is set to Manual. License Network Network Interface Process Version 4. See Editing Network Interface Configurations on page 380 for more information. enables you to specify values for the internal network and management port that the Defense Center uses to communicate with its managed sensors and high availability peer. See Viewing and Modifying the Appliance Information on page 362 for more information. Enables you to change options such as the IP address. On the Defense Center. System Settings Options Option Information Description Allows you to view current information about the appliance.Configuring System Settings Chapter 10 The System Settings Options table describes the options you can configure in the system settings. and proxy settings of the appliance that were initially set up as part of the installation.9. hostname. See Configuring Remote Access to the Defense Center on page 386 for more information. You can also change the appliance name. See Setting the Time Manually on page 389 for more information. Provides you with options for managing your current licenses and for adding additional feature licenses on the platforms that support them. Provides options that you can use to: • shut down the appliance • reboot the appliance • restart the Sourcefire 3D System-related processes See Shutting Down and Restarting the System on page 382 for more information. See Understanding Licenses on page 364 for more information.

The information includes view-only information such as the product name and model number. See Specifying NetFlow-Enabled Devices on page 392 for more information. The page also provides you with an option to change the name of the appliance. The Series 2 DC1000 or DC3000 Defense Center version of this the page is shown below. with a list on the left side of the page that you can use to access other system settings. See Blacklisting Health Modules on page 391 for more information. On the Defense Center. The Information page appears. Viewing and Modifying the Appliance Information Requires: Any The Information page provides you with information about the Defense Center or 3D Sensor. and the current appliance-level policies. NetFlow Devices Remote Storage To configure the system settings: Access: Admin Select Operations > System Settings. the operating system and version. allows you to configure remote storage for backups and reports.Configuring System Settings Viewing and Modifying the Appliance Information Chapter 10 System Settings Options (Continued) Option Health Blacklist Description On the Defense Center.9. See Managing Remote Storage on page 393 for more information. allows you to specify the NetFlow-enabled devices you want to use to collect flow data.1 Sourcefire 3D System Administrator Guide 362 . allows you to temporarily disable health monitoring for a 3D Sensor to prevent the Defense Center from generating unnecessary health events. On Series 2 DC1000 and DC3000 Defense Centers. IMPORTANT! You cannot view sensor information for Intrusion Agents. Version 4.

The operating system currently running on the appliance. The IP address of the appliance.9. Note that this name is only used within the context of the Sourcefire 3D System.Configuring System Settings Viewing and Modifying the Appliance Information Chapter 10 The Appliance Information table describes each field. but not the managed sensor. The appliance-level policies currently applied to the appliance. If a policy has been updated since it was last applied. Enable this check box to store event data on the Defense Center.1 Sourcefire 3D System Administrator Guide 363 . Product Model Software Version Store Events Only on Defense Center Prohibit Packet Transfer to the Defense Center Operating System Operating System Version IP Address Current Policies Model Number Version 4. Clear this check box to store event data on both appliances. the name of the policy appears in italics. entering a different name in this field does not change the hostname. The version of the operating system currently running on the appliance. The version of the software currently installed. The model name for the appliance. Enable this check box to prevent the managed sensor from sending packet data with the events. The model number for the appliance. Clear this check box to allow packet data to be stored on the DC with events. Although you can use the hostname as the name of the appliance. This number can be important for troubleshooting. Appliance Information Field Name Description A name you assign to the appliance.

Understanding Licenses Requires: Any You can license a variety of products and features to create your optimal deployment. The Information page appears. 2. the Sourcefire 3D System requires that you enable IPS by applying a product license file to each appliance as part of the installation process. To change the appliance name. the 3D Sensor version of the page is shown below. Version 4.Configuring System Settings Understanding Licenses Chapter 10 To modify the appliance information: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 364 . The page refreshes and your changes are saved. For Defense Centers. Select Operations > System Settings. The Defense Center version of the page is shown below. click Save.9. To save your changes. type a new name in the Name field. You can also add feature licenses such as RNA host licenses and Intrusion Agent licenses. For comparison. 3. WARNING! The name must be alphanumeric characters and should not be composed of numeric characters only.

TIP! You can view your licenses by using the Product Licensing widget in the dashboard.9.. see Sourcefire 3D Sensor Installation Guide. see Understanding Feature Licenses on page 366. see Adding Feature Licenses on page 370. a 3D Sensor or a Defense Center during installation so that you can. For information on how to use virtual appliances. Version 4. See Understanding the Product Licensing Widget on page 84 for more information. Virtual License a Defense Center at any time use virtual machines.. see the Sourcefire Licenses table on page 365. For information on IPS. For information on adding a product license.. For information on how the various features function. Product License to. RUA.. To understand why and when to use these licenses. and so on. For information on how to add a feature license. Sourcefire Licenses You apply a.1 Sourcefire 3D System Administrator Guide 365 . and Sourcefire Defense Center Installation Guide. use IPS on that appliance.. see Sourcefire Virtual Defense Center and 3D Sensor Installation Guide. see Introduction to Sourcefire IPS in Sourcefire 3D System Analyst Guide Feature License a Defense Center at any time use additional features such as RNA.Configuring System Settings Understanding Licenses Chapter 10 See the following for more information: • • • Understanding Feature Licenses on page 366 Verifying Your Product License on page 368 Managing Your Feature Licenses on page 370 You can use a variety of appliances and optional features in your deployment.

or network vulnerabilities transmit events generated by open source Snort installations to the Defense Center IPS for use with Crossbeam Systems X-Series you need a license for. capture and export data about the traffic that passes through NetFlow-enabled devices monitor hosts on your network (including hosts discovered by NetFlow-enabled devices) to observe your network traffic to analyze a complete. the Sourcefire 3D System uses RNA detection engines on 3D Sensors to analyze NetFlow data..1 Sourcefire 3D System Administrator Guide 366 . up-to-the-minute profile of your network correlate threat. NetFlows. NetFlow is available not only on Cisco networking devices. IPS Software Sensors. FreeBSD. RNA Hosts. NetFlow NetFlow is an embedded instrumentation within Cisco IOS Software that characterizes network operation. and network intelligence with user identity information identify the source of policy breaches. Although you can use NetFlow-enabled devices exclusively to monitor your network. RUA Users and either RNA Hosts or the product license (or both). and your deployment must include at least one 3D Sensor with RNA that can communicate with your NetFlow-enabled devices. Standardized through the RFC process. and use NetFlow data to monitor those networks. The NetFlow cache stores a record of every flow (a sequence of packets that represents a connection between a source and destination host) that passes through the devices.Configuring System Settings Understanding Licenses Chapter 10 Understanding Feature Licenses The Feature Licenses table describes how to determine which features to license for your deployment.. endpoint. You must use a Defense Center to configure NetFlow data collection and to view the collected data. Intrusion Agents. Feature Licenses If you want to. You can deploy NetFlow-enabled devices on networks that your sensors cannot monitor. attacks. RUA Users.. For more information.. Version 4. see Introduction to NetFlow in the Sourcefire 3D System Analyst Guide.9. NetFlow-enabled devices are widely used to capture and export data about the traffic that passes through those devices. and OpenBSD devices. but can also be embedded in Juniper.

behavioral profiling. For more information.1 Sourcefire 3D System Administrator Guide 367 . You can then analyze the events detected by Snort alongside your other data. the Defense Center assigns impact flags to the events. see Using Sourcefire RUA in the Sourcefire 3D System Analyst Guide. and built-in alerting and remediation. RNA is installed on most 3D Sensors. Intrusion Agent If you have an existing installation of Snort®.Configuring System Settings Understanding Licenses Chapter 10 RNA Host Sourcefire RNA allows your organization to confidently monitor and protect your network using a combination of forensic analysis. If the network map on the Defense Center has entries for the target host in a given event. and network intelligence with user identity information. see Introduction to Sourcefire RNA in the Sourcefire 3D System Analyst Guide. you can do analysis and reporting on those events. Version 4. or network vulnerabilities. as well as mitigate risk. also called RUA. RUA Host Sourcefire Real-time User Awareness. traffic. By default. block users or user activity. attacks. You can continue to manually tune Snort rules and preprocessors with the Intrusion Agent in place. In addition. For more information. up-tothe-minute profile of your network. and events directly to individual users. to control how network intelligence is gathered and to view the resulting information. endpoint. RUA can help you to identify the source of policy breaches. All RUA deployments require a Defense Center that has an RUA feature license installed. 3D Sensors with RNA passively observe your organization’s network traffic and analyze it to provide you with a complete. to enable RNA functionality.) Sourcefire also makes key components of RNA available in installation packages for Red Hat Linux servers and Crossbeam Systems security switches. allows your organization to correlate threat. you must manage 3D Sensors with RNA with a Defense Center. you can install an Intrusion Agent to forward intrusion events to a Defense Center. that Defense Center must have an RNA host license installed and the 3D Sensor must have a product license installed. and take action to protect others from disruption. If your organization uses LDAP you can use the user information on your . These capabilities also significantly improve audit controls and enhance regulatory compliance. see Sourcefire 3D System Intrusion Agent Configuration Guide.9. (The 3D9800 does not support RNA. However. For more information. LDAP server to augment the Defense Center’s database of user identity information with available metadata. By linking network behavior. Although you cannot manage policies or rules for an Intrusion Agent from the Defense Center.

1 Sourcefire 3D System Administrator Guide 368 . To verify the product license file: Access: Admin 1. and deleting feature licenses. viewing. The Information page appears. 2.Configuring System Settings Understanding Licenses Chapter 10 IPS Software Sensor An IPS Software Sensor allows you to use 3D Sensor Software for X-Series on a Crossbeam® Next Generation Security Platform to gather network intelligence and intrusion information. Version 4. Verifying Your Product License Requires: Any During installation. see Sourcefire Crossbeam Installation Guide XOS. For information on adding. the user who sets up the appliance adds the software license as part of the process.9. see Managing Your Feature Licenses on page 370. In most cases. Select Operations > System Settings. The License page appears. you do not need to re-install the license. Click License. For more information.

Click Verify License.1 Sourcefire 3D System Administrator Guide 369 . a message appears under the License field. you will receive an error message.com/. paste it into the License field (as shown in Step 3). Continue with step 5 to obtain a license and install it. which will be sent to you in an email. • • If the license file is valid.sourcefire. and the features for the appliance are available in the web interface. Click Get License. If the license file is invalid. the license is added to the appliance. Copy the license key at the bottom of the page and browse to https://keyserver. The Licensing Center web site appears. The Manage License page appears. Copy the license file from the email. IMPORTANT! If you purchased a feature license. IMPORTANT! If your web browser cannot access the Internet. Version 4. Follow the on-screen instructions for an appliance license to obtain your license file. If the license file is correct. you must switch to a host that can access it.9. 7. For more information about feature licenses. 6. Under Product Licenses. 5. 4. click Edit.Configuring System Settings Understanding Licenses Chapter 10 3. Do not proceed to step 5. and click Submit License. see Managing Your Feature Licenses on page 370. click Add New License and add it using the Add Feature License page.

Configuring System Settings Understanding Licenses Chapter 10 Managing Your Feature Licenses Requires: DC The Defense Center uses feature licenses to allow for additional features. you can find it by logging into the Sourcefire Support Site (https://support. See the following sections for more information: • • • Adding Feature Licenses on page 370 Viewing Feature Licenses on page 372 Configuring Network Settings on page 377 Adding Feature Licenses Requires: DC If you need to obtain a feature license for a feature you purchased. IMPORTANT! Both Defense Centers in a high-availability pair must have NetFlow licenses for at least the number of NetFlow-enabled devices you are using. you must add them to the Defense Center from the web interface.1 Sourcefire 3D System Administrator Guide 370 . Feature licenses include: • • • • • • NetFlow licenses. then clicking Products & Contracts. which allow you use virtual sensors in your deployment IPS licenses for Crossbeam. which allow you to use the RUA feature Intrusion Agent licenses. which allow you to use 3D Sensor Software with IPS on Crossbeam Systems security switches When you purchase license packs for any licensable feature. which allow you to use intrusion agents 3D Virtual Sensors. which specify the number of hosts that you can monitor with RNA RUA licenses.sourcefire.9. The serial number appears in the Sourcefire Software & Licenses section. you can request it from the web interface. which specify the number of NetFlow-enabled devices you can use to gather flow data RNA host licenses.com/). If you do not have the serial number. you should have the 12-digit feature license serial number provided by Sourcefire when you purchased the licensable feature. If one Defense Center does not have a NetFlow license. it will not receive data from your NetFlow-enabled devices. clicking Account. Version 4. Before beginning.

The Add Feature License page appears. Version 4.Configuring System Settings Understanding Licenses Chapter 10 To add a license: Access: Admin 1. 2. The Information page appears. 3. Select Operations > System Settings. Click Add New License.9. The License page appears.1 Sourcefire 3D System Administrator Guide 371 . Click License.

A summary of your licenses appears below the itemized list. If you have feature or host licenses installed.sourcefire. model code. copy the license file from the email. Copy the license key at the bottom of the page and browse to https://keyserver. you must switch to a host that can access it. For more information about viewing and modifying product licenses. 6.1 Sourcefire 3D System Administrator Guide 372 . and shows the total number of hosts. and so on).com/. 5.Configuring System Settings Understanding Licenses Chapter 10 4. You can repeat this process for each feature license you need to add. paste it into the License field. exporters. After you receive an email with the feature license file. the license is added to the appliance. See Understanding the Product Licensing Widget on page 84 for more information. node (MAC address). and the licensed feature is available. TIP! Your Defense Center can have multiple feature licenses (for example. which will be sent to you in an email. and expiration date. If the license file is correct. and click Submit License.9. Version 4. The Licensing Center web site appears. IMPORTANT! If your web browser cannot access the Internet. they appear itemized below the product license. RUA. see Verifying Your Product License on page 368. Note that there is only one product license. virtual appliances. TIP! You can also view licenses by using the Product Licensing widget on the dashboard. Click Get License. connections. one or more licenses for RNA Hosts in addition to one or more licenses for Intrusion Agents. and provides a link that allows you to view or edit the license. Follow the on-screen instructions for a feature license to obtain your license file. Viewing Feature Licenses Requires: DC The licenses page displays the product and feature licenses that you have added to the Defense Center. or users allowed by the sum of your feature or host licenses. The first license that appears shows the Defense Center’s product license which shows the license status.

9. or if a temporary license has expired.Configuring System Settings Understanding Licenses Chapter 10 The NetFlow License Columns table describes each column that appears in a NetFlow license.1 Sourcefire 3D System Administrator Guide 373 . Displays the feature serial number. NetFlow License Columns Column Feature ID Serial Number Status Model Allowed NetFlow Exporters Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. invalid. Displays the appliance’s MAC address. Displays the appliance model number. invalid. Version 4. Indicates if the license is valid. Indicates if the license is valid. Displays the date and time that the feature license expires. Displays the appliance model number. Lists the number of monitored hosts added by the license. Lists the number of NetFlow-enabled devices that the license allows you to use. Displays the appliance’s MAC address. Allows you to delete the feature license by clicking Delete. The RNA Host License Columns table describes each column that appears in an RNA host license. Displays the feature serial number. RNA Host License Columns Column Feature ID Serial Number Status Number of Hosts Model Node Description Displays the ID number that corresponds with the feature being licensed. or if a temporary license has expired.

Configuring System Settings Understanding Licenses Chapter 10 RNA Host License Columns (Continued) Column Expires Action Description Displays the date and time that the feature license expires. Displays the date and time that the feature license expires. Lists the number of monitored users added by the license. Displays the feature serial number. Displays the feature serial number. Indicates if the license is valid. Displays the appliance’s MAC address. Displays the appliance model number. RUA License Columns Column Feature ID Serial Number Status Model Number of Users Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. or if a temporary license has expired.1 Sourcefire 3D System Administrator Guide 374 .9. The Intrusion Agent License Columns table describes each column that appears in an intrusion agent license. Allows you to delete the feature license by clicking Delete. invalid. Version 4. Allows you to delete the host license by clicking Delete. Intrusion Agent License Columns Column Feature ID Serial Number Description Displays the ID number that corresponds with the feature being licensed. The RUA License Columns table describes each column that appears in an RUA host license.

Displays the appliance model number.Configuring System Settings Understanding Licenses Chapter 10 Intrusion Agent License Columns (Continued) Column Status Model Swagent Max Connections Node Expires Action Description Indicates if the license is valid. Displays the feature serial number. Maximum throughput is limited by other factors such as number of Virtual Machines on your VMware server. Allows you to delete the feature license by clicking Delete.1 Sourcefire 3D System Administrator Guide 375 . Lists the maximum number of Virtual 3D Sensors allowed by the license. invalid. Displays the appliance’s MAC address. invalid. Lists the maximum number of software agent connections allowed by the license. or if a temporary license has expired. Displays the date and time that the feature license expires. The Virtual 3D Sensor License Columns table describes each column that appears in an intrusion agent license. Indicates if the license is valid. Displays the maximum capacity licensed for processing by the Virtual 3D Sensor (20. or if a temporary license has expired. IMPORTANT! These speeds are not a guaranteed throughput for the Virtual 3D Sensor you license. Version 4. Displays the appliance model number. or 250MB). its connections. 100.9. Virtual 3D Sensor License Columns Column Feature ID Serial Number Status Model Allowed Virtual Sensors Node Throughput Limit Description Displays the ID number that corresponds with the feature being licensed. and other physical hardware constraints. Displays the appliance’s MAC address. 45.

Configuring System Settings Understanding Licenses Chapter 10 Virtual 3D Sensor License Columns (Continued) Column Expires Action Description Displays the date and time that the feature license expires. Allows you to delete the feature license by clicking Delete. Version 4. invalid.1 Sourcefire 3D System Administrator Guide 376 . To view or delete your feature licenses: Access: Admin 1. Allows you to delete the feature license by clicking Delete. Displays the feature serial number. or if a temporary license has expired. Indicates if the license is valid. Displays the appliance model number. The Information page appears.9. Displays the appliance’s MAC address. The IPS Software License Columns table describes each column that appears in an IPS Software license. Displays the date and time that the feature license expires. IPS Software License Columns Column Feature ID Serial Number Status Model Node Expires Action Description Displays the ID number that corresponds with the feature being licensed. Select Operations > System Settings.

or both IPv4 and IPv6 network settings in System Settings. For more information on configuring settings for Intrusion Agents. The exceptions include software sensors or 3Dx800 sensors. such as command line interfaces.1 Sourcefire 3D System Administrator Guide 377 . IPv6. see the Intrusion Agent Configuration Guide. For the feature that you want to delete.9. The License page appears. see the 3D Sensor Installation Guide. For more information on configuring settings for 3Dx800 appliances. to manage network settings for software sensors or 3Dx800 sensors: • For more information on configuring settings for Crossbeam-based software sensors. For more information on configuring settings for RNA Software for Red Hat Linux. click Delete in the Action column. you must manually configure all network properties. For more information on configuring settings for Virtual 3D Sensors. Disabled (IPv4 or IPv6) Manual (IPv4 and IPv6) DHCP (IPv4 and IPv6) Router assigned (IPv6 only) • • • • You have the following configuration options: • • • • If you specify manual. Version 4. If you specify DHCP the appliance automatically retrieves its network settings from a . or the operating system interface. see the Virtual Defense Center and 3D Sensor Installation Guide. 3. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide.Configuring System Settings Configuring Network Settings Chapter 10 2. Click License. You must use native applications. showing the product license and any feature licenses you have added. Configuring Network Settings Requires: Any With some exceptions. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. third-party user interfaces. your Sourcefire 3D System provides a dual stack implementation so that you can choose IPv4.

In most installations.Configuring System Settings Configuring Network Settings Chapter 10 local DHCP server. the appliance retrieves its network settings from a local router.255. the new name is not reflected in the syslog until after you reboot the appliance. Select Operations > System Settings. Version 4. the management interface is connected to an internal. The Information page appears. you specify Router assigned.1 Sourcefire 3D System Administrator Guide 378 . This is the network through which Defense Centers and sensors communicate. • For IPv6. the appliance is configured to directly connect to the Internet. you must set the address and netmask in dotted decimal form (for example: a netmask of 255.9. Domain Primary DNS Server Secondary DNS Server Tertiary DNS Server The fully-qualified domain name where the appliance resides The IP address of the DNS server for the network where the appliance resides A secondary DNS server’s IP address A tertiary DNS server’s IP address If the appliance is not directly connected to the Internet. If. in the case of IPv6. To configure network settings: Access: Admin 1. Default Network Gateway Hostname The IP address of the gateway device for your network The DNS-resolvable name for the appliance IMPORTANT! If you change the hostname. By default. you must set the address in colon-separated hexadecimal form and the number of bits in the prefix (for example: a prefix length of 112). you can configure a proxy server to be used when downloading updates and SEUs.0). protected network. Manual Network Configuration Settings Setting Management Interface Address and either IPv4 Netmask or IPv6 Prefix Length Description The IP address for the management interface.0. • For IPv4.

If you selected Manual. 4. Specify which IP version (v4. Select DHCP to allow DHCP server network setting resolution. Click Network. You can change the Shared Settings (hostname. v6.9. domain.Configuring System Settings Configuring Network Settings Chapter 10 2.1 Sourcefire 3D System Administrator Guide 379 . or both) you want to use by selecting the Configuration from the IPv4 and IPv6 settings: • • • • Select Disabled to use only the alternative IP version (for example. The Network page appears. See the Manual Network Configuration Settings table on page 378 for a full description of each field you can configure. and domain servers) if you use manual or router assigned configurations. 3. if your network uses only IPv6. in the IPv4 section select Disabled). Version 4. specify the network settings. Select Router assigned (an IPv6-only configuration) to allow router assigned network setting resolution. Select Manual to manually specify network settings.

1 Sourcefire 3D System Administrator Guide 380 . To configure network interfaces from a Defense Center. Version 4.Configuring System Settings Editing Network Interface Configurations Chapter 10 5. To edit a network interface: Access: Admin 1. select Manual proxy configuration and enter the IP address or fully qualified domain name of your proxy server in the HTTP Proxy field and the port in the Port field. If your appliance is not directly connected to the Internet. You have two choices: • • To configure network interfaces from a 3D Sensor. To configure a proxy server. If your network uses a proxy. you have two options: • • If you have a direct connection from the appliance to the Internet. The network settings are changed. the sensor drops traffic while the network interface card renegotiates its network connection. By default. WARNING! Do not modify the settings for the management interface unless you have physical access to the appliance. The System Settings page appears. select Operations > Sensor. You must configure 3Dx800 interfaces on the 3Dx800 CLI.9. Editing Network Interface Configurations Requires: DC or 3D Sensor You can use the Network Interface page to modify the default settings for each network interface on your appliance. select Operations > System Settings. If you change the link mode for a sensing interface. select Direct connection. you can identify a proxy server to be used when downloading updates and rules. It is possible to select a setting that makes it difficult to access the web interface. then click Edit next to the 3D Sensor. appliances are configured to connect directly to the Internet. 6. Click Save. Any changes you make to the Auto Negotiate value are ignored for Gigabit interfaces.

9. listing the current settings for each interface on your appliance. 3. Click Edit next to the interface that you want to modify. Click Network Interface. The current settings for the interface appear: These setting include: • • • • • interface name sensor name interface type.1 Sourcefire 3D System Administrator Guide 381 . The Network Interface page appears.Configuring System Settings Editing Network Interface Configurations Chapter 10 2. either Sensing or Management interface description whether the interface is configured to auto-negotiate speed and duplex settings Version 4.

but does not physically shut off power.9. You can: • • • • shut down the appliance reboot the appliance restart communications. for an appliance without a power button. N/A in this column indicates that the interface does not support MDI/MDIX the current link mode. unplug it. N/A indicates that there is no link for the interface • You can modify the interface name and description. the process shuts down the operating system on the appliance. • Series 2 3D Sensors only If you disable auto negotiation and specify a link mode.1 Sourcefire 3D System Administrator Guide 382 . you must press the power button on the appliance. keep the following in mind: • In the Auto Negotiate field. If you need to specify a link mode.Configuring System Settings Shutting Down and Restarting the System Chapter 10 • whether the interface is configured for MDI (medium dependent interface). Shutting Down and Restarting the System Requires: Any You have several options for controlling the processes on your appliance. MDI/MDIX settings. 4. making it impossible for the endpoints to attain link unless you manually set the required MDI/MDIX mode. The Network Interface page appears again. when you set a specific link mode. or. select Off only if you require a specific link mode setting. MDI/MDIX is set to Auto. select it in the Link Mode field. you must also set the MDI/MDIX field to the required MDI or MDIX mode. Version 4. However. Click Save. You cannot change the Auto Negotiate setting for 10Gb interfaces. including the bandwidth and duplex setting (Full or Half). and the link mode as needed. which automatically handles switching between MDI and MDIX to attain link. To shut off power to the appliance. automatic MDI/MDIX handling is disabled. Normally. or Auto mode (Series 2 3D Sensors only). Any changes you make to the Auto Negotiate value are ignored for Gigabit interfaces. MDIX (medium dependent interface crossover). You must configure 3Dx800 interfaces on the 3Dx800 CLI. and http server processes on the appliance (this is typically used during troubleshooting) restart the RNA and Snort processes (Snort runs on the 3D Sensor only if you are licensed to use IPS) IMPORTANT! If you shut down the appliance. However. database.

3. To restart the Snort and RNA processes. To reboot the system. The Defense Center version of the page is shown below.0.1 Sourcefire 3D System Administrator Guide 383 . The default port for communications between the Defense Center. click Run Command next to Reboot Defense Center. The Appliance Process page appears. click Run Command next to Restart Detection Engines. To restart the 3D Sensor. its high availability peer is 8305/tcp. Click Process. The Information page appears. its managed sensors.0/ 16. click Run Command next to Restart Appliance Console. Enhancements in the current software eliminate the need for the management virtual network provided both the Defense Center and the sensors it manages are Version 4. For 3D Sensor • • • • Configuring the Communication Channel Requires: DC + 3D Sensor Version 4. Note that this logs you out of the Defense Center. Select Operations > System Settings. Note that restarting the Defense Center may cause deleted hosts to reappear in the network map. 2. to its Defense Center peer. The communication on port 8305 is bi-directional. The default address range is 172.9. click Run Command next to Shutdown Appliance. To restart the Defense Center. To reboot the system.Configuring System Settings Configuring the Communication Channel Chapter 10 To shut down or restart your appliance: Access: Admin 1. in high availability deployments. click Run Command next to Restart Defense Center Console.8 and earlier Defense Centers and sensors use a range of internal network IP addresses called the management virtual network to transmit thirdparty communications such as NTP to managed sensors and. Specify the command you want to perform: For DC/MDC • • • To shut down the Defense Center. click Run Command next to Shutdown Defense Center.16. To shut down the 3D Sensor. and if high availability is enabled. click Run Command next to Reboot Appliance. Note that this logs you out of the 3D Sensor.

You can not edit the Management Virtual Network field of a Master Defense Center. see the Sourcefire 3D Sensor Installation Guide. For more information on configuring settings for Intrusion Agents. third-party user interfaces. Version 4. such as command line interfaces. For more information on configuring settings for 3Dx800 sensors. or the operating system interface. IMPORTANT! The management virtual network is required only when the Defense Center must communicate with sensors running an older version. but you can change it later.0. For more information on configuring settings for RNA Software for Red Hat Linux. you can specify different values.1 Sourcefire 3D System Administrator Guide 384 . and Intrusion Agents. The user interface prevents you from entering the address range for the management network. see the Sourcefire RNA Software for Red Hat Linux Configuration Guide. If both the Defense Center and all sensors have been upgraded to the current version. but make sure you do not to enter a range that overlaps other local networks.Configuring System Settings Configuring the Communication Channel Chapter 10 both using the current software. you will need to use a management virtual network and ensure that it does not conflict with other communications on your network.0. refer to: • • Setting Up the Management Virtual Network on page 384 Editing the Management Virtual Network on page 385 Setting Up the Management Virtual Network Requires: DC + 3D Sensor If the IP address range or the port conflicts with other communications on your network. For more information. The field is filled with 0. WARNING! The IP address range you specify for the Management Virtual Network must not conflict with any other local network. if your Defense Center is running the current version of the software and the sensors it manages are running an older version of the software. This is usually configured as part of the installation process. IMPORTANT! Master Defense Centers do not currently use a Management Virtual Network.9. the management virtual network is unnecessary. However.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. see the Sourcefire 3D Sensor Software for X-Series Installation Guide. to manage the communication channel sensor settings for Crossbeam-based software sensors. Doing so may break communications between hosts on the local network. including your management network. 3Dx800 sensors. You must use native applications. see the Intrusion Agent Configuration Guide. For more information on configuring settings for Crossbeam-based software sensor.

5. enter the IP address range that you want to use.0/24 to indicate that the Management Virtual Network is disabled on a Master Defense Center. The new values are saved. Click Remote Management.9.1 Sourcefire 3D System Administrator Guide 385 . The Remote Management page appears. WARNING! Changing the management port on the Defense Center requires that you also manually change the management port on every managed sensor. In the Management Port field. The Information page appears. You can not edit the Management Virtual Network field of a Master Defense Center.0. The field is filled with 0. this function is used only under the direction of Sourcefire Support. In the Management Virtual Network field. 4. a feature that is especially useful after network reconfigurations or appliance updates. 3. The current Version 4. Select Operations > System Settings. Master Defense Centers do not currently use a Management Virtual Network. it should not be edited. Typically. Past versions of Sourcefire 3D Systems used a default /24 (twenty-four bit) CIDR address space. Click Save to save your changes for both the IP address range and the port number. You can also regenerate the Virtual IP address. WARNING! If the Management Virtual Network is functioning properly. TIP! The subnet mask is fixed at /16 (sixteen bits). 2.0. enter the port number that you want to use. Editing the Management Virtual Network Requires: DC + 3D Sensor You can change the host IP or host name of the connected appliance. which provided enough addresses for 127 appliances.Configuring System Settings Configuring the Communication Channel Chapter 10 To configure the communications channel: Access: Admin 1.

Select Operations > System Settings. See Working in NAT Environments on page 112 for more information. 3. Configuring Remote Access to the Defense Center Requires: DC + 3D Sensor You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor. Click Remote Management.the hostname of IP address. Optionally. 2. click Regenerate VIP to regenerate the IP address used by the virtual network. Version 4. 6. which provides for a much greater number of appliances. To edit the remote management virtual network: Access: Admin 1. After appropriate management virtual network edits are made. Registration Key . 4. TIP! The regenerate VIP option is useful after you reconfigure your network or change the Sourcefire 3D System to take advantage of a larger address space.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 version uses a default /16 (sixteen bit) CIDR address space. 5.a unique alphanumeric ID for use when registering sensors in NAT environments. Click Edit next to the host whose Management Virtual Network you want to change.9.1 Sourcefire 3D System Administrator Guide 386 . Three fields are provided for setting up communications between appliances: • • • Management Host . The Remote Management page appears. Edit the name or host ID in the Name or Host fields as required. click Save. The Information page appears.registration key Unique NAT ID . The Edit Remote Management page appears.

To set up sensor management from the sensor: Access: Admin 1. see Setting Up the Management Virtual Network on page 384. Registration Key. Click Add Manager. and Unique NAT ID used on the Defense Center. 2. 4. If you must change the Management Port. WARNING! Leave the Management Port field at the top of the Remote Management page in the default setting in nearly all cases. The Management Host or Host field (hostname or IP address) must be used on at least one of the appliances. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center. type the IP address or the hostname of the Defense Center that you want to use to manage the sensor.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 Valid combinations include: • • • Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. 3. Management Host. select Operations > System Settings. Sourcefire strongly recommends that you read Using the Defense Center on page 99 before you add sensors to the Defense Center. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. Registration Key. Click Remote Management. the Remote Management page displays the Unique NAT ID in the Host field. Version 4. In the Management Host field. The Remote Management page appears. On the sensor’s web interface. but without a hostname or IP address.1 Sourcefire 3D System Administrator Guide 387 . TIP! If you register a sensor to a Defense Center using a Registration Key and Unique NAT ID.9. The Add Remote Management page appears. The Information page appears.

in the Unique NAT ID field. In the Registration Key field. Click Save. type the same one-time use registration key that you used in step 5. 7. In that case. 10. 6. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 5. 11. If you used a unique ID in step 6. 12.1 Sourcefire 3D System Administrator Guide 388 . Click New Sensor. use both the Registration Key and the Unique NAT ID fields. In the Registration Key field. Version 4. type the one-time use registration key that you want to use to set up a communications channel between the sensor and the Defense Center. Access the Defense Center web interface and select Operations > Sensors.9. type a unique alphanumeric NAT ID that you want to use to identify the sensor. type the same value in the Unique NAT ID field. The Add New Sensor page appears. the Pending Registration status appears. 8. After the sensor confirms communication with the Defense Center.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 Note that you can leave the Management Host field empty if the management host does not have a routable address. The Sensors page appears. Optionally. 9. Type the IP address or the hostname of the sensor you want to add in the Host field.

14. 15. select the group from the Add to Group list.Configuring System Settings Setting the Time Manually Chapter 10 13. IMPORTANT! If you elect to prohibit sending packets and you do not store events on the 3D Sensor. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. You can store IPS data on both the Defense Center and the sensor by clearing the Store Events and Packets Only on the Defense Center check box. then you can manually set the time for the appliance using the Time page in the system settings. you may need to use the Add Manager feature to add the secondary Defense Center. By default. For more information about groups. You must store events on the Defense Center. The sensor is added to the Defense Center. Setting the Time Manually Requires: Any If the Time Synchronization setting in the currently applied system policy is set to Manual. IMPORTANT! 3Dx800 sensors and Crossbeam-based software sensors cannot store IPS data locally. You can prevent packet data from leaving a sensor by checking the Prohibit Packet Transfer to the Defense Center check box. To add the sensor to a group. see Managing Sensor Groups on page 131.9. Click Add. IMPORTANT! In some high availability deployments where network address translation is used.1 Sourcefire 3D System Administrator Guide 389 . Contact Sourcefire Support for more information. Note that RNA data is never stored on the sensor. Version 4. packet data is not retained. Packet data is often important for forensic analysis. IPS data is stored only on the Defense Center and not on the sensor. 16.

The following states may appear: • Being Used indicates that the appliance is synchronized with the NTP server. Instead. The Information page appears. To manually configure the time: Access: Admin 1. • Unknown indicates that the status of the NTP server is unknown. its value should change to Being Used. or Not Available.9. if you see larger update times such as 300 seconds. The NTP daemon automatically adjusts the synchronization times based on a number of conditions. • Not Available indicates that the NTP server is in your configuration but the NTP daemon is unable to use it. and positive values indicate that it is ahead. • Available indicates that the NTP server is available for use but time is not yet synchronized. The status of the NTP server time synchronization. time manually. that indicates that the time is relatively stable and the NTP daemon has determined that it does not need to use a lower update increment. The number of seconds that have elapsed since the time was last synchronized with the NTP server. Available. Offset The number of milliseconds of difference between the time on the appliance and the configured NTP server. Last Update See Synchronizing Time on page 354 for more information about the time settings in the system policy. Over time. • Pending indicates that the NTP server is new or the NTP daemon was recently restarted. Negative values indicate that the appliance is behind the NTP server. For example.1 Sourcefire 3D System Administrator Guide 390 . Version 4. the NTP Status section on the Time page provides the following information: NTP Status Column NTP Server Status Description The IP address and name of the configured NTP server.Configuring System Settings Setting the Time Manually Chapter 10 If the appliance is synchronizing its time based on NTP you cannot change the . Select Operations > System Settings.

You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. For more information about using the time zone page. If you need to disable the results of a group of appliances’ health monitoring. select the following: • • • • • year month day hour minute 4. see Setting Your Default Time Zone on page 34. 5. after the time zone setting is saved. the appliances report a disabled status in the Health Monitor Summary. Click Apply.1 Sourcefire 3D System Administrator Guide 391 . you can blacklist the policy.Configuring System Settings Blacklisting Health Modules Chapter 10 2. The time is updated. you can blacklist the group of appliances. The Time page appears. A pop-up window appears. if an appliance is temporarily disconnected from the management network. 6. From list boxes that appear. Once the blacklist settings take effect. Click Time. Blacklisting Health Modules Requires: DC/MDC If you want to disable health events for all appliances with a particular health policy. For information on blacklisting individual or groups of appliances see Blacklisting Health Policies or Appliances on page 535. you can blacklist the Appliance Heartbeat module during that maintenance window. click Close to close the pop-up window. 3. If you want to change the time zone. click the time zone link located next to the date and time. For information on blacklisting an individual policy modules. see Blacklisting a Health Policy Module on page 537 Version 4. Select your time zone and click Save and.9. You can also blacklist individual health policy modules on appliances. For example.

Keep in mind that if you remove a NetFlow-enabled device from the system policy. 2. Select Operations > System Settings. Click Add Device to add a NetFlow-enabled device. 3. You must configure these NetFlow-enabled devices to export NetFlow version 5 data. you should also remove it from your RNA detection policy.9. The Information page appears. 4. TIP! To remove a NetFlow-enabled device. 6. Click NetFlow Devices. One of the prerequisites for using NetFlow data is to use the system settings to specify the NetFlow-enabled devices you are going to use to collect the data. The NetFlow Devices page appears.1 Sourcefire 3D System Administrator Guide 392 . see Introduction to NetFlow in the Analyst Guide. For more information on using NetFlow data with the Sourcefire 3D System. For more information. In the IP Address field. Click Save. The list of NetFlow-enabled devices is saved. you can use the flow data that these devices collect to supplement the flow data collected by 3D Sensors with RNA by specifying the devices and the networks they monitor in your RNA detection policy. enter the IP address of the NetFlow-enabled device you want to use to collect flow data. 5. including information on additional prerequisites. Version 4. To add NetFlow-enabled devices for flow data collection: Access: Admin 1. To add additional NetFlow-enabled devices.Configuring System Settings Specifying NetFlow-Enabled Devices Chapter 10 Specifying NetFlow-Enabled Devices Requires: DC + RNA If you have enabled the NetFlow feature on your NetFlow-enabled devices). see Editing an RNA Detection Policy in the Analyst Guide. repeat steps 3 and 4. click Delete next to the device you want to remove.

but you can choose to send either to a remote system and store the other on the local Defense Center. You cannot send backups to one remote system and reports to a another.9. you can switch back to local storage only if you have not increased the RNA flow database limit. see Using NFS for Remote Storage on page 394. see Using SSH for Remote Storage on page 395. For information on backup and restore. see Using SMB for Remote Storage on page 396. see Using Local Storage on page 393. To use SSH for backup and report storage. To use SMB for backup and report storage. see Using Backup and Restore on page 413. or Intrusion Agents.1 Sourcefire 3D System Administrator Guide 393 . 3Dx800 sensors. or Server Message Block (SMB)/Common Internet File System (CIFS) for backup and report remote storage. IMPORTANT! You cannot use remote backup and restore to manage data on Crossbeam-based software sensors. Keep in mind that only Series 2 Defense Centers and not Master Defense Centers provide backup and report remote storage. You can use Network File System (NFS). To store backups and reports locally: Access: Admin 1.Configuring System Settings Managing Remote Storage Chapter 10 Managing Remote Storage Requires: Series 2 DC On Series 2 Defense Centers you can use local or remote storage for backups and reports. Select one of the backup and report storage options: • • • • To disable external remote storage and use the local Defense Center for backup and report storage. Version 4. Secure Shell (SSH). You must ensure that your external remote storage system is functional and accessible from the Defense Center. Using Local Storage Requires: Series 2 DC You can store backups and reports on the local Defense Center. Select Operations > System Settings. TIP! After configuring and selecting remote storage. The Information page appears. To use NFS for backup and report storage. RNA Software for Red Hat Linux.

TIP! You do not use the Test button with local storage. The Remote Storage Device page appears. The page refreshes to display the NFS storage configuration options.1 Sourcefire 3D System Administrator Guide 394 . Add the connection information: • • Enter the IP or hostname of the storage system in the Host field. Select Operations > System Settings. 3.Configuring System Settings Managing Remote Storage Chapter 10 2. 3. select NFS. At Storage Type. At Storage Type. Click Remote Storage Device. The Information page appears. Using NFS for Remote Storage Requires: Series 2 DC You can select Network File System (NFS) protocol to store your reports and backups. Version 4. Your storage location choice is saved. Enter the path to your storage area in the Directory field. Click Remote Storage Device. Click Save. To store backups and reports using NFS: Access: Admin 1. 2. select Local (No Remote Storage).9. 4. The Remote Storage Device page appears. 4.

Your remote storage configuration is saved. Select Operations > System Settings. The page refreshes to display the SSH storage configuration options. Optionally. Select Enable Remote Storage for Reports to store reports on the designated host. The Information page appears. select Use Advanced Options. At Storage Type. select SSH. Click Remote Storage Device. To store backups and reports using SSH: Access: Admin 1. select either or both of the following: • • 7. click Test. 2. Under System Usage.1 Sourcefire 3D System Administrator Guide 395 . 3. 6.9. 8.Configuring System Settings Managing Remote Storage Chapter 10 5. The test ensures that the Defense Center can access the designated host and directory. Version 4. Select Enable Remote Storage for Backups to store backups on the designated host. Click Save. The Remote Storage Device page appears. Using SSH for Remote Storage Requires: Series 2 DC You can select Secure Shell (SSH) protocol to store your reports and backups. If there are any required command line options. A Command Line Options field appears where you can enter the commands.

select either or both of the following: • • 7. Add the connection information: • • • • Enter the IP or hostname of the storage system in the Host field. 2. Click Save. Enter the storage system’s user name in the Username field and the password for that user in the Password field. Select Enable Remote Storage for Reports to store reports on the designated host.9.Configuring System Settings Managing Remote Storage Chapter 10 4. Optionally. Version 4. The test ensures that the Defense Center can access the designated host and directory.1 Sourcefire 3D System Administrator Guide 396 . Enter the path to your storage area in the Directory field. The Remote Storage Device page appears. If there are any required command line options. 8. Under System Usage. A Command Line Options field appears where you can enter the commands. Select Operations > System Settings. To use SSH keys. To store backups and reports using SMB: Access: Admin 1. 5. The Information page appears. copy the content of the SSH Public Key field and place it in your authorized_keys file. Select Enable Remote Storage for Backups to store backups on the designated host. 6. click Test. Click Remote Storage Device. select Use Advanced Options. Your remote storage configuration is saved. Using SMB for Remote Storage Requires: Series 2 DC You can select Server Message Block (SMB) protocol to store your reports and backups.

Select Enable Remote Storage for Backups to store backups on the designated host.1 Sourcefire 3D System Administrator Guide 397 . Click Save. 5. A Command Line Options field appears where you can enter the commands. If there are any required command line options. At Storage Type. select either or both of the following: • • 7. 6. 8. Optionally. Your remote storage configuration is saved. enter the domain name for the remote storage system in the Domain field. click Test. Select Enable Remote Storage for Reports to store reports on the designated host. select SMB. Under System Usage. The page refreshes to display the SMB storage configuration options.9. Version 4. Enter the share of your storage area in the Share field. Enter the user name for the storage system in the Username field and the password for that user in the Password field.Configuring System Settings Managing Remote Storage Chapter 10 3. 4. The test ensures that the Defense Center can access the designated host and directory. Optionally. Add the connection information: • • • • Enter the IP or hostname of the storage system in the Host field. select Use Advanced Options.

1).9.Updating System Software Chapter 11 Administrator Guide Use the Update feature to update the Sourcefire 3D System. for example.1 Sourcefire 3D System Administrator Guide 398 . for example. see the Intrusion Agent Configuration Guide. Feature updates are more comprehensive than patches and generally include new features (and usually change the third digit in the version number. 4. Vulnerability database (VDB) updates affect the vulnerabilities reported by RNA as well as the operating systems. for example.0. For information on Intrusion Agents.9.9. Sourcefire electronically distributes several different types of updates: • • Patches include a limited range of fixes (and usually change the fourth digit in the version number. Version 4. client applications. Major and minor version releases include new features and functionality and may entail large-scale changes to the product (and usually change the first or second digit in version number. • • IMPORTANT! You cannot use the Update feature to update the SEU or Intrusion Agents. and services that RNA detects. 4. see Importing SEUs and Rule Files in the Analyst Guide. 4.0). For information on updating your SEU.9 or 5.1).

The following graphic shows the Defense Center version of the page. See the following sections for more information: • • • Installing Software Updates on page 400 Uninstalling Software Updates on page 409 Updating the Vulnerability Database on page 410 Version 4. which are created when you install a patch to a Sourcefire appliance. nor is it supported for appliances that do not have local web interfaces. including software sensors. Uploaded VDB updates also appear on the page. you may need to uninstall the previous version and install the new version. new features and functionality. warnings. as do uninstaller updates.Updating System Software Chapter 11 You can obtain updates from the Sourcefire Support and then manually install them using the Patch Update Management page. for major updates to software sensors. Before you update Sourcefire software. The release notes describe supported platforms. They also contain information on any prerequisites. The list of updates shows the type of each update. you can take advantage of the automated update feature. you must read the release notes that accompany the update. TIP! For patches. known and resolved issues. However. and VDB updates. Uninstalling from the web interface is not supported for major version upgrades. and the date and time it was generated.9. and specific installation and uninstallation instructions. feature updates. You can uninstall patches to the Sourcefire software using an appliance’s local web interface. they appear on the page. WARNING! This chapter contains general information on updating the Sourcefire 3D System. see Scheduling Tasks on page 425. and product compatibility. the version number.1 Sourcefire 3D System Administrator Guide 399 . When you upload updates to your appliance. If your deployment includes a Defense Center. you can use it to install updates on its managed 3D Sensors. It also indicates whether a reboot is required as part of the update.

see Automating Software Updates on page 430.Updating System Software Installing Software Updates Chapter 11 Installing Software Updates Requires: Any Sourcefire periodically issues updates to the Sourcefire 3D System software. see the release notes for more information. 2. you may need to uninstall the previous version and install the new version. Make sure your appliances (including software sensors) are running the correct version of the Sourcefire 3D System. Install the latest SEU on your appliances.9. Make sure the computers or appliances where you installed software sensors are running the correct versions of their operating systems. You can obtain the SEU from the Sourcefire Support Site. You must install the latest SEU (see Importing SEUs and Rule Files in the Analyst Guide) on your appliances before you begin the update. 4. you can obtain updates from the Sourcefire Support Site. Available on the Sourcefire Support Site. 3. you can take advantage of the automated update feature. The release notes for the update indicate the required version. the policies and network settings on the appliance remain intact. Make sure that any Crossbeam Systems or Red Hat Linux platforms you are using to host Sourcefire software sensors are running the correct version of the operating system. and product compatibility. Note that for major updates to software sensors (Crossbeam-based software sensors and RNA for Red Hat Linux). Updating an appliance does not modify its configuration. the release notes describe supported platforms. Read the release notes for the update. To update your Sourcefire 3D System appliances: Access: Admin 1. new features and functionality. warnings. For patches and feature updates.1 Sourcefire 3D System Administrator Guide 400 . and specific installation and uninstallation instructions. as described in the release notes. they also contain information on any prerequisites. Version 4. TIP! This section explains how to plan for and perform manual software updates on your Sourcefire appliances. If you are running an earlier version. known and resolved issues.

7. paired Defense Centers do not receive software updates as part of the regular synchronization process. After you update any Master Defense Centers in your deployment. Note that when you begin to update one Defense Center in a high availability pair. see Updating a Defense Center or Master Defense Center on page 402. Note that you must use the Defense Center to update sensors that do not have a web interface. the paired Defense Centers stop sharing configuration information.1 Sourcefire 3D System Administrator Guide 401 . Make sure you have enough free disk space and allow enough time for the update. 6. see Using Backup and Restore on page 413. you can update the Defense Centers they manage. then back up current event and configuration data to an external location.Updating System Software Installing Software Updates Chapter 11 5. See Updating Unmanaged 3D Sensors on page 406. see Updating Managed Sensors on page 404. In addition. 9. if it is not already. 8. then update the second Defense Center. The release notes for the update indicate space and time requirements. When you update a managed sensor. the update requires additional disk space on the Defense Center. Sourcefire strongly recommends that you delete or move any backup files that reside on your appliance. Update your Master Defense Centers. 10. do not update paired Defense Center at the same time. see the release notes for more information. Delete any backups that reside on the appliance. After you update the Master Defense Centers and Defense Centers in your deployment. Always update Master Defense Centers first. Event data is not backed up as part of the update process. including the types of backups that are supported for your appliance. Update your managed 3D Sensors. then back up current event and configuration data to an external location. To ensure continuity of operations. However. and 3Dx800 sensors. you can update your managed sensors (including software sensors). Update your Defense Centers. the other Defense Center in the pair becomes the primary.9. Version 4. for major updates to software sensors. First. RNA for Red Hat Linux. For more information on the backup and restore feature. complete the update procedure for one of the Defense Centers. see Updating a Defense Center or Master Defense Center on page 402. Update your unmanaged 3D Sensors. Sourcefire strongly recommends that you use your Defense Centers to update the sensors they manage. you may need to uninstall the previous version and install the new version. including Crossbeam-based software sensors.

To ensure continuity of operations.1 Sourcefire 3D System Administrator Guide 402 . complete the update procedure for one of the Defense Centers. from the appliance. the paired Defense Centers stop sharing configuration information. In addition.Updating System Software Installing Software Updates Chapter 11 Updating a Defense Center or Master Defense Center Requires: DC/MDC Use the procedure in this section to update your Defense Centers and Master Defense Centers. First. Pre-update tasks can include making sure that the Defense Center is running the correct version of the Sourcefire software. Version 4. making sure you have set aside adequate time to perform the update. and so on. If your deployment includes Master Defense Centers. paired Defense Centers do not receive software updates as part of the regular synchronization process.9. if it is not already. then update the second Defense Center. Choose this option if your Defense Center has access to the internet and you are not performing a major update. IMPORTANT! For major updates. updating the Defense Center removes any existing updates and patches. as well as their uninstall scripts. To update the Defense Center or Master Defense Center: Access: Admin 1. Choose this option if your Defense Center does not have access to the internet or if you are performing a major update. You can manually download the update from the Sourcefire Support Site and then upload it to the Defense Center. Read the release notes for the update and complete any required pre-update tasks. This option is not supported for major updates. • Note that when you begin to update one Defense Center in a high availability pair. backing up event and configuration data. You update the Defense Center in one of two ways. making sure you have enough free disk space to perform the update. you must update them before you update the Defense Centers that they manage. do not update paired Defense Center at the same time. the other Defense Center in the pair becomes the primary. depending on the type of update and whether your Defense Center has access to the internet: • You can use the Defense Center to obtain the update directly from the Support Site.

it may become corrupted. 6. Select Operations > Update to display the Patch Update Management page. and the date and time it was generated. You must wait until any long-running tasks are complete before you begin the update. The Patch Update Management page appears. select Operations > Update to display the Patch Update Management page. you must manually delete them from the task queue after the update completes. and if your Defense Center has access to the Internet. For major releases. Click Install next to the update you uploaded. either manually or by clicking Update on the Patch Update Management page. The task queue automatically refreshes every 10 seconds. Version 4. The page also indicates whether a reboot is required as part of the update. Tasks that are running when the update begins are stopped and cannot be resumed. then click Upload Update. The Install Update page appears. • For all except major releases. The Patch Update Management page shows the type of update you just uploaded. Select Operations > Monitoring > Task Status to view the task queue and make sure that there are no jobs in process. Make sure that the appliances in your deployment are successfully communicating and that there are no issues being reported by the health monitor. If you transfer an update file by email.1 Sourcefire 3D System Administrator Guide 403 .9. The update is uploaded to the Defense Center. Browse to the update and click Upload. 3. 4. depending on the type of update and whether your Defense Center has access to the internet. You have two options. 5. Upload the update to the Defense Center. • IMPORTANT! Download the update directly from the Support Site. or if your Defense Center does not have access to the Internet. then click Download Updates to check for the latest updates on the Support Site. first manually download the update from the Sourcefire Support Site.Updating System Software Installing Software Updates Chapter 11 2. its version number. Select Operations > Update.

Updating Managed Sensors Requires: DC + 3D Sensor After you update your Defense Centers. the web interface may become unavailable. may cause a few packets to pass through the sensor uninspected. for most detection engines with inline interface sets. Update the VDB on your Defense Centers and the 3D Sensors with RNA that they manage. If you encounter issues with the update (for example. 10. If this occurs. Otherwise. First. 12. 14. This can cause a short pause in processing and. Finally. If prompted. confirm that you want to install the update and reboot the Defense Center. see Updating the Vulnerability Database on page 410. Note that you can update Version 4. to update the Sourcefire software on the sensors that the Defense Center manages. After the update finishes. Sourcefire strongly recommends that you use them to update the sensors they manage. install the software. 11. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). Re-apply intrusion policies to the IPS detection engines on your managed 3D Sensors.Updating System Software Installing Software Updates Chapter 11 7. if necessary. the user interface may exhibit unexpected behavior. 9. continue to refrain from using the web interface until the update has completed. download the update from the Support Site and upload it to the managing Defense Center. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). Continue with the next section. Updating Managed Sensors. do not restart the update. log in again to view the task queue. Under Selected Update. Updating managed sensors is a multi-step process. Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. Next. If the update is still running. Select Operations > Help > About and confirm that the software version is listed correctly. 13. contact Support. applying an intrusion policy causes IPS detection engines to restart. Instead. Clear your browser cache and force a reload of the browser. select the Defense Center and click Install. WARNING! Do not use the web interface to perform any other tasks until the update has completed and (if necessary) the Defense Center reboots. The update process begins.1 Sourcefire 3D System Administrator Guide 404 . or the Defense Center may log you out. push the update to the sensors from the Defense Center. see Creating a Detection Engine on page 193). log into the Defense Center. Verify that all managed sensors are successfully communicating with the Defense Center. Before the update completes.9. 8. This is expected behavior.

Click Upload Update to browse to the update you downloaded. 6. and date and time it was generated. for major updates to software sensors. On the managing Defense Center. including Crossbeam-based software sensors. it may become corrupted. The Patch Update Management page appears. Read the release notes for the update and complete any required pre-update tasks.Updating System Software Installing Software Updates Chapter 11 multiple 3D Sensors at once. To update managed 3D Sensors: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 405 . then click Upload. and so on. The update is uploaded to the Defense Center. For information on the updates you can download. RNA for Red Hat Linux. making sure you have enough free disk space to perform the update. see the release notes. and 3Dx800 sensors. Update the Sourcefire software on the sensors’ managing Defense Center. making sure that the 3D Sensors are running the correct version of the Sourcefire software. making sure software sensors are running the correct version of their operating systems. IMPORTANT! You must use the Defense Center to update sensors that do not have a web interface. you have set aside adequate time to perform the update. Version 4. For information on updating the 3D Sensors in your deployment. 4.9. However. backing up event and configuration data. 5. Click Push next to the update. select Operations > Update. If you transfer an update file by email. The Patch Update Management page shows the type of update you just uploaded. 3. but only if they use the same update. IMPORTANT! Download the update directly from the Support Site. see Updating a Defense Center or Master Defense Center on page 402. 7. Pre-update tasks can include updating your managing Defense Center. see the release notes for more information. 2. you may need to uninstall the previous version and install the new version. The Push Update page appears. Download the update from the Sourcefire Support Site. see the release notes. Make sure that the appliances in your deployment are successfully communicating and that there are no issues being reported by the health monitor. its version number. Different 3D Sensor models use different updates. The page also indicates whether a reboot is required as part of the update.

10. confirm that you want to install the update and reboot the 3D Sensors. Re-apply intrusion policies to the IPS detection engines on your managed 3D Sensors. it may take some time to push the update to all sensors. traffic is interrupted while the sensors reboot. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). Updating Unmanaged 3D Sensors Requires: 3D Sensor Use the procedure in this section to update unmanaged 3D Sensors only. applying an intrusion policy causes IPS detection engines to restart. For more information. Version 4. The Install Update page appears.1 Sourcefire 3D System Administrator Guide 406 . select the sensors you want to update. Click Install next to the update you are installing. Verify that the sensors you updated are successfully communicating with the Defense Center. may cause a few packets to pass through the sensor uninspected. 9. your 3D Sensors use IPS detection engines with inline interface sets. Depending on the size of the file. This can cause a short pause in processing and. see Creating a Detection Engine on page 193). see Updating Managed Sensors on page 404. If the update requires a reboot. WARNING! If you encounter issues with the update (for example. The update process begins. for most detection engines with inline interface sets. 13. then click Push. Instead. Select Operations > Sensors and confirm that the sensors you updated have the correct version listed. You can monitor the update's progress in the Defense Center’s task queue (Operations > Monitoring > Task Status). Sourcefire strongly recommends that you update managed 3D Sensors using their managing Defense Centers. You can monitor the progress of the push in the task queue (Operations > Monitoring > Task Status). Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. 12.Updating System Software Installing Software Updates Chapter 11 8. Select the sensors where you pushed the update and click Install. If prompted. When the push is complete. If your sensors have fail-open network cards. contact Support. 11. continue with the next step. Under Selected Update. do not restart the update. some traffic may pass through the sensors uninspected while they reboot.9. and the sensors do not have fail-open network cards.

Version 4.Updating System Software Installing Software Updates Chapter 11 You update the 3D Sensor in one of two ways. updating the 3D Sensor removes any existing updates and patches. it may become corrupted. • IMPORTANT! Download the update directly from the Support Site. Read the release notes for the update and complete any required pre-update tasks. and if your 3D Sensor has access to the Internet. either manually or by clicking Update on the Patch Update Management page. first manually download the update from the Sourcefire Support Site. backing up event and configuration data. 2. • For all except major releases. • IMPORTANT! For major updates. The Patch Update Management page shows the type of update you just uploaded. The update is uploaded to the 3D Sensor. from the sensor. The page also indicates whether a reboot is required as part of the update. then click Download Updates to check for the latest updates on the Support Site. Choose this option if your 3D Sensor does not have access to the internet or if you are performing a major update. making sure you have set aside adequate time to perform the update. select Operations > Update to display the Patch Update Management page. You have two options. making sure you have enough free disk space to perform the update. as well as their uninstall scripts. Select Operations > Update to display the Patch Update Management page. Choose this option if your 3D Sensor has access to the internet and you are not performing a major update. Pre-update tasks can include making sure that the 3D Sensor is running the correct version of the Sourcefire software. or if your 3D Sensor does not have access to the Internet. and the date and time it was generated.1 Sourcefire 3D System Administrator Guide 407 . its version number. This option is not supported for major updates. depending on the type of update and whether your 3D Sensor has access to the internet: • You can use the 3D Sensor to obtain the update directly from the Support Site. Upload the update to the 3D Sensor. Browse to the update and click Upload. and so on. If you transfer an update file by email. You can manually download the update from the Sourcefire Support Site and then upload it to the 3D Sensor. To update an unmanaged 3D Sensor: Access: Admin 1.9. depending on the type of update and whether your 3D Sensor has access to the internet. then click Upload Update. For major releases.

some traffic may pass through the sensor uninspected while it reboots. Otherwise. The Patch Update Management page appears. applying an intrusion policy causes IPS detection engines to restart. Version 4. The task queue automatically refreshes every 10 seconds. 6. 9. you must manually delete them from the task queue after the update completes.1 Sourcefire 3D System Administrator Guide 408 . 8. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). If the update is still running. If prompted. Before the update completes. 5. continue to refrain from using the web interface until the update has completed. see Creating a Detection Engine on page 193). Re-apply intrusion policies to your IPS detection engines. Unless you enabled the Inspect Traffic During Policy Apply option when you created your IPS detection engines (this option is supported on many sensor models. You must wait until any long-running tasks are complete before you begin the update. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress). the user interface may exhibit unexpected behavior. Instead. This can cause a short pause in processing and. your 3D Sensor uses IPS detection engines with inline interface sets. If you encounter issues with the update (for example. contact Support. If the update requires a reboot. Clear your browser cache and force a reload of the browser. the web interface may become unavailable. log in again to view the task queue. for most detection engines with inline interface sets. may cause a few packets to pass through the sensor uninspected. 7. Select Operations > Monitoring > Task Status to view the task queue and make sure that there are no jobs in process. Tasks that are running when the update begins are stopped and cannot be resumed. Select Operations > Help > About and confirm that the software version is listed correctly. do not restart the update. log into the 3D Sensor. After the update finishes. if necessary. or the 3D Sensor may log you out. and the sensor does not have a fail-open network card. Select Operations > Update. traffic is interrupted while the sensor reboots.9. If the sensor has a fail-open network card. If this occurs. WARNING! Do not use the web interface to perform any other tasks until the update has completed and (if necessary) the 3D Sensor reboots.Updating System Software Installing Software Updates Chapter 11 3. The update process begins. 4. This is expected behavior. confirm that you want to install the update and reboot the 3D Sensor. Click Install next to the update you just uploaded.

0.2 patch might result in an appliance running Version 4. For information on the resulting Sourcefire software version when you uninstall an update.9.9.0. as described by the procedure in this section. Select Operations > Update.Updating System Software Uninstalling Software Updates Chapter 11 Uninstalling Software Updates Requires: Any When you install a patch to a Sourcefire appliance.1. For information on uninstalling patches from appliances that do not have local web interfaces (Crossbeam-based software sensors. even though you never installed the Version 4. you must uninstall a patch from the appliances in your deployment in the reverse order of how you installed it. The Patch Update Management page appears. That is.2. RNA for Red Hat Linux. first uninstall the patch from your managed 3D Sensors. see the release notes. contact Support.9. To uninstall a patch using the local web interface: Access: Admin 1. and finally your Master Defense Centers.9. then your Defense Centers. see the release notes. For example. the update process creates an uninstaller update that allows you to uninstall the patch from that appliances’s web interface. and 3Dx800 sensors). you cannot use the Defense Center to uninstall patches from managed sensors.1 Sourcefire 3D System Administrator Guide 409 . When you uninstall a patch.9. the resulting Sourcefire software version depends on the update path for your appliance.1 update. If you upgraded to a new version of the appliance and need to revert to an older version. IMPORTANT! Uninstalling from the web interface is not supported for major version upgrades.0. consider a scenario where you updated an appliance directly from Version 4.0 to Version 4. You must use the local web interface to uninstall patches. Uninstalling the Version 4.0. In addition.9. Version 4.

do not restart the uninstall. log in again and view the task queue.9. Updating the Vulnerability Database Requires: DC + RNA The Sourcefire Vulnerability Database (VDB) is a database of known vulnerabilities to which hosts may be susceptible. 5. for example.1 Sourcefire 3D System Administrator Guide 410 . some traffic may pass through the sensor uninspected while it reboots. 3. If you encounter issues with the uninstall. If the uninstall is still running. Instead. the Install Update page appears. If this occurs. • • On the Defense Center. If the uninstall for a 3D Sensor requires a reboot. the sensor uses IPS detection engines with inline interface sets. confirm that you want to uninstall the update and reboot the appliance. You can monitor its progress in the task queue (Operations > Monitoring > Task Status). client applications. Select Operations > Help > About and confirm that the software version is listed correctly. as well as fingerprints for RNA-detection operating systems. if necessary. if the task queue indicates that the uninstall has failed or if a manual refresh of the task queue shows no progress. On the 3D Sensor. If the sensor has a fail-open network card. select the Defense Center and click Install. WARNING! Do not use the web interface to perform any other tasks until the uninstall has completed and (if necessary) the appliance reboots. The uninstall process begins. Click Install next to the uninstaller for the update you want to remove. Under Selected Update. 4. Before the uninstall completes. After the uninstall finishes. 6. Verify that the appliance where you uninstalled the patch is successfully communicating with its managed sensors (for the Defense Center) or its managing Defense Center (for 3D Sensors). continue to refrain from using the web interface until the uninstall has completed. if prompted. In either case. RNA correlates the operating system and services detected on each host with the vulnerability database to help you determine whether a particular host increases your risk of network compromise. and services. or the appliance may log you out. traffic is interrupted while the sensor reboots. This is expected behavior. Otherwise. Version 4. contact Support. there is no intervening page. Clear your browser cache and force a reload of the browser. and the sensor does not have a fail-open network card. log into the appliance. The Sourcefire Vulnerability Research Team (VRT) issues periodic updates to the VDB. the web interface may become unavailable.Updating System Software Updating the Vulnerability Database Chapter 11 2. the user interface may exhibit unexpected behavior.

The time it takes to update vulnerability mappings depends on the number of hosts in your network map. including software sensors.9. 3. If you transfer an update file by email. Version 4. The VDB update is saved on the Defense Center and appears in the Updates section. you do not need to update the VDB on these appliances. You may want to schedule the update during low system usage times to minimize the impact of any system downtime. Upload the update to the Defense Center. divide the number of hosts on your network by 1000 to determine the approximate number of minutes to perform the update. IMPORTANT! Download the update directly from the Support Site. 2. If your Defense Center does not have access to the Internet. The Patch Update Management page appears. As a rule of thumb. Browse to the update and click Upload. The VDB Update Advisory Text includes information about the changes to the VDB made in the update. it may become corrupted. 4. TIP! This section explains how to plan for and perform manual VDB updates on your Sourcefire 3D System appliances. To update the vulnerability database: Access: Admin 1. then click Upload Update. as well as product compatibility information. You can take advantage of the automated update feature to schedule VDB updates.Updating System Software Updating the Vulnerability Database Chapter 11 You should install the same version of the VDB on all the appliances in your deployment. To ensure you install the same VDB version. click Download Updates to check for the latest updates on the Support site. either manually or by clicking Update. • • If your Defense Center has access to the Internet. Click Push next to the VDB update. The Push Update page appears. see Automating Vulnerability Database Updates on page 437. Select Operations > Update.1 Sourcefire 3D System Administrator Guide 411 . use your Defense Centers to push and install the VDB on all managed 3D Sensors with RNA. manually download the update from the Sourcefire Support Site. Read the VDB Update Advisory Text for the update. Because you cannot view RNA data on Master Defense Centers or on unmanaged 3D Sensors.

Click Install next to the VDB update. do not restart the update. Depending on the size of the file.9. contact Support. 7. 8. Instead. Under Selected Update. it may take some time to push the VDB update to all sensors. for example. select the managed 3D Sensors you want to update. select Operations > Help > About. The Install Update page appears. • • To check the VDB build number on the Defense Center. If you encounter issues with the update. WARNING! Do not use the web interface to perform tasks related to mapped vulnerabilities until the update has completed. the update may take some time. To check the VDB build number on your managed sensors. Depending on the number of hosts in your network map. continue with the next step. select Operations > Sensors on the Defense Center. if the task queue indicates that the update has failed or if a manual refresh of the task queue shows no progress. Select the Defense Center. You can monitor the update's progress in the task queue (Operations > Monitoring > Task Status). 6. After the update finishes. then click Push. Version 4.1 Sourcefire 3D System Administrator Guide 412 . confirm that the VDB build number matches the update you installed. The update process begins. then click Install. You can monitor the progress of the push in the Defense Center’s task queue (Operations > Monitoring > Task Status). then click Edit next to each sensor you updated.Updating System Software Updating the Vulnerability Database Chapter 11 5. When the push is complete. as well as the sensors where you pushed the VDB update.

By default. system configuration files are saved in the backup file. those updates are not backed up. While each organization’s backup plan is highly individualized. WARNING! Do not use the backup and restore process to copy the configuration files between sensors.Using Backup and Restore Chapter 12 Administrator Guide Backup and restoration is an essential part of any system maintenance plan. if applicable for the range of appliances in your deployment: • • • the entire intrusion event database the entire RNA event database additional files that reside on the appliance WARNING! If you applied any SEU updates.9. Version 4. You can restore a backup onto a replacement appliance if the two appliances are the same model and are running the same version of the Sourcefire 3D System software. Sourcefire 3D System provides a mechanism for archiving data so that the Defense Center or 3D Sensor can be restored in case of disaster. You can also choose to back up the following. You need to apply the latest SEU update after you restore.1 Sourcefire 3D System Administrator Guide 413 . The configuration files include information that uniquely identifies a sensor and cannot be shared.

the backup file can be saved to a remote location. See the following sections for more information. in addition to event and packet data. copy it via SCP to a remote host. As an alternative or if your backup file is larger than 4GB. You may also want to back up the system when testing configuration changes so that you can revert to the saved configuration. Additionally.Using Backup and Restore Creating Backup Files Chapter 12 You can save backup files to the appliance or to your local computer. • • • • • See Creating Backup Files on page 414 for information about backing up files from the appliance. Creating Backup Files Requires: IPS or DC/ MDC To view and use existing system backups go to the System Backup Management page.9. You can choose to save the backup file on the appliance or on your local computer. if needed. if you are using a Series 2 Defense Center. Uploading a backup from your local computer does not work on backup files larger than 4GB since web browsers do not support uploading files that large. data correlation is temporarily suspended. See Uploading Backups from a Local Host on page 420 for information about uploading backup files from a local host. See Creating Backup Profiles on page 418 for information about creating backup profiles that you can use later as templates for creating backups. Version 4. you can use remote storage as detailed in Managing Remote Storage on page 393.1 Sourcefire 3D System Administrator Guide 414 . You should periodically save a backup file that contains all of the configuration files required to restore the appliance. See Restoring the Appliance from a Backup File on page 421 for information about how to restore a backup file to the appliance. See Performing Sensor Backup with the Defense Center on page 419 for information about backing up managed sensors with the Defense Center. see Managing Remote Storage on page 393. When your backup task is collecting RNA events. On Series 2 Defense Centers.

Version 4.9.1 Sourcefire 3D System Administrator Guide 415 .Using Backup and Restore Creating Backup Files Chapter 12 The Defense Center and Master Defense Center version of the page is shown below.

type a name for the backup file. Select Operations > Tools > Backup/Restore. 6. 3. Click Sensor Backup on a 3D Sensor toolbar or Defense Center Backup on a Defense Center toolbar. Version 4.9. and spaces. the 3D Sensor version of the page is shown below. select the files that you want to include from the Unified File List. Requires: IPS or DC/MDC To archive the configuration. 2. In the Name field. select Backup Configuration. Requires: IPS or DC/MDC To archive the entire event database. To create a backup file: Access: Maint/Admin 1. 4.Using Backup and Restore Creating Backup Files Chapter 12 For comparison. select Backup Events. The System Backup Management page appears.1 Sourcefire 3D System Administrator Guide 416 . punctuation. You can use alphanumeric characters. The Backup page appears. Requires: IPS To archive individual intrusion event data files. 5.

select the Email when complete check box and type your email address in the accompanying text box. to be notified when the backup is complete.1 Sourcefire 3D System Administrator Guide 417 . to use secure copy (scp) to copy the backup archive to a different machine. 8.Using Backup and Restore Creating Backup Files Chapter 12 7. TIP! You can repeat this step to add additional files. select the Copy when complete check box and then type the following information in the accompanying text boxes: • • • • the hostname or IP address of the machine where you want to copy the backup the path to the directory where you want to copy the backup the user name that you want to use to log into the remote machine the password for that user name TIP! Sourcefire recommends that you periodically save backups to a remote location so that the appliance can be restored in case of system failure. Requires: IPS Ensure that the value of the compressed backup file in the Selected Sum field is less than the value in the Available Space field. If you want to include an additional file in the backup. Optionally. You must make sure that your mail relay host is configured as described in Configuring a Mail Relay Host and Notification Address on page 338. Often. TIP! The compressed value that appears in the Selected Sum field is a conservative estimate of the size of the compressed file. Optionally. the file will be smaller. 9. type the full path and file name in the Additional Files field and click the plus sign (+).9. Version 4. 10.

2. Select Operations > Tools > Backup/Restore. you can direct the backup file to a remote location. a backup profile is automatically created.1 Sourcefire 3D System Administrator Guide 418 . The backup file is saved in the /var/sf/backup directory. 3. click Start Backup. TIP! When you create a backup file as described in Creating Backup Files on page 414. see Managing Remote Storage on page 393. To create a backup profile: Access: Maint/Admin 1. See Creating Backup Profiles on page 418 for more information.9. • To save this configuration as a backup profile that you can use later. You can later select one of these profiles when you are backing up the files on your appliance. see Restoring the Appliance from a Backup File on page 421. Version 4. click Save As New. You have the following options: • To save the backup file to the appliance. Click Create Profile. TIP! You can click Edit to modify an existing profile or click Delete to delete a profile from the list. you can view the file on the Restoration Database page. The System Backup page appears. On Series 2 Defense Centers. Click Backup Profiles on the toolbar. You can modify or delete the backup profile by selecting Operations > Tools > Backup & Restore and then clicking Backup Profiles. The Backup Profiles page appears with a list of existing backup profiles. The System Backup Management page appears. For information about restoring a backup file.Using Backup and Restore Creating Backup Profiles Chapter 12 11. When the backup process is complete. Creating Backup Profiles Requires: IPS or DC/ MDC You can use the Backup Profiles page to create backup profiles that contain the settings that you want to use for different types of backups.

You can use alphanumeric characters. 2. See Creating Backup Files on page 414 for more information about the options on this page. The default name for the backup file uses the name of the managed 3D Sensor. 3. RNA Software for Red Hat Linux. Type a name for the backup profile. or Intrusion Agents. they change to underscores.1 Sourcefire 3D System Administrator Guide 419 . select the Include All Unified Files check box. and spaces. Version 4. Click Sensor Backup on the toolbar. 4. To include event data in addition to configuration data. The System Backup Management page appears. 3Dx800 sensors. select the managed sensors that you want to back up. 6. To back up a managed sensor: Access: Maint/Admin 1. The Backup Profiles page appears and includes your new profile in the list. Note that the unified files are binary file that the Sourcefire 3D System uses to log event data. 5. In the Sensors field. The Remote Backup page appears.Using Backup and Restore Performing Sensor Backup with the Defense Center Chapter 12 4. punctuation. You cannot use remote backup and restore to manage data on Crossbeam-based software sensors. Select Operations > Tools > Backup/Restore. Configure the backup profile according to your needs. Click Save As New to save the backup profile. TIP! If you use a backup file name containing spaces or punctuation characters.9. Performing Sensor Backup with the Defense Center Requires: DC You can use the Defense Center to back up data on managed 3D Sensors.

As an alternative. select the Retrieve to DC check box. leave this check box unselected. Uploading Backups from a Local Host Requires: DC If you download a backup file to your local host using the download function described in the Backup Management table on page 421. The System Backup Management page appears. click Upload Backup. Click Upload Backup. 2. A success messages appears and the backup task is set up. 3.Using Backup and Restore Uploading Backups from a Local Host Chapter 12 5. 6. To save the backup file on the Defense Center. see Managing Remote Storage on page 393. Click Start Backup. you can view the backup file on the Restoration Database page. The Upload Backup page appears. Version 4. Click Browse. To upload a backup from your local host: Access: Maint/Admin 1. Check the task status for progress. Select Operations > Tools > Backup/Restore. After you select the file to upload. On Series 2 Defense Centers.9. TIP! To save each sensor’s backup file on the sensor itself. copy the backup via SCP to a remote host and retrieve it from there. When the backup is complete. the backup file can be saved to and retrieved from a remote location. TIP! Uploading a backup larger than 4GB from your local host does not work because web browsers do not support uploading files that large. TIP! It can take several minutes to complete the backup. and navigate to the backup file.1 Sourcefire 3D System Administrator Guide 420 . you can upload it to a Defense Center.

Click with the backup file selected to restore it on the appliance. the protocol. On Series 2 Defense Centers. The backup file is uploaded and appears in the backup list. and version. type. After you complete the restoration process. If you use remote storage.9. and backup directory are listed at the top of the page.1 Sourcefire 3D System Administrator Guide 421 . you must apply the latest SEU. Note that you can only restore a backup to an identical appliance type and version. Restoring the Appliance from a Backup File Requires: IPS or DC/ MDC You can restore the appliance from backup files using the System Backup Management page. If you use local storage. Version 4.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 4. Click Backup Management on the toolbar to return to the System Backup Management page. TIP! After the Defense Center verifies the file integrity. Backup Management Column System Information Date Created File Name Location Size (MB) Events? View Restore Description The originating appliance name. Click with the backup file selected to view a list of the files included in the compressed backup file. in megabytes “Yes” indicates the backup includes event data. refresh the System Backup Management page to reveal detailed file system information. select Enable Remote Storage for Backups to enable or disable remote storage at the top of the System Backup Management page. backup system. The Backup Management table describes each column and icon on the System Backup Management page. backup files are saved to /var/sf/backup which is listed with the amount of disk space used in the /var partition at the top of the System Backup Management page. The date and time that the backup file was created The full name of the backup file The location of the backup file The size of the backup file.

1 Sourcefire 3D System Administrator Guide 422 . The System Backup Management page appears. click to send the backup to the designated remote backup location. A Series 2 Defense Center version of the page is shown.9.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 Backup Management (Continued) Column Download Delete Move Description Click with the backup file selected to save it to your local computer. On a Series 2 Defense Center when you have a previouslycreated local backup selected. Click with the backup file selected to delete it. Version 4. To restore the appliance from a backup file: Access: Admin 1. Select Operations > Tools > Backup/Restore.

all event data. The Restore Screen page appears. and its file size and date. Select the backup file that you want to restore and click Restore. To view the contents of a backup file. select either or both: • • Replace Configuration Data Restore Event Data Then click Restore to begin the restoration. on the 3D Sensor.9. 3. select the file and click View. its owner and permissions. On the toolbar. 5. WARNING! This procedure will overwrite all configuration files and. Version 4. The manifest appears listing the name of each file. 4. click Backup Management to return to the System Backup Management page.1 Sourcefire 3D System Administrator Guide 423 . Requires: DC/MDC To restore files.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 2. The Defense Center version of the page is truncated to show a sample of the files that are backed up.

Re-apply any intrusion. 9. Click Restore to begin the restoration. Version 4. select the files that you want to include from the Unified File List box. 8. click Cancel. TIP! To cancel the restoration. 7. Reboot the appliance.9. RNA detection. Requires: IPS If you want to restore intrusion event data.1 Sourcefire 3D System Administrator Guide 424 . and system policies to the restored system. Apply the latest SEU to re-apply SEU rule and software updates.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 6. health. The appliance is restored using the backup file you specified.

IMPORTANT! Some tasks (such as those involving automated software and SEU updates and those that require pushing updates or intrusion policies to managed sensors) can place a significant load on networks with low bandwidths. including: • • • • • • • • • • • running backups Requires: IPS applying intrusion policies generating reports Requires: DC + RNA running Nessus scans Requires: DC + RNA synchronizing Nessus plugins Requires: DC + RNA running Nmap scans Requires: DC + RNA + IPS using RNA rule recommendations Requires: IPS importing Security Enhancement Updates (SEUs) downloading and installing software updates Requires: DC + RNA downloading and installing vulnerability database updates Requires: DC pushing downloaded updates to managed sensors You can schedule tasks to run once or on a recurring schedule. You should always schedule tasks like these to run during periods of low network use.9. Version 4.Scheduling Tasks Chapter 13 Administrator Guide You can schedule many different types of administrative tasks to run at scheduled times.1 Sourcefire 3D System Administrator Guide 425 .

• • • • • • • • • • Configuring a Recurring Task Requires: IPS or DC/ MDC You set the frequency for a recurring task using the same process for all types of tasks.1 Sourcefire 3D System Administrator Guide 426 . Automating Vulnerability Database Updates on page 437 provides procedures for scheduling the download. Automating Recommended Rule State Generation on page 456 provides procedures for scheduling automatic update of intrusion rule state recommendations based on RNA data. Synchronizing Nessus Plugins on page 452 provides procedures for synchronizing your sensor with the Nessus server. Editing Scheduled Tasks on page 461 describes how to edit an existing task. Automating Reports on page 448 provides procedures for scheduling reports. and installation of software updates. Automating Software Updates on page 430 provides procedures for scheduling the download. Automating SEU Imports on page 444 provides procedures for scheduling rule updates. Automating Intrusion Policy Applications on page 446 provides procedures for scheduling intrusion policy applications. IMPORTANT! You cannot configure a recurring task schedule on the inactive Defense Center in a high availability pair of Defense Centers. push. Deleting Scheduled Tasks on page 461 describes how to delete one-time tasks and all instances of recurring tasks. Viewing Tasks on page 458 describes how to view and manage tasks after they are scheduled. Version 4. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active.9. Automating Backup Jobs on page 428 provides procedures for scheduling backup jobs. push. and installation of software updates. Automating Nmap Scans on page 454 provides procedures for scheduling Nessus scans.Scheduling Tasks Configuring a Recurring Task Chapter 13 See the following sections for more information: • • • • Configuring a Recurring Task on page 426 explains how to set up a scheduled task so that it runs at regular intervals. Automating Nessus Scans on page 450 provides procedures for scheduling Nessus scans.

From the Job Type list. specify the time when you want to start your recurring task. if you create a task scheduled for 2am during standard time. You can use the drop-down list to select the month. 7. To configure a recurring task: Access: Maint/Admin 1. type 2 and select Day(s) to run the task every two days. In the Start On field. 5. Click Add Task. the Defense Center or 3D Sensor with IPS automatically adjusts its local time display for daylight saving time (DST). day. In the Run At field. For the Schedule task to run option. Further. You can specify a number of hours. Each of the types of tasks you can schedule is explained in its own section. specify the date when you want to start your recurring task. if you create a task scheduled for 2am during DST. specify how often you want the task to recur. select the type of task that you want to schedule. it will run at 1am during standard time. 2. However. Select Operations > Tools > Scheduling. it will run at 3am during DST. 4. which is determined by using the time zone you specify in your system settings. or months. The page reloads with the recurring task options.9.Scheduling Tasks Configuring a Recurring Task Chapter 13 Note that the time displayed on most pages on the web interface is the local time. select Recurring. In the Repeat Every field. That is. Version 4. where appropriate. The Scheduling page appears. For example. and year. The Add Task page appears. 6. recurring tasks that span the transition dates from DST to standard time and back do not adjust for the transition. days. weeks. TIP! You can either type a number or use the arrow buttons to specify the interval. Similarly. 3.1 Sourcefire 3D System Administrator Guide 427 .

9.1 Sourcefire 3D System Administrator Guide 428 . The remaining options on the Add Task page are determined by the task you are creating. Select Operations > Tools > Scheduling. If you selected Month(s) in the Repeat Every field. See the following sections for more information: • • • • • • • • • • Automating Backup Jobs on page 428 Automating Software Updates on page 430 Automating Vulnerability Database Updates on page 437 Automating SEU Imports on page 444 Automating Intrusion Policy Applications on page 446 Automating Reports on page 448 Automating Nessus Scans on page 450 Synchronizing Nessus Plugins on page 452 Automating Nmap Scans on page 454 Automating Recommended Rule State Generation on page 456 Automating Backup Jobs Requires: IPS or DC/ MDC You can use the scheduler to automate system backups of a Defense Center or a 3D Sensor with IPS. a Repeat On field appears. a Repeat On field appears. Click Add Task. TIP! You must design a backup profile before you can configure it as a scheduled task. 2. For information on backup profiles. To automate backup tasks: Access: Maint/Admin 1. The Add Task page appears. Use the drop-down list to select the day of the month when you want to run the task. If you selected Week(s) in the Repeat Every field. 9. The Scheduling page appears. see Creating Backup Profiles on page 418. Version 4. Select the check boxes next to the days of the week when you want to run the task.Scheduling Tasks Automating Backup Jobs Chapter 13 8.

4. TIP! The comment field appears in the View Tasks section of the page. select the appropriate backup profile. TIP! The Current Time field indicates the current time on the appliance. type a name using up to 255 alphanumeric characters. spaces. From the Job Type list. spaces. Optionally. select Backup. In the Job Name field. Specify how you want to schedule the backup. or periods. 6. see Creating Backup Profiles on page 418. The page reloads to show the backup options.9. 5. in the Comment field.Scheduling Tasks Automating Backup Jobs Chapter 13 3. type a comment using up to 255 alphanumeric characters. 7. Version 4.1 Sourcefire 3D System Administrator Guide 429 . or dashes. you have several options for setting the interval between instances of the task. • For recurring tasks. use the drop-down lists to specify the start date and time. See Configuring a Recurring Task on page 426 for details. so you should try to keep it relatively short. For more information on creating new backup profiles. From the Backup Profile list. Once or Recurring. • For one-time tasks.

type the email address (or multiple email addresses separated by commas) where you want status messages sent. you can schedule automatic software installation and.1 Sourcefire 3D System Administrator Guide 430 . Note that when the Defense Center runs either the Push Latest Update or the Install Latest Update task. for example. However. and installation of software updates vary depending on whether you are updating an appliance directly or are using a Defense Center to perform the updates. if you schedule a task to install an update and the update has not finished copying from the Defense Center to the sensor. push. Optionally. So.Scheduling Tasks Automating Software Updates Chapter 13 8. IMPORTANT! You must have a valid email relay server configured to send status messages. if you want to update your 3D Sensor directly and it is connected to the internet. Always allow enough time between tasks for the process to complete. if you want to update the software for your Defense Center. Automating Software Updates The tasks you schedule to automate download. You should schedule the push and install tasks to happen in succession. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. the appliance automatically downloads the latest update when the installation task runs. Note that the tasks for pushing the update to managed sensors (on the Defense Center) and installing the update (on any appliance) automatically check the Version 4. it will install the pushed update when it runs the next day. The backup task is created. as long as it has access to the Internet. you can just schedule the Install Latest Update task. you can schedule Install Latest Update to download and install the latest Defense Center update. you must schedule two tasks: 1.9. For example. Push the update to managed sensors. If you use your Defense Center to automate software updates for managed 3D Sensors. When automating direct software updates for an appliance. 9. Install the update on managed sensors. you must always push the update to the sensor first. if you want to automate software updates on your managed sensors. For example. Similarly. then install it on the sensor. in the Email Status To: field. 2. as long as the appliance has access to the Internet. the installation task will not succeed. Tasks should be scheduled at least 30 minutes apart. if the scheduled installation task repeats daily. it queries the Sourcefire support site for the latest updates. Click Save.

Specifically. you can also automate vulnerability database (VDB) updates. push. you must manually upload. To automate software updates: Access: Maint/Admin 1. TIP! The automated update process allows you to download and install software patches and feature releases (generally when the last two digits in the four-digit version number change. you can use the Once option to download and install updates during off-peak hours after you learn that an update has been released. The Scheduling page appears. if you manually download an update to an appliance that cannot access the Support site.9.1).8. Click Add Task. Version 4. the task does not complete.2. This behavior also has implications for appliances that cannot access the Support site at all. You can use this task to schedule download of updates you plan to push or install manually. such as 4.Scheduling Tasks Automating Software Updates Chapter 13 Support site to ensure that you have the latest version of the update.1 or 4.8.8 or 4. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). and install the upgrade files. On the Defense Center. See the following sections for more information: • • • Automating Software Downloads on page 431 Automating Software Pushes on page 433 Automating Software Installs on page 435 Automating Software Downloads Requires: IPS or DC/ MDC You can create a scheduled task that automatically downloads the latest software updates from Sourcefire. 2. Select Operations > Tools > Scheduling. If you want to have more control over this process. For larger.9). If your appliance cannot access the Support site. more comprehensive updates (such as 4.1 Sourcefire 3D System Administrator Guide 431 . Instead you must manually push or install the updates as described in Updating System Software on page 398. The Add Task page appears.

specify which updates you want to download. In the Job Name field. you should set up a proxy as described in Configuring Network Settings on page 377 to allow it to download updates from the Sourcefire Support site (https://support. Requires: DC Select Vulnerability Database to download the most recent vulnerability database update. type a name using up to 255 alphanumeric characters. use the drop-down lists to specify the start date and time. Version 4. Specify how you want to schedule the task. select Download Latest Update.1 Sourcefire 3D System Administrator Guide 432 . 5. IMPORTANT! If your appliance is not directly connected to the Internet. or dashes. See Configuring a Recurring Task on page 426 for details. The Add Task page reloads to show the update options. Once or Recurring. • • Select Software to download the most recent software patch. • For recurring tasks.9. 4. In the Update Items section. From the Job Type list. The Defense Center version of the page is shown below. • For one-time tasks. Both options are selected by default. spaces.sourcefire. 6.Scheduling Tasks Automating Software Updates Chapter 13 3. you have several options for setting the interval between instances of the task. TIP! The Current Time field indicates the current time on the appliance.com/).

Click Add Task. Select Operations > Tools > Scheduling.Scheduling Tasks Automating Software Updates Chapter 13 7. make sure you allow enough time between the push task and a scheduled install task for the updates to be copied to the sensor. See Viewing the Status of Long-Running Tasks on page 600 for more information. To push software updates to managed sensors: Access: Maint/Admin 1. Version 4. you must push the software to the managed sensors before installing. Automating Software Pushes Requires: DC/MDC If you are installing software or vulnerability database updates on managed 3D Sensors. When you push software updates to managed sensors. The Scheduling page appears. IMPORTANT! You must have a valid email relay server configured to send status messages.1 Sourcefire 3D System Administrator Guide 433 . The task is created. so you should try to keep it relatively short. The Add Task page appears. 8. Optionally. Click Save. type a comment using up to 255 alphanumeric characters. When you create the task to push software updates to managed sensors. or periods. Note that if you manually download an update to an appliance that cannot access the Support site. Instead you must manually push the update as described in Updating System Software on page 398. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Optionally. information about the push process status is reported on the Tasks page. spaces. type the email address (or multiple email addresses separated by commas) where you want status messages sent. 2. TIP! The comment field appears in the View Tasks section of the page. in the Comment field.9. in the Email Status To: field. you cannot schedule pushes to managed sensors. 9.

type a comment using up to 255 alphanumeric characters.9. TIP! The Current Time field indicates the current time on the appliance. Requires: DC + RNA Select Vulnerability Database to push the VDB update. in the Comment field. or periods. so you should try to keep it relatively short. you have several options for setting the interval between instances of the task. Optionally. specify which updates you want to push to your managed sensors. or dashes. type a name using up to 255 alphanumeric characters. spaces. From the Sensor list. select the sensor that you want to receive updates. Version 4. spaces. • • Select Software to push the software update. 4. use the drop-down lists to specify the start date and time. See Configuring a Recurring Task on page 426 for details. Specify how you want to schedule the task.Scheduling Tasks Automating Software Updates Chapter 13 3. 8. 6. In the Job Name field.1 Sourcefire 3D System Administrator Guide 434 . In the Update Items section. Once or Recurring. The page reloads to show the options for pushing updates. TIP! The comment field appears in the View Tasks section of the page. • For one-time tasks. Both options are selected by default. From the Job Type list. select Push Latest Update. • For recurring tasks. 5. 7.

Version 4. you cannot schedule installation of that update. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Select Operations > Tools > Scheduling. The Add Task page appears. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Instead you must manually install the update as described in Updating System Software on page 398.9.Scheduling Tasks Automating Software Updates Chapter 13 9.1 Sourcefire 3D System Administrator Guide 435 . To schedule a software installation task: Access: Maint/Admin 1. 2. Click Add Task. WARNING! Depending on the update being installed. IMPORTANT! You must have a valid email relay server configured to send status messages. Note that if you manually download an update to an appliance that cannot access the Support site. in the Email Status To: field. the appliance may reboot after the software is installed. The Scheduling page appears. You can check the status of a running task on the Task Status page. The task is added. 10. Optionally. make sure you allow enough time between the task that pushes the update to the sensor and the task that installs the update. Click Save. See Automating Software Pushes on page 433 for information about pushing updates to managed sensors. Automating Software Installs Requires: IPS or DC/ MDC If you are using a Defense Center to create a task to install a software update on a managed sensor. See Viewing the Status of Long-Running Tasks on page 600 for more information.

Select the sensor where you want to install the update. or periods. use the drop-down lists to specify the start date and time. See Configuring a Recurring Task on page 426 for details. Optionally.Scheduling Tasks Automating Software Updates Chapter 13 3.9. 6. in the Comment field. you have several options for setting the interval between instances of the task. select Software to install the software update. The page reloads to show the options for installing updates. type a name using up to 255 alphanumeric characters. type a comment using up to 255 alphanumeric characters. In the Update Items section. spaces. Select the name of the Defense Center to install the update there. 8. so you should try to keep it relatively short. From the Job Type list. TIP! The comment field appears in the View Tasks section of the page. select Install Latest Update. Version 4. The Defense Center version of the page is shown below. or dashes. Once or Recurring. 5. If you are using a Defense Center. 4. TIP! The Current Time field indicates the current time on the appliance. • For recurring tasks. In the Job Name field. Specify how you want to schedule the task. from the Sensor list. you have the following options: • • 7.1 Sourcefire 3D System Administrator Guide 436 . • For one-time tasks. spaces.

Installing the VDB update. Optionally. you must schedule three tasks in this order: 1. Download the VDB update on your Defense Center. You can use the scheduling feature to download and install the latest VDB updates. 10. See Viewing the Status of Long-Running Tasks on page 600 for more information. VDB updates also include new vulnerabilities discovered by the Sourcefire Vulnerability Research Team (VRT). You can check the status of a running task on the Task Status page. For example.9. When automating VDB updates for your Defense Center. TIP! If your Sourcefire 3D System deployment includes IPS and RNA monitoring the same network segments. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Install the VDB update on the Defense Center and on those managed sensors. thereby ensuring that RNA is using the most up-to-date information to evaluate the hosts on your network. Downloading the VDB update. Automating Vulnerability Database Updates Sourcefire uses vulnerability database (VDB) updates to distribute new operating system fingerprints as we expand the list of operating systems that RNA recognizes. This ensures that your Defense Center is correctly setting the impact flag on the intrusion events generated by the traffic on your network. 2. IMPORTANT! You must have a valid email relay server configured to send status messages. Push the VDB update to your managed 3D Sensors that are using the RNA component. The scheduled software installation task is added. 2. you must automate two separate steps: 1.1 Sourcefire 3D System Administrator Guide 437 . Click Save. if you schedule a task to install an update and the update has not fully Version 4. Always allow enough time between tasks for the process to complete. When automating VDB updates for managed sensors with RNA.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 9. make sure that you download and install VDB updates and SEUs on a regular basis. 3. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. in the Email Status To: field.

IMPORTANT! You cannot download the VDB using a scheduled task on a sensor. However.9. Click Add Task.1 Sourcefire 3D System Administrator Guide 438 . 2. You must download the VDB on the Defense Center and push it to the sensor. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). Select Operations > Tools > Scheduling. Instead you must manually push or install the updates as described in Updating System Software on page 398. The Add Task page appears. the installation task will not succeed. If you want to have more control over this process. you can use the Once option to download and install VDB updates during off-peak hours after you learn that an update has been released. The Scheduling page appears. See the following sections for more information: • • • Automating VDB Update Downloads on page 438 Automating VDB Update Pushes on page 440 Automating VDB Update Installs on page 442 Automating VDB Update Downloads Requires: DC/MDC + RNA You can create a scheduled task that automatically downloads the latest vulnerability database updates from Sourcefire.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 downloaded. Version 4. if the scheduled installation task repeats daily. it will install the downloaded VDB update when it runs the next day. Note that if you manually download an update to an appliance that cannot access the Support site. To automate VDB updates: Access: Maint/Admin 1.

4.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. From the Job Type list. type a name using up to 255 alphanumeric characters. spaces. make sure Vulnerability Database is selected. so you should try to keep it relatively short. Version 4. See Configuring a Recurring Task on page 426 for details. you have several options for setting the interval between instances of the task. 7. 6. or periods. Specify how you want to schedule the task. Optionally. The Add Task page reloads to show the update options. In the Update Items section. 5. or dashes. TIP! The comment field appears in the View Tasks section of the page. use the drop-down lists to specify the start date and time. IMPORTANT! If your appliance is not directly connected to the Internet.sourcefire. TIP! The Current Time field indicates the current time on the appliance.1 Sourcefire 3D System Administrator Guide 439 . Both the Software and Vulnerability Database options are selected by default.com/). in the Comment field.9. In the Job Name field. • For one-time tasks. you should set up a proxy as described in Configuring Network Settings on page 377 to allow it to download updates from the Sourcefire Support site (https://support. type a comment using up to 255 alphanumeric characters. Once or Recurring. select Download Latest Update. • For recurring tasks. spaces.

The task is created. Optionally. Click Add Task. Automating VDB Update Pushes Requires: DC/MDC + 3D Sensor + RNA If you are installing vulnerability database updates on managed 3D Sensors with RNA. 2. To push VDB updates to managed 3D Sensors with RNA: Access: Maint/Admin 1. information about the process status is reported on the Tasks page.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 8. you cannot schedule pushes to managed sensors. Version 4. Select Operations > Tools > Scheduling. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Click Save. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. IMPORTANT! You must have a valid email relay server configured to send status messages.1 Sourcefire 3D System Administrator Guide 440 . The Add Task page appears. 9. WARNING! You must download vulnerability database updates before you can push them to managed sensors. you must push the update to the managed sensors before installing. Instead you must manually push the update as described in Updating System Software on page 398.9. Note that if you manually download an update to an appliance that cannot access the Support site. See Viewing the Status of Long-Running Tasks on page 600 for more information. The Scheduling page appears. When you push VDB updates to managed sensors. in the Email Status To: field.

select Push Latest Update. 7. Optionally. in the Comment field. you have several options for setting the interval between instances of the task. so you should try to keep it relatively short. In the Update Items section. 6. 4. TIP! The Current Time field indicates the current time on the appliance. Specify how you want to schedule the task. Both the Software and Vulnerability Database options are selected by default. Once or Recurring. make sure Vulnerability Database is selected.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. TIP! The comment field appears in the View Tasks section of the page. In the Job Name field. or dashes. The page reloads to show the options for pushing updates. 5. • For recurring tasks. or periods.1 Sourcefire 3D System Administrator Guide 441 . spaces. select the sensor that you want to receive updates. type a name using up to 255 alphanumeric characters. 8.9. See Configuring a Recurring Task on page 426 for details. type a comment using up to 255 alphanumeric characters. Version 4. spaces. • For one-time tasks. From the Job Type list. use the drop-down lists to specify the start date and time. From the Sensor list.

If you are creating a task to install a VDB update on a managed sensor.1 Sourcefire 3D System Administrator Guide 442 . See Automating VDB Update Pushes on page 440 for information about pushing updates to managed sensors. You should allow enough time for a scheduled VDB update to download when you set up a scheduled task to install it. Click Add Task. The Add Task page appears. You can check the status of a running task on the Task Status page. Automating VDB Update Installs Requires: DC/MDC + RNA After you have downloaded a VDB update. 2. Optionally. you cannot schedule installation of that update. Version 4. type the email address (or multiple email addresses separated by commas) where you want status messages sent. IMPORTANT! You must have a valid email relay server configured to send status messages. The Scheduling page appears.9. To schedule a software installation task: Access: Maint/Admin 1. 10. you can schedule the installation process. The task is added. Note that if you manually download an update to an appliance that cannot access the Support site. See Viewing the Status of Long-Running Tasks on page 600 for more information. you must allow enough time between the task that pushes the update to the sensor and the task that installs the update. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. in the Email Status To: field.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 9. Click Save. Instead you must manually install the updates as described in Updating System Software on page 398. Select Operations > Tools > Scheduling.

4. spaces. select Install Latest Update. select Vulnerability Database to install the VDB update. spaces. select the name of the Defense Center from the drop-down list. so you should try to keep it relatively short. In the Update Items section.9. From the Sensor list. in the Comment field. In the Job Name field. From the Job Type list. Once or Recurring. use the drop-down lists to specify the start date and time. If you want to install the update on the Defense Center. • For one-time tasks. TIP! The comment field appears in the View Tasks section of the page.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 3. Version 4. type a comment using up to 255 alphanumeric characters. 6. or dashes. you have the following options: • • 7. you have several options for setting the interval between instances of the task. select the name of the sensor from the drop-down list. See Configuring a Recurring Task on page 426 for details. The page reloads to show the options for installing updates. If you want to install the update on a managed sensor. 8. 5.1 Sourcefire 3D System Administrator Guide 443 . or periods. TIP! The Current Time field indicates the current time on the appliance. Specify how you want to schedule the task. Optionally. • For recurring tasks. type a name using up to 255 alphanumeric characters.

If you allow SEUs to update your base policy. Download the latest SEU. Automating SEU Imports Requires: IPS or DC/ MDC + IPS As new vulnerabilities are identified. however. However. You can check the status of a running task on the Task Status page. 2. IMPORTANT! You must have a valid email relay server configured to send status messages. Applying an intrusion policy from a Defense Center to a managed sensor after you import an SEU does not apply the SEU to the sensor. If you enable Update when a new SEU is installed for the base policy of an existing policy and the SEU contains changes to the default rule states for existing rules in that base policy. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. 3. The selected subtasks present in the Import SEU task occur in the following order: download. and policy re-apply. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Optionally. An SEU contains new and updated standard text rules and shared object rules and may contain updated versions of Snort® and features such as preprocessors and decoders.Scheduling Tasks Automating SEU Imports Chapter 13 9. VRT sometimes uses an SEU to change the default state of one or more rules in a default policy. the Sourcefire Vulnerability Research Team (VRT) releases Security Enhancement Updates (SEUs). The Import SEU task allows you to schedule the following subtasks separately or to combine them into one scheduled task: 1. Import the SEU. you also must re-apply your intrusion policies on your managed 3D Sensors with IPS. you also allow the Version 4. 10. those changes are also imported. the next configured subtask begins. install. Note that you can only re-apply policies applied from the appliance where the scheduled task is configured. rule state update. The scheduled VDB installation task is added.9. See Viewing the Status of Long-Running Tasks on page 600 for more information. any new rules or features provided by the SEU that are enabled in the policy you apply to the sensor are also enabled on the sensor by that policy. You can automatically download and install SEUs. Note that on the Defense Center. in the Email Status To: field.1 Sourcefire 3D System Administrator Guide 444 . the SEU does not override your change. Once one subtask completes. Click Save. Re-apply your intrusion policy so that the new SEU takes effect. that if you changed a rule state. Note.

that if you have changed the rule state. see Importing SEUs and Rule Files in the Analyst Guide. The Add Task page appears. 3. so make sure you schedule downloads during periods of low network use. In addition. the SEU will not override your change. however. Select Operations > Tools > Scheduling. 2. From the Job Type list. you can also use the recurring SEU import feature on the Import SEU page. Note. To schedule an Import SEU task: Access: Maint/Admin 1.Scheduling Tasks Automating SEU Imports Chapter 13 SEU to change the default state of a rule in your policy when the default state changes in the default policy you used to create your policy (or in the default policy it is based on). select Import SEU. For more information on the recurring SEU import feature and a comparison of the two methods of setting up recurring imports. Click Add Task.1 Sourcefire 3D System Administrator Guide 445 . The Scheduling page appears. Note that you must be using Snort 2.9.8.2 or higher to import recurring SEUs on the Import SEU page. In addition to configuring SEU imports on the Scheduling page. Version 4. IMPORTANT! SEUs may contain new binaries. SEUs can be quite large. Make sure your process for downloading and importing SEUs complies with your security policies. The page reloads to show the options for importing SEUs.

Once or Recurring. type a comment using up to 255 alphanumeric characters. TIP! The comment field appears in the View Tasks section of the page. Optionally. select Reapply intrusion policies after the SEU import completes. type the email address (or multiple email addresses separated by commas) where you want status messages sent. To use this task to install the latest downloaded SEU. you have several options for setting the interval between instances of the task. or dashes. The task is created.Scheduling Tasks Automating Intrusion Policy Applications Chapter 13 4. 10. 5. select Install the latest downloaded SEU. 8. select Download the latest SEU from the support site. This feature is useful if you need to use different policies during different times of the day. spaces. in the Comment field. type a name using up to 255 alphanumeric characters. 11. use the drop-down lists to specify the start date and time. Click Save. • For one-time tasks. or periods. Specify how you want to schedule the task. IMPORTANT! You must have a valid email relay server configured to send status messages. so you should try to keep it relatively short. Automating Intrusion Policy Applications Requires: IPS or DC/ MDC + IPS You can automatically apply intrusion policies at scheduled intervals. To re-apply intrusion policies after installing an SEU.1 Sourcefire 3D System Administrator Guide 446 . To use this task to download the latest SEU. See Configuring a Recurring Task on page 426 for details. 9. Optionally. spaces. In the Job Name field. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. in the Email Status To: field. • For recurring tasks. 6. Version 4. 7. TIP! The Current Time field indicates the current time on the appliance.9.

Click Add Task. select the detection engine where you want to apply the policy. The Add Task page appears. In the Detection Engine field. 7. 4. select Apply Policy. The Scheduling page appears. In the Policy Name field. or dashes. use the drop-down lists to specify the start date and time. 6. Select Operations > Tools > Scheduling. • For one-time tasks. you have several options for setting the interval between instances of the task.1 Sourcefire 3D System Administrator Guide 447 . See Configuring a Recurring Task on page 426 for details. Version 4. 5. From the Job Type list.Scheduling Tasks Automating Intrusion Policy Applications Chapter 13 To automate intrusion policy application: Access: Maint/Admin 1. select the intrusion policy you want to apply from the drop-down list or select Policy Default to apply the policy to each detection engine targeted in the policy. 2. type a name using up to 255 alphanumeric characters. In the Job Name field. spaces. • For recurring tasks. Once or Recurring. 3. Specify how you want to schedule the task. The page reloads to show the options for applying an intrusion policy. TIP! The Current Time field indicates the current time on the appliance.9.

See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Version 4. 2. Optionally. Click Add Task. or periods. Click Save. so you should try to keep it relatively short. Automating Reports Requires: IPS or DC/ MDC You can automate reports so that they run at regular intervals. 9. However.1 Sourcefire 3D System Administrator Guide 448 . you must design a profile for your report before you can configure it as a scheduled task. in the Email Status To: field. type a comment using up to 255 alphanumeric characters. See Creating a Report Profile on page 246 for more information about using the report designer to create a report profile. See Viewing the Status of Long-Running Tasks on page 600 for more information. Optionally. The task is created. type the email address (or multiple email addresses separated by commas) where you want status messages sent. To automate a report: Access: Maint/Admin 1. TIP! The comment field appears in the View Tasks section of the page. The Add Task page appears. Select Operations > Tools > Scheduling.9. IMPORTANT! You must have a valid email relay server configured to send status messages. You can check the status of a running task on the Task Status page. 10. The Scheduling page appears.Scheduling Tasks Automating Reports Chapter 13 8. in the Comment field. spaces.

TIP! The Current Time field indicates the current time on the appliance. 4. Optionally.9. In the Job Name field. Once or Recurring. type a comment using up to 255 alphanumeric characters. Version 4. In the Report Profile field. or dashes. spaces. See Configuring a Recurring Task on page 426 for details. Specify how you want to schedule the task. in the Comment field. • For one-time tasks.Scheduling Tasks Automating Reports Chapter 13 3. select Reports.1 Sourcefire 3D System Administrator Guide 449 . From the Job Type list. The page reloads to show the options for setting up a report to run automatically. 7. use the drop-down lists to specify the start date and time. so you should try to keep it relatively short. spaces. select the report profile that you want to use from the drop-down list. TIP! The comment field appears in the View Tasks section of the page. • For recurring tasks. The Defense Center version of the page is displayed below. 5. in the Remote Run field. You cannot run remote reports on Crossbeam-based software Requires: DC If you want to run the report on a managed sensor. 6. select the name of the sensor from the drop-down list. 8. type a name using up to 255 alphanumeric characters. or periods. IMPORTANT! sensors. you have several options for setting the interval between instances of the task.

Optionally. Click Save. in the Email Status To: field. Automating Nessus Scans You can schedule regular Nessus scans of targets on your network.9. The task is created. 10.1 Sourcefire 3D System Administrator Guide 450 . see Nessus Scan Remediations in the Analyst Guide. you need to complete several Nessus configuration steps prior to defining a scheduled scan. For more information on starting the server and configuring and activating a Nessus user. set up the Nessus server on your Defense Center. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Preparing Your System to Run a Nessus Scan If you have not used the Nessus scanning capability before. You can also schedule scans to test for recurrent vulnerabilities to attacks that have happened in the past. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Version 4. see Creating a Nessus Scan Instance on page 643. see Configuring a Local Nessus Server on page 641. IMPORTANT! Make note of the name of the scan instance you create. Create a scan instance to define the Nessus server to be used by your scan. Automated scans allow you to test periodically to make sure that operating system updates or other changes do not introduce vulnerabilities on your enterprise-critical systems. For more information.Scheduling Tasks Automating Nessus Scans Chapter 13 9. See the following sections for more information: • • Preparing Your System to Run a Nessus Scan on page 450 Scheduling a Nessus Scan on page 451 Note that a Policy & Response Administrator can also use a Nessus scan as a remediation. 1. If you do not have an existing external Nessus server. For more information on setting up a Nessus server connection profile. IMPORTANT! You must have a valid email relay server configured to send status messages. 2. You need to select this name when prompted for the Nessus Remediation name when setting up the scheduled scan.

Click Add Task. select Nessus Scan. 3. see Creating a Nessus Remediation on page 646. 2. For more information on setting up a scan target. 5. To schedule Nessus scanning: Access: Maint/Admin 1. The Scheduling page appears. For more information on setting up a remediation definition. Scheduling a Nessus Scan Requires: DC + RNA You can automate Nessus scanning using a specific scan remediation by scheduling the scan.1 Sourcefire 3D System Administrator Guide 451 . Create a remediation definition to define what plugins and Nessus scan settings should be used when the scheduled scan runs. From the Job Type list. Version 4.Scheduling Tasks Automating Nessus Scans Chapter 13 3. see Creating a Nessus Scan Target on page 645. Create a scan target to define the target hosts and host ports to scan. The Add Task page appears. Continue with Scheduling a Nessus Scan. 4. Select Operations > Tools > Scheduling.9. The page reloads to show the options for automating Nessus scans.

use the drop-down lists to specify the start date and time. 6. Click Save. See Configuring a Recurring Task on page 426 for details. select the scan target that defines the target hosts you want to scan. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. spaces. in the Comment field. type a comment using up to 255 alphanumeric characters. you have several options for setting the interval between instances of the task. IMPORTANT! You must have a valid email relay server configured to send status messages.1 Sourcefire 3D System Administrator Guide 452 . Optionally. In the Job Name field. in the Email Status To: field. The task is created. You may want to schedule your plugin synchronization to occur shortly before your scheduled Nessus scans to make sure that you scan with the latest list of plugins. 9. Optionally. • For recurring tasks. Specify how you want to schedule the task. TIP! The Current Time field indicates the current time on the appliance. or dashes. or periods. spaces. so you should try to keep it relatively short. Version 4. select the Nessus remediation for the Nessus server where you want to run the scan. Synchronizing Nessus Plugins Requires: DC + RNA You can automate synchronization with the Nessus server to obtain an up-to-date list of plugins before you scan. Once or Recurring. TIP! The comment field appears in the View Tasks section of the page. In the Nessus Remediation field. 8. In the Nessus Target field. type the email address (or multiple email addresses separated by commas) where you want status messages sent.9. 10. type a name using up to 255 alphanumeric characters. 5. • For one-time tasks.Scheduling Tasks Synchronizing Nessus Plugins Chapter 13 4. 7.

5. 4. In the Nessus Instance field. type a comment using up to 255 alphanumeric characters. The page reloads to show the Nessus plugin synchronization options. The Scheduling page appears. See Configuring a Recurring Task on page 426 for details. you have several options for setting the interval between instances of the task. or periods. 2. 7. TIP! The comment field appears in the View Tasks section of the page. use the drop-down lists to specify the start date and time. so you should try to keep it relatively short. select the instances with the Nessus plugins that you want to synchronize. Once or Recurring. in the Comment field.1 Sourcefire 3D System Administrator Guide 453 . 3. Optionally. spaces. In the Job Name field. Specify how you want to schedule the task. The Add Task page appears. From the Job Type list. select Synchronize Nessus Plugins. The Current Time field indicates the current time on the appliance. • For one-time tasks.Scheduling Tasks Synchronizing Nessus Plugins Chapter 13 To schedule Nessus plugin synchronization: Access: Maint/Admin 1. or dashes. • For recurring tasks. Select Operations > Tools > Scheduling. 6. type a name using up to 255 alphanumeric characters. spaces. Click Add Task. Version 4.9.

Click Save. when an operating system conflict occurs on a host. For more information on setting up a Nmap server connection profile. 1. which resolves the conflict.Scheduling Tasks Automating Nmap Scans Chapter 13 8. in the Email Status To: field. 9. you need to rescan periodically to keep that data up to date. Version 4. see Creating an Nmap Scan Target in the Analyst Guide. Preparing Your System for an Nmap Scan If you have not used the Nmap scanning capability before. IMPORTANT! You must have a valid email relay server configured to send status messages. Create a scan target to define the target hosts and host ports to scan. For example. see Creating an Nmap Scan Instance in the Analyst Guide. type the email address (or multiple email addresses separated by commas) where you want status messages sent. Optionally. 2. that conflict can trigger an Nmap scan.1 Sourcefire 3D System Administrator Guide 454 .9. you must complete several Nmap configuration steps prior to defining a scheduled scan. For more information. For more information on setting up a scan target. Automated scans allow you to refresh operating system and service information previously supplied by an Nmap scan. See the following sections for more information: • • Preparing Your System for an Nmap Scan Scheduling an Nmap Scan Note that a Policy & Response Administrator can also use an Nmap scan as a remediation. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. You can also schedule scans to automatically test for unidentified services on hosts in your network. Because RNA cannot update Nmap-supplied data. Create a scan instance to define the Nmap server to be used by your scan. You need to select this name when prompted for the Nmap Configuration name when setting up the scheduled scan. see Nmap Scan Remediations in the Analyst Guide. Running the scan obtains updated operating system information for the host. The task is created. IMPORTANT! Make note of the name of the scan instance you create. Automating Nmap Scans You can schedule regular Nmap scans of targets on your network.

To schedule Nmap scanning: Access: Maint/Admin 1. Create a remediation definition to define what plugins and Nmap scan settings should be used when the scheduled scan runs. see Creating an Nmap Remediation in the Analyst Guide. Version 4. Once Nmap replaces a host’s operating system or services detected by RNA with the results from an Nmap scan.Scheduling Tasks Automating Nmap Scans Chapter 13 3. Click Add Task. The page reloads to show the options for automating Nmap scans. Continue with Scheduling an Nmap Scan. Scheduling an Nmap Scan Requires: DC + RNA You can schedule a scan of a host or hosts on your network using the Nmap utility. From the Job Type list. 4. Nmap-supplied service and operating system data remains static until you run another Nmap scan. The Add Task page appears. 2.9. For more information on setting up a remediation definition. you may want to set up regularly scheduled scans to keep Nmap-supplied operating system and services up to date.1 Sourcefire 3D System Administrator Guide 455 . select Nmap Scan. If the host is deleted from the network map and re-added. any Nmap scan results are discarded and RNA resumes monitoring of all operating system and service data for the host. If you plan to scan a host using Nmap. 3. The Scheduling page appears. RNA no longer updates the information replaced by Nmap for the host. Select Operations > Tools > Scheduling.

5. In the Job Name field. In the Nmap Remediation field. Optionally. select the scan target that defines the target hosts you want to scan. select the Nmap remediation to use when running the scan. Click Save. in the Comment field. you have several options for setting the interval between instances of the task. spaces. See Configuring a Recurring Task on page 426 for details. TIP! The Current Time field indicates the current time on the appliance. type a comment using up to 255 alphanumeric characters. 9. IMPORTANT! You must have a valid email relay server configured to send status messages. In the Nmap Target field. Version 4. The task is created. or dashes. • For recurring tasks. • For one-time tasks. 7. or periods. Automating Recommended Rule State Generation Requires: DC + RNA + IPS IMPORTANT! If the system automatically generates scheduled recommendations for an intrusion policy with unsaved changes. Once or Recurring. 6.1 Sourcefire 3D System Administrator Guide 456 . so you should try to keep it relatively short. TIP! The comment field appears in the View Tasks section of the page.Scheduling Tasks Automating Recommended Rule State Generation Chapter 13 4. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. type the email address (or multiple email addresses separated by commas) where you want status messages sent.9. you must discard your changes in that policy and commit the policy if you want the policy to reflect the automatically generated recommendations. 10. use the drop-down lists to specify the start date and time. spaces. Specify how you want to schedule the task. type a name using up to 255 alphanumeric characters. in the Email Status To: field. See Committing Intrusion Policy Changes in the Analyst Guide for more information. 8. Optionally.

Click Add Task. To generate recommendations: Access: Maint/Admin 1.Scheduling Tasks Automating Recommended Rule State Generation Chapter 13 You can automatically generate rule state recommendations based on RNA data for your network using the most recently saved configuration settings in your custom intrusion policy. Version 4. 3. Modified rule states take effect the next time you apply your intrusion policy. The Add Task page appears. When the task runs. where you can configure RNA Recommended Rules in a policy. The Scheduling page appears. the system automatically generates recommended rule states. depending on the configuration of your policy. 4. See Managing RNA Rule State Recommendations in the Analyst Guide for more information. Select Operations > Tools > Scheduling. See Using RNA Recommendations in the Analyst Guide for more information. select RNA Recommended Rules. Optionally. 2. click the policies link in the Job Type field to display the Detection & Prevention page. Optionally. it also modifies the states of intrusion rules based on the criteria described in Managing RNA Rule State Recommendations in the Analyst Guide. The page reloads to show the options for generating RNA-recommended rule states. From the Job Type list.1 Sourcefire 3D System Administrator Guide 457 .9.

Once or Recurring. See Configuring a Recurring Task on page 426 for details. Next to Policies. in the Email Status To: field. 10. 8. Click the All Policies check box to select all policies. you have several options for setting the interval between instances of the task. You have the following options: • • In the Policies field. spaces. spaces. 9. Specify how you want to schedule the task. 6.1 Sourcefire 3D System Administrator Guide 458 .9. in the Comment field. or periods. type a comment using up to 255 alphanumeric characters. TIP! The Current Time field indicates the current time on the appliance. select one or more policies where you want to generate recommendations. type the email address (or multiple email addresses separated by commas) where you want status messages sent. 7. Version 4. • For recurring tasks.Scheduling Tasks Viewing Tasks Chapter 13 5. you can view them and evaluate their status. use the drop-down lists to specify the start date and time. Optionally. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. Use the Shift and Ctrl keys to select multiple policies. type a name using up to 255 alphanumeric characters. • For one-time tasks. IMPORTANT! You must have a valid email relay server configured to send status messages. select one or more policies. TIP! The comment field appears in the View Tasks section of the page. so you should try to keep it relatively short. The task is created. or dashes. In the Job Name field. Viewing Tasks After adding scheduled tasks. Click Save. Optionally. The View Options section of the page allows you to view scheduled tasks using a calendar and a list of scheduled tasks.

To view scheduled tasks using the calendar: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 459 .9.Scheduling Tasks Viewing Tasks Chapter 13 See the following sections for more information: • • Using the Calendar on page 459 Using the Task List on page 460 Using the Calendar Requires: DC/MDC or 3D Sensor The Calendar view option allows you to view which scheduled tasks occur on which day. Click < to move back one month. The Scheduling page appears. Select Operations > Tools > Scheduling. You can perform the following tasks using the calendar view: • • Click << to move back one year. 2. Version 4.

you can access it by selecting a date or task from the calendar. The task list appears at below the calendar when you open the calendar. Describes the current status for a scheduled task. Displays the comment that accompanies the scheduled task. • A check mark icon indicates that the task ran successfully. see Using the Task List on page 460. Displays the scheduled start date and time. In addition. Using the Task List Requires: DC/MDC or 3D Sensor The Task List shows a list of tasks along with their status. Click >> to move forward one year. Click Add Task to schedule a new task. Displays how often the task is run. Creator Delete Displays the name of the user that created the scheduled task. • A red ! indicates that the task failed. • A question mark icon indicates that the task is in an unknown state.1 Sourcefire 3D System Administrator Guide 460 . Click a specific task on a date to view the task in a task list table below the calendar. Click a date to view all scheduled tasks for the specific date in a task list table below the calendar. Version 4.) Task List Columns Column Name Type Start Time Frequency Comment Status Description Displays the name of the scheduled task. Click Today to return to the current month and year. Displays the type of scheduled task. IMPORTANT! For more information about using the task list. (See Using the Calendar on page 459 for more information.9. Deletes the scheduled task.Scheduling Tasks Viewing Tasks Chapter 13 • • • • • • Click > to move forward one month.

Later. Deleting Scheduled Tasks There are two types of deletions you can perform from the Schedule View page. To edit an existing scheduled task: Access: Maint/Admin 1. If you delete a task that is scheduled to run once. Click either the task that you want to edit or the day on which the task appears. after the task completes successfully. This feature is especially useful if you want to test a scheduled task once to make sure that the parameters are correct. If you delete an instance of a recurring task. See the following sections for more information: • • • • • • • • • • Automating Backup Jobs on page 428 Automating Software Updates on page 430 Automating Vulnerability Database Updates on page 437 Automating SEU Imports on page 444 Automating Intrusion Policy Applications on page 446 Automating Reports on page 448 Automating Nessus Scans on page 450 Synchronizing Nessus Plugins on page 452 Automating Nmap Scans on page 454 Automating Recommended Rule State Generation on page 456 5.1 Sourcefire 3D System Administrator Guide 461 . 2. Your change are saved and the Scheduling page appears again. Locate the task you want to edit in the table and click Edit. Select Operations > Tools > Scheduling. 3. You cannot change the type of job.9. and how often the task runs. The Task Details table containing the selected task or tasks appears. Edit the task to meet your needs. You can delete a specific one-time task that has not yet run or you can delete every instance of a recurring task. The Edit Task page appears showing the details of the task you selected. Version 4. the job name. you can change it to a recurring task. once or recurring. all instances of the task are deleted. only that task is deleted. including the start time.Scheduling Tasks Editing Scheduled Tasks Chapter 13 Editing Scheduled Tasks Requires: DC/MDC or 3D Sensor You can edit a scheduled task that you previously created. The remaining options are determined by the task you are editing. Click Save to save your edits. The Scheduling page appears. 4.

9. you automatically delete all instances of that task. The page reloads to display a table of tasks below the calendar. see Deleting a Recurring Task on page 462. To delete a single instance of a task. 2. A table containing the selected task or tasks appears. The Scheduling page appears. delete a task record: Access: Maint/Admin 1. 2. To delete a single task or. To delete a recurring task: Access: Maint/Admin 1. see Deleting a One-Time Task on page 462. Locate an instance of the recurring task you want to delete in the table and click Delete. The Scheduling page appears.1 Sourcefire 3D System Administrator Guide 462 . Select Operations > Tools > Scheduling. if it has already run.Scheduling Tasks Deleting Scheduled Tasks Chapter 13 The following sections describe how to delete tasks: • • To delete all instances of a task. On the calendar. select an instance of the recurring task you want to delete. Deleting a Recurring Task Requires: DC/MDC or 3D Sensor When you delete one instance of a recurring task. Deleting a One-Time Task Requires: DC/MDC or 3D Sensor You can delete a one-time scheduled task or delete the record of a previously-run scheduled task using the task list. 3. The instance of the task you selected is deleted. Version 4. 3. Select Operations > Tools > Scheduling. All instances of the recurring task are deleted. Locate the task you want to delete in the table and click Delete. Click the task that you want to delete or the day on which the task appears.

For more information.1 Sourcefire 3D System Administrator Guide 463 . You can also monitor both summary and detailed information on all processes that are currently running on the Defense Center or 3D Sensor. all on a single page. on the Host Statistics page you can monitor basic host statistics. The following sections provide more information about the monitoring features that the system provides: • Viewing Host Statistics on page 464 describes how to view host information such as: • • • • • • system uptime disk and memory usage RNA process statistics Data Correlator statistics system processes intrusion event information On the Defense Center. Version 4. For example. intrusion event information. see Understanding Health Monitoring on page 483. you can also use the health monitor to monitor disk usage and alert on low disk space conditions.9.Monitoring the System Chapter 14 Administrator Guide The Sourcefire 3D System provides many useful monitoring features to assist you in the daily administration of your system. and statistics for the Data Correlator and RNA processes for the current day.

see the Intrusion Event Information table on page 467 for details The Host Statistics table describes the host statistics listed on the Statistics page. and minutes since the system was last started. Viewing RNA Performance Statistics on page 478 describes how to view RNA performance statistics and how to generate graphs based on these statistics. The average number of processes in the CPU queue for the past 1 minute. Viewing IPS Performance Statistics on page 476 describes how to view IPS performance statistics and how to generate graphs based on these statistics. 5 minutes.1 Sourcefire 3D System Administrator Guide 464 . Understanding Running Processes on page 471 describes the basic system processes that run on the appliance. and 15 minutes. The percentage of system memory that is being used.Monitoring the System Viewing Host Statistics Chapter 14 • • • • Monitoring System Status and Disk Space Usage on page 468 describes how to view basic event and disk partition information. Viewing System Process Status on page 468 describes how to view basic process status. Host Statistics Category Time Uptime Memory Usage Load Average Description The current time on the system. see the Data Correlator Process Statistics table on page 465 for details RNA process statistics (Defense Center only .requires RNA). The number of days (if applicable). • Viewing Host Statistics Requires: Any The Statistics page lists the current status of following: • • • • general host statistics.requires RNA). hours. see the RNA Process Statistics table on page 466 for details intrusion event information (requires IPS).9. see the Host Statistics table on page 464 for details Data Correlator statistics (Defense Center only . Version 4.

System (%) VmSize (KB) VmRSS (KB) Description Number of RNA events that the Data Correlator receives and processes per second Number of flows that the Data Correlator receives and processes per second Average percentage of CPU time spent on user processes for the current day Average percentage of CPU time spent on system processes for the current day Average size of memory allocated to the Data Correlator for the current day. As the 3D Sensors perform data acquisition.Monitoring the System Viewing Host Statistics Chapter 14 Host Statistics (Continued) Category Disk Usage Description The percentage of the disk that is being used. in kilobytes Average amount of memory used by the Data Correlator for the current day. Data Correlator Process Statistics Category Events/Sec Flows/Sec CPU Usage . Processes If your Sourcefire 3D System deployment includes a Defense Center managing 3D Sensors with RNA.User (%) CPU Usage . and creates the RNA network map. See Viewing System Process Status on page 468 for more information. using statistics gathered between 12:00AM and 11:59PM for each detection engine. and analysis.9. See Monitoring System Status and Disk Space Usage on page 468 for more information. the RNA process correlates the data with the fingerprint and vulnerability databases. generates events. decoding.1 Sourcefire 3D System Administrator Guide 465 . Click the arrow to view more detailed host statistics. The Data Correlator analyzes the information from the binary files. The Data Correlator Process Statistics table describes the statistics displayed for the Data Correlator process. you can also view statistics about the Data Correlator and RNA processes for the current day. A summary of the processes running on the system. The statistics that appear for RNA and the Data Correlator are averages for the current day. and then produces binary files that are processed by the Data Correlator running on the Defense Center. in kilobytes Version 4.

Monitoring the System Viewing Host Statistics Chapter 14 The RNA Process Statistics table describes the statistics displayed for the RNA process. you can also view the time and date of the last intrusion event. RNA Process Statistics Category Packets Dropped (%) Mbits/Second Packets/Second CPU Usage . in kilobytes Average amount of memory used by the RNA process for the current day.9. If you manage your sensor so that intrusion events are not stored locally.System (%) VmSize (KB) VmRSS (KB) Description Average percentage of packets dropped by the RNA process for the current day Average number of megabits per second processed by the RNA process for the current day Average number of packets per second processed by the RNA process for the current day Average percentage of CPU time spent by user processes for the current day Average percentage of CPU time spent by system processes for the current day Average size of memory allocated to the RNA process for the current day. and the total number in the database. The information in the Intrusion Event Information section of the Statistics page is based on intrusion events stored on the sensor rather than those sent to the Defense Center. no intrusion event information is listed on this page.1 Sourcefire 3D System Administrator Guide 466 . This is also the case for 3D Sensors that cannot store events locally.User (%) CPU Usage . Version 4. in kilobytes On 3D Sensors with IPS and on Defense Centers that manage sensors with IPS. the total number of events that have occurred in the past hour and the past day.

Monitoring the System Viewing Host Statistics Chapter 14 The Intrusion Event Information table describes the statistics displayed in the Intrusion Event Information section of the Statistics page.1 Sourcefire 3D System Administrator Guide 467 . Select Operations > Monitoring > Statistics. The Defense Center version of the page is shown below. Intrusion Event Information Statistic Last Alert Was Total Events Last Hour Total Events Last Day Total Events in Database Description The date and time that the last event occurred The total number of events that occurred in the past hour The total number of events that occurred in the past twenty-four hours The total number of events in the events database To view the Statistics page: Access: Maint/Admin 1. Version 4. The Statistics page appears.9.

It provides general process information and specific information for each running process. Monitoring System Status and Disk Space Usage Requires: Any The Disk Usage section of the Statistics page provides a quick synopsis of partition status. listing host statistics for each sensor you selected. On the Defense Center. Version 4. The page reloads. Click the down arrow next to Disk Usage to expand it. If you are managing sensors with a Defense Center.Monitoring the System Monitoring System Status and Disk Space Usage Chapter 14 2. you can also list statistics for managed sensors. Click the down arrow next to Disk Usage to expand it. to view disk usage information for a specific sensor: Access: Maint/Admin 1. and click Select Devices. On the Defense Center.1 Sourcefire 3D System Administrator Guide 468 . You can monitor this page from time to time to ensure that enough disk space is available for system processes and the database. The Disk Usage section expands. From the Select Device(s) box and click Select Devices. 2. see Understanding Health Monitoring on page 483. Viewing System Process Status Requires: Any The Processes section of the Host Statistics page allows you to see the processes that are currently running on an appliance. For more information. The Disk Usage section expands. The Statistics page appears. you can use the Defense Center’s web interface to view the process status for any managed sensor.9. Select Operations > Monitoring > Statistics. The Statistics page is updated with statistics for the devices that you selected. Select the sensor name from the Select Device(s) box. You can use the Shift and Ctrl keys to select multiple devices at once. To access disk usage information: Access: Maint/Admin 1. 2. TIP! On the Defense Center you can also use the health monitor to monitor disk usage and alert on low disk space conditions.

process is paging • X . Process Status Column Pid Username Pri Nice Description The process ID number The name of the user or group running the process The process priority The nice value.process has a positive nice value • R .process is dead • Z . which indicates megabytes) The process state: • D . The Statistics page appears.1 Sourcefire 3D System Administrator Guide 469 .process is being traced or stopped • W .process is in sleep mode • T . Version 4. Select Operations > Monitoring > Statistics. Values range between -20 (highest priority) and 19 (lowest priority) The memory size used by the process (in kilobytes. which indicates megabytes) The amount of resident paging files in memory (in kilobytes.process has a negative nice value Time Cpu Command The amount of time (in hours:minutes:seconds) that the process has been running The percentage of CPU that the process is using The executable name of the process Size Res State To expand the process list: Access: Maint/Admin 1.Monitoring the System Viewing System Process Status Chapter 14 The Process Status table describes each column that appears in the process list.process is in uninterruptible sleep (usually Input/Output) • N . which is a value that indicates the scheduling priority of a process.process is runnable (on queue to run) • S .process is defunct • < .9. unless the value is followed by m. unless the value is followed by m.

the current time. the system load average.1 Sourcefire 3D System Administrator Guide 470 . listing general process status that includes the number and types of running tasks. see Understanding Running Processes on page 471. memory. CPU. indicating a higher priority) Nice values indicate the scheduled priority for system processes and can range between -20 (highest priority) and 19 (lowest priority).9. and swap information. • • • • • • • • • idle usage percentage total number of kilobytes in memory total number of used kilobytes in memory total number of free kilobytes in memory total number of buffered kilobytes in memory total number of kilobytes in swap total number of used kilobytes in swap total number of free kilobytes in swap total number of cached kilobytes in swap Mem lists the following memory usage information: Swap lists the following swap usage information: IMPORTANT! For more information about the types of processes that run on the appliance.Monitoring the System Viewing System Process Status Chapter 14 2. The process list expands. 3. Cpu(s) lists the following CPU usage information: • • • user process usage percentage system process usage percentage nice usage percentage (CPU usage of processes that have a negative nice value. Version 4. the current system uptime. On the Defense Center. select the device or devices you want to view process statistics for and click Select Devices. Click the down arrow next to Processes. and specific information about each running process.

System Daemons Daemon crond dhclient fpcollect httpd httpsd Description Manages the execution of scheduled commands (cron jobs) Manages dynamic host IP addressing Manages the collection of client and server fingerprints Manages the HTTP (Apache web server) process Manages the HTTPS (Apache web server with SSL) service. Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files. The process list collapses. and checks for working SSL and valid certificate authentication. See the following sections for more information: • • Understanding System Daemons on page 471 Understanding Executables and System Utilities on page 473 Understanding System Daemons Daemons continually run on an appliance. This table is not an exhaustive list of all processes that may run on an appliance. They ensure that services are available and spawn processes when required. Daemons always run.9. runs in the background to provide secure web access to the appliance Manages Linux kernel event notification messages Manages the interception and logging of Linux kernel messages Manages Linux kernel swap memory keventd klogd kswapd Version 4. and executable files are run when required.Monitoring the System Understanding Running Processes Chapter 14 To collapse the process list: Access: Maint/Admin Click the up arrow next to Processes. The System Daemons table lists daemons that you may see on the Process Status page and provides a brief description of their functionality.1 Sourcefire 3D System Administrator Guide 471 .

only seen if Checkpoint SAM support is enabled Manages remediation responses Forwards time synchronization messages to managed sensors Provides access to the sfmb message broker process running on a remote appliance.requires RNA) sftimeserviced (Defense Center only) sfmbservice (requires IPS) Description Manages the Linux kernel update process. using an sftunnel connection to the appliance. restarts the database daemon if an error occurs and logs runtime information to a file Manages data transmission Manages connections to third-party client applications that use the Event Streamer Provides the RPC service for remotely managing and configuring an appliance using an sftunnel connection to the appliance Manages Check Point OPSEC integration. starts required processes. between Defense Centers Listens for connections on incoming sockets and then invokes the correct executable (typically the Sourcefire message broker. in a high availability environment.1 Sourcefire 3D System Administrator Guide 472 . restarts any process that fails unexpectedly Manages reports Manages RNA reports Manages safe mode operation of the database. Currently used only by health monitoring to send health events and alerts from a 3D Sensor to a Defense Center or. sfmb) to handle the request sftroughd Version 4.9. which performs disk synchronization Manages Sourcefire 3D System database processes Manages the Network Time Protocol (NTP) process Manages all Sourcefire processes.Monitoring the System Understanding Running Processes Chapter 14 System Daemons (Continued) Daemon kupdated mysqld ntpd pm reportd rnareportd safe_mysqld SFDataCorrelator sfestreamer (Defense Center only) sfmgr sfreactd SFRemediateD (Defense Center only .

and the network map Utility that copies files Utility that lists the amount of free space on the appliance Utility that writes content to standard output Utility that searches files and folders for specified input.1 Sourcefire 3D System Administrator Guide 473 . System Executables and Utilities Executable awk bash cat chown chsh correlator (Defense Center only requires RNA) cp df echo egrep Description Utility that executes programs written in the awk programming language GNU Bourne-Again SHell Utility that reads files and writes content to standard output Utility that changes user and group file permissions Utility that changes the default login shell Analyzes binary files created by RNA to generate events. runs in the background to provide SSH access to the appliance Manages the system logging (syslog) process Understanding Executables and System Utilities There are a number of executables on the system that run when executed by other processes or through user action. The System Executables and Utilities table describes the executables that you may see on the Process Status page.Monitoring the System Understanding Running Processes Chapter 14 System Daemons (Continued) Daemon sftunnel sshd syslogd Description Provides the secure communication channel for all processes requiring communication with a remote appliance Manages the Secure Shell (SSH) process. flow data.9. supports extended set of regular expressions not supported in standard grep Version 4.

multiple instances may appear Indicates authentication certificate creation Indicates a perl process iptables-restore iptables-save kill killall ksh logger md5sum mv myisamchk mysql openssl perl Version 4.9. See Configuring the Access List for Your Appliance on page 325 for more information about access configuration. Ensures that the MAC address stays constant Handles access restriction based on changes made to the Access Configuration page.1 Sourcefire 3D System Administrator Guide 474 .Monitoring the System Understanding Running Processes Chapter 14 System Executables and Utilities (Continued) Executable find grep halt httpsdctl hwclock ifconfig iptables Description Utility that recursively searches directories for specified input Utility that searches files and directories for specified input Utility that stops the server Handles secure Apache Web processes Utility that allows access to the hardware clock Indicates the network configuration executable. Handles iptables file restoration Handles saved changes to the iptables Utility that can be used to end a session and process Utility that can be used to end all sessions and processes Public domain version of the Korn shell Utility that provides a way to access the syslog daemon from the command line Utility that prints checksums and block counts for specified files Utility that moves (renames) files Indicates database table checking and repairing Indicates a database process.

which allows users other than root to run executables Utility that displays information about the top CPU processes Utility that can be used to change the access and modification times of specified files sed sfheartbeat sfmb sfsnort (requires IPS) sh shutdown sleep smtpclient snmptrap ssh sudo top touch Version 4. decodes and performs session reassembly.9.1 Sourcefire 3D System Administrator Guide 475 .Monitoring the System Understanding Running Processes Chapter 14 System Executables and Utilities (Continued) Executable ps RNA (requires RNA) Description Utility that writes process information to standard output Captures packets. correlating acquired data with the RNA fingerprint database. indicating that the appliance is active. Indicates that Snort is running Public domain version of the Korn shell Utility that shuts down the appliance Utility that suspends a process for a specified number of seconds Mail client that handles email transmission when email event notification functionality is enabled Forwards SNMP trap data to the SNMP trap server specified when SNMP notification functionality is enabled Indicates a Secure Shell (SSH) connection to the appliance Indicates a sudo process. handles communication between Defense Centers and sensor. heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process. then generates binary files that the Data Correlator processes to generate the network map and to populate the database with events and flow data Utility used to edit one or more text files Identifies a heartbeat broadcast.

last week. and the percent of packets uninspected by Snort.9. These graphs can show statistics for the last hour.1 Sourcefire 3D System Administrator Guide 476 . The IPS page appears. The Defense Center version of the page is shown below. Graphs can be generated to reflect number of intrusion events per second. and byte counts on specified files Viewing IPS Performance Statistics Requires: IPS or DC/MDC + IPS The IPS performance statistics page allows you to generate graphs that depict performance statistics for IPS over a specific period of time. IPS performance statistics refer only to the data stored locally on the 3D Sensor. See the following sections for more information: • • Generating IPS Performance Statistics Graphs on page 476 Saving IPS Performance Statistics Graphs on page 478 Generating IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS You can generate graphs that depict performance statistics for a Defense Center or a 3D Sensor with IPS based on the number of events per second. last day. IMPORTANT! Because of the way traffic is processed on 3Dx800 sensors. Version 4. or average bytes per packet. word. megabits per second. To view the IPS performance statistics: Access: Maint/Admin Select Operations > Monitoring > Performance > IPS.Monitoring the System Viewing IPS Performance Statistics Chapter 14 System Executables and Utilities (Continued) Executable vim wc Description Utility used to edit text files Utility that performs line. or last month of operation. number of megabits per second. performance statistics for those sensors are under reported. average number of bytes per packet.

From the Select Device list. 3. Therefore. Version 4. The IPS page appears. The IPS Performance Statistics Graph Types table lists the available graph types. If you assign two detection resources to a detection engine that has two interface sets and each interface set is connected to a different network segment. select the type of graph you want to create. if you reload a graph quickly. select the detection engines whose data you want to view. The Defense Center version of the page is shown below. To generate IPS performance statistics graphs: Access: Maint/Admin 1.9.1 Sourcefire 3D System Administrator Guide 477 . From the Select Graph(s) list. It may also indicate that both segments have a drop rate of 50%. 2. Select Operations > Monitoring > Performance > IPS. IPS Performance Statistics Graph Types Graph Type Events/Sec Mbits/Sec Avg Bytes/Packet Percent Packets Dropped Output Displays a graph that represents the number of events that are generated on the sensor per second Displays a graph that represents the number of megabits of traffic that pass through the sensor per second Displays a graph that represents the average number of bytes included in each packet This graph depicts the average percentage of uninspected packets across all detection resources (instances of Snort) assigned to the selected detection engine. then an average of 50% may indicate that one segment has a 90% drop rate and the other has a 10% drop rate.Monitoring the System Viewing IPS Performance Statistics Chapter 14 New data is accumulated for statistics graphs every five minutes. The graph only represents the total % drop when there is a single detection resource assigned to a selected detection engine. the data may not change until the next five-minute increment occurs.

you can save the graph as a graphic file for later use. or last month. To save the graph: Access: Maint/Admin Right-click on the graph and follow the instructions for your browser to save the image. From the Select Time Range list. Viewing RNA Performance Statistics Requires: DC + RNA The RNA Performance page allows you to generate graphs that display RNA-related performance statistics over a specific period of time. select the time range you would like to use for the graph. displaying the information you specified. Saving IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS After you have generated an IPS performance statistics graph. Graphs can be generated to display: • • • • the number of events generated by the Data Correlator per second the number of megabits analyzed by the RNA process per second average number of bytes included in each packet analyzed by the RNA process the percentage of packets dropped by RNA Version 4.9. Click Graph. The graph appears. last week.Monitoring the System Viewing RNA Performance Statistics Chapter 14 4. 5.1 Sourcefire 3D System Administrator Guide 478 . You can choose from last hour. last day.

9. if you reload a graph quickly. See the following sections for more information: • • Generating RNA Performance Statistics Graphs on page 479 Saving RNA Performance Statistics Graphs on page 481 Generating RNA Performance Statistics Graphs Requires: DC + RNA You can generate graphs that display performance statistics for managed 3D Sensors with RNA. To access the RNA Performance page: Access: Maint/Admin Select Operations > Monitoring > Performance > RNA. The RNA page appears.1 Sourcefire 3D System Administrator Guide 479 . the data may not change until the next five-minute increment occurs. in thousands.Monitoring the System Viewing RNA Performance Statistics Chapter 14 • • the number of packets. last week. New data is accumulated for statistics graphs every five minutes. RNA Performance Statistics Graph Types Graph Type Processed Events/Sec Output Displays a graph that represents the number of events that the Data Correlator processes per second Displays a graph that represents the number of flows that the Data Correlator processes per second Displays a graph that represents the number of events that RNA generates per second Processed Flows/Sec Generated Events/Sec Version 4. The RNA Performance Statistics Graph Types table lists the available graph types. analyzed by the RNA process per second the number of established connections analyzed by the RNA process per second These graphs can show statistics for the last hour. last day. or last month of operation. Therefore.

Monitoring the System Viewing RNA Performance Statistics Chapter 14 RNA Performance Statistics Graph Types (Continued) Graph Type Mbits/Sec Output Displays a graph that represents the number of megabits of traffic that are analyzed by the RNA process per second Displays a graph that represents the average number of bytes included in each packet analyzed by the RNA process Displays a graph that represents the percentage of packets dropped by RNA Displays a graph that represents the number of packets analyzed by the RNA process per second. The RNA page appears. From the Select Time Range list. in thousands Displays a graph that represents the number of established connections observed by the RNA process per second Avg Bytes/Packet Percent Packets Dropped K Packets/Sec Syn/Ack/Sec To generate RNA performance statistics graphs: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 480 . select the time range you would like to use for the graph. last week. You can choose from last hour. or the detection engines that you want to include. select the Defense Center. From the Select Target list. Depending on whether you select a detection engine or a sensor. the managed 3D Sensors. or last month. 4. Select Operations > Monitoring > Performance > RNA. Version 4. From the Select Graph(s) list. TIP! You can select multiple graphs by holding down the Ctrl or Shift keys while clicking on the graph type. the Select Graph(s) list adjusts to display the available graphs. 2. last day. 3. select the type of graph you want to create.9.

Monitoring the System Viewing RNA Performance Statistics Chapter 14 5. Saving RNA Performance Statistics Graphs Requires: DC + RNA After you have generated an RNA performance statistics graph. you can save the graph as a graphic file for later use. displaying the information you specified. Version 4. Right-click on the graph and follow the instructions for your browser to save the image. If you selected multiple graphs. The graph appears.1 Sourcefire 3D System Administrator Guide 481 .9. To save the graph: Access: Maint/Admin 1. 2. Create an RNA performance statistic graph as described in Generating RNA Performance Statistics Graphs on page 479. Click Graph. each graph appears on the page.

you can view health status information for the entire system or for a particular appliance. SNMP or syslog alerting in response to health events. You can create one health policy for every appliance in your system.Using Health Monitoring Chapter 15 Administrator Guide The health monitor provides numerous tests for determining the health of an appliance from the Defense Center. You can use the health monitor to create a collection of tests. The tests in a health policy run automatically at the interval you configure. The health monitor collects health events based on the test conditions configured. referred to as a health policy. Fully customizable event views allow you to quickly and easily analyze the health status events gathered by the health monitor. or use one of the default health policies. You can also run all tests or a specific test on demand. See the following sections for more information: • • Understanding Health Monitoring on page 483 Configuring Health Policies on page 489 Version 4. and you can delete health policies that you no longer need. customize a health policy for the specific appliance where you plan to apply it. These event views allow you to search and view event data and to access other information that may be related to the events you are investigating. are scripts that test for criteria you specify. You can also import a health policy exported from another Defense Center. Optionally. You can modify a health policy by enabling or disabling tests or by changing test settings. The tests. You can also suppress messages from selected appliances by blacklisting them. and apply the health policy to one or more appliances. You can also generate troubleshooting files for an appliance if you are asked to do so by Support.9. At the Defense Center. you can also configure email. . referred to as health modules.1 Sourcefire 3D System Administrator Guide 482 .

then drill down into status details if needed. For example. You can use the health monitor to access health status information for the entire system or for a particular appliance.Using Health Monitoring Understanding Health Monitoring Chapter 15 • • Using the Health Monitor Blacklist on page 534 Configuring Health Monitor Alerts on page 539 Understanding Health Monitoring You can use the health monitor to check the status of critical functionality across your Sourcefire 3D System deployment. if you need to make sure an appliance never fails due to hardware overload. The Health Monitor page provides a visual summary of the status of all appliances on your system. you can open a table view of occurrences of a specific event. if you want to see all the occurrences of CPU usage with a certain percentage. or you can retrieve all the health events for that appliance. SNMP or syslog alerting in response to health . A health alert is an association between a standard alert and a health status level. you can set up an email alert. disk. Individual appliance health monitors let you drill down into health details for a specific appliance. From an individual appliance’s health monitor.1 Sourcefire 3D System Administrator Guide 483 . You can then create a health alert that triggers that email alert whenever CPU. you can search for the CPU usage module and enter the percentage value. Monitor the health of your entire Sourcefire 3D System through the Defense Center by applying health policies to each of the managed appliances and collecting the resulting health data at the Defense Center. For example. You can also view health events in the standard Sourcefire 3D System table view. so you can check status at a glance.9. You can set alerting thresholds to minimize the number of repeating alerts you receive. You can also search for specific health events. events. You can also configure email. Version 4. or memory usage reaches the Warning level you configure in the health policy applied to that appliance. Pie charts and status tables on the Health Monitor page visually represent the health status for monitored appliances.

When you create health policies. For more information on creating customized health policies. you have to apply a health policy to that appliance. see Modifying User Privileges and Options on page 306. which also monitors CPU.1 Sourcefire 3D System Administrator Guide 484 . You can also apply one of the five default health policies to each appliance. and memory usage. For more information on health policies and the health modules you can run to test system health. you can create a policy that monitors just the intrusion event rate and the IPS process. and traffic status.9.Using Health Monitoring Understanding Health Monitoring Chapter 15 Because health monitoring is an administrative activity. For example. If you want to monitor the health of a managed appliance. IMPORTANT! Except for the Defense Center. to monitor the health of a 3D Sensor with IPS. For details on applying policies. Version 4. the Data Correlator process. disk. only users with Admin access privileges can access system health data. Sourcefire 3D System appliances do not have health monitoring policies applied to them by default. The health monitor tracks a variety of health indicators to ensure that your Sourcefire 3D System hardware and software are working correctly. see Creating Health Policies on page 497. see Applying Health Policies on page 528. or you can apply the default policy. For more information on assigning user privileges. see the following topics: • • • Understanding Health Policies on page 484 Understanding Health Modules on page 485 Understanding Health Monitoring Configuration on page 489 Understanding Health Policies A health policy is a collection of health module settings you apply to an appliance to define the criteria that the Defense Center uses when checking the health of the appliance. you choose which tests to run to determine appliance health. For more information on available default health policies you can apply to an appliance. see Predefined Health Policies on page 490.

9. CPU Usage Card Reset Data Correlator Process Version 4. are scripts that test for the criteria you specify in a health policy. the alert level resets to Normal. This module checks that the CPU on the appliance is not overloaded and alerts when CPU usage exceeds the percentages configured for the module. Even if multiple restarts occur between tests. The restart counter does not count actual restarts.1 Sourcefire 3D System Administrator Guide 485 . which may indicate a problem with the process. Critical is reduced to Warning or Warning is reduced to Normal). and alerts when the number of restarts exceeds limits configured for the module. and alerts when a bypass occurs. but sets the module status to Critical for that test. the module resets the counter to zero. This module determines if the Data Correlator process (SFDataCorrelator) is restarting too often. the module adds one to the restart count. For more information on system daemons such as SFDataCorrelator. The status remains Critical until the module finds that the process is running. At that point. Health Modules Module Appliance Heartbeat Automatic Application Bypass Status CPU Temperature Description This module determines if an appliance heartbeat is being heard from the sensor and alerts based on the sensor heartbeat status. regardless of the limits set for the module. The available health modules are described in the Health Modules table. the module only increments the restart counter by one each time it checks. If the module finds that the process is not running at all. The alert level also lowers by one level (for example. The second time the module checks and no restarts have occurred since the last test. The first time the module checks and no restarts have occurred since the last test. see Understanding System Daemons on page 471. This module checks for network cards which have restarted due to hardware failure and alerts when a reset occurs. This module determines if a detection engine has been bypassed because it did not respond within the number of seconds set in the bypass threshold. If any restarts occur. This module determines if the CPU on the sensor is overheated and alerts when the temperature exceeds temperatures configured for the module.Using Health Monitoring Understanding Health Monitoring Chapter 15 Understanding Health Modules Health modules. The module checks if any restarts occurred during the period between tests. This module only runs on 3Dx800 sensors. the module sets status according to the restart counter value and the configured limits for the module. also sometimes referred to as health tests. it increments the restart counter by one.

which may indicate a problem with the process. If the module finds that the process is not running at all. The first time the module checks and no restarts have occurred since the last test. If any restarts occur. Disk Usage This module compares disk usage on the appliance to the limits configured for the module and alerts when usage exceeds the percentages configured for the module. The module checks if any restarts occurred during the period between tests. Event Stream Status This module compares the number of events per second to the limits configured for this module and alerts if the limits are exceeded. it increments the restart counter by one. This module only runs on Defense Centers. This module determines if hardware needs to be replaced on a 3Dx800 or 3D9900 sensor and alerts based on the hardware status. eStreamer Process Version 4. At that point. the module also reports on the status of hardware-related daemons. The status remains Critical until the module finds that the process is running. the module adds one to the restart count. This module only runs on Master Defense Centers. This module determines if the eStreamer process is restarting too often. If the Event Stream is zero. The second time the module checks and no restarts have occurred since the last test. This module only runs on Master Defense Centers. the module resets the counter to zero.1 Sourcefire 3D System Administrator Guide 486 . This module only runs on 3Dx800 sensors and 3D9900 sensors. the eStreamer process may be down or the Defense Center may not be sending events. This module only runs on 3Dx800 sensors. the alert level resets to Normal. On the 3D9900. Even if multiple restarts occur between tests.Using Health Monitoring Understanding Health Monitoring Chapter 15 Health Modules (Continued) Module Defense Center Status Description This module ensures that there are heartbeats from connected Defense Centers and alerts based on the Defense Center status. the module only increments the restart counter by one each time it checks. The restart counter does not count actual restarts. see Interpreting Hardware Alert Details for 3D9900 Sensors on page 560. and alerts when the number of restarts exceeds limits configured for the module. but sets the module status to Critical for that test.9. Critical is reduced to Warning or Warning is reduced to Normal). The alert level also lowers by one level (for example. regardless of the limits set for the module. the module sets status according to the restart counter value and the configured limits for the module. For more information on the details reported for 3D9900 sensors. Fan Alarm Hardware Alarms This module determines if fans need to be replaced on the sensor and alerts based on the fan status.

Using Health Monitoring Understanding Health Monitoring

Chapter 15

Health Modules (Continued) Module Health Monitor Process Description This module monitors the status of the health monitor itself and alerts if the number of minutes since the last health event received by the Defense Center exceeds the Warning or Critical limits. This module only runs on Defense Centers. IPS Event Rate This module compares the number of intrusion events per second to the limits configured for this module and alerts if the limits are exceeded. If the IPS Event Rate is zero, the IPS process may be down or the 3D Sensor may not be sending events. Select Analysis & Reporting > Event Summary > Intrusion Event Statistics to check if events are being received from the sensor. This module determines if the IPS process (snort) has been restarting too often, which may indicate a problem with the process, and alerts when the number of restarts exceeds the limits configured for the module. The IPS process (also known as snort) is the packet decoder on a 3D Sensor with that is licensed for IPS component. If the IPS process is down or has been restarting, the IPS Event Rate results may be inaccurate. The restart counter does not indicate the number of restarts. Instead, the module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. Link State Propagation MDC Event Service Memory Usage This module determines when a link in a paired inline interface set fails and triggers the link state propagation mode. This module monitors the health of the internal eStreamer process used to transmit events to the Master Defense Center from the Defense Center. This module compares memory usage on the appliance to the limits configured for the module and alerts when usage exceeds the levels configured for the module. This module monitors the application of PEP rules to interface sets on a 3D9900. If PEP rules cannot be applied to interfaces in an interface set, the module generates an alert.

IPS Process

PEP Status

Version 4.9.1

Sourcefire 3D System Administrator Guide

487

Using Health Monitoring Understanding Health Monitoring

Chapter 15

Health Modules (Continued) Module Power Supply Description This module determines if power supplies on the sensor require replacement and alerts based on the power supply status. This module only runs on the Series 2 DC3000, MDC3000, 3Dx800, 3D9900, 3D3500, 3D4500, and 3D6500 appliances. This module indicates whether a specified period of time has passed since any RNA events have been detected by a sensor. This module determines if sufficient RNA host licenses remain and alerts based on the warning level configured for the module. This module determines if the RNA process (rna) is restarting too often, which may indicate a problem with the process, and alerts based on the number of restarts configured for the module. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. Time Synchronization Status Traffic Status This module tracks the synchronization of a sensor clock that obtains time using NTP with the clock on the NTP server and alerts if the difference in the clocks is more than ten seconds. This module determines if the sensor currently collects traffic and alerts based on the traffic status.

RNA Event Status RNA Host License Limit RNA Process

Version 4.9.1

Sourcefire 3D System Administrator Guide

488

Using Health Monitoring Configuring Health Policies

Chapter 15

Understanding Health Monitoring Configuration
There are several steps to setting up health monitoring on your Sourcefire 3D System, as indicated in the following procedure: 1. Create health policies for your appliances. You can set up specific policies for each kind of appliance you have in your Sourcefire 3D System, enabling only the appropriate tests for that appliance. TIP! If you want to quickly enable health monitoring without customizing the monitoring behavior, you can apply one of the default policies provided for that purpose. For more information on setting up health policies, see Configuring Health Policies on page 489. 2. Apply a health policy to each appliance where you want to track health status. For information on the default health policies available for immediate application, see Predefined Health Policies on page 490. 3. Optionally, configure health monitor alerts. You can set up email, syslog, or SNMP alerts that trigger when the health status level reaches a particular severity level for specific health modules. For more information on setting up health monitor alerts, see Configuring Health Monitor Alerts on page 539. After you set up health monitoring on your system, you can view the health status at any time on the Health Monitor page or the Health Table Events View. For more information about viewing system health data, see the following topics: • • • Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555

Configuring Health Policies
A health policy contains configured health test criteria for several modules. You can control which health modules run against each of your appliances and configure the specific limits used in the tests run by each module. For more information on the health modules you can configure in a health policy, see Understanding Health Monitoring on page 483. You can create one health policy that can be applied to every appliance in your system, customize each health policy to the specific appliance where you plan to apply it, or use the default health policies provided for you. You can also import a health policy exported from another Defense Center.

Version 4.9.1

Sourcefire 3D System Administrator Guide

489

Using Health Monitoring Configuring Health Policies

Chapter 15

When you configure a health policy, you decide whether to enable each health module for that policy. You also select the criteria that control which health status each enabled module reports each time it assesses the health of a process. For more information on the default health policy, which is applied to the Defense Center and Master Defense Center automatically, see Default Health Policy on page 493. For more information, see the following topics: • • • • • Predefined Health Policies on page 490 Creating Health Policies on page 497 Applying Health Policies on page 528 Editing Health Policies on page 530 Deleting Health Policies on page 533

Predefined Health Policies
The Defense Center health monitor includes several default health policies to make it easier for you to quickly implement health monitoring for your appliances. The Default Health Policy is automatically applied to the Defense Center. To also monitor sensor health, you can push health policies to 3D Sensors. IMPORTANT! You cannot apply a health policy to RNA Software for Red Hat Linux or Crossbeam-based software sensors. For more information, see the following topics: • • • • • • • Default 3D Sensor Health Policy on page 491 Default 3Dx800 Health Policy on page 491 Suggested 3D9900 Health Policy on page 492 Default Health Policy on page 493 Default Intrusion Sensor Health Policy on page 495 Default IPS (3Dx800 only) Health Policy on page 495 Default RNA Sensor Health Policy on page 496

Version 4.9.1

Sourcefire 3D System Administrator Guide

490

Using Health Monitoring Configuring Health Policies

Chapter 15

Default 3D Sensor Health Policy
Use the Default 3D Sensor Health Policy to monitor health on any 3D Sensor. Enabled health modules for this policy are listed in the Enabled Health Modules: 3D Sensor Health Policy table. Enabled Health Modules: 3D Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage IPS Event Rate IPS Process Link State Propagation Memory Usage Power Supply RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Default 3Dx800 Health Policy
Use the Default 3Dx800 Health Policy to monitor health on 3Dx800 sensors. Enabled health modules for this policy are listed in the Enabled Health Modules: Default 3Dx800 Health Policy table. Note that the Hardware Alarm module should

Version 4.9.1

Sourcefire 3D System Administrator Guide

491

Using Health Monitoring Configuring Health Policies

Chapter 15

be used instead of the Power Supply module to monitor power supply health on the 3Dx800 sensor models. Enabled Health Modules: Default 3Dx800 Health Policy Module Automatic Application Bypass Status CPU Temperature Disk Usage Fan Alarm Hardware Alarms IPS Event Rate IPS Process Memory Usage RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring Disk Usage Monitoring on page 508 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Memory Usage Monitoring on page 520 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Suggested 3D9900 Health Policy
The Defense Center interface does not include a default health policy specifically for 3D9900 sensors. Sourcefire recommends that you start with the default 3D Sensor policy and enable the Hardware Alarms module. If the sensor will be running RNA, enable the RNA Process module as well. Health modules that should be enabled when creating a policy for this type of sensor are listed in the Suggested Health Modules: 3D9900 Health Policy table. Note that the CPU Usage module cannot be enabled when monitoring 3D9900

Version 4.9.1

Sourcefire 3D System Administrator Guide

492

Using Health Monitoring Configuring Health Policies

Chapter 15

sensor models. CPU usage for a 3D9900 may reach 100% during normal sensor operation, so the data provided by the module would generate misleading events. Suggested Health Modules: 3D9900 Health Policy Module Data Correlator Process Disk Usage Hardware Alarms IPS Event Rate IPS Process Link State Propagation Memory Usage PEP Status Power Supply RNA Process Traffic Status For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Default Health Policy
Use the Default Health Policy to monitor health on a Defense Center. Enabled health modules for this policy are listed in the Enabled Defense Center Health Modules - Default Health Policy table. Enabled Defense Center Health Modules - Default Health Policy Module Automatic Application Bypass Status Appliance Heartbeat For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Appliance Heartbeat Monitoring on page 501

Version 4.9.1

Sourcefire 3D System Administrator Guide

493

Using Health Monitoring Configuring Health Policies

Chapter 15

Enabled Defense Center Health Modules - Default Health Policy (Continued) Module Data Correlator Process Disk Usage Link State Propagation Memory Usage Time Synchronization Status Power Supply RNA Host License Limit For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Time Synchronization Monitoring on page 526 Configuring Power Supply Monitoring on page 522 Configuring RNA Host Usage Monitoring on page 524

Use the Default Health Policy to monitor health on a Master Defense Center. Enabled health modules for this policy are listed in the Enabled MDC Health Modules - Default Health Policy table. Enabled MDC Health Modules - Default Health Policy Module Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Memory Usage RNA Host License Limit For more information, see... Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Memory Usage Monitoring on page 520 Configuring RNA Host Usage Monitoring on page 524

Version 4.9.1

Sourcefire 3D System Administrator Guide

494

Using Health Monitoring Configuring Health Policies

Chapter 15

Default Intrusion Sensor Health Policy
Use the Default IPS Health Policy to monitor health on legacy Intrusion Sensors that you have not upgraded to Version 4.9.1. Enabled health modules for this policy are listed in the Enabled Health Modules: Default Intrusion Sensor Health Policy table. Enabled Health Modules: Default Intrusion Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage Health Monitor Process IPS Event Rate IPS Process Link State Propagation Memory Usage Power Supply Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Health Status Monitoring on page 514 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring Traffic Status Monitoring on page 527

Default IPS (3Dx800 only) Health Policy
Use the Default IPS (3Dx800 only) Health Policy to monitor IPS health on 3Dx800 sensors. Enabled health modules for this policy are listed in the Enabled Health Modules: Default IPS (3Dx800 only) Health Policy table. Note that the Hardware

Version 4.9.1

Sourcefire 3D System Administrator Guide

495

Using Health Monitoring Configuring Health Policies

Chapter 15

Alarm module should be used instead of the Power Supply module to monitor power supply health on the 3Dx800 sensor models. Enabled Health Modules: Default IPS (3Dx800 only) Health Policy Module Automatic Application Bypass Status CPU Temperature Data Correlator Process Disk Usage Fan Alarm Hardware Alarms IPS Event Rate IPS Process Memory Usage Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Memory Usage Monitoring on page 520 Configuring Traffic Status Monitoring on page 527

Default RNA Sensor Health Policy
Use the Default RNA Sensor Health Policy to monitor health on legacy RNA Sensors that you have not upgraded to Version 4.9.1. Enabled health modules for

Version 4.9.1

Sourcefire 3D System Administrator Guide

496

Using Health Monitoring Configuring Health Policies

Chapter 15

this policy are listed in the Enabled Health Modules: Default RNA Sensor Health Policy table. Enabled Health Modules: Default RNA Sensor Health Policy Module Automatic Application Bypass Status Data Correlator Process Disk Usage Link State Propagation Memory Usage Power Supply RNA Host License Limit RNA Process Traffic Status For more information, see... Configuring Automatic Application Bypass Monitoring on page 502 Configuring Data Correlator Process Monitoring on page 506 Configuring Disk Usage Monitoring on page 508 Configuring Link State Propagation Monitoring on page 518 Configuring Memory Usage Monitoring on page 520 Configuring Power Supply Monitoring on page 522 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Traffic Status Monitoring on page 527

Creating Health Policies
Requires: DC/MDC If you want to customize a health policy to use with your appliances, you can create a new policy. The settings in the policy initially populate with the settings from the health policy you select as a basis for the new policy. You can enable or disable modules within the policy and change the alerting criteria for each module as needed. TIP! Instead of creating a new policy, you can export a health policy from another Defense Center and then import it onto your Defense Center. You can then edit the imported policy to suit your needs before you apply it. For more information, see Importing and Exporting Objects on page 583. To create a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

497

Using Health Monitoring Configuring Health Policies

Chapter 15

2. On the toolbar, click Health Policy. The Health Policy page appears.

3. Click Create Policy to create a new policy. The Create Health Policy page appears.

4. Select the existing policy that you want to use as the basis for the new policy from the Copy Policy drop-down list. 5. Enter a name for the policy. 6. Enter a description for the policy.

Version 4.9.1

Sourcefire 3D System Administrator Guide

498

9. Select Save to save the policy information. including a list of the modules. as described in the following sections: • • • • • • • • • • • • Configuring Policy Run Time Intervals on page 500 Configuring Appliance Heartbeat Monitoring on page 501 Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring CPU Usage Monitoring on page 504 Configuring Card Reset Monitoring on page 505 Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Fan Monitoring on page 512 Version 4.Using Health Monitoring Configuring Health Policies Chapter 15 7.1 Sourcefire 3D System Administrator Guide 499 . The Health Policy Configuration page appears. Configure settings on each module you want to use to test the health status of your appliances. 8.

9. Version 4. Disabled modules do not produce health status feedback. On the Health Policy Configuration page. select Policy Run Time Interval. even if the policy that contains the module has been applied to an appliance.Using Health Monitoring Configuring Health Policies Chapter 15 • • • • • • • • • • • • • • Configuring Hardware Monitoring on page 513 Configuring Health Status Monitoring on page 514 Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring MDC Event Service Monitoring on page 519 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Event Status Monitoring on page 523 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Time Synchronization Monitoring on page 526 Configuring Traffic Status Monitoring on page 527 IMPORTANT! Make sure you enable each module that you want to run to test the health status on each Health Policy Configuration page as you configure the settings. Configuring Policy Run Time Intervals Requires: DC/MDC You can control how often health tests run by modifying the Policy Run Time Interval for the health policy. WARNING! Do not set a run interval of less than five minutes. To configure a policy run time interval: Access: Maint/Admin 1. The Health Policy Configuration .1 Sourcefire 3D System Administrator Guide 500 . For more information on applying health policies. The maximum run time interval you can set is 99999 minutes. You must apply the policy to each appliance for it to take effect. see Applying Health Policies on page 528. Click Save to save the policy.Policy Run Time Interval page appears. 9.

select Appliance Heartbeat. In the Health Policy Configuration page.Using Health Monitoring Configuring Health Policies Chapter 15 2. Configuring Appliance Heartbeat Monitoring Requires: DC Supported Platforms: Defense Center The Defense Center receives heartbeats from its managed appliances once every two minutes or every 200 events. 2. If you click Save Policy and Exit when you are done. enter the time in minutes that you want to elapse between automatic repetitions of the test. To configure Appliance Heartbeat health module settings: Access: Maint/Admin 1. you discard all changes. If the Defense Center does not detect a heartbeat from a appliance. click Save Policy and Exit.9. The Health Policy Configuration . You have three options: • • • To save your changes to this module and return to the Health Policy page. To temporarily save your changes to this module and switch to another module’s settings to modify. To return to the Health Policy page without saving any of your settings for this module. Use the Appliance Heartbeat health status module to track whether the Defense Center receives heartbeats from managed appliances.Appliance Heartbeat page appears. Version 4.1 Sourcefire 3D System Administrator Guide 501 . That status data feeds into the health monitor. the status classification for this module changes to Critical. 3. if you click Cancel. whichever comes first. You must apply the health policy to the appropriate appliances if you want your settings to take effect. all changes you made will be saved. click Cancel. select the other module from the list at the left of the page. Select On for the Enabled option to enable use of the module for health status testing. See Applying Health Policies on page 528 for more information. as an indicator that the appliance is running and communicating properly with the Defense Center. In the Run Interval (mins) field.

all changes you made will be saved. select Automatic Application Bypass Status. You must apply the health policy to the appropriate appliances if you want your settings to take effect.1 Sourcefire 3D System Administrator Guide 502 . Select On for the Enabled option to enable use of the module for health status testing. If you click Save Policy and Exit when you are done. For more information on automatic application bypass. To temporarily save your changes to this module and switch to another module’s settings to modify. To return to the Health Policy page without saving any of your settings for this module. You have three options: • • • To save your changes to this module and return to the Health Policy page. if you click Cancel. see Automatic Application Bypass on page 212.9. To configure automatic application bypass monitoring status: Access: Maint/Admin 1. click Save Policy and Exit. 2. Version 4. you discard all changes. Configuring Automatic Application Bypass Monitoring Requires: DC/MDC Supported Platforms: 3D Sensors except 3D9900 Use this module to detect when a detection engine is bypassed because it did not respond within the number of seconds configured as the bypass threshold. That status data feeds into the health monitor. See Applying Health Policies on page 528 for more information. select the other module from the list at the left of the page.Using Health Monitoring Configuring Health Policies Chapter 15 3. In the Health Policy Configuration page. If a bypass occurs. this module generates an alert. The Automatic Application Bypass Status page appears. click Cancel.

the status classification for that module changes to Critical. That status data feeds into the health monitor. You have three options: • • • To save your changes to this module and return to the Health Policy page.9. To configure CPU temperature health module settings: Access: Maint/Admin 1. the Critical limit is set to 52 degrees Celsius and the Warning limit is set to 50 degrees Celsius. WARNING! Sourcefire recommends that you do not set the Critical limit higher than 65 degrees Celsius and that you do not set the Warning limit higher than 55 degrees Celsius. You must apply the health policy to the appropriate 3D Sensor if you want your settings to take effect. If you click Save Policy and Exit when you are done. the status classification for that module changes to Warning.Using Health Monitoring Configuring Health Policies Chapter 15 3. and the Critical limit must be greater than the Warning limit. If the CPU temperature on the monitored sensor exceeds the Warning limit. By default. To return to the Health Policy page without saving any of your settings for this module. Use the CPU Temperature health status module to set CPU temperature limits.CPU Temperature page appears. you discard all changes. click Cancel. select the other module from the list at the left of the page. Version 4. In the Health Policy Configuration page. click Save Policy and Exit. See Applying Health Policies on page 528 for more information. If the CPU temperature on the monitored sensor exceeds the Critical limit. To temporarily save your changes to this module and switch to another module’s settings to modify. select CPU Temperature. The Health Policy Configuration . Configuring CPU Temperature Monitoring Requires: DC/MDC Supported Platforms: 3Dx800 The temperature of the central processing unit (CPU) on your 3Dx800 sensor provides an important barometer for the health of your sensor.1 Sourcefire 3D System Administrator Guide 503 . if you click Cancel. The maximum temperature you can set for either limit is 100 degrees Celsius. all changes you made will be saved. Overheating a CPU can damage the processing unit.

To return to the Health Policy page without saving any of your settings for this module. that should trigger a warning health status. enter the number of degrees. If the CPU usage on the monitored appliance exceeds the Warning limit. in Celsius. click Save Policy and Exit. In the Warning Threshold Celsius field. 5. 4.Using Health Monitoring Configuring Health Policies Chapter 15 2.1 Sourcefire 3D System Administrator Guide 504 . all changes you made will be saved. If you click Save Policy and Exit when you are done. the status classification for that module changes to Critical. in Celsius. if you click Cancel. that should trigger a critical health status. See Applying Health Policies on page 528 for more information. Note that this module is not available for health policies applied to 3D9900 sensors. Configuring CPU Usage Monitoring Requires: DC/MDC Supported Platforms: All except 3D9900 Excessive CPU usage can indicate that you need to upgrade your hardware or that there are processes that are not functioning correctly. You must apply the health policy to the appropriate sensors if you want your settings to take effect. In the Critical Threshold Celsius field. Use the CPU Usage health status module to set CPU usage limits.9. You have three options: • • • To save your changes to this module and return to the Health Policy page. The maximum percentage you can set for either limit is 100 percent. and the Critical limit must be higher than the Warning limit. you discard all changes. If the CPU usage on the monitored appliance exceeds the Critical limit. click Cancel. 3. Version 4. the status classification for that module changes to Warning. select the other module from the list at the left of the page. Select On for the Enabled option to enable use of the module for health status testing. enter the number of degrees. That status data feeds into the health monitor. To temporarily save your changes to this module and switch to another module’s settings to modify.

3. If you click Save Policy and Exit when you are done. click Save Policy and Exit. if you click Cancel. If a reset occurs. enter the percentage of CPU usage that should trigger a critical health status. That status data feeds into the health monitor. You must apply the health policy to the appropriate appliances if you want your settings to take effect. On the Health Policy Configuration page. 4. You have three options: • • • To save your changes to this module and return to the Health Policy page. Version 4. Select On for the Enabled option to enable use of the module for health status testing. select CPU Usage. click Cancel.1 Sourcefire 3D System Administrator Guide 505 .Using Health Monitoring Configuring Health Policies Chapter 15 To configure CPU Usage health module settings: Access: Maint/Admin 1. select the other module from the list at the left of the page. In the Health Policy Configuration page. you discard all changes.9. See Applying Health Policies on page 528 for more information. enter the percentage of CPU usage that should trigger a warning health status. To return to the Health Policy page without saving any of your settings for this module. 5. In the Warning Threshold % field. To configure card reset monitoring: Access: Maint/Admin 1. To temporarily save your changes to this module and switch to another module’s settings to modify. 2. Configuring Card Reset Monitoring Requires: DC/MDC Supported Platforms: 3D500 . all changes you made will be saved. The Card Reset Monitoring page appears. this module generates an alert. In the Critical Threshold % field. select Card Reset. The Health Policy Configuration .3D6500 except 3Dx800 Use the card reset monitoring health status module to track when the network card restarts because of hardware failure.CPU Usage page appears.

but sets the module status to Critical for that test. the alert level resets to Normal. click Cancel. That status data feeds into the health monitor. To return to the Health Policy page without saving any of your settings for this module. At that point.9. and each time one or more restarts have occurred. If you click Save Policy and Exit when you are done. The module checks if any restarts occurred during the period between tests. The first time the module checks and no restarts have occurred since the last test. if you click Cancel. 3. Critical is reduced to Warning or Warning is reduced to Normal). The restart counter does not count actual restarts. Select On for the Enabled option to enable use of the module for health status testing. If the module finds that the process is not running at all. the module adds one to the restart count. The status remains Critical until the module finds that the process is running. Configuring Data Correlator Process Monitoring Requires: DC/MDC Supported Platforms: All The Data Correlator. Version 4. and each time one or more restarts have occurred. the status classification for that module changes to Warning. all changes you made will be saved. the status classification for that module changes to Critical. select the other module from the list at the left of the page. the module resets the counter to zero. it increments the restart counter by one. Use the Data Correlator Process health status module to set limits for the number of restarts that trigger a change in the health status. regardless of the limits set for the module. the module only increments the restart counter by one each time it checks. Even if multiple restarts occur between tests. If the module checks the Data Correlator process as many times as configured in the Warning Number of restarts limit. manages data transmission. the module sets status according to the restart counter value and the configured limits for the module. click Save Policy and Exit. short for the system daemon SFDataCorrelator. If the module checks the Data Correlator process as many times as configured in the Critical Number of restarts limit. The second time the module checks and no restarts have occurred since the last test.1 Sourcefire 3D System Administrator Guide 506 . To temporarily save your changes to this module and switch to another module’s settings to modify. you discard all changes. You have three options: • • • To save your changes to this module and return to the Health Policy page. See Applying Health Policies on page 528 for more information. You must apply the health policy to the appropriate Defense Center if you want your settings to take effect.Using Health Monitoring Configuring Health Policies Chapter 15 2. The alert level also lowers by one level (for example. If any restarts occur.

enter the number of process restarts that should trigger a warning health status. To configure Data Correlator Process health module settings: Access: Maint/Admin 1. You must apply the health policy to the appropriate appliances if you want your settings to take effect. 2. Version 4. Select On for the Enabled option to enable use of the module for health status testing. If a heartbeat is not obtained from the managed Defense Center or Defense Centers. select Data Correlator Process.Data Correlator Process page appears. To temporarily save your changes to this module and switch to another module’s settings to modify. In the Critical Number of restarts field. To return to the Health Policy page without saving any of your settings for this module. Configuring Defense Center Status Requires: MDC Supported Platforms: Master Defense Center Use the Defense Center Status health status module to monitor the status of a Defense Center or Defense Centers managed by the Master Defense Center where the health policy is applied. That status data feeds into the health monitor. 4. 5. this module generates an alert. select the other module from the list at the left of the page. enter the number of process restarts that should trigger a critical health status. In the Warning Number of restarts field. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page.9.1 Sourcefire 3D System Administrator Guide 507 . The Health Policy Configuration . and the Critical limit must be higher than the Warning limit. you discard all changes. See Applying Health Policies on page 528 for more information. if you click Cancel. If you click Save Policy and Exit when you are done.Using Health Monitoring Configuring Health Policies Chapter 15 The maximum number of restarts you can set for either limit is 100. all changes you made will be saved. On the Health Policy Configuration page. click Save Policy and Exit. click Cancel.

If the disk usage on the monitored appliance exceeds the Warning limit. Version 4. Configuring Disk Usage Monitoring Requires: DC/MDC Supported Platforms: All Without sufficient disk space. If the disk usage on the monitored appliance exceeds the Critical limit. the size of the partition is static so the module does not alert on the boot partition. 3. That status data feeds into the health monitor. the status classification for that module changes to Warning. IMPORTANT! Although the disk usage module lists the /boot partition as a monitored partition. all changes you made will be saved. The maximum percentage you can set for either limit is 100 percent.Using Health Monitoring Configuring Health Policies Chapter 15 To configure Defense Center Status: Access: Maint/Admin 1. if you click Cancel. an appliance cannot run. The Defense Center Status page appears.9. click Save Policy and Exit. If you click Save Policy and Exit when you are done. The health monitor can identify low disk space conditions on your appliances before the space runs out. Use the Disk Usage health status module to set disk usage limits for the / and / volume partitions on the appliance. click Cancel. and the Critical limit must be higher than the Warning limit. select Defense Center Status. In the Health Policy Configuration page. select the other module from the list at the left of the page. Select On for the Enabled option to enable use of the module for health status testing.1 Sourcefire 3D System Administrator Guide 508 . you discard all changes. See Applying Health Policies on page 528 for more information. the status classification for that module changes to Critical. To return to the Health Policy page without saving any of your settings for this module. You have three options: • • • To save your changes to this module and return to the Health Policy page. To temporarily save your changes to this module and switch to another module’s settings to modify. You must apply the health policy to the appropriate Defense Center if you want your settings to take effect. 2.

4. enter the percentage of disk usage that should trigger a critical health status. If you click Save Policy and Exit when you are done. You have three options: • • • To save your changes to this module and return to the Health Policy page.Disk Usage page appears. The restart counter does not count actual restarts. 2.1 Sourcefire 3D System Administrator Guide 509 . 5. eStreamer. The Health Policy Configuration . all changes you made will be saved. short for the Sourcefire Event Streamer. you discard all changes. if you click Cancel. Even if multiple restarts occur between tests. Configuring eStreamer Process Monitoring Requires: DC/MDC Supported Platforms: Defense Center Use the eStreamer Process health status module to monitor the health of the eStreamer process on the Defense Center. If any restarts occur.Using Health Monitoring Configuring Health Policies Chapter 15 To configure Disk Usage health module settings: Access: Maint/Admin 1.9. Select On for the Enabled option to enable use of the module for health status testing. Version 4. In the Warning Threshold % field. The module checks if any restarts occurred during the period between tests. See Applying Health Policies on page 528 for more information. 3. the module adds one to the restart count. enter the percentage of disk usage that should trigger a warning health status. the module only increments the restart counter by one each time it checks. You can set limits for the number of restarts that trigger a change in the health status. click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module. To temporarily save your changes to this module and switch to another module’s settings to modify. allows you to stream Sourcefire 3D System intrusion and network discovery data from the Sourcefire Defense Center to an eStreamer client. select the other module from the list at the left of the page. select Disk Usage. In the Critical Threshold % field. On the Health Policy Configuration page. You must apply the health policy to the appropriate appliances if you want your settings to take effect. click Cancel.

The maximum number of restarts you can set for either limit is 100. the status classification for that module changes to Critical. The alert level also lowers by one level (for example. 4. On the Health Policy Configuration page. the status classification for that module changes to Warning. If the module checks the eStreamer process as many times as configured in the Warning Number of restarts limit. To configure eStreamer Process health module settings: Access: Maint/Admin 1. Version 4. The Health Policy Configuration .9. it increments the restart counter by one. The status remains Critical until the module finds that the process is running.eStreamer Process page appears. 3. Critical is reduced to Warning or Warning is reduced to Normal). but sets the module status to Critical for that test. the alert level resets to Normal. In the Critical Number of restarts field.1 Sourcefire 3D System Administrator Guide 510 . and each time one or more restarts have occurred. At that point. and the Critical limit must be higher than the Warning limit. enter the number of process restarts that should trigger a critical health status. That status data feeds into the health monitor. Select On for the Enabled option to enable use of the module for health status testing. The second time the module checks and no restarts have occurred since the last test.Using Health Monitoring Configuring Health Policies Chapter 15 The first time the module checks and no restarts have occurred since the last test. enter the number of process restarts that should trigger a warning health status. the module sets status according to the restart counter value and the configured limits for the module. the module resets the counter to zero. 2. select eStreamer Process. If the module finds that the process is not running at all. regardless of the limits set for the module. In the Warning Number of restarts field. and each time one or more restarts have occurred. If the module checks the eStreamer process as many times as configured in the Critical Number of restarts limit.

1 Sourcefire 3D System Administrator Guide 511 . In the Critical Seconds since last event field. click Cancel. the status classification for that module changes to Critical. You have three options: • • • To save your changes to this module and return to the Health Policy page. Configuring Event Stream Monitoring Requires: DC/MDC Supported Platforms: Master Defense Center Use the Event Stream Status module to monitor the health of the event stream process on a Defense Center by generating alerts when too many seconds elapse between events received by the Master Defense Center. To temporarily save your changes to this module and switch to another module’s settings to modify. You must apply the health policy to the appropriate appliances if you want your settings to take effect. See Applying Health Policies on page 528 for more information. before triggering a critical health status. In the Health Policy Configuration page. you discard all changes. 3. click Save Policy and Exit. That status data feeds into the health monitor. Select On for the Enabled option to enable use of the module for health status testing.9. and the Critical limit must be higher than the Warning limit. all changes you made will be saved. If the wait exceeds the number of seconds configured in the Warning Seconds since last event limit. select the other module from the list at the left of the page. The Health Policy Configuration . The minimum number of seconds is 300. If the wait exceeds the Critical Seconds since last event limit. If you click Save Policy and Exit when you are done. The maximum number of seconds you can set for either limit is 600. Version 4. To configure Event Stream Status health module settings: Access: Maint/Admin 1. To return to the Health Policy page without saving any of your settings for this module. in seconds. You can configure the elapsed duration between events. that causes an alert to be generated.Event Stream Status page appears. the status classification for that module changes to Warning. enter the maximum number of seconds to wait between events. if you click Cancel. select Event Stream Status. 2.Using Health Monitoring Configuring Health Policies Chapter 15 5.

5. 2.Fan Alarm monitor page appears. before triggering a warning health status. In the Warning Seconds since last event field. click Cancel.Using Health Monitoring Configuring Health Policies Chapter 15 4. all changes you made will be saved. That status data feeds into the health monitor. click Save Policy and Exit. In the Health Policy Configuration page.1 Sourcefire 3D System Administrator Guide 512 . To configure Fan Alarm health module settings: Access: Maint/Admin 1. select Fan Alarm.9. Select On for the Enabled option to enable use of the module for health status testing. select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done. enter the maximum number of seconds to wait between events. you discard all changes. To temporarily save your changes to this module and switch to another module’s settings to modify. You must apply the health policy to the Master Defense Center for your settings to take effect. Configuring Fan Monitoring Requires: DC/MDC Supported Platforms: 3Dx800 Use the Fan Alarm health status module to warn of fan failure on a 3Dx800 sensor. You have three options: • • • To save your changes to this module and return to the Health Policy page. Version 4. If the Fan Alarm module finds a fan that has failed. To return to the Health Policy page without saving any of your settings for this module. The Health Policy Configuration . See Applying Health Policies on page 528 for more information. if you click Cancel. the status classification for that module changes to Critical.

For more information on the hardware status conditions that can cause hardware alerts on 3D9900 sensors.Using Health Monitoring Configuring Health Policies Chapter 15 3. The Health Policy Configuration . click Save Policy and Exit. 3D9900 Use the Hardware Alarm health status module to detect hardware failure on a 3Dx800 or 3D9900 sensor. Select On for the Enabled option to enable use of the module for health status testing. To return to the Health Policy page without saving any of your settings for this module.9. That status data feeds into the health monitor. See Applying Health Policies on page 528 for more information. 2. if you click Cancel.Hardware Alarm monitor page appears. If you click Save Policy and Exit when you are done.1 Sourcefire 3D System Administrator Guide 513 . Note that the Hardware Alarm module can be used in addition to the Power Supply module to monitor power supply health on the 3Dx800 sensor models. You must apply the health policy to the appropriate sensors if you want your settings to take effect. Version 4. click Cancel. all changes you made will be saved. If the Hardware Alarm module finds a hardware component that has failed. To temporarily save your changes to this module and switch to another module’s settings to modify. select the other module from the list at the left of the page. Configuring Hardware Monitoring Requires: DC/MDC Supported Platforms: 3Dx800. you discard all changes. see Interpreting Hardware Alert Details for 3D9900 Sensors on page 560. You have three options: • • • To save your changes to this module and return to the Health Policy page. In the Health Policy Configuration page. To configure Hardware Alarm health module settings: Access: Maint/Admin 1. select Hardware Alarms. the status classification for that module changes to Critical.

The Health Monitor Process module then reports events that indicate how many minutes have elapsed since the last event was received from dogwood. 3.com.Using Health Monitoring Configuring Health Policies Chapter 15 3. all changes you made will be saved. the status classification for that module changes to Warning.9.1 Sourcefire 3D System Administrator Guide 514 . in minutes. if you click Cancel. click Cancel. The maximum number of minutes you can set for either limit is 144. In the Critical Minutes since last event field.example. You have three options: • • • To save your changes to this module and return to the Health Policy page. You must apply the health policy to the appropriate sensors if you want your settings to take effect. select the other module from the list at the left of the page. Configuring Health Status Monitoring Requires: DC/MDC Supported Platforms: Defense Center Use the Health Monitor Process module to monitor the health of the health monitor on a Defense Center by generating alerts when too many minutes elapse between health events received from monitored appliances. if a Defense Center (myrtle. that causes an alert to be generated. If the wait exceeds the Critical Minutes since last event limit. For example. If the wait exceeds the number of minutes configured in the Warning Minutes since last event limit.Health Monitor Process page appears. Select On for the Enabled option to enable use of the module for health status testing. Version 4.example. See Applying Health Policies on page 528 for more information.com. and the Critical limit must be higher than the Warning limit. you apply a health policy with the Health Monitor Process module enabled to myrtle.example. The Health Policy Configuration . The minimum number of minutes is 5. In the Health Policy Configuration page.example.com). before triggering a critical health status. 2. To temporarily save your changes to this module and switch to another module’s settings to modify. If you click Save Policy and Exit when you are done. That status data feeds into the health monitor. To configure Health Monitor Process module settings: Access: Maint/Admin 1. the status classification for that module changes to Critical. enter the maximum number of minutes to wait between events. select Health Monitor Process. To return to the Health Policy page without saving any of your settings for this module.com) monitors a sensor (dogwood. click Save Policy and Exit. you discard all changes. You can configure the elapsed duration between events.

9. the status classification for that module changes to Warning. you discard all changes. To temporarily save your changes to this module and switch to another module’s settings to modify.5 Events per second (Warning) = Events/Sec *1. enter the maximum number of minutes to wait between events. click Save Policy and Exit. If the event rate exceeds the number of events per second configured in the Events per second (Critical) limit. To determine limits for your system. and the Critical limit must be higher than the Warning limit. If the event rate for the IPS process on the monitored sensor exceeds the number of events per second configured in the Events per second (Warning) limit. You have three options: • • • To save your changes to this module and return to the Health Policy page. If you click Save Policy and Exit when you are done. Configuring IPS Event Rate Monitoring Requires: DC/MDC Supported Platforms: IPS Use the IPS Event Rate health status module to set limits for the number of packets per second that trigger a change in the health status. Typically. all changes you made will be saved. the event rate for a network segment averages 20 events per second. select the other module from the list at the left of the page. For a network segment with this average rate. Events per second (Critical) should be set to 50 and Events per second (Warning) should be set to 30. You must apply the health policy to the Defense Center for your settings to take effect. click Cancel. if you click Cancel. then calculate the limits using these formulas: • • Events per second (Critical) = Events/Sec * 2. See Applying Health Policies on page 528 for more information. the status classification for that module changes to Critical. before triggering a warning health status.5 The maximum number of events you can set for either limit is 999. 5. That status data feeds into the health monitor. Version 4. find the Events/Sec value on the Statistics page for your sensor (Operations > Monitoring > Statistics). In the Warning Minutes since last event field. To return to the Health Policy page without saving any of your settings for this module.1 Sourcefire 3D System Administrator Guide 515 .Using Health Monitoring Configuring Health Policies Chapter 15 4.

In the Events per second (Warning) field. The restart counter does not count actual restarts. 2. You must apply the health policy to the appropriate sensors if you want your settings to take effect.IPS Event Rate page appears. The Health Policy Configuration . You can configure how many restarts trigger a change in the health status for the process. To temporarily save your changes to this module and switch to another module’s settings to modify. enter the number of events per second that should trigger a warning health status.9. 4. select IPS Event Rate. Select On for the Enabled option to enable use of the module for health status testing. To return to the Health Policy page without saving any of your settings for this module. In the Events per second (Critical) field. See Applying Health Policies on page 528 for more information. enter the number of events per second that should trigger a critical health status. Use the IPS Process health status module to monitor the health of the IPS process on a sensor. If you click Save Policy and Exit when you are done. the module adds one to the restart count. if you click Cancel. click Cancel.Using Health Monitoring Configuring Health Policies Chapter 15 To configure IPS Event Rate Monitor health module settings: Access: Maint/Admin 1. click Save Policy and Exit. the module only increments the restart counter by one each time it checks. Even if multiple restarts occur between tests. select the other module from the list at the left of the page. If any restarts occur. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page. Configuring IPS Process Monitoring Requires: DC/MDC Supported Platforms: IPS The IPS process (also known as Snort) is the packet decoder on a 3D Sensor with the IPS component.1 Sourcefire 3D System Administrator Guide 516 . The first time the module checks and no restarts have occurred since the last test. all changes you made will be saved. The alert level also lowers by one level (for Version 4. the module resets the counter to zero. In the Health Policy Configuration page. 3. The module checks if any restarts occurred during the period between tests. you discard all changes.

That status data feeds into the health monitor. Critical is reduced to Warning or Warning is reduced to Normal). the alert level resets to Normal. but sets the module status to Critical for that test. The second time the module checks and no restarts have occurred since the last test. the status classification for that module changes to Warning. and each time one or more restarts have occurred. To configure IPS Process Monitor health module settings: Access: Maint/Admin 1. The maximum number of restarts you can set for either limit is 100. The status remains Critical until the module finds that the process is running. it increments the restart counter by one. At that point. In the Warning Number of restarts field. 4. Select On for the Enabled option to enable use of the module for health status testing. 3. If the module checks the IPS process as many times as configured in the Critical Number of restarts limit.Using Health Monitoring Configuring Health Policies Chapter 15 example. If the module finds that the process is not running at all. and the Critical limit must be higher than the Warning limit. The Health Policy Configuration . enter the number of process restarts that should trigger a critical health status. select IPS Process. Version 4. In the Critical Number of restarts field.9.IPS Process page appears. the module sets status according to the restart counter value and the configured limits for the module. If the module checks the IPS process as many times as configured in the Warning Number of restarts limit.1 Sourcefire 3D System Administrator Guide 517 . regardless of the limits set for the module. In the Health Policy Configuration page. the status classification for that module changes to Critical. and each time one or more restarts have occurred. 2. enter the number of process restarts that should trigger a warning health status.

the status classification for that module changes to Critical and the state reads: Module Link State Propagation: ethx_ethy is Triggered where x and y are the paired interface numbers. click Cancel. select Link State Propagation. all changes you made will be saved. you discard all changes. You have three options: • • • To save your changes to this module and return to the Health Policy page.Using Health Monitoring Configuring Health Policies Chapter 15 5. To configure Link State Propagation health module settings: Access: Maint/Admin 1. 2. To temporarily save your changes to this module and switch to another module’s settings to modify. click Save Policy and Exit. select the other module from the list at the left of the page. The Health Policy Configuration . You must apply the health policy to the appropriate sensors if you want your settings to take effect. if you click Cancel. See Applying Health Policies on page 528 for more information. Configuring Link State Propagation Monitoring Requires: DC/MDC Supported Platforms: IPS Use the Link State Propagation health status module to detect the interface link state propagation status on an inline interface pair. Version 4.1 Sourcefire 3D System Administrator Guide 518 . Select On for the Enabled option to enable use of the module for health status testing. If a link state propagates to the paired interface.9.Link State Propagation monitor page appears. To return to the Health Policy page without saving any of your settings for this module. If you click Save Policy and Exit when you are done. On the Health Policy Configuration page.

Using Health Monitoring Configuring Health Policies

Chapter 15

3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring MDC Event Service Monitoring
Requires: DC/MDC Supported Platforms: Defense Center Use the MDC health status module to monitor the health of the internal eStreamer process on the Defense Center that is used to transmit events to the Master Defense Center. You can set limits for the number of restarts that trigger a change in the health status. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. If the module checks the MDC event service as many times as configured in the Warning Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Warning. If the module checks the MDC event service as many times as configured in the Critical Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of restarts you can set for either limit is 100, and the Critical limit must be higher than the Warning limit.

Version 4.9.1

Sourcefire 3D System Administrator Guide

519

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure MDC Event Service health module settings: Access: Maint/Admin 1. On the Health Policy Configuration page, select MDC Event Service. The Health Policy Configuration - MDC Event Service Process page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Number of restarts field, enter the number of process restarts that should trigger a critical health status. 4. In the Warning Number of restarts field, enter the number of process restarts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate appliances if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Memory Usage Monitoring
Requires: DC/MDC Supported Platforms: All Use the Memory Usage health status module to set memory usage limits. The module calculates free memory by adding free memory and cached memory. If the memory usage on the monitored appliance exceeds the Warning limit, the status classification for that module changes to Warning. If the memory usage on the monitored appliance exceeds the Critical limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum percentage you can set for either limit is 100 percent, and the Critical limit must be higher than the Warning limit.

Version 4.9.1

Sourcefire 3D System Administrator Guide

520

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure Memory Usage health module settings: Access: Maint/Admin 1. On the Health Policy Configuration page, select Memory Usage. The Health Policy Configuration - Memory Usage page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Threshold % field, enter the percentage of memory usage that should trigger a critical health status. 4. In the Warning Threshold % field, enter the percentage of memory usage that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate appliances if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring PEP Status Monitoring
Requires: DC/MDC Supported Platforms: 3D9900 Use the PEP Status health status module to monitor the application of PEP rules to interface sets on a 3D9900. If PEP rules cannot be applied to interfaces in an interface set, this module generates an alert. That status data feeds into the health monitor.

Version 4.9.1

Sourcefire 3D System Administrator Guide

521

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure PEP Status health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select PEP Status. The Health Policy Configuration - PEP Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Power Supply Monitoring
Requires: DC/MDC Supported Platforms: Series 2 DC3000, MDC3000, 3D9900, 3Dx800, 3D3500, 3D4500, 3D6500 Use the Power Supply health status module to detect a power supply failure on a Series 2 DC3000, MDC3000, 3Dx800, 3D9900, 3D3500, 3D4500, or 3D6500 sensor. If the Power Supply module finds a power supply that has no power, the status classification for that module changes to No Power. If the module cannot detect the presence of the power supply, the status changes to Critical Error. That status data feeds into the health monitor. You can expand the Power Supply item on the Alert Detail list in the health monitor to see specific status items for each power supply. Note that the Hardware Alarm module can be used in addition to the Power Supply module to monitor power supply health on the 3Dx800 sensor models. To configure Power Supply health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Power Supply. The Health Policy Configuration - Power Supply monitor page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

522

Using Health Monitoring Configuring Health Policies

Chapter 15

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Event Status Monitoring
Requires: DC/MDC Supported Platforms: DC Use the RNA Event Status module to monitor the health of the RNA process on a sensor from the Defense Center by generating alerts when too many seconds elapse between RNA events received by the Defense Center. You can configure the elapsed duration between events, in seconds, that causes an alert to be generated. If the wait exceeds the number of seconds configured in the Warning Seconds since last event limit, the status classification for that module changes to Warning. If the wait exceeds the Critical Seconds since last event limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of seconds you can set for either limit is 7200, and the Critical limit must be higher than the Warning limit. The minimum number of seconds is 3600. Note that the RNA Health module was renamed to the RNA Event Status module in 4.9.1 and that the supported platforms changed from 3D Sensor to Defense Center in 4.9.1. To configure RNA Event Status module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Event Status. The Health Policy Configuration - RNA Event Status page appears.

Version 4.9.1

Sourcefire 3D System Administrator Guide

523

Using Health Monitoring Configuring Health Policies

Chapter 15

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Seconds since last event field, enter the maximum number of seconds to wait between events, before triggering a critical health status. 4. In the Warning Seconds since last event field, enter the maximum number of seconds to wait between events, before triggering a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the Defense Center for your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Host Usage Monitoring
Requires: DC/MDC Supported Platforms: RNA Use the RNA Host License Limit health status module to set RNA Host shortage limits. If the number of remaining RNA Hosts on the monitored sensor falls below the Warning Hosts limit, the status classification for that module changes to Warning. If the number of remaining RNA Hosts on the monitored sensor falls below the Critical Hosts limit, the status classification for that module changes to Critical. That status data feeds into the health monitor. The maximum number of hosts you can set for either limit is 999, and the Critical limit must be higher than the Warning limit. To configure RNA Host License Limit health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Host License Limit. The Health Policy Configuration - RNA Host License Limit page appears.

2. Select On for the Enabled option to enable use of the module for health status testing.

Version 4.9.1

Sourcefire 3D System Administrator Guide

524

Using Health Monitoring Configuring Health Policies

Chapter 15

3. In the Critical number Hosts field, enter the remaining number of available hosts that should trigger a critical health status. 4. In the Warning number Hosts field, enter the remaining number of available hosts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring RNA Process Monitoring
Requires: DC/MDC Supported Platforms: RNA Use the RNA Process health status module to set limits for the number of restarts that trigger a change in the health status. The restart counter does not count actual restarts. The module checks if any restarts occurred during the period between tests. Even if multiple restarts occur between tests, the module only increments the restart counter by one each time it checks. If any restarts occur, the module adds one to the restart count. The first time the module checks and no restarts have occurred since the last test, the module resets the counter to zero. The alert level also lowers by one level (for example, Critical is reduced to Warning or Warning is reduced to Normal). The second time the module checks and no restarts have occurred since the last test, the alert level resets to Normal. If the module finds that the process is not running at all, it increments the restart counter by one, but sets the module status to Critical for that test, regardless of the limits set for the module. The status remains Critical until the module finds that the process is running. At that point, the module sets status according to the restart counter value and the configured limits for the module. If the module checks the RNA process as many times as configured in the Warning Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Warning. If the module checks the RNA process as many times as configured in the Critical Number of restarts limit, and each time one or more restarts have occurred, the status classification for that module changes to Critical. That status data feeds into the health monitor.

Version 4.9.1

Sourcefire 3D System Administrator Guide

525

Using Health Monitoring Configuring Health Policies

Chapter 15

The maximum number of restarts you can set for either limit is 100, and the Critical limit must be higher than the Warning limit. To configure RNA Process health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select RNA Process. The Health Policy Configuration - RNA Process page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. In the Critical Number of restarts field, enter the number of process restarts that should trigger a critical health status. 4. In the Warning Number of restarts field, enter the number of process restarts that should trigger a warning health status. 5. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Time Synchronization Monitoring
Requires: DC/MDC Supported Platforms: Defense Center Use the Time Synchronization Status module to detect when the time on a managed sensor that uses NTP to obtain time from an NTP server differs by 10 seconds or more from the time on the server.

Version 4.9.1

Sourcefire 3D System Administrator Guide

526

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure time synchronization monitoring settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Time Synchronization Status. The Health Policy Configuration - Time Synchronization Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Configuring Traffic Status Monitoring
Requires: DC/MDC Supported Platforms: IPS, RNA Use the Traffic Status health status module to detect whether a sensor receives traffic. If the Traffic Status module determines that a sensor does not receive traffic, the status classification for that module changes to Critical. That status data feeds into the health monitor. WARNING! If you enable the Traffic Status module on a sensor where there are unused interfaces that are included in an interface set associated with a detection engine, the module interprets the idleness of the port as a traffic failure and alerts on traffic status. To prevent alerting on idle interfaces, remove those interfaces from all interface sets associated with detection engines. For more information on managing interface sets, see Editing an Interface Set on page 221.

Version 4.9.1

Sourcefire 3D System Administrator Guide

527

Using Health Monitoring Configuring Health Policies

Chapter 15

To configure Traffic Status health module settings: Access: Maint/Admin 1. In the Health Policy Configuration page, select Traffic Status. The Health Policy Configuration - Traffic Status monitor page appears.

2. Select On for the Enabled option to enable use of the module for health status testing. 3. You have three options: • • • To save your changes to this module and return to the Health Policy page, click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module, click Cancel. To temporarily save your changes to this module and switch to another module’s settings to modify, select the other module from the list at the left of the page. If you click Save Policy and Exit when you are done, all changes you made will be saved; if you click Cancel, you discard all changes.

You must apply the health policy to the appropriate sensors if you want your settings to take effect. See Applying Health Policies on page 528 for more information.

Applying Health Policies
Requires: DC/MDC When you apply a health policy to an appliance, the health tests for all the modules you enabled in the policy automatically monitor the health of the processes and hardware on the appliance. Health tests then continue to run at the intervals you configured in the policy, collecting health data for the appliance and forwarding that data to the Defense Center. If you enable a module in a health policy and then apply the policy to an appliance that does not require that health test, the health monitor reports the status for that health module as disabled. If you apply a policy with all modules disabled to an appliance, it removes all applied health policies from the appliance so no health policy is applied. When you apply a different policy to an appliance that already has a policy applied, expect some latency in the display of new data based on the newly applied tests. IMPORTANT! Default health policies are not replicated between Defense Centers in a high availability pair. Each appliance uses the local default health policy configured for that appliance.

Version 4.9.1

Sourcefire 3D System Administrator Guide

528

Using Health Monitoring Configuring Health Policies

Chapter 15

You cannot apply a health policy to RNA Software for Red Hat Linux. To apply a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears. 2. Click Health Policy in the health monitor toolbar. The Health Policy page appears.

3. Click Apply next to the policy you want to apply. The Health Policy Apply page appears.

TIP! The status icon next to the Health Policy column ( ) indicates the current health status for the appliance. The status icon next to the System Policy column ( ) indicates the communication status between the Defense Center and the sensor. Note that you can remove the currently applied policy by clicking the remove icon ( ).

4. Check the appliances where you want to apply the health policy. 5. Click Apply to apply the policy to the selected appliances. The Health Policy page appears, with a message indicating if the application of the policy was successful. Monitoring of the appliance starts as soon as the policy is successfully applied.

Version 4.9.1

Sourcefire 3D System Administrator Guide

529

Using Health Monitoring Configuring Health Policies

Chapter 15

To unapply a health policy: Access: Maint/Admin 1. Select Operations > Monitoring > Health. The Health Monitor page appears. 2. Click Health Policy in the health monitor toolbar. The Health Policy page appears.

3. Click Apply next to the policy you want to apply. The Health Policy Apply page appears.

4. You have two options: • • Apply a health policy with all modules disabled. Click the x next to the health policy.

Under Health Policy the status of None appears.

Editing Health Policies
Requires: DC/MDC You can modify a health policy by enabling or disabling modules or by changing module settings. If you modify a policy that is already applied to an appliance, the changes do not take effect until you reapply the policy.

Version 4.9.1

Sourcefire 3D System Administrator Guide

530

and 3D6500 Version 4.9. MDC3000. 3Dx800.1 Sourcefire 3D System Administrator Guide 531 . 3D4500. Health Modules Applicable to Appliances Module Appliance Heartbeat Automatic Application Bypass Status CPU Temperature CPU Usage Card Reset Data Correlator Process Defense Center Status Disk Usage eStreamer Process Event Stream Status Fan Alarm Hardware Alarms Health Monitor Process IPS Event Rate IPS Process Link State Propagation MDC Event Service Memory Usage PEP Status Power Supply Applicable Appliance Defense Center 3D Sensors. 3D3500.Using Health Monitoring Configuring Health Policies Chapter 15 Applicable health modules for various appliances are listed in the Health Modules Applicable to Appliances table. except 3D9900 3Dx800 Only All except 3D9900 All All Master Defense Center All Defense Center Master Defense Center 3Dx800 3Dx800 and 3D9900 Defense Center 3D Sensors with IPS 3D Sensors with IPS 3D Sensors with IPS Master Defense Center All 3D9900 Series 2 DC3000.

as described in the following sections: • • • • • • • • Configuring Policy Run Time Intervals on page 500 Configuring Appliance Heartbeat Monitoring on page 501 Configuring Automatic Application Bypass Monitoring on page 502 Configuring CPU Temperature Monitoring on page 503 Configuring CPU Usage Monitoring on page 504 Configuring Card Reset Monitoring on page 505 Configuring Data Correlator Process Monitoring on page 506 Configuring Defense Center Status on page 507 Version 4. Select Operations > Monitoring > Health. The Health Policy Configuration page appears.9.1 Sourcefire 3D System Administrator Guide 532 . Click Edit next to the policy you want to modify. 4. The Health Monitor page appears. Modify settings as needed.Using Health Monitoring Configuring Health Policies Chapter 15 Health Modules Applicable to Appliances (Continued) Module RNA Health RNA Host License Limit RNA Process Time Synchronization Status Traffic Status Applicable Appliance Defense Center Defense Center 3D Sensors with RNA Defense Center 3D Sensors with IPS. The Health Policy page appears. Click Health Policy in the health monitor toolbar. with the Policy Run Time Interval settings selected. 2. 3D Sensors with RNA To edit a health policy: Access: Maint/Admin 1. 3.

all changes you made will be saved. any health monitoring alerts in effect for the sensor remain active until you Version 4. click Cancel. if you delete a health policy that is applied to a sensor. select the other module from the list at the left of the page. If you delete a policy that is still applied to an appliance.1 Sourcefire 3D System Administrator Guide 533 . click Save Policy and Exit.9. the policy settings remain in effect until you apply a different policy. Deleting Health Policies Requires: DC/MDC You can delete health policies that you no longer need. 5. Reapply the policy to the appropriate appliances as described in Applying Health Policies on page 528. To return to the Health Policy page without saving any of your settings for this module. you discard all changes. if you click Cancel. You have three options: • • • 6. In addition. If you click Save Policy and Exit when you are done. To temporarily save your changes to this module and switch to another module’s settings to modify.Using Health Monitoring Configuring Health Policies Chapter 15 • • • • • • • • • • • • • • • • • • Configuring Disk Usage Monitoring on page 508 Configuring eStreamer Process Monitoring on page 509 Configuring Event Stream Monitoring on page 511 Configuring Fan Monitoring on page 512 Configuring Hardware Monitoring on page 513 Configuring Health Status Monitoring Configuring IPS Event Rate Monitoring on page 515 Configuring IPS Process Monitoring on page 516 Configuring Link State Propagation Monitoring on page 518 Configuring MDC Event Service Monitoring on page 519 Configuring Memory Usage Monitoring on page 520 Configuring PEP Status Monitoring on page 521 Configuring Power Supply Monitoring on page 522 Configuring RNA Event Status Monitoring on page 523 Configuring RNA Host Usage Monitoring on page 524 Configuring RNA Process Monitoring on page 525 Configuring Time Synchronization Monitoring on page 526 Configuring Traffic Status Monitoring on page 527 To save your changes to this module and return to the Health Policy page.

For more information on applying health policies. indicating if the deletion was successful. you disable appliances or make them temporarily unavailable. 3. Because those outages are deliberate. go to the Blacklist configuration page. see Creating Health Policies on page 497. The Health Policy page appears. Using the Health Monitor Blacklist In the course of normal network maintenance. After the setting takes effect the appliance no longer includes the appliance when calculating the overall health status. To delete a health policy: Access: Maint/Admin 1. The Health Monitor Appliance Status Summary lists the appliance as disabled. At times it may be more practical to just blacklist an individual health monitoring module on an appliance or detection engine. see Activating and Deactivating Alerts in the Analyst Guide. module. but they have a disabled status and do not affect the health status for the health monitor.9. and add an appliance to the blacklist. You can use the health monitor blacklist feature to disable health monitoring status reporting on an appliance. For example. When you disable health monitoring status. health events are still generated. Click Health Policy in the health monitor toolbar. TIP! To stop health monitoring for an appliance. A message appears. or detection engine from the blacklist. you can temporarily disable health monitoring for a 3D Sensor on that segment to prevent the health status on the Defense Center from displaying a warning or critical state because of the lapsed connection to the 3D Sensor. create a health policy with all modules disabled and apply it to the appliance.1 Sourcefire 3D System Administrator Guide 534 . module. when you run out of Version 4. the events that were generated during the blacklisting continue to show a status of disabled. Click Delete next to the policy you want to delete. see Applying Health Policies on page 528. For more information on creating health policies. The Health Monitor page appears. if you know that a segment of your network will be unavailable. you do not want the health status from those appliances to affect the summary health status on your Defense Center or Master Defense Center.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 deactivate the underlying associated alert. 2. If you remove the appliance. For example. or detection engine. Select Operations > Monitoring > Health. To temporarily disable health events from an appliance. For more information on deactivating alerts.

Health Monitor blacklist settings are system settings. then delete it and later re-register it with the Defense Center. If you need to disable the results of a group of appliances’ health monitoring. Make sure to remove all unused sensing interfaces from any interface sets in use by a detection engine so health monitoring alerts do not generate for those interfaces. the blacklist settings remain persistent. you can blacklist the RNA Host License Limit status messages until you install a new license with more hosts. you can blacklist a managed sensor on one HA peer and not the other. Select Operations > Monitoring > Health. 2. You cannot blacklist intrusion agents. You can also blacklist the HA peer to cause it to mark events generated by it and the sensors from which it receives health events as disabled. To blacklist an entire health policy or group of appliances: Access: Maint/Admin 1. not a Master Defense Center. The newly re-registered sensor remains blacklisted. Therefore if you blacklist a sensor. Once the blacklist settings take effect. Note that if your Defense Center is in a high availability configuration. TIP! You can blacklist 3D Sensors only from a Defense Center. Note that on the main Health Monitor page you can distinguish between appliances that are blacklisted if you expand to view the list of appliances with a particular status by clicking the arrow in that status row. A blacklist icon ( ) and a notation are visible once you expand the view for a blacklisted or partially blacklisted appliance. the appliances report a disabled status in the Appliance Status Summary. For more information on expanding that view. The Health Monitor page appears. Blacklisting Health Policies or Appliances Requires: DC/MDC If you want to set health events to disabled for all appliances with a particular health policy. Version 4. The Blacklist page appears.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 RNA host licenses on an appliance. On the toolbar. see Using the Health Monitor on page 545. click Blacklist. you can blacklist the policy. IMPORTANT! On a Defense Center. you can blacklist the group of appliances.9.1 Sourcefire 3D System Administrator Guide 535 .

The status icon next to the System Policy column ( ) indicates the communication status between the Defense Center and the sensor. sort the list by group. Once the blacklist settings take effect. or model. Note that you can remove the currently applied policy by clicking the remove icon ( ). sort the list by group. to blacklist all appliances associated with a manager. (On a Master Defense Center. 4. or policy category. The Health Monitor page appears. policy or model.) TIP! The status icon next to the Health Policy column ( ) indicates the current health status for the appliance. policy or model. select the category then click Apply. 2.1 Sourcefire 3D System Administrator Guide 536 . To blacklist an individual appliance: Access: Maint/Admin 1. Use the drop-down list on the right to sort the list by group. On the toolbar. manager. model. Use the drop-down list on the right to sort the list by appliance group.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 3. select the manager then click Apply. Groups on a Defense Center are 3D Sensors. policy. model.) Version 4. Blacklisting an Appliance If you need to set the events and health status for an individual appliance to disabled. Select Operations > Monitoring > Health. Groups on a Master Defense Center are appliances.9. manager. or by policy. now indicating the blacklisted state of the appliances. the appliance shows as disabled in the Health Monitor Appliance Module Summary and health events for the appliance have a status of disabled. To blacklist all appliances in a group. (On a Master Defense Center.) The page refreshes. The Blacklist page appears. (On a Master Defense Center. click Blacklist. you can blacklist the appliance. 3.

you can blacklist the Traffic Status module for that detection engine. the line for that module appears in boldface type in the Defense Center web interface. In addition. Note that modules that allow you to select a specific detection engine have an arrow next to the module. Defense Center Only Specific health policy modules operate for a Defense Center. When any part of a module is blacklisted. if you know you are going to disable the RNA detection engine on a sensor and do not want traffic status alerts to change the status for the sensor. only include the following modules: • • • • • • • • • Appliance Heartbeat CPU Usage Data Correlator Process Disk Usage eStreamer Process Health Monitor Process MDC Event Service Memory Usage Time Synchronization Status Version 4. then click Apply. Click Edit and see Blacklisting a Health Policy Module on page 537 to blacklist individual health policy modules. select and expand a category folder.9. you can blacklist that module for a specific detection engine. For example. select the box next to the appropriate appliance. When blacklisting modules for Defense Centers. To blacklist an individual appliance.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 4. Blacklisting a Health Policy Module Requires: DC/MDC You can blacklist individual health policy modules on appliances. For some modules. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical.1 Sourcefire 3D System Administrator Guide 537 . the interface indicates the following information in parentheses after each module with detection engines: number of blacklisted detection engines/maximum number of detection engines. The page refreshes then indicates the blacklisted state of the appliances.

2. only include the following modules: • • • • • • • CPU Usage Data Correlator Process Defense Center Status Disk Usage Event Stream Status Memory Usage Power Supply For details about applicable modules on all appliances. Make sure that you keep track of individually blacklisted modules so you can reactivate them when you need them. Version 4.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 • • Power Supply RNA Host License Limit Master Defense Center Only Specific health policy modules operate for a Master Defense Center. click Blacklist. TIP! Once the blacklist settings take effect.1 Sourcefire 3D System Administrator Guide 538 . To blacklist an individual health policy module: Access: Maint/Admin 1. You may miss necessary warning or critical messages if you accidentally leave a module disabled. see the Health Modules Applicable to Appliances table on page 531. On the toolbar. the appliance shows as Part Blacklisted or All Modules Blacklisted in the Blacklist page and in the Appliance Health Monitor Module Status Summary but only in expanded views on the main Appliance Status Summary page.9. When blacklisting modules for Master Defense Centers. Select Operations > Monitoring > Health. The Blacklist page appears. The Health Monitor page appears.

then select each detection engine for which you want to blacklist the module. The health policy modules appear.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 3.9. system log when the status changes for the modules in a health policy. Policy. then click Edit to display the list of health policy modules. Expand the detection engine list by clicking on the arrow next to modules with detection engine lists. or Model. Configuring Health Monitor Alerts You can set up alerts to notify you through email. Click Save. 4. You can associate an existing alert with health event levels to cause that alert to trigger when health events of a particular level occur.1 Sourcefire 3D System Administrator Guide 539 . 5. Sort by Group. Version 4. You have two options: • • Select each module that you want to blacklist. through SNMP or through the .

Enter the name of the Mail Relay Host. If you want to use email alerting. If you plan to use email alerting: • • • • • • Select Operations > System Policy. • • • Continue with Creating Health Monitor Alerts on page 540. you can send a second email when the hard drive reaches the critical level. Create email. You can use an existing alert or configure a new one specifically to report on system health. Click Save Policy and Exit. For more information on creating SNMP alerts. For more information Version 4. For more information on creating email alerts. In the policy. see the following topics: • • • • • Preparing to Create a Health Alert on page 540 Creating Health Monitor Alerts on page 540 Interpreting Health Monitor Alerts on page 542 Editing Health Monitor Alerts on page 543 Deleting Health Monitor Alerts on page 544 Preparing to Create a Health Alert Requires: DC/MDC If you want to create a health alert.9. Click Apply and apply the policy to the Defense Center where you plan to create the health alert. To prepare your system for alerting: Access: Admin 1. and an alert. you create an association between a severity level. click Email Notification. see Creating SNMP Alerts in the Analyst Guide. SNMP or syslog alerts you want to associate with health alerts: . If the hard drive continues to fill. see Creating Email Alerts in the Analyst Guide. you also need to set up your email relay host in your system policy and re-apply that policy.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 For example. a health module.1 Sourcefire 3D System Administrator Guide 540 . if you are concerned that your appliances may run out of hard disk space. For more information. 2. Create a new policy or click Edit next to an existing one. you can automatically send an email to a system administrator when the remaining disk space reaches the warning level. For more information on creating syslog alerts. you first need to create the underlying alert that you associate to the health alert. Creating Health Monitor Alerts Requires: DC/MDC When you create a health monitor alert. see Creating Syslog Alerts in the Analyst Guide.

the health monitor uses the threshold that generates the fewest alerts and ignores the others. The Health Monitor page appears. 2.9. 5. TIP! To select multiple modules.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 on creating the alert. you are notified of the conflict. The Health Monitor Alerts page appears. the associated alert triggers. select the severity level you want to use to trigger the alert.967 . From the Severity list. The timeout value for the threshold must be between 5 and 4. Note that if you create or update a threshold in a way that duplicates an existing threshold. Version 4. To create health monitor alerts: Access: Admin 1.1 Sourcefire 3D System Administrator Guide 541 . Type a name for the health alert in the Health Alert Name field. Select Operations > Monitoring > Health. From the Module list. When duplicate thresholds exist. Click Health Monitor Alerts in the health monitor toolbar. When the severity level occurs for the selected module. 3. see Preparing to Create a Health Alert on page 540.295 minutes. press Shift + Ctrl and click the module names. select the modules for which you want the alert to apply.294. 4.

which indicates the severity level of the alert. The health test results met the criteria to return to a normal alert status. see the Alert Severities table.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 6. For more information on health alert severity levels. For more information on creating alerts. For more information on health modules. From the Alert list. In the Threshold Timeout field. Click Save to save the health alert. see Creating Alerts in the Analyst Guide. see Understanding Health Modules on page 485. indicating if the alert configuration was successfully saved. The health test did not run. TIP! Click Alerts in the toolbar to open the Alerts page. type the number of minutes that should elapse before each threshold period ends and the threshold count resets. Interpreting Health Monitor Alerts The alerts generated by the health monitor contain the following information: • • • Severity. The health test results met the criteria to trigger a Normal alert status. Version 4.1 Sourcefire 3D System Administrator Guide 542 . select the alert which you want to trigger when the selected severity level is reached. Alert Severities Severity Critical Warning Normal Error Recovered Description The health test results met the criteria to trigger a Critical alert status. 7. A message appears. Module. which includes the health test results that triggered the alert. which specifies the health module whose test results triggered the alert. Description. The health test results met the criteria to trigger a Warning alert status. The Active Health Alerts list now includes the alert you created. following a Critical or Warning alert status. 8.9.

6. The Health Monitor page appears. For more information. Click Save to save the modified health alert. Modify settings as needed. see Creating Health Monitor Alerts on page 540. To edit health monitor alerts: Access: Admin 1. health module.1 Sourcefire 3D System Administrator Guide 543 . or alert associated with the health monitor alert. 5. Version 4. Click Health Monitor Alerts in the health monitor toolbar. 2. The Health Monitor Alerts page appears. A message appears.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 Editing Health Monitor Alerts Requires: DC/MDC You can edit existing health monitor alerts to change the severity level. 4. Select the alert you want to modify in the Active Health Alerts list. 3. indicating if the alert configuration was successfully saved. Select Operations > Monitoring > Health. Click Load to load the configured settings for the selected alert.9.

Click Health Monitor Alerts in the health monitor toolbar. The Health Monitor Alerts page appears. 4.9. For more information on deleting alerts. Select the alert you want to delete in the Active Health Alerts list. A message appears. You must deactivate or delete the underlying alert to ensure that alerting does not continue. IMPORTANT! Deleting a health monitor alert does not delete the associated alert. To delete health monitor alerts: Access: Admin 1. For more information on deactivating alerts. see Deleting Alerts in the Analyst Guide. indicating if the alert configuration was successfully deleted.1 Sourcefire 3D System Administrator Guide 544 . Click Delete. Version 4. 3. 2. Select Operations > Monitoring > Health.Using Health Monitoring Configuring Health Monitor Alerts Chapter 15 Deleting Health Monitor Alerts Requires: DC/MDC You can delete existing health monitor alerts. The Health Monitor page appears. see Activating and Deactivating Alerts in the Analyst Guide.

Administrators can create and apply a health policy to an appliance. The Status table provides a count of the managed appliances for this Defense Center by overall health status. see the following topics: • • • Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555 Using the Health Monitor Requires: DC/MDC The Health Monitor page provides the compiled health status for all sensors managed by the Defense Center.1 Sourcefire 3D System Administrator Guide 545 .9. indicating the percentage of appliances currently in each health status category. plus the Defense Center.Reviewing Health Status Chapter 16 Administrator Guide You can obtain information about the health of your Sourcefire 3D System through the Health Monitor. The Health Monitor then generates health events to indicate the current status of any aspects of appliance health that you chose to monitor. For more information on viewing the health status of your appliance. Version 4. The pie chart supplies another view of the health status breakdown.

9. TIP! If the arrow in the row for a status level points down. If the arrow points right. Select the appropriate status in the Status column of the table or the appropriate portion of the pie chart to the list appliances with that status. Click Health Monitor on the toolbar. 2. The following topics provide details on the tasks you can perform from the Health Monitor page: • • • • Interpreting Health Monitor Status on page 547 Using Appliance Health Monitors on page 547 Configuring Health Policies on page 489 Configuring Health Monitor Alerts on page 539 Version 4. the appliance list is hidden.1 Sourcefire 3D System Administrator Guide 546 .Reviewing Health Status Using the Health Monitor Chapter 16 To use the health monitor: Access: Maint/Admin/ Any Analyst except Restricted 1. The Health Monitor page appears. the appliance list for that status shows in the lower table.

Critical. Normal. Health Status Indicator Status Level Error Status Icon Status Color White Description Indicates that at least one health monitoring module has failed on the appliance and has not been successfully re-run since the failure occurred.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Interpreting Health Monitor Status Available status categories. Contact your technical support representative to obtain an update to the health monitoring module.1 Sourcefire 3D System Administrator Guide 547 . including modules that were in a Critical or Warning state. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. Version 4. or that the appliance is currently unreachable. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. include Error. Indicates that the critical limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. Warning. Indicates that warning limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. and Disabled. Indicates that an appliance is disabled or blacklisted. IMPORTANT! Your browser session will not be automatically timed out while you are viewing the Health Monitor page. Critical Red Warning Yellow Normal Green Recovered Green Disabled Blue Using Appliance Health Monitors Requires: DC/MDC The Appliance health monitor provides a detailed view of the health status of an appliance. by severity.9. as described in the Health Status Indicator table. that the appliance does not have a health policy applied to it.

Optionally. 4. TIP! If the arrow in the row for a status level points down. 3. click the color for the event status category you want to view. the appliance list is hidden. click the arrow in that status row. If the arrow points right.9. see the following sections: • • • Interpreting Appliance Health Monitor Status on page 549 Viewing Alerts by Status on page 549 Running All Modules for an Appliance on page 550 Version 4.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To view the status summary for a specific appliance: Access: Maint/Admin/ Any Analyst except Restricted 1. 2. The Health Monitor page appears. In the Appliance column of the appliance list.1 Sourcefire 3D System Administrator Guide 548 . click the name of the appliance for which you want to view details in the health monitor toolbar. Select Operations > Monitoring > Health. The Health Monitor Appliance page appears. in the Module Status Summary graph. For more information. The Alert Detail list toggles the display to show or hide events. To show the list of appliances with a particular status. the appliance list for that status shows in the lower table.

Normal. Appliance Health Status Indicator Status Level Error Status Icon Status Color White Description Indicates that the health monitoring module has failed and has not been successfully re-run since the failure occurred.9. by severity. Viewing Alerts by Status Requires: DC/MDC You can show or hide categories of alerts by status. include Error. Critical. Normal Green Indicates that the monitored item is running within the limits configured in the health policy applied to the appliance.1 Sourcefire 3D System Administrator Guide 549 . Contact your technical support representative to obtain an update to the health monitoring module. Version 4. as described in the Appliance Health Status Indicator table that follows. Disabled Blue Indicates that a module is disabled or blacklisted. that the appliance does not have a health policy applied to it. Indicates that the critical limits have been exceeded for the health module on the appliance and the problem has not been corrected. and Disabled.Reviewing Health Status Using Appliance Health Monitors Chapter 16 • • • Running a Specific Health Module on page 551 Generating Health Module Alert Graphs on page 553 Generating Appliance Troubleshooting Files on page 554 Interpreting Appliance Health Monitor Status Available status categories. or that the appliance is currently unreachable. Critical Red Warning Yellow Indicates that warning limits have been exceeded for the health module on the appliance and the problem has not been corrected. Warning. Recovered Green Indicates that the health for the monitored item is back within the limits configured in the health policy applied to the appliance.

To hide alerts by status: Access: Maint/Admin/ Any Analyst except Restricted Click the status icon or the color segment in the pie chart that corresponds to the health status of the alerts you want to view. the appliance list is hidden. Version 4. If the arrow points right. The alerts for that category appear in the Alert Detail list. To expand the appliance list to show appliances with a particular status.1 Sourcefire 3D System Administrator Guide 550 . you can also run all health module tests on demand to collect up-to-date health information for the appliance. the appliance list for that status shows in the lower table. However.9.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To show alerts by status: Access: Maint/Admin/ Any Analyst except Restricted Click the status icon or the color segment in the pie chart that corresponds to the health status of the alerts you want to view. Select Operations > Monitoring > Health. TIP! If the arrow in the row for a status level points down. Running All Modules for an Appliance Requires: DC/MDC Health module tests run automatically at the policy run time interval you configure when you create a health policy. The Health Monitor page appears. 2. To run all health modules for the appliance: Access: Maint/Admin/ Any Analyst except Restricted 1. click the arrow in that status row. The alerts in the Alert Detail list for that category disappear.

click the name of the appliance for which you want to view details in the health monitor toolbar. Click Run All Modules. If the value has not changed for a module that you just ran manually. wait a few seconds. Running a Specific Health Module Requires: DC/MDC Health module tests run automatically at the policy run time interval you configure when you create a health policy. The status bar indicates the progress of the tests. then refresh the page by clicking the sensor name. then the Health Monitor Appliance page refreshes. the first refresh that automatically occurs may not reflect the data from the manually-run tests. Version 4. 4.9. In the Appliance column of the appliance list.1 Sourcefire 3D System Administrator Guide 551 . You can also wait for the page to refresh again automatically. you can also run a health module test on demand to collect up-to-date health information for that module. However. IMPORTANT! When you manually run health modules.Reviewing Health Status Using Appliance Health Monitors Chapter 16 3. The Health Monitor Appliance page appears.

click the arrow in that status row. You can also wait for the page to refresh automatically again.9. The Alert Detail list expands to list the health alerts for the selected appliance for that status category. The Health Monitor Appliance page appears. click the color for the health alert status category you want to view. 3. the appliance list is hidden. In the Appliance column of the appliance list. In the Module Status Summary graph of the Health Monitor Appliance page. 2. click the name of the appliance for which you want to view details in the health monitor toolbar. Version 4. In the Alert Detail row for the alert for which you want to view a list of events.1 Sourcefire 3D System Administrator Guide 552 . the first refresh that automatically occurs may not reflect the data from the manually-run tests. TIP! If the arrow in the row for a status level points down. To expand the appliance list to show appliances with a particular status. then the Health Monitor Appliance page refreshes. then refresh the page by clicking the sensor name.Reviewing Health Status Using Appliance Health Monitors Chapter 16 To run a specific health module: Access: Maint/Admin/ Any Analyst except Restricted 1. The Health Monitor page appears. If the value has not changed for a module that you just manually ran. 4. the appliance list for that status shows in the lower table. The status bar indicates the progress of the test. If the arrow points right. wait a few seconds. click Run. IMPORTANT! When you manually run health modules. 5. Select Operations > Monitoring > Health.

Version 4. In the Module Status Summary graph of the Health Monitor Appliance page. 4. The Health Monitor page appears. the appliance list for that status shows in the lower table.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Generating Health Module Alert Graphs Requires: DC/MDC You can graph the results over a period of time of a particular health test for a specific appliance. 2. TIP! If the arrow in the row for a status level points down. To generate a health module alert graph: Access: Maint/Admin/ Any Analyst except Restricted 1. In the Appliance column of the appliance list. If the arrow points right. 3.9. To expand the appliance list to show appliances with a particular status.1 Sourcefire 3D System Administrator Guide 553 . The Alert Detail list expands to list the health alerts for the selected appliance for that status category. click the name of the appliance for which you want to view details in the health monitor toolbar. the appliance list is hidden. The Health Monitor Appliance page appears. Select Operations > Monitoring > Health. click the arrow in that status row. click the color for the health alert status category you want to view.

TIP! If no events appear. TIP! If the arrow in the row for a status level points down. Version 4. In the Alert Detail row for the alert for which you want to view a list of events. if you have a problem with your appliance. If the arrow points right.Reviewing Health Status Using Appliance Health Monitors Chapter 16 5. To expand the appliance list to show appliances with a particular status. 2. To generate appliance troubleshooting files: Access: Maint/Admin/ Any Analyst except Restricted 1. click Graph. Select Operations > Monitoring > Health. showing the status of the event over time. you may need to adjust the time range.1 Sourcefire 3D System Administrator Guide 554 . Sourcefire Support may ask you to generate troubleshooting files to help them diagnose the problem. click the arrow in that status row. See Setting Event Time Constraints in the Analyst Guide for more information. The Alert Detail section below the graph lists all health alerts for the selected appliance. the appliance list for that status shows in the lower table.9. The Health Monitor page appears. A graph appears. Generating Appliance Troubleshooting Files Requires: DC/MDC In some cases. the appliance list is hidden.

Version 4. 6. Click Generate Troubleshooting Files and confirm that you want to generate the files. click the name of the appliance for which you want to view details in the health monitor toolbar. you can view health events. Select Operations > Monitoring > Task Status. The Health Monitor Appliance page appears. 4. See Understanding Health Event Views on page 556 for more information about these common procedures.Reviewing Health Status Working with Health Events Chapter 16 3.1 Sourcefire 3D System Administrator Guide 555 . 5. Click the folder for the file generation job entry to expand the entry. Many functions that you can perform on the health event view pages are constant across all event view pages. Select Click to retrieve generated files. Working with Health Events The Defense Center provides fully customizable event views that allow you to quickly and easily analyze the health status events gathered by the health monitor.9. and can search for specific events. A File Download dialog box appears. These event views allow you to search and view event data and to easily access other information that may be related to the events you are investigating. Save the files to a location on your computer. In the Appliance column of the appliance list. The Task Status page appears. 8. From the Operations > Monitoring > Health menu. The file generation task is added to the task status queue. 9. 7. Send the generated files to technical support to assist in troubleshooting your system.

If you understand what conditions each health module tests for. see the following topics: • • • • Viewing All Health Events on page 556 Viewing Health Events by Module and Appliance on page 557 Working with the Health Events Table View on page 559 Searching for Health Events on page 563 Viewing All Health Events Requires: DC/MDC The Table View of Health Events page provides a list of all health events on the selected appliance. When you access health events from the Health Monitor page on your Defense Center. you can more effectively configure alerting for health events. see the following sections: • • • Viewing Health Events on page 556 Understanding the Health Events Table on page 561 Searching for Health Events on page 563 Viewing Health Events You can view the appliance health data collected by your health monitor in several ways. For a description of the health modules that generated the events that you may see on this page. see Understanding Health Modules on page 485. For more information.Reviewing Health Status Working with Health Events Chapter 16 See the following sections for more information about viewing events: • • • Understanding Health Event Views on page 556 describes the types of events that RNA generates.9. Viewing Health Events on page 556 describes how to access and use the Event View page.1 Sourcefire 3D System Administrator Guide 556 . For more information about viewing and searching for health events. Version 4. For more information on the different types of health modules that generate health events. which you can see on the Health Event View page. Understanding Health Event Views The Defense Center health monitor logs health events. Searching for Health Events on page 563 describes how to search for specific events using the Event Search page. see Understanding Health Modules on page 485. you retrieve all health events for all managed appliances.

the appliance list is hidden. For more information. If no events appear. In the toolbar. The Health Monitor page appears. Viewing Health Events by Module and Appliance Requires: DC/MDC You can query for events generated by a specific health module on a specific appliance. containing all health events.1 Sourcefire 3D System Administrator Guide 557 . click Health Events. you may need to adjust the time range. but you can then modify the time range to update the table with more recent information if needed.9. Select Operations > Monitoring > Health. To expand the appliance list to show appliances with a particular status.Reviewing Health Status Working with Health Events Chapter 16 To view all health events on all managed appliances: Access: Maint/Admin/ Any Analyst except Restricted 1. TIP! If the arrow in the row for a status level points down. The Health Monitor page appears. the appliance list for that status shows in the lower table. The bookmarked view retrieves events within the time range you are currently viewing. Version 4. see Setting Event Time Constraints in the Analyst Guide. Select Operations > Monitoring > Health. click the arrow in that status row. The Events page appears. To view the health events for a specific module: Access: Maint/Admin/ Any Analyst except Restricted 1. 2. TIP! You can bookmark this view to allow you to return to the page in the health events workflow containing the Health Events table of events. See Setting Event Time Constraints in the Analyst Guide for more information. 2. If the arrow points right.

Reviewing Health Status Working with Health Events Chapter 16 3.1 Sourcefire 3D System Administrator Guide 558 .9. 6. In the Module Status Summary graph of the Health Monitor Appliance page. Version 4. In the Alert Detail row for the alert for which you want to view a list of events. expand Search Constraints and click the Module Name constraint to remove it. 4. click the name of the appliance for which you want to view details in the health monitor toolbar. 5. The Health Monitor Appliance page appears. containing query results for a query with the name of the appliance and the name of the selected health alert module as constraints. you may need to adjust the time range. If you want to view all health events for the selected appliance. See Setting Event Time Constraints in the Analyst Guide for more information. The Health Events page appears. In the Appliance column of the appliance list. If no events appear. The Alert Detail list expands to list the health alerts for the selected appliance for that status category. click Events. click the color for the health alert status category you want to view.

Note that events that were generated outside the appliance's configured time window (whether global or event-specific) may appear in an event view if you constrain the event view by time...9. See Using Bookmarks in the Analyst Guide for more information. provide a name for the bookmark and click Save. or constrain the events that appear delete health events find more information in Sorting Drill-down Workflow Pages in the Analyst Guide. find more information in Navigating to Other Pages in the Workflow in the Analyst Guide. change what columns display in the table of events. click Bookmark This Page. See Using Bookmarks in the Analyst Guide for more information. sort the events that appear.. learn more about the contents of the columns that appear in the Health event view modify the time and date range for events listed in the Health table view You can. click Delete All.Reviewing Health Status Working with Health Events Chapter 16 Working with the Health Events Table View Requires: DC/MDC The Health Event View Functions table describes each action you can perform from the Event View page. find more information in Understanding the Health Events Table on page 561. See Generating Reports from Event Views on page 235 for more information. This can occur even if you configured a sliding time window for the appliance. then confirm you want to delete all the events. find more information in Setting Event Time Constraints in the Analyst Guide. navigate through event view pages navigate to other event tables to view associated events bookmark the current page so that you can quickly return to it navigate to the bookmark management page generate a report based on data in the table view Version 4. To delete all the events in the current constrained view. from any event view.1 Sourcefire 3D System Administrator Guide 559 . click View Bookmarks. click Report Designer. select the check box next to the events you want to delete and click Delete. Health Event View Functions To. select Analysis & Reporting > Bookmarks or. find more information in Navigating between Workflows in the Analyst Guide..

health status for the Hardware Alarms module changes to red and the message details include a reference to the NFE card presence. • If NFE temperature exceeds 99 degrees Fahrenheit. The triggering condition can be found in the message detail for the alert. view the details associated with a single health event view event details for multiple health events view event details for all events in the view view all events of a particular status Interpreting Hardware Alert Details for 3D9900 Sensors For 3D9900 sensor models. • If NFE temperature exceeds 89 degrees Fahrenheit.9. select the check box next to the rows that correspond with the events you want to view details for and then click View. health status for the Hardware Alarms module changes to red and the message details include a reference to the NFE temperature.1 Sourcefire 3D System Administrator Guide 560 .. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon.. select another health events workflow You can. NFE Platform daemon If the NFE Platform daemon goes down.. click the status icon in the Status column for an event with that status.. hardware alarms generate in response to the events described in the Conditions Monitored for 3D9900 Sensors table. NFE temperature Version 4. See Selecting Workflows in the Analyst Guide for more information. click Workflows or select from the Workflows dropdown list in the toolbar.Reviewing Health Status Working with Health Events Chapter 16 Health Event View Functions (Continued) To. Conditions Monitored for 3D9900 Sensors Condition Monitored NFE card presence Causes of Yellow or Red Error Conditions If NFE hardware is detected that is not valid for the appliance. health status for the Hardware Alarms module changes to yellow and the message details include a reference to the NFE temperature. click View All. click the down arrow link on the left side of the event.

health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the Ftwo daemon goes down. You create and apply health policies to your appliances. The Health Monitor modules you choose to enable Version 4. If the Rulesd daemon goes down. If the Load-Balancing Interface Module (LBIM) switch assembly is not present or not communicating.Reviewing Health Status Working with Health Events Chapter 16 Conditions Monitored for 3D9900 Sensors (Continued) Condition Monitored NFE Message daemon Causes of Yellow or Red Error Conditions If the NFE Message daemon goes down. If the Psls daemon goes down. If the NFE TCAM daemon goes down. If the Scmd daemon goes down. which monitor a variety of aspects. NFE TCAM daemon LBIM presence Scmd daemon Psls daemon Ftwo daemon Rulesd (host rules) daemon nfm_ipfragd (host frag) daemon Understanding the Health Events Table You can use the Defense Center’s health monitor to determine the status of critical functionality within the Sourcefire 3D System.9. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the nfm_ipfragd daemon goes down. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. health status for the Hardware Alarms module changes to yellow and the message details include a reference to the daemon. including hardware and software status. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon.1 Sourcefire 3D System Administrator Guide 561 . health status for the Hardware Alarms module changes to red and the message details include a reference to the LBIM presence.

the value could be a number from 80 to 100. Health Event Fields Field Module Name Description The name of the health module that generated the event. or Disabled) reported for the appliance. You can use the asterisk (*) to create wildcard searches. Yellow.1 Sourcefire 3D System Administrator Guide 562 . The name of the test. if the Defense Center generates a health event whenever a sensor it is monitoring is using 80 percent or more of its CPU resources. The timestamp for the health event. Version 4. the units is a percentage sign (%). When the health status meets criteria that you specify. Select Operations > Monitoring > Health. For example.9. Units The units descriptor for the result. see Monitoring the System on page 463. This is typically the same as the module name. if the Defense Center generates a health event when a sensor it is monitoring is using 80 percent or more of its CPU resources. The value (number of units) of the result obtained by the health test that generated the event. see the Health Modules table on page 485. The description of the health module that generated the event. a health event is generated. health events generated when a process was unable to execute are labeled Unable to Execute. Test Name Time Description Value To display the table view of health events: Access: Maint/Admin/ Any Analyst except Restricted 1. For more information on health monitoring. For example. For a list of health modules. Green. The Health Monitor page appears. For example. Status Sensor The status (Critical. The fields in the health events table are described in the Health Event Fields table. The appliance where the health event was reported.Reviewing Health Status Working with Health Events Chapter 16 in your health policy run various tests to determine appliance health status.

When creating new searches or modifying default searches. For example. The table view appears. TIP! If you are using a custom workflow that does not include the table view of health events. For information on working with health events. Searching for Health Events Requires: DC/MDC You can use Event Search to search for specific network discovery events. For example. click Health Events.1 Sourcefire 3D System Administrator Guide 563 . save. The search should retrieve applicable CPU Usage and CPU temperature events. click Health Events.9. You can create. see Working with Health Events on page 555. type CPU. On the Select Workflow page. you retrieve events where the appliance CPU was running at 15% utilization at the time the test ran. The Health Event Search Criteria table describes each search criterion you can specify. Value Version 4. You can use an asterisk (*) in this field to create wildcard searches. On the toolbar.Reviewing Health Status Working with Health Events Chapter 16 2. Specify the value (number of units) of the result obtained by the health test for the events you want to view. Health Event Search Criteria Search Field Module Name Description Specify the name of the module which generated the health events you want to view. if you specify a value of 15 and type CPU in the Units field. to view events that measure CPU performance. click Workflows. For example. Description Specify the description of the events you want to view. you could enter Unable to Execute to view any health events where a process was unable to execute. and re-use event searches. there are a number of options you can configure.

9. Status Specify the status for the health events that you want to view.Reviewing Health Status Working with Health Events Chapter 16 Health Event Search Criteria (Continued) Search Field Units Description Specify the units descriptor for the result obtained by the health test for the events you want to view. If you do not enter a name. To run and save health event searches: Access: Any Analyst except Restricted/ Admin 1. type Critical to retrieve all health events that indicate a critical status. one is created automatically when you save the search. enter a name for the search in the Name field. Version 4. Appliance Specify the name of appliance. See Health Event Search Criteria on page 563 for more information about the values you can enter for search criteria. For example. because the Disk Usage module has a “%” label in the Units field (and no additional text). if you want to save the search. Select Analysis & Reporting > Searches > Health Events. 2. Normal. For example.1 Sourcefire 3D System Administrator Guide 564 . The Search page appears. 3. Warning. if you type % in the Units field. you retrieve all events for the Disk Usage modules. if you type *% in the Units field. you retrieve all events for any modules that contain text followed by a “%” sign in the Units field. and Disabled. You can use an asterisk (*) in this field to create wildcard searches. Optionally. Error. Enter your search criteria. Valid status levels are Critical. However.

if you want to save the search so that other users can access it. Click Save as New Search to save the search criteria. Your search results appear in the default health events workflow. Loading a Saved Search in the Analyst Guide Deleting a Saved Search in the Analyst Guide For more information about searching. Otherwise. To use a different workflow. leave the check box selected to save the search as private. you must save it as a private search. disable the Save As Private check box. see the following sections: • • Version 4.1 Sourcefire 3D System Administrator Guide 565 . You have the following options: • Click Search to execute the search. 5. The search is saved and associated with your user account (if you selected Save As Private). constrained by the current time range. including a custom workflow.9. see Configuring Event View Settings on page 27. • • Click Save if you are modifying an existing search and want to save your changes. TIP! If you want to save a search as a restriction for restricted data users.Reviewing Health Status Working with Health Events Chapter 16 4. For information on specifying a different default workflow. so that you can run it at a later time. Optionally. use the Workflows menu on the toolbar.

Managing Audit Records Requires: DC/MDC or 3D Sensor Defense Centers and 3D Sensors log read-only auditing information for user activity. sort.9. which contains system status messages. Viewing the System Log on page 578 describes how to view the system log. For more information.Auditing the System Chapter 17 Administrator Guide You can audit activity on your system in two ways. Audit logs are presented in a standard event view that allows you to view.1 Sourcefire 3D System Administrator Guide 566 . Version 4. see Working with Event Reports on page 232. The appliances that are a part of the Sourcefire 3D System generate an audit record for each user interaction with the web interface. The following sections provide more information about the monitoring features that the system provides: • • Managing Audit Records on page 566 describes how to view and manage system audit information. TIP! Defense Centers and 3D Sensors with IPS also provide full-featured reporting features that allow you to generate reports for almost any type of data accessible in an event view. including auditing data. and also record system status messages in the system log. and filter audit log messages based on any item in the audit view. You can easily delete and report on audit information.

Auditing the System Managing Audit Records Chapter 17 The audit log stores a maximum of 100. The Audit Log Actions table below describes some of the specific actions you can perform on an audit log workflow page. the appliance prunes the oldest records from the database to reduce the number to 100.000. For information on creating a custom workflow. find more information at Setting Event Time Constraints in the Analyst Guide.. For more information. you can manipulate the view depending on the information you are looking for... sort and constrain events on the current workflow page navigate within the current workflow page find more information in Sorting Table View Pages and Changing Their Layout in the Analyst Guide. The predefined workflow includes a single table view of events. find more information in Understanding the Audit Log Table on page 574. learn more about the contents of the columns in the table modify the time range used when viewing audit records You can. Note that events that were generated outside the appliance's configured time window (whether global or event-specific) may appear in an event view if you constrain the event view by time.000. When the number of audit log entries exceeds 100. Audit Log Actions To. see Creating Custom Workflows in the Analyst Guide. Then. This can occur even if you configured a sliding time window for the appliance.1 Sourcefire 3D System Administrator Guide 567 .. see the following sections: • • • • Viewing Audit Records on page 567 Suppressing Audit Records on page 570 Understanding the Audit Log Table on page 574 Searching Audit Records on page 575 Viewing Audit Records Requires: DC/MDC or 3D Sensor You can use the appliance to view a table of audit records.9.000 entries. You can also create a custom workflow that displays only the information that matches your specific needs. Version 4. find more information in Navigating to Other Pages in the Workflow in the Analyst Guide.

• To drill down to the next workflow page keeping the current constraints. navigate between pages in the current workflow. If you click a value on a drilldown page. For more information..9. use one of the following methods: • To drill down to the next workflow page constraining on a specific value. Version 4. TIP! Table views always include “Table View“ in the page name.1 Sourcefire 3D System Administrator Guide 568 . For more information.. see Using Work