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

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

9. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account. and event viewing preferences. dashboard. such as the home page. • • • Components of the Sourcefire 3D System on page 15 provides descriptions of each of the components that may be in your Sourcefire 3D System. 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. • • • Version 4. time zone. 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. account password. Logging Out of the Appliance on page 24 explains how to log out of the web interface.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. 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.1 Sourcefire 3D System Administrator Guide 14 . Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface.

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. • • • • • • • • • 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. 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. listening to the network segments you specify. compliance white lists. IP Address Conventions on page 41 explains how the Sourcefire 3D System treats IP address ranges specified using Classless Inter-Domain Routing (CIDR) notation. 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. Documentation Conventions on page 38 explains typeface conventions used throughout the guide to convey specific types of information visually. You can set up compliance policies. and traffic profiles to protect your company’s infrastructure by monitoring network traffic for unusual patterns or behavior and automatically responding as needed. You must use a Defense Center to manage a 3D Sensor if it is running RNA.9. RNA monitors traffic on your network.1 Sourcefire 3D System Administrator Guide 15 . As RNA passively observes traffic. using information from detected packets to build a comprehensive map of the devices on the network.

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

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

9. but if you want to use RNA on the sensor. the Defense Center correlates threat. Key DC1000 database quantities are: • • • Intrusion Events . You can rack mount a DC1000 and collect data from a large number of 3D Sensors. Key DC500 database limits are: • • • Intrusion Events . 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. Version 4.500 thousand default and 2.1 million default and 10 million maximum RNA Flow Summaries .2 million default and 10 million maximum DC3000 You can use DC3000 Defense Centers in high-demand environments. If you deploy Real-time User-Awareness (RUA). 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 Flows . IMPORTANT! You cannot use DC500s in high availability configurations.1 million default and 10 million maximum RNA Flow Summaries . A DC3000 allows you to use higher database quantities. the Defense Center correlates intrusion events from IPS with host vulnerabilities from RNA and assigns impact flags to the intrusion events. attacks. 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. 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). you must manage the sensor with a Defense Center. You can configure a DC3000 as a Master Defense Center during the initial setup. You can use either DC1000s or DC3000s in high availability configurations.1 Sourcefire 3D System Administrator Guide 18 .5 million maximum RNA Flows . or network vulnerabilities.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 the IPS component includes its own local web interface. Impact correlation lets you focus in on attacks most likely to damage high priority hosts.2 million default and 10 million maximum DC1000 You can use DC1000 Defense Centers in most environments.

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

Version 4. 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. but allows you to request specific data from a Defense Center.1 Sourcefire 3D System Administrator Guide 20 . 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. 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. you could write a program to retrieve host criticality or vulnerability data from the Defense Center and add that information to your display.9.Introduction to the Sourcefire 3D System Components of the Sourcefire 3D System Chapter 1 assigns impact flags to the events. eStreamer You can access event data within your own applications through the eStreamer Application Programming Interface (API). eStreamer integration requires custom programming. you must use a Defense Center to manage it. IMPORTANT! Because the 3D Sensor Software for X-Series does not have a web interface. you display network host data within one of your network management applications. IMPORTANT! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. IMPORTANT! You must have a Defense Center in your Sourcefire 3D System deployment to use RNA for Red Hat Linux. for example. See the eStreamer Integration Guide for more information. Separate installation and configuration guides are available for the 3D Sensor Software for X-Series. 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. If. 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. See the Sourcefire RNA Software on Red Hat Linux Configuration Guide for more information.

you must log in using the admin user account.5. Browser Requirements Browser Firefox 3.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 . and Virtual 3D Sensors) do not have a web interface.0 Microsoft Internet Explorer 8.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. and analysis tasks. The initial setup process is described in Setting Up 3D Sensors on page 44. 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. you are presented with a more complete web interface that you can use to perform additional configuration and event analysis. RNA for Red Hat Linux.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. Note that 3Dx800 and software sensors (Crossbeam-based software sensors. make sure you allow the script to continue until it finishes.9. You can access the web interface by logging into the appliance using a web browser. Intrusion Agents.1 Sourcefire 3D System Administrator Guide 21 . The current version of the web interface supports the browsers listed in the following table. If you are the first user to log into the appliance after it is installed. Version 4. You must use the Defense Center’s web interface to manage these sensors. management. If your 3D Sensor is not licensed for IPS. If your 3D Sensor is licensed for IPS. If this occurs.

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

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

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

Specifying Your User Preferences Requires: Any Users can specify certain preferences for their user account. see Changing an Expired Password on page 26.1 Sourcefire 3D System Administrator Guide 25 . You can change your password at any time. After setting this value. you may have to change your password periodically. 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. you can view information about the last login session for the appliance.9. To log out of the appliance: Access: Any Click Logout on the toolbar. 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. event viewing preferences. Version 4. Last Successful Login Requires: Any The first time you visit the appliance home page during a web session.Introduction to the Sourcefire 3D System Last Successful Login Chapter 1 Note that your session automatically logs you out after 3.5 hours of inactivity. unless you are viewing a page (such as an unpaused dashboard) that periodically communicates with the web server on the appliance. month. and depending on the settings for your user account. and home page preferences. Configuring Event View Settings on page 27 describes how the event preferences affect what you see as you view events. Specifying Your Default Dashboard on page 35 explains how to choose which of the dashboards you want to use as your default dashboard. including passwords. Specifying Your Home Page on page 35 explains how to use one of the existing pages as your default home page. this is the first page you see upon logging into the appliance. You can see the following information about that user account last login: • • • day of the week. • • Changing Your Password Requires: Any All user accounts are protected with a password. 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.

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

In the toolbar. Click Save. click Preferences. see Event Preferences on page 27.9. For more information. 2. 5. Version 4. 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. Configure the default time window or windows. The User Preferences page appears. Your changes are implemented. 6. Click Event View Settings. see Default Time Windows on page 29. Configure the basic characteristics of event views.1 Sourcefire 3D System Administrator Guide 27 . 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. see Default Workflows on page 32. For more information. The Event View Settings page appears. 4. To configure event preferences: Access: Any 1. 3.

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

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

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

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

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

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

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

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

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

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

Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section.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. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure. Any DC Any appliance with any combination of licenses A DC500.9.1 Sourcefire 3D System Administrator Guide 38 . 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. Virtual Defense Center. 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. or DC3000 appliance used as a Defense Center Version 4. All platform information is formatted with an orange typeface. DC1000. Platform requirement information for specific aspects of a feature is provided where needed.

A “+” conjunction indicates that the platforms are required in combination. All access information is formatted with a green typeface.1 Sourcefire 3D System Administrator Guide 39 . 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. 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.9. In contrast. you can change an expired password on a Defense Center or Master Defense Center or on a 3D Sensor. so the Changing an Expired Password topic has a Requires statement of DC/MDC or 3D Sensor. so the Adding a Master Defense Center topic has a Requires statement of MDC + DC.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. For example. you need both a Defense Center and a Master Defense Center. to manage a Defense Center with a Master Defense Center.

The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin. Rule thresholding in the packet view provides an example of required combined access roles. For example. 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.9. to view the Hosts network map.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. A “+” conjunction indicates that the platforms are required in combination. 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.

0.048.168. the following table lists the private IPv4 address spaces in CIDR notation.168.0/16 IP Addresses in CIDR Block 10.0.1.16. 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. For example.2.255.0 10. if you type 10. Version 4.16.31.0.0.777 . the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.0.0 Number of IP Addresses 16. 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.1 Sourcefire 3D System Administrator Guide 41 .0 255.0 192.0.2.240. CIDR Notation Syntax Examples CIDR Block 10. For example.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.0/12 192.255.536 When you use CIDR notation to specify a range of IP addresses.255.0.576 65.255.3/8.0 255.255 192.3/8.216 1.255 172.255. without changing your user input. the Sourcefire 3D System uses only the masked portion of the network IP address you specified.0/8 172.0. 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.0.0.1.0 172. As a result.0.255 Subnet Mask 255. variables. but the web interface continues to display 10.0.168.9.0.0/8. the Sourcefire 3D System uses 10.0.

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

provide a rapid set up feature and a status page. Consult your original documentation or contact Sourcefire Support for information about performing the initial setup on those sensor models. see the Sourcefire 3D System Virtual Defense Center and 3D Sensor Installation Guide. 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. Newer models of the 3D Sensor.9. called Series 2 sensors. you may have a Series 1 3D Sensor. you are presented with a series of start-up pages. To perform the initial setup of a Virtual 3D Sensor. Version 4. What’s Next? on page 52 provides detailed lists of the next tasks to be performed by each type of user.1 Sourcefire 3D System Administrator Guide 43 .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. Note that if you purchased your sensor prior to 2008. Setting up Defense Centers on page 47 explains how to complete the setup process for Defense Centers.

TIP! The initial change to the admin user password changes the root password for the shell account. Defense Centers use the setup process in Setting up Defense Centers on page 47.9. Use the command line interface on the appliance for subsequent changes to the root password. in the New Password and Confirm fields. the Install page appears so that you can continue the setup process. and logging into the 3D Sensor’s web interface (as described in the 3D Sensor Installation Guide). 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. If the initial setup is interrupted or if a second user logs in while it is underway. Avoid using words that appear in a dictionary. To complete the initial setup: Access: Admin 1.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. After physically installing the 3D Sensor. Under Change Password. Version 4. The same password is used for both accounts. enter a new password for the admin user account and for the root password for the shell account. Series 2 sensors) provide a simple web form to collect information about your network environment and how you intend to deploy the sensor.1 Sourcefire 3D System Administrator Guide 44 . WARNING! Prepare for the initial setup and complete it promptly after you begin. Sourcefire strongly recommends that your password is at least eight alphanumeric characters of mixed case and includes at least one numeric character. setting up the IP address for the management interface. the results can be unpredictable.

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

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

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

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

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

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

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. Required Open Ports Ports 20.9. Refer to the Required Open Ports table for more information on functions and their associated ports. 80 162 389. 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. Open this port for communications between the Defense Center and Intrusion Agents. 21 22 23 25 53 67 68 . Notes Version 4. 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 .

Review the tasks in the following sections. which are based on the user account privileges required for the task.1 Sourcefire 3D System Administrator Guide 52 . For deployments that include a Defense Center. or 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.x 3D Sensors. Maintenance user. For standalone 3D Sensor deployments (that is.8. Requires: RNA. 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. you can perform much of the process on the Defense Center itself. Intrusion Event Analyst user. RNA. • 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. • • Version 4. Notes What’s Next? Requires: Any After you complete the initial setup for the Sourcefire 3D System. 4. See Managing Users on page 264 for more information about user roles. if your Defense Center or 3D Sensor must be licensed for IPS. or Requires: RUA.9. or RNA Event Analyst user) and what appliance you are using. Policy & Response Administrator user. a user with Administrator access must perform the first steps. deployments that do not include a Defense Center and do not use RNA). the task is preceded with Requires: IPS. Similarly. IMPORTANT! Tasks that must be completed on specific hardware or software platforms are indicated by special text: For example. tasks that require a Defense Center are preceded with Requires: DC. 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.

In most network environments. 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. Version 4. 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. but you cannot use high availability mode directly on the Master Defense Center itself.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. Requires: DC If you want to authenticate users using an external authentication server. 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. set up high availability as explained in Configuring High Availability on page 145. you should set it up now. 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.9. TIP! You can use high availabilty mode on Defense Centers which are managed by a Master Defense Center. 2. you must create an authentication object for that server as described in Creating LDAP Authentication Objects on page 269. 3. Administrator User Tasks Requires: Any Administrator users have a superset of tasks. the sensors you add to the primary Defense Center are automatically added to the secondary Defense Center. 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. TIP! After you set up management. Tasks essential to initial setup are listed below. Requires: DC If you are deploying two Defense Centers in high availability mode.1 Sourcefire 3D System Administrator Guide 53 . The first steps for the Administrator user are as follows: Access: Admin 1.

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

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

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

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

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

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

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

and so on.Using Dashboards Understanding Dashboard Widgets Chapter 3 different aspect of the Sourcefire 3D System. Widgets are grouped into three categories: • • • Analysis & Reporting widgets display data about the events collected and generated by the Sourcefire 3D System. that dashboard may contain unauthorized or invalid widgets. add and remove widgets from tabs. For more information. 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.1 Sourcefire 3D System Administrator Guide 61 . the Appliance Information widget is available on all appliances for all user roles. the Master Defense Center cannot access flow data.9. 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. Also note that widgets cannot display data to which an appliance has no access. Miscellaneous widgets display neither event data nor operations data. or RNA Event Analyst account privileges. 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. RUA events. For example. An unauthorized widget is one that you cannot view because you do not have the necessary 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. the widget displays an error message. each dashboard has a set of preferences that determines its behavior. In addition. Although you cannot add an unauthorized or invalid widget to a dashboard. if you import a dashboard created either on a different kind of appliance or by a user with different access privileges. while the Compliance Events widget is available only on the Defense Center for users with Administrator. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role. Operations widgets display information about the status and overall health of the Sourcefire 3D System. You can minimize and maximize widgets. Version 4. as well as rearrange the widgets on a tab.

For example. Note than any content generated in table format can be sorted by clicking on the table column header.Using Dashboards Understanding Dashboard Widgets Chapter 3 Similarly. but on Defense Centers and Master Defense Centers the widget displays only the status of the management interface. 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. The Sourcefire Appliances and Dashboard Widget Availability table lists the valid widgets for each appliance.9. keeping in mind that modifying a widget on a shared dashboard modifies it for all users of the appliance. For more information. An X indicates that the appliance can display the widget.1 Sourcefire 3D System Administrator Guide 62 . see Minimizing and Maximizing Widgets on page 97 and Deleting Widgets on page 97. the content of a widget can differ depending on the type of appliance you are using. the Current Interface Status widget on a 3D Sensor displays the status of its sensing interfaces. as well as widgets that display no data. You can delete or minimize unauthorized and invalid widgets.

An X indicates the user can view the widget.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. 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.1 Sourcefire 3D System Administrator Guide 63 . IMPORTANT! dashboards.9.

The preferences section for that widget appears. which is a highly customizable widget that allows you to display detailed information on the events collected and generated by the Sourcefire 3D System. Widget preferences can be simple.9. On the title bar of the widget whose preferences you want to change. the following graphic shows the preferences for the Current Interface Status widget.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. Version 4. Widget preferences can also be more complex. You can only configure the update frequency for this widget. the following graphic shows the preferences for the Custom Analysis widget. To modify a widget’s preferences: Access: Any except Restricted 1.1 Sourcefire 3D System Administrator Guide 64 . For example. which displays the current status of the network interfaces for the appliance. click the show preferences icon ( ). For example.

see Understanding the Predefined Widgets on page 65. 3. see Understanding Widget Availability on page 61. For information on the preferences you can specify for individual widgets. as well as information about the status and overall health of the appliances in your deployment. For more information. can provide you with at-a-glance views of current system status.Using Dashboards Understanding the Predefined Widgets Chapter 3 2.9. including data about the events collected and generated by the Sourcefire 3D System.1 Sourcefire 3D System Administrator Guide 65 . For detailed information on the widgets delivered with the Sourcefire 3D System. Version 4. ) to hide the Understanding the Predefined Widgets Requires: Any The Sourcefire 3D System is delivered with several predefined widgets that. On the widget title bar. 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. Your changes take effect immediately. Make changes as needed. when used on dashboards. click the hide preferences icon ( preferences section.

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. the name. model. the preferences also control how often the widget updates. and model of the appliance the versions of the Sourcefire 3D System software.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. For more information. operating system. The widget provides: • • the name. see Understanding Widget Preferences on page 64. module pack. and vulnerability database (VDB) installed on the appliance for managed appliances. the name and status of the communications link with the managing appliance for Defense Centers in a high availability pair. SEU. management interface IP address.1 Sourcefire 3D System Administrator Guide 66 .9. and Sourcefire 3D System software and operating system versions of the peer Defense Center. Snort. Version 4. rule pack.

see Using the Health Monitor on page 545. For more information. over the dashboard time range. Version 4.9. 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.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 must manually apply a health policy or their status appears as Disabled. The preferences also control how often the widget updates. Note that because the Defense Center does not automatically apply a health policy to managed sensors. see Understanding Widget Preferences on page 64.1 Sourcefire 3D System Administrator Guide 67 . For more information. You can configure the widget to display appliance status as a pie chart or in a table by modifying the widget preferences. Understanding the Compliance Events Widget Requires: DC/MDC The Compliance Events widget shows the average events per second by priority.

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

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

you can further constrain the widget using a saved search. aggregating by Unique OS tells you how many unique versions of each operating system are running on the same hosts (for example. For example. 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. how many unique versions of Linux. either one of the predefined searches delivered with your appliance or a custom search that you created. and so on). Microsoft Windows. Mac OS X.9.1 Sourcefire 3D System Administrator Guide 70 . On the other hand. constraining the first example (operating systems Version 4. Aggregating this data by Count tells you how many hosts are running each operating system. if you are using Sourcefire RNA as part of your deployment.Using Dashboards Understanding the Predefined Widgets Chapter 3 For example.

you can configure the Custom Analysis widget to display a line graph. if you set the dashboard time range to a year. A number indicating how many places the event has moved up appears next to the icon. the widget updates every five minutes. hover your pointer over the Last updated notice in the bottom left corner of the widget.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. you should read the bars from right to left. A number indicating how many places the event has moved down appears next to the icon. A downward-pointing icon indicates descending order. You can also configure the widget to display the most frequently occurring events or the least frequently occurring events. based on the local time of the appliance. If you want information on events or other collected data over time. You can change the color of the bars as well as the number of rows that the widget displays. The down-arrow icon ( ) indicates that the event has moved down in the standings since the last time the widget updated. an upwards-pointing icon indicates ascending order. The widget updates with a frequency that depends on the dashboard time range. To determine when the dashboard will update next. The up-arrow icon ( ) indicates that the event has moved up in the standings since the last time the widget updated. such as one that displays the total number of intrusion events generated in your deployment over 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.9. • The widget displays the last time it updated. click the icon. The colored bars in the widget background show the relative number of occurrences of each event. The direction icon ( ) indicates and controls the sort order of the display.1 Sourcefire 3D System Administrator Guide 71 . the widget updates once a week. if you set the dashboard time range to an hour. Next to each event. For example. To change the sort order. On the other hand.

show the preferences as described in Understanding Widget Preferences on page 64. IMPORTANT! Depending on how they are configured. For graphs over time. Custom Analysis widgets can place a drain on an appliance’s resources. you can choose the time zone that the widget uses as well as the color of the line.Using Dashboards Understanding the Predefined Widgets Chapter 3 time. or you configure the widget to show a graph over time (that is. workflows) that provide detailed information about the events displayed in the widget. Finally. 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. the Custom Analysis widget has preferences that determines its behavior. you can choose a custom title for the widget. you can invoke event views (that is. Version 4. a red-shaded Custom Analysis widget indicates that its use is harming system performance.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 a Custom Analysis widget. From Custom Analysis widgets.1 Sourcefire 3D System Administrator Guide 72 . For more information. a line graph). you should remove the widget. a bar graph).

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

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

Displays the most active services on your monitored network. Displays counts for the most frequently occurring intrusion events. 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. Displays the most active client applications on your monitored network. based on the number of flows where the host initiated the session. by application type. based on the number of detected flows.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset. by classification. Displays the most frequently occurring types of intrusion events. Displays the most active hosts on your monitored network.9.1 Sourcefire 3D System Administrator Guide 75 . 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. Displays the most active ports on your monitored network. by classification. where the packet was not dropped as part of the event. based on the number of flows where the host was the responder in the session. where the packet was dropped. (The predefined dashboards on the Master Defense Center and 3D Sensor do not include Custom Analysis widgets. based on the number of detected flows.

Displays the most common operating system. Displays a count of intrusion event requiring analysis. based on the number of intrusion events where the host was the targeted host in the flow that caused the event.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. Displays the most active hours of the day. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. 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.1 Sourcefire 3D System Administrator Guide 76 . Displays the most common RNA service vendors. Displays the most frequently occurring types of intrusion events.9. based on frequency of intrusion events. Displays the most active hosts on your monitored network. based on the number of intrusion events occurring on high criticality hosts. based on the number of hosts running each operating system within your network. based on event classification. Displays the most active hosts on your monitored network. based on the number of hosts on the network running services made by that vendor. over the dashboard time range.

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. based on the number of kilobytes per second of data transmitted by the hosts. Displays the most active hosts on your monitored network. based on the number of kilobytes per second of data transmitted by the service. Displays a graph of the total kilobytes of data transmitted on your monitored network over the dashboard time range. based on the total number of kilobytes of data received by the hosts where those users are logged in. Displays the most active responder ports on your monitored network. based on the number of kilobytes per second of data received by the hosts.1 Sourcefire 3D System Administrator Guide 77 . Displays the most active services on your monitored network. based on the number of kilobytes per second of data transmitted via the port. Displays the most active RUA users on your monitored network.9.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.

and the global time window changes to the dashboard time range. For example.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. you can invoke an event view (that is. As another example.1 Sourcefire 3D System Administrator Guide 78 . the events appear in the default workflow for that event type. 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. the events appear in the default health events workflow. For more information on time windows. Displays the number of unique intrusion event types associated with each impact flag level. and the health monitoring time window changes to the dashboard time range. the events appear in the default workflow for that event type. Displays the hosts with the most white list violations. constrained by the dashboard time range. When you invoke an event view from the dashbaord. This also changes the appropriate time window for the appliance. based on the number of unique intrusion events per targeted host. if you configure multiple time windows on your Defense Center and then access health events from a Custom Analysis widget. Version 4. a workflow) that provides detailed information about the events displayed in the widget. depending on how many time windows you have configured and on what type of event you are trying to view. if you configure a single time window and then access any type of event from the Custom Analysis widget.9. see Default Time Windows on page 29 and Specifying Time Constraints in Searches in the Analyst Guide.

• For information on working with specific event types. click the View All icon in the lower right corner of the widget to view all associated events.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. If you are configuring the widget on a shared dashboard. 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. click any event to view associated events constrained by the widget preferences. remember that not all users can view data of all event types. depending on the user’s account privileges. bar graphs). depending on how you configured the widget: • On widgets configured to show relative occurrences of events (that is. constrained by the widget preferences. Similarly. Intrusion Event Analysts cannot view RNA events. 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.1 Sourcefire 3D System Administrator Guide 79 . On widgets configured to show flow data over time. For Version 4. remember that not all appliances have access to data of all event types. as well as by that event.9. For example. if you are using a dashboard imported from another appliance.

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

see Understanding Widget Preferences on page 64. On the 3D Sensor. On 3D Sensors. Note that only 3D Sensors have interfaces other than the management interface. 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.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.9. the preferences also control whether the widget displays the traffic rate for unused interfaces (by default. For more information.1 Sourcefire 3D System Administrator Guide 81 . On the Defense Center and Master Defense Center. The widget preferences control how often the widget updates. or both. On the Defense Center and Master Defense Center. you can configure the widget to display intrusion events of different impacts by modifying the widget preferences. you cannot configure the widget to display Version 4. you must enable local event storage or the widget will not have any data to display. On the 3D Sensor. this includes statistics on intrusion events of different impacts. the widget only displays the traffic rate for interfaces that belong to an interface set). Note that for managed 3D Sensors. the widget can display statistics for dropped intrusion events. all intrusion events.

For more information.1 Sourcefire 3D System Administrator Guide 82 . 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). On either appliance. 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. see Understanding Widget Preferences on page 64. you can: • Requires: DC/MDC select one or more Event Flags check boxes to display separate graphs for events of specific impacts. By default.Using Dashboards Understanding the Predefined Widgets Chapter 3 intrusion events by impact. see Viewing Intrusion Events in the Analyst Guide. the widget displays a pie chart that shows the Version 4. you can display dropped events. In the widget preferences. regardless of impact or rule state.9. The following graphic shows the Defense Center version of the widget preferences. 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. For more information on intrusion events. accessing intrusion events via the dashboard changes the events (or global) time window for the appliance. On the Intrusion Events widget. select All to display an additional graph for all intrusion events.

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

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

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

or you can create a custom connection to any other RSS feed by specifying its URL in the widget preferences.Using Dashboards Understanding the Predefined Widgets Chapter 3 On the Product Updates widget. When you configure the widget. see Scheduling Tasks on page 425 • Understanding the RSS Feed Widget Requires: Any The RSS Feed widget adds an RSS feed to a dashboard. or VDB by clicking either the latest version or the Unknown link in the Latest column. 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. or VDB. the widget shows a feed of Sourcefire company news. SEU. By default. you can also choose how many stories from the feed you want to show in the widget. you can: • manually update an appliance by clicking the current version of the Sourcefire 3D System software. 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. You can also configure the widget to display a preconfigured feed of Sourcefire security news.9. 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. Version 4. as well as whether you want to show descriptions of the stories along with the headlines. SEU.1 Sourcefire 3D System Administrator Guide 86 . keep in mind that not all RSS feeds use descriptions.

both currently and over the dashboard time range. For more information. The preferences also control how often the widget updates. You can configure the widget to show or hide the load average by modifying the widget preferences. uptime. The preferences also control how often the widget synchronizes with the appliance’s clock.9. and boot time for the appliance. Understanding the System Time Widget Requires: Any The System Time widget shows the local system time. You can configure the widget to hide the boot time by modifying the widget preferences. and system load (also called the load average. For more information. 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). memory (RAM) usage. see Understanding Widget Preferences on page 64.1 Sourcefire 3D System Administrator Guide 87 .Using Dashboards Understanding the Predefined Widgets Chapter 3 On the RSS Feed widget. see Understanding Widget Preferences on page 64. Version 4. measured by the number of processes waiting to execute) on the appliance.

