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

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

such as the home page. time zone. Logging Out of the Appliance on page 24 explains how to log out of the web interface.1 Sourcefire 3D System Administrator Guide 14 . and event viewing preferences. dashboard. 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.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. 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. Using the Context Menu on page 36 explains how to display a context-specific menu of shortcuts on certain pages in the web interface. Specifying Your User Preferences on page 25 explains how to configure the preferences that are tied to a single user account.9. • • • 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 to Set Up an Account on page 23 explains how to set up an association between a external user account and a set of credentials on the appliance. • • • Version 4. account password.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Platform requirement information for specific aspects of a feature is provided where needed. or DC3000 appliance used as a Defense Center Version 4.1 Sourcefire 3D System Administrator Guide 38 . All platform information is formatted with an orange typeface. Virtual Defense Center. Any DC Any appliance with any combination of licenses A DC500.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. DC1000. The following table defines the abbreviations used to indicate each different platform requirement: Platform and Licensing Requirement Abbreviations Requires Acronym 3D Sensor Indicates One of the following Series 1 or Series 2 sensors: • 3D500 • 3D1000 • 3D2000 • 3D2100 • 3D2500 • 3D3500 • 3D4500 • 3D6500 • 3D9900 This acronym on its own indicates that the task in question can be performed on any of these sensors even if an IPS license is not applied on the sensor and the sensor is not managed. Refer to Access Requirements Conventions on page 39 for the meaning of the Access statement at the beginning of each procedure. 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.9. Refer to Platform Requirements Conventions on page 38 for the meaning of the Requires statement at the beginning of each section.

you can change an expired password on a Defense Center or Master Defense Center or on a 3D Sensor. 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. All access information is formatted with a green typeface.9.1 Sourcefire 3D System Administrator Guide 39 . A “+” conjunction indicates that the platforms are required in combination. In contrast. For example.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. so the Changing an Expired Password topic has a Requires statement of DC/MDC or 3D Sensor. to manage a Defense Center with a Master Defense Center. so the Adding a Master Defense Center topic has a Requires statement of MDC + DC. you need both a Defense Center and a Master Defense Center. The following table defines the abbreviations used to indicate each different platform requirement: Access Requirement Abbreviations Requires Acronym Admin Any Any Analyst Any except Restricted Indicates User must have the Administrator role User can have any role User can have any analyst role User can have any role except Restricted Analyst or Restricted Analyst (Read Only) Version 4.

The Access setting for the procedure in the Working with the Hosts Network Map topic is Any RNA/Admin.1 Sourcefire 3D System Administrator Guide 40 . Rule thresholding in the packet view provides an example of required combined access roles. 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.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. For example.9. a user must have the RNA Event Analyst or RNA Event Analyst (Read Only) role or the Restricted Event Analyst or Restricted Event Analyst (Read Only) role with RNA Hosts Data set to Show All Data or to show a specific search. to view the Hosts network map. A “+” conjunction indicates that the platforms are required in combination.

3/8.1 Sourcefire 3D System Administrator Guide 41 .255 Subnet Mask 255.168.0 255.0.Introduction to the Sourcefire 3D System IP Address Conventions Chapter 1 from the packet view.0.0/8 172.0.31.1. without changing your user input.16. variables.0.536 When you use CIDR notation to specify a range of IP addresses. 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. CIDR Notation Syntax Examples CIDR Block 10.255.0.16.0.255 192.0.0. For example.3/8.1. the following table lists the private IPv4 address spaces in CIDR notation.777 . the Sourcefire 3D System uses only the masked portion of the network IP address you specified. the Access setting for the procedure in the Setting Threshold Options within the Packet View topic is IPS + P&R Admin/Admin.0.0.0.0 192.216 1.0/12 192. but the web interface continues to display 10.0 255.0/16 IP Addresses in CIDR Block 10.255.240.255. 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/8. 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.0 Number of IP Addresses 16.9. As a result. if you type 10.0.0. For example. the Sourcefire 3D System uses 10.168.2.048.168.255.2.0 10.0.0 172.255 172.255.576 65. Version 4.

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

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

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

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

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

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

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

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

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