accessing white list events via the dashboard changes the events (or global) time window for the Defense Center. over the dashboard time range. For more information on white list events. In either case. You can click a graph to view white list events of a specific priority. 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. see Understanding Widget Preferences on page 64. including events that do not have a priority select Show All to display an additional graph for all white list events. the events are constrained by the dashboard time range. you can: • • • select one or more Priorities check boxes to display separate graphs for events of specific priorities. Version 4.9. In the widget preferences. For more information.1 Sourcefire 3D System Administrator Guide 88 . You can configure the widget to display white list events of different priorities by modifying the widget preferences.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. or click the All graph to view all white list events. see Viewing White List Events in the Analyst Guide.

modify. the user who created it) and whether a dashboard is private. Optionally. Note that. unless you have Admin access. individual widgets update according to their preferences. you can create a blank new dashboard by choosing not to base your dashboard on any pre-existing dashboards. For more information on working with dashboards.9. This makes a copy of the pre-existing dashboard. or on any user-defined dashboard. the page indicates the owner (that is. 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. You can create. You must also specify (or disable) the tab change and page refresh intervals. including the Sourcefire default dashboard. you can only see your own private dashboards. see Specifying Your Default Dashboard on page 35. or that you made to a private dashboard on another computer. you can modify this copy to suit your needs. Version 4. for example. view.1 Sourcefire 3D System Administrator Guide 89 . These settings determine how often the dashboard cycles through its tabs and how often the entire dashboard page refreshes. Then. you can make the changes at a local computer. for more information. you can choose to base it on any pre-existing dashboard. the page indicates which dashboard is the default. You specify the default dashboard in your user preferences. 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. you cannot view or modify private dashboards created by other users. Note that you do not need to refresh the entire dashboard to see data updates. Finally. If you want to make changes to the dashboard. export. since the last time the dashboard refreshed. 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. This can be useful. and delete dashboards.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). For each dashboard.

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

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

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

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

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

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

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

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

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

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

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. This saves you from having Version 4. you can use the Defense Center as a central point of management. Working with Sensors on page 113 describes how to establish and disable connections between sensors and your Defense Center. and change the state of managed sensors and how to reset management of a sensor.1 Sourcefire 3D System Administrator Guide 100 . The sections that follow explain some of the concepts you need to know as you plan your Sourcefire 3D System deployment. It also explains how to add. For example. Managing Sensor Groups on page 131 describes how to create sensor groups as well as how to add and remove sensors from groups. Working in NAT Environments on page 112 describes the principles of setting up the management of your sensors in Network Address Translation environments. • • • • • Management Concepts Requires: DC You can use a Defense Center to manage nearly every aspect of a sensor’s behavior. 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. delete. • • • • • 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. 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 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. Managing a Clustered Pair on page 140 describes how to create a clustered pair of 3D9900s and how to remove 3D9900s from clusters. First. Editing a Managed Sensor’s System Settings on page 133 describes the sensor attributes you can edit and explains how to edit them.9. Instead of managing each sensor using its own local web interface.

and those sensors view the same network traffic. which can be a laborious task depending on how many of the thousands of intrusion rules you want to enable or disable. Second.9. Finally. You can also generate reports based on events from multiple sensors. so you must use the Defense Center to manage it. when you manage a sensor with a Defense Center. A system policy controls several appliance-level settings such as the login banner and the access control list. Third. 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 push the external authentication object to the sensor. You can use user information from an external server to authenticate users on your Sourcefire 3D System appliances. By pushing a system policy with configured authentication objects to your sensor.1 Sourcefire 3D System Administrator Guide 101 . The Defense Center can then assign impact flags to each intrusion event. all the intrusion events and RNA events are automatically sent to the Defense Center. then the Defense Center can correlate the intrusion events it receives with the information about hosts that RNA provides. The impact flag indicates how likely it is that an intrusion attempt will affect its target. You can also create and apply system policies to your managed sensors. 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. 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. 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.Using the Defense Center Management Concepts Chapter 4 to replicate the intrusion policy on each sensor. External authentication cannot be managed on the sensor. if your Defense Center manages sensors with IPS and RNA. you can create the policy on the Defense Center and push it to the appropriate sensors instead of replicating it locally. 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. There is a similar savings when you create and apply RNA appliance and detection policies to managed 3D Sensors with RNA. 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.

SSL-encrypted TCP tunnel. information is transmitted between the Defense Center and the sensor over a secure. you can see a read-only version of the policy on the Defense Center’s web interface.9.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. When you manage a sensor (or a software sensor). Note that the types of events and policies that are sent between the appliances are based on the sensor type. For details on DC500 database limitations see Database Event Limits on page 333. You can also use a DC500 to manage Sourcefire 3D Sensor software on approved platforms. If you apply a policy on a sensor before you begin managing it with a Defense Center. Version 4.1 Sourcefire 3D System Administrator Guide 102 . as well as intrusion agents and RNA software on approved platforms. The following illustration lists what is transmitted between a Sourcefire Defense Center and its managed sensors.

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

If you want to edit a policy.9. the following graphic shows the Detection Engine page on a 3D Sensor with IPS.com). 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.example. Sourcefire recommends that you use only the Defense Center’s web interface to view events and manage policies for your managed sensors. after communications are set up.1 Sourcefire 3D System Administrator Guide 104 . you must do it on the appliance where the policy was created. The Sample Intrusion Policy that is currently applied to the sensor’s two detection engines was created on the Defense Center (pine. Version 4. For example. TIP! After you set up management with a Defense Center.Using the Defense Center Management Concepts Chapter 4 Then.

RNA Software for Red Hat Linux . 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. 3D3800.for more information. see Managing RNA Software for Red Hat Linux on page 109 3D Sensor Software with RNA for Crossbeam X-Series . Understanding Software Sensors Requires: DC Several of the sensors you can manage with a Defense Center are softwarebased sensors. see Managing 3D Sensor Software with RNA for Crossbeam on page 110 3D Sensor Software with IPS for Crossbeam X-Series . see Managing Intrusion Agents on page 106 3D5800.1 Sourcefire 3D System Administrator Guide 105 .for more information.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.for more information. see Managing 3D Sensor Software with IPS for Crossbeam on page 110 • Version 4. they are automatically shared with managed 3D Sensors with RNA. see Managing 3Dx800 Sensors on page 107.for more information. if you delete an intrusion event from the Defense Center. The following Sourcefire 3D System sensors are software-based: • • • • Intrusion Agents for various platforms .for more information. A software-based sensor is a software-only installation of Sourcefire 3D System sensor software. Similarly. and 3D9800 sensors . deleting an intrusion event from a sensor does not delete it from the Defense Center. For example.9.

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

However.Using the Defense Center Management Concepts Chapter 4 See the Supported Features for Intrusion Agents table for more information.9. and 3D Sensor 9800 models (usually referred to as the 3Dx800 sensors) provide many of the features found on other 3D Sensors. because these models do not have a web interface and because configuration and event data cannot be stored on the sensors.1 Sourcefire 3D System Administrator Guide 107 . 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 . Version 4.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.

See the Supported Features for 3Dx800 Sensors table for more information. 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.Using the Defense Center Management Concepts Chapter 4 certain features cannot be used with these sensors.1 Sourcefire 3D System Administrator Guide 108 .9.

See the Supported Features for RNA Software for Red Hat Linux table for more information. 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. However.1 Sourcefire 3D System Administrator Guide 109 .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. not all of the features function in the same manner.9.

See the Supported Features for RNA on Crossbeam table for more information.1 Sourcefire 3D System Administrator Guide 110 . 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. because the Crossbeam sensors do not have a user interface and because configuration and event data cannot be stored on Version 4. However.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. not all of the features function in the same manner.

See the Supported Features for IPS on Crossbeam table for more information. This is particularly useful if you want to generate a report for the audit events on a managed sensor. Running Remote Reports You can create a report profile on the Defense Center and run it remotely using the data on a managed sensor. 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. you can also perform other sensor-related tasks on the Defense Center. certain features cannot be used with this software.Using the Defense Center Management Concepts Chapter 4 the sensors. See Performing Sensor Backup with the Defense Center on page 419 for more information. Audit events are stored locally Version 4.1 Sourcefire 3D System Administrator Guide 111 . you can use the Defense Center’s web interface to back up those events from the sensor.9. Backing Up a Sensor If you are storing event data on your sensor in addition to sending it to the Defense Center.

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

You can create the following policies on your Defense Center and apply them to managed sensors: • • • health policies system policies RUA policies Version 4. you set up a two-way. it generates events and sends them to the Defense Center using the same channel.9. and then use a different unique NAT ID when adding the Miami 3D Sensor. you must use a unique NAT ID when adding the New York 3D Sensor to the Defense Center. Working with Sensors Requires: DC + 3D Sensor When you manage a sensor. However. SSL-encrypted communication channel between the Defense Center and the 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.1 Sourcefire 3D System Administrator Guide 113 .Using the Defense Center Working with Sensors Chapter 4 be unique. Each NAT ID has to be unique among all NAT IDs used to register sensors on the Defense Center. As the sensor evaluates the traffic.

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

Version 4. and software version for each sensor. sensor group. If you use clustered 3D9900 sensors. See Editing Health Policies on page 530 for information about modifying an existing health policy. intrusion agents. and sensor groups. the sensor model) Sensor List The first column lists the hostname. see the Virtual Defense Center and 3D Sensor Installation Guide. You can click the name of the health policy to view a read-only version of the policy.9. sensor model. if one has been applied. they are designated in the sensor list by a peer icon.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). you can see which sensors are paired and if you configured the sensor as a master or a slave. The following sections describe some of the features on the Sensors page. the field for a Virtual Sensor count appears above the sensor list on the Sensors page. When you hover over the peer icon. Health Policy The next column lists the health policy for the sensor. You can sort by: • • Group (that is. 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. see Managing Sensor Groups on page 131) Model (that is. sensor type. For details about Virtual 3D Sensors. Virtual Sensor Count When you manage Virtual 3D Sensors from the Defense Center.1 Sourcefire 3D System Administrator Guide 115 .

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

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

Version 4. Select Operations > System Settings. or on both the Defense Center and the sensor • • TIP! Set up the managed appliance first.for a unique alphanumeric ID. Log into the web interface of the sensor you want to add. Registration Key. Three fields are provided for setting up communications between appliances: • • • Management Host . Valid combinations include: • • • IMPORTANT! 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 Defense Center. Management Host and Registration Key used on both appliances Registration Key and Unique NAT ID used on the 3D Sensor with Host. Refer to Working in NAT Environments on page 112 for more information.for registration key. Management Host.Using the Defense Center Working with Sensors Chapter 4 To add a sensor.9. Registration Key. Unique NAT ID . The Information page appears.for the hostname or IP address. Registration Key . 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. 2. You must begin the procedure for setting up the management relationship between a Defense Center and a sensor on the sensor.1 Sourcefire 3D System Administrator Guide 118 . To add a sensor to a Defense Center: Access: Admin 1. and Unique NAT ID used on the 3D Sensor with Registration Key and Unique NAT ID used on the Defense Center.

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

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. By default. The Sensors page appears. 11. IMPORTANT! If you elect to prohibit sending packets and you do not store events on the 3D Sensor. 14. 10. Type the IP address or the hostname of the sensor you want to add in the Host field. packet data is not retained. You can prevent packet data from leaving a sensor by enabling the Prohibit Packet Transfer to the Defense Center check box. The Add New Sensor page appears. 15. see Understanding Software Sensors on page 105. In the Registration Key field. 12. data is stored only on the Defense Center and not on the sensor. Click New Sensor. You must store events on the Defense Center. 13. If you used a NAT ID in step 7. IMPORTANT! Software-based sensors such as the 3D Sensor Software for Crossbeam cannot store data locally. enter the same ID in the Unique NAT ID (optional) field. enter the same registration key that you used in step 6.9. Packet data is often important for forensic analysis. and select Operations > Sensors.1 Sourcefire 3D System Administrator Guide 120 . 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. Version 4.Using the Defense Center Working with Sensors Chapter 4 9.

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

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

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

type the same one-time use registration key that you used in step 3.Using the Defense Center Working with Sensors Chapter 4 4. packet data is not retained. Packet data is often important for forensic analysis. The Sensors page appears. Click New Sensor. The Add New Sensor page appears. 11. By default. Log into the Defense Center’s web interface using a user account with Admin access. 6. type a unique ID that you want to use to identify the sensor. 5. In the Registration Key field. 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 . Type the IP address or the hostname of the sensor you want to add in the Host field. 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. the Pending Registration status appears. 12. 8. data is stored only on the Defense Center and not on the sensor. type the same value in the Unique NAT ID field. If you elect to prohibit sending packets and you do not store events on the 3D Sensor. Click Save. After the sensor confirms communication with the Defense Center. 10. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 9. and select Operations > Sensors. 7. in the Unique NAT ID field. Version 4.9. Optionally. If you used a unique NAT ID in step 4.

and 3D Sensor 9800 (usually called the 3Dx800 sensors) do not have their own web interfaces.domain [admin] Version 4. You can view the sensor’s status on the Sensors page (Operations > Sensors). sensor. To manage a 3Dx800 sensor with a Defense Center: Access: Admin 1. Contact technical support for more information.Using the Defense Center Working with Sensors Chapter 4 13. you may need to use the Add Manager feature a second time to add the secondary Defense Center.9. It can take up to two minutes for the Defense Center to verify the sensor’s heartbeat and establish communication. 3D Sensor 5800. 14. Managing a 3Dx800 Sensor Requires: DC + 3D Sensor Because the Sourcefire 3D Sensor 3800. This procedure assumes that you have completed the setup steps described in the sensor’s Installation Guide. select the group from the Add to Group list. The CLI prompt appears. see Managing Sensor Groups on page 131. In some high availability deployments where network address translation is used. To add the sensor to a group. The sensor is added to the Defense Center.1 Sourcefire 3D System Administrator Guide 125 . Click Add. 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. Log into the 3D Sensor using the admin account. For more information about groups.

If you changed the management port on the Defense Center. • If you are deploying your sensor in a network that does use network address translation. Use the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 7. 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. Version 4. reg_key is a unique single-use alphanumeric registration key. Select Operations > Sensors.1 Sourcefire 3D System Administrator Guide 126 . 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. the sensor may be managed by another Defense Center. Using a user account with Admin access. The Sensors page appears. 6. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. In either case. 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. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center. a message appears indicating that remote management is enabled.9. 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 the following command to determine whether remote management is already enabled: [admin:sensor] show management If management is already enabled. 8. 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.Using the Defense Center Working with Sensors Chapter 4 2. and nat_id is a unique alphanumeric string. 4. 5. Enter the following at the CLI prompt: [admin] configure sensor 3. log into the web interface of the Defense Center where you want to add the sensor.

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

4. you can manually reset communications on the sensor. On the sensor. Click Delete next to the sensor that is no longer communicating with the Defense Center. Select Operations > Sensors. access the command prompt and use the admin account to log in. Resetting Communications on the 3Dx800 Requires: DC + 3D Sensor If communication fails between a 3Dx800 sensor and the Defense Center that manages it. Log into the web interface of the Defense Center that manages the sensor. Resetting Communications on the 3Dx800. The CLI prompt appears. 6.domain [admin] 5. 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. 3. The CLI prompt appears. Enter the following at the CLI prompt: [admin] configure sensor 2. Click Delete next to the sensor you want to delete. 3. The Sensors page appears. Select Operations > Sensors. see the next section. you must re-enable remote management and then add the sensor to the Defense Center. sensor. The sensor is deleted.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.9. The Sensors page appears. Version 4.domain [admin] 2. sensor. The sensor is deleted. 4. On the sensor. 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. 7. Log into the web interface of the Defense Center where you want to delete the sensor. For more information.1 Sourcefire 3D System Administrator Guide 128 .

and nat_id is a unique alphanumeric string. • If your sensor is in a network that does use network address translation. In the Host field. 10. 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. 7. remote management is enabled again. Enter the following command to exit the CLI and return to the login prompt: [admin:sensor] exit 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. In either case. 8. The Sensors page appears. Version 4. The NAT ID together with the registration key must uniquely identify the communications channel between the sensor and the Defense Center. Enter the following command to disable remote management: [admin:sensor] set management disable Remote management is disabled. 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. • If your sensor is in a network that does not use network address translation. On the Defense Center’s Sensors page.9. The IP address and registration key pair must uniquely identify the communications channel between the sensor and the Defense Center. Click Add. Use one of the following commands to enable remote management. Communications are restarted and the sensor is re-added to the Defense Center. Enter the following at the CLI prompt: [admin] configure sensor 6.1 Sourcefire 3D System Administrator Guide 129 . 11.Using the Defense Center Working with Sensors Chapter 4 5. re-add the sensor by clicking New Sensor. reg_key is a unique single-use alphanumeric registration key.

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

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

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

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

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

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

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

Using the Defense Center Editing a Managed Sensor’s System Settings Chapter 4 2. you can reboot or restart the processes on a managed sensor using the Defense Center’s web interface. Click Edit next to the name of the sensor whose system settings you want to edit. 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. See the Sensor Information table on page 135 for a description of each field. Change the sensor’s attributes as needed. Click Save. RNA Software for Red Hat Linux. Stopping and Restarting a Managed Sensor Requires: DC For 3D Sensors. Version 4. The Information page for that sensor appears. 4. and Intrusion Agents.9.1 Sourcefire 3D System Administrator Guide 137 . You must use the command line interface (CLI) to manage processes on Crossbeam-based software sensors. 3. The updated sensor attributes are saved.

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

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

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

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.Using the Defense Center Managing a Clustered Pair Chapter 4 After you establish the relationship between the two sensors. interface set. and data from a clustered pair. For information about the connections between the master and slave 3D9900 sensors. they act like two separate sensors with a single.1 Sourcefire 3D System Administrator Guide 141 . Cluster Interconnect Master Interface ethb2 RX ethb2 TX Slave Interface ethb0 TX ethb0 RX Version 4. shared detection configuration.9. see the Cluster Interconnect table. For information on the detection engines. and local management is blocked on the shared portion of the clustered pair. The following diagram shows interfaces on the master and slave sensors.

you must: • • • decide which unit will be the master have SEU 2. 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. see the Sourcefire 3D Sensor Installation Guide. After you establish the master/slave relationship. 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. For more information.8. IMPORTANT! You cannot connect the slave’s ethb2 and ethb3 pair when you establish the clustered pairing.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. Before you begin. Version 4. you cannot change which sensor is the master or slave unless you break and reestablish the relationship using the Defense Center. You determine the master/slave designation by the way you cable the pair.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. After you establish the relationship. Connect the master’s ethb2 and ethb3 pair to the slave’s ethb0 and ethb1 pair as shown in the Cluster Interconnect table. the detection engines and interface set are combined on the two sensors. you must edit and reapply your detection policy after you establish clustering.1 Sourcefire 3D System Administrator Guide 142 . For more information about cabling.9.

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

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

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

see Feature Licenses on page 148 details of high availability pair operation. • • • • • • • • • • custom dashboards authentication objects for Sourcefire 3D System user accounts custom workflows custom tables sensor attributes. make sure you remove duplicate user accounts from one of the Defense Centers. Also. 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. make sure you register all intrusion agents to the primary Defense Center. • • RNA detection policies RNA custom service detectors Version 4. you must make sure that the admin account uses the same password on both Defense Centers. such as the sensor’s host name. and the group in which the sensor resides intrusion. 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.9. if you have any user accounts with the same name on both Defense Centers. see Sensor Configurations and User Information on page 146 health and system policies shared in a high availability pair. RNA. because both Defense Centers must have an admin account. see Health and System Policies on page 147 feature license operation in a high availability pair.Using the Defense Center Configuring High Availability Chapter 4 For more information on: • • • • sensor attributes and user information shared in a high availability pair.1 Sourcefire 3D System Administrator Guide 146 .

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

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.1 Sourcefire 3D System Administrator Guide 148 . IMPORTANT! An RUA Agent can only connect to one Defense Center at a time. if the primary Defense Center fails. and any change you make to one Defense Center should be applied on the other Defense Center within ten minutes. 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. In an high-availability environment. RUA. For more information. if you want to use NetFlow data to supplement the data gathered by your 3D Sensors with RNA. it will not receive data from your NetFlow-enabled devices. both Defense Centers must have RUA licenses if you want to manage 3D Sensors with RUA with the high availability pair. 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. so changes appear within two five-minute Version 4. While NetFlow data and devices are shared. you can make policy or other changes to either Defense Center.9. Understanding High Availability Requires: DC Although Defense Centers in high availability mode are named “primary” and “secondary. but the cycles themselves could be out of sync by as much as five minutes. you must make sure that your RUA Agents can communicate with the secondary Defense Center. the two Defense Centers must have enough NetFlow licenses to merge the list of devices on each. • While RUA LDAP authentication objects are shared. ” Defense Centers periodically update each other on changes to their configurations.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.

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

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

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

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

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

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

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

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

You can also choose whether to include the packet data collected with the intrusion events. The following sections explain more about using a Master Defense Center in your Sourcefire 3D System deployment. 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. 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. although most deployments will use the same configuration across the enterprise. The settings on the Filter Configuration page determine which events are forwarded from the Defense Center to the Master Defense Center. Managing Appliance Groups on page 179 explains how to use appliance groups to aid in managing 3D Sensors and Defense Centers. In this way. The Master Defense Center can also aggregate events related to the health of managed Defense Centers.9.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. • • • • 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. Understanding Global Policy Management on page 161 explains which policies you can send from your Master Defense Center to 3D Sensors and Defense Centers. • Understanding Event Aggregation on page 157 explains which types of events you can send from your Master Defense Centers to your Master Defense Center. You can configure a Defense Center to send intrusion events based on their flag. 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. Adding and Deleting Defense Centers on page 164 explains how to configure a Defense Center to communicate with a Master Defense Center. you can view the current status of the Defense Centers across your enterprise from a web interface. You can set up a different configuration for each Defense Center. When you apply intrusion policies from a Master Defense Center. If it finds an older SEU. the Sourcefire 3D System checks the SEU on the managing Defense Center. it updates the managing Defense Center’s SEU.1 Sourcefire 3D System Administrator Guide 157 .

Version 4. you may also want to send intrusion events with the black inline result flag.The intrusion events specified in the Flags section are forwarded to the Master Defense Center. then intrusion events are limited to gray impact flags to indicate unknown impact. RNA events. When you use the Filter Configuration page to specify which events are forwarded to the Master Defense Center.1 Sourcefire 3D System Administrator Guide 158 . If your 3D Sensors are deployed inline and you are using intrusion rules set to Drop and Generate Events. For example. along with any related packets. you can choose one of the following options: • • Do Not Send . are forwarded to the Master Defense Center. you can greatly reduce the number of events sent from a Defense Center by excluding events with the blue or gray impact flags.Intrusion events are not forwarded to the Master Defense Center. If you do not deploy 3D Sensors with RNA on your network. 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. Events and Packet Data . For example. Packet decoders. flow data. 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. the red impact flag. Events Only . however. and intrusion rules are all able to generate intrusion events. The conditions that can trigger a compliance rule include intrusion events. • You can use the Flags section of the Filter Configuration page to forward only the intrusion events that are important to your analysis. that is. you may want to limit the intrusion events on the Master Defense Center to only those with the greatest impact.The intrusion events specified in the Flags section. and anomalous network traffic.9. preprocessors. IMPORTANT! You must deploy both RNA and IPS on your network to generate intrusion events with meaningful impact flags.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. any packets captured for the event are not sent.

and NetFlow. health events. allows you search for intrusion events. network interfaces. and RUA events. health events. white list events. However. white list events. RNA and RUA feature licenses allows you to configure detection engines. 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. there are certain limitations that you should take into consideration when you design your Master Defense Center deployment. client applications. remediation status. compliance events. interface sets. audit log. users.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. white list violations. RNA events. 3D Sensor configuration allows you to configure detection engines allows you to search for intrusion events.1 Sourcefire 3D System Administrator Guide 159 . you can choose to send or not send compliance events. host attributes. The Master Defense Center and Defense Center Functional Comparison table compares and contrasts Defense Center and Master Defense Center functional areas. flow data. SEU import log. scan results. SEU import log.9. compliance events. audit log. Master Defense Center and Defense Center Functional Comparison Function License provisions Master Defense Center provides product license Defense Center provides product license. services. hosts. vulnerabilities. Analysis and reporting search Version 4.

This means that if your Defense Centers are accepting events from their 3D Sensors up to the rate limit. you can gain insight into RNA-detected activity across your enterprise. However. the Master Defense Center does not build a network map or host data for the hosts on your network. and not sending the packet data. Version 4. 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 can also limit the amount of data transferred between a Defense Center and its Master Defense Center by sending only intrusion event data. Event Rate The event rate limit for the Master Defense Center is the same rate limit on Defense Centers. you must adjust the event filter on the Master Defense Center so that only the most important events are forwarded from the Defense Centers. Intrusion Agents Intrusion events generated by intrusion agents are not forwarded to the Master Defense Center. In addition.1 Sourcefire 3D System Administrator Guide 160 . 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. 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.9. because you can forward compliance events and white list events from your managed Defense Centers to your Master Defense Center. 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. For example.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. To take advantage of this.

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

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. • Using RNA Detection Policies on a Master Defense Center Requires: MDC You can create. Refer to the following. and apply default health policies to the Master Defense Center and to connected Defense Centers. delete. export. This section also explains how to configure rules in inline intrusion policies so that they drop malicious packets. and for brief descriptions of those modules that are used.9. and apply RNA detection policies from a Master Defense Center. Note that SEUs can also contain new and updated decoders and preprocessors. 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. 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. edit. 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.1 Sourcefire 3D System Administrator Guide 162 . 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. the Sourcefire 3D System checks for any older SEUs on Defense Center(s) managing those detection engines. delete.9. if your Version 4. 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. export. The Sourcefire 3D System bases intrusion policies on SEUs residing on the appliance where the policy is built. The Defense Center and Master Defense Center do not handle these policies in the same manner. RNA detection. and apply intrusion detection and prevention policies from a Master Defense Center. You cannot apply a non-filtered policy from a Defense Center then add filters to it from a managing Master Defense Center. Therefore. you must apply a non-filtered policy to the detection engine from the same Defense Center or Master Defense Center. Master Defense Center Policy Management Limitations Requires: MDC There are several types of policies including detection and prevention. RUA detection. If it finds SEUs older than those on the Master Defense Center. the Apply button activates. However. TIP! Before applying a filtered policy. they are updated. and listing client applications and vulnerabilities are performed on Defense Centers and not on Master Defense Centers. listing RNA hosts and events. Detection and Prevention Policies You can create. When you apply an intrusion policy to a 3D Sensor’s detection engines from a Master Defense Center. After you acknowledge the message by clicking its check box.1 Sourcefire 3D System Administrator Guide 163 .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. a warning message with a check box appears. RNA Detection Policies RNA analysis and reporting functions such as using the network map. and health policies.

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

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

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

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

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

type the IP address or the host name of the Master Defense Center that you want to use to manage the Defense Center. Optionally. Click Remote Management. 4. In the Management Host field. TIP! You can leave the Management Host field empty if the management host does not have a routable address. In that case. 8. log into the web interface of the Defense Center you want to add. 5. Click Add Manager. The Information page appears. Select Operations > System Settings. Version 4. 2. In the Registration Key field. The Remote Management page appears.9. type a unique alphanumeric NAT ID that you want to use to identify the Defense Center. 3. The Add Remote Management page appears. 7. 6. After the Defense Center confirms communication with the Master Defense Center. 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. Click Save. in the Unique NAT ID field. To add a Defense Center to a Master Defense Center: Access: Admin 1. 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 To add a Defense Center. the Pending Registration status appears.1 Sourcefire 3D System Administrator Guide 169 . use both the Registration Key and the Unique NAT ID fields. Using a user account with Admin access. you need to predetermine which events on the Defense Center you want to forward to the Master Defense Center.

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

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

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

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

See Editing Settings for a Managed Defense Center on page 175 for more information. See Deleting a Defense Center on page 171 for more information. Click the Delete icon next to a Defense Center if you no longer want to manage the Defense Center with the Master Defense Center. The red exclamation point icon indicates that the Master Defense Center has not received communications from the Defense Center in the last three minutes. which sorts by appliance model number. You can sort by: • Group. An HA pair is listed as a group named with the name of the active Defense Center. 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. and seconds) since the last contact. • • Manager. the health blacklist settings. the remote management configuration. The system settings include the filter configuration for the Defense Center. it sends a two-byte heartbeat packet to establish contact and ensure that the communications channel is still running. and so on. Status Icons The status icons indicate the state of a Defense Center. you can contact technical support to change the default time interval.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. If your network is constrained in bandwidth. minutes. The green check mark icon indicates that the Master Defense Center and the Defense Center are communicating properly. If you hover your cursor over the icon. Model. If the Master Defense Center has not received a communication from a Defense Center within the last two minutes. the Defense Center 1000 and the Defense Center 3000. 3D Sensor 2100.9.1 Sourcefire 3D System Administrator Guide 174 . Edit and Delete Icons Click the Edit icon next to a sensor if you want to change the Defense Center’s current system settings. that is. which sorts by the Defense Center then the 3D Sensor connected to it. a pop-up window indicates the amount of time (in hours. and the high availability settings. Version 4.

not the hostname. The model name for the managed Defense Center. Note that this is the name of the Defense Center in the Master Defense Center web interface.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. The IP address of the managed Defense Center. See the following sections for more information. 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. select Appliances from the Operations menu. The version of the software currently installed on 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.1 Sourcefire 3D System Administrator Guide 175 . then click Edit next to the Defense Center. Defense Center Information Field Name Description The assigned name for the Defense Center. The Vulnerability Database version on the managed Defense Center.9. Product Model Software Version Operating System Operating System Version VDB Version IP Address Version 4. The operating system currently running on the managed Defense Center. you can use the Master Defense Center web interface to view and edit the configuration of the Defense Center.

See the Impact Flags table in the Analyst Guide for an explanation of what each impact Version 4.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. If you hover your cursor over the icon. and compliance events.1 Sourcefire 3D System Administrator Guide 176 . Change the Defense Center’s attributes as needed. If you want to send intrusion events (with or without packet data). 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. 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. The group that the Defense Center belongs to. you can also specify which intrusion events are sent based on their impact flag. a pop-up message indicates how long it has been (in hours. intrusion events and related packet data. Model Number Current Group The model number for the Defense Center. and seconds) since the Defense Center communicated with the Master Defense Center. To edit a managed Defense Center’s settings: Access: Admin 1. minutes. Your options are to send intrusion events. Click Save. You can click Refresh to update the Status icon and its accompanying pop-up message. 2. The updated Defense Center attributes are saved. if any.9. This number can be important for troubleshooting.

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

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

TIP! A light bulb icon shows which of the high availability paired Defense Centers is currently active. The redundant Defense Center is activated. register all Intrusion Agents to the primary Defense Center. you can activate Defense Center High Availability from a Master Defense Center. To activate a redundant Defense Center: Access: Admin 1. TIP! When using Intrusion Agents registered to Defense Centers configured for high availability and managed by a Master Defense Center. The Appliances page appears. Click Edit next to the appropriate Defense Center. 2. 3.9. Click Activate to activate the redundant Defense Center.1 Sourcefire 3D System Administrator Guide 179 . Select Operations > Appliances. 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.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. The System Settings page for that Defense Center appears. The high availability page appears with the paired Defense Centers. Version 4. TIP! High availability Defense Center pairs are automatically listed as an appliance group. 4. Click High Availability. An HA pair is listed as a group with the name of the active Defense Center.

In the Group Name field. 5. 7. The Appliances page appears. Click Create New Appliance Group. type the name of the group you want to create. Click Save. On the Master Defense Center. Click Save. select Operations > Appliances. The Appliance Group Edit page appears. Editing Appliance Groups on page 180 explains how to modify the list of Defense Centers in a Defense Center group. 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. 6. The group is added. To create an appliance group and add appliances to it: Access: Admin 1. Version 4. 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.1 Sourcefire 3D System Administrator Guide 180 . Moving an appliance to a new group does not change any of its policies or configurations. TIP! You must remove an appliance from its current group before you can add it to a new group. To add appliances to the group. 2. The Create Appliance Group page appears. Deleting Appliance Groups on page 181 explains how to delete a Defense Center group. 3. return to the Appliances page (Operations > Appliances) and click Edit next to the name of the group. 4.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.9. Editing Appliance Groups Requires: MDC You can change the set of appliances that reside in any appliance group. The appliances are added to the group and the Appliances page appears again.

Click Edit next to the Appliance group you want to edit. 2. Deleting Appliance Groups Requires: MDC If you delete a group that contains appliances. To delete an appliance group: Access: Admin 1. They are not deleted from the Master Defense Center. Select Operations > Appliances. The Appliance Group Edit page appears. select it from the Available Appliances list and click the arrow pointing toward the group you are editing. The appliances group is removed from the Master Defense Center. The Appliances page appears. To remove an appliance from a group. On the Master Defense Center.1 Sourcefire 3D System Administrator Guide 181 .Using the Master Defense Center Editing Master Defense Center System Settings Chapter 5 To edit an appliance group: Access: Admin 1. the Master Defense Center system settings are the same as those of a Defense Center. Editing Master Defense Center System Settings Requires: MDC With a few exceptions. Click Save. select Operations > Appliances. Select the appliance you want to move and click the arrow to add or remove it from the group. select it from the list in the group you are editing and click the arrow pointing to the Available Appliances list. • • • • 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.9. Click Delete next to the group you want to delete. • • To add an appliance to the group. 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. 3. the appliances are moved to Ungrouped on the Appliances page. 4. 2. The Appliances page appears.

2. The updated Master Defense Center attributes are saved. see Configuring Network Settings on page 377.9. Click License. Configuring Network Settings Requires: MDC The network settings are identical to those of the Defense Center.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. The Information page appears. WARNING! The name must be made up of a combination of alphanumeric characters and should not be made up of numeric characters only. For information on configuring the Master Defense Center network settings. To view information about the Master Defense Center license: Access: Admin 1. To edit a Master Defense Center’s settings: Access: Admin 1. Select Operations > System Settings. The License page appears. You can: • • • shut down the appliance reboot the appliance restart the appliance Version 4.1 Sourcefire 3D System Administrator Guide 182 . Click Save. Change the name of the Master Defense Center attributes as needed. Shutting Down and Restarting the System Requires: MDC You have several options for controlling the processes on your Master Defense Center. a Master Defense Center cannot manage the licenses of Defense Centers or 3D Sensors. 2. see Defense Center Information on page 175. Viewing a Master Defense Center License Requires: MDC Unlike a Defense Center.

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

see Synchronizing Time on page 354.9. type the IP address of the NTP server or. if DNS is enabled. in the text box.1 Sourcefire 3D System Administrator Guide 184 . WARNING! If the appliance is rebooted and your DHCP server sets an NTP server record different than the one you specify here. Blacklisting Health Policies Requires: MDC You can blacklist health policy modules when required. For more information about setting system time. type the fully qualified host and domain name. select Manually in the System Settings. Version 4. select Via NTP Server from and. To avoid this situation. To receive time through NTP from a different server. the DHCP-provided NTP server will be used instead.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. 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. see Blacklisting a Health Policy Module on page 537. you should configure your DHCP server to set the same NTP server.

However. the Sourcefire 3D System provides a feature called the detection engine. you cannot use RUA or RNA on 3D9800 sensors. and the third for RUA.1 Sourcefire 3D System Administrator Guide 185 . In addition.9. one for RNA. you can combine the data from those sensors with RUA or RNA on a Defense Center. See the Detection Resources by Model table on page 190 for more information. Most 3D Sensor models have at least three detection resources available and can support at least three detection engines: one for IPS.Using Detection Engines and Interface Sets Chapter 6 Administrator Guide To give you increased flexibility in your deployment choices. Version 4. 3D Sensors support three types of detection engines: • • • IPS RNA RUA TIP! You cannot use the RUA feature on Crossbeam-based software sensors. 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).

Managing Detection Engines on page 193 explains how to create. To list the available detection engines: Access: Admin Select Operations > Configuration > Detection Engines > Detection Engines. Version 4. Using Interface Sets on page 207 describes how to create interface sets and how to use them with detection engines. 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. • • • • • • • 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.1 Sourcefire 3D System Administrator Guide 186 . The figure below shows the Defense Center version of the page.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. and delete detection engines. sensor. edit. 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. detection engine type. Using Interface Set Groups on page 223 describes how to create and use interface sets groups. Using Clustered 3D Sensors on page 227 explains how to use detection engines and interface sets in a clustered 3D9900 sensor pairing. policy.9. The Available Detection Engines page appears. or interface set type. including some of the limitations based on the sensor model. You can sort the available detection engines by group. Using Detection Engine Groups on page 197 explains how to create and use detection engine groups. This section also describes how default detection engines are configured.

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

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

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

and detection resources available on Crossbeam System hardware. current Crossbeam System hardware and software support. Version 4. Crossbeam-based Software Sensor Considerations Depending upon the capabilities of your X-Series and the products you are licensed to use. Refer to the Sourcefire 3D Sensor Software for X-Series Installation Guide for information on deployment scenarios. Understanding Default Detection Engines Requires: DC or 3D Sensor When you install a new 3D Sensor. After initial installation can modify interface sets and detection engines. you can use initial interface sets and default detection engines to quickly begin evaluating network traffic. you can reduce latency by distributing your network traffic across all available interfaces on the sensor. Consider how your network is configured and how you want to deploy the Sourcefire 3D System within it. As with other 3D Sensors. you have several deployment options for 3D Sensor Software.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.9. the maximum number of detection engines that you can create is equal to the number of available detection resources.1 Sourcefire 3D System Administrator Guide 191 . 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 default that builds paired fail-open interface sets on all 3D Sensor interfaces. Passive that builds a single passive interface set for all 3D Sensor interfaces. and you have deployed it in a high-bandwidth environment where the traffic load is likely to reach the design limits of the appliance. less the management interface. less the management interface.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. typically you pair adjacent interfaces. the second on-board interface cannot support the same high-performance standards as the interfaces on the network interface cards. usually near the management interface. Select Inline with Fail-Open Mode if you cabled the sensing interfaces inline on your network as an IPS. 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. Choose from these initial interface sets based on how you deployed the sensor. the detection engine may not provide optimum performance. If you want to change either the number of detection resources or the interfaces assigned to the default detection engine. Depending on the 3D Sensor. Version 4. note that the default detection engine does not include the second on-board interface. IMPORTANT! For the 3D3000 on the IBM xSeries 346 appliance.1 Sourcefire 3D System Administrator Guide 192 . Sourcefire recommends that you remove the second on-board interface from the detection engine for improved performance. If you modify the default detection engine to include it. for example. see Editing a Detection Engine on page 194. on some of the older models. that is automatically included in the default detection engine. Select Passive Mode if the sensing interfaces are not cabled inline.9. If your appliance has one of these extra interfaces. 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. Second On-Board Interface Some Sourcefire sensors have a second on-board interface. With this configuration. 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. However.

when they are available on your 3D Sensor. Click Create Detection Engine. The figure below shows the Defense Center version of the page.1 Sourcefire 3D System Administrator Guide 193 . The Detection Engines page appears. 2. 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. and spaces. Select Operations > Configuration > Detection Engines > Detection Engines. Version 4. edit. 3. punctuation. In the Name and Description fields. You can use alphanumeric characters. 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. The Create Detection Engine page appears. You can use interface sets that include multiple inline interface pairs. enter a name and description for the new detection engine.9. and delete detection engines.

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

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

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

Version 4. Select Operations > Configuration > Detection Engines > Detection Engines. To delete a detection engine: Access: Admin 1. see Modifying a Rule in the Analyst Guide. you should not delete a detection engine that is used as a constraint in one or more compliance rules. The Detection Engines page appears.9. Also. The Detection Engines page appears. 2. The detection engine is deleted. you should first delete (or modify) the constraint in all rules in which it is used.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. For information on modifying compliance rules. WARNING! Do not delete a detection engine that is in use. Select Operations > Configuration > Detection Engines > Detection Engines. however. confirm that you want to delete the detection engine. 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. a record of the detection engine is retained so that events generated by that detection engine are viewable. Click Delete next to the detection engine you want to delete. At the prompt. To create a detection engine group: 1.1 Sourcefire 3D System Administrator Guide 197 . 3. These groups make it easier to apply policies to detection engines that have similar purposes. Using Detection Engine Groups Requires: DC/MDC or 3D Sensor You can use detection engine groups to combine similar detection engines.

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