80 162 389. Notes Version 4. Open this port for communications between the Defense Center and Intrusion Agents.9. Open this port only if you are using a remote syslog server. Open this port when you connect to a remote web server through the RSS widget. 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. 21 22 23 25 53 67 68 . Refer to the Required Open Ports table for more information on functions and their associated ports.Performing the Initial Setup Communication Ports Chapter 2 certain functionality within the network deployment. Open this port for communicatiosn between the Defense Center and RUA Agents.1 Sourcefire 3D System Administrator Guide 51 . Required Open Ports Ports 20.

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

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

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

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

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

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

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

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

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

RNA events. These widgets are disabled and display error messages that indicate the reason why you cannot view them. Version 4. Although you cannot add an unauthorized or invalid widget to a dashboard.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. the widget displays an error message. Operations widgets display information about the status and overall health of the Sourcefire 3D System. The dashboard widgets that you can view depend on the type of appliance you are using and on your user role. Currently the only widget in this category displays an RSS feed. Intrusion Event Analyst. as well as rearrange the widgets on a tab. if you import a dashboard created either on a different kind of appliance or by a user with different access privileges. Also note that widgets cannot display data to which an appliance has no access. RUA events. add and remove widgets from tabs. Miscellaneous widgets display neither event data nor operations data. For example. and so on. while the Compliance Events widget is available only on the Defense Center for users with Administrator. For more information.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. 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. An unauthorized widget is one that you cannot view because you do not have the necessary account privileges. In addition. For example. that dashboard may contain unauthorized or invalid widgets. You can minimize and maximize widgets. each dashboard has a set of preferences that determines its behavior. If you import a dashboard onto a Master Defense Center that contains a Custom Analysis widget configured to display one of those data types.1 Sourcefire 3D System Administrator Guide 61 . the Appliance Information widget is available on all appliances for all user roles. or RNA Event Analyst account privileges. the Master Defense Center cannot access flow data.

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