Select Operations > Configuration > Detection Engines > Detection Engines. Click Delete next to the name of the detection engine group.0/24) and another monitors a different class (for example.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. you can use the system default Version 4. The Detection Engines page appears. which includes a mixed address space. In the system default variable used in the intrusion policy: HOME_NET = 10.10. However.10.10.10. 10. When you apply an intrusion policy to that detection engine.30.0/16). hosts in your accounting department in the address range 10. For example.0/16 In the detection engine named DE_DMZ: HOME_NET = 10. they are not deleted.1 Sourcefire 3D System Administrator Guide 199 . To delete a detection engine group: Access: Admin 1. which are specific to the policy in which they are created. 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.90. if you have created your detection engines so that one detection engine monitors one class of hosts (in this example.90. 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.0/24 In the detection engine named DE_ACCT: HOME_NET = 10. You can define HOME_NET in your system default variable to encompass your internal address range (for example.10.0/24). hosts in your network’s DMZ in the range 10.0.10. For information on policy-specific variables. The detection engine group is deleted. any detection engines in the group are automatically ungrouped.0. 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. you can use detection engine-specific variable values to tailor your detection capabilities to more closely match your infrastructure.30.0/24 If you later create another detection engine that monitors the rest of your network. see Creating New Policy-Specific Variables in the Analyst Guide. 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.9. 2.

Configuration details in this section relate to 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. For an explanation see Using Variables within Detection Engines on page 199. IMPORTANT! You cannot use variables with RNA detection engines. 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. which means 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 variable value rather than creating another detection engine-specific value for HOME_NET. Optionally. See Creating New Variables in the Analyst Guide and Modifying Variables in the Analyst Guide for more information. You can view the corresponding new system default variable in the list of system default variables within each policy. If you disable a variable defined on the Variable List page by resetting the variable. For more information. For configuration details related to setting detection engine-specific variables within an intrusion policy. the definition reverts to the definition in the intrusion policy the next time you apply the policy. you can modify the variable in the intrusion policies and detection engines where it is added automatically to give it a specific definition. You can also create new variables for use only within the context of the detection engine. 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. see Creating New Variables in the Analyst Guide. 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. Version 4. or on the detection engine Variable List page for the detection engine. 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.1 Sourcefire 3D System Administrator Guide 200 .9. and on the Variable list page for all other detection engines where it is listed with the value set to Policy Defined. When they exist. a detection engine-specific variable value takes precedence over a policy-specific or system default value for the same variable.

Enter a value for the variable and click Save. The Variable List page appears. Click Edit next to the variable you want to define. Select Operations > Configuration > Detection Engines > Detection Engines. Version 4. The Detection Engines page appears. See Creating New Variables in the Analyst Guide for information about variable syntax. The Variable List page appears again and shows the new value for the variable. 2. The value for each of the variables defaults to the value within the intrusion policy that is applied to the detection engine. 4. as described in Applying an Intrusion Policy in the Analyst Guide.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. 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. The Variable Binding page appears.9. 3.1 Sourcefire 3D System Administrator Guide 201 .

Click Add Variable. enter a name for the variable. Click Variables next to the detection engine where you want to define a variable value. you can associate detection engine-specific variable definitions with the policy. 5.9. 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. 4. • • • See Defining IP Addresses in Variables and Rules in the Analyst Guide for more information if you are defining a IP address-based variable. The Detection Engines page appears. 3. select IP Port. or Custom.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. The Variable List page appears. . Version 4. Select Operations > Configuration > Detection Engines > Detection Engines.1 Sourcefire 3D System Administrator Guide 202 . 2. To create a new variable for a detection engine: Access: Admin 1. From the Variable Type drop-down list. See Defining Ports in Variables and Rules in the Analyst Guide for more information if you are defining a port-based variable. For an explanation see Using Variables within Detection Engines on page 199. In the Variable Name field. The Variable 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. You cannot delete predefined system variables within an intrusion policy. In the Value field. The variable is created and is accessible to all policies as a system default variable. You can delete predefined system variables on the detection engine Variable List page. The Detection Engines page appears. enter a value for the variable and click Save. Select Operations > Configuration > Detection Engines > Detection Engines. as described in Applying an Intrusion Policy in the Analyst Guide. 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. To delete or reset variables on a detection engine: Access: Admin 1. See Creating New Variables in the Analyst Guide for information about the syntax for variables. but only if they are not used in any active or inactive rule within the system. Version 4. and listed for all other detection engines on the Variable List page with a value of Policy Defined. 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. Creating the new detection engine variable also lists the description Policy Defined for all other IPS detection engines on the Variable List page. the value any will be used. The variable takes effect the next time you apply an intrusion policy to the detection engine. You can also delete variables that you created within the context of the detection engine.9. IMPORTANT! Each new detection engine variable adds a system variable with a value of any that is accessible in all your intrusion policies. It is listed in the variable list for the detection engine in all intrusion policies with the explicitly set value.1 Sourcefire 3D System Administrator Guide 203 .Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 6.

You can add a new USER_CONF detection engine variable using the reserved name USER_CONF . You can set an explicit detection engine value for the predefined SNORT_BPF custom system variable. 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. or by creating a variable using a specific reserved name. The variable is reset and Policy Defined appears in the Value column. The variable is deleted from the detection engine the next time you apply an intrusion policy to the detection engine. click Delete next to the name of the variable. • To delete a locally created variable. Click Variables next to the detection engine where you want to delete or reset a variable value.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 2. The Variable List page appears.1 Sourcefire 3D System Administrator Guide 204 . 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.9. 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 Understanding Custom Variables in the Analyst Guide. For more information. You then define the variable value with a set of instructions appropriate to the function the variable provides. Version 4. 3.

One downside to using multiple detection resources is that no single resource sees all the traffic on a network segment. 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. which is a requirement for the portscan preprocessor. In this way.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.1 Sourcefire 3D System Administrator Guide 205 . Engines on page 202. 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. To overcome this issue. Make sure you use the interface set that you created in step 1. Remember that the portscan-only detection engine can use only one detection resource. 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. inline. 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. 3. Using the Defense Center’s web interface. However.9. Depending on the traffic mix on your network. 1. 2. Version 4. you may need to adjust the number of resources in the multi-resource detection engine. the sensor can process more packets with greater efficiency. 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 . Internal logic on the sensor ensures that packets belonging to the same session are directed to the same resource for analysis. The interface set can be passive. create an interface set that includes the network interfaces you want to use on the sensor. Create an IPS portscan-only detection engine and assign one detection resource to it. or inline with fail open depending on how your sensor is deployed. 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. you can create a portscan-only intrusion policy and apply it to a portscan-only detection engine on the sensor. see Assigning Values to System Default Variables in Detection Engines on page 200. Multiple detection engines will use this interface set.

make sure you disable portscan detection in this policy. • • • • • • IMPORTANT! Note that when portscan detection is enabled. Create and apply an intrusion policy to the portscan-only detection engine. You do not need to set up variables for this policy. Make sure you match the type of intrusion policy to the type of interface set that you created in step 1.1 Sourcefire 3D System Administrator Guide 206 . Ensure that the DCE/RPC Configuration preprocessor. Also. 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. 6. 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. Create and apply an intrusion policy for the multi-resource detection engine. or Rule Processing Configuration. Review the resulting intrusion events to ensure that you are receiving the events you expect. Ensure that OPSEC Configuration (under External Responses) is disabled. See Enabling and Disabling Advanced IPS Features in the Analyst Guide for more information. 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. You should not change the default settings for Checksum Verification or Packet Decoding (under Transport/Network Layer Preprocessors). the SMTP Configuration preprocessor (under Application Layer Preprocessors). 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. the HTTP Configuration preprocessor. Working with Layers.Using Detection Engines and Interface Sets Using Variables within Detection Engines Chapter 6 4. 5.9. items listed under Performance Statistics. Enable Portscan Detection and configure it for your network environment. and Back Orifice Detection (under Specific Threat Detection) are disabled. Version 4. Note that all rules are disabled on the Rules page. See Detecting Portscans in the Analyst Guide for more information. See the Portscan Detection SIDs (GID:122) table in the Analyst Guide for more information. See Selecting the Base Policy in the Analyst Guide for more information. Make sure portscan rules are enabled for the types of portscans you configure.

You can also set interfaces on most sensors in transparent inline mode. Only 3D9900 sensors provide a fail-safe option that works with inline interface sets. Some installations require that the link state be propagated and most sensor interfaces provide that option. For more information on the PEP feature. On selected sensors you can set interfaces to tap mode. • With the exception of the Virtual 3D Sensor. see Using PEP to Manage Traffic in the Analyst Guide. To list the available interface sets: Access: Admin Select Operations > Configuration > Detection Engines > Interface Sets. The Virtual 3D Sensor supports only passive mode operation. or inline with fail-open mode.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. Only 3D9900 sensors provide the PEP feature. You can sort the available interface sets by group.9. inline. Sensors with Gigabit Ethernet interfaces can employ jumbo frames. • • • • • • • Version 4. 3D Sensors deployed in networks that are highly sensitive to latency can use the automatic application bypass option. set type. or PEP policy. sensor. 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.1 Sourcefire 3D System Administrator Guide 207 . you can set up any of your 3D Sensor interfaces in passive.

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. 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.1 Sourcefire 3D System Administrator Guide 208 .

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

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

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

The valid range is from 250 ms to 60.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. If a detection engine is bypassed. or RUA detection engine and allows packets to bypass the detection engine if the time is exceeded. 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. The feature functions with both passive and inline interface sets. a core file is automatically generated for potential troubleshooting by Sourcefire Support. To see a list of which 3D Sensors you can use Automatic Application Bypass Monitoring on. however. 3D Sensors generate a health monitoring alert.1 Sourcefire 3D System Administrator Guide 212 . Typical maximum sized jumbo frames are 9018 bytes. excessive numbers of core files can result in disk usage health alerts. Version 4. You can apply automatic application bypass on an interface set basis. You can change the bypass threshold if the option is selected. If the application bypass triggers repeatedly. see the Supported Features by 3D Sensor Model table on page 208.000 ms. If your 3D Sensor and interface supports jumbo frames. see Configuring Automatic Application Bypass Monitoring on page 502. Automatic Application Bypass The automatic application bypass feature allows you to balance packet processing delays with your network’s tolerance for packet latency. WARNING! If a detection engine is bypassed. For more information on the health monitoring alert. Jumbo Frames Jumbo frames are Ethernet frames with a frame size greater than the standard 1518 bytes. it is most valuable in inline deployments. set the maximum frame size for the interface using the Create Interface Set page. RNA.9. Most gigabit Ethernet network interface cards support jumbo frames to increase efficiency. The automatic application bypass option is off by default. Automatic application bypass limits the time allowed to process packets through an IPS. Note also that frames larger than the configured maximum frame size are silently dropped by the sensor. The default setting is 750 milliseconds (ms). you do not need to set it in the Create Interface Set page.

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

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

Version 4. including a list of ungrouped sensors. You can set any jumbo frame size between 1518 and 9018 bytes. A list of sensors appears.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10. The following shows a 3D9900 interface set. inclusive. Defense Center Only Select one of the sensors from the list. 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. A list of network interfaces on the sensor appears. On the Defense Center only. Defense Center Only Select the sensor group containing the sensors where you want to create the interface set.1 Sourcefire 3D System Administrator Guide 215 . 12.9. Optionally. a list of sensor groups appears. You can also select the ungrouped sensors. 11.

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

as shown in the following graphic. in many cases you can improve performance by modifying the interface set to include only the inline interface pairs your network requires. the sensor might not correctly analyze your network traffic because a detection engine might see only half of the traffic.9. You can also use multiple interface pairs when your network employs asynchronous routing.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 3D Sensor deployment. you can refine policies for specific connected network segments and their requirements. If you include only one interface pair in an interface set. Later. 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.1 Sourcefire 3D System Administrator Guide 217 . Version 4. TIP! Although the default interface set on 3D Sensors includes all the available inline interface pairs.

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

You can set any jumbo frame size between 1518 and 9018 bytes. The following shows a 3D9900 interface set. a list of network interfaces on the sensor appears. IMPORTANT! Link state propagation and automatic application bypass are not supported on Sourcefire 3D Sensor Software for X-Series platforms. If you are creating an inline interface set.9. you can select a Bypass Threshold in milliseconds (ms). a list of paired network interfaces on the sensor’s fail-open cards appears. Optionally. including a list of ungrouped sensors. inclusive. You can. Optionally. however. and if you are configuring an interface set on a 3D9900.000 ms. select Automatic Application Bypass if your network is sensitive to latency.1 Sourcefire 3D System Administrator Guide 219 . On the Defense Center only. The default setting is 750 ms and the valid range is from 250 ms to 60. Optionally. 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. Select one of the sensors from the list. When the option selected. 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. If you are creating an inline with fail open interface set. 7. 8. a list of sensor groups appears. set jumbo frame options on the Crossbeam CLI. 9. Version 4.

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. If you are creating an inline with fail open interface set. see the Installation Guide for your sensor or sensor software. • For more information. 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. You can configure inline interface sets on 3D3800 and 3D5800 sensors to contain up to four pairs of interfaces.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10.9. TIP! 3D9800 sensors with earlier versions of firmware do not support tap mode. s0. For example. 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. but each pair must reside on a single fail-open network card. 11. Determining which interface name corresponds with a physical interface on your sensor depends on the model: • For 3Dx800 sensors. Add the interfaces to your interface set. inline and inline with fail open interface sets can include up to the total number of interface pairs on the sensor. • Use the Shift and Ctrl keys to select multiple interfaces or interface pairs at once. 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. select the Enable Tap Mode check box to use tap mode. the names that appear in the Available Interfaces list correspond to the slot number and interface location. Note that 3D Sensor Software for Crossbeam Systems X-Series does not support inline with fail open interface sets. On the 3D9800 sensor.1 Sourcefire 3D System Administrator Guide 220 .e0 corresponds to the leftmost interface on the network interface module (NIM) in I/O Slot 0 on the back of your appliance. Optionally. Repeat to add additional interface pairs. Inline with fail open interface sets on 3D3800 and 3D5800 sensors can also contain up to four pairs of interfaces. • If you are creating an inline interface set. for a 3DX800 or 3DX900 sensor. Version 4.

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

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

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

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

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

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

Using Detection Engines and Interface Sets Using Clustered 3D Sensors Chapter 6 4. you can identify them on the Sensor list page. Enter the following at the command line: failopen_pair. 2. Version 4. For information on establishing and separating clustered pairs. enter the following: failopen_pair. 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. see Managing a Clustered Pair on page 140. If you did not specify the correct interfaces. Then. enter the following: failopen_pair. After the cluster is established. if the interfaces in the interface set are eth2 and eth3. if you specified the correct interfaces.pl open eth#:eth# For example. shared configuration. the following message appears: Mode changed for interfaces eth2:eth3 The interfaces switch to bypass mode and the traffic is no longer analyzed.9. To return an inline fail open interface set to normal mode: Access: Admin 1. Select Operation > Sensors and note that clustered sensors have a peer icon. the following message appears: No failopen interface set configured for interfaces eth2:eth3. enter the correct password. When you establish a clustered pair configuration.pl close eth#:eth# For example.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.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. Log in as root onto the sensor and.. if the interfaces in the interface set are eth2 and eth3.1 Sourcefire 3D System Administrator Guide 227 . you combine the 3D9900 sensors resources into a single. Enter the following at the command line: failopen_pair.. at the prompt.

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

9. fir.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.example.example. where Z inline DE is the name of the detection engine.example. The master’s ethb0 and ethb1 pair are used for sensing connections. The master’s ethb2 and ethb3 pair connect to the slave’s ethb0 and ethb1 pair.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.com is the name of the master in the pair. a master/slave relationship is established between the two 3D9900 sensors. 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. SlaveSensorName) when you use them in: • • • • IPS policies PEP policies RNA detection policies compliance rules For example.1 Sourcefire 3D System Administrator Guide 229 . those pages are replaced with an informational page.example. the detection resources are listed as from both sensors. Understanding Interface Sets on Clustered 3D Sensors Requires: DC + 3D9900 After you set up the clustered pair. and fir. IMPORTANT! You cannot use the Policy & Response menu on the local GUI of a paired 3D Sensor. Version 4.com). The slave’s ethb2 and ethb3 pair are not functional and must not be connected when you establish the clustered pairing.com. Clustered 3D Sensors detection engines present their names in the form DetectionEngineName (MasterSensorName. 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.com). birch.example.1 Sourcefire 3D System Administrator Guide 230 . add data from both sensor of the detection engine to measure the total. fir. The Interface Sets page appears.example. in the form DetectionEngineName/MasterSensorName and DetectionEngineName/SlaveSensorName.example.com is the master sensor.example. where Z inline DE is the detection engine.com is the slave sensors. IMPORTANT! If you collect statistics from clustered 3D9900s. When you examine information from the clustered pair. it is listed as from both Z inline DE / birch.9. A clustered pair interface set displays both the master and the slave in the Sensor column. Managing Information from a Clustered 3D Sensor Requires: DC + 3D9900 Clustered sensors report information from each of the sensors. see Using Detection Engines on Clustered 3D Sensors on page 228. Analysis & Reporting tools display the information from each half of the detection engine independently. For example. For information about using interface sets in the detection engines of clustered 3D9900s. Do not attempt to change the interface settings while a clustered sensor is paired.com and from Z inline DE / fir.example. and fir.com. A Select Detection Engines list from the Intrusion Event Statistics page is show below.com. the clustered 3D Sensors detection engine could be: Z inline DE (birch.example.

The eStreamer settings are not automatically synchronized over the pair.1 Sourcefire 3D System Administrator Guide 231 . collect the data from both 3D9900s and ensure that you configure each 3D9900 identically.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. Version 4.9.

the RNA Events report appears under the RNA report category on the Report Designer page.1 Sourcefire 3D System Administrator Guide 232 .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. 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. the Intrusion Events report appears under the IPS report category and requires the IPS component on a 3D Sensor. You can run the report on the 3D Sensor or on the Defense Center that manages the sensor. You must have an RNA host license on the Defense Center managing your 3D Sensor. For example.9. Event reports include the data that you see on the event view pages for each type of event presented in a report format. 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.

see Editing Report Profiles on page 263. Version 4. For more information on how to create and save report profiles.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.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.9. You can create a new report profile through the use of the Report Designer. For information on modifying a predefined or existing report profile. see Understanding Report Profiles on page 241.

You can view. or delete previously generated reports. For more information on how to create and save report profiles. see Generating Reports from Event Views on page 235.9. if you use a Defense Center to manage your sensors. or SMB. see Editing Report Profiles on page 263. For information on how to generate a report for the data that appears in an event view. You can create a new report profile through the use of the Report Designer. download. For more information on how to manage your reports. You can run reports remotely from the Defense Center using the data on the sensors for the report. see Running Remote Reports on page 240. For more information on how to how to generate reports on managed sensors and view the results on the Defense Center. You can also specify which detection engine to use when generating the report. For more information on how to configure a Defense Center to store reports in a remote location using SSH. see Creating a Report Profile on page 246. see Using a Report Profile on page 260.1 Sourcefire 3D System Administrator Guide 234 . 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. NFS. see Managing Remote Storage on page 393. see Managing Generated Reports on page 237. For information on how to modify a report profile. Working with Report Profiles Requires: IPS or DC/ MDC You can use a predefined report profile to generate your report.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. Version 4. For information on how to generate a report from a report profile view. You can store reports locally or remotely.

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

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

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

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

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

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

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

and run the report manually or automatically. Version 4. As with custom report profiles that you create (see Creating a Report Profile on page 246).1 Sourcefire 3D System Administrator Guide 242 . You can modify field settings as appropriate. you can use a predefined report profile as a template for an event report.9. save the report with the new values.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.

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

1 Sourcefire 3D System Administrator Guide 244 . 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.9. 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. This report profile is available on the Defense Center or on a 3D Sensor with IPS.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.

9. 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. This report profile is available only on a Defense Center that manages 3D Sensors with RNA and IPS.1 Sourcefire 3D System Administrator Guide 245 . This report profile is available only on the Defense Center that manages 3D Sensors with RNA. 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. Priority.Working with Event Reports Understanding Report Profiles Chapter 7 twenty-four hours. 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.

selecting the Intrusion Events report type gives you the option to select which detection engines to search. save the report profile. or an image file. Note that all reports contain the option for a summary report and an image file. but not all options are available for all reports. selecting the Intrusion Events with Source Criticality report type does not provide that option. 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.1 Sourcefire 3D System Administrator Guide 246 .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. the criteria for the search. Report Sections. For more information on how to modify a predefined report profile. You perform three steps to create the a report profile: first. Version 4. and Report Options). and which workflows to examine. create the report profile in the system. second.9. For example. configure the options in each of three report areas (Report Information. such as a drill down of events. Creating a Report Profile Requires: IPS or DC/ MDC You can create the report profile by defining category and type. Working with Report Sections on page 255 explains how to specify which the sections to be included in the report. Not all options are available for all reports. queries. and then specifying which detection engines to search. and workflows to apply. finally. table view of events. . see Editing Report Profiles on page 263. and saving the report with the new values. Working with Report Information on page 248 explains how to set the type of report and how to specify which detection engines. Criticality Table View of Events Packets (limit 50 pages) Setting Operating System Summary Last week. in the IPS report category. and.

To create a report profile: Access: Any Analyst/ Admin 1. and how to use the option which emails the report. Click Create Report Profile. Continue with Defining Report Information on page 254. adds a custom . 3. Select Analysis & Reporting > Report Profiles. footer or logo.9. The Report Profiles page appears.1 Sourcefire 3D System Administrator Guide 247 . 2. The Report Designer page appears. TIP! You can also reach the Report Designer page from any event view by clicking Report Designer on the toolbar. Version 4.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). The following graphic shows the Defense Center version of the page.

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. search query.9. Depending upon your choices. Version 4. dashes. The following graphic is an example of the Report Information section. parentheses. The Report Name can be any name using 1-80 alphanumeric characters. Note that not all options are available for all categories or types. such as detection engine. periods. you will have other options to define. and spaces.1 Sourcefire 3D System Administrator Guide 248 . and workflow. and then selecting the report category and type.

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

9. or sliding time frame. However. Options vary depending upon which options you selected for Report Type. Options for the report type vary depending upon which Report Category is selected. 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. host attributes. and can include such options as Network Services by Count or Host Violations. expanding. Options vary depending upon Report Type. and IP-Specific or Impact and Priority. This option is available when searching for events. have limited report types and are self-explanatory. see Setting Event Time Constraints in the Analyst Guide. See the following sections for more information: • • IPS Category Report Types on page 251 RNA Category Report Types on page 252 Version 4. white list. 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.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. such a intrusion. or compliance events. the report types available to the IPS and RNA report categories are extensive and provide detailed options for defining your report profile. The Workflow allows you to select which workflow to examine. or when searching the network for RNA hosts. The Search Query identifies the search criteria for the report. and Search Query. For more information. such as the Compliance or Audit Log report categories. Detection Engine. Click in the current time field to open a pop-up window from which you can select a static. The Time option allows you to define the period of time for which the report is generated. client applications. and health monitoring. Some report categories. RNA.1 Sourcefire 3D System Administrator Guide 250 .

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

9. You can also edit a report profile to make changes to the resulting report. follow the instructions for your browser to save the report profile. 3. Click Delete next to the profile that you want to delete.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. and saving the report with the new values.1 Sourcefire 3D System Administrator Guide 263 . Select Analysis & Reporting > Report Profiles. 2. remember to change the name of the report profile in the Report Name field. Click Edit next to the profile that you want to delete. Click Save Report Profile. When prompted. modifying the field settings as appropriate. Access: Any Analyst/ Admin To edit a report profile: 1. The report profile is deleted. To delete a report profile: 1. Deleting Report Profiles Requires: IPS or DC/ MDC Access: Any Analyst/ Admin Use the following procedure to delete a report profile. 2. The report profile is saved with the name you specified in the Report Name field. Use the following procedure to edit a report profile. The Report Designer page appears and contains the current settings for the report profile. Select Analysis & Reporting > Report Profiles. 4. 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. The Report Profiles page appears. Make changes to the report areas as needed. The Report Profiles page appears. Version 4.

the process checks the local database to see if the user exists there and.1 Sourcefire 3D System Administrator Guide 264 . the authentication process checks the local database for this list. On the Defense Center.Managing Users Chapter 8 Administrator Guide If your user account has Administrator access. For more information. you can also set up user authentication via an external authentication server. If the user’s account uses internal authentication. rather than through the internal database. 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. such as a Lightweight Directory Version 4. if the user is not found locally.9. There are two kinds of authentication: internal and external. it queries an external server. you can manage the user accounts that can access the web interface on your Defense Center or 3D Sensor. If the account uses external authentication. This process is called authentication.

for a list of users. For users with either internal or external authentication.Managing Users Understanding Sourcefire User Authentication Chapter 8 Access Protocol (LDAP) directory server or a Remote Authentication Dial In User Service (RADIUS) authentication server. unless you change the user permissions manually. you can control user permissions. Users with external authentication receive the permissions either for the group or access list they belong to. Version 4.9. 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.1 Sourcefire 3D System Administrator Guide 265 .

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

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

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

directory on your network that organizes objects. you define settings that let you connect to an authentication server. When you create an authentication object. host statistics. 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. 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. Managing Authentication Objects Requires: DC Authentication objects are server profiles for external authentication servers. Version 4. such as user credentials. If you ever need to change a user's credentials. Optionally. and system logs) and maintenance functions (including task scheduling and backing up the system). and responses. in a centralized location. you can configure shell access authentication. You also select the directory context and search criteria you want to use to retrieve user data from the server. policies. containing connection settings and authentication filter settings for those servers. and delete authentication objects on the Defense Center.1 Sourcefire 3D System Administrator Guide 269 . You can create. Maintenance Administrators can access monitoring functions (including health monitoring. Creating LDAP Authentication Objects Requires: DC You can create LDAP authentication objects to provide user authentication services for an appliance.Managing Users Managing Authentication Objects Chapter 8 • • Policy & Response Administrators can manage intrusion rules. allows you to set up a .9. policies. you can change them in one place. rather than having to change them on the local appliances as well as on any other application that uses them. performance data. and responses. Multiple applications can then access those credentials and the information used to describe them. as well as compliance rules. manage.

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

for example.9. 7. IMPORTANT! If you are using a certificate to connect via TLS or SSL. 2. Optionally. Select LDAP from the Authentication Method drop-down list. you can set a timeout for the connection attempt to the primary server. 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. Optionally. modify the port used by the primary authentication server in the Primary Server Port field. the appliance then queries the backup server. the failover to the backup server does not occur. Configuring LDAP Authentication Settings Requires: DC If you specify a backup authentication server. 4. the appliance would query the backup server. 3. Optionally.1 Sourcefire 3D System Administrator Guide 271 . In addition.Managing Users Managing Authentication Objects Chapter 8 To identify an LDAP authentication server: Access: Admin 1. 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). Continue with Configuring LDAP Authentication Settings. 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. 5. IPv6 addresses are not supported. however. If. Version 4. 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. the primary server has LDAP disabled. modify the port used by the primary authentication server in the Backup Server Port field. Type a name and description for the authentication server in the Name and Description fields. 6. the host name in the certificate must match the host name used in this field.

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

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

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

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

the default access role defined in the Group Controlled Access Roles section is granted to the user. For this reason. however. Version 4. If a new user does not belong to any specified groups. the user is assigned the default minimum access role specified in the Group Controlled Access Roles section of the authentication object.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. If you configure any group settings. the user receives the access role for the group with the highest access as a minimum access role. assign additional rights.1 Sourcefire 3D System Administrator Guide 276 .9. the Authentication Method column on the User Management page provides a status of External . • • • 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. If a user’s group membership is not established in those recursions. new users belonging to specified groups inherit the minimum access setting for the groups where they are members. the Sourcefire 3D System limits the number of recursions of a search to four to prevent search syntax errors from causing infinite loops. You can.Locally Modified. If a user belongs to more than one configured group. the LDAP query is used exactly as it is configured on the LDAP server. 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. when a new user logs in. IMPORTANT! If you use a dynamic group. When you modify the access rights for an externally authenticated user.

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

see Configuring Authentication Profiles on page 329. Continue with Configuring Administrative Shell Access on page 278.1 Sourcefire 3D System Administrator Guide 278 . For more information on user access roles. For more information on managing authentication object order. or Crossbeam-based software sensors. Optionally. 6. 10. 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. 11. 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). Select the default minimum access role for users that do not belong to any of the specified groups from the Default User Role list. Specify a search filter that will retrieve entries for users you want to grant shell access. 3Dx800 sensors. For example. IMPORTANT! Sourcefire does not support external authentication for RNA Software for Red Hat Linux. 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 (Read Only) field. 8. 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. 9. type memberURL. type member.9. 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. if the memberURL attribute contains the LDAP search that retrieves members for the dynamic group you specified for default Admin access. Type the LDAP attribute that designates membership in a static group in the Group Member Attribute field. if the member attribute is used to indicate membership in the static group you reference for default Policy & Response Administrator access. Intrusion Agents. 7.Managing Users Managing Authentication Objects Chapter 8 5. TIP! Press the Ctrl key while clicking role names to select multiple roles in the list. Note that you can only configure shell access for the first authentication object in your system policy. see Adding New User Accounts on page 300. Version 4.

Version 4. in the Shell Access Filter field. If the user then is re-enabled.9. a warning displays when you save the authentication object to confirm that you meant to leave the filter blank. Shell users should log in using usernames with all lowercase letters. or select Same as Base Filter to use the same filter you specified when configuring authentication settings. Continue with Testing User Authentication. For example. shell access is controlled entirely though the shell access attribute you set. using the same home directory. even after they log in. WARNING! All shell users have sudoers privileges. You can use the Same as Base Filter option to run the query only once for both purposes. and when an LDAP shell access user account is disabled (by disabling the LDAP connection). 2. type the attribute type. but the user shell is set to /bin/false in /etc/password to disable the shell. Make sure that you restrict the list of users with shell access appropriately. the directory remains. Note that a home directory for each shell user is created on login. and the attribute value you want to use as a filter. the same query would be run twice. Addition and deletion of shell access users occurs only on the LDAP server. a comparison operator. if all network administrators have a manager attribute which has an attribute value of shell. enclosed in parentheses.Managing Users Managing Authentication Objects Chapter 8 With the exception of the root account. the shell is reset. you can set a base filter of (manager=shell). the LDAP query to retrieve users combines the base filter with the shell access filter.1 Sourcefire 3D System Administrator Guide 279 . which is unnecessarily time-consuming. If the shell access filter was the same as the base filter. and the filter you set here determines which set of users on the LDAP server can log into the shell. IMPORTANT! If you choose not to specify a shell access filter. To configure shell account authentication: Access: Admin 1. Shell users are not configured as local users on the appliance. To set a filter to retrieve administrative user entries based on attribute value. 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 User Name and Password fields. If the test succeeds. type JSmith.Managing Users Managing Authentication Objects Chapter 8 Testing User Authentication Requires: DC After you configure LDAP server and authentication settings. If that succeeds supply a user name and password to test with the specific user. For example. 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. you must apply a system policy with that object enabled to the appliance. 4. For the user name. click Save. You can also specify a fully-qualified distinguished name for the user. Version 4. either indicating success of the test or detailing what settings are missing or need to be corrected. the test fails even if the server configuration is correct. to test to see you can retrieve the JSmith user credentials at our example company. 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. To view details of test output. 2.1 Sourcefire 3D System Administrator Guide 280 . you can enter the value for the uid attribute for the user you want to test with. you can specify user credentials for a user who should be able to authenticate to test those settings. Test the server configuration without the additional test parameters first. Note that testing the connection to servers with more than 1000 users only returns 1000 users because of UI page size limitations. A message appears. Click Test.9. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. To test user authentication: Access: Admin 1. use the value for that attribute as the user name. select Show Details. To enable LDAP authentication using the object on an appliance. TIP! If you mistype the name or password of the test user. For more information. with the new object listed. The Login Authentication page appears. 3.

3. Version 4. with a backup server that has an IP address of 10.4.1 Sourcefire 3D System Administrator Guide 281 .10. This example illustrates important aspects of LDAP configuration.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.DC=example.9.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. Note that the connection uses port 389 for access and that connections to the server time out after 30 seconds of disuse.DC=it. • OU=security.10. 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.3.5.

allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account.9.5. with a backup server that has an IP address of 10. Like the OpenLDAP server. the user name template for the connection uses CN=%s.3. followed by the base distinguished name for the server directory. Note that all objects in the directory are checked because no base filter is set.11.11. 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.4.Managing Users Managing Authentication Objects Chapter 8 • Because this is an OpenLDAP server that uses CN as a part of each user’s name. Version 4. to indicate the template used to format user names retrieved from the server.3. no UI access attribute is specified. A shell access filter has been applied to this configuration.1 Sourcefire 3D System Administrator Guide 282 . • • • To support shell access. Aspects of this example illustrate important differences in this LDAP configuration from the configuration discussed in the OpenLDAP Example on page 281. the CN attribute is set as the shell access attribute. 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 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).

However. • • 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. this example shows a connection using a base distinguished name of OU=security.DC=com for the security organization in the information technology domain of the Example company.DC=example.9. As a result. Again. 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. 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.Managing Users Managing Authentication Objects Chapter 8 • Like the OpenLDAP server. the user name template for the connection uses address specification syntax documented in RFC 822 rather than the typical LDAP naming syntax. • Because this is a Microsoft Active Directory Server.DC=it. Note that the configuration includes a UI Access Attribute of userPrincipalName. Version 4. it uses the userPrincipalName attribute to store user names rather than the uid attribute.1 Sourcefire 3D System Administrator Guide 283 . because no base filter is applied to this server.

9.5.4.12.1 Sourcefire 3D System Administrator Guide 284 .DC=example. a shell access attribute value of sAMAccountName must be set for shell access to work on a Microsoft Active Directory server.12. Version 4.3. with a backup server that has an IP address of 10. However. 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.DC=it. as noted above.3. • As in the OpenLDAP server. allowing only those users who have a common name attribute value of jsmith to log into the appliance using a shell account.DC=com.Managing Users Managing Authentication Objects Chapter 8 • This example also has group settings in place. 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. a shell access filter has been specified for this server.

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.9. • • The user name template shown uses the uid attribute value as the user name. no UI access attribute is specified.DC=com for the security organization in the information technology domain of the Example company. the Server Port is set to 636.DC=example. note that this server does have a base filter of (cn=*smith). allowing all users with a common name ending in smith to log in using a shell account as well. Because user names can be retrieved from the uid attribute on this server. 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. • This example shows a connection using a base distinguished name of OU=security. However. • To allow shell access on the server. Version 4. the uid attribute is named as the Shell Access Attribute and the Same as Base Filter option for the shell access filter is set. Note that all objects in the directory are checked because no base filter is set.1 Sourcefire 3D System Administrator Guide 285 .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. A certificate has been uploaded to allow the SSL connection. The filter restricts the users retrieved from the server to those with a common name ending in smith.DC=it.

Managing Users Managing Authentication Objects Chapter 8 Editing LDAP Authentication Objects Requires: DC You can edit an existing authentication object. Select Operations > Configuration > Login Authentication. upload the new certificate and re-apply the system policy to your appliances to copy over the new certificate. Version 4. 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. The Create Authentication Object page appears. For more information. The Login Authentication page appears. Click Edit next to the object you want to edit. To edit an authentication object: Access: Admin 1. the settings in place at the time the policy was applied stay in effect until you re-apply the policy. If the object is in use in a system policy. 3. Modify the object settings as needed. 2.1 Sourcefire 3D System Administrator Guide 286 .9.

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

see Testing User Authentication on page 294. Configuring RADIUS Connection Settings Requires: DC When you create a RADIUS authentication object.9. the appliance then re-queries the primary server. 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. 6. For more information. If. If you specify a backup authentication server. you can set a timeout for the connection attempt to the primary 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. 5. for example. see Configuring Authentication Profiles on page 329 and Applying a System Policy on page 324. IMPORTANT! For FreeRADIUS to function correctly. Set the default user role. 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. Your changes are saved.1 Sourcefire 3D System Administrator Guide 288 . If the profiles for any of the users to authenticate return custom RADIUS attributes. see Configuring Administrative Shell Access on page 292. For more information. Identify the primary and backup authentication servers where you want to retrieve user data for external authentication and set timeout and retry values. you need to open both ports 1812 and 1813 on your firewall and on the FreeRADIUS server. 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.Managing Users Managing Authentication Objects Chapter 8 3. For more information. 4. 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. Optionally. For more information. specify the users or user attribute values for users that you want to receive specific Sourcefire 3D System access roles. 7. Test your configuration by entering the name and password for a user who should successfully authenticate. configure administrative shell access. the appliance would query the backup server. For more information. see Configuring RADIUS User Roles on page 290. the primary server has RADIUS disabled. see Defining Custom RADIUS Attributes on page 293. define those attributes. the appliance then rolls over to the backup server. see Configuring RADIUS Connection Settings on page 288.

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

that user receives all assigned access roles. see Defining Custom RADIUS Attributes on page 293. and you must remove the assigned user right on the user management page. 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 can also use attribute-value pairs. you can also configure a default access setting for those users detected by RADIUS that are not specified for a particular role. Continue with Configuring RADIUS User Roles. For more information on the user roles supported by the Sourcefire 3D System. 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 a user logs in. 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.Managing Users Managing Authentication Objects Chapter 8 10. when a new user logs in. see Configuring User Roles on page 304. If you add a user to the list for one or more specific role. to identify users who should receive a particular user role. You can. WARNING! If you want to change the minimum access setting for a user. you can type User-Category=Analyst in the RNA Analyst List field to grant that role to those users. For more information. Note that you need to define any custom attributes before you use them to set user role membership. 11. Type the number of times the primary server connection should be tried before rolling over to the backup connection in the Retries field.9. 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. if you know all users who should be RNA Analysts have the value Analyst for their User-Category attribute. You can select multiple roles on the Default User Role list. however. assign additional rights. Version 4. rather than usernames. 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.1 Sourcefire 3D System Administrator Guide 290 . you must reapply the system policy. 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. When you do so. 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. For example.

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

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

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

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

Policy & Response Administrator Access Modifying User Privileges and Options Requires: DC/MDC or 3D Sensor After adding user accounts to the system.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. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus. you must configure access rights for all accounts. 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. incidents. See Modifying Restricted Event Analyst Access Properties on page 307 for more information. including intrusion event views. For externally authenticated users. Policy & Response Administrators have access to the main toolbar and rule and policy-related options on the Policy & Response and Operations menus. including those that are externally authenticated. account options. including intrusion event views. Provides read-only access to IPS analysis features. Note that if you change the authentication for a user from externally authenticated to internally authenticated. Version 4. When you modify the access rights for an externally authenticated user.9. Provides access to the same features as Intrusion Event Analyst or RNA Event Analyst access.1 Sourcefire 3D System Administrator Guide 306 . Restricted event analyst users see only the main toolbar and analysis-related options on the Analysis & Reporting and Operations menus. the Authentication Method column on the User Management page provides a status of External . 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. However. or passwords at any time. assign additional rights. incidents. and reports. You manage those settings on the external server. however. you must supply a new password for the user. and reports. Intrusion Event Analysts see the main toolbar and IPS analysis-related options on the Analysis & Reporting and Operations menus.Locally Modified. you can modify access privileges. Note that password management options do not apply to users who authenticate to an external directory server. Provides access to rules and policy configuration. You can.

1 Sourcefire 3D System Administrator Guide 307 . See Configuring User Roles on page 304 for more information on configuring roles to grant access for Sourcefire 3D System functions. • • • 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.9. Optionally. 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. Version 4. The Edit User page appears. for users with event analyst roles. Select Operations > User Management. 3. See Managing User Password Settings on page 303 for information on changing password settings for internally authenticated users. The User Management page appears.Managing Users Managing User Accounts Chapter 8 To modify user account privileges: Access: Admin 1. See Adding New User Accounts on page 300 for information about adding new user accounts. 2. You can specify this information only after the user is added. 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. Click Edit next to the user you want to modify.

Managing Users Managing User Accounts Chapter 8 Restricted event analyst users have access to only a few sections of the web interface..9.1 Sourcefire 3D System Administrator Guide 308 . The Restricted Event Analyst Settings table shows the correlation between platform and access requirements for the restricted event analyst.included in the base set of rights for the restricted analyst role Version 4. 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 . Restricted Event Analyst Settings To allow the restricted event analyst to.... view the network map When these platforms are present.

1 Sourcefire 3D System Administrator Guide 309 .Managing Users Managing User Accounts Chapter 8 Restricted Event Analyst Settings (Continued) To allow the restricted event analyst to. The User Management page appears. on the Defense Center. Searches must be private. restricted event analyst users could delete the searches and enhance their access privileges. one for each of the event types. Select Operations > User Management.9... Version 4. 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 ..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. See Searching for Events in the Analyst Guide for more information.. IMPORTANT! You must have saved private searches available before you can add restricted event analyst values to a user account. If they are saved as public. 2. custom tables create and manage bookmarks view events from a custom table When these platforms are present. Click Edit next to the user to whom you want to grant restricted event analyst rights. and then apply each saved search to the account as described in the following procedure. generate (but not view) reports create (but not modify) incident reports change user-specific preferences such as the account password. To restrict event analyst access to events: Access: Admin 1. create multiple private saved searches. and event view settings create custom workflows and. time zone.

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

The Edit User page appears. The User Management page appears. 2. Next to the user name. 3. Note that you must manage externally authenticated user passwords on the LDAP or RADIUS server. click Reset Password next to the user account on the User Management page. Select Operations > User Management. To change a user’s password: Access: Admin 1. type the new password (up to 32 alphanumeric characters). click Edit. In the Password field.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. TIP! If you want to force a user to change the password on the next log-in.9.1 Sourcefire 3D System Administrator Guide 311 . Version 4.

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

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. An X indicates that the user can access the option.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.9.1 Sourcefire 3D System Administrator Guide 313 .

1 Sourcefire 3D System Administrator Guide 314 .9.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.

1 Sourcefire 3D System Administrator Guide 315 .9.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.

or Maintenance access can not see the Policy & Response menu at all. 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.1 Sourcefire 3D System Administrator Guide 316 .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.9. An X indicates that the user can access the option. RNA Event Analyst. Users with Intrusion Event Analyst. Policy & Response Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.

Operations Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.9.1 Sourcefire 3D System Administrator Guide 317 . An X indicates that the user can access the option. All users can access at least some options on the Operations menu. 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. 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.

Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.9.1 Sourcefire 3D System Administrator Guide 318 . 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.

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.1 Sourcefire 3D System Administrator Guide 319 . An X indicates that the user can access the option. 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.9. 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. All users can access at least some of the options on the toolbar.

9.1 Sourcefire 3D System Administrator Guide 320 . For example. 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. 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.

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

The Policy Name column includes its description. For information about configuring each aspect of the system policy. 4. 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.9. 2. Select Operations > 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 Version 4.1 Sourcefire 3D System Administrator Guide 322 . Click Create Policy. Type a name and description (up to 40 alphanumeric characters and spaces each) for your new policy. select an existing policy to use as a template for your new system policy. Click Save.Managing System Policies Creating a System Policy Chapter 9 To create a system policy: Access: Admin 1. The System Policy page appears. Your system policy is saved and the Access List page appears. From the drop-down list. 3. The Create page appears. 5.

1 Sourcefire 3D System Administrator Guide 323 . but remember to re-apply the policy as explained in Applying a System Policy on page 324. With the Policy Name and Policy Description fields at the top. You can change the policy name and description. For information about configuring each aspect of the system policy. Click Edit next to the system policy that you want to edit. The System Policy page appears. appears. including a list of the existing system policies. Access List. Select Operations > System Policy.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.9. To edit an existing system policy: Access: Admin 1. 2. the first section of the 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 Version 4.

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