IMPORTANT! dashboards. 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.Using Dashboards Understanding Dashboard Widgets Chapter 3 Sourcefire Appliances and Dashboard Widget Availability (Continued) Widget System Load System Time White List Events Master Defense Center X X X Defense Center X X X 3D Sensor with IPS (and RNA) X X 3D Sensor with RNA (only) X X The User Roles and Dashboard Widget Availability table lists the user account privileges required to view each widget.1 Sourcefire 3D System Administrator Guide 63 .9. An X indicates the user can view the widget.

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

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

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

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

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

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

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

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

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

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

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

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. based on the number of flows where the host initiated the session. 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. Displays the most active hosts on your monitored network. Displays the most frequently occurring types of intrusion events. by classification. Displays the most active hosts on your monitored network. Displays the most active ports on your monitored network. based on the number of detected flows. 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. where the packet was dropped. Displays the most active services on your monitored network.) . by application type. Displays the most active client applications on your monitored network. (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 counts for the most frequently occurring intrusion events.Using Dashboards Understanding the Predefined Widgets Chapter 3 each preset.1 Sourcefire 3D System Administrator Guide 75 .9. by classification.

based on the number of intrusion events where the host was the targeted host in the flow that caused the event.9. 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. Displays the most active hosts on your monitored network. based on the number of hosts on the network running services made by that vendor.1 Sourcefire 3D System Administrator Guide 76 . based on event classification. Displays the most common operating system.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. based on the number of intrusion events where the host was the attacking host in the flow that caused the event. Displays the most active hosts on your monitored network. Displays the most common RNA service vendors. based on frequency of intrusion events. Displays a count of intrusion event requiring analysis. over the dashboard time range. Displays the most frequently occurring types of intrusion events. Predefined Dashboards Flow Summary Requires DC + RNA Intrusion Events Requiring Analysis Intrusion Events by Hour Intrusion Events to High Criticality Hosts Detailed Dashboard DC/MDC + IPS + RNA IPS or DC/MDC + IPS DC/MDC + IPS + RNA none Detailed Dashboard Operating Systems Detailed Dashboard DC + RNA Services Detailed Dashboard DC + RNA Top Attackers Default Dashboard IPS or DC/MDC + IPS Top Targets Default Dashboard IPS or DC/MDC + IPS Version 4. Displays the most active hours of the day.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

SSL-encrypted communication channel between the Defense Center and the sensor. you set up a two-way.9. 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. 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 must use a unique NAT ID when adding the New York 3D Sensor to the Defense Center.1 Sourcefire 3D System Administrator Guide 113 . Working with Sensors Requires: DC + 3D Sensor When you manage a sensor. it generates events and sends them to the Defense Center using the same channel. However.Using the Defense Center Working with Sensors Chapter 4 be unique. and then use a different unique NAT ID when adding the Miami 3D Sensor. The Defense Center uses this channel to send information (in the form of policies) to the sensor about how you want to analyze your network traffic.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

export. delete. delete. and apply RNA detection policies from a Master Defense Center. Note that SEUs can also contain new and updated decoders and preprocessors. 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.9. 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. and apply default health policies to the Master Defense Center and to connected Defense Centers. • Using RNA Detection Policies on a Master Defense Center Requires: MDC You can create. Importing SEUs and Rule Files in the Analyst Guide explains how to download and import Security Enhancement Updates (SEUs) that contain new intrusion rules. This section also explains how to configure rules in inline intrusion policies so that they drop malicious packets.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. 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. Refer to the following.1 Sourcefire 3D System Administrator Guide 162 . edit. and for brief descriptions of those modules that are used.

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

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

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

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

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

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

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

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

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

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

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

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

then click Edit next to the Defense Center. select Appliances from the Operations menu.1 Sourcefire 3D System Administrator Guide 175 . See the following sections for more information. Note that this is the name of the Defense Center in the Master Defense Center web interface. • • • • • 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.9. The operating system currently running on the managed Defense Center. The Vulnerability Database version on the managed Defense Center. The IP address of the managed Defense Center.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. you can use the Master Defense Center web interface to view and edit the configuration of the Defense Center. Product Model Software Version Operating System Operating System Version VDB Version IP Address Version 4. The Information page for a managed Defense Center includes the fields described in the Defense Center Information table. Defense Center Information Field Name Description The assigned name for the Defense Center. not the hostname. The version of the software currently installed on the managed Defense Center. The version of the operating system currently running on the managed Defense Center. The model name for the managed 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 want to send intrusion events (with or without packet data). Model Number Current Group The model number for the Defense Center. a pop-up message indicates how long it has been (in hours. and seconds) since the Defense Center communicated with the Master Defense Center. you can also specify which intrusion events are sent based on their impact flag. 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. minutes. If you hover your cursor over the icon. You can click Refresh to update the Status icon and its accompanying pop-up message. intrusion events and related packet data. This number can be important for troubleshooting. 2. Your options are to send intrusion events.1 Sourcefire 3D System Administrator Guide 176 . Change the Defense Center’s attributes as needed. and compliance events.9. To edit a managed Defense Center’s settings: Access: Admin 1. if any. The group that the Defense Center belongs to. The updated Defense Center attributes are saved. 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. Click Save.

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

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

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

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

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

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

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 190 . 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 Maximum column indicates the total number of detection resources available on the sensor. • • 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. • 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.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. 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. 3D Sensors can run combinations of IPS. can be any type Maximum of two.

Version 4.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. current Crossbeam System hardware and software support. Understanding Default Detection Engines Requires: DC or 3D Sensor When you install a new 3D Sensor. The number of detection resource depends on the Crossbeam System hardware. you can reduce latency by distributing your network traffic across all available interfaces on the sensor. and detection resources available on Crossbeam System hardware. the maximum number of detection engines that you can create is equal to the number of available detection resources. you can use initial interface sets and default detection engines to quickly begin evaluating network traffic. Consider how your network is configured and how you want to deploy the Sourcefire 3D System within it. After initial installation can modify interface sets and detection engines. Crossbeam-based Software Sensor Considerations Depending upon the capabilities of your X-Series and the products you are licensed to use.9.1 Sourcefire 3D System Administrator Guide 191 . As with other 3D Sensors. you have several deployment options for 3D Sensor Software. then distribute the detection engines and detection resources across all operative interfaces on the sensor. Refer to the Sourcefire 3D Sensor Software for X-Series Installation Guide for information on deployment scenarios.

Passive that builds a single passive interface set for all 3D Sensor interfaces. the second on-board interface cannot support the same high-performance standards as the interfaces on the network interface cards. for example. the default that builds paired fail-open interface sets on all 3D Sensor interfaces.1 Sourcefire 3D System Administrator Guide 192 . If your appliance has one of these extra interfaces. Sourcefire recommends that you remove the second on-board interface from the detection engine for improved performance. see Editing a Detection Engine on page 194. Select Inline with Fail-Open Mode if you cabled the sensing interfaces inline on your network as an IPS. less the management interface. 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. IMPORTANT! For the 3D3000 on the IBM xSeries 346 appliance. Choose from these initial interface sets based on how you deployed the sensor. 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. With this configuration. on some of the older models. 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. less the management interface. that is automatically included in the default detection engine. Version 4. 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. If you modify the default detection engine to include it.9. Second On-Board Interface Some Sourcefire sensors have a second on-board interface. the detection engine may not provide optimum performance. However. typically you pair adjacent interfaces. note that the default detection engine does not include the second on-board interface. Select Passive Mode if the sensing interfaces are not cabled inline.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. and you have deployed it in a high-bandwidth environment where the traffic load is likely to reach the design limits of the appliance. usually near the management interface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 .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.

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

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

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

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

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

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

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 . A list of sensors appears. Optionally. a list of sensor groups appears. You can set any jumbo frame size between 1518 and 9018 bytes. Version 4. The following shows a 3D9900 interface set. A list of network interfaces on the sensor appears. Defense Center Only Select one of the sensors from the list.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 10. including a list of ungrouped sensors.9. 12. inclusive. You can also select the ungrouped sensors. 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. 11.

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

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

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

set jumbo frame options on the Crossbeam CLI. a list of sensor groups appears. and if you are configuring an interface set on a 3D9900. you can select a Bypass Threshold in milliseconds (ms). Version 4. Select one of the sensors from the list. Optionally. The following shows a 3D9900 interface set. a list of paired network interfaces on the sensor’s fail-open cards appears. The default setting is 750 ms and the valid range is from 250 ms to 60. When the option selected. select Automatic Application Bypass if your network is sensitive to latency. 8.000 ms. Optionally. 7.Using Detection Engines and Interface Sets Using Interface Sets Chapter 6 6. however.1 Sourcefire 3D System Administrator Guide 219 . You can. 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 with fail open interface set. 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. inclusive. including a list of ungrouped sensors. you can select the Enable Fail-safe check box to enable traffic pass-though during application bypass.9. Optionally. If you are creating an inline interface set. You can set any jumbo frame size between 1518 and 9018 bytes. 9.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Version 4. TIP! If you need to go back to the drill-down page where you opened the Report Designer. Click Report Designer in the toolbar. The settings on the page reflect the parameters that you selected for the search or through the drill-down pages. Change any of the parameters as necessary to meet your needs. 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 . 4.9. see Creating a Report Profile on page 246. 5. 3. or CSV.Working with Event Reports Generating Reports from Event Views Chapter 7 2. The Report Designer page appears. HTML. Note that you may select more than one format. For details on the parameters for a report. Click Generate Report. The following graphic shows the Defense Center version of the page.

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 243 . you have created a new report profile. The following graphic shows the Blocked Events report profile on the Defense Center version of the page. and Host Audit. Version 4. Note that if you modify the default settings. High Priority Events.Working with Event Reports Understanding Report Profiles Chapter 7 Predefined reports are provided by the Sourcefire system: Blocked Events. 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. The following tables provide the default settings for each of the predefined report profiles.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 . An X indicates that the user can access the option. 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. Users with only Rules or Maintenance access cannot see the Analysis & Reporting menu at all.

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 314 .

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

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

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.1 Sourcefire 3D System Administrator Guide 317 .9. Operations Menu Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res. An X indicates that the user can access the option. 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. All users can access at least some options on the Operations menu.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 RUA Sensors User Management System Settings System Policy Update Monitoring Statistics Performance | IPS Performance | RNA Audit Task Status Syslog Health Tools Scheduling Backup/Restore Import/Export Whois Scan Results Scanners X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X Version 4.1 Sourcefire 3D System Administrator Guide 318 .9.Managing Users Managing User Accounts Chapter 8 Operations Menu (Continued) Menu Admin Maint RNA/ RNA-RO Event Analyst IPS/ IPS-RO Event Analyst Res.

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

9. For example.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. your organization’s security policies may require that Version 4. 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.1 Sourcefire 3D System Administrator Guide 320 .

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

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

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

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

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

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

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

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

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

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

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

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

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. flow summaries.1 Sourcefire 3D System Administrator Guide 333 . The Database Event Limits on page 333 below describes the maximum number of records you can store in the databases on your appliance.. or DC1000 100 million events on the DC3000 10 million events on the DC500. if you specify 100 million intrusion events and apply that policy to a 3D Sensor). In addition. 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. any health alert limits you set in the policy have no effect on the sensors.. the maximum limit for the appliance is silently enforced. database limits that do not apply to a particular appliance are silently ignored. 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.. Virtual Defense Center.9. Virtual Defense Center. For example. and health events..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.Managing System Policies Configuring the Parts of Your System Policy Chapter 9 These databases include those that store RNA and RUA events. 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.. Database Event Limits The. 2.. as well as flow events.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. You can also choose to back up the following. The configuration files include information that uniquely identifies a sensor and cannot be shared. those updates are not backed up. WARNING! Do not use the backup and restore process to copy the configuration files between sensors. 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. 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. By default.9. Version 4. While each organization’s backup plan is highly individualized. system configuration files are saved in the backup file.1 Sourcefire 3D System Administrator Guide 413 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

see Understanding Health Monitoring on page 483.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. 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. For example. on the Host Statistics page you can monitor basic host statistics. you can also use the health monitor to monitor disk usage and alert on low disk space conditions.1 Sourcefire 3D System Administrator Guide 463 . and statistics for the Data Correlator and RNA processes for the current day. intrusion event information. For more information. 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. Version 4.9.

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

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

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

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

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

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

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

1 Sourcefire 3D System Administrator Guide 471 .Monitoring the System Understanding Running Processes Chapter 14 To collapse the process list: Access: Maint/Admin Click the up arrow next to Processes. 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. The System Daemons table lists daemons that you may see on the Process Status page and provides a brief description of their functionality. and checks for working SSL and valid certificate authentication. The process list collapses. 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. Understanding Running Processes There are two different types of processes that run on an appliance: daemons and executable files. 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. They ensure that services are available and spawn processes when required.9. This table is not an exhaustive list of all processes that may run on an appliance. and executable files are run when required. Daemons always run.

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

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. Ensures that the MAC address stays constant Handles access restriction based on changes made to the Access Configuration page. See Configuring the Access List for Your Appliance on page 325 for more information about access configuration.9. 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.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.

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. 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 . 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. handles communication between Defense Centers and sensor.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. decodes and performs session reassembly.9. correlating acquired data with the RNA fingerprint database. indicating that the appliance is active.

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

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

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

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. the data may not change until the next five-minute increment occurs.Monitoring the System Viewing RNA Performance Statistics Chapter 14 • • the number of packets. last day. See the following sections for more information: • • Generating RNA Performance Statistics Graphs on page 479 Saving RNA Performance Statistics Graphs on page 481 Generating RNA Performance Statistics Graphs Requires: DC + RNA You can generate graphs that display performance statistics for managed 3D Sensors with RNA. To access the RNA Performance page: Access: Maint/Admin Select Operations > Monitoring > Performance > RNA. or last month of operation. last week.1 Sourcefire 3D System Administrator Guide 479 . New data is accumulated for statistics graphs every five minutes. in thousands. 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.9. The RNA Performance Statistics Graph Types table lists the available graph types. The RNA page appears. Therefore. if you reload a graph quickly.

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

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

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

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

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

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

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

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

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

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

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