The System Policy page appears.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. port 443 (Hypertext Transfer Protocol Version 4. Select Operations > System Policy. The policy is deleted. For information about configuring each aspect of the system policy. Click Delete next to the system policy that you want to delete. including a list of the existing system policies. Default system policies cannot be deleted. If the policy is still in use. it is used until a new policy is applied. By default. 2.9. Configuring the Parts of Your System Policy Requires: Any You can change various parts of your system policy.1 Sourcefire 3D System Administrator Guide 325 . 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. To delete a system policy: Access: Admin 1.

To delete one of the current settings. To operate the appliance in a more secure environment. To configure the access list as part of a new system policy. or SSH). the Access List page appears. which is used to access the command line. click Delete. In either case. click Create Policy. 2. and click Save. or HTTPS). 3. access to the appliance is not restricted. which is used to access the web interface and port 22 (Secure Shell. the access list does not take effect until you apply the system policy. you will lose access to the system when you apply the policy. The setting is removed. WARNING! By default. You can specify the access list either by creating a new system policy or by editing an existing policy. 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 326 . Version 4. Select Operations > System Policy. click Edit next to the system policy. 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”). The access list is part of the system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Secure.9. The System Policy page appears. 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. In either case. You have two options: • • To modify the access list in an existing system policy. are enabled for any IP address.

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

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

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

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

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

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

..9. if you specify 100 million intrusion events and apply that policy to a 3D Sensor). any health alert limits you set in the policy have no effect on the sensors. flow summaries. Note that if you apply a system policy to an appliance that does not support the maximum limit you specify (for example. if you use the Defense Center to apply the same system policy to itself and the 3D Sensors it manages. database limits that do not apply to a particular appliance are silently ignored.1 Sourcefire 3D System Administrator Guide 333 . or DC1000 100 million events on the DC3000 10 million events on the DC500. the maximum limit for the appliance is silently enforced. In addition.. 2. as well as flow events. 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. For example. Virtual Defense Center. 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. 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.. IMPORTANT! You cannot apply system policies to Crossbeam-based software sensors or Intrusion Agents. 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. The Database Event Limits on page 333 below describes the maximum number of records you can store in the databases on your appliance.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. Virtual Defense Center... and health events.

beginning with the oldest files.. and click Save. click Edit next to the system policy.. audit records remediation status events on a Defense Center the white list violation history of the hosts on your network. Select Operations > System Policy. In addition. Version 4. click Create Policy. You have two options: • • To modify the database settings in an existing system policy. 2. see Purging the RNA and RUA Databases on page 598. 100. unified files are deleted from the system..9. The System Policy page appears. To configure the database settings as part of a new system policy.. 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. For information on manually pruning the RNA and RUA databases. Provide a name and description for the system policy as described in Creating a System Policy on page 321. In either case. the Access List page appears. the oldest events and packet files are pruned until the database is back within limits..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. if the /volume disk partition reaches 85% of its capacity.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 Database Event Limits (Continued) The. 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.1 Sourcefire 3D System Administrator Guide 334 . See Configuring a Mail Relay Host and Notification Address on page 338 for information about generating automated email notifications when events are automatically pruned. To configure the maximum number of records in the database: Access: Admin 1..

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

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

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

Your changes do not take effect until you apply the system policy. The system policy is updated. See Applying a System Policy on page 324 for more information. Provide a name and description for the system policy as described in Creating a System Policy on page 321. and compliance event alerting (Defense Center only . the Access List page appears. Select Operations > System Policy. To configure the email settings as part of a new system policy. 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. impact flag. click Create Policy.requires RNA) use email for intrusion 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.9. click Edit next to the system policy. To configure a mail relay host: Access: Admin 1. You have two options: • • To modify the email settings in an existing system policy. 2. you can configure an email address that will receive notifications when intrusion events and audit logs are pruned from the database. Version 4.requires IPS) use email for health event alerting (Defense Center only) you must configure a mail host.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. and click Save. Click Save Policy and Exit. WARNING! Although DNS caching is enabled for the appliance. In either case. The System Policy page appears.1 Sourcefire 3D System Administrator Guide 338 . In addition.

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

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

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

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

see Combining Flow Summaries from External Responders in the Analyst Guide as well as Configuring RNA Detection Policy Settings in the Analyst Guide. 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. the table view contains no 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. in minutes. access data on individual flows) for a flow summary that involves an external responder. 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. and reports use external to indicate the hosts outside your monitored network. IMPORTANT! Make sure that the client application timeout value is longer than the update interval in the RNA detection policy. service. 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. For more information. This can reduce the space required to store flow data and can also speed up the rendering of flow data graphs. graphs. Event views. However.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. see Creating RNA Detection Policies in the Analyst Guide.1 Sourcefire 3D System Administrator Guide 343 . which can reduce the number of events sent to the Defense Center. before RNA drops a client application from the network map due to inactivity. protocol. 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. The default setting is 10080 minutes(7 days). However. instead of an individual IP address. if you enable this option and you attempt to drill down to the table view of flow data (that is. keep in mind that setting this option in the RNA detection policy requires that you set your flow data mode to Summary. Version 4. 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.9. This option is especially valuable if you want to prevent spoofed hosts from taking the place of valid hosts in the network map. For more information.

9. For more information.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. Duplicate flow events can be created if you use two RNA detection policies. Just as with RNA flow events. for example. see Drop Duplicate RNA Flow Events. if you use one policy to monitor both networks. Note that best practices are to use only one detection policy and to not overlap network segment coverage. best practices are to avoid creating duplicate NetFlow events. 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.1 Sourcefire 3D System Administrator Guide 344 . only the reporting detection engine for the flow initiator generates a flow event. not following best practices can degrade performance as the Defense Center attempts to resolve the conflicts. In that scenario. Version 4. and can also use excessive bandwidth. Duplicate flow events can also be created if you overlap network segment coverage with your RNA detection engines in your RNA detection policy. each of which is monitoring a separate network segment using separate detection engines. 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. Duplicate NetFlow events can be created. On the other hand. if two NetFlow-enabled devices export information about the same session.

For example. 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. as described in the following table. • Select the Use RNA Vulnerability Mappings check box if you want to use RNA vulnerability information to perform impact flag correlation. RNA collates fingerprint information from several sources. 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.1 Sourcefire 3D System Administrator Guide 345 . see Using Impact Flags to Evaluate Events in the Analyst Guide. Note that if you clear all the check boxes. intrusion events will never be marked with the red impact flag. 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. Version 4. You can select any or all of the check boxes in this section. For more information. the intrusion event will be marked with the red (Vulnerable) impact flag. control which vulnerability types to use for impact assessment. See Understanding RNA Host Input Event Types in the Analyst Guide for information about each event type. 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. see Mapping Third-Party Vulnerabilities in the Analyst Guide.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. For more information. • Select the Third Party Vulnerability Mappings check box if you want to use third-party vulnerability references 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. 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. select this option to use the Nessus vulnerability mappings. see Understanding Nessus Scans in the Analyst Guide or the Sourcefire 3D System Host Input API Guide. To provide the most reliable operating system and service identity information. if you scan using Nessus.9.

1 Sourcefire 3D System Administrator Guide 346 .9. unless there is an identity conflict. but does allow integration of imported application or scan results.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. 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. You can use the Multiple Fingerprinting page to rank scanner and application fingerprint sources by priority. Note. 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. that user input data overrides scanner and application data regardless of priority. Note that adding a scanner to this page does not add the full integration capabilities that exist for the Nmap and Nessus scanners. If you import data from a third-party application or scanner. RNA retains one identity for each source. see Enhancing Your Network Map in the Analyst Guide. or change the priority or timeout settings for existing sources. remember to make sure that you map vulnerabilities from the source to the RNA vulnerabilities in the network Version 4. however. identity data added by a scanner or application overrides identity data detected by RNA. For more information on current identities and how RNA selects the current identity. 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. By default. but only data from the highest priority application or scanner source is used as the current identity. By default. as indicated in the Multiple Fingerprint Settings table. You can add new active sources through this page. However.

from the Type drop-down list. Select Operations > System Policy. You have the following options: • To force manual conflict resolution of identity conflicts. select Scanner or Application. see Mapping Third-Party Vulnerabilities in the Analyst Guide. For more information. • To change the type of source. Days. • To use the RNA fingerprint when an identity conflict occurs. • To use the current identity from the highest priority active source when an identity conflict occurs. Type a name for the source.9. The System Policy page appears. select Active from the Automatically Resolve Conflicts drop-down list. select Passive from the Automatically Resolve Conflicts drop-down list. • 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. • 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. 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. Configuring Settings for RNA Requires: DC + RNA Use the following procedure to configure RNA settings in the system policy. select Hours. Version 4. or Weeks from the Timeout drop-down list and type the appropriate duration.1 Sourcefire 3D System Administrator Guide 347 . click Add in the Multiple Fingerprints page of the system policy. To specify RNA settings: Access: Admin 1. click the down arrow next to the source name.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 map. • To promote a source and cause the operating system and service identities to be used in favor of sources below it in the list. Scanner/ Application List You have several options: • To add a new source. click the up arrow next to the source name. select Disabled from the Automatically Resolve Conflicts drop-down list.

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

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

1 Sourcefire 3D System Administrator Guide 350 . including operating system and service identity data.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. The following diagram illustrates the automated subnet detection process. Note that you can configure the Defense Center to notify you of subnet recommendations via email so that you can make the changes manually. Version 4. or.9. if you configured the Defense Center to automatically apply recommendations. To get detailed information about the hosts in a subnet. and so on. you must explicitly assign an RNA detection engine to monitor that subnet. flow data. to notify you of any changes made.

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

Note that this option has no effect unless you enable daily recommendations. When RUA detects a user login for a user who is not already in the database.1 Sourcefire 3D System Administrator Guide 352 . RUA users are not added to the database based on SMTP logins. POP3. the Defense Center does not record them unless there is already a user with a matching email address in the database. and IMAP can introduce usernames not relevant to your organization due to network access from contractors. For example. 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. 7. In addition. The system policy is updated. See Applying a System Policy on page 324 for more information. Enable the Automatically Apply Daily Recommendations check box to automatically update and apply your RNA detection policies after RNA generates subnet recommendations. 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. Restricting RUA helps minimize username clutter and preserve RUA licenses. obtaining usernames through protocols such as AIM. RUA stops adding new users to the Defense Center database. and SIP logins always create duplicate user records. and other guests.9. Click Save Policy and Exit. Version 4. 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. visitors. Your changes do not take effect until you apply the system policy.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 6. 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. an RUA user is added to the Defense Center user database. This is because these logins are not associated with any of the user metadata that RUA obtains from an LDAP server. Oracle. AIM. After you reach your licensed limit.

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

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

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

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

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

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

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

Contrast the system settings. which controls aspects of an appliance that are likely to be similar across a deployment. with a system policy.9. Version 4. See Managing System Policies on page 320 for more information.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. which are likely to be specific to a single appliance.1 Sourcefire 3D System Administrator Guide 360 .

hostname. See Viewing and Modifying the Appliance Information on page 362 for more information. See Editing Network Interface Configurations on page 380 for more information. See Configuring Network Settings on page 377 for more information. If the time synchronization settings in the current system policy for the appliance is set to Manual. Time Displays the current time. On the Defense Center. enables you to establish communications with a Defense Center from the sensor. System Settings Options Option Information Description Allows you to view current information about the appliance. then you can use this page to change the time. Enables you to change options such as the IP address. and proxy settings of the appliance that were initially set up as part of the installation.Configuring System Settings Chapter 10 The System Settings Options table describes the options you can configure in the system settings. Allows you to view and modify the settings for the network interfaces on your appliance. See Understanding Licenses on page 364 for more information. 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. License Network Network Interface Process Version 4.9. See Configuring the Communication Channel on page 383 for more information.1 Sourcefire 3D System Administrator Guide 361 . See Configuring Remote Access to the Defense Center on page 386 for more information. 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. Remote Management On the 3D Sensor. 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. You can also change the appliance name.

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

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

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

For information on IPS. TIP! You can view your licenses by using the Product Licensing widget in the dashboard..1 Sourcefire 3D System Administrator Guide 365 ... and Sourcefire Defense Center Installation Guide. For information on adding a product license. see the Sourcefire Licenses table on page 365. RUA. For information on how to use virtual appliances.. Version 4. see Adding Feature Licenses on page 370. see Sourcefire 3D Sensor Installation Guide. use IPS on that appliance.9. a 3D Sensor or a Defense Center during installation so that you can. Product License to.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. Sourcefire Licenses You apply a. see Sourcefire Virtual Defense Center and 3D Sensor Installation Guide. To understand why and when to use these licenses. 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. For information on how to add a feature license. Virtual License a Defense Center at any time use virtual machines. see Understanding Feature Licenses on page 366. See Understanding the Product Licensing Widget on page 84 for more information. and so on. For information on how the various features function..

Version 4. the Sourcefire 3D System uses RNA detection engines on 3D Sensors to analyze NetFlow data. FreeBSD. IPS Software Sensors. NetFlow is available not only on Cisco networking devices. You must use a Defense Center to configure NetFlow data collection and to view the collected data. RUA Users and either RNA Hosts or the product license (or both). 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.. and your deployment must include at least one 3D Sensor with RNA that can communicate with your NetFlow-enabled devices. RUA Users. NetFlow NetFlow is an embedded instrumentation within Cisco IOS Software that characterizes network operation. attacks. Although you can use NetFlow-enabled devices exclusively to monitor your network..1 Sourcefire 3D System Administrator Guide 366 ... up-to-the-minute profile of your network correlate threat. NetFlow-enabled devices are widely used to capture and export data about the traffic that passes through those devices. Feature Licenses If you want to. and network intelligence with user identity information identify the source of policy breaches. NetFlows. You can deploy NetFlow-enabled devices on networks that your sensors cannot monitor. but can also be embedded in Juniper.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. RNA Hosts. see Introduction to NetFlow in the Sourcefire 3D System Analyst Guide. For more information. Standardized through the RFC process. 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.9. and OpenBSD devices. Intrusion Agents. and use NetFlow data to monitor those networks. endpoint. 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.

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

1 Sourcefire 3D System Administrator Guide 368 . Click License. In most cases. Version 4. see Sourcefire Crossbeam Installation Guide XOS.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. Select Operations > System Settings. see Managing Your Feature Licenses on page 370.9. To verify the product license file: Access: Admin 1. viewing. 2. The Information page appears. the user who sets up the appliance adds the software license as part of the process. For information on adding. The License page appears. Verifying Your Product License Requires: Any During installation. For more information. you do not need to re-install the license. and deleting feature licenses.

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

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

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

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

Displays the appliance’s MAC address. Indicates if the license is valid. Lists the number of monitored hosts added by the license. invalid. or if a temporary license has expired. or if a temporary license has expired. 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. Displays the appliance’s MAC address. Allows you to delete the feature license by clicking Delete. Displays the date and time that the feature license expires. The RNA Host License Columns table describes each column that appears in an RNA host license. Displays the feature serial number. Lists the number of NetFlow-enabled devices that the license allows you to use. Indicates if the license is valid. Displays the appliance model number.1 Sourcefire 3D System Administrator Guide 373 . invalid. Displays the appliance model number.Configuring System Settings Understanding Licenses Chapter 10 The NetFlow License Columns table describes each column that appears in a NetFlow license. 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. Displays the feature serial number.9. Version 4.

Indicates if the license is valid. Version 4. The Intrusion Agent License Columns table describes each column that appears in an intrusion agent license.1 Sourcefire 3D System Administrator Guide 374 . The RUA License Columns table describes each column that appears in an RUA host license. 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. Lists the number of monitored users added by the license. Allows you to delete the host license by clicking Delete. Allows you to delete the feature license by clicking Delete. Displays the date and time that the feature license expires. Intrusion Agent License Columns Column Feature ID Serial Number Description Displays the ID number that corresponds with the feature being licensed. invalid. Displays the appliance’s MAC address.9. Displays the feature serial number. Displays the feature serial number. 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.

Allows you to delete the feature license by clicking Delete. and other physical hardware constraints.9. Displays the appliance model number. Lists the maximum number of software agent connections allowed by the license. 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. invalid. or if a temporary license has expired. Version 4. IMPORTANT! These speeds are not a guaranteed throughput for the Virtual 3D Sensor you license. Displays the feature serial number. 100. or if a temporary license has expired. Displays the date and time that the feature license expires.1 Sourcefire 3D System Administrator Guide 375 . Maximum throughput is limited by other factors such as number of Virtual Machines on your VMware server.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. The Virtual 3D Sensor License Columns table describes each column that appears in an intrusion agent license. Lists the maximum number of Virtual 3D Sensors allowed by the license. 45. or 250MB). Displays the appliance’s MAC address. invalid. Displays the appliance model number. Displays the appliance’s MAC address. its connections. Displays the maximum capacity licensed for processing by the Virtual 3D Sensor (20. Indicates if the license is valid.

The Information page appears. Displays the appliance’s MAC address. Allows you to delete the feature license by clicking Delete. Displays the date and time that the feature license expires. invalid. The IPS Software License Columns table describes each column that appears in an IPS Software license. Displays the appliance model number. Indicates if the license is valid.9. Allows you to delete the feature license by clicking Delete.1 Sourcefire 3D System Administrator Guide 376 . To view or delete your feature licenses: Access: Admin 1. Version 4. or if a temporary license has expired. 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.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. Select Operations > System Settings. Displays the feature serial number.

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

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).Configuring System Settings Configuring Network Settings Chapter 10 local DHCP server. In most installations. protected network. you must set the address and netmask in dotted decimal form (for example: a netmask of 255. If. Version 4. the management interface is connected to an internal. Manual Network Configuration Settings Setting Management Interface Address and either IPv4 Netmask or IPv6 Prefix Length Description The IP address for the management interface. you can configure a proxy server to be used when downloading updates and SEUs. 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. the appliance retrieves its network settings from a local router. By default.0. the new name is not reflected in the syslog until after you reboot the appliance. The Information page appears. • For IPv4. the appliance is configured to directly connect to the Internet. To configure network settings: Access: Admin 1. in the case of IPv6. 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. • For IPv6. Select Operations > System Settings. you specify Router assigned.0).255.1 Sourcefire 3D System Administrator Guide 378 .9. This is the network through which Defense Centers and sensors communicate.

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

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

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

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

16. and if high availability is enabled.1 Sourcefire 3D System Administrator Guide 383 . click Run Command next to Restart Appliance Console. The Appliance Process page appears. 2. click Run Command next to Shutdown Appliance. in high availability deployments. The default port for communications between the Defense Center. click Run Command next to Reboot Appliance. The Information page appears. 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. To shut down the 3D Sensor. Note that this logs you out of the 3D Sensor.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. click Run Command next to Shutdown Defense Center. The default address range is 172. To reboot the system. to its Defense Center peer. To reboot the system. click Run Command next to Restart Defense Center Console. its managed sensors. Note that restarting the Defense Center may cause deleted hosts to reappear in the network map. For 3D Sensor • • • • Configuring the Communication Channel Requires: DC + 3D Sensor Version 4. To restart the Snort and RNA processes.0. Specify the command you want to perform: For DC/MDC • • • To shut down the Defense Center.Configuring System Settings Configuring the Communication Channel Chapter 10 To shut down or restart your appliance: Access: Admin 1. 3. To restart the 3D Sensor. click Run Command next to Reboot Defense Center. its high availability peer is 8305/tcp.9. The communication on port 8305 is bi-directional. To restart the Defense Center. Select Operations > System Settings. click Run Command next to Restart Detection Engines. Click Process. Note that this logs you out of the Defense Center. The Defense Center version of the page is shown below.0/ 16.

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

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

Click Edit next to the host whose Management Virtual Network you want to change. Registration Key .9.a unique alphanumeric ID for use when registering sensors in NAT environments.Configuring System Settings Configuring Remote Access to the Defense Center Chapter 10 version uses a default /16 (sixteen bit) CIDR address space. See Working in NAT Environments on page 112 for more information. Optionally. After appropriate management virtual network edits are made.registration key Unique NAT ID .1 Sourcefire 3D System Administrator Guide 386 . To edit the remote management virtual network: Access: Admin 1.the hostname of IP address. Three fields are provided for setting up communications between appliances: • • • Management Host . 3. The Remote Management page appears. 6. The Edit Remote Management page appears. 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. 2. click Regenerate VIP to regenerate the IP address used by the virtual network. 5. 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. 4. The Information page appears. which provides for a much greater number of appliances. Edit the name or host ID in the Name or Host fields as required. Select Operations > System Settings. Version 4. click Save.

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

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 Add New Sensor page appears. type a unique alphanumeric NAT ID that you want to use to identify the sensor. 10. After the sensor confirms communication with the Defense Center. 11. Version 4. in the Unique NAT ID field. WARNING! Make sure you use hostnames rather than IP addresses if your network uses DHCP to assign IP addresses. 7. type the same one-time use registration key that you used in step 5. If you used a unique ID in step 6. use both the Registration Key and the Unique NAT ID fields. 12. Type the IP address or the hostname of the sensor you want to add in the Host field. Access the Defense Center web interface and select Operations > Sensors. the Pending Registration status appears.9. In that case. type the same value in the Unique NAT ID field. The Sensors page appears.1 Sourcefire 3D System Administrator Guide 388 . In the Registration Key field. 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. Click New Sensor. Click Save. 6. 5. 9. In the Registration Key field. Optionally. 8.

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

its value should change to Being Used. To manually configure the time: Access: Admin 1. 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 following states may appear: • Being Used indicates that the appliance is synchronized with the 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 .9. time manually. if you see larger update times such as 300 seconds. • Available indicates that the NTP server is available for use but time is not yet synchronized. The Information page appears. • Unknown indicates that the status of the NTP server is unknown. For example. The NTP daemon automatically adjusts the synchronization times based on a number of conditions. or Not Available. Select Operations > System Settings. • Pending indicates that the NTP server is new or the NTP daemon was recently restarted. Available. 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. and positive values indicate that it is ahead. Negative values indicate that the appliance is behind the NTP server. • Not Available indicates that the NTP server is in your configuration but the NTP daemon is unable to use it. Instead. The status of the NTP server time synchronization. Last Update See Synchronizing Time on page 354 for more information about the time settings in the system policy. Over time. Offset The number of milliseconds of difference between the time on the appliance and the configured NTP server. Version 4.1 Sourcefire 3D System Administrator Guide 390 . The number of seconds that have elapsed since the time was last synchronized with the NTP server.

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