To configure automatic application bypass monitoring status: Access: Maint/Admin 1. select the other module from the list at the left of the page. click Cancel. See Applying Health Policies on page 528 for more information. Version 4. To temporarily save your changes to this module and switch to another module’s settings to modify. 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. Select On for the Enabled option to enable use of the module for health status testing. select Automatic Application Bypass Status. In the Health Policy Configuration page. If a bypass occurs. click Save Policy and Exit. To return to the Health Policy page without saving any of your settings for this module.1 Sourcefire 3D System Administrator Guide 502 . That status data feeds into the health monitor. For more information on automatic application bypass.9. You must apply the health policy to the appropriate appliances if you want your settings to take effect. see Automatic Application Bypass on page 212. this module generates an alert. You have three options: • • • To save your changes to this module and return to the Health Policy page. you discard all changes. 2. If you click Save Policy and Exit when you are done. all changes you made will be saved.Using Health Monitoring Configuring Health Policies Chapter 15 3. if you click Cancel. The Automatic Application Bypass Status page appears.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Using Health Monitoring Configuring Health Policies

Chapter 15

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

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

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

select the other module from the list at the left of the page. If you delete a policy that is still applied to an appliance. In addition. click Save Policy and Exit. click Cancel. if you click Cancel.1 Sourcefire 3D System Administrator Guide 533 . the policy settings remain in effect until you apply a different policy.9. you discard all changes. if you delete a health policy that is applied to a sensor. 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. 5. If you click Save Policy and Exit when you are done. Reapply the policy to the appropriate appliances as described in Applying Health Policies on page 528. all changes you made will be saved. any health monitoring alerts in effect for the sensor remain active until you Version 4. You have three options: • • • 6. Deleting Health Policies Requires: DC/MDC You can delete health policies that you no longer need.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.

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

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

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

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

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

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

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

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

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

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

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

Administrators can create and apply a health policy to an appliance. plus the Defense Center. 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. indicating the percentage of appliances currently in each health status category. The Status table provides a count of the managed appliances for this Defense Center by overall health status. The pie chart supplies another view of the health status breakdown.9.Reviewing Health Status Chapter 16 Administrator Guide You can obtain information about the health of your Sourcefire 3D System through the Health Monitor. see the following topics: • • • Using the Health Monitor on page 545 Using Appliance Health Monitors on page 547 Working with Health Events on page 555 Using the Health Monitor Requires: DC/MDC The Health Monitor page provides the compiled health status for all sensors managed by the Defense Center.1 Sourcefire 3D System Administrator Guide 545 . Version 4.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Note that clicking a value within a row in a table view constrains the table view and does not drill down to the next page. • To drill down to the next workflow page keeping the current constraints. • To drill down to the next workflow page constraining on some events.9. For more information. Version 4. click View All. Note that this only works on drill-down pages. keeping the current constraints drill down to the next page in the workflow You can. you move to the next page and constrain on the value. click the appropriate page link at the top left of the workflow page. use one of the following methods: • To drill down to the next workflow page constraining on a specific value. For more information.. select the checkboxes next to the events you want to view on the next workflow page.1 Sourcefire 3D System Administrator Guide 568 . TIP! Table views always include “Table View” in