TIP! To remove a NetFlow-enabled device.1 Sourcefire 3D System Administrator Guide 392 . 5. Keep in mind that if you remove a NetFlow-enabled device from the system policy. enter the IP address of the NetFlow-enabled device you want to use to collect flow data. 2. click Delete next to the device you want to remove.9. see Introduction to NetFlow in the Analyst Guide. To add additional NetFlow-enabled devices. Select Operations > System Settings. The NetFlow Devices page appears. For more information on using NetFlow data with the Sourcefire 3D System. you should also remove it from your RNA detection policy. Click Save. In the IP Address field. including information on additional prerequisites. The Information page appears. Click Add Device to add a NetFlow-enabled device. To add NetFlow-enabled devices for flow data collection: Access: Admin 1. 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. You must configure these NetFlow-enabled devices to export NetFlow version 5 data.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). The list of NetFlow-enabled devices is saved. Click NetFlow Devices. 3. 4. 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. 6. repeat steps 3 and 4. see Editing an RNA Detection Policy in the Analyst Guide. Version 4. For more information.

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

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

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

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

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

Vulnerability database (VDB) updates affect the vulnerabilities reported by RNA as well as the operating systems. 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.0. Version 4.0). • • IMPORTANT! You cannot use the Update feature to update the SEU or Intrusion Agents. 4. For information on updating your SEU. For information on Intrusion Agents. client applications. for example. see Importing SEUs and Rule Files in the Analyst Guide.1). 4.9. and services that RNA detects. for example. Feature updates are more comprehensive than patches and generally include new features (and usually change the third digit in the version number. see the Intrusion Agent Configuration Guide.1).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. 4.9 or 5.9.1 Sourcefire 3D System Administrator Guide 398 . for example.Updating System Software Chapter 11 Administrator Guide Use the Update feature to update the Sourcefire 3D System.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

9. Version 4. those updates are not backed up. You can also choose to back up the following. system configuration files are saved in the backup file. While each organization’s backup plan is highly individualized. 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. The configuration files include information that uniquely identifies a sensor and cannot be shared.1 Sourcefire 3D System Administrator Guide 413 . 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.Using Backup and Restore Chapter 12 Administrator Guide Backup and restoration is an essential part of any system maintenance plan. 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 need to apply the latest SEU update after you restore. By default. WARNING! Do not use the backup and restore process to copy the configuration files between sensors.

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

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

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

8. select the Email when complete check box and type your email address in the accompanying text box.1 Sourcefire 3D System Administrator Guide 417 . to use secure copy (scp) to copy the backup archive to a different machine. 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. 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. type the full path and file name in the Additional Files field and click the plus sign (+). TIP! The compressed value that appears in the Selected Sum field is a conservative estimate of the size of the compressed file. to be notified when the backup is complete. Often. 9. TIP! You can repeat this step to add additional files. Optionally. If you want to include an additional file in the backup.Using Backup and Restore Creating Backup Files Chapter 12 7. Optionally. the file will be smaller.9. Version 4. 10. 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.

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

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

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

TIP! After the Defense Center verifies the file integrity.9. in megabytes “Yes” indicates the backup includes event data. Click with the backup file selected to restore it on the appliance. If you use remote storage. After you complete the restoration process. type. refresh the System Backup Management page to reveal detailed file system information. and version. Click with the backup file selected to view a list of the files included in the compressed backup file. select Enable Remote Storage for Backups to enable or disable remote storage at the top of the System Backup Management page. On Series 2 Defense Centers. Note that you can only restore a backup to an identical appliance type and version. If you use local storage. 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.Using Backup and Restore Restoring the Appliance from a Backup File Chapter 12 4. backup system. the protocol. Backup Management Column System Information Date Created File Name Location Size (MB) Events? View Restore Description The originating appliance name. 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. and backup directory are listed at the top of the page. The backup file is uploaded and appears in the backup list.1 Sourcefire 3D System Administrator Guide 421 . 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. you must apply the latest SEU. Version 4. Click Backup Management on the toolbar to return to the System Backup Management page.

click to send the backup to the designated remote backup location. Click with the backup file selected to delete it.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. A Series 2 Defense Center version of the page is shown. The System Backup Management page appears. To restore the appliance from a backup file: Access: Admin 1. On a Series 2 Defense Center when you have a previouslycreated local backup selected. Version 4. Select Operations > Tools > Backup/Restore.1 Sourcefire 3D System Administrator Guide 422 .9.

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

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

1 Sourcefire 3D System Administrator Guide 425 .Scheduling Tasks Chapter 13 Administrator Guide You can schedule many different types of administrative tasks to run at scheduled times. You should always schedule tasks like these to run during periods of low network use. Version 4. 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.9. 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.

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. Version 4. Editing Scheduled Tasks on page 461 describes how to edit an existing task. Automating Recommended Rule State Generation on page 456 provides procedures for scheduling automatic update of intrusion rule state recommendations based on RNA data. Deleting Scheduled Tasks on page 461 describes how to delete one-time tasks and all instances of recurring tasks. Automating Nmap Scans on page 454 provides procedures for scheduling Nessus scans. Synchronizing Nessus Plugins on page 452 provides procedures for synchronizing your sensor with the Nessus server. Viewing Tasks on page 458 describes how to view and manage tasks after they are scheduled. Automating SEU Imports on page 444 provides procedures for scheduling rule updates. and installation of software updates. Automating Software Updates on page 430 provides procedures for scheduling the download.1 Sourcefire 3D System Administrator Guide 426 . push. You must recreate the recurring task schedule on a newly activated Defense Center when it changes from inactive to active.9. push. Automating Backup Jobs on page 428 provides procedures for scheduling backup jobs. Automating Vulnerability Database Updates on page 437 provides procedures for scheduling the download. IMPORTANT! You cannot configure a recurring task schedule on the inactive Defense Center in a high availability pair of Defense Centers. and installation of software updates. Automating Reports on page 448 provides procedures for scheduling reports. Automating Intrusion Policy Applications on page 446 provides procedures for scheduling intrusion policy applications. • • • • • • • • • • 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.

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

Use the drop-down list to select the day of the month when you want to run the task. TIP! You must design a backup profile before you can configure it as a scheduled task. To automate backup tasks: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 428 . see Creating Backup Profiles on page 418. For information on backup profiles. If you selected Month(s) in the Repeat Every field. The remaining options on the Add Task page are determined by the task you are creating. Select Operations > Tools > Scheduling. If you selected Week(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. 9. Version 4.9.Scheduling Tasks Automating Backup Jobs Chapter 13 8. Select the check boxes next to the days of the week when you want to run the task. The Scheduling page appears. The Add Task page appears. a Repeat On field appears. Click Add Task. 2. a Repeat On field appears.

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

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

9).1 or 4. Select Operations > Tools > Scheduling.8. The Add Task page appears. 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. On the Defense Center.9. For larger. you must manually upload. Version 4. To automate software updates: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 431 . This behavior also has implications for appliances that cannot access the Support site at all.1). and install the upgrade files. the task does not complete. 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. Click Add Task. 2. Specifically. You can use this task to schedule download of updates you plan to push or install manually. If you want to have more control over this process.8.2. more comprehensive updates (such as 4. such as 4. push. you can also automate vulnerability database (VDB) updates.8 or 4. The Scheduling page appears. Instead you must manually push or install the updates as described in Updating System Software on page 398.Scheduling Tasks Automating Software Updates Chapter 13 Support site to ensure that you have the latest version of the update. if you manually download an update to an appliance that cannot access the Support site. If your appliance cannot access the Support site. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance).

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

in the Comment field. Optionally. To push software updates to managed sensors: Access: Maint/Admin 1. Click Add Task. Click Save.9. When you push software updates to managed sensors.Scheduling Tasks Automating Software Updates Chapter 13 7. you must push the software to the managed sensors before installing. TIP! The comment field appears in the View Tasks section of the page. in the Email Status To: field. When you create the task to push software updates to managed sensors. The Scheduling page appears. The task is created. Instead you must manually push the update as described in Updating System Software on page 398. Select Operations > Tools > Scheduling. Version 4. See Configuring a Mail Relay Host and Notification Address on page 338 for more information about configuring a relay host. make sure you allow enough time between the push task and a scheduled install task for the updates to be copied to the sensor. Optionally. 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. 9. spaces.1 Sourcefire 3D System Administrator Guide 433 . information about the push process status is reported on the Tasks page. or periods. Automating Software Pushes Requires: DC/MDC If you are installing software or vulnerability database updates on managed 3D Sensors. 2. you cannot schedule pushes to managed sensors. so you should try to keep it relatively short. 8. 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 Add Task page appears. type a comment using up to 255 alphanumeric characters.

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

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

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

Installing the VDB update. make sure that you download and install VDB updates and SEUs on a regular basis. 2. 3. Click Save. Download the VDB update on your Defense Center. This ensures that your Defense Center is correctly setting the impact flag on the intrusion events generated by the traffic on your network. 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 437 . See Viewing the Status of Long-Running Tasks on page 600 for more information. you must automate two separate steps: 1. TIP! If your Sourcefire 3D System deployment includes IPS and RNA monitoring the same network segments. When automating VDB updates for managed sensors with RNA. 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. you must schedule three tasks in this order: 1. Optionally. 2.9. thereby ensuring that RNA is using the most up-to-date information to evaluate the hosts on your network.Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 9. Install the VDB update on the Defense Center and on those managed sensors. if you schedule a task to install an update and the update has not fully Version 4. in the Email Status To: field. type the email address (or multiple email addresses separated by commas) where you want status messages sent. 10. You can use the scheduling feature to download and install the latest VDB updates. Push the VDB update to your managed 3D Sensors that are using the RNA component. The scheduled software installation task is added. Always allow enough time between tasks for the process to complete. Downloading the VDB update. When automating VDB updates for your Defense Center. For example. 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.

Scheduling Tasks Automating Vulnerability Database Updates Chapter 13 downloaded. the installation task will not succeed. Note that if you manually download an update to an appliance that cannot access the Support site. If you want to have more control over this process. 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. Version 4. The Scheduling page appears. Select Operations > Tools > Scheduling.9. You must download the VDB on the Defense Center and push it to the sensor.1 Sourcefire 3D System Administrator Guide 438 . However. you cannot schedule either pushes to managed sensors (on the Defense Center) or installs (on any appliance). IMPORTANT! You cannot download the VDB using a scheduled task on a sensor. 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. Instead you must manually push or install the updates as described in Updating System Software on page 398. To automate VDB updates: Access: Maint/Admin 1. The Add Task page appears. Click Add Task. it will install the downloaded VDB update when it runs the next day. 2. if the scheduled installation task repeats daily.

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

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

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

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

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

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

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

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

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

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

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

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

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

or periods. type a comment using up to 255 alphanumeric characters. Optionally. 8. Optionally. In the Job Name field. 5. spaces. See Configuring a Recurring Task on page 426 for details. select the scan target that defines the target hosts you want to scan. TIP! The comment field appears in the View Tasks section of the page. Version 4. 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. Specify how you want to schedule the task. 6. The task is created. in the Email Status To: field. type the email address (or multiple email addresses separated by commas) where you want status messages sent. in the Comment field. type a name using up to 255 alphanumeric characters. use the drop-down lists to specify the start date and time. TIP! The Current Time field indicates the current time on the appliance. In the Nessus Remediation field. 7. 10. so you should try to keep it relatively short. • For one-time tasks. In the Nessus Target field. 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.Scheduling Tasks Synchronizing Nessus Plugins Chapter 13 4. Click Save. • For recurring tasks. select the Nessus remediation for the Nessus server where you want to run the scan. spaces. you have several options for setting the interval between instances of the task. 9.9. or dashes.1 Sourcefire 3D System Administrator Guide 452 . 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.

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

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

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

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

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

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

You can perform the following tasks using the calendar view: • • Click << to move back one year. Click < to move back one month.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. To view scheduled tasks using the calendar: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 459 . Select Operations > Tools > Scheduling. 2. The Scheduling page appears.9. Version 4.

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

If you delete a task that is scheduled to run once. 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. The Edit Task page appears showing the details of the task you selected. including the start time. Click either the task that you want to edit or the day on which the task appears. Select Operations > Tools > Scheduling. the job name.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. Deleting Scheduled Tasks There are two types of deletions you can perform from the Schedule View page. This feature is especially useful if you want to test a scheduled task once to make sure that the parameters are correct. Your change are saved and the Scheduling page appears again. Locate the task you want to edit in the table and click Edit. 2. 4. To edit an existing scheduled task: Access: Maint/Admin 1.1 Sourcefire 3D System Administrator Guide 461 . only that task is deleted.9. You cannot change the type of job. Version 4. once or recurring. The Task Details table containing the selected task or tasks appears. after the task completes successfully. The Scheduling page appears. all instances of the task are deleted. Edit the task to meet your needs. Click Save to save your edits. If you delete an instance of a recurring task. 3. The remaining options are determined by the task you are editing. Later. you can change it to a recurring task. and how often the task runs. You can delete a specific one-time task that has not yet run or you can delete every instance of a recurring task.

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

Version 4. 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. and statistics for the Data Correlator and RNA processes for the current day.1 Sourcefire 3D System Administrator Guide 463 .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. see Understanding Health Monitoring on page 483. all on a single page. You can also monitor both summary and detailed information on all processes that are currently running on the Defense Center or 3D Sensor. For more information. you can also use the health monitor to monitor disk usage and alert on low disk space conditions. For example. on the Host Statistics page you can monitor basic host statistics. intrusion event information.

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

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

Version 4.Monitoring the System Viewing Host Statistics Chapter 14 The RNA Process Statistics table describes the statistics displayed for the RNA process.User (%) CPU Usage . and the total number in the database. If you manage your sensor so that intrusion events are not stored locally. 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. 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. you can also view the time and date of the last intrusion event.9.1 Sourcefire 3D System Administrator Guide 466 .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. This is also the case for 3D Sensors that cannot store events locally. 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.

9. Select Operations > Monitoring > Statistics. Version 4. The Statistics page appears. The Defense Center version of the page is shown below.1 Sourcefire 3D System Administrator Guide 467 .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. 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.

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

unless the value is followed by m.process is in sleep mode • T .process is runnable (on queue to run) • S . which indicates megabytes) The amount of resident paging files in memory (in kilobytes. Version 4.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.process is in uninterruptible sleep (usually Input/Output) • N .process has a positive nice value • R . 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.Monitoring the System Viewing System Process Status Chapter 14 The Process Status table describes each column that appears in the process list.process is paging • X . which indicates megabytes) The process state: • D .process is dead • Z . The Statistics page appears.process is defunct • < . unless the value is followed by m.process is being traced or stopped • W . which is a value that indicates the scheduling priority of a process. Select Operations > Monitoring > Statistics.1 Sourcefire 3D System Administrator Guide 469 . Values range between -20 (highest priority) and 19 (lowest priority) The memory size used by the process (in kilobytes.9.

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. select the device or devices you want to view process statistics for and click Select Devices.9. Version 4. and specific information about each running process. see Understanding Running Processes on page 471. • • • • • • • • • 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. listing general process status that includes the number and types of running tasks. Click the down arrow next to Processes. On the Defense Center. the current time. indicating a higher priority) Nice values indicate the scheduled priority for system processes and can range between -20 (highest priority) and 19 (lowest priority). and swap information. the current system uptime.1 Sourcefire 3D System Administrator Guide 470 . 3.Monitoring the System Viewing System Process Status Chapter 14 2. the system load average. memory. CPU. The process list expands.

This table is not an exhaustive list of all processes that may run on an appliance. Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files.9. 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. 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.Monitoring the System Understanding Running Processes Chapter 14 To collapse the process list: Access: Maint/Admin Click the up arrow next to Processes. and checks for working SSL and valid certificate authentication. Daemons always run. 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 . They ensure that services are available and spawn processes when required. 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. The process list collapses. and executable files are run when required.

sfmb) to handle the request sftroughd Version 4. Currently used only by health monitoring to send health events and alerts from a 3D Sensor to a Defense Center or.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 .1 Sourcefire 3D System Administrator Guide 472 . using an sftunnel connection to the appliance. restarts any process that fails unexpectedly Manages reports Manages RNA reports Manages safe mode operation of the database. 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.requires RNA) sftimeserviced (Defense Center only) sfmbservice (requires IPS) Description Manages the Linux kernel update process. 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. between Defense Centers Listens for connections on incoming sockets and then invokes the correct executable (typically the Sourcefire message broker.9. which performs disk synchronization Manages Sourcefire 3D System database processes Manages the Network Time Protocol (NTP) process Manages all Sourcefire processes. in a high availability environment. starts required processes.

supports extended set of regular expressions not supported in standard grep Version 4.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. 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. flow data. 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 .9. The System Executables and Utilities table describes the executables that you may see on the Process Status page.

9. See Configuring the Access List for Your Appliance on page 325 for more information about access configuration.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. 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 . 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. 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.

correlating acquired data with the RNA fingerprint database. 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.1 Sourcefire 3D System Administrator Guide 475 . handles communication between Defense Centers and sensor. 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. heartbeat used to maintain contact between a sensor and Defense Center Indicates a message broker process. indicating that the appliance is active. 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.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.9.

IMPORTANT! Because of the way traffic is processed on 3Dx800 sensors. last day.9. last week. The Defense Center version of the page is shown below. 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. number of megabits per second. word. or average bytes per packet.1 Sourcefire 3D System Administrator Guide 476 . To view the IPS performance statistics: Access: Maint/Admin Select Operations > Monitoring > Performance > IPS. average number of bytes per packet. megabits per second. The IPS page appears. IPS performance statistics refer only to the data stored locally on the 3D Sensor. and the percent of packets uninspected by Snort. Version 4.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. These graphs can show statistics for the last hour. 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. performance statistics for those sensors are under reported. Graphs can be generated to reflect number of intrusion events per second.

if you reload a graph quickly. 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. The IPS Performance Statistics Graph Types table lists the available graph types. The IPS page appears. It may also indicate that both segments have a drop rate of 50%. select the type of graph you want to create. select the detection engines whose data you want to view. 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. Therefore. Version 4.Monitoring the System Viewing IPS Performance Statistics Chapter 14 New data is accumulated for statistics graphs every five minutes. Select Operations > Monitoring > Performance > IPS. then an average of 50% may indicate that one segment has a 90% drop rate and the other has a 10% drop rate. From the Select Device list. 3. 2. The graph only represents the total % drop when there is a single detection resource assigned to a selected detection engine. From the Select Graph(s) list.1 Sourcefire 3D System Administrator Guide 477 . the data may not change until the next five-minute increment occurs. To generate IPS performance statistics graphs: Access: Maint/Admin 1.9. The Defense Center version of the page is shown below.

To save the graph: Access: Maint/Admin Right-click on the graph and follow the instructions for your browser to save the image. 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. you can save the graph as a graphic file for later use. You can choose from last hour. or last month.Monitoring the System Viewing RNA Performance Statistics Chapter 14 4. last week. The graph appears. Saving IPS Performance Statistics Graphs Requires: IPS or DC/MDC + IPS After you have generated an IPS performance statistics graph. 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. Click Graph. last day. From the Select Time Range list. displaying the information you specified.1 Sourcefire 3D System Administrator Guide 478 . 5. select the time range you would like to use for the graph.9.

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. New data is accumulated for statistics graphs every five minutes. or last month of operation. The RNA Performance Statistics Graph Types table lists the available graph types. To access the RNA Performance page: Access: Maint/Admin Select Operations > Monitoring > Performance > RNA. if you reload a graph quickly. 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 week. in thousands. the data may not change until the next five-minute increment occurs. last day.Monitoring the System Viewing RNA Performance Statistics Chapter 14 • • the number of packets. Therefore. 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 page appears.1 Sourcefire 3D System Administrator Guide 479 .9.

3. TIP! You can select multiple graphs by holding down the Ctrl or Shift keys while clicking on the graph type. From the Select Target list. last week. select the type of graph you want to create. or the detection engines that you want to include. the Select Graph(s) list adjusts to display the available graphs. From the Select Time Range list.9. select the Defense Center. You can choose from last hour. The RNA page appears. or last month. Version 4. Depending on whether you select a detection engine or a sensor. select the time range you would like to use for the graph. Select Operations > Monitoring > Performance > RNA. last day. 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. 2.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 managed 3D Sensors. 4. From the Select Graph(s) list.1 Sourcefire 3D System Administrator Guide 480 .

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

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

if you want to see all the occurrences of CPU usage with a certain percentage. Version 4.9. you can search for the CPU usage module and enter the percentage value. disk. you can set up an email alert. A health alert is an association between a standard alert and a health status level. You can also configure email. 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. You can then create a health alert that triggers that email alert whenever CPU. Individual appliance health monitors let you drill down into health details for a specific appliance. You can also search for specific health events. SNMP or syslog alerting in response to health . You can set alerting thresholds to minimize the number of repeating alerts you receive.1 Sourcefire 3D System Administrator Guide 483 . then drill down into status details if needed. For example. or memory usage reaches the Warning level you configure in the health policy applied to that appliance. 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 open a table view of occurrences of a specific event. The Health Monitor page provides a visual summary of the status of all appliances on your system. You can also view health events in the standard Sourcefire 3D System table view. or you can retrieve all the health events for that appliance. Pie charts and status tables on the Health Monitor page visually represent the health status for monitored appliances. so you can check status at a glance. From an individual appliance’s health monitor. events.

see Applying Health Policies on page 528. 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. Version 4. For details on applying policies. the Data Correlator process.1 Sourcefire 3D System Administrator Guide 484 . see Modifying User Privileges and Options on page 306. only users with Admin access privileges can access system health data. IMPORTANT! Except for the Defense Center.9. When you create health policies. For more information on available default health policies you can apply to an appliance. which also monitors CPU. you can create a policy that monitors just the intrusion event rate and the IPS process. and memory usage. see Creating Health Policies on page 497. For example. and traffic status. disk. or you can apply the default policy. For more information on assigning user privileges.Using Health Monitoring Understanding Health Monitoring Chapter 15 Because health monitoring is an administrative activity. you choose which tests to run to determine appliance health. For more information on health policies and the health modules you can run to test system health. see Predefined Health Policies on page 490. to monitor the health of a 3D Sensor with IPS. You can also apply one of the five default health policies to each appliance. 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 have to apply a health policy to that appliance. If you want to monitor the health of a managed appliance. For more information on creating customized health policies.

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

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

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

The Health Policy Configuration page appears. Configure settings on each module you want to use to test the health status of your appliances. 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. 8.Using Health Monitoring Configuring Health Policies Chapter 15 7.9. Select Save to save the policy information.1 Sourcefire 3D System Administrator Guide 499 .

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. 9. To configure a policy run time interval: Access: Maint/Admin 1. Version 4. select Policy Run Time Interval. The maximum run time interval you can set is 99999 minutes. WARNING! Do not set a run interval of less than five minutes. even if the policy that contains the module has been applied to an appliance. For more information on applying health policies. The Health Policy Configuration . You must apply the policy to each appliance for it to take effect. On the Health Policy Configuration page. Click Save to save the policy.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. see Applying Health Policies on page 528.1 Sourcefire 3D System Administrator Guide 500 . Disabled modules do not produce health status feedback.Policy Run Time Interval page appears.9.

select the other module from the list at the left of the page. enter the time in minutes that you want to elapse between automatic repetitions of the test.1 Sourcefire 3D System Administrator Guide 501 . See Applying Health Policies on page 528 for more information. The Health Policy Configuration . if you click Cancel. If the Defense Center does not detect a heartbeat from a appliance. 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. To configure Appliance Heartbeat health module settings: Access: Maint/Admin 1.Using Health Monitoring Configuring Health Policies Chapter 15 2. To return to the Health Policy page without saving any of your settings for this module. 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. click Cancel. 3. as an indicator that the appliance is running and communicating properly with the Defense Center. the status classification for this module changes to Critical. whichever comes first. you discard all changes. Version 4. 2. Use the Appliance Heartbeat health status module to track whether the Defense Center receives heartbeats from managed appliances.9. You have three options: • • • To save your changes to this module and return to the Health Policy page. select Appliance Heartbeat.Appliance Heartbeat page appears. In the Run Interval (mins) field. To temporarily save your changes to this module and switch to another module’s settings to modify. In the Health Policy Configuration page. If you click Save Policy and Exit when you are done. click Save Policy and Exit. all changes you made will be saved. 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. you discard all changes. To temporarily save your changes to this module and switch to another module’s settings to modify. The Automatic Application Bypass Status page appears. select Automatic Application Bypass Status. For more information on automatic application bypass. To return to the Health Policy page without saving any of your settings for this module. this module generates an alert. click Cancel.1 Sourcefire 3D System Administrator Guide 502 .Using Health Monitoring Configuring Health Policies Chapter 15 3. If a bypass occurs. 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.9. if you click Cancel. That status data feeds into the health monitor. To configure automatic application bypass monitoring status: Access: Maint/Admin 1. Version 4. In the Health Policy Configuration page. all changes you made will be saved. You must apply the health policy to the appropriate appliances if you want your settings to take effect. 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. click Save Policy and Exit. 2. see Automatic Application Bypass on page 212. 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.

See Applying Health Policies on page 528 for more information. In the Health Policy Configuration page. and the Critical limit must be greater than the Warning limit. click Cancel.Using Health Monitoring Configuring Health Policies Chapter 15 3. the Critical limit is set to 52 degrees Celsius and the Warning limit is set to 50 degrees Celsius. If the CPU temperature on the monitored sensor exceeds the Warning limit. if you click Cancel. By default. you discard all changes. all changes you made will be saved.1 Sourcefire 3D System Administrator Guide 503 . Use the CPU Temperature health status module to set CPU temperature limits. That status data feeds into the health monitor. Overheating a CPU can damage the processing unit. You must apply the health policy to the appropriate 3D Sensor if you want your settings to take effect. 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. To configure CPU temperature health module settings: Access: Maint/Admin 1. select the other module from the list at the left of the page. 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. select CPU Temperature. 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. the status classification for that module changes to Warning. The maximum temperature you can set for either limit is 100 degrees Celsius.CPU Temperature page appears. If the CPU temperature on the monitored sensor exceeds the Critical limit. You have three options: • • • To save your changes to this module and return to the Health Policy page.9. Version 4. If you click Save Policy and Exit when you are done. the status classification for that module changes to Critical.

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

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

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

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

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

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

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

select the other module from the list at the left of the page. 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. and the Critical limit must be higher than the Warning limit. See Applying Health Policies on page 528 for more information. 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. In the Health Policy Configuration page. if you click Cancel. the status classification for that module changes to Warning.Event Stream Status page appears. you discard all changes. 3. The maximum number of seconds you can set for either limit is 600. 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. If the wait exceeds the number of seconds configured in the Warning Seconds since last event limit. The Health Policy Configuration . that causes an alert to be generated. select Event Stream Status. That status data feeds into the health monitor. click Cancel.9. before triggering a critical health status. enter the maximum number of seconds to wait between events. You have three options: • • • To save your changes to this module and return to the Health Policy page. To configure Event Stream Status health module settings: Access: Maint/Admin 1. click Save Policy and Exit. The minimum number of seconds is 300. in seconds. To return to the Health Policy page without saving any of your settings for this module. 2. Select On for the Enabled option to enable use of the module for health status testing. In the Critical Seconds since last event field.Using Health Monitoring Configuring Health Policies Chapter 15 5. If the wait exceeds the Critical Seconds since last event limit. You can configure the elapsed duration between events. Version 4.1 Sourcefire 3D System Administrator Guide 511 . the status classification for that module changes to Critical.

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

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

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

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

If you click Save Policy and Exit when you are done. enter the number of events per second that should trigger a warning health status. Use the IPS Process health status module to monitor the health of the IPS process on a sensor. The first time the module checks and no restarts have occurred since the last test. enter the number of events per second that should trigger a critical health status. the module adds one to the restart count. You can configure how many restarts trigger a change in the health status for the process. If any restarts occur. In the Events per second (Critical) field. 2. you discard all changes. In the Health Policy Configuration page. 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. if you click Cancel. The alert level also lowers by one level (for Version 4. click Cancel. You must apply the health policy to the appropriate sensors if you want your settings to take effect. The restart counter does not count actual restarts. Even if multiple restarts occur between tests. select IPS Event Rate.Using Health Monitoring Configuring Health Policies Chapter 15 To configure IPS Event Rate Monitor health module settings: Access: Maint/Admin 1. the module only increments the restart counter by one each time it checks. select the other module from the list at the left of the page.IPS Event Rate page appears. 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. In the Events per second (Warning) field. The module checks if any restarts occurred during the period between tests. 3. 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. all changes you made will be saved. 5. click Save Policy and Exit. the module resets the counter to zero. See Applying Health Policies on page 528 for more information. 4. The Health Policy Configuration .9.1 Sourcefire 3D System Administrator Guide 516 .

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

Select On for the Enabled option to enable use of the module for health status testing. Version 4. all changes you made will be saved.Link State Propagation monitor page appears. You have three options: • • • To save your changes to this module and return to the Health Policy page. select the other module from the list at the left of the page. If a link state propagates to the paired interface.1 Sourcefire 3D System Administrator Guide 518 . click Save Policy and Exit. The Health Policy Configuration . To temporarily save your changes to this module and switch to another module’s settings to modify. 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. if you click Cancel. You must apply the health policy to the appropriate sensors if you want your settings to take effect.Using Health Monitoring Configuring Health Policies Chapter 15 5. 2. 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. See Applying Health Policies on page 528 for more information. To return to the Health Policy page without saving any of your settings for this module. click Cancel. select Link State Propagation.9. If you click Save Policy and Exit when you are done. you discard all changes. On the Health Policy Configuration page. To configure Link State Propagation health module settings: Access: Maint/Admin 1.

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

3D3500. 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.9.1 Sourcefire 3D System Administrator Guide 531 .Using Health Monitoring Configuring Health Policies Chapter 15 Applicable health modules for various appliances are listed in the Health Modules Applicable to Appliances table. 3D4500. 3Dx800. MDC3000. 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. and 3D6500 Version 4.

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. with the Policy Run Time Interval settings selected. 3D Sensors with RNA To edit a health policy: Access: Maint/Admin 1.9. Modify settings as needed.1 Sourcefire 3D System Administrator Guide 532 . 2.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 Monitor page appears. 4. The Health Policy Configuration page appears. Click Edit next to the policy you want to modify. 3. The Health Policy page appears. Click Health Policy in the health monitor toolbar.

5.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. To temporarily save your changes to this module and switch to another module’s settings to modify. all changes you made will be saved. If you delete a policy that is still applied to an appliance. any health monitoring alerts in effect for the sensor remain active until you Version 4. Reapply the policy to the appropriate appliances as described in Applying Health Policies on page 528.1 Sourcefire 3D System Administrator Guide 533 . 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. click Save Policy and Exit. In addition. you discard all changes. if you click Cancel. click Cancel. the policy settings remain in effect until you apply a different policy. To return to the Health Policy page without saving any of your settings for this module. You have three options: • • • 6.9. If you click Save Policy and Exit when you are done. Deleting Health Policies Requires: DC/MDC You can delete health policies that you no longer need.

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

9. Note that if your Defense Center is in a high availability configuration. On the toolbar. you can blacklist the RNA Host License Limit status messages until you install a new license with more hosts. If you need to disable the results of a group of appliances’ health monitoring. Therefore if you blacklist a sensor. the appliances report a disabled status in the Appliance Status Summary. you can blacklist the group of appliances. IMPORTANT! On a Defense Center. 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. click Blacklist. A blacklist icon ( ) and a notation are visible once you expand the view for a blacklisted or partially blacklisted appliance. you can blacklist the policy. TIP! You can blacklist 3D Sensors only from a Defense Center. Select Operations > Monitoring > Health. Once the blacklist settings take effect. Health Monitor blacklist settings are system settings. You cannot blacklist intrusion agents. 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. To blacklist an entire health policy or group of appliances: Access: Maint/Admin 1. For more information on expanding that view. 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.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 RNA host licenses on an appliance. Version 4. see Using the Health Monitor on page 545. The Health Monitor page appears. then delete it and later re-register it with the Defense Center. not a Master Defense Center. 2. The newly re-registered sensor remains blacklisted. The Blacklist page appears. 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. you can blacklist a managed sensor on one HA peer and not the other. the blacklist settings remain persistent.1 Sourcefire 3D System Administrator Guide 535 .

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

When any part of a module is blacklisted. The page refreshes then indicates the blacklisted state of the appliances. When blacklisting modules for Defense Centers. 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. you can blacklist the Traffic Status module for that detection engine. you can blacklist that module for a specific detection engine. You may want to do this to prevent events from the module from changing the status for the appliance to warning or critical. 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.Using Health Monitoring Using the Health Monitor Blacklist Chapter 15 4. Note that modules that allow you to select a specific detection engine have an arrow next to the module.9. In addition. For some modules. For example.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. then click Apply. To blacklist an individual appliance. select and expand a category folder. Blacklisting a Health Policy Module Requires: DC/MDC You can blacklist individual health policy modules on appliances. Click Edit and see Blacklisting a Health Policy Module on page 537 to blacklist individual health policy modules. the line for that module appears in boldface type in the Defense Center web interface. Defense Center Only Specific health policy modules operate for a Defense Center. select the box next to the appropriate appliance.

When blacklisting modules for Master Defense Centers. To blacklist an individual health policy module: Access: Maint/Admin 1. On the toolbar. see the Health Modules Applicable to Appliances table on page 531.1 Sourcefire 3D System Administrator Guide 538 . TIP! Once the blacklist settings take effect. Select Operations > Monitoring > Health.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. Make sure that you keep track of individually blacklisted modules so you can reactivate them when you need them. 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. click Blacklist. You may miss necessary warning or critical messages if you accidentally leave a module disabled.9. The Health Monitor page appears. The Blacklist page appears. Version 4. 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. 2.

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

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

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

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

Modify settings as needed. or alert associated with the health monitor alert. health module.1 Sourcefire 3D System Administrator Guide 543 . The Health Monitor Alerts page appears. Select the alert you want to modify in the Active Health Alerts list.9. see Creating Health Monitor Alerts on page 540. 5. Select Operations > Monitoring > Health. 4. For more information. 6.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. Click Health Monitor Alerts in the health monitor toolbar. Version 4. Click Save to save the modified health alert. To edit health monitor alerts: Access: Admin 1. 3. A message appears. Click Load to load the configured settings for the selected alert. 2. The Health Monitor page appears. indicating if the alert configuration was successfully saved.

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

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. Version 4. 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. Administrators can create and apply a health policy to an appliance. The pie chart supplies another view of the health status breakdown. plus the Defense Center.1 Sourcefire 3D System Administrator Guide 545 .Reviewing Health Status Chapter 16 Administrator Guide You can obtain information about the health of your Sourcefire 3D System through the Health Monitor. indicating the percentage of appliances currently in each health status category.9.

TIP! If the arrow in the row for a status level points down.9. the appliance list for that status shows in the lower table.Reviewing Health Status Using the Health Monitor Chapter 16 To use the health monitor: Access: Maint/Admin/ Any Analyst except Restricted 1. 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. The Health Monitor page appears. If the arrow points right. Click Health Monitor on the toolbar. 2. 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.1 Sourcefire 3D System Administrator Guide 546 .

1 Sourcefire 3D System Administrator Guide 547 . Indicates that warning limits have been exceeded for at least one health module on the appliance and the problem has not been corrected. 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. or that the appliance is currently unreachable. including modules that were in a Critical or Warning state. by severity.9. as described in the Health Status Indicator table. Version 4. Indicates that an appliance is disabled or blacklisted. Critical. that the appliance does not have a health policy applied to it. IMPORTANT! Your browser session will not be automatically timed out while you are viewing the Health Monitor page.Reviewing Health Status Using Appliance Health Monitors Chapter 16 Interpreting Health Monitor Status Available status categories. 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. Normal. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. 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. Contact your technical support representative to obtain an update to the health monitoring module. Indicates that all health modules on the appliance are running within the limits configured in the health policy applied to the appliance. and Disabled.

the appliance list is hidden. click the name of the appliance for which you want to view details in the health monitor toolbar. the appliance list for that status shows in the lower table. The Health Monitor Appliance page appears. Select Operations > Monitoring > Health. The Alert Detail list toggles the display to show or hide events. Optionally.9. TIP! If the arrow in the row for a status level points down. click the arrow in that status row. 2. click the color for the event status category you want to view. 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. The Health Monitor page appears. For more information.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. To show the list of appliances with a particular status. In the Appliance column of the appliance list. If the arrow points right. 3.1 Sourcefire 3D System Administrator Guide 548 . 4. in the Module Status Summary graph.

Version 4. Normal. Critical. as described in the Appliance Health Status Indicator table that follows. Viewing Alerts by Status Requires: DC/MDC You can show or hide categories of alerts by status. Disabled Blue Indicates that a module is disabled or blacklisted. include Error. 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. Indicates that the critical limits have been exceeded for the health module on the appliance and the problem has not been corrected.1 Sourcefire 3D System Administrator Guide 549 . or that the appliance is currently unreachable. by severity.9. Normal Green Indicates that the monitored item is running within the limits configured in the health policy applied to the appliance. 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. Recovered Green Indicates that the health for the monitored item is back within the limits configured in the health policy applied to the appliance. Warning. 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. that the appliance does not have a health policy applied to it. Contact your technical support representative to obtain an update to the health monitoring module.

The alerts for that category appear in the Alert Detail list. To expand the appliance list to show appliances with a particular status. To run all health modules for the appliance: Access: Maint/Admin/ Any Analyst except Restricted 1. Select Operations > Monitoring > Health.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. the appliance list is hidden. The alerts in the Alert Detail list for that category disappear. click the arrow in that status row. The Health Monitor page appears. Version 4. 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. 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.1 Sourcefire 3D System Administrator Guide 550 .9. 2. However. TIP! If the arrow in the row for a status level points down. If the arrow points right. 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.

IMPORTANT! When you manually run health modules. 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 Health Monitor Appliance page appears.9.1 Sourcefire 3D System Administrator Guide 551 . then refresh the page by clicking the sensor name. the first refresh that automatically occurs may not reflect the data from the manually-run tests. 4. You can also wait for the page to refresh again automatically. wait a few seconds. you can also run a health module test on demand to collect up-to-date health information for that module.Reviewing Health Status Using Appliance Health Monitors Chapter 16 3. In the Appliance column of the appliance list. Click Run All Modules. However. click the name of the appliance for which you want to view details in the health monitor toolbar. If the value has not changed for a module that you just ran manually. The status bar indicates the progress of the tests. Version 4. then the Health Monitor Appliance page refreshes.

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

click the color for the health alert status category you want to view. the appliance list is hidden. The Alert Detail list expands to list the health alerts for the selected appliance for that status category.1 Sourcefire 3D System Administrator Guide 553 .9. the appliance list for that status shows in the lower table. Select Operations > Monitoring > Health. Version 4. click the name of the appliance for which you want to view details in the health monitor toolbar. The Health Monitor page appears. In the Appliance column of the appliance list. To generate a health module alert graph: Access: Maint/Admin/ Any Analyst except Restricted 1. 2. The Health Monitor Appliance page appears. In the Module Status Summary graph of the Health Monitor Appliance page. 3. To expand the appliance list to show appliances with a particular status. TIP! If the arrow in the row for a status level points down. click the arrow in that status row.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. If the arrow points right. 4.

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

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

9. 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. If you understand what conditions each health module tests for. Version 4. Understanding Health Event Views The Defense Center health monitor logs health events. you retrieve all health events for all managed appliances. see Understanding Health Modules on page 485. When you access health events from the Health Monitor page on your Defense Center. you can more effectively configure alerting for health events. For a description of the health modules that generated the events that you may see on this page.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. 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. Searching for Health Events on page 563 describes how to search for specific events using the Event Search page. which you can see on the Health Event View page. For more information on the different types of health modules that generate health events. see Understanding Health Modules on page 485. For more information. For more information about viewing and searching for health events. Viewing Health Events on page 556 describes how to access and use the Event View page.1 Sourcefire 3D System Administrator Guide 556 .

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. click the arrow in that status row. containing all health events. click Health Events. The bookmarked view retrieves events within the time range you are currently viewing. Select Operations > Monitoring > Health. The Health Monitor page appears. In the toolbar. The Health Monitor page appears. For more information.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. Select Operations > Monitoring > Health. but you can then modify the time range to update the table with more recent information if needed. you may need to adjust the time range. The Events page appears. 2. the appliance list for that status shows in the lower table. 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.9. If the arrow points right. To view the health events for a specific module: Access: Maint/Admin/ Any Analyst except Restricted 1. If no events appear. the appliance list is hidden. See Setting Event Time Constraints in the Analyst Guide for more information.1 Sourcefire 3D System Administrator Guide 557 . 2. see Setting Event Time Constraints in the Analyst Guide. To expand the appliance list to show appliances with a particular status. Version 4.

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

then confirm you want to delete all the events. select the check box next to the events you want to delete and click Delete. 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. select Analysis & Reporting > Bookmarks or.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.. from any event view. click View Bookmarks. change what columns display in the table of events. 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. See Using Bookmarks in the Analyst Guide for more information. 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. click Report Designer. or constrain the events that appear delete health events find more information in Sorting Drill-down Workflow Pages in the Analyst Guide. click Delete All.9. To delete all the events in the current constrained view. See Using Bookmarks in the Analyst Guide for more information. find more information in Navigating between Workflows in the Analyst Guide. find more information in Understanding the Health Events Table on page 561. Health Event View Functions To. See Generating Reports from Event Views on page 235 for more information.1 Sourcefire 3D System Administrator Guide 559 . provide a name for the bookmark and click Save. sort the events that appear. This can occur even if you configured a sliding time window for the appliance. click Bookmark This Page.. find more information in Navigating to Other Pages in the Workflow in the Analyst Guide... find more information in Setting Event Time Constraints in the Analyst Guide.

Reviewing Health Status Working with Health Events Chapter 16 Health Event View Functions (Continued) To... NFE temperature Version 4. 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. • If NFE temperature exceeds 99 degrees Fahrenheit. See Selecting Workflows in the Analyst Guide for more information. click the status icon in the Status column for an event with that status. 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.9.1 Sourcefire 3D System Administrator Guide 560 . The triggering condition can be found in the message detail for the alert. 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 NFE temperature. click the down arrow link on the left side of the event. click Workflows or select from the Workflows dropdown list in the toolbar.. click View All. select another health events workflow You can. health status for the Hardware Alarms module changes to red and the message details include a reference to the NFE temperature. hardware alarms generate in response to the events described in the Conditions Monitored for 3D9900 Sensors table.. • If NFE temperature exceeds 89 degrees Fahrenheit. NFE Platform daemon If the NFE Platform daemon goes down. 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 card presence.

If the Ftwo daemon goes down. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon.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 Rulesd daemon goes down. If the nfm_ipfragd daemon goes down. The Health Monitor modules you choose to enable Version 4. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. If the NFE TCAM 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. health status for the Hardware Alarms module changes to red and the message details include a reference to the daemon. including hardware and software status.1 Sourcefire 3D System Administrator Guide 561 .9. 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. You create and apply health policies to your appliances. If the Psls daemon goes down. health status for the Hardware Alarms module changes to red and the message details include a reference to the LBIM presence. If the Load-Balancing Interface Module (LBIM) switch assembly is not present or not communicating. 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. If the Scmd daemon goes down. which monitor a variety of aspects.

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

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

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

Loading a Saved Search in the Analyst Guide Deleting a Saved Search in the Analyst Guide For more information about searching. You have the following options: • Click Search to execute the search. see Configuring Event View Settings on page 27. TIP! If you want to save a search as a restriction for restricted data users. Optionally. if you want to save the search so that other users can access it. disable the Save As Private